Method, apparatus and device for reporting capability information, and storage medium

Abstract

This application discloses a method, apparatus, device, and storage medium for reporting capability information, relating to the field of mobile communications. The method includes: reporting capability information, which indicates the capability to perform joint channel estimation for downlink channels in an NTN. By having the terminal report its capability for joint channel estimation of downlink channels in an NTN, downlink joint channel estimation in the NTN system can be achieved, thereby improving downlink channel coverage in the NTN system.

Description

Technical Field

[0001] This application relates to the field of mobile communications, and in particular to a method, apparatus, device, and storage medium for reporting capability information. Background Technology

[0002] In non-terrestrial network (NTN) systems, the long distance between satellites (base stations) and ground terminals results in significant path loss, which can lead to limited coverage of some downlink channels. Summary of the Invention

[0003] This application provides a method, apparatus, device, and storage medium for reporting capability information. The technical solution is as follows:

[0004] According to one aspect of this application, a method for reporting capability information is provided, the method being executed by a terminal, the method comprising:

[0005] Report capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN.

[0006] According to another aspect of this application, a method for reporting capability information is provided, the method being performed by a network device, the method comprising:

[0007] The terminal receives capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN.

[0008] According to another aspect of this application, a capability information reporting device is provided, the device comprising:

[0009] A transmitting module is used to report capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN.

[0010] According to another aspect of this application, a capability information reporting device is provided, the device comprising:

[0011] The receiving module is used to receive capability information reported by the terminal, which indicates the capability to perform joint channel estimation for the downlink channels in the NTN.

[0012] According to another aspect of this application, a terminal is provided, the terminal comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the capability information reporting method as described above.

[0013] According to another aspect of this application, a network device is provided, the network device comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement a capability information reporting method as described above.

[0014] According to another aspect of this application, a computer-readable storage medium is provided, wherein executable instructions are stored in the storage medium, the executable instructions being loaded and executed by a processor to implement the capability information reporting method as described above.

[0015] According to another aspect of this application, a chip is provided, the chip including programmable logic circuitry and / or program instructions, which, when the chip is run on a computer device, are used to implement the capability information reporting method described above.

[0016] According to another aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium, wherein a processor reads from the computer-readable storage medium and executes the computer instructions, causing a computer device to perform the capability information reporting method described above.

[0017] The technical solution provided in this application includes at least the following beneficial effects:

[0018] By enabling terminals to report joint channel estimation for downlink channels in NTN, downlink joint channel estimation in the NTN system can be achieved, thereby improving downlink channel coverage in the NTN system. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of an NTN scenario based on transparent payload provided in an exemplary embodiment of this application;

[0021] Figure 2 This is a schematic diagram of an NTN scenario based on regenerative load provided in an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart of a capability information reporting method provided in an exemplary embodiment of this application;

[0023] Figure 4 This is a flowchart of a capability information reporting method provided in an exemplary embodiment of this application;

[0024] Figure 5 This is a flowchart of a capability information reporting method provided in an exemplary embodiment of this application;

[0025] Figure 6 This is a schematic diagram of a TDD spectrum provided in an exemplary embodiment of this application;

[0026] Figure 7 This is a schematic diagram of an FDD spectrum provided in an exemplary embodiment of this application;

[0027] Figure 8 This is a structural block diagram of a capability information reporting device provided in an exemplary embodiment of this application;

[0028] Figure 9 This is a structural block diagram of a capability information reporting device provided in an exemplary embodiment of this application;

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

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0031] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0032] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0033] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0034] An introduction to the NTN system:

[0035] Currently, the Third Generation Partnership Project (3GPP) is researching NTN technology. Compared to traditional terrestrial networks (TN), NTN systems utilize satellites and High Altitude Platform Stations (HAPS) for network deployment. Taking satellite communication as an example, theoretically only a few satellites are needed to achieve global coverage except for the polar regions. Compared to TN systems, NTN systems offer significant coverage advantages. Typical application scenarios for NTN systems include situations where base stations cannot be built or are damaged, such as continuous coverage in remote mountainous areas, deserts, oceans, and forests, or emergency communication during disasters or base station damage. Typical NTN system scenarios can be summarized as: all-terrain coverage, signaling offloading, emergency communication, the Internet of Things (IoT), and broadcast services.

[0036] NTN systems can include satellite systems. Based on satellite altitude, i.e., orbital altitude, satellite systems can be categorized into High Elliptical Orbit (HEO) satellites, Geostationary Earth Orbit (GEO) satellites, Medium Earth Orbit (MEO) satellites, and Low Earth Orbit (LEO) satellites. Furthermore, NTN systems may also include aerial network equipment such as High Altitude Platform Station (HAPS) communication systems; the network equipment involved in this application is not limited to the examples above.

[0037] LEO satellites: LEO satellites can be called non-geostationary satellites, and there are many types of non-geostationary satellites. Taking LEO satellites as an example, LEO satellites move relatively fast relative to the ground, approximately 7 km / s. Therefore, the coverage area provided by LEO satellites also moves with the LEO satellites. LEO satellite signals have short propagation distances, low link loss, and low requirements for the transmission power of user terminals.

[0038] GEO satellites: GEO satellites, also known as geostationary satellites, move at the same speed as the Earth's rotation system, thus remaining stationary relative to the ground. Consequently, the cell area of ​​a GEO satellite is also stationary. GEO satellite cells have a relatively large coverage area, typically with a cell diameter of 500 km.

[0039] In order to ensure the coverage of communication satellites and improve the system capacity of the entire satellite communication system, communication satellites use multi-beam coverage of the ground. A single communication satellite can form dozens or even hundreds of beams to cover the ground; a single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0040] Currently, 3GPP considers two types of satellites: transparent payload satellites and regenerative payload satellites. Figure 1 A schematic diagram of an NTN scenario based on transparent load transmission is shown. Figure 2 A schematic diagram of an NTN scenario based on regenerative load is shown.

[0041] The NTN network consists of the following network elements:

[0042] • One or more network devices 16: used to connect the satellite 14 and the data network 18 on the ground.

[0043] • Feeder Link: The link used for communication between network device 16 and satellite 14.

[0044] • Service Link: The link used for communication between user terminal 12 and satellite 14.

[0045] Satellite 14: Based on the functions it provides, it can be divided into two types: transparent payload and regenerative payload.

[0046] • Transparent payload: Provides only wireless frequency filtering, frequency conversion, and amplification functions. It only provides transparent signal forwarding and does not change the waveform signal it forwards.

[0047] • Regenerative payload: In addition to providing wireless frequency filtering, frequency conversion, and amplification functions, it can also provide demodulation / decoding, routing / conversion, and encoding / modulation functions. It has some or all of the functions of a base station.

[0048] • Inter-Satellite Links (ISL): Exist in NTN scenarios with regenerated payloads.

[0049] It should be noted that the terminal in the embodiments of this application can refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. Optionally, the terminal can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal in 5GS (5th Generation System), or terminal in the future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of this application are not limited in this respect.

[0050] The access network device in this application embodiment is a device deployed in an access network to provide wireless communication functions for terminals. Access network devices can include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the names of devices with access network device functions may differ; for example, in a 5G NR system, they are called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this application embodiment, the aforementioned devices providing wireless communication functions for terminals are collectively referred to as access network devices. Optionally, a communication relationship can be established between the terminal and core network devices through the access network device. For example, in a Long Term Evolution (LTE) system, the access network device can be one or more eNodeBs within an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, the access network device can be one or more gNBs within an RAN or RAN.

[0051] The core network equipment primarily functions to provide user connectivity, manage users, and bear services, serving as the interface to external networks. For example, core network equipment in a 5G NR system may include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, SMF (Session Management Function) entities, and Location Management Function (LMF) entities. Access network equipment and core network equipment can be collectively referred to as network equipment.

[0052] In NTN systems, the long distance between satellites (base stations) and ground terminals results in significant path loss, which can lead to limited coverage of some downlink channels.

[0053] This section introduces joint channel estimation:

[0054] Joint channel estimation can improve channel coverage. Joint channel estimation can include demodulation reference signal (DMRS) bundling. Specifically, the receiver (base station) uses the DMRS of multiple uplink channels (e.g., physical uplink shared channels) that are repeatedly transmitted by the transmitter (terminal) to jointly demodulate these multiple uplink channels. This improves the accuracy of channel estimation and, consequently, uplink channel coverage.

[0055] The prerequisite for using DMRS bundling is that the terminal can guarantee power consistency and phase continuity over a period of uplink transmission. According to existing standards, phase continuity (phase consistency) is satisfied when the phase difference between two slots is no greater than 25 or 30 degrees. For example, Table 1 shows the maximum allowable phase difference for DMRS bundling.

[0056] Table 1

[0057]

[0058]

[0059] For downlink joint channel estimation, network equipment (base stations) needs to ensure power consistency and phase continuity during downlink transmission, while the terminal also needs to have the capability for joint channel estimation of the downlink channel. The method provided in this application enables downlink joint channel estimation in the NTN system by having the terminal report its ability to perform downlink channel estimation for the NTN system, thereby improving downlink channel coverage in the NTN system.

[0060] Figure 3 A flowchart illustrating a capability information reporting method according to an embodiment of this application is shown. This method can be applied to a terminal. The method includes:

[0061] Step 302: Report capability information, which indicates the capability to perform joint channel estimation for downlink channels in NTN.

[0062] This terminal belongs to the NTN system and is capable of reporting this capability information to network devices within the NTN system. Terminals and network devices within the NTN system can be referenced... Figure 1 and 2 Examples are shown in the text.

[0063] Optionally, this capability information carries a single bit of information. This single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel. Alternatively, this single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink retransmission channel within a first duration. The downlink retransmission channel refers to the downlink channel that has been repeatedly transmitted. Optionally, the first duration refers to the duration occupied when the downlink retransmission channel is repeatedly transmitted a preset number of times, which is configured by the network device.

[0064] Alternatively, the capability information carries multiple bits of information reflecting a first duration for which the terminal supports joint channel estimation of the downlink channel. This downlink channel undergoes repeated transmissions, and the first duration is no greater than the duration of repeated transmissions of the downlink channel up to a preset number, which is configured by the network device. For example, the first duration is equal to the transmission duration of repeated transmissions of the downlink channel up to the preset number; in this case, the first duration can also be referred to as the maximum duration (N).

[0065] For example, this capability information carries 3 bits of information, the content of which is 111. These 3 bits reflect that the terminal supports (maximum supports) joint channel estimation of the downlink channel over 8 time units. Optionally, this multi-bit information can also be used to indicate the number of first durations for which the terminal supports joint channel estimation of the downlink channel. For example, 3 bits can be used to indicate 8 first durations for which the terminal supports joint channel estimation of the downlink channel.

[0066] Optionally, the unit of the first duration includes any of the following:

[0067] • Time slot;

[0068] ·millisecond;

[0069] • The number of time slots associated with SCS.

[0070] Optionally, the aforementioned capability information is reported for downlink channels. That is, the terminal can report capability information separately for different downlink channels. For example, the terminal reports first capability information and second capability information, where the first capability information is reported for the Physical Downlink Shared Channel (PDSCH), and the second capability information is reported for the Physical Downlink Control Channel (PDCCH). The capability information reported by the terminal for different downlink channels may be the same or different.

[0071] Optionally, the aforementioned capability information is reported for the downlink channel transmission mode. That is, for different downlink channel transmission modes, the terminal can report capability information separately, and the reported capability information may be the same or different. The aforementioned capability information can also be reported for the repetition type of the downlink channel. That is, for different repetition types of the downlink channel, the terminal can report capability information separately, and the reported capability information may be the same or different. For example, the terminal reports first capability information and second capability information, where the first capability information is reported for PDSCH repetition type A, and the second capability information is reported for PDSCH repetition type B. In this case, the capability information reported by the terminal for different downlink channel transmission modes may be the same or different.

[0072] After reporting capability information to the network device, the terminal receives a configuration duration from the network device, or the terminal can determine the configuration duration itself. This configuration duration indicates the duration for the terminal to perform joint channel estimation of the downlink channel. This configuration duration can also be called the Time Domain Window (TDW).

[0073] For cases where the duration of joint channel estimation is explicitly configured on network devices:

[0074] Optionally, if the capability information reported by the terminal reflects that the terminal supports joint channel estimation for the downlink channel, the network device will configure and send the configuration duration to the terminal. For example, if the terminal reports to the network device that it supports joint channel estimation for the PDSCH, the network device will indicate to the terminal the duration for joint channel estimation of the PDSCH.

[0075] Optionally, the configured duration (L) is no greater than a first duration, which is the duration during which the terminal supports joint channel estimation of the downlink channel, i.e., L≤N. The downlink channel is repeatedly transmitted, and the first duration is no greater than the duration occupied when the downlink channel is repeatedly transmitted a preset number of times, which is configured by the network device.

[0076] Optionally, the downlink channel includes at least one of the following:

[0077] ·PDSCH;

[0078] ·PDCCH.

[0079] When there are multiple downlink channels, the network device can send multiple configuration durations to the terminal. Each configuration duration corresponds to a downlink channel, and the configuration durations for each downlink channel may be the same or different. Optionally, the configuration duration sent by the network device for different downlink channels is determined based on the capability information reported by the terminal for different downlink channels.

[0080] Optionally, the configuration duration sent by the network device to the terminal is configured separately based on the downlink bandwidth part (DL BWP), that is, configured per DL BWP. For example, the network device can configure the same or different configuration durations for the downlink channels in different DL BWPs.

[0081] For cases where the terminal determines the duration of the joint channel estimation itself:

[0082] If the network device does not send the configured duration to the terminal, the terminal can determine the minimum of the first duration and the second duration as the configured duration, i.e., L = min(first duration, second duration). Here, the first duration is the duration for which the terminal supports joint channel estimation of the downlink channel. This downlink channel undergoes repeated transmissions, and the first duration is no greater than the duration occupied by the downlink channel when it undergoes repeated transmissions a preset number of times. The second duration can be called the maximum repeated transmission duration, specifically referring to the duration occupied by the downlink channel when it undergoes repeated transmissions a preset number of times, which is configured by the network device.

[0083] For example, the preset number of downlink channel retransmissions is 8, and the duration occupied by the downlink channel retransmissions 8 times is 9 time units, that is, the second duration is 9 time units. The terminal supports joint channel estimation of the downlink channel in 8 time units, that is, the first duration is 8 time units. In this case, the configuration duration determined by the terminal itself is 8 time units.

[0084] After determining the configured duration, the terminal will determine the actual time window for joint channel estimation of the downlink channels, and perform joint channel estimation of the downlink channels within this time window. Optionally, if there are multiple downlink channels, the terminal will perform joint channel estimation of the downlink channels separately in the same or different time windows.

[0085] The above descriptions, regarding the explicit configuration of joint channel estimation duration by network devices and / or the determination of joint channel estimation duration by the terminal itself, only determine the nominal duration of downlink joint channel estimation performed by the terminal. The actual duration of downlink joint channel estimation performed by the terminal depends on the specific circumstances.

[0086] For Time Division Duplex (TDD) systems:

[0087] (1) The terminal determines the time window based on the configured duration.

[0088] The terminal can determine the time window for joint channel estimation of the downlink channel based at least on the configured duration. Optionally, the terminal determines the time window for joint channel estimation of the downlink channel based on the TDD configuration and the configured duration. The TDD configuration includes the correspondence between different time units and the channels they transmit. For example, if the TDD configuration indicates that a certain time unit is used to transmit the uplink channel within the configured duration, the terminal will not perform joint channel estimation for the channel transmitted in that time unit. Instead, it will start calculating from the next downlink channel, and the calculation time length will not exceed the TDW.

[0089] (2) The terminal determines the time window itself.

[0090] The terminal can also determine the time window for joint channel estimation of the downlink channel. Optionally, the terminal determines the time window for joint channel estimation of the downlink channel according to the TDD configuration. That is, the number of consecutive time units on which the terminal actually performs joint channel estimation depends on the terminal implementation and is not standardized. The TDD configuration includes the correspondence between different time units and the channels they transmit. For example, if the TDD configuration indicates that a certain time unit is used to transmit the uplink channel, the terminal will not perform joint channel estimation for the channel transmitted in that time unit.

[0091] Optionally, the aforementioned time window includes at least one of the following information:

[0092] • Starting position;

[0093] • End position;

[0094] • Time span.

[0095] Optionally, the aforementioned start position refers to the time unit at which the terminal begins joint channel estimation, the end position refers to the time unit at which the terminal ends joint channel estimation, and the time span refers to the number of time units occupied by the terminal for joint channel estimation. Optionally, when determining the time window, the terminal may also consider the first duration during which it supports joint channel estimation of the downlink channel.

[0096] For Frequency Division Duplex (FDD) systems:

[0097] In an FDD system, the terminal performs joint channel estimation of the downlink channel within a configured time period, starting from the moment it first receives the repetitive downlink channel transmission. That is, in an FDD system, the length of the time window determined by the terminal is the configured time period, and the starting point is the moment the terminal first receives the repetitive downlink channel transmission.

[0098] Optionally, during the joint channel estimation of the downlink channel in the FDD system, the terminal will terminate the joint channel estimation of the downlink channel if at least one of the following conditions is met:

[0099] • A predefined termination event was detected;

[0100] • The repetitive transmission of the downlink channel has ended.

[0101] For example, the aforementioned termination events include collision rules causing the dropping or cancellation of downlink transmission.

[0102] In summary, the method provided in this embodiment, by having the terminal report the joint channel estimation for downlink channels in NTN, can realize downlink joint channel estimation in NTN system, thereby improving downlink channel coverage in NTN system.

[0103] Figure 4 A flowchart illustrating a capability information reporting method according to an embodiment of this application is shown. This method can be applied to network devices. The method includes:

[0104] Step 402: Receive capability information reported by the terminal. The capability information is used to indicate the capability to perform joint channel estimation for downlink channels in the NTN.

[0105] This terminal belongs to the NTN system and is capable of reporting this capability information to network devices within the NTN system. Terminals and network devices in the NTN system can be referenced... Figure 1 and 2 Examples are shown in the text.

[0106] Optionally, the capability information carries a single bit of information. This single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel. Alternatively, this single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink retransmission channel within a first duration. The downlink retransmission channel refers to the downlink channel that has been repeatedly transmitted. Optionally, the first duration refers to the duration occupied when the downlink retransmission channel is repeatedly transmitted a preset number of times, which is configured by the network device. Alternatively, the capability information carries multiple bits of information, which are used to reflect the first duration for which the terminal supports joint channel estimation for the downlink channel. This first duration is not greater than the duration occupied when the downlink channel is repeatedly transmitted a preset number of times. When the first duration is equal to the transmission duration occupied when the downlink channel is repeatedly transmitted a preset number of times, the first duration can also be called the maximum duration (N).

[0107] Optionally, the unit of the first duration includes any of the following:

[0108] • Time slot;

[0109] ·millisecond;

[0110] • The number of time slots associated with SCS.

[0111] Optionally, the above capability information is reported for downlink channels. That is, the terminal can report capability information separately for different downlink channels. The capability information reported by the terminal for different downlink channels may be the same or different. Optionally, the above capability information is reported for downlink channel transmission methods. That is, the terminal can report capability information separately for different downlink channel transmission methods, and the reported capability information may be the same or different. The above capability information can also be reported for the repetition transmission type of the downlink channel. That is, the terminal can report capability information separately for different repetition transmission types of the downlink channel, and the reported capability information may be the same or different.

[0112] After receiving the capability information reported by the terminal, the network device will configure the terminal and send a configuration duration. Optionally, the terminal can also determine the configuration duration itself. This configuration duration is used to indicate the duration for the terminal to perform joint channel estimation of the downlink channel.

[0113] Optionally, if the capability information reported by the terminal reflects that the terminal supports joint channel estimation for the downlink channel, the network device will configure and send the configuration duration to the terminal. For example, if the terminal reports to the network device that it supports joint channel estimation for the PDSCH, the network device will indicate to the terminal the duration for joint channel estimation of the PDSCH.

[0114] Optionally, the configured duration (L) is no greater than a first duration, which is the duration during which the terminal supports joint channel estimation of the downlink channel, i.e., L≤N. The downlink channel is repeatedly transmitted, and the first duration is no greater than the duration occupied when the downlink channel is repeatedly transmitted a preset number of times, which is configured by the network device.

[0115] Optionally, the downlink channel includes at least one of the following:

[0116] ·PDSCH;

[0117] ·PDCCH.

[0118] When there are multiple downlink channels, the network device can send multiple configuration durations to the terminal. Each configuration duration corresponds to a downlink channel, and the configuration durations for each downlink channel may be the same or different. Optionally, the configuration duration sent by the network device for different downlink channels is determined based on the capability information reported by the terminal for different downlink channels.

[0119] Optionally, the configuration duration sent by the network device to the terminal is based on the configuration per DL BWP. For example, the network device can configure the same or different configuration durations for downlink channels in different DL BWPs.

[0120] After receiving the above-mentioned configuration duration, the terminal will determine the actual time window for joint channel estimation of the downlink channel, and perform joint channel estimation of the downlink channel within the time window.

[0121] In summary, the method provided in this embodiment, by having the terminal report the joint channel estimation for downlink channels in NTN, can realize downlink joint channel estimation in NTN system, thereby improving downlink channel coverage in NTN system.

[0122] Figure 5 A flowchart illustrating a capability information reporting method according to an embodiment of this application is shown. This method can be applied to, for example... Figure 1 Or the system shown in Figure 2. The method includes:

[0123] Step 502: The terminal reports capability information, which indicates the ability to perform joint channel estimation for downlink channels in the NTN.

[0124] This terminal belongs to the NTN system and is capable of reporting this capability information to network devices within the NTN system. Terminals and network devices within the NTN system can be referenced... Figure 1 and 2 Examples are shown in the text.

[0125] Optionally, this capability information carries a single bit of information. This single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel. Alternatively, this single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink retransmission channel within a first duration. The downlink retransmission channel refers to the downlink channel that has been repeatedly transmitted. Optionally, the first duration refers to the duration occupied when the downlink retransmission channel is repeatedly transmitted a preset number of times, which is configured by the network device.

[0126] Alternatively, the capability information carries multiple bits of information reflecting a first duration for which the terminal supports joint channel estimation of the downlink channel. This downlink channel undergoes repeated transmissions, and the first duration is no greater than the duration of repeated transmissions of the downlink channel up to a preset number, which is configured by the network device. For example, the first duration is equal to the transmission duration of repeated transmissions of the downlink channel up to the preset number; in this case, the first duration can also be referred to as the maximum duration (N).

[0127] For example, this capability information carries 3 bits of information, the content of which is 111. These 3 bits are used to reflect that the terminal supports joint channel estimation of the downlink channel over 8 time units. Optionally, this multi-bit information can also be used to indicate the number of first durations for which the terminal supports joint channel estimation of the downlink channel. For example, 3 bits of information can be used to indicate 8 first durations for which the terminal supports joint channel estimation of the downlink channel.

[0128] Optionally, the unit of the first duration includes any of the following:

[0129] • Time slot;

[0130] ·millisecond;

[0131] • The number of time slots associated with SCS.

[0132] Optionally, the aforementioned capability information is reported for downlink channels. That is, the terminal can report capability information separately for different downlink channels. For example, the terminal reports first capability information and second capability information, where the first capability information is reported for PDSCH and the second capability information is reported for PDCCH. The capability information reported by the terminal for different downlink channels may be the same or different.

[0133] Optionally, the aforementioned capability information is reported for the downlink channel transmission mode. That is, for different downlink channel transmission modes, the terminal can report capability information separately, and the reported capability information may be the same or different. The aforementioned capability information can also be reported for the repetition type of the downlink channel. That is, for different repetition types of the downlink channel, the terminal can report capability information separately, and the reported capability information may be the same or different. For example, the terminal reports first capability information and second capability information, where the first capability information is reported for PDSCH repetition type A, and the second capability information is reported for PDSCH repetition type B. In this case, the capability information reported by the terminal for different downlink channel transmission modes may be the same or different.

[0134] Step 504: The network device sends the configuration duration to the terminal.

[0135] This configuration duration indicates the time allotted for the terminal to perform joint channel estimation on the downlink channel. This configuration duration can also be referred to as TDW. Optionally, if the capability information reported by the terminal reflects that the terminal supports joint channel estimation on the downlink channel, the network device will configure and send this configuration duration to the terminal. For example, if the terminal reports to the network device that it supports joint channel estimation on the PDSCH, in this case, the network device will indicate the duration for joint channel estimation on the PDSCH to the terminal.

[0136] Optionally, the configured duration (L) is no greater than a first duration, which is the duration during which the terminal supports joint channel estimation of the downlink channel, i.e., L≤N. The downlink channel is repeatedly transmitted, and the first duration is no greater than the duration occupied when the downlink channel is repeatedly transmitted a preset number of times, which is configured by the network device.

[0137] Optionally, the downlink channel includes at least one of the following:

[0138] ·PDSCH;

[0139] ·PDCCH.

[0140] When there are multiple downlink channels, the network device can send multiple configuration durations to the terminal. Each configuration duration corresponds to a downlink channel, and the configuration durations for each downlink channel may be the same or different. Optionally, the configuration duration sent by the network device for different downlink channels is determined based on the capability information reported by the terminal for different downlink channels.

[0141] Optionally, the configuration duration sent by the network device to the terminal is configured separately for each DL BWP, i.e., configured for each perDL BWP. For example, the network device can configure the same or different configuration durations for downlink channels in different DL BWPs.

[0142] Step 506: The terminal automatically determines the configuration duration.

[0143] If the network device does not send the configured duration to the terminal, the terminal can determine the minimum of the first duration and the second duration as the configured duration, i.e., L = min(first duration, second duration). Here, the first duration is the duration for which the terminal supports joint channel estimation of the downlink channel. This downlink channel undergoes repeated transmissions, and the first duration is no greater than the duration occupied by the downlink channel when it undergoes repeated transmissions a preset number of times. The second duration can be called the maximum repeated transmission duration, specifically referring to the duration occupied by the downlink channel when it undergoes repeated transmissions a preset number of times, which is configured by the network device.

[0144] Step 508: The terminal determines the time window for joint channel estimation of the downlink channel.

[0145] Optionally, when there are multiple downlink channels, the terminal performs joint channel estimation for the downlink channels in the same or different time windows.

[0146] The above descriptions, regarding the explicit configuration of joint channel estimation duration by network devices and / or the determination of joint channel estimation duration by the terminal itself, only determine the nominal duration of downlink joint channel estimation performed by the terminal. The actual duration of downlink joint channel estimation performed by the terminal depends on the specific circumstances.

[0147] Regarding TDD systems:

[0148] (1) The terminal determines the time window based on the configured duration.

[0149] The terminal can determine the time window for joint channel estimation of the downlink channel based at least on the configured duration. Optionally, the terminal determines the time window for joint channel estimation of the downlink channel based on the TDD configuration and the configured duration. The TDD configuration includes the correspondence between different time units and the channels they transmit. For example, if the TDD configuration indicates that a certain time unit is used to transmit the uplink channel within the configured duration, the terminal will not perform joint channel estimation for the channel transmitted in that time unit. Instead, it will start calculating from the next downlink channel, and the calculation time length will not exceed the TDW.

[0150] (2) The terminal determines the time window itself.

[0151] The terminal can also determine the time window for joint channel estimation of the downlink channel. Optionally, the terminal determines the time window for joint channel estimation of the downlink channel according to the TDD configuration. That is, the number of consecutive time units on which the terminal actually performs joint channel estimation depends on the terminal implementation and is not standardized. The TDD configuration includes the correspondence between different time units and the channels they transmit. For example, if the TDD configuration indicates that a certain time unit is used to transmit the uplink channel, the terminal will not perform joint channel estimation for the channel transmitted in that time unit.

[0152] Optionally, the aforementioned time window includes at least one of the following information:

[0153] • Starting position;

[0154] • End position;

[0155] • Time span.

[0156] Optionally, the aforementioned start position refers to the time unit at which the terminal begins joint channel estimation, the end position refers to the time unit at which the terminal ends joint channel estimation, and the time span refers to the number of time units occupied by the terminal for joint channel estimation. Optionally, when determining the time window, the terminal may also consider the first duration during which it supports joint channel estimation of the downlink channel.

[0157] For example, Figure 6 This is a schematic diagram of a TDD spectrum provided in an exemplary embodiment of this application. Figure 6 As shown, U in the spectrum represents downlink transmission, and D represents uplink transmission. In a TDD system, the configuration duration L = 4, and the downlink channel is retransmitted 8 times (in a TDD system, if a PDSCH retransmission encounters an uplink transmission, it is skipped, but the retransmission count is still recorded). The downlink channel retransmission begins in slot 1 (or a symbol within slot 1) and continues until slot 9. The time window (actual TDW) length for joint channel estimation determined by the terminal is 4. In this case, the terminal performs joint channel estimation in slots 1 and 2, skips uplink in slot 3, and then performs joint channel estimation in slots 4-7. Although slots 8 and 9 are also downlink retransmissions, continuing joint channel estimation based on slots 4-7 would exceed the time window length; therefore, the terminal only performs joint channel estimation in slots 4-7. Afterward, joint channel estimation is performed in slots 8 and 9.

[0158] Regarding FDD systems:

[0159] In an FDD system, the terminal performs joint channel estimation of the downlink channel within a configured time period, starting from the moment it first receives the retransmitted downlink channel. That is, in an FDD system, the length of the time window determined by the terminal is the configured time period, and the starting position is the moment the terminal first receives the retransmitted downlink channel. Optionally, the moment the terminal first receives the retransmitted downlink channel refers to the slot or symbol of the first retransmitted downlink channel received by the terminal.

[0160] Optionally, during the joint channel estimation of the downlink channel in the FDD system, the terminal will terminate the joint channel estimation of the downlink channel if at least one of the following conditions is met:

[0161] • A predefined termination event was detected;

[0162] • The repetitive transmission of the downlink channel has ended.

[0163] For example, the aforementioned termination events include collision rules causing the dropping or cancellation of downlink transmission.

[0164] For example, Figure 7 This is a schematic diagram of an FDD spectrum provided in an exemplary embodiment of this application. For example... Figure 7 As shown, U in the spectrum represents downlink transmission, and D represents uplink transmission. In an FDD system, the configuration duration L = 4, and the downlink channel is retransmitted 15 times. The retransmission of the downlink channel begins in slot 1 (or a symbol within slot 1) and continues until slot 15, where the terminal first receives the retransmitted downlink channel in slot 1. In this case, the terminal performs joint channel estimation in slots 0-3. Since a termination event is detected in slot 4, the terminal skips slots 4-7 without performing joint channel estimation. Then, the terminal performs joint channel estimation in slots 8 and 9. Since a termination event is detected in slot 10, the terminal skips slots 10 and 11. Next, the terminal performs joint channel estimation in slots 12-14. Since a termination event is detected in slot 15, the terminal ends the joint channel estimation.

[0165] It should be noted that steps 504 and 506 are parallel steps, meaning that when performing the method provided in this embodiment, only one of steps 504 and 506 is executed.

[0166] Optionally, in this embodiment, the duration reported by the terminal and the duration configured by the network device are configured in a specific duration manner, or in other ways. For example, they can be configured using bits and code points. The corresponding duration can be determined by combining information such as bits and code points with preset information.

[0167] In summary, the method provided in this embodiment, by having the terminal report the joint channel estimation for downlink channels in NTN, can realize downlink joint channel estimation in NTN system, thereby improving downlink channel coverage in NTN system.

[0168] It should be noted that the order of the method steps provided in the embodiments of this application can be appropriately adjusted, and the steps can also be added or removed as appropriate. Any method variations 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 protection scope of this application, and therefore will not be elaborated further.

[0169] Figure 8 A structural block diagram of a capability information reporting device provided in an exemplary embodiment of this application is shown. Figure 8 As shown, the device includes:

[0170] The transmitting module 801 is used to report capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN.

[0171] In an optional design, the capability information carries a single bit of information; the single bit of information is used to reflect whether the device supports joint channel estimation for the downlink channel; or, the single bit of information is used to reflect whether the device supports joint channel estimation for the downlink retransmission channel within a first duration.

[0172] In an optional design, the capability information carries multiple bits of information that reflect a first duration for which the device supports joint channel estimation of the downlink channel.

[0173] In an optional design, the unit of the first duration includes any of the following:

[0174] Time slot;

[0175] millisecond;

[0176] The number of time slots associated with SCS.

[0177] In an optional design, the device further includes:

[0178] The receiving module 802 is used to receive the configuration duration sent by the network device;

[0179] The configuration duration is used to indicate the duration for which the device performs joint channel estimation on the downlink channel.

[0180] In an optional design, the configuration duration is no greater than a first duration, which is the duration during which the device supports joint channel estimation of the downlink channel.

[0181] In an optional design, the downlink channel includes at least one of the following:

[0182] PDSCH;

[0183] PDCCH.

[0184] In an optional design, when there are multiple downlink channels, the configuration duration for each downlink channel is different.

[0185] In an optional design, the configuration duration is configured separately based on DL BWP.

[0186] In an optional design, the device further includes:

[0187] The determining module 803 is used to determine the minimum value between the first duration and the second duration as the configured duration;

[0188] Wherein, the first duration is the duration during which the device supports joint channel estimation of the downlink channel, and the second duration is the duration occupied by the downlink channel for a preset number of repeated transmissions.

[0189] In an optional design, the device further includes:

[0190] The determination module 803 is used to determine, at least based on the configured duration, the time window for the device to perform joint channel estimation on the downlink channel.

[0191] In an optional design, the determining module 803 is used for:

[0192] Based on the TDD configuration and the configuration duration, the time window for the device to perform joint channel estimation on the downlink channel is determined.

[0193] In an optional design, the device further includes:

[0194] The determination module 803 is used to determine the time window for the device to perform joint channel estimation of the downlink channel.

[0195] In an optional design, the determining module 803 is used for:

[0196] Based on the TDD configuration, the time window for the device to perform joint channel estimation on the downlink channel is determined.

[0197] In an optional design, the time window includes at least one of the following information:

[0198] Starting position;

[0199] End position;

[0200] Time span.

[0201] In an optional design, the device further includes:

[0202] The estimation module 804 is used in an FDD system to perform joint channel estimation on the downlink channel within the configured duration, starting from the moment when the device first receives the repeatedly transmitted downlink channel.

[0203] In an optional design, the estimation module 804 is used for:

[0204] The joint channel estimation of the downlink channel shall be terminated when at least one of the following conditions is met:

[0205] A predefined termination event was detected;

[0206] The repetitive transmission of the downlink channel has ended.

[0207] In an optional design, the capability information is reported for the downlink channel.

[0208] Figure 9 A structural block diagram of a capability information reporting device provided in an exemplary embodiment of this application is shown. Figure 9 As shown, the device includes:

[0209] The receiving module 901 is used to receive capability information reported by the terminal, the capability information being used to indicate the capability to perform joint channel estimation for downlink channels in the NTN.

[0210] In an optional design, the capability information carries a single bit of information; the single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel; or, the single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink retransmission channel within a first duration.

[0211] In an optional design, the capability information carries multiple bits of information that reflect a first duration during which the terminal supports joint channel estimation of the downlink channel.

[0212] In an optional design, the unit of the first duration includes any of the following:

[0213] Time slot;

[0214] millisecond;

[0215] The number of time slots associated with SCS.

[0216] In an optional design, the device further includes:

[0217] The sending module 902 is used to send the configuration duration to the terminal;

[0218] The configuration duration is used to indicate the duration for the terminal to perform joint channel estimation on the downlink channel.

[0219] In an optional design, the configuration duration is no greater than a first duration, where the first duration is the duration during which the terminal supports joint channel estimation of the downlink channel.

[0220] In an optional design, the downlink channel includes at least one of the following:

[0221] PDSCH;

[0222] PDCCH.

[0223] In an optional design, when there are multiple downlink channels, the configuration duration for each downlink channel is different.

[0224] In an optional design, the configuration duration is configured separately based on DL BWP.

[0225] In an optional design, the capability information is reported for the downlink channel.

[0226] It should be noted that the device provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0227] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0228] Figure 10The diagram shows a schematic of the structure of a communication device 100 provided in an exemplary embodiment of this application. The communication device 100 includes: a processor 1001, a receiver 1002, a transmitter 1003, a memory 1004, and a bus 1005.

[0229] The processor 1001 includes one or more processing cores. The processor 1001 executes various functional applications and information processing by running software programs and modules.

[0230] The receiver 1002 and the transmitter 1003 can be implemented as a communication component, which can be a communication chip.

[0231] The memory 1004 is connected to the processor 1001 via the bus 1005.

[0232] The memory 1004 can be used to store at least one instruction, and the processor 1001 can execute the at least one instruction to implement the various steps in the above method embodiments.

[0233] Furthermore, the memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic storage, flash memory, and programmable read-only memory (PROM).

[0234] When the communication device is implemented as a terminal, the processor and transceiver in the communication device involved in this application embodiment can be implemented together as a single communication chip, or the transceiver can be implemented as a separate communication chip. The transmitter in the transceiver performs the sending step performed by the terminal in any of the methods described above, the receiver in the transceiver performs the receiving step performed by the terminal in any of the methods described above, and the processor performs steps other than the sending and receiving steps, which will not be elaborated here.

[0235] When the communication device is implemented as a network device, the processor and transceiver in the communication device involved in this application embodiment can be implemented together as a single communication chip, or the transceiver can be implemented as a separate communication chip. The transmitter in the transceiver performs the sending step performed by the network device in any of the methods described above, the receiver in the transceiver performs the receiving step performed by the network device in any of the methods described above, and the processor performs steps other than the sending and receiving steps, which will not be elaborated here.

[0236] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the capability information reporting method provided in the above-described method embodiments.

[0237] In an exemplary embodiment, a chip is also provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is run on a communication device, is used to implement the capability information reporting method provided in the above-described method embodiments.

[0238] In an exemplary embodiment, a computer program product is also provided, which, when run on the processor of a computer device, causes the computer device to perform the aforementioned capability information reporting method.

[0239] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0240] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for reporting capability information, characterized in that, The method is executed by a terminal, and the method includes: Report capability information, which indicates the capability to perform joint channel estimation for downlink channels in a non-terrestrial communication network (NTN); The configuration duration is determined by receiving a configuration duration sent by the network device, or by determining the minimum value between the first duration and the second duration; wherein the configuration duration is used to indicate the duration for the terminal to perform joint channel estimation on the downlink channel, the first duration is the duration for the terminal to support joint channel estimation on the downlink channel, and the second duration is the duration occupied by the downlink channel for a preset number of repeated transmissions; In a Time Division Duplex (TDD) system, a time window for the terminal to perform joint channel estimation on the downlink channel is determined based on the TDD configuration and the configured duration, or the time window for the terminal to perform joint channel estimation on the downlink channel is determined based on the TDD configuration, wherein the TDD configuration includes the correspondence between different time units and the transmitted channels; in a Frequency Division Duplex (FDD) system, joint channel estimation on the downlink channel is performed within the configured duration, starting from the moment when the terminal first receives the repeatedly transmitted downlink channel.

2. The method according to claim 1, characterized in that, The capability information carries a single bit of information. The single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel; or, the single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink repetitive transmission channel within the first duration.

3. The method according to claim 1, characterized in that, The capability information carries multiple bits of information, which are used to reflect the first duration during which the terminal supports joint channel estimation of the downlink channel.

4. The method according to claim 3, characterized in that, The unit of the first duration includes any of the following: Time slot; millisecond; The number of time slots associated with the subcarrier spacing (SCS).

5. The method according to any one of claims 1 to 4, characterized in that, The configuration duration is no greater than the first duration.

6. The method according to any one of claims 1 to 4, characterized in that, The downlink channel includes at least one of the following: Physical Downlink Shared Channel (PDSCH); Physical Downlink Control Channel (PDCCH).

7. The method according to claim 6, characterized in that, When there are multiple downlink channels, the configuration duration for each downlink channel is different.

8. The method according to any one of claims 1 to 4, characterized in that, The configuration duration is configured separately for the downlink bandwidth DL BWP.

9. The method according to any one of claims 1 to 4, characterized in that, The time window includes at least one of the following information: Starting position; End position; Time span.

10. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The joint channel estimation of the downlink channel shall be terminated when at least one of the following conditions is met: A predefined termination event was detected; The repetitive transmission of the downlink channel has ended.

11. The method according to any one of claims 1 to 4, characterized in that, The capability information is reported for the downlink channel.

12. A method for reporting capability information, characterized in that, The method is performed by a network device, and the method includes: The terminal receives capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN. Send a configuration duration to the terminal; wherein the configuration duration is used to indicate the duration for the terminal to perform joint channel estimation on the downlink channel; In a TDD system, the TDD configuration and the configuration duration are used to determine the time window for the terminal to perform joint channel estimation on the downlink channel, or the TDD configuration is used to determine the time window for the terminal to perform joint channel estimation on the downlink channel, and the TDD configuration includes the correspondence between different time units and the transmitted channel; in an FDD system, the configuration duration is used to perform joint channel estimation on the downlink channel starting from the moment when the terminal first receives the repeatedly transmitted downlink channel.

13. The method according to claim 12, characterized in that, The capability information carries a single bit of information. The single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink channel; or, the single bit of information is used to reflect whether the terminal supports joint channel estimation for the downlink repetitive transmission channel within a first duration.

14. The method according to claim 12, characterized in that, The capability information carries multiple bits of information, which are used to reflect the first duration for which the terminal supports joint channel estimation of the downlink channel.

15. The method according to claim 14, characterized in that, The unit of the first duration includes any of the following: Time slot; millisecond; The number of time slots associated with SCS.

16. The method according to any one of claims 12 to 15, characterized in that, The configuration duration is no greater than a first duration, where the first duration is the duration during which the terminal supports joint channel estimation of the downlink channel.

17. The method according to any one of claims 12 to 15, characterized in that, The downlink channel includes at least one of the following: PDSCH; PDCCH.

18. The method according to claim 17, characterized in that, When there are multiple downlink channels, the configuration duration for each downlink channel is different.

19. The method according to any one of claims 12 to 15, characterized in that, The configuration duration is configured separately for each DL BWP.

20. The method according to any one of claims 12 to 15, characterized in that, The capability information is reported for the downlink channel.

21. A capability information reporting device, characterized in that, The device includes: A transmitting module is used to report capability information, which indicates the capability to perform joint channel estimation for downlink channels in the NTN. A receiving module is used to receive a configuration duration sent by a network device, or a determining module is used to determine the minimum value between a first duration and a second duration as the configuration duration; wherein the configuration duration is used to indicate the duration for the device to perform joint channel estimation on the downlink channel, the first duration is the duration for which the device supports joint channel estimation on the downlink channel, and the second duration is the duration occupied by the downlink channel for a preset number of repeated transmissions; The determining module is used in a TDD system to determine, based on the TDD configuration and the configuration duration, a time window for the device to perform joint channel estimation on the downlink channel, or to determine, based on the TDD configuration, a time window for the device to perform joint channel estimation on the downlink channel, wherein the TDD configuration includes the correspondence between different time units and the transmitted channels; the estimating module is used in an FDD system to perform joint channel estimation on the downlink channel within the configuration duration, starting from the moment the device first receives the repeatedly transmitted downlink channel.

22. A capability information reporting device, characterized in that, The device includes: The receiving module is used to receive capability information reported by the terminal, wherein the capability information is used to indicate the capability to perform joint channel estimation for the downlink channels in the NTN; A sending module is configured to send a configuration duration to the terminal; wherein the configuration duration is used to indicate the duration for the terminal to perform joint channel estimation on the downlink channel; In a TDD system, the TDD configuration and the configuration duration are used to determine the time window for the terminal to perform joint channel estimation on the downlink channel, or the TDD configuration is used to determine the time window for the terminal to perform joint channel estimation on the downlink channel, and the TDD configuration includes the correspondence between different time units and the transmitted channel; in an FDD system, the configuration duration is used to perform joint channel estimation on the downlink channel starting from the moment when the terminal first receives the repeatedly transmitted downlink channel.

23. A terminal, characterized in that, The terminal includes: processor; A transceiver connected to the processor; Memory for storing the executable instructions of the processor; The processor is configured to load and execute the executable instructions to implement the capability information reporting method as described in any one of claims 1 to 11.

24. A network device, characterized in that, The network device includes: processor; A transceiver connected to the processor; Memory for storing the executable instructions of the processor; The processor is configured to load and execute the executable instructions to implement the capability information reporting method as described in any one of claims 12 to 20.

25. A computer-readable storage medium, characterized in that, The readable storage medium stores executable instructions, which are loaded and executed by a processor to implement the capability information reporting method as described in any one of claims 1 to 20.

26. A chip, characterized in that, The chip includes a programmable logic circuit or a program, and the chip is used to implement the capability information reporting method as described in any one of claims 1 to 20.

Images