Methods for sending and receiving capability information, apparatus, and storage medium

Abstract

The present disclosure relates to methods for sending and receiving capability information, an apparatus, and a storage medium. The method for sending capability information comprises: a terminal sends capability information to a network device, the capability information being used for indicating whether the terminal supports a bundling capability of a downlink channel demodulation reference signal (DMRS). In the methods of the present disclosure, a terminal sends capability information so as to report to a network device whether to support a bundling capability of a downlink channel DMRS, so that the network device can perform reasonable scheduling on the basis of the terminal capability information, thereby enhancing downlink coverage performance.

Description

Method, device and storage medium for sending and receiving capability information Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method, device, and storage medium for sending and receiving capability information. Background Art

[0002] In non-terrestrial networks (NTNs), due to the long transmission distance and limited onboard power, the coverage of downlink signals or channels is challenged, and methods to enhance the coverage of downlink signal and channel transmission need to be explored.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a method, device, and storage medium for sending and receiving capability information.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for sending capability information, the method comprising:

[0006] The terminal sends capability information to the network device, where the capability information is used to indicate whether the terminal supports a bundling capability of a downlink channel demodulation reference signal (DMRS).

[0007] In a second aspect, an embodiment of the present disclosure provides a method for receiving capability information, the method comprising:

[0008] The network device receives capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports a downlink channel DMRS bundling capability.

[0009] In a third aspect, an embodiment of the present disclosure provides a terminal, including:

[0010] The transceiver module is used to send capability information to the network device, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel DMRS.

[0011] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0012] The transceiver module is used to receive capability information sent by a terminal, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel DMRS.

[0013] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

[0014] one or more processors;

[0015] The communication device is used to execute the method described in the first aspect.

[0016] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

[0017] one or more processors;

[0018] Wherein, the communication device is used to execute the method described in the second aspect.

[0019] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0020] The terminal is configured to implement the method according to the first aspect;

[0021] The network device is configured to implement the method described in the second aspect.

[0022] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0023] When the instructions are executed on a communication device, the communication device is caused to execute the method of the first aspect or the second aspect.

[0024] In the disclosed embodiment, the terminal reports to the network device whether it supports the bundling capability of the downlink channel DMRS by sending capability information, so that the network device can perform reasonable scheduling based on the terminal capability information, thereby enhancing the downlink coverage performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0026] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0027] FIG2 is an exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0028] 3a to 3d are exemplary flowcharts of a method according to an embodiment of the present disclosure;

[0029] 4a to 4c are exemplary flowcharts of a method according to an embodiment of the present disclosure;

[0030] FIG5a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

[0031] FIG5b is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

[0032] FIG6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0033] FIG6 b is a schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] Embodiments of the present disclosure provide a method, device, and storage medium for sending and receiving capability information.

[0035] In a first aspect, an embodiment of the present disclosure provides a method for sending capability information, the method comprising:

[0036] The terminal sends capability information to the network device, where the capability information is used to indicate whether the terminal supports a bundling capability of a downlink channel demodulation reference signal (DMRS bundling).

[0037] In the above embodiment, the terminal reports to the network device whether it supports the bundling capability of downlink channel DMRS by sending capability information, so that the network device can perform reasonable scheduling based on the terminal capability information to enhance downlink coverage performance.

[0038] In combination with the embodiments of the first aspect, in some embodiments, the capability information includes whether the terminal supports the bundling capability of DMRSs of each downlink channel in different downlink channels.

[0039] In the above embodiment, the terminal can report whether it supports the DMRS bundling capability on different downlink channels, so that the network device can perform scheduling based on the terminal capabilities of different downlink channels.

[0040] In combination with the embodiments of the first aspect, in some embodiments, the capability information includes: a maximum time domain window (maximum Time Domain Window, maximum TDW) length of DMRS bundling supported by the terminal.

[0041] In the above embodiment, the terminal reports the maximum TDW length, so that the network device can have a reference when performing nominal TDW configuration, thereby improving the rationality of the configuration.

[0042] In combination with the embodiment of the first aspect, in some embodiments, different downlink channels correspond to different maximum TDW lengths (sizes).

[0043] In the above embodiment, based on the maximum TDW supported by the terminal on different downlink channels, the network device can configure nominal TDWs on different downlink channels for the terminal to accommodate different capabilities of the terminal.

[0044] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0045] The terminal performs phase compensation on the downlink channel received within an actual TDW (actual TDW), wherein the actual TDW is the TDW actually applied to DMRS bundling determined by the terminal, and the terminal supports the DMRS bundling capability.

[0046] In the above embodiment, when the terminal supports the DMRS bundling capability, it can perform phase compensation on the received downlink channel at an appropriate time to maintain the phase continuity of the downlink transmission within the actual TDW, thereby improving the terminal's joint demodulation performance based on DMRS bundling.

[0047] In conjunction with the embodiments of the first aspect, in some embodiments, phase compensation includes:

[0048] Phase compensation between the terminal and the uplink time synchronization reference point, or phase compensation on the service link;

[0049] The service link is the link between the terminal and the satellite in the non-terrestrial network NTN, and the uplink time synchronization reference point is the uplink signal arrival reference point after the terminal in the NTN performs uplink timing advance (TA) adjustment.

[0050] In the above embodiment, in the NTN network, the terminal may perform phase compensation based on different links to maintain phase continuity of downlink transmission within the actual TDW.

[0051] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0052] The terminal performs joint channel estimation on the downlink channel received within the actual TDW.

[0053] In the above embodiment, when the terminal supports the DMRS bundling capability, joint channel estimation can be performed on the downlink channels within the actual TDW, thereby improving demodulation performance and enhancing communication quality.

[0054] In conjunction with the embodiments of the first aspect, in some embodiments, the actual TDW includes a plurality of consecutive time domain units, and the downlink channel includes:

[0055] A physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH) that is repeatedly transmitted over multiple consecutive time domain units; or a PDSCH that carries a transport block (TB) and is transmitted over multiple consecutive time domain units.

[0056] In the above embodiment, the transmission within the actual TDW may be repeated transmission of the downlink channel or TB transmission across time domain units. The terminal may perform joint channel estimation on the two types of transmission to improve demodulation performance and communication quality.

[0057] In combination with the embodiments of the first aspect, in some embodiments, the number of continuous time domain units in the actual TDW is determined by the terminal based on the nominal TDW length and protocol-defined events; wherein the nominal TDW length is the TDW length that can be used for DMRS bundling.

[0058] In the above embodiment, the terminal determines the number of continuous time domain units in the actual TDW based on the nominal TDW length and the event, so that the terminal can perform phase compensation or joint channel estimation on downlink channels in the corresponding number of time domain units.

[0059] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0060] The terminal receives configuration information sent by the network device, where the configuration information includes the nominal TDW length; or,

[0061] The nominal TDW length is determined by the terminal according to the maximum TDW length supported, the number of consecutive transmissions of the downlink channel and / or the number of time domain units of PDSCH transmission carrying one TB, wherein the nominal TDW is not configured.

[0062] In the above embodiment, the terminal obtains the nominal TDW length according to the configuration information sent by the network device, or if the network device does not configure the nominal TDW length, the terminal can determine the nominal TDW based on the maximum TDW supported by itself, so that the terminal can determine a reasonable actual TDW.

[0063] In combination with the embodiments of the first aspect, in some embodiments, different downlink channels correspond to different nominal TDW lengths.

[0064] In the above embodiment, the network device configures nominal TDWs for different channels, and the terminal can determine the actual TDW adapted to each channel, thereby performing joint channel estimation for downlink channels in a suitable range.

[0065] In conjunction with the embodiments of the first aspect, in some embodiments, the event includes at least one of the following:

[0066] Uplink transmission occurs in the time domain unit of downlink transmission;

[0067] The interval between two consecutive downlink transmissions exceeds the threshold;

[0068] There is downlink scheduling between two consecutive downlink transmissions;

[0069] The spatial information of downlink transmission changes.

[0070] In the above embodiment, when the above events occur, the terminal learns that there may be a break in the continuous time domain units, and thus can determine the number of the continuous time domain units.

[0071] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0072] The terminal receives indication information sent by the network device, where the indication information is used to indicate that the terminal can apply the supported DMRS bundling capability.

[0073] In the above embodiment, the terminal can learn whether the network device enables the DMRS bundling function according to the instruction information sent by the network device, so that the terminal can apply the DMRS bundling capability at an appropriate time.

[0074] In a second aspect, an embodiment of the present disclosure provides a method for receiving capability information, the method comprising:

[0075] The network device receives capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports a downlink channel DMRS bundling capability.

[0076] In the above embodiment, the network device obtains the capability information reported by the terminal, thereby knowing whether the terminal supports DMRS bundling capability for downlink channels, so that the network device can perform reasonable scheduling based on the terminal capability information to enhance downlink coverage performance.

[0077] In combination with the embodiments of the second aspect, in some embodiments, the capability information includes whether the terminal supports the bundling capability of DMRSs of each downlink channel in different downlink channels.

[0078] In combination with the embodiments of the second aspect, in some embodiments, the capability information includes: a maximum TDW length of DMRS bundling supported by the terminal.

[0079] In conjunction with the embodiments of the second aspect, in some embodiments, different downlink channels correspond to different maximum TDW lengths.

[0080] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0081] The network device sends configuration information to the terminal, where the configuration information includes a nominal TDW length.

[0082] In combination with the embodiments of the second aspect, in some embodiments, different downlink channels correspond to different nominal TDW lengths.

[0083] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0084] The network device sends indication information to the terminal, where the indication information is used to indicate that the terminal can apply the supported DMRS bundling capability.

[0085] In combination with the embodiments of the second aspect, in some embodiments, the downlink channel includes: PDSCH or PDCCH.

[0086] In a third aspect, an embodiment of the present disclosure provides a terminal, including:

[0087] The transceiver module is used to send capability information to the network device, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel DMRS.

[0088] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0089] The transceiver module is used to receive capability information sent by a terminal, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel DMRS.

[0090] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

[0091] one or more processors;

[0092] The communication device is used to execute the method described in the first aspect.

[0093] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

[0094] one or more processors;

[0095] Wherein, the communication device is used to execute the method described in the second aspect.

[0096] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0097] The terminal is configured to implement the method according to the first aspect;

[0098] The network device is configured to implement the method described in the second aspect.

[0099] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0100] When the instructions are executed on a communication device, the communication device is caused to execute the method of the first aspect or the second aspect.

[0101] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0102] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0103] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0104] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0105] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0106] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0107] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0108] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0109] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0110] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0111] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0112] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0113] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0114] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0115] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0116] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0117] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0118] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0119] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0120] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0121] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0122] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0123] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0124] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0125] As shown in FIG. 1 , a communication system 100 may be an NTN system, and the communication system 100 may include a terminal 101 , a network device 102 , and a satellite 103 .

[0126] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0127] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0128] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0129] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0130] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0131] In some embodiments, a core network device may be a single device comprising one or more network elements, or may be a plurality of devices or a group of devices, each comprising all or part of one or more network elements. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0132] In some embodiments, the satellite 103 may also be referred to as a satellite base station, and the satellite 103 may be a satellite with different orbits, altitudes, and coverage areas.

[0133] In some embodiments, in an NTN, terminal 101 can connect to network device 102 via satellite 103. Network device 102 transmits wireless resources to terminal 101 via satellite 103. For example, satellite 103 transmits signals in transparent transmission mode. The link between terminal 101 and satellite 103 is a service link, and the link between satellite 103 and network device 102 is a feeder link.

[0134] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0135] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1 , or a part of the main body thereof, but are not limited thereto.

[0136] The entities shown in Figure 1 are examples. The communication system may include all or part of the entities in Figure 1, and may also include other entities outside of Figure 1. The number and form of the entities are arbitrary. The connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

[0137] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0138] In embodiments of the present disclosure, to enhance uplink channel coverage, terminal 101 can transmit an uplink channel, such as a physical uplink shared channel (PUSCH), and network device 102 performs joint demodulation or measurement based on DMRS bundling. During this process, terminal 101 needs to ensure power consistency and phase continuity of uplink transmissions within the actual TDW. For example, in an NTN, terminal 101 performs phase pre-compensation on the uplink PUSCH in advance.

[0139] In the embodiment of the present disclosure, if DMRS bundling is performed on the downlink channel, the measurement or joint channel estimation of the downlink channel will be performed on the terminal 101 side, and the phase compensation problem needs to be solved.

[0140] FIG2 is an interactive diagram illustrating a method for sending and receiving capability information according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for sending and receiving capability information, the method comprising:

[0141] Step S2101 : Terminal 101 sends capability information to network device 102 .

[0142] Optionally, the capability information is used to indicate whether the terminal supports downlink channel DMRS bundling capability.

[0143] Optionally, the capability information may be for the NTN network, such as the terminal reporting whether it supports DMRS bundling of downlink channels in the NTN, or DMRS bundling.

[0144] Optionally, the capability information may be a UE capability report.

[0145] In some embodiments, the terminal 101 may indicate support or non-support of the DMRS bundling capability through 1-bit information in the capability information, or indicate support for the DMRS bundling capability through an enumeration value in the capability information as a set value.

[0146] In some embodiments, the capability information includes whether the terminal supports the bundling capability of DMRSs of each downlink channel in different downlink channels.

[0147] Optionally, the downlink channel includes, for example, PDCCH and PDSCH, and the capability information reported by the terminal 101 may indicate whether the terminal 101 supports DMRS bundling for PDCCH, and whether the terminal 101 supports DMRS bundling for PDSCH.

[0148] In some embodiments, the capability information includes: the maximum TDW or maximum TDW length of the DMRS bundling supported by the terminal 101 .

[0149] Optionally, the maximum TDW indicates that the terminal 101 supports joint demodulation of downlink channels within the maximum TDW length range at most during the DMRS bundling process.

[0150] Optionally, the maximum TDW length, i.e., the window size or length (size), can be expressed as the number of time domain units, where a time domain unit can be a time slot (slot), a symbol (symbol), or a millisecond (ms), etc. Taking a time slot as an example, the maximum TDW length is a number of time slots.

[0151] In one example, terminal 101 reports support for PDSCH DMRS bundling in its capability information, and supports a maximum TDW size of 16, meaning terminal 101 can perform joint demodulation on PDSCHs transmitted on at most 16 consecutive time slots. If the number exceeds 16 time slots, terminal 101 cannot perform joint demodulation.

[0152] Optionally, the nominal TDW length configured by the network device 102 needs to be less than or equal to the maximum TDW length, or the actual TDW length determined by the terminal 101 needs to be less than or equal to the maximum TDW length.

[0153] Optionally, different downlink channels correspond to different maximum TDW lengths.

[0154] In one example, for PDCCH, the maximum TDW length supported by terminal 101 is N time slots; for PDSCH, the maximum TDW length supported by terminal 101 is M time slots, where M and N are both constants. For example, in this example, M is 4 and N is 16, meaning that the maximum TDW size for PDCCH is 4 and the maximum TDW size for PDSCH is 16.

[0155] In some embodiments, network device 102 receives the capability information.

[0156] In step S2102 , the network device 102 sends instruction information to the terminal 101 .

[0157] Optionally, the indication information is used to indicate that the terminal 101 can apply the DMRS bundling capability supported by it, or in other words, the network device 102 sends the indication information to enable the DMRS bundling capability of the terminal, that is, to enable the terminal 101 to use or apply the DMRS bundling capability supported by it. Optionally, after receiving the indication information, the terminal 101 that supports the DMRS bundling capability can use the capability to perform related operations, such as executing the following steps S2104 or S2105 based on the DMRS bundling capability.

[0158] Optionally, the indication information is used to indicate that the terminal 101 can apply the DMRS bundling capability on different downlink channels or specific downlink channels, or the indication information is used to enable the terminal to apply the DMRS bundling capability on different downlink channels or specific downlink channels. The specific downlink channel can be one or any one of multiple downlink channels.

[0159] For example, network device 102 may enable DMRS bundling for different downlink channels for terminal 101. Terminal 101 may support DMRS bundling for different downlink channels, and the maximum TDW durations corresponding to different information channels may be different. After receiving the indication information, terminal 101 may use or apply the DMRS bundling capability on at least one downlink channel supported by the capability.

[0160] Alternatively, network device 102 enables DMRS bundling for a specific downlink channel for terminal 101. Terminal 101 may support DMRS bundling for multiple downlink channels, with different information channels corresponding to different maximum TDW durations. Upon receiving the indication information, terminal 101 may use or apply the DMRS bundling capability on the downlink channel that is supported and enabled by the indication information.

[0161] Optionally, the indication information may be sent via downlink control information (DCI) or radio resource control (RRC) information.

[0162] Optionally, terminal 101 receives the indication information.

[0163] Optionally, only when the network device 102 enables the DMRS bundling capability corresponding to the downlink channel, can the terminal 101 perform DMRS bundling related operations according to its own capability, such as performing joint demodulation of the downlink channel.

[0164] Optionally, if step S2102 is omitted, the DMRS bundling capability of the terminal may be enabled by default, or in other words, the terminal may use or apply the DMRS bundling capability when supporting the capability by default.

[0165] Step S2103 , the network device 102 sends configuration information to the terminal 101 .

[0166] Optionally, the configuration information includes nominal TDWs or nominal TDW lengths corresponding to different downlink channels. For example, the nominal TDWs or nominal TDW lengths corresponding to different downlink channels are different.

[0167] Optionally, the configuration information may be sent via RRC information.

[0168] Optionally, the network device 102 may determine configuration information based on the capability information.

[0169] For example, when network device 102 learns from capability information that terminal 101 supports DMRS bundling, it configures a nominal TDW for terminal 101. For another example, when network device 102 learns from capability information that terminal 101 supports DMRS bundling for PDCCH and PDSCH, network device 102 may configure two nominal TDWs for terminal 101, one nominal TDW corresponding to DMRS bundling for PDCCH, and the other nominal TDW corresponding to DMRS bundling for PDSCH.

[0170] In some embodiments, terminal 101 receives configuration information and can determine the actual TDW or actual TDW length based on the nominal TDW length and the maximum TDW length supported by the terminal 101. The actual TDW is the TDW used by terminal 101 to perform DMRS bundling-related operations, or the TDW actually used for DMRS bundling.

[0171] In some embodiments, step S2103 may be omitted, that is, the network device 102 is not configured with a nominal TDW length.

[0172] Optionally, when the network device 102 is not configured with a nominal TDW length, the nominal TDW length is determined by the terminal based on the maximum supported TDW length, the number of consecutive transmissions on the downlink channel, and / or the number of time domain units for PDSCH transmissions carrying one TB. For example, the terminal determines the nominal TDW length based on the maximum supported TDW length and the number of consecutive transmissions on the downlink channel, where the number of consecutive transmissions is configured by the network device.

[0173] In one example, if the network device does not configure the nominal TDW (pdsch-TimeDomainWindowLength), the terminal determines the nominal TDW length = min (maxDurationDMRS-Bundling, M) or the nominal TDW length = min (maximum TDW length, N*K).

[0174] Among them, for repeated PDSCH transmission, M is the duration of N*K consecutive time slots of PDSCH transmission, and K is the number of consecutive transmissions or repetitions; if there is no multiple transmission of the same PDSCH on multiple consecutive time slots (TB over multiple slots, TBOMS), N=1; otherwise, N=the number of consecutive time slots in TBOMS, such as for PDSCH transmission handled by TB on multiple time slots, N is the number of time slots determined by the transport block size (TBS), and K is the number of repetitions of the number of time slots N determined by the TBS.

[0175] Optionally, the network device 102 may configure the number of consecutive transmissions of the downlink channel (pdsch-AggregationFactor) through configuration information.

[0176] In one example, if the network device 102 enables the DMRS bundling function of the terminal 101 through indication information, but does not configure the nominal TDW, such as step S2103 is omitted, the terminal 101 can determine the nominal TDW as the smaller value of {maximum TDW, number of consecutive transmissions of the downlink channel}.

[0177] In step S2104, the terminal 101 performs phase compensation on the downlink channel received within the actual TDW.

[0178] Optionally, when the terminal 101 supports the DMRS bundling capability, step S2104 is executed.

[0179] Optionally, the downlink channel may be a PDSCH or a PDCCH.

[0180] In some embodiments, the terminal 101 performs phase compensation after receiving the downlink channel within the actual TDW, ie, phase post-compensation, to overcome the phase rotation or phase offset caused by satellite movement in the NTN.

[0181] In some embodiments, phase compensation includes:

[0182] Phase compensation between the terminal 101 and an uplink time synchronization reference point, or phase compensation on a service link; wherein the service link is the link between the terminal 101 and the satellite 103 in the NTN.

[0183] Optionally, the uplink time synchronization reference point is an offset-based alignment point between uplink transmission and downlink transmission in NTN, for example, the uplink signal arrival reference point after the terminal 101 performs uplink timing advance (TA) adjustment. The offset can be a constant N TA，offset .

[0184] Optionally, the terminal may determine a common TA To pre-compensate for the two-way transmission delay between the uplink time synchronization reference point and the satellite. common (t) can be determined by the distance between the satellite and the uplink time synchronization reference point at time t divided by the speed of light.

[0185] Optionally, the uplink time synchronization reference point may be indicated or set by the network device 102. For example, the uplink time synchronization reference point may be set at the network device 102 or other ground base station, or at the satellite 103. The time at which the uplink signal of the terminal 101, after TA adjustment, reaches the network device 102 must meet the time alignment requirement corresponding to the uplink time synchronization reference point.

[0186] Optionally, the uplink time synchronization reference point may indicate the arrival time of the uplink signal of the terminal 101, or based on which the arrival position or transmission distance of the uplink signal may be determined.

[0187] In one example, when the uplink time synchronization reference point is set at the network device 102 or the ground base station, the phase compensation between the terminal 101 and the uplink time synchronization reference point may include compensation of the service link and the feeder link.

[0188] In some embodiments, the actual TDW includes a plurality of consecutive time domain units, or the number of the plurality of consecutive time domain units is used to represent the length (size) of the actual TDW. For example, taking the time domain unit as a time slot as an example, the actual TDW may include a plurality of consecutive time slots.

[0189] Optionally, the downlink channels transmitted in the actual TDW may include:

[0190] PDSCH or PDCCH repeatedly transmitted over multiple consecutive time domain units; or

[0191] A PDSCH carrying a TB transmitted over multiple consecutive time domain units (TB over multiple slots), for example, different parts of a TB are transmitted over multiple consecutive time domain units; or

[0192] The PDSCH carrying one TB is repeatedly transmitted over multiple consecutive time domain units.

[0193] In one example, taking the time domain unit as a time slot, the actual TDW includes repeated transmissions (PDSCH repetition) of the same PDSCH in multiple consecutive time slots. The terminal 101 can perform phase compensation on the PDSCHs in the multiple consecutive time slots.

[0194] In another example, still taking the time domain unit as a time slot, the actual TDW includes multiple transmissions of the same PDSCH in multiple consecutive time slots (TB over multiple slots, TBOMS), and the terminal 101 can perform phase compensation on the PDSCHs in multiple consecutive time slots.

[0195] In some embodiments, the number of consecutive time domain units in the actual TDW is determined by terminal 101 based on a nominal TDW length and protocol-defined events. The nominal TDW length is the TDW length that can be used for DMRS bundling. Alternatively, terminal 101 determines the actual TDW based on the nominal TDW and the event. The actual TDW includes the consecutive time domain units.

[0196] Optionally, the event is used to determine the interruption position of multiple consecutive time domain units.

[0197] Optionally, the nominal TDW length may refer to the two determination methods in the aforementioned embodiments.

[0198] Optionally, the event includes at least one of the following:

[0199] Uplink transmission occurs in the time domain unit of downlink transmission;

[0200] The gap between two consecutive downlink transmissions exceeds the threshold;

[0201] There is downlink scheduling between two consecutive downlink transmissions;

[0202] The spatial information of downlink transmission changes.

[0203] For example, whether an uplink transmission occurs in a downlink transmission time slot is determined based on the time slot configuration tdd-UL-DL-configurationCommon. The threshold may be 13 symbols for a normal cyclic prefix (CP) and 11 symbols for an extended CP. Downlink scheduling between two consecutive downlink transmissions may refer to downlink scheduling other than the two downlink transmissions. An example of a change in spatial domain information is a change in Quasi Co-location (QCL) Type D.

[0204] Optionally, the occurrence of any event indicates that the continuous time domain units will be interrupted, which will affect the number of continuous time domain units in the actual TDW. For example, terminal 101 determines N consecutive time slots based on the nominal TDW. If any of the above events occurs in the i-th time slot, the number of consecutive time slots includes the time slots before the i-th time slot in the N time slots.

[0205] In step S2105 , the terminal 101 performs joint channel estimation (JCE) on the downlink channel received within the actual TDW.

[0206] Optionally, when the terminal 101 supports the DMRS bundling capability, step S2105 is executed.

[0207] Optionally, the downlink channel received by the terminal 101 within the actual TDW may include:

[0208] PDSCH or PDCCH repeatedly transmitted over multiple consecutive time domain units; or

[0209] A PDSCH carrying one TB is transmitted over multiple consecutive time domain units.

[0210] For example, referring to the description of the downlink channel in the embodiment of step S2104, the terminal 101 can perform joint channel estimation on the PDSCHs on multiple consecutive time slots in the actual TDW, such as joint demodulation and decoding, to improve the downlink channel estimation performance.

[0211] Optionally, the terminal may determine the actual TDW based on the nominal TDW and the event, i.e., determine the number of consecutive time domain units, as described in the preceding embodiment. Alternatively, the nominal TDW may refer to the two determination methods described in the preceding embodiment. In some embodiments, after performing phase post-compensation on the downlink channels of multiple consecutive time domain units in the actual TDW, the terminal 101 may perform joint channel estimation on the downlink channels. This helps improve the demodulation and decoding efficiency of the downlink channels and enhances the quality of downlink communications.

[0212] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", and "field" can be used interchangeably.

[0213] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0214] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0215] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0216] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0217] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0218] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0219] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0220] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0221] The method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2105, such as the method including step S2101.

[0222] In some embodiments, at least one of steps S2102, S2103, S2104, and S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0223] In some embodiments, steps S2102 and S2103 are executed in an interchanged order, or are executed synchronously through the same signaling.

[0224] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0225] FIG3a is a schematic diagram of a method for sending capability information according to an embodiment of the present disclosure. As shown in FIG3a, an embodiment of the present disclosure relates to a method for sending capability information, which is executed by terminal 101 and includes:

[0226] Step S3101: Send capability information.

[0227] In some embodiments, the implementation of step S3101 can refer to the optional implementation of step S2101 and will not be repeated here.

[0228] Optionally, the terminal 101 may send the capability information to the network device 102 or other entities.

[0229] Step S3102, obtain instruction information.

[0230] In some embodiments, the implementation of step S3102 can refer to the optional implementation of step S2102 and will not be repeated here.

[0231] Optionally, the terminal 101 may obtain the indication information from the network device 102 or other entities.

[0232] Step S3103, obtain configuration information.

[0233] In some embodiments, the implementation of step S3103 can refer to the optional implementation of step S2103 and will not be repeated here.

[0234] Optionally, the terminal 101 may obtain the configuration information from the network device 102 or other entities.

[0235] Step S3104: performing phase compensation on the downlink channel received within the actual TDW.

[0236] In some embodiments, the implementation of step S3104 can refer to the optional implementation of step S2104 and will not be repeated here.

[0237] Step S3105: perform joint channel estimation on the downlink channels received within the actual TDW.

[0238] In some embodiments, the implementation of step S3105 can refer to the optional implementation of step S2105 and will not be repeated here.

[0239] The method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3105, such as the method including step S3101.

[0240] In some embodiments, at least one of steps S3102, S3103, S3104, and S3105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0241] In some embodiments, steps S3102 and S3103 are executed in an interchanged order, or are executed synchronously through the same signaling.

[0242] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 a .

[0243] FIG3b is a schematic diagram of a method for sending capability information according to an embodiment of the present disclosure. As shown in FIG3b, an embodiment of the present disclosure relates to a method for sending capability information, which is executed by terminal 101 and includes:

[0244] Step S3201: Send capability information.

[0245] In some embodiments, the implementation of step S3201 can refer to the optional implementation of step S2101 and will not be repeated here.

[0246] Step S3202, obtain configuration information.

[0247] In some embodiments, the implementation of step S3202 can refer to the optional implementation of step S2103 and will not be repeated here.

[0248] Step S3203: Perform phase compensation on the downlink channel received within the actual TDW.

[0249] In some embodiments, the implementation of step S3203 can refer to the optional implementation of step S2104 and will not be repeated here.

[0250] Step S3204: perform joint channel estimation on the downlink channels received within the actual TDW.

[0251] In some embodiments, the implementation of step S3204 can refer to the optional implementation of step S2105 and will not be repeated here.

[0252] The method involved in the embodiment of the present disclosure may include at least one of steps S3201 to S3204, such as the method including step S3201.

[0253] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 b .

[0254] FIG3c is a schematic diagram of a method for sending capability information according to an embodiment of the present disclosure. As shown in FIG3c, an embodiment of the present disclosure relates to a method for sending capability information, which is executed by terminal 101 and includes:

[0255] Step S3301: Send capability information.

[0256] In some embodiments, the implementation of step S3301 can refer to the optional implementation of step S2101 and will not be repeated here.

[0257] Step S3302: Perform phase compensation on the downlink channel received within the actual TDW.

[0258] In some embodiments, the implementation of step S3302 can refer to the optional implementation of step S2104 and will not be repeated here.

[0259] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3c.

[0260] FIG3 d is a schematic diagram of a method for sending capability information according to an embodiment of the present disclosure. As shown in FIG3 d , an embodiment of the present disclosure relates to a method for sending capability information, which is executed by terminal 101 and includes:

[0261] Step S3401: Send capability information.

[0262] In some embodiments, the implementation of step S3401 can refer to the optional implementation of step S2101 and will not be repeated here.

[0263] Optionally, the capability information is used to indicate whether the terminal supports the bundling capability of downlink channel DMRS.

[0264] In some embodiments, the capability information includes whether the terminal supports the bundling capability of DMRSs of each downlink channel in different downlink channels.

[0265] In some embodiments, the capability information includes: a maximum time domain window TDW length of DMRS bundling supported by the terminal.

[0266] In some embodiments, different downlink channels correspond to different maximum TDW lengths.

[0267] In some embodiments, the method further comprises:

[0268] The terminal performs phase compensation on the downlink channel received within the actual TDW, wherein the actual TDW is the TDW actually applied to the DMRS bundling determined by the terminal, and the terminal supports the DMRS bundling capability.

[0269] Optionally, phase compensation includes:

[0270] Phase compensation between the terminal and the uplink time synchronization reference point, or phase compensation on the service link;

[0271] The service link is the link between the terminal and the satellite in the NTN, and the uplink time synchronization reference point is the offset-based alignment of the uplink transmission and the downlink transmission in the NTN.

[0272] In some embodiments, the method further comprises:

[0273] The terminal performs joint channel estimation on the downlink channel received within the actual TDW, and the terminal supports the DMRS bundling capability.

[0274] Optionally, the actual TDW includes a plurality of consecutive time domain units, and the downlink channel of the transmission includes:

[0275] A physical downlink shared channel PDSCH or a physical downlink control channel PDCCH that is repeatedly transmitted over multiple consecutive time domain units; or a PDSCH that carries one transport block TB and is transmitted over multiple consecutive time domain units.

[0276] Optionally, the number of consecutive time domain units in the actual TDW is determined by the terminal based on the nominal TDW length and the event defined by the protocol; wherein the nominal TDW length is the TDW length that can be used for DMRS bundling, and the event is used to determine the interruption position of the consecutive time domain units.

[0277] In some embodiments, the method further comprises:

[0278] The terminal receives configuration information sent by the network device, where the configuration information includes the nominal TDW length; or,

[0279] The nominal TDW length is determined by the terminal according to the maximum supported TDW length, the number of consecutive transmissions of the downlink channel and / or the number of time domain units of PDSCH transmission carrying one TB, wherein the network device is not configured with the nominal TDW.

[0280] Optionally, different downlink channels correspond to different nominal TDW lengths.

[0281] Optionally, the event includes at least one of the following:

[0282] Uplink transmission occurs in the time domain unit of downlink transmission;

[0283] The interval between two consecutive downlink transmissions exceeds the threshold;

[0284] There is downlink scheduling between two consecutive downlink transmissions;

[0285] The spatial information of downlink transmission changes.

[0286] In some embodiments, the method further comprises:

[0287] The terminal receives indication information sent by the network device, where the indication information is used to indicate that the terminal can apply the supported DMRS bundling capability.

[0288] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 d .

[0289] FIG4a is a schematic diagram of a method for receiving capability information according to an embodiment of the present disclosure. As shown in FIG4a, an embodiment of the present disclosure relates to a method for receiving capability information, which is executed by a network device 102 and includes:

[0290] Step S4101, obtaining capability information.

[0291] In some embodiments, the implementation of step S4101 can refer to the optional implementation of step S2101 and will not be repeated here.

[0292] Optionally, the network device 102 may obtain the capability information from the terminal 101 or other entities.

[0293] Step S4102, sending instruction information.

[0294] In some embodiments, the implementation of step S4102 can refer to the optional implementation of step S2102 and will not be repeated here.

[0295] Optionally, the network device 102 may send the indication information to the terminal 101 or other entities.

[0296] Step S4103: Send configuration information.

[0297] In some embodiments, the implementation of step S4103 can refer to the optional implementation of step S2104 and will not be repeated here.

[0298] Optionally, the network device 102 may send the configuration information to the terminal 101 or other entities.

[0299] The method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4103, such as the method including step S4101.

[0300] In some embodiments, at least one of steps S4102 and S4103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0301] In some embodiments, steps S4102 and S4103 are executed in an interchanged order, or are executed synchronously through the same signaling.

[0302] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 a .

[0303] FIG4 b is a schematic diagram of a method for receiving capability information according to an embodiment of the present disclosure. As shown in FIG4 b , an embodiment of the present disclosure relates to a method for receiving capability information, which is executed by a network device 102 and includes:

[0304] Step S4201, obtaining capability information.

[0305] In some embodiments, the implementation of step S4201 can refer to the optional implementation of step S2101 and will not be repeated here.

[0306] Step S4202, sending configuration information.

[0307] In some embodiments, the implementation of step S4202 can refer to the optional implementation of step S2103 and will not be repeated here.

[0308] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 b .

[0309] FIG4c is a schematic diagram of a method for receiving capability information according to an embodiment of the present disclosure. As shown in FIG4c, an embodiment of the present disclosure relates to a method for receiving capability information, which is executed by a network device 102 and includes:

[0310] Step S4301, obtaining capability information.

[0311] In some embodiments, the implementation of step S4301 can refer to the optional implementation of step S2101 and will not be repeated here.

[0312] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4c.

[0313] Optionally, the capability information is used to indicate whether the terminal supports the bundling capability of downlink channel DMRS.

[0314] In some embodiments, the capability information includes whether the terminal supports the bundling capability of DMRSs of each downlink channel in different downlink channels.

[0315] In some embodiments, the capability information includes: a maximum TDW length of DMRS bundling supported by the terminal.

[0316] In some embodiments, different downlink channels correspond to different maximum TDW lengths.

[0317] In some embodiments, the method further comprises:

[0318] The network device sends indication information to the terminal, where the indication information is used to indicate that the terminal can apply the supported DMRS bundling capability.

[0319] In some embodiments, the method further comprises:

[0320] The network device sends configuration information to the terminal, where the configuration information includes the nominal TDW length.

[0321] Optionally, different downlink channels correspond to different nominal TDW lengths.

[0322] In some embodiments, the downlink channel includes: PDSCH or PDCCH.

[0323] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4c.

[0324] In the embodiments of this disclosure, DMRS bundling is performed on the downlink channel. The UE can perform joint channel estimation on the DMRS in consecutive time slots, thereby improving decoding performance. DMRS bundling requires maintaining transmit power consistency and phase continuity within the actual TDW. In this embodiment, the downlink channel is measured on the UE side, and a method for compensating the phase is provided based on this. To facilitate understanding of the embodiments of this disclosure, some examples are listed below:

[0325] Example 1:

[0326] The UE reports whether it supports DMRS bundling for downlink channels in NTN.

[0327] Optionally, if supported, the UE may perform joint channel estimation based on a group of downlink channel transmissions.

[0328] Example 2:

[0329] Based on Example 1, a group of downlink transmissions may be PDSCHs or PDCCHs transmitted on consecutive time slots, for example:

[0330] Example 1: Repeated transmission of the same PDSCH in multiple consecutive time slots, i.e., PDSCH repetition;

[0331] Embodiment 2: Multiple transmissions of the same PDSCH over multiple consecutive time slots, ie, TB over multiple slots.

[0332] Example 3:

[0333] The UE reports its capabilities for different DL channels, where the capability report includes the length of the bundling, that is, the TDW size supported by the UE for joint channel demodulation.

[0334] Optionally, the UE supports DMRS bundling for PDSCH, and maximum TDW size = 16, which means that the UE can perform joint demodulation on PDSCHs transmitted on a maximum of 16 consecutive slots. If the number of slots exceeds 16, the UE will not be able to perform joint demodulation.

[0335] Optionally, the length may be different for different channels, for example, PDSCH-maximum TDW size=16; PDCCH-maximum TDW size=4.

[0336] Example 4:

[0337] The above UE capabilities are reported in the UE capability report.

[0338] Example 5:

[0339] If the UE reports support for DL ​​DMRS bundling, it means that the UE has the capability to perform phase post-compensation on downlink channels within the actual TDW, such as PDSCH and PDCCH.

[0340] Optionally, the phase post-compensation is that the UE compensates for the phase rotation between the UE and the uplink time synchronization point;

[0341] Optionally, the phase post-compensation is that the UE compensates for the phase rotation between the UE and the satellite.

[0342] Example 6:

[0343] The base station configures the nominal TDW size for different downlink channels for the UE.

[0344] Example 7:

[0345] The base station enables DMRS bundling for different downlink channels for the UE.

[0346] Example 8:

[0347] If the base station does not configure the nominal TDW size for the UE when DMRS bundling is enabled for the channel, the unit of the continuous time slots used by the UE to transmit the duration of PDSCH repetitions by default is the smaller value of {the TDW value in the UE capability report and the number of consecutive transmissions of the downlink channel configured by the base station}.

[0348] Based on the above example, in a specific instance, after accessing the network, the UE reports support for PDSCH DMRS bundling, or PDSCH joint channel estimation, in its UE capability. In this example, the base station configures a PDSCH TDW size of 8 for the UE, i.e., nominal TDW = 8. The base station also configures a set of semi-persistent scheduling for the UE, with a retransmission count of pdsch-aggregation factor = 8.

[0349] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0350] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0351] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0352] Figure 5a is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in Figure 5a, terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. In some embodiments, transceiver module 5101 is configured to send capability information to a network device, indicating whether the terminal supports downlink demodulation reference signal (DMRS) bundling.

[0353] Optionally, the transceiver module 5101 is configured to execute at least one of the communication steps of sending and / or receiving performed by the terminal 101 in any of the above methods, which are not described in detail here. Optionally, the processing module 5102 is configured to execute at least one of the other steps performed by the terminal 101 in any of the above methods, which are not described in detail here.

[0354] Figure 5b is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in Figure 5b, network device 5200 may include at least one of a transceiver module 5201 and a processing module 5202. In some embodiments, transceiver module 5201 is configured to receive capability information sent by the terminal, indicating whether the terminal supports downlink channel DMRS bundling.

[0355] Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps of sending and / or receiving performed by the network device 102 in any of the above methods, which are not described in detail here. Optionally, the processing module 5202 is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

[0356] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0357] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0358] Figure 6a is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0359] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0360] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 6101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0361] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and may be configured to receive data from the memories 6103 or other devices, or to send data to the memories 6103 or other devices. For example, the interface circuits 6104 may read data stored in the memories 6103 and send the data to the processor 6101.

[0362] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0363] FIG6b is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6b , but the present disclosure is not limited thereto.

[0364] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0365] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.

[0366] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0367] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0368] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0369] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0370] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods. Industrial Applicability

[0371] The terminal reports to the network device whether it supports the bundling capability of the downlink channel DMRS by sending capability information, so that the network device can perform reasonable scheduling based on the terminal capability information, thereby enhancing the downlink coverage performance.

Claims

1. A method for sending capability information, the method comprising: A terminal sends capability information to a network device, where the capability information is used to indicate whether the terminal supports the bundling capability of a downlink channel demodulation reference signal (DMRS).

2. The method according to claim 1, wherein the capability information includes whether the terminal supports the bundling capability of the DMRS for each downlink channel in different downlink channels.

3. The method according to claim 1 or 2, wherein the capability information includes: the maximum time domain window (TDW) length that the terminal supports for bundling the DMRS.

4. The method according to claim 3, wherein The maximum TDW lengths corresponding to different downlink channels are different.

5. The method according to any one of claims 1 to 4, wherein The method further comprises: The terminal performs phase compensation on the downlink channel received within the actual TDW, where the actual TDW is the TDW actually applied by the terminal for bundling the DMRS, and the terminal supports the bundling capability of the DMRS.

6. The method according to claim 5, wherein, The phase compensation includes: phase compensation between the terminal and the uplink time synchronization reference point, or phase compensation on the service link; wherein the service link is the link between the terminal and the satellite in a non-terrestrial network (NTN), and the uplink time synchronization reference point is the alignment point based on offset for uplink transmission and downlink transmission in the NTN.

7. The method according to claim 5, wherein, The method further comprises: The terminal performs joint channel estimation on the downlink channel received within the actual TDW.

8. The method according to claim 7, wherein, The actual TDW includes a continuous plurality of time domain units, and the downlink channel includes: A physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH) repeatedly transmitted on the continuous plurality of time domain units; or, A PDSCH carrying one transport block (TB) transmitted on the continuous plurality of time domain units.

9. The method according to claim 8, wherein the number of continuous time domain units in the actual TDW is determined by the terminal according to the nominal TDW length and events defined by the protocol, and the nominal TDW length is the TDW length that can be used for bundling the DMRS.

10. The method according to claim 9, wherein, The method further comprises: The terminal receives configuration information sent by the network device, where the configuration information includes the nominal TDW length; or, The nominal TDW length is determined by the terminal according to the supported maximum TDW length, the continuous transmission times of the downlink channel, and / or the number of time domain units for transmitting the PDSCH carrying one TB, where the nominal TDW length is not configured.

11. The method according to claim 10, wherein, The nominal TDW lengths corresponding to different downlink channels are different.

12. The method according to claim 9, wherein, The events include at least one of the following: An uplink transmission appears in the time domain unit of the downlink transmission; The interval between two consecutive downlink transmissions exceeds a threshold; There is a downlink scheduling between two consecutive downlink transmissions; The spatial domain information of the downlink transmission changes.

13. The method according to any one of claims 1 to 10, wherein, The method further comprises: The terminal receives indication information sent by the network device, where the indication information is used to indicate that the terminal can apply the supported bundling capability of the DMRS.

14. A method for receiving capability information, the method comprising: A network device receives capability information sent by a terminal, where the capability information is used to indicate whether the terminal supports the bundling capability of a downlink channel DMRS.

15. The method according to claim 14, wherein the capability information includes the bundling capability of the DMRS of each downlink channel in different downlink channels supported by the terminal.

16. The method according to claim 14 or 15, wherein the capability information includes: the maximum TDW length supported by the terminal for bundling the DMRS.

17. The method according to claim 16, wherein the maximum TDW lengths corresponding to different downlink channels are different.

18. The method according to any one of claims 14 to 17, wherein The method further includes: the network device sends configuration information to the terminal, and the configuration information includes a nominal TDW length.

19. The method according to claim 18, wherein the nominal TDW lengths corresponding to different downlink channels are different.

20. The method according to any one of claims 14 to 17, wherein The method further includes: the network device sends indication information to the terminal, and the indication information is used to indicate that the terminal can apply the bundling capability of the DMRS supported by the terminal.

21. The method according to any one of claims 14 to 20, wherein, The downlink channel includes: PDSCH or PDCCH.

22. A terminal, comprising: a transceiver module, configured to send capability information to a network device, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel demodulation reference signal DMRS.

23. A network device, comprising: a transceiver module, configured to receive the capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports the bundling capability of the downlink channel DMRS.

24. A communication device, comprising: one or more processors; wherein the communication device is configured to execute the method according to any one of claims 1 to 13.

25. A communication device, comprising: one or more processors; wherein the communication device is configured to execute the method according to any one of claims 14 to 21.

26. A communication system, comprising a terminal and a network device, wherein the terminal is configured to implement the method according to any one of claims 1 to 13; the network device is configured to implement the method according to any one of claims 14 to 21.

27. A storage medium, storing instructions, wherein when the instructions run on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 13 or any one of claims 14 to 21.

Images