Apparatus and method for communication

Abstract

Embodiments of the present disclosure provide a solution for communication. In one solution, a terminal device sends first information to a network device, the first information indicating at least one of: an antenna switching capability of the terminal device, or a first parameter associated with a time domain window (TDW) determination for demodulation reference signal (DMRS) binding. The terminal device determines the TDW for DMRS binding based on at least one of the following: second information indicating one or more TDWs from the network device, the first information or a second parameter corresponding to the first information.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein relate generally to the field of communication technology, and more specifically to apparatus and methods for demodulation reference signal (DMRS) bonding. Background Technology

[0002] Non-terrestrial networks (NTNs) refer to networks or segments of networks that utilize radio frequency (RF) resources mounted on satellite or unmanned aircraft systems (UAS). NTNs provide ubiquitous and resilient wireless services that extend beyond the coverage of terrestrial networks. The 3rd Generation Partnership Project (3GPP) has been working on NTN standardization since the fifth generation (5G) communication systems. It is anticipated that NTNs will be fully integrated with terrestrial networks (TNs) in the sixth generation (6G). Coverage enhancements in Rep. 18 (Rel-18) are a major topic in enhancing new radio (NR) NTNs. Enhancing the DMRS binding process for the physical uplink shared channel (PUSCH) in Rep. 17 (Rel-17) is one aspect that needs to be addressed, taking into account NTN characteristics (e.g., time-frequency precompensation). Summary of the Invention

[0003] In a first aspect, a terminal device is provided, the terminal device comprising: a processor configured to cause the terminal device to: send first information to a network device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first parameter associated with a time domain window (TDW) for demodulation reference signal (DMRS) binding; and determine a TDW for DMRS binding based on at least one of: second information from the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information.

[0004] In a second aspect, a network device is provided, the network device comprising: a processor configured such that the network device: receives first information from a terminal device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and determines a TDW for DMRS binding based on at least one of: second information indicating one or more TDWs sent to the network device, the first information, or a second parameter corresponding to the first information.

[0005] In a third aspect, a communication method performed by a terminal device is provided. The method includes: sending first information to a network device, the first information indicating at least one of the following: the terminal device's antenna switching capability, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; determining the TDW for DMRS binding based on at least one of the following: second information from the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information.

[0006] In a fourth aspect, a communication method performed by a network device is provided. The method includes: receiving first information from a terminal device, the first information indicating at least one of the following: the terminal device's antenna switching capability, or a first parameter associated with determining a time-domain window (TDW) for demodulation reference signal (DMRS) binding; determining the TDW for DMRS binding based on at least one of the following: second information indicating one or more TDWs sent to the network device, the first information, or a second parameter corresponding to the first information.

[0007] In a fifth aspect, a computer-readable medium is provided that stores instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the third or fourth aspect.

[0008] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other objects, features and advantages of this disclosure will become more apparent from a more detailed description of some exemplary embodiments thereof in the accompanying drawings, wherein: Figure 1 An example communication environment in which an example implementation of the present disclosure can be carried out is illustrated; Figure 2A and Figure 2B Schematic diagrams illustrating non-terrestrial network scenarios with different payload types according to some embodiments of this disclosure are shown; Figure 3 Signaling flows for example communication processes according to some embodiments of this disclosure are illustrated; Figure 4A and Figure 4B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 5A and Figure 5B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 6A and Figure 6B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 7A and Figure 7B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 8A and Figure 8B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 9A and Figure 9B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 10 Signaling flows for example communication processes according to some embodiments of this disclosure are illustrated; Figure 11A and Figure 11B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 12 Example communication procedures are illustrated for explicit cases according to some embodiments of this disclosure; Figure 13A and Figure 13B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 14A and Figure 14B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 15A and Figure 15B Example communication procedures for explicit and implicit cases according to some embodiments of this disclosure are illustrated respectively; Figure 16 Flowcharts illustrating methods implemented at a terminal device according to some example embodiments of this disclosure are shown; Figure 17Flowcharts illustrating methods implemented at a network device according to some example embodiments of this disclosure are shown; Figure 18 Flowcharts illustrating methods implemented at a terminal device according to some example embodiments of this disclosure are shown; Figure 19 Flowcharts illustrating methods implemented at a network device according to some example embodiments of this disclosure are shown; Figure 20 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is shown.

[0010] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0011] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0012] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0013] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE); personal computers; desktop computers; mobile phones; cellular phones; smartphones; personal digital assistants (PDAs); portable computers; tablets; wearable devices; Internet of Things (IoT) devices; Ultra-reliable and Low-Latency Communication (URLLC) devices; Internet of Everything (IoE) devices; machine-type communication (MTC) devices; devices on vehicles for V2X communication, where X refers to pedestrians, vehicles, or infrastructure / networks; devices for Integrated Access and Backhaul (IAB); spacecraft or aerospace vehicles in non-terrestrial networks (NTNs), including satellites and high-altitude platforms (HAPs) covering Unmanned Aircraft Systems (UAS); and different types of reality (such as Augmented Reality (AR), Mixed Reality (MR)). Extended Reality (XR) devices, including those for Virtual Reality (VR) and Virtual Reality (VR); unmanned aerial vehicles (UAVs), often referred to as drones (aircraft without human pilots); devices on high-speed trains (HSTs); or image capture devices such as digital cameras and sensors; gaming devices; music storage and playback equipment; or internet devices enabling wireless or wired internet access and browsing. "Terminal devices" may also have "multicast / broadcast" capabilities to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, wireless software delivery, group communication, and IoT applications. "Terminal devices" may also incorporate one or more Subscriber Identity Modules (SIMs), a situation known as multi-SIM. The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0014] The term "network device" refers to a device that provides or hosts a cell or coverage area for terminal devices to communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), transmission reception points (TRPs), remote radio units (RRUs), radioheads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (such as femtonodes and piconodes), reconfigurable intelligent surfaces (RISs), etc.

[0015] Terminal devices or network devices may have artificial intelligence (AI) or machine learning capabilities. Terminal devices or network devices typically include models that have been trained on specific functions based on a large amount of collected data and can be used to predict some information.

[0016] Terminal or network devices can operate within several frequency ranges, such as FR1 (e.g., 450MHz to 6000MHz), FR2 (e.g., 24.25GHz to 52.6GHz), bands greater than 100GHz, and terahertz (THz). Terminal or network devices can also operate on licensed / unlicensed / shared spectrum. In Multi-Radio Dual Connectivity (MR-DC) applications, terminal devices may connect to more than one network device. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.

[0017] The embodiments of this disclosure can be executed in test equipment (e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal equipment, test network equipment, channel simulator). In some embodiments, the terminal equipment can be connected to a first network equipment and a second network equipment. One of the first network equipment and the second network equipment can be a master node, and the other can be a slave node. The first network equipment and the second network equipment can use different Radio Access Technologies (RATs). In some embodiments, the first network equipment can be a first RAT device, and the second network equipment can be a second RAT device. In some embodiments, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs can be sent to the terminal equipment from at least one of the first network equipment or the second network equipment. In some embodiments, information can be sent from the first network equipment to the terminal equipment, and the same or different information can be sent from the second network equipment directly or via the first network equipment to the terminal equipment. In some embodiments, information configured by the second network equipment and related to the configuration of the terminal equipment can be sent from the second network equipment via the first network equipment. Information configured by the second network device and related to the reconfiguration of the terminal device can be sent directly from the second network device or via the first network device to the terminal device.

[0018] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one implementation” and “implementation” should be understood as “at least one implementation.” The term “another implementation” should be understood as “at least one other implementation.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions are given below.

[0019] In some examples, values, programs, or devices are described as “best,” “lowest,” “highest,” “smallest,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many alternative functionalities used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0020] As used herein, the terms “resource,” “transmission resource,” “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, or any other resource used to implement communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0021] As used in this article, it is represented as " interSlotFreqHopInterSlotBundlingPUSCH-r17 The parameter indicates whether the UE supports enhanced inter-slot frequency hopping with inter-slot binding for PUSCH.

[0022] In some implementations, the parameter "the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network" can be used, and in some implementations, this parameter can be expressed as " maxDurationDMRS-Bundling The use of the term "for general networks" may imply that this parameter may not take into account NTN characteristics. In some implementations, this parameter may also be referred to as "second maximum duration".

[0023] As " maxDurationDMRS-Bundling Example of "", parameter " maxDurationDMRS-Bundling- r17 "Indicates whether the UE supports the ability of the UE to maintain power consistency and phase continuity to support the maximum duration of DMRS bonding for the Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH).

[0024] As used in this article, it is represented as " interSlotAntennaSwichingPUSCH-r18 The parameter indicates whether the UE supports enhanced inter-slot antenna switching with inter-slot bonding for PUSCH.

[0025] In some implementations, the parameter "duration of continuous uplink transmission" can be used, also denoted as "M". For example, parameter M can refer to N. The duration of consecutive time slots in K PUSCH transmissions. For PUSCH transmissions of PUSCH repetition type A, N=1 and K is the number of PUSCH repetitions. For PUSCH transmissions of PUSCH repetition type B, N=1 and K is the nominal number of repetitions. For PUSCH transmissions processed over multiple transport blocks (TBs) on multiple time slots, N is the number of time slots used to determine the TB size (TBS), and K is the number of repetitions used to determine the number of time slots N for TBS.

[0026] As used in this article, the parameter " pusch-TimeDomainWindowLength "This can be used to configure the nominal TDW length in multiple consecutive time slots for a DMRS bond used for PUSCH. This value must not exceed the maximum duration of a DMRS bond used for PUSCH as described above."

[0027] Example Environment Figure 1 A schematic diagram illustrating an example communication environment 100 in which an example embodiment of the present disclosure may be implemented is shown. In communication environment 100, multiple communication devices (including terminal device 110 and network device 120) can communicate with each other. Figure 1 In the example, terminal device 110 can be a UE, and network device 120 can be a base station serving the UE.

[0028] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the example embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be deployed in communication environment 100.

[0029] In the following examples, for illustrative purposes, some example implementations are described in which terminal device 110 operates as a UE and network device 120 operates as a gNB. However, in some example implementations, the operations described in connection with the terminal device may be implemented at the network device or other devices, and the operations described in connection with the network device may be implemented at the terminal device or other devices.

[0030] The link from network device 120 to terminal device 110 is called a downlink (DL), and the link from terminal device 110 to network device 120 is called an uplink (UL). In the DL, network device 120 is the transmitting (TX) device (or sender), and terminal device 110 is the receiving (RX) device (or receiver). In the UL, terminal device 110 is the TX device (or sender), and network device 120 is the RX device (or receiver). During communication, terminal device 110 can perform uplink transmissions with network device 120, such as PUSCH transmissions. The timing of uplink transmissions may require DMRS binding.

[0031] The communications in communication environment 100 may conform to any suitable standard, including but not limited to Global System for Mobile Communication (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. The embodiments of this disclosure may be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced Networks, or sixth-generation (6G) networks.

[0032] Communication environment 100 can be implemented in NTN. NTN can have different payload types. Figure 2A and Figure 2B A schematic diagram illustrating NTN scenarios with different payload types is provided. Figure 2A The NTN is based on a transparent payload, and Figure 2B The NTN is based on regenerated payload.

[0033] In some example implementations, the satellite or UAS platform can implement transparent or regenerative (with onboard (or airborne) processing) payloads. The satellite or UAS platform can generate beams (e.g., typically several beams) over a given service area defined by its field of view 260. The coverage area 250 of the beams is typically elliptical. The field of view of the satellite or UAS platform depends on the onboard (or airborne) antenna pattern and the minimum elevation angle.

[0034] like Figure 2AAs shown, in the transparent payload scenario, UE 210 can communicate with satellite 220 or the UAS platform via a serving link, and satellite 220 or the UAS platform can communicate with gateway 230 connected to data network 240 via a feed link. In this scenario, satellite 220 or the UAS platform can perform RF filtering, frequency conversion, and amplification, so the waveform signal repeated by the payload may remain unchanged. Based on the transparent payload, UE 210 can connect to data network 240. The round-trip time (RTT) in this case reflects the time it takes for data to travel from UE 210 to the gNB (which is on the ground) via satellite 220 or the UAS platform.

[0035] like Figure 2B As shown, in the regenerated payload scenario, UE 210 can communicate with satellite 220-1 or the UAS platform via a serving link. Satellite 220-1 or the UAS platform can communicate with satellite 220-2 or the UAS platform via an inter-switch link (ISL), and satellite 220-2 or the UAS platform can communicate with gateway 230 connected to data network 240 via a feed link. If the ISL is unavailable, satellite 220 or the UAS platform can communicate with gateway 230 connected to data network 240 via a feed link. In this scenario, satellites 220-1 and 220-2 (or the UAS platform) can perform RF filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and decoding / modulation, which is essentially equivalent to having all or part of the functions of a base station (e.g., gNB) on the satellite or UAS platform. Based on the regenerated payload, UE 210 can connect to data network 240. In this context, RTT reflects the time it takes for data to be sent from UE 210 to gNB (which is on a satellite or UAS platform).

[0036] As mentioned above, PUSCH transmission may require DMRS binding. Table 1 lists some example feature groups (FG).

[0037] Table 1: Example feature groups related to DMRS binding

[0038]

[0039]

[0040] In these example FGs, FG 30-4, "Maximum Duration for DM-RS Bonding," may also be referred to as FG 30-4 below. FG 30-4 corresponds to the parameter "Maximum Duration for which the terminal device can maintain power consistency and phase continuity for a general network," as described above. FG 30-4 defines UE characteristics for a general network, i.e., without considering NTN characteristics.

[0041] The FG “NTN DMRS Binding Enhancement for PUSCH” with index 44-2 may also be referred to as FG 44-2 below. FG 44-2 defines the UE features that support DMRS binding enhancement for PUSCH in the case of NTN.

[0042] In some solutions, for NTN-specific PUSCH DMRS bindings, Clause 6.1.7 of TS 38.214 can be reused for nominal TDW determination, except for aspects related to UE capabilities and auxiliary information (if required). For example, if the parameter " PUSCH-TimeDomainWindowLength ", then TDW is labeled as PUSCH-TimeDomainWindowLength Confirm; otherwise, the nominal TDW is determined based on UE capability signaling. It is necessary to specify which UE capability signaling to use and whether / how to use UE assistance information (if supported).

[0043] In some solutions, for NTN-specific PUSCH DMRS binding, five alternative options are considered for determining the actual TDW. In the first option, no additional events are added, assuming no specific impact on the actual TDW determination. In the second option, new events for time advance (TA) pre-compensation timing are dynamically indicated by the gNB, and the TA pre-compensation timing can be dynamically indicated by the gNB. It should be noted that the UE can perform TA pre-compensation updates at the indicated timing. In the third option, the actual TDW can be dynamically indicated by the gNB. In the fourth option, new events based on epoch time can be used for determining the actual TDW. In the fifth option, new events based on antenna switching can be used for determining the actual TDW.

[0044] In some solutions, for NTN-specific PUSCH DMRS bonding, UE capability reports (other than FG 44-2) can be selected from one or more of the following options 1a-1g. In option 1a, new capabilities other than FG 44-2 may not be reported. It should be noted that FG 30-4 is reported considering pre-compensation to keep phase rotation caused by timing drift within phase difference limits and without considering TA pre-compensation updates. In option 1b: the maximum TDW length can be reported when pre-compensation is performed to keep phase rotation caused by timing drift within phase difference limits and without considering TA pre-compensation updates. In this option, FG 30-4 is not reported for NTN bands. In option 1c, support for antenna handover with DMRS bonding in the NTN can be reported. In option 1d: The maximum TDW length per NTN platform (e.g., Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary Earth Orbit (GEO)) can be reported, taking into account TA pre-compensation updates. In option 1e: The maximum TDW length per elevation angle can be reported, taking into account TA pre-compensation updates. In option 1f: Whether actual TDW across pre-compensation segments is supported. Segments defined in R17 IoT-NTN can be used as a reference. In option 1g: Whether TA pre-compensation updates are supported within actual TDW without violating phase difference limits can be reported.

[0045] Regarding UE auxiliary information (e.g., signaling reports other than UE capability reports), one or more of the following options 2a-2d can be selected. In option 2a, auxiliary information may not be reported. In option 2b, the maximum TDW length based on the reporting timing may be reported. In option 2c, TA adjustment timing may be reported. In option 2d, antenna switching intervals may be reported.

[0046] There is no example signaling flow for FG 44-2. Despite the solutions described above, several issues remain to be addressed. One such issue is how to determine the nominal TDW and / or actual TDW based on the UE's capabilities if the UE does not report or does not have an FG with NTN DMRS binding enhancements. In other words, how to determine the nominal TDW and / or actual TDW based on the UE's capabilities without having an FG 44-2. For example, how to determine the nominal and / or actual TDW without having an FG 44-2 but with antenna switching capabilities is an unresolved issue.

[0047] According to some embodiments of this disclosure, if the terminal device has not confirmed its FG 44-2 capability but has confirmed its antenna switching capability and FG 30-4, the TDW for DMRS bonding can be determined implicitly and explicitly using specific parameters. These specific parameters can be based on antenna switching information reported by the terminal device or predefined constants. In this way, if the terminal device has not confirmed its FG 44-2 capability but has confirmed its antenna switching capability and FG 30-4, basic coverage gain with TDW can be provided to the NR NTN.

[0048] refer to Figure 3 This illustrates a signaling flow 300 for an example communication process between terminal device 110 and network device 120 according to some embodiments of the present disclosure. For discussion purposes, reference will be made to... Figure 1 The signaling flow 300 is discussed, for example, by using terminal device 110 and network device 120.

[0049] like Figure 3 As shown, terminal device 110 sends (310) first information to network device 120. This first information may indicate the antenna switching capability of terminal device 110, for example, the antenna switching capability for uplink transmission over a continuous time period, or the antenna switching interval of terminal device 110. Alternatively or otherwise, the first information may indicate a first parameter associated with the determination of TDW for DMRS bonding, for example, the TDW length that terminal device 110 can use for DMRS bonding, or the period for updating the timing advance (TA) of terminal device 110. This first information may be reported to network device 120 via any suitable signaling, such as a new FG (referred herein to as FG 44-2x) or uplink control information (UCI) / MAC CE / channel state information (CSI).

[0050] Accordingly, network device 120 receives (320) the first information from terminal device 110.

[0051] In some example implementations, in the case of an explicit procedure, network device 120 may determine (330) second information. This second information may indicate one or more TDWs, for example, the nominal TDW length or an event associated with the actual TDW. Network device 120 may send (340) this second information to terminal device 110. This second information may be sent to terminal device 120 via any suitable signaling, such as through the parameter " pusch-TimeDomainWindowLength ", RRC signaling, DCI, MAC CE, etc."

[0052] Accordingly, terminal device 110 may receive (350) the second information from network device 120. Then, terminal device 110 may determine (360) the TDW for DMRS binding based on the second information. The second information may be considered an explicit indication of the TDW. In other words, in the case of an explicit process, network device 120 may explicitly indicate the TDW for DMRS binding to terminal device 110.

[0053] In some example implementations, in the case of an implicit process, network device 120 may not provide the second information to terminal device 110. Terminal device 110 may determine (370) the TDW for DMRS binding based on the first information and / or a second parameter corresponding to the first information. The second parameter may be a predefined window length. For example, terminal device 110 may base its decision on the parameter... j function f The TDW is determined based on antenna switching information or a constant known to both terminal device 110 and network device 120. Therefore, network device 120 can determine (380) the TDW for DMRS bonding based on a second parameter in the same manner as terminal device 110. For example, network device 110 can determine the TDW based on the parameter... j The function f is used to determine the TDW. In the case of an implicit procedure, no explicit indication is provided to terminal device 110. Terminal device 110 and network device 120 can determine the TDW based on the same rules.

[0054] In some implementations, to determine the TDW, terminal device 110 may determine whether it has received second information from network device 120. If terminal device 110 receives the second information from network device 120, terminal device 110 may determine the TDW based on the second information (360). If terminal device 110 does not receive the second information from network device 120, terminal device 110 may determine the TDW based on at least one of the first information or the second parameter (370).

[0055] In this way, solutions with explicit or implicit processes can be determined via TDW to enhance the coverage performance of low-cost / capable terminal devices.

[0056] In some implementations, the first information may indicate the antenna switching capability of the terminal device 120, and the TDW may be determined based on the first information and / or the second parameter. (See reference...) Figure 4A and Figure 4B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 4A and Figure 4BAn example communication process between a UE 410 and a gNB 420 according to some embodiments of this disclosure is illustrated. UE 410 is an example of terminal device 110, and gNB 420 is an example of network device 120.

[0057] like Figure 4A and Figure 4B As shown, at 430, UE 410 reports FG 30-4 to gNB 420. At 435, UE 410 reports antenna switching information to gNB 420, i.e., gNB 420's antenna switching capability. Antenna switching information can be reported via the new FG 44-2x (which will be described in detail below) or UCI, MAC CE, CSI. In this case, UE 410 does not report support for FG 44-2 to gNB 420. For example, UE 410 may report to gNB 420 that it is a RedCap (reduced capability) UE. As another example, UE 410 may report one or more events that may affect its capability, such as insufficient battery capacity or events requiring power saving.

[0058] In the explicit case, such as Figure 4A As shown, at 440, gNB 420 determines the TDW length based on the antenna handover information reported by UE 410. At 445, gNB 420 determines the TDW length using the parameter " pusch-TimeDomainWindowLength The RRC signaling, DCI, or MAC CE sends an indication of the determined TDW length to the UE 410.

[0059] If the instruction is provided by gNB 420, UE 410 can determine the TDW based on the instruction from gNB 420. Otherwise, the TDW can be determined implicitly, as described below. At 450, UE 410 performs PUSCH transmission to gNB 420 based on the determined TDW. At 460, gNB 420 processes PUSCH transmission based on the TDW indicated to UE 410.

[0060] In the implicit case, such as Figure 4B As shown, at position 465, UE 410 is based on parameters j The function determines the nominal TDW length. At 470, gNB 420 similarly uses parameters... j The function determines the nominal TDW length. Parameters j This can be based on antenna switching information or constants known to both UE 410 and gNB 420. At 475, UE 410 performs PUSCH transmission to gNB 420 based on the determined nominal TDW. At 480, gNB 420 processes PUSCH transmission based on the determined nominal TDW.

[0061] Continue to refer to Figure 3 In some example implementations, the first information may indicate antenna switching capability for uplink transmission over a continuous time period. In some example implementations, in the case of an explicit process, network device 120 may determine the nominal TDW length based on the antenna switching capability for uplink transmission over a continuous time period; and send second information indicating the nominal TDW length to terminal device 110. Accordingly, terminal device 110 may receive the second information indicating the nominal TDW length from network device 120. Then, terminal device 110 and network device 120 may determine the nominal TDW based on the indicated nominal TDW length.

[0062] In some example implementations, in the case of implicit procedures, terminal device 110 and network device 120 may base their procedures on a predefined window length (which may be determined by the parameters described above). j The duration of continuous uplink transmission (which can be represented by parameter M as described above) and the maximum duration for which terminal device 110 can maintain power consistency and phase continuity for a general network (which can be represented by parameter " maxDurationDMRS-Bundling The nominal TDW is determined by a window length (represented by a symbol). In some example implementations, the value of the predefined window length may correspond to the type of service transmitted on the uplink corresponding to the TDW. For example, the service type may be VoIP or a regular type.

[0063] In such an example implementation, terminal device 110 may support inter-slot antenna switching with DMRS binding.

[0064] refer to Figure 5A and Figure 5B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 5A and Figure 5B An example communication process between UE 410 and gNB 420 according to some embodiments of this disclosure is shown.

[0065] like Figure 5A and Figure 5BAs shown, at 510, UE 410 reports support for FG 30-4 to gNB 420. At 515, UE 410 reports support for antenna switching for PUSCH over consecutive time slots via a new feature group denoted as FG 44-2x. However, support for FG 44-2 is not provided to gNB 420. For example, UE 410 may report to gNB 420 that it is a RedCap UE. As another example, UE 410 does not support FG 44-2. As a further example, UE 410 may report one or more events that may affect its capabilities, such as insufficient battery capacity or events requiring power saving.

[0066] In one example, to report the UE's ability to switch antennas for PUSCH over consecutive time slots, it can be expressed, for example, as " interSlotAntennaSwichingPUSCH-r18 The new parameter is "". interSlotAntennaSwichingPUSCH-r18 "This can indicate whether the UE supports enhanced inter-slot antenna switching with inter-slot bonding for PUSCH. In some implementations, indicating whether the UE supports this feature can also indicate whether it supports..." dmrs- BundlingPUSCH-RepTypeA-r17 , dmrs-BundlingPUSCH-RepTypeB-r17 or dmrs- BundlingPUSCH-multiSlot-r17 At least one of them.

[0067] Table 2 shows the parameter " interSlotAntennaSwichingPUSCH-r18 Example information element (IE, information element).

[0068] Table 2: Example IE

[0069] In another example, a set of features corresponding to the antenna switching capability for PUSCH over consecutive time slots can be introduced. Table 3 shows example feature sets.

[0070] Table 3: Example Feature Groups

[0071] Therefore, in the following text, FG 44-2x can be used to indicate the ability to switch antennas for PUSCH over consecutive time slots.

[0072] Continue the process, in explicit cases, such as Figure 5A As shown, at 520, gNB 420 determines the nominal TDW length based on whether UE 410 supports antenna switching of PUSCH over consecutive time slots. At 520, gNB 420 determines the nominal TDW length, for example, through the parameter " pusch-TimeDomainWindowLength Indicate the nominal TDW length to UE 410.

[0073] At 530, if indicated by gNB 420, then UE 410 is based on parameter " pusch- TimeDomainWindowLength The nominal TDW is determined, and UE 410 performs PUSCH transmission based on the determined nominal TDW. At 535, gNB 420 processes PUSCH transmission based on the determined nominal TDW.

[0074] In the implicit case where no instruction is received from gNB 420, such as Figure 5B As shown, at 540, if UE 410 supports antenna switching for PUSCH over consecutive time slots, then UE 410 will use the parameter " maxDurationDMRS-Bundling The nominal TDW length is determined by M and j, for example, it is determined to be min( maxDurationDMRS-Bundling , M, j). As used in this article, the operation "min()" means selecting the element with the minimum value among the elements listed in parentheses as the result of the operation. In this case, the parameter j This can be the default NTN window length, and the value can depend on the service type. For example, for VoIP services, this value can be a divisor of 20, or for regular PUSCH transmissions, it can be a divisor of 32. For example, to maximize coverage performance, possible values ​​for j for VoIP could include 2, 4, or 5, and for regular PUSCH transmissions, possible values ​​for j could include 2 or 4.

[0075] Similar to UE 410, at 545, if antenna switching for PUSCH over consecutive time slots is supported, gNB420 is based on parameter " maxDurationDMRS-Bundling The nominal TDW length is determined by M and j, for example, it is determined to be min( maxDurationDMRS-Bundling At 550, UE 410 can perform PUSCH transmission based on the determined nominal TDW. At 555, gNB 420 can process PUSCH transmission based on the determined nominal TDW.

[0076] In this way, solutions with explicit and implicit processes can enhance the coverage performance of low-cost / capable UEs by determining explicit and implicit nominal TDW.

[0077] Continue to refer to Figure 3 In some example implementations, the first information may indicate the antenna switching interval of the terminal device 110.

[0078] In some example implementations, in the case of an explicit process, network device 120 may determine an antenna switching event based on the antenna switching interval of terminal device 110. Network device 120 may send second information indicating the antenna switching event to terminal device 110. Accordingly, terminal device 110 may receive the second information indicating the antenna switching event from network device 120 and determine the actual TDW based on the indicated antenna switching event. Network device 120 may determine the actual TDW based on the indicated antenna switching event.

[0079] In some example implementations, in the case of an implicit process, terminal device 110 and network device 120 may determine the period of an antenna switching event based on the antenna switching interval, and determine the actual TDW based on the period of the antenna switching event.

[0080] refer to Figure 6A and Figure 6B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 6A and Figure 6B An example communication process between UE 410 and gNB 420 according to some embodiments of this disclosure is shown.

[0081] like Figure 6A and Figure 6B As shown, at 510, UE 410 reports support for FG 30-4 to gNB 420. Then, at 610, UE 410 reports the antenna switching interval for PUSCH on consecutive time slots to gNB 420 via UCI, MAC CE, and RRC signaling. i Furthermore, it does not provide confirmation support for FG 44-2. For example, UE 410 may report to gNB 420 that it is a RedCap UE. As another example, UE 410 does not support FG 44-2. As a further example, UE 410 may report one or more events that may affect its capabilities, such as events that UE 410 has insufficient battery capacity or requires power saving.

[0082] In the explicit case, such as Figure 6A As shown, at position 615, the gNB 420 can determine the antenna switching event period as the antenna switching interval. i At 620, the gNB can explicitly indicate the configuration of the antenna switching event via, for example, RRC signaling, DCI, MAC CE, etc. At 625, if indicated by gNB 420, UE 410 can determine the actual TDW based on the antenna switching event. At 630, UE 410 can perform PUSCH transmission based on the determined actual TDW. At 635, gNB 420 processes PUSCH transmission based on the determined actual TDW determined by the antenna switching event.

[0083] In the implicit case where no instruction is received from gNB 420, such as Figure 6B As shown, at position 640, UE 410 can determine the actual TDW using antenna switching events, where the antenna switching event period is equal to the antenna switching interval. i At position 645, gNB 420 can be used with an antenna switching interval equal to the required range. i The actual TDW is determined by the antenna switching event period. At 650, UE 410 can perform PUSCH transmission based on the determined actual TDW. At 655, gNB 420 processes PUSCH transmission based on the determined actual TDW.

[0084] In this way, solutions with explicit and implicit processes can enhance the coverage performance of low-cost / capable UEs by using antenna switching intervals reported by the UE, through explicit and implicit actual TDW determination.

[0085] Return to reference Figure 3 In some example implementations, the first information may indicate a first parameter (which may be represented by u), and the terminal device 110 and the network device 120 may determine the TDW based on the second information or the first parameter.

[0086] refer to Figure 7A and Figure 7B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 7A and Figure 7B An example communication process between UE 410 and gNB 420 according to some embodiments of this disclosure is shown.

[0087] like Figure 7A and Figure 7B As shown, at 510, UE 410 reports support for FG 30-4 to gNB 420. At 710, UE 410 reports the first parameters for the upcoming PUSCH transmission to gNB 420. u For example, via RRC signaling, DCI, or MACCE. However, support for FG 44-2 and antenna switching information are not provided. For example, UE 410 may report to gNB 420 that it is a RedCap UE. As another example, UE 410 does not support FG 44-2. As a further example, UE 410 may report one or more events that may affect its capabilities, such as events that UE 410 has insufficient battery capacity or requires power saving.

[0088] In the explicit case, such as Figure 7A As shown, at 715, gNB 420 can base its response on the first parameter reported by UE 410. uTo determine the TDW indication. At 720, gNB 420 can, for example, use the parameter " pusch-TimeDomainWindowLength The TDW instruction is sent via RRC signaling, DCI, and MAC CE. At 725, UE 410 can perform PUSCH transmission according to the TDW indicated by gNB 420. At 730, gNB 420 can process PUSCH based on the indicated TDW.

[0089] In the implicit case where no instruction is received from gNB 420, such as Figure 7B As shown, at 745, UE 410 can determine TDW based on a function f of the first parameter u, where u is reported by UE 410 via, for example, a MAC CE report. At 750, gNB 420 can determine TDW based on the first parameter... u The function f is used to determine the TDW, where u The UE reports this via MAC CE. At 755, UE 410 can perform PUSCH transmission based on the determined TDW. At 760, gNB 420 can process PUSCH transmission based on the determined TDW.

[0090] References above Figure 7A and Figure 7B The example implementation described reports the first parameter. u However, the antenna switching capability was not reported to the gNB. It should be noted, however, that antenna switching capability is not tied to FG 44-2, meaning that a UE without FG 44-2 may have antenna switching capability.

[0091] Therefore, in some example implementations, the UE may report the first parameter to the gNB. u Antenna switching capability. In such an implementation, the TDW can be further determined based on the antenna switching capability or parameters associated with the antenna switching capability (e.g., parameter j as described above).

[0092] In this way, solutions with explicit and implicit processes enable DMRS binding to enhance the coverage performance of low-cost / capable UEs via the TDW length recommended by the UE.

[0093] In some implementations, the first parameter may be the TDW length that the terminal device can use for DMRS binding, for example, a suggested nominal TDW length. In some example implementations, in the case of an explicit procedure, network device 120 may determine the nominal TDW length based on the TDW length that can be used by the terminal device; and send second information indicating the nominal TDW length to terminal device 110. Accordingly, terminal device 110 may receive the second information indicating the nominal TDW length from network device 120. Terminal device 110 and network device 120 may determine the nominal TDW based on the indicated nominal TDW length.

[0094] In some example implementations, in the case of an implicit process, terminal device 110 and network device 120 may base their decisions on at least the proposed TDW length, the duration of continuous uplink transmission (e.g., parameter M), and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network (e.g., parameter M). maxDurationDMRS- Bundling The nominal TDW is determined by this method.

[0095] In some example implementations, the first parameter u This can be indicated in the power headroom report (PHR). Specifically, the first parameter can be indicated in the maximum permissible exposure (MPE) field of the PHR. Typically, the MPE field in the PHR MAC CE is only used for the FR2 operating band. Terminal devices in the NR NTN may only operate on the FR1 band. Therefore, the MPE field is reserved as a reserved bit for communication between the terminal device and the NTN. Due to limitations in uplink transmit power and antenna gain, terminal devices may require coverage enhancement to meet basic VoIP requirements. Here, the reserved bits in the MPE field are reused to represent the parameter. u UE assistance information can be passed to gNB and the determination of TDW can be optimized.

[0096] refer to Figure 8A and Figure 8B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 8A and Figure 8B An example communication procedure between UE 410 and gNB 420 according to some embodiments of this disclosure is illustrated. In this example, the first parameter... u This is the recommended TDW length.

[0097] like Figure 8A and Figure 8BAs shown, at 510, UE 410 reports support for FG 30-4 to gNB 420. At 812, UE 410, for example via MAC CE, reports the proposed TDW length for the upcoming PUSCH transmission to gNB 420. u However, support for FG 44-2 and antenna switching information are not provided. For example, UE 410 may report to gNB 420 that it is a RedCap UE. As another example, UE 410 does not support FG 44-2. As a further example, UE 410 may report one or more events that may affect its capabilities, such as insufficient battery capacity or events requiring power saving. Recommended TDW length u It can be considered as the nominal TDW length recommended by UE 410.

[0098] In the explicit case, such as Figure 8A As shown, at 810, gNB 420 can base its TDW length on the data reported by UE 410. u To determine the nominal TDW length. At 815, gNB 420 can be determined by, for example... parameter “ pusch-TimeDomainWindowLength "Send an indication of the determined nominal TDW length. At 820, UE 410 may perform PUSCH transmission according to the nominal TDW indicated by gNB 420. At 825, gNB 420 may process PUSCH transmission based on the determined nominal TDW."

[0099] In the implicit case where no instruction is received from gNB 420, such as Figure 8B As shown, at 830, if there is no confirmed antenna switching capability information, UE 410 can rely on the parameter " maxDurationDMRS-Bundling “, M and u To determine the nominal TDW length, for example, to determine it as min( maxDurationDMRS-Bundling M, u ),in u Reported by UE 410 via MAC CE (e.g., PHR). In some example implementations, the recommended TDW length... u This can be indicated in the MPE field of the PHR. For example, a 2-bit MPE field can be multiplexed to indicate this. u The length of , where u The value can be any value in {2, 4, 5, 8}, and the reporting time can follow the PHR-config in TS 38.311. In this way, the question of how and when to report auxiliary information is resolved.

[0100] At 835, if no confirmed antenna switching capability information is provided, the gNB 420 can rely on the parameter " maxDurationDMRS-Bundling “, M and u To determine the nominal TDW length, for example, to determine it as min( maxDurationDMRS-Bundling M, u ),in u The UE 410 reports via MAC CE (e.g., PHR). At 840, the UE 410 may perform PUSCH transmission based on the determined nominal TDW. At 845, the gNB 420 may process PUSCH transmission based on the determined nominal TDW.

[0101] Now return to the reference Figure 3 In some example implementations, the first information may also indicate antenna switching capability, and the nominal TDW may be further based on a second parameter. j To determine, as described above. For example, terminal device 110 may report antenna switching capability information to network device 120.

[0102] Still referencing Figure 8B Example. If UE 410 reports antenna switching capability, then at 830 and 835, the nominal TDW length can be based on the parameter " maxDurationDMRS-Bundling “、M、 u and j To determine, for example, to determine as min( maxDurationDMRS-Bundling M, u, j ).

[0103] In this way, solutions with explicit and implicit processes enable DMRS binding to enhance the coverage performance of low-cost / capable UEs through a nominal TDW determined by the TDW length proposed by the UE.

[0104] In some example implementations, the first parameter may be the period for updating the TA (Task Type) of terminal device 110. In some example implementations, in the case of an explicit procedure, network device 120 may determine a TA update event based on the period for updating the TA and send second information indicating the TA update event to terminal device 110. Terminal device 110 may then receive the second information indicating the TA update event from network device 120. Terminal device 110 and network device 120 may determine the actual TDW (Time Difference of Warp Drive) based on the TA update event.

[0105] In some example implementations, in the case of an implicit process, terminal device 110 and network device 120 may determine the actual TDW based on TA update events with a period for updating TA.

[0106] refer to Figure 9A and Figure 9B Specific examples are given for the explicit and implicit cases of signaling flow 300, respectively. Figure 9A and Figure 9B An example communication process between UE 410 and gNB 420 according to some embodiments of this disclosure is shown.

[0107] like Figure 9A and Figure 9B As shown, at 510, UE 410 reports support for FG 30-4 to gNB 420. At 910, UE 410 reports the proposed TA update cycle, for example via CSI report or MAC CE. l However, support for FG 44-2 and antenna switching information are not provided. For example, UE 410 may report to gNB 420 that it is a RedCap UE. As another example, UE 410 does not support FG 44-2. As a further example, UE 410 may report one or more events that may affect its capabilities, such as insufficient battery capacity or events requiring power saving.

[0108] In the explicit case, such as Figure 9A As shown, at 915, gNB 420 can update the TA period based on the UE 410 recommended. l To determine the TA update event interval, at position 920, the gNB 420 can indicate the TA update cycle via RRC signaling, MAC CE, or DCI. l At 925, if indicated by gNB 420, UE 410 can determine the actual TDW using the TA update event. At 930, UE 410 can perform PUSCH transmission based on the determined actual TDW. At 935, gNB 420 can process PUSCH transmission based on the actual TDW.

[0109] In the implicit case where no instruction is received from gNB 420, such as Figure 9B As shown, at 940, UE 410 can use the TA update event to determine the actual TDW, where the TA update event period is equal to the TA update period suggested by UE 410. l At position 945, the available cycle time of gNB is equal to... l The TA update event determines the actual TDW length. At 950, UE 410 can perform PUSCH transmission based on the determined actual TDW. At 955, gNB 420 can process PUSCH transmission based on the actual TDW.

[0110] In this way, solutions with explicit and implicit processes enable DMRS binding to enhance the coverage performance of low-cost / capable UEs via the actual TDW determined by the TA update cycle proposed by the UE.

[0111] Example signaling flow with FG 44-2 The above describes an example implementation for a terminal device with reduced capabilities (e.g., without FG 44-2). Several issues need to be addressed for terminal devices with FG 44-2. One of these issues is how to determine the TDW under restricted signaling for a UE with FG44-2 and other UE reporting information.

[0112] Given the satellite altitude and elevation angle, the relative velocity between the UE and the satellite can be calculated. The delay drift rate can then be calculated from the relative velocity. Using the delay drift rate, the maximum TDW length can be calculated using PUSCH radio resource information (e.g., subcarriers) under the constraints of RAN4 requirements.

[0113] Therefore, in some example implementations, the parameter “the first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of the NTN device” can be used. The NTN device can be a satellite or a UAS platform. A given state can include two or more of the following: the first altitude of the NTN device, the first elevation angle of the NTN device, or the payload type of the NTN device. In some implementations, this parameter may also be referred to as “MAX NTN TDW” for a given satellite altitude and elevation angle and an optional payload type (also known as architecture type).

[0114] Different payload types have different round-trip times and timing drift rates. In order to derive TDW based on a specific timing drift rate, the network may need payload type information from the end devices.

[0115] According to some embodiments of this disclosure, the terminal device reports the MAX NTN TDW length at a given satellite altitude and elevation angle (and optional architecture type). N And / or antenna switching capability. TDW can be based on the parameter MAX NTN TDW length. N and / or a function of antenna switching capability f It is implicitly determined. Alternatively, the TDW can be based on the MAX NTN TDW length. N And / or antenna switching capability is explicitly determined.

[0116] In this way, the determined TDW can be optimized to further enhance the NTN PUSCH coverage performance.

[0117] The following describes some example implementations of terminal devices with FG 44-2, with reference to example signaling flows.

[0118] refer to Figure 10 This illustrates a signaling flow 1000 for an example communication process between terminal device 110 and network device 120 according to some embodiments of the present disclosure. For discussion purposes, reference will be made to... Figure 1 The signaling process 1000 is discussed, for example, by using terminal device 110 and network device 120.

[0119] like Figure 10 As shown, terminal device 110 sends (1010) first information to network device 120. This first information may indicate the antenna switching capability of terminal device 110, for example, the antenna switching capability for uplink transmission over a continuous time period. Alternatively or additionally, the first information may indicate a first maximum duration as described above, for example, the TDW length at a given satellite altitude and elevation angle. The first information may be reported to network device 120 via any suitable signaling.

[0120] Accordingly, network device 120 receives (1020) the first information from terminal device 110.

[0121] In some example implementations, in the case of an explicit procedure, network device 120 may determine (1030) second information. This second information may indicate one or more TDWs, for example, the nominal TDW length or an event associated with the actual TDW. Network device 120 may send (1040) this second information to terminal device 110. This second information may be sent to terminal device 120 via any suitable signaling, such as through the parameter " pusch-TimeDomainWindowLength ", RRC signaling, DCI, MAC CE, etc."

[0122] Accordingly, terminal device 110 may receive (1050) the second information from network device 120. Then, terminal device 110 may determine (1060) the TDW for DMRS binding based on the second information. This second information can be considered an explicit indication of the TDW. In other words, in the case of an explicit process, network device 120 may explicitly indicate the TDW for DMRS binding to terminal device 110.

[0123] In some example implementations, in the case of an implicit process, network device 120 may not provide the second information to terminal device 110. Terminal device 110 may determine (1070) the TDW for DMRS binding based on the first information. Therefore, network device 120 may determine (1080) the TDW for DMRS binding in the same manner as terminal device 110, based on the first information. In the case of an implicit process, no explicit indication is provided to terminal device 110. Terminal device 110 and network device 120 may determine the TDW based on the same rules.

[0124] refer to Figure 11A and Figure 11B Specific examples are given for the explicit and implicit cases of signaling flow 1000, respectively. Figure 11A and Figure 11BAn example communication process between a UE 1110 and a gNB 1120 according to some embodiments of this disclosure is illustrated. UE 1110 is an example of terminal device 110, and gNB 1120 is an example of network device 120.

[0125] like Figure 11A and Figure 11B As shown, at 1130, UE 1110 reports FG 44-2 to gNB 1120. At 1135, UE 1110 reports FG 44-2x and / or FG 44-2y to gNB 1120. As mentioned above, FG 44-2x corresponds to antenna switching capability. FG 44-2y corresponds to the first maximum duration as defined above, which can also be expressed as MAX NTN TDW.

[0126] Table 4 shows an example feature group for parameter MAX NTN TDW.

[0127] Table 4 Example Feature Groups

[0128] In the explicit case, such as Figure 11A As shown, at 1140, gNB 1120 can base its MAX NTNTDW length on the data reported by UE 1110. N And / or antenna switching capabilities (i.e., FG 44-2y and / or FG 44-2x) determine the TDW length or events associated with the actual TDW. At 1145, the gNB 1120 can determine the TDW length or events associated with the actual TDW by using the parameter " pusch-TimeDomainWindowLength The RRC signaling, DCI, or MAC CE sends an indication to the UE 1110 of the determined TDW length or an event related to the actual TDW.

[0129] If the instruction is provided by gNB 1120, UE 1110 can determine the TDW based on the instruction from gNB 1120. Otherwise, the TDW can be determined implicitly, as described below. At 1150, UE 1110 can perform PUSCH transmission to gNB 1120 based on the indicated TDW. At 1160, gNB 1120 processes PUSCH transmission based on the TDW indicated to UE 1110.

[0130] In the implicit case, such as Figure 11B As shown, at 1165, UE 1110 can be based on the MAX NTN TDW length. N and / or a function of antenna switching capability f To determine the TDW length. At 1170, gNB 1120 can similarly be based on the MAX NTN TDW length. Nand / or a function of antenna switching capability f The TDW length is determined. At 1175, UE 1110 can perform PUSCH transmission to gNB 1120 based on the determined TDW. At 1180, gNB 1120 can process PUSCH transmission based on the determined TDW.

[0131] In some example implementations, the first information may indicate a first maximum duration, and the terminal device 110 may receive second information from the network device 120. The second information may indicate a nominal TDW length. The terminal device 110 may determine the nominal TDW based on the indicated nominal TDW length.

[0132] refer to Figure 12 Here is a specific example of signaling flow 1000. Figure 12 An example communication process between a UE 1110 and a gNB 1120 according to some embodiments of this disclosure is illustrated. UE 1110 is an example of terminal device 110, and gNB 1120 is an example of network device 120.

[0133] like Figure 12 As shown, at 1130, UE 1110 reports FG 44-2 to gNB 1120. At 1210, UE 1110 reports FG 44-2y to gNB 1120. In other words, in addition to FG 44-2, UE 1110 can also report the MAX NTN TDW length N to gNB 1120 for a given satellite altitude and elevation angle, and an optional architecture type.

[0134] At 1215, the gNB 1120 determines the nominal TDW length based on the MAX NTN TDW length N and satellite ephemeris. In some implementations, the nominal TDW length may be further determined based on UE positioning. At 1220, the gNB 1120 uses the parameter " pusch-TimeDomainWindowLength The RRC signaling, DCI, or MAC CE sends an indication of the determined nominal TDW length to the UE 1110.

[0135] Based on the instructions provided by gNB 1120, UE 1110 can determine the TDW (Time Difference Time Warp) from the instructions from gNB 1120. At 1225, UE 1110 performs PUSCH transmission to gNB 1120 based on the indicated TDW. At 1240, gNB 1120 processes PUSCH transmission based on the TDW indicated to UE 1110.

[0136] In this way, network device 120 can determine the duration of the change in nominal TDW based on the capability report of terminal device 110 for fast-moving satellites.

[0137] In some example implementations, the first information may indicate antenna switching capability and a first maximum duration. In some example implementations, in the case of an explicit process, terminal device 110 may receive second information from network device 120. The second information may indicate a nominal TDW length. Terminal device 110 may determine the nominal TDW based on the indicated nominal TDW length.

[0138] In some example implementations, in the case of an implicit process, the terminal device 110 may base its decision on a first maximum duration (which is denoted as...). N ), and the predefined window length (as described above) j ), the duration of continuous uplink transmission (expressed as M ) and the second maximum duration (as described above) maxDurationDMRS-Bundling The nominal TDW is determined by this method.

[0139] refer to Figure 13A and Figure 13B Specific examples of signaling flow 1000 are provided below. Figure 13A and Figure 13B An example communication process between a UE 1110 and a gNB 1120 according to some embodiments of this disclosure is illustrated. UE 1110 is an example of terminal device 110, and gNB 1120 is an example of network device 120.

[0140] like Figure 13A and Figure 13B As shown, at 1130, UE 1110 reports FG 44-2 to gNB 1120. At 1310, UE 1110 reports FG 44-2x and FG 44-2y to gNB 1120. In other words, in addition to FG 44-2, UE 1110 also reports antenna switching capability (FG 44-2x) and MAX NTN TDW length N (FG 44-2y) for a given satellite altitude and elevation angle and optional payload type to gNB 1120.

[0141] At 1315, gNB 1120 reports MAX NTN TDW based on UE 1110. N The nominal TDW length is determined by the antenna switching capability. At 1320, the gNB 1120 uses the parameter " pusch-TimeDomainWindowLength The gNB sends the determined nominal TDW length to the UE 1110 via RRC signaling, DCI, or MAC CE. It should be noted that when coverage performance can be ensured through spatial diversity, the gNB may prefer to configure a shorter TDW length to ensure the UE meets RAN4 requirements.

[0142] If the indication is provided by gNB 1120, UE 1110 can determine the nominal TDW based on the indication from gNB 1120. Otherwise, the TDW can be determined implicitly, as described below. At 1325, UE 1110 performs a PUSCH transmission to gNB 1120 based on the determined nominal TDW. At 1330, gNB 1120 processes the PUSCH transmission based on the nominal TDW length indicated to UE 1110.

[0143] In the implicit case, such as Figure 13B As shown, at 1335, if antenna switching for PUSCH over consecutive time slots is supported, then UE 1110 is based on parameters. maxDurationDMRS-Bundling , N , M , j To determine the nominal TDW length, for example, to determine it as min( maxDurationDMRS-Bundling , N, M, j At 1340, gNB 1120 similarly uses parameters... maxDurationDMRS-Bundling , N , M , j To determine the nominal TDW length, for example, to determine it as min( maxDurationDMRS-Bundling , N, M, j ).

[0144] parameter j This is the default NTN window length. In some example implementations, the default NTN window length value may correspond to the type of uplink transmission service associated with TDW. For example, for VoIP services, this value is a divisor of 20, or for regular PUSCH transmissions, it is a divisor of 32. To maximize coverage performance, j The possible values ​​are 2, 4, or 5 for VoIP and 2 or 4 for regular PUSCH transmission.

[0145] At 1345, UE 1110 performs a PUSCH transmission to gNB 1120 based on the determined nominal TDW. At 1350, gNB 1120 processes the PUSCH transmission based on the determined nominal TDW.

[0146] In this way, both implicit and explicit methods are provided to determine the nominal TDW, which jointly utilizes the joint channel estimation gain and spatial diversity gain under restricted signaling.

[0147] In some example implementations, the first information may indicate the number of switchable antennas of terminal device 110 and a first maximum duration. In some example implementations, in the case of an explicit process, terminal device 110 may receive second information from network device 120. The second information may indicate a nominal TDW length. Terminal device 110 may determine the nominal TDW based on the indicated nominal TDW length.

[0148] In some example implementations, in the case of an implicit process, terminal device 110 may determine a reference duration based on the duration of continuous uplink transmissions and the number of switchable antennas. Terminal device 110 may determine the nominal TDW based on a first maximum duration, a reference duration, and a second maximum duration. During the second maximum duration, terminal device 110 may be able to maintain power consistency and phase continuity for a general network.

[0149] refer to Figure 14A and Figure 14B Specific examples of signaling flow 1000 are provided below. Figure 14A and Figure 14B An example communication process between a UE 1110 and a gNB 1120 according to some embodiments of this disclosure is illustrated. UE 1110 is an example of terminal device 110, and gNB 1120 is an example of network device 120.

[0150] like Figure 14A and Figure 14B As shown, at 1130, UE 1110 reports FG 44-2 to gNB 1120. At 1405, UE 1110 reports the number of switchable antennas to gNB 1120. s The antenna switching capability and the MAX NTN TDW length N (FG 44-2y) under a given satellite altitude and elevation angle and optional payload type.

[0151] In one example, a number corresponding to the number of switchable antennas can be introduced. s The feature set of antenna switching capability. Table 5 shows an example feature set represented as FG 44-2z.

[0152] Table 5 Example Feature Groups

[0153] At 1410, gNB 1120 is based on MAX NTN TDW N and the number of switchable antennas s To determine the nominal TDW length. s This refers to the number of switchable antennas. At 1415, the gNB 1120 uses the parameter " pusch-TimeDomainWindowLengthThe RRC signaling, DCI, or MAC CE sends an indication of the determined nominal TDW length to the UE 1110.

[0154] If the instruction is provided by gNB 1120, UE 1110 can determine the nominal TDW based on the instruction from gNB 1120. Otherwise, the TDW can be determined implicitly, as described below. At 1420, UE 1110 performs a PUSCH transmission to gNB 1120 based on the determined nominal TDW. At 1425, gNB 1120 processes the PUSCH transmission based on the nominal TDW indicated to UE 1110.

[0155] In the implicit case, such as Figure 14B As shown, at 1430, UE 1110 determines the nominal TDW length as min( maxDurationDMRS-Bundling , N, [M / s The parameter "[M / s]" can be considered as the reference duration as described above. Similarly, at 1435, gNB 1120 determines the nominal TDW length as min( maxDurationDMRS-Bundling , N,[M / s The operation [] can be floor, ceil, or round. Here, floor ensures that each antenna transmits a PUSCH signal at least once during the M repetitions. At 1440, UE 1110 performs PUSCH transmission to gNB 1120 based on the determined nominal TDW. At 1445, gNB 1120 processes PUSCH transmission based on the determined nominal TDW.

[0156] In this way, both implicit and explicit methods are provided to determine the nominal TDW, which jointly utilizes joint channel estimation gain and spatial diversity gain under constrained signaling without a predefined window length.

[0157] In some example implementations, the first information may indicate the number of switchable antennas of terminal device 110. In some example implementations, in the case of an explicit process, terminal device 110 may receive second information from network device 120. The second information may indicate an antenna switching event. Terminal device 110 may determine the actual TDW based on the indicated antenna switching event.

[0158] In some example implementations, in the case of an implicit process, terminal device 110 may determine a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas. Terminal device 110 may determine the antenna switching interval based on the reference duration and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network. Terminal device 110 may determine the actual TDW based on antenna switching events with antenna switching intervals.

[0159] refer to Figure 15A and Figure 15B Specific examples of signaling flow 1000 are provided below. Figure 15A and Figure 15B An example communication process between a UE 1110 and a gNB 1120 according to some embodiments of this disclosure is illustrated. UE 1110 is an example of terminal device 110, and gNB 1120 is an example of network device 120.

[0160] like Figure 15A and Figure 15B As shown, at 1505, UE 1110 reports FG 30-4 to gNB 1120. At 1510, UE 1110 reports the number of switchable antennas to gNB 1120. s Antenna switching capability (with) s (FG 44-2x). In other words, in addition to the FG 44-2, UE 1110 also reported a number of switchable antennas. s Antenna switching capability.

[0161] At position 1515, the gNB 1120 determines the antenna switching event based on the number of switchable antennas. s The antenna switching interval. At 1520, gNB 1120 sends an indication of the determined antenna switching event to UE 1110 via RRC signaling, DCI, or MAC CE.

[0162] If the indication is provided by gNB 1120, UE 1110 can determine the actual TDW based on the antenna switching event indicated by gNB 1120. Otherwise, the actual TDW can be determined implicitly, as described below. At 1530, UE 1110 performs a PUSCH transmission to gNB 1120 based on the determined actual TDW. At 1535, gNB 1120 processes the PUSCH transmission based on the actual TDW determined by the antenna switching event.

[0163] In the implicit case, such as Figure 15B As shown, at 1540, UE 1110 uses an interval equal to min( maxDurationDMRS-Bundling , [M / s The actual TDW is determined by the antenna switching event. At 1545, gNB1120 similarly uses an interval equal to min( maxDurationDMRS-Bundling , [M / s The actual TDW is determined by the antenna switching event. At 1550, UE 1110 performs PUSCH transmission to gNB 1120 based on the determined actual TDW. At 1555, gNB 1120 processes the PUSCH transmission based on the determined actual TDW.

[0164] In this way, both implicit and explicit methods are provided to determine the actual TDW, which jointly utilizes the joint channel estimation gain and spatial diversity gain under constrained signaling.

[0165] The above describes some example implementations. It should be noted that the different examples, parameters, signaling, etc., described with reference to the different figures can be combined in some other implementations.

[0166] Example methods and specific implementations Figure 16 A flowchart illustrating a communication method 1600 implemented at a terminal device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1600 is described from the perspective of terminal device 110.

[0167] At box 1610, terminal device 110 sends first information to network device, the first information indicating at least one of the following: the antenna switching capability of terminal device, or a first parameter associated with the time domain window (TDW) determination for demodulation reference signal (DMRS).

[0168] At box 1620, terminal device 110 determines the TDW for DMRS binding based on at least one of the following: second information from network device indicating one or more TDWs, first information, or a second parameter corresponding to the first information.

[0169] In some example implementations, terminal device 110 determines whether it has received second information from network device; determines TDW based on the second information if it has been determined that the second information has been received from network device; and determines TDW based on at least one of first information or second parameter if it has been determined that the second information has not been received from network device.

[0170] In some example implementations, the first information indicates the antenna switching capability of the terminal device, and the terminal device 110 determines the TDW based on the second information or the second parameter.

[0171] In some example implementations, the first information indicates antenna switching capability for uplink transmission over a continuous time period, and the terminal device 110 receives second information from the network device indicating the nominal TDW length; and determines the nominal TDW based on the indicated nominal TDW length.

[0172] In some example implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the terminal device 110 determines the nominal TDW based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

[0173] In some example implementations, the value of the predefined window length corresponds to the service type transmitted on the uplink corresponding to TDW.

[0174] In some example implementations, the first information indicates the antenna switching interval of the terminal device, and the terminal device 110 receives second information from the network device indicating an antenna switching event; and determines the actual TDW based on the indicated antenna switching event.

[0175] In some example implementations, the first information indicates the antenna switching interval of the terminal device, and the terminal device 110 determines the period of the antenna switching event based on the antenna switching interval; and determines the actual TDW based on the period of the antenna switching event.

[0176] In some example implementations, the first information indicates the first parameter, and the terminal device 110 determines the TDW based on the second information or the first parameter.

[0177] In some example implementations, the first parameter is the TDW length that the terminal device can use for DMRS binding, and the terminal device 110 receives second information indicating the nominal TDW length from the network device; and determines the nominal TDW based on the indicated nominal TDW length.

[0178] In some example implementations, the first parameter is the TDW length that the terminal device can use for DMRS bonding, and the terminal device 110 determines the nominal TDW based at least on the TDW length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for the general network.

[0179] In some example implementations, the first information also indicates antenna switching capability, and the nominal TDW is further determined based on a second parameter.

[0180] In some example implementations, the first parameter is indicated in the Maximum Permissible Exposure (MPE) field of the power headroom report.

[0181] In some example implementations, the first parameter is the period for updating the timing advance of the terminal device, and the terminal device 110 receives second information from the network device indicating the timing advance update event; and determines the actual TDW based on the timing advance update event.

[0182] In some example implementations, the first parameter is the period for updating the timing advance of the terminal device, and the terminal device 110 determines the actual TDW based on the timing advance update event having the period for updating the timing advance.

[0183] Figure 17 A flowchart illustrating a communication method 1700 implemented at a network device according to some embodiments of this disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The method for describing the angle of network device 120 in 1700.

[0184] At box 1710, network device 120 receives first information from terminal device indicating at least one of the following: the antenna switching capability of terminal device, or a first parameter associated with the time domain window (TDW) determination for demodulation reference signal (DMRS).

[0185] At box 1750, network device 120 determines the TDW for DMRS binding based on at least one of the following: second information, first information, or a second parameter corresponding to the first information sent to the network device indicating one or more TDWs.

[0186] In some example implementations, if the second information is sent to the terminal device, the network device 120 determines the TDW based on the second information, or based on at least one of the first information or the second parameter.

[0187] In some example implementations, the first information indicates the antenna switching capability of the terminal device, and the network device 120 determines the TDW based on the second information or the second parameter.

[0188] In some example implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, and the network device 120 determines the nominal TDW length based on the antenna switching capability for uplink transmission over that continuous time period; sends the second information indicating the nominal TDW length to the terminal device; and determines the nominal TDW based on the indicated nominal TDW length.

[0189] In some example implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the network device 120 determines the nominal TDW based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

[0190] In some example implementations, the value of the predefined window length corresponds to the service type transmitted on the uplink corresponding to TDW.

[0191] In some example implementations, the first information indicates the antenna switching interval of the terminal device, and the network device 120 determines the antenna switching event based on the antenna switching interval of the terminal device; sends the second information indicating the antenna switching event to the terminal device; and determines the actual TDW based on the indicated antenna switching event.

[0192] In some example implementations, the first information indicates the antenna switching interval of the terminal device, and the network device 120 determines the period of the antenna switching event based on the antenna switching interval; and determines the actual TDW based on the period of the antenna switching event.

[0193] In some example implementations, the first information indicates the first parameter, and the network device 120 determines the TDW based on the second information or the first parameter.

[0194] In some example implementations, the first parameter is the TDW length that the terminal device can use for DMRS binding, and the network device 120 determines the nominal TDW length based on the TDW length that can be used for the terminal device; sends second information indicating the nominal TDW length to the terminal device; and determines the nominal TDW based on the indicated nominal TDW length.

[0195] In some example implementations, the first parameter is the TDW length that the terminal device can use for DMRS bonding, and the network device 120 determines the nominal TDW based at least on the TDW length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for the general network.

[0196] In some example implementations, the first information also indicates antenna switching capability, and the nominal TDW is further determined based on a second parameter.

[0197] In some example implementations, the first parameter is indicated in the Maximum Permissible Exposure (MPE) field of the power headroom report.

[0198] In some example implementations, the first parameter is the period for updating the timing advance of the terminal device, the second information indicates the timing advance update event, and the network device 120 determines the timing advance update event based on the period for updating the timing advance; sends the second information indicating the timing advance update event to the terminal device; and determines the actual TDW based on the timing advance update event.

[0199] In some example implementations, the first parameter is the timing advance period used to update the terminal device, and the network device 120 determines the actual TDW based on the timing advance update event with the timing advance period used to update the timing advance.

[0200] Figure 18 A flowchart illustrating a communication method 1800 implemented at a terminal device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1800 is described from the perspective of terminal device 110.

[0201] At box 1810, terminal device 110 sends first information to network device, the first information indicating at least one of the following: the antenna switching capability of the terminal device, or the first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of a non-terrestrial network (NTN) device, wherein the first state of the NTN device includes two or more of the following: the first altitude of the NTN device, the first elevation angle of the NTN device, or the payload type of the NTN device.

[0202] At box 1820, terminal device 110 determines the TDW for demodulation reference signal (DMRS) binding based on at least one of the following: first information, or second information from network devices indicating one or more TDWs.

[0203] In some example implementations, terminal device 110 determines whether it has received second information from network device; determines TDW based on the second information if it has been determined that the second information has been received from network device; and determines TDW based on the first information if it has been determined that the second information has not been received from network device.

[0204] In some example implementations, the first information indicates a first maximum duration, and the terminal device 110 receives second information from the network device indicating the nominal TDW length; and determines the nominal TDW based on the indicated nominal TDW length.

[0205] In some example implementations, the first information indicates antenna switching capability and a first maximum duration, and the terminal device 110 receives second information from the network device indicating the nominal TDW length; and determines the nominal TDW based on the indicated nominal TDW length.

[0206] In some example implementations, the first information indicates antenna switching capability and a first maximum duration, and the terminal device 110 determines the nominal TDW based on the first maximum duration, a predefined window length, the duration of continuous uplink transmission, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0207] In some example implementations, the value of the predefined window length corresponds to the service type transmitted on the uplink corresponding to TDW.

[0208] In some example implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the terminal device 110 receives second information from the network device indicating the nominal TDW length; and determines the nominal TDW based on the indicated nominal TDW length.

[0209] In some example implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the terminal device 110 determines a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; and determines the nominal TDW based on the first maximum duration, the reference duration, and a second maximum duration in which the terminal device can maintain power consistency and phase continuity for a general network.

[0210] In some example implementations, the first information indicates the number of switchable antennas of the terminal device, and the terminal device 110 receives second information about antenna switching events from the network device; and determines the actual TDW based on the indicated antenna switching events.

[0211] In some example implementations, the first information indicates the number of switchable antennas of the terminal device, and the terminal device 110 determines a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; determines an antenna switching interval based on the reference duration and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network; and determines the actual TDW based on antenna switching events with antenna switching intervals.

[0212] Figure 19 A flowchart illustrating a communication method 1900 implemented at a network device according to some embodiments of this disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The method for describing the angle of network device 120 in 1900.

[0213] At box 1910, network device 120 receives first information from terminal device indicating at least one of the following: the antenna switching capability of terminal device, or the first maximum duration for which terminal device can maintain power consistency and phase continuity in a first state of non-terrestrial network (NTN) device, wherein the first state of NTN device includes two or more of the following: the first altitude of NTN device, the first elevation angle of NTN device, or the payload type of NTD device.

[0214] At box 1920, network device 120 determines the TDW for demodulation reference signal (DMRS) binding based on at least one of the following: second information sent to the terminal device indicating one or more TDWs, or first information.

[0215] In some example implementations, if second information is sent to the terminal device, network device 120 determines TDW based on the second information or based on the first information.

[0216] In some example implementations, the first information indicates a first maximum duration, and the network device 120 determines the nominal TDW length based on the first maximum duration, the second state of the NTN device corresponding to the uplink transmission, and the location of the terminal device; sends the second information indicating the nominal TDW length to the network device; and determines the nominal TDW based on the indicated nominal TDW length.

[0217] In some example implementations, the first information indicates antenna switching capability and a first maximum duration, and the network device 120 determines the nominal TDW length based on the antenna switching capability and the first maximum duration; sends the second information indicating the nominal TDW length to the terminal device; and determines the nominal TDW based on the indicated nominal TDW length.

[0218] In some example implementations, the first information indicates antenna switching capability and a first maximum duration, and network device 120 determines the nominal TDW based on the first maximum duration, a predefined window length, the duration of continuous uplink transmission, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0219] In some example implementations, the value of the predefined window length corresponds to the service type transmitted on the uplink corresponding to TDW.

[0220] In some example implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the network device 120 determines the nominal TDW length based on the number of switchable antennas and the first maximum duration of the terminal device; sends the second information indicating the nominal TDW length to the terminal device; and determines the nominal TDW based on the indicated nominal TDW length.

[0221] In some example implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the network device 120 determines a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; and determines the nominal TDW based on the first maximum duration, the reference duration, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0222] In some example implementations, the first information indicates the number of switchable antennas of the terminal device, and the network device 120 determines an antenna switching event with an antenna switching interval based on the number of switchable antennas; sends second information indicating the antenna switching event to the terminal device; and determines the actual TDW based on the indicated antenna switching event.

[0223] In some example implementations, the first information indicates the number of switchable antennas of the terminal device, and the network device 120 determines a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; determines an antenna switching interval based on the reference duration and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network; and determines the actual TDW based on antenna switching events with antenna switching intervals.

[0224] Figure 20 This is a simplified block diagram of a device 2000 suitable for implementing embodiments of the present disclosure. Device 2000 can be considered as follows: Figure 1 Another example implementation of any of the devices shown. Therefore, device 2000 may be implemented at terminal device 110 or network device 120, or may be implemented as at least a part of the terminal device or the network device.

[0225] As shown in the figure, device 2000 includes a processor 2010, a memory 2020 coupled to the processor 2010, a suitable transceiver 2040 coupled to the processor 2010, and a communication interface coupled to the transceiver 2040. The memory 2020 stores at least a portion of a program 2030. Depending on requirements, the transceiver 2040 can be used for bidirectional or unidirectional communication. The transceiver 2040 may include at least one of a transmitter 2042 and a receiver 2044. The transmitter 2042 and receiver 2044 may be functional modules or physical entities. The transceiver 2040 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal equipment.

[0226] Assume that program 2030 includes program instructions that, when executed by the associated processor 2010, enable device 2000 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 19 The embodiments discussed herein may be implemented by computer software executable by processor 2010 of device 2000, or by hardware, or by a combination of software and hardware. Processor 2010 may be configured to implement various embodiments of this disclosure. Furthermore, a combination of processor 2010 and memory 2020 may form a processing unit 2050 suitable for implementing various embodiments of this disclosure.

[0227] The memory 2020 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 2020 is shown in device 2000, several physically different memory modules may exist in device 2000. The processor 2010 can be of any type suitable for a local technology network and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 2000 may have multiple processors, such as application-specific integrated circuit (ASIC) chips, which are time-dependent on a clock that synchronizes the main processor.

[0228] According to embodiments of this disclosure, a terminal device including circuitry is provided. The circuitry is configured to: send first information to a network device, the first information indicating at least one of the following: the terminal device's antenna switching capability, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and determine the TDW for DMRS binding based on at least one of the following: second information from the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods implemented by the terminal device as discussed above.

[0229] According to embodiments of this disclosure, a network device including circuitry is provided. The circuitry is configured to: receive first information from a terminal device, the first information indicating at least one of the following: the terminal device's antenna switching capability, or a first parameter associated with determining a time-domain window (TDW) for demodulation reference signal (DMRS) binding; and determine the TDW for DMRS binding based on at least one of the following: second information sent to the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods implemented by the network device as discussed above.

[0230] As used herein, the term "circuit" can refer to hardware circuitry and / or a combination of hardware and software circuitry. For example, a circuit can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit can be any part of a hardware processor with software, including digital signal processors, software, and memory, which work together to enable a device (such as a terminal device or network device) to perform various functions. In yet another example, a circuit can be hardware circuitry and / or a processor (such as a microprocessor or a portion thereof) that requires software / firmware to operate, but which may be absent when operation is not required. As used herein, the term "circuit" also encompasses a specific implementation of hardware circuitry or a processor alone, or a portion thereof, and its accompanying software and / or firmware.

[0231] According to embodiments of this disclosure, a first apparatus is provided. The first apparatus includes: components for transmitting first information to a network device, the first information indicating at least one of: antenna switching capability of a terminal device, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and components for determining the TDW for DMRS binding based on at least one of: second information from the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information. In some embodiments, the first apparatus may include components for performing corresponding operations of method 1600. In some example embodiments, the first apparatus may also include components for performing other operations of some example embodiments of terminal device 110. The components may be implemented in any suitable form. For example, the components may be implemented as circuitry or software modules.

[0232] According to embodiments of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving first information from a terminal device, the first information indicating at least one of the following: the antenna switching capability of the terminal device, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and components for determining the TDW for DMRS binding based on at least one of the following: second information indicating one or more TDWs, the first information, or a second parameter corresponding to the first information transmitted to a network device. In some embodiments, the second apparatus may include components for performing corresponding operations of method 1700. In some example embodiments, the second apparatus may also include components for performing other operations of some example embodiments of network device 120. The components may be implemented in any suitable form. For example, the components may be implemented as circuitry or software modules.

[0233] In summary, the implementation scheme disclosed herein provides the following aspects.

[0234] In one aspect, a terminal device is proposed, the terminal device comprising: a processor configured to cause the terminal device to: send first information to a network device, the first information indicating at least one of: the terminal device's antenna switching capability, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and determine the TDW for DMRS binding based on at least one of: second information from the network device indicating one or more TDWs, the first information, or a second parameter corresponding to the first information.

[0235] In some implementations, the terminal device is further configured to: determine whether second information has been received from the network device; determine TDW based on the second information if the second information has been received from the network device; and determine TDW based on at least one of the first information or the second parameter if the second information has not been received from the network device.

[0236] In some implementations, the first information indicates the antenna switching capability of the terminal device, and the terminal device is configured to determine the TDW based on the second information or the second parameter.

[0237] In some implementations, the first information indicates antenna switching capability for uplink transmission over a continuous time period, and the terminal device is configured to: receive second information from the network device indicating the nominal TDW length; and determine the nominal TDW based on the indicated nominal TDW length.

[0238] In some implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the terminal device is configured to determine the nominal TDW based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

[0239] In some implementations, the predefined window length value corresponds to the service type transmitted on the uplink corresponding to TDW.

[0240] In some implementations, the first information indicates the antenna switching interval of the terminal device, and the terminal device is further configured to: receive second information indicating an antenna switching event from the network device; and determine the actual TDW based on the indicated antenna switching event.

[0241] In some implementations, the first information indicates the antenna switching interval of the terminal device, and the terminal device is further configured to: determine the period of the antenna switching event based on the antenna switching interval; and determine the actual TDW based on the period of the antenna switching event.

[0242] In some implementations, the first information indicates the first parameter, and the terminal device is configured to determine the TDW based on the second information or the first parameter.

[0243] In some implementations, the first parameter is the TDW length that the terminal device can use for DMRS binding, and the terminal device is configured to: receive second information indicating the nominal TDW length from the network device; and determine the nominal TDW based on the indicated nominal TDW length.

[0244] In some implementations, the first parameter is the TDW length that the terminal device can use for DMRS bonding, and the terminal device is made to determine the nominal TDW based at least on the TDW length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for the general network.

[0245] In some implementations, the first information also indicates antenna switching capability, and the nominal TDW is further determined based on a second parameter.

[0246] In some implementations, the first parameter is indicated in the Maximum Permissible Exposure (MPE) field of the power headroom report.

[0247] In some implementations, the first parameter is the period for updating the timing advance of the terminal device, and the terminal device is configured to: receive second information from the network device indicating a timing advance update event; and determine the actual TDW based on the timing advance update event.

[0248] In some implementations, the first parameter is the period for updating the timing advance of the terminal device, and the terminal device is further configured to determine the actual TDW based on the timing advance update event having the period for updating the timing advance.

[0249] In one aspect, a network device is proposed, the network device comprising: a processor configured to cause the network device to: receive first information from a terminal device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first parameter associated with a time-domain window (TDW) determination for demodulation reference signal (DMRS) binding; and determine a TDW for DMRS binding based on at least one of: second information, the first information, or a second parameter corresponding to the first information, sent to the network device indicating one or more TDWs.

[0250] In some implementations, the network device is further configured to: determine the TDW based on the second information if the second information is sent to the terminal device, or determine the TDW based on at least one of the first information or the second parameter.

[0251] In some implementations, the first information indicates the antenna switching capability of the terminal device, and the network device is configured to determine the TDW based on the second information or the second parameter.

[0252] In some implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, and the network device is configured to: determine the nominal TDW length based on the antenna switching capability for uplink transmission over a continuous time period; send the second information indicating the nominal TDW length to the terminal device; and determine the nominal TDW based on the indicated nominal TDW length.

[0253] In some implementations, the first information indicates the antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the network device is configured to determine the nominal TDW based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for the general network.

[0254] In some implementations, the predefined window length value corresponds to the service type transmitted on the uplink corresponding to TDW.

[0255] In some implementations, the first information indicates the antenna switching interval of the terminal device, and the network device is further configured to: determine an antenna switching event based on the antenna switching interval of the terminal device; send second information indicating the antenna switching event to the terminal device; and determine the actual TDW based on the indicated antenna switching event.

[0256] In some implementations, the first information indicates the antenna switching interval of the terminal device, and the network device is further configured to: determine the period of the antenna switching event based on the antenna switching interval; and determine the actual TDW based on the period of the antenna switching event.

[0257] In some implementations, the first information indicates the first parameter, and the network device is configured to determine the TDW based on the second information or the first parameter.

[0258] In some implementations, the first parameter is the TDW length that the terminal device can use for DMRS binding, and the network device is configured to: determine the nominal TDW length based on the TDW length that can be used by the terminal device; send second information indicating the nominal TDW length to the terminal device; and determine the nominal TDW based on the indicated nominal TDW length.

[0259] In some implementations, the first parameter is the TDW length that the terminal device can use for DMRS bonding, and the network device is made to determine the nominal TDW based at least on the TDW length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for the general network.

[0260] In some implementations, the first information also indicates antenna switching capability, and the nominal TDW is further determined based on a second parameter.

[0261] In some implementations, the first parameter is indicated in the Maximum Permissible Exposure (MPE) field of the power headroom report.

[0262] In some implementations, the first parameter is the period for updating the timing advance of the terminal device, the second information indicates the timing advance update event, and the network device is configured to: determine the timing advance update event based on the period for updating the timing advance; send the second information indicating the timing advance update event to the terminal device; and determine the actual TDW based on the timing advance update event.

[0263] In some implementations, the first parameter is the timing advance period used to update the terminal device, and the network device is further configured to determine the actual TDW based on the timing advance update event with the timing advance period used to update the timing advance.

[0264] In one aspect, a terminal device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the terminal device as discussed above.

[0265] In one aspect, a network device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the network device as discussed above.

[0266] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the terminal device discussed above.

[0267] In one aspect, a computer-readable medium stores instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0268] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods discussed above and implemented by the terminal device.

[0269] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0270] According to embodiments of this disclosure, a first apparatus is provided. The first apparatus includes: components for transmitting first information to a network device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of a non-terrestrial network (NTN) device, wherein the first state of the NTN device includes two or more of: a first altitude of the NTN device, a first elevation angle of the NTN device, or a payload type of the NTN device; and components for determining a TDW for demodulation reference signal (DMRS) bonding based on at least one of: the first information, or second information from the network device indicating one or more TDWs. In some embodiments, the first apparatus may include components for performing corresponding operations of method 1800. In some example embodiments, the first apparatus may also include components for performing other operations of some example embodiments of terminal device 110. The components may be implemented in any suitable form. For example, the components may be implemented as circuitry or software modules.

[0271] According to embodiments of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving first information from a terminal device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of a non-terrestrial network (NTN) device, wherein the first state of the NTN device includes two or more of: a first altitude of the NTN device, a first elevation angle of the NTN device, or a payload type of the NTD device; and components for determining a TDW for demodulation reference signal (DMRS) bonding based on at least one of: second information indicating one or more TDWs transmitted to the terminal device, or the first information. In some embodiments, the second apparatus may include components for performing corresponding operations of method 1900. In some example embodiments, the second apparatus may also include components for performing other operations in some example embodiments of network device 120. The components may be implemented in any suitable form. For example, the components may be implemented as circuitry or software modules.

[0272] In summary, the implementation scheme disclosed herein provides the following aspects.

[0273] In one aspect, a terminal device is proposed, comprising: a processor configured to cause the terminal device to: send first information to a network device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of a non-terrestrial network (NTN) device, wherein the first state of the NTN device includes two or more of: a first altitude of the NTN device, a first elevation angle of the NTN device, or a payload type of the NTN device; and determine a TDW for demodulation reference signal (DMRS) binding based on at least one of: the first information, or second information from the network device indicating one or more TDWs.

[0274] In some implementations, the terminal device is further configured to: determine whether second information has been received from the network device; determine TDW based on the second information if the second information has been received from the network device; and determine TDW based on the first information if the second information has not been received from the network device.

[0275] In some implementations, the first information indicates a first maximum duration, and the terminal device is configured to: receive second information from the network device indicating a nominal TDW length; and determine the nominal TDW based on the indicated nominal TDW length.

[0276] In some implementations, the first information indicates antenna switching capability and a first maximum duration, and the terminal device is configured to: receive second information indicating a nominal TDW length from the network device; and determine the nominal TDW based on the indicated nominal TDW length.

[0277] In some implementations, the first information indicates antenna switching capability and a first maximum duration, and the terminal device is configured to determine the nominal TDW based on the first maximum duration, a predefined window length, the duration of continuous uplink transmission, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0278] In some implementations, the predefined window length value corresponds to the service type transmitted on the uplink corresponding to TDW.

[0279] In some implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the terminal device is configured to: receive second information indicating the nominal TDW length from the network device; and determine the nominal TDW based on the indicated nominal TDW length.

[0280] In some implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the terminal device is configured to: determine a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; and determine the nominal TDW based on the first maximum duration, the reference duration, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0281] In some implementations, the first information indicates the number of switchable antennas of the terminal device, and the terminal device is configured to: receive second information about an antenna switching event from the network device; and determine the actual TDW based on the indicated antenna switching event.

[0282] In some implementations, the first information indicates the number of switchable antennas of the terminal device, and the terminal device is configured to: determine a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; determine an antenna switching interval based on the reference duration and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network; and determine the actual TDW based on antenna switching events with antenna switching intervals.

[0283] In one aspect, a network device is proposed, comprising: a processor configured such that the network device: receives first information from a terminal device, the first information indicating at least one of: the antenna switching capability of the terminal device, or a first maximum duration for which the terminal device can maintain power consistency and phase continuity in a first state of a non-terrestrial network (NTN) device, wherein the first state of the NTN device includes two or more of: a first altitude of the NTN device, a first elevation angle of the NTN device, or a payload type of the NTD device; and determines a TDW for demodulation reference signal (DMRS) binding based on at least one of: second information indicating one or more TDWs transmitted to the terminal device, or the first information.

[0284] In some implementations, the network device is further configured to determine the TDW based on the second information if the second information is sent to the terminal device, or to determine the TDW based on the first information.

[0285] In some implementations, the first information indicates a first maximum duration, and the network device is configured to: determine a nominal TDW length based on the first maximum duration, a second state of the NTN device corresponding to the uplink transmission, and the location of the terminal device; send second information indicating the nominal TDW length to the network device; and determine the nominal TDW based on the indicated nominal TDW length.

[0286] In some implementations, the first information indicates antenna switching capability and a first maximum duration, and the network device is configured to: determine a nominal TDW length based on the antenna switching capability and the first maximum duration; send second information indicating the nominal TDW length to the terminal device; and determine the nominal TDW based on the indicated nominal TDW length.

[0287] In some implementations, the first information indicates antenna switching capability and a first maximum duration, and the network device is configured to determine the nominal TDW based on the first maximum duration, a predefined window length, the duration of continuous uplink transmission, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0288] In some implementations, the predefined window length value corresponds to the service type transmitted on the uplink corresponding to TDW.

[0289] In some implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the network device is configured to: determine the nominal TDW length based on the number of switchable antennas and the first maximum duration of the terminal device; send second information indicating the nominal TDW length to the terminal device; and determine the nominal TDW based on the indicated nominal TDW length.

[0290] In some implementations, the first information indicates the number of switchable antennas and the first maximum duration of the terminal device, and the network device is configured to: determine a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; and determine the nominal TDW based on the first maximum duration, the reference duration, and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network.

[0291] In some implementations, the first information indicates the number of switchable antennas of the terminal device, and the network device is configured to: determine an antenna switching event with an antenna switching interval based on the number of switchable antennas; send second information indicating the antenna switching event to the terminal device; and determine the actual TDW based on the indicated antenna switching event.

[0292] In some implementations, the first information indicates the number of switchable antennas of the terminal device, and the network device is configured to: determine a reference duration based on the duration of continuous uplink transmission and the number of switchable antennas; determine an antenna switching interval based on the reference duration and a second maximum duration during which the terminal device can maintain power consistency and phase continuity for a general network; and determine the actual TDW based on antenna switching events with antenna switching intervals.

[0293] In one aspect, a terminal device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the terminal device as discussed above.

[0294] In one aspect, a network device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the network device as discussed above.

[0295] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the terminal device discussed above.

[0296] In one aspect, a computer-readable medium stores instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0297] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods discussed above and implemented by the terminal device.

[0298] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0299] Generally, various embodiments of this disclosure can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or other illustrations, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0300] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in program modules) that execute on a target real or virtual processor in a device to perform the functions described above. Figures 1 to 20 The described process or method. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined in various implementation schemes or split among program modules as needed. The machine-executable instructions used for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0301] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0302] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium containing or storing a program used by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0303] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all the illustrated operations to achieve the desired result. In some environments, multitasking and parallel processing can be advantageous. While several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in a single embodiment in combination. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0304] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

Claims

1. A terminal device, the terminal device comprising: Processor, the processor being configured to cause the terminal device to: Send a first message to the network device, the first message indicating at least one of the following: The antenna switching capability of the terminal device, or The first parameter is determined by the time domain window (TDW) bound to the demodulation reference signal (DMRS); The TDW used for DMRS binding is determined based on at least one of the following: Second information from the network device indicating one or more TDWs. The first information, or The second parameter corresponding to the first information.

2. The terminal device according to claim 1, wherein the terminal device is further configured such that: Determine whether the second information has been received from the network device; Based on the determination that the second information has been received from the network device, the TDW is determined; as well as The TDW is determined based on at least one of the first information or the second parameter, if it is determined that the second information has not been received from the network device.

3. The terminal device according to claim 1, wherein the first information indicates the antenna switching capability of the terminal device, and the terminal device is configured to: The TDW is determined based on the second information or the second parameter.

4. The terminal device according to claim 3, wherein the first information indicates antenna switching capability for uplink transmission over a continuous time period, and the terminal device is configured to: Receive the second information indicating the nominal TDW length from the network device; and The nominal TDW is determined based on the indicated nominal TDW length.

5. The terminal device according to claim 3, wherein the first information indicates antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the terminal device is configured such that: The nominal TDW is determined based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

6. The terminal device according to claim 5, wherein the value of the predefined window length corresponds to the service type transmitted on the uplink corresponding to the TDW.

7. The terminal device according to claim 3, wherein the first information indicates the antenna switching interval of the terminal device, and the terminal device is further configured such that: Receive the second information indicating an antenna switching event from the network device; and The actual TDW is determined based on the indicated antenna switching event.

8. The terminal device according to claim 3, wherein the first information indicates the antenna switching interval of the terminal device, and the terminal device is further configured such that: The period of the antenna switching event is determined based on the antenna switching interval; and The actual TDW is determined based on the period of the antenna switching event.

9. The terminal device according to claim 1, wherein the first information indicates the first parameter, and the terminal device is configured to: The TDW is determined based on the second information or the first parameter.

10. The terminal device of claim 9, wherein the first parameter is a TDW length that the terminal device can use for DMRS binding, and the terminal device is configured such that: Receive the second information indicating the nominal TDW length from the network device; and The nominal TDW is determined based on the indicated nominal TDW length.

11. The terminal device of claim 9, wherein the first parameter is a TDW length that the terminal device can use for DMRS binding, and the terminal device is configured such that: The nominal TDW is determined at least based on the TDW length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

12. The terminal device of claim 11, wherein the first information further indicates the antenna switching capability, and the nominal TDW is further determined based on the second parameter.

13. The terminal device according to any one of claims 10 to 12, wherein the first parameter is indicated in the maximum permissible exposure (MPE) field of the power headroom report.

14. The terminal device according to claim 9, wherein the first parameter is a period for updating the timing advance of the terminal device, and the terminal device is configured such that: Receive the second information indicating an early update event from the network device; and The actual TDW is determined based on the aforementioned timed advance update event.

15. The terminal device according to claim 9, wherein the first parameter is a period for updating the timing advance of the terminal device, and the terminal device is further configured such that: The actual TDW is determined based on a timing advance update event with a period for updating the timing advance.

16. A network device, the network device comprising: Processor, the processor being configured to cause the network device to: Receive first information from the terminal device, the first information indicating at least one of the following: The antenna switching capability of the terminal device, or The first parameter is determined by the time-domain window (TDW) bound to the demodulation reference signal (DMRS); The TDW used for DMRS binding is determined based on at least one of the following: Second information indicating one or more TDWs sent to the network device. The first information, or The second parameter corresponding to the first information.

17. The network device of claim 1, wherein the network device is further configured such that: If the second information is sent to the terminal device, then the TDW is determined based on the second information, or The TDW is determined based on at least one of the first information or the second parameter.

18. The network device of claim 16, wherein the first information indicates the antenna switching capability of the terminal device, and the network device is configured such that: The TDW is determined based on the second information or the second parameter.

19. The network device of claim 18, wherein the first information indicates antenna switching capability for uplink transmission over a continuous time period, the second parameter is a predefined window length, and the network device is configured such that: The nominal TDW is determined based on the predefined window length, the duration of continuous uplink transmission, and the maximum duration for which the terminal device can maintain power consistency and phase continuity for a general network.

20. The network device of claim 16, wherein the first information indicates the first parameter, and the network device is configured such that: The TDW is determined based on the second information or the first parameter.

Images