Uplink muting configuration method and apparatus, terminal, and network side device

Abstract

The present application belongs to the technical field of communications. Disclosed are an uplink muting configuration method and apparatus, a terminal, and a network side device. The uplink muting configuration method in the embodiments of the present application comprises: a terminal receiving, from a network side device, first information related to uplink muting, wherein the first information is at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information respectively configured for a DG PUSCH and a CG PUSCH, configuration information configured by means of higher layer signaling, and indication information indicated by means of DCI; and on the basis of the first information, the terminal executing an uplink-muting-related operation on a first PUSCH.

Description

Uplink silent configuration method, device, terminal and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410984816.6, filed in China on July 22, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to an uplink silent configuration method, apparatus, terminal, and network-side equipment. Background Technology

[0004] In dynamic time division duplex (TDD) systems or subband full duplex (SBFD) systems, there is interference between base stations. In order to improve system performance, the covariance matrix of the interference channel can be obtained first, and then interference cancellation can be performed based on the covariance matrix.

[0005] However, to obtain the covariance matrix of the aforementioned interference channels, the terminal needs to perform uplink muting, i.e., UL muting, when transmitting the Physical Uplink Shared Channel (PUSCH). However, how to configure, indicate, or enable uplink muting and the applied uplink muting pattern has become a pressing technical problem that needs to be solved. Summary of the Invention

[0006] This application provides an uplink muting configuration method, apparatus, terminal, and network-side device, which can configure, indicate, or enable uplink muting and the uplink muting style of applications to facilitate the elimination of interference between base stations.

[0007] In a first aspect, an uplink silence configuration method is provided, executed by a terminal. The method includes: the terminal receiving first information related to uplink silence from a network-side device, the first information being at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI; the terminal performing uplink silence-related operations on a first PUSCH based on the first information.

[0008] Secondly, an uplink silence configuration method is provided, executed by a network-side device. The method includes: the network-side device sending first information related to uplink silence to the terminal; wherein the first information is at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0009] Thirdly, an uplink silence configuration apparatus is provided, comprising: a receiving module and a processing module; the receiving module is configured to receive first information related to uplink silence from a network-side device, the first information being at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI; the processing module is configured to perform uplink silence-related operations on a first PUSCH based on the first information.

[0010] Fourthly, an uplink silence configuration device is provided, the device comprising: a transmitting module; the transmitting module being configured to transmit first information related to uplink silence to a terminal; wherein the first information is at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0011] Fifthly, an uplink silence configuration device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0012] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0013] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive first information related to uplink muting from a network-side device, the first information being at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI; the processor is configured to perform uplink muting-related operations on a first PUSCH based on the first information.

[0014] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0015] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the communication interface is used to send first information related to uplink silence to a terminal; wherein the first information is at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0016] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0017] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0018] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0019] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0020] In this embodiment, the terminal receives first information related to uplink silence from the network-side device. The first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI. Based on the first information, the terminal performs uplink silence-related operations on the first PUSCH. This scheme allows the terminal to receive uplink silence-related configuration or indication information from the network-side device, enabling it to perform uplink silence-related operations on the transmitted PUSCH based on this configuration or indication information (e.g., whether to perform uplink silence, or on which resources to perform uplink silence, etc.). This provides a specific scheme for configuring, indicating, or enabling uplink silence and the application of uplink silence patterns, facilitating uplink silence when transmitting PUSCH. Attached Figure Description

[0021] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0022] Figure 2 is a schematic diagram of cross-link interference in related technologies;

[0023] Figure 3 is a schematic diagram of the SBFD method in related technologies;

[0024] Figure 4 is a flowchart of an uplink silent configuration method provided in an embodiment of this application;

[0025] Figure 5 is a schematic diagram of an uplink silent configuration method provided in an embodiment of this application;

[0026] Figure 6 is a flowchart of another uplink silent configuration method provided in an embodiment of this application;

[0027] Figure 7 is a schematic diagram of an uplink silent configuration device provided in an embodiment of this application;

[0028] Figure 8 is a schematic diagram of another uplink silent configuration device provided in an embodiment of this application;

[0029] Figure 9 is a schematic diagram of the communication device provided in an embodiment of this application;

[0030] Figure 10 is a schematic diagram of the hardware structure of the terminal provided in an embodiment of this application;

[0031] Figure 11 is a schematic diagram of the hardware structure of the network-side device provided in an embodiment of this application;

[0032] Figure 12 is one of the schematic diagrams of frequency domain comb division in an uplink silent configuration method provided in an embodiment of this application;

[0033] Figure 13 is a second schematic diagram of frequency domain comb division in an uplink silent configuration method provided in an embodiment of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0035] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0036] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0037] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0038] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0039] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0040] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0041] The uplink silent configuration method, apparatus, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0042] Currently, when NR cells are deployed on asymmetric spectrum, TDD duplex mode is typically used. In this case, TDD-UL-DL-ConfigCommon can be configured in the cell common parameters to indicate TDD frame structure information, including the TDD frame period, the number of complete downlink or uplink time slots contained in a single frame period, and the number of additional downlink or uplink symbols contained in addition to the complete downlink or uplink time slots. In addition, TDD-UL-DL-ConfigDedicated can be configured independently for each terminal using Radio Resource Control (RRC) signaling. This is used to further modify the uplink and downlink symbol configuration of one or more time slots within a single frame period based on TDD-UL-DL-ConfigCommon (i.e., the initial value of the uplink and downlink symbol configuration of the time slot is specified by TDD-UL-DL-ConfigCommon and then further modified by TDD-UL-DL-ConfigDedicated; this modification only applies to the terminal receiving this RRC signaling). However, this modification is limited to further indicating uplink or downlink symbols within the time slot (i.e., flexible symbols, which do not have a clearly defined transmission direction and can be determined later as needed for downlink or uplink transmission). It cannot modify the uplink or downlink symbols within the time slot to other directions.

[0043] The aforementioned TDD-UL-DL-ConfigCommon and / or TDD-UL-DL-ConfigDedicated are optional configurations. Since these configuration information can only be semi-statically configured or modified based on information from the RRC layer, each symbol within a single TDD frame period (combined with its configured transmission direction) determined by this configuration information is referred to below as a semi-static uplink, downlink, or flexible symbol. Symbols can be further abstracted into time-domain units, which can correspond to time slots, symbols, etc. Therefore, a single TDD frame period can contain multiple semi-static uplink, downlink, or flexible time-domain units based on the aforementioned configuration information.

[0044] When TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated are not configured, there is no explicit concept of TDD frame period. At this time, each time slot or symbol in each radio frame of the NR cell can be understood as a semi-static flexible time domain or symbol (i.e., a semi-static flexible slot / symbol), or abstracted as a semi-static flexible time domain unit.

[0045] In addition, the base station can also indicate the slot format indicator (SFI) through dynamic signaling group common DCI (e.g., DCI 2-0); wherein, the dynamic SFI can only indicate whether the static flexible symbol is uplink, downlink or flexible, but cannot change the transmission direction of the static uplink or downlink symbol 1.

[0046] In a dynamic TDD system, adjacent cells can be configured with different TDD configurations, or different User Equipment (UE) devices within a single cell can have different TDD configurations or indications. This can lead to interference between adjacent cells (gNB to gNB) or between UEs (UE to UE). As shown in Figure 2, when gNB2 is transmitting downlink data while gNB1 is receiving uplink data, gNB1 will receive interference from gNB2. Similarly, when UE1 is transmitting uplink data while UE2 is receiving downlink data, UE2 will receive interference from UE1.

[0047] Currently, when deploying traditional cellular networks, based on available spectrum and service characteristics, Frequency Division Duplex (FDD) or Time-Division Duplex (TDD) can be used. With FDD, uplink and downlink transmissions operate on different frequencies, do not interfere with each other, and can occur simultaneously. With TDD, uplink and downlink transmissions operate on the same frequency, interleaving in a time-division manner. To more flexibly utilize limited spectrum resources, dynamically match service demands, and improve resource utilization efficiency as well as data transmission performance such as uplink coverage and latency, SBFD has been proposed. SBFD includes:

[0048] Network-side full-duplex

[0049] From the network's perspective, uplink and downlink transmissions can occur simultaneously in different frequency subbands. To avoid interference between uplink and downlink, a guard band can be reserved between the frequency subbands corresponding to different transmission directions (e.g., uplink and downlink subbands).

[0050] Terminal-side half-duplex or full-duplex

[0051] When the terminal supports half-duplex, only uplink or downlink transmission can occur at any given time; they cannot occur simultaneously. Understandably, in this case, the network side can only perform uplink or downlink transmission at any given time, or uplink and downlink transmissions at the same time can only be performed for different terminals. When the terminal supports full-duplex, similar to the network side, uplink and downlink transmissions can occur simultaneously in different frequency subbands.

[0052] For example, Figure 3 illustrates a possible schematic diagram of the SBFD method. As shown in Figure 3, the network side semi-statically divides the frequency domain of a single carrier into three sub-bands within a portion of the downlink symbols. The two sides of the carrier are the downlink sub-bands, and the center is the uplink sub-band, in order to reduce interference to adjacent carriers. The resources other than the downlink and uplink sub-bands are the Guard Band. In the third time slot, UE1 performs uplink transmission and UE2 performs downlink reception, while the base station receives data from UE1 and simultaneously transmits data to UE2.

[0053] In dynamic TDD or SBFD systems, for gNB-to-gNB interference, the covariance matrix of the interfering channel can be obtained first, and then interference cancellation can be performed based on this covariance matrix. However, to obtain the covariance matrix of the interfering channel, the terminal needs to perform uplink muting when transmitting PUSCH, that is, there should be no PUSCH or signal transmission on certain resources. However, how to configure, indicate, or enable uplink muting and the applied uplink muting pattern has become a technical problem that urgently needs to be solved.

[0054] To address the aforementioned issues, embodiments of this application provide an uplink muting configuration method, apparatus, terminal, and network-side device. The uplink muting configuration method provided in this application can be applied to scenarios where the terminal needs to perform uplink muting when transmitting PUSCH, such as scenarios requiring interference elimination between base stations.

[0055] In the uplink silence configuration method provided in this application embodiment, the terminal can receive first information related to uplink silence from the network-side device. The first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each bandwidth part (BWP), configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for Dynamic Grant (DG) PUSCH and Configured Grant (CG) PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by Downlink Control Information (DCI). Then, based on the first information, uplink silence-related operations are performed on the first PUSCH. Through this scheme, since the terminal can receive uplink silence-related configuration information or indication information from the network-side device, the terminal can perform uplink silence-related operations on the transmitted PUSCH (e.g., whether to perform uplink silence, or on which resources to perform uplink silence, etc.) based on the configuration information or indication information. This provides a specific scheme for configuring, indicating, or enabling uplink silence and the application of uplink silence patterns, so that the terminal can perform uplink silence when transmitting PUSCH.

[0056] This application provides an uplink silence configuration method, and Figure 4 shows a flowchart of the uplink silence configuration method provided in this application embodiment. As shown in Figure 4, the uplink silence configuration method provided in this application embodiment may include the following steps 401 and 402.

[0057] Step 401: The terminal receives the first information related to uplink silence from the network-side device.

[0058] The first information mentioned above includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0059] Optionally, in this embodiment of the application, the configuration information configured for each serving cell can be the information configured by the network-side device in IE PUSCH-ServingCellConfig.

[0060] Optionally, in this embodiment of the application, the configuration information configured for each BWP (i.e., per BWP) can be the information configured by the network-side device in IE BWP-UplinkDedicated.

[0061] Optionally, in this embodiment of the application, when the first information is the configuration information configured for each waveform, the network-side device can configure Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM) waveforms (conversion precoding is not enabled) and Discrete Fourier Transform (DFT)-S-OFDM waveforms (conversion precoding is enabled).

[0062] Optionally, in this embodiment of the application, the configuration information configured for DG PUSCH and CG PUSCH respectively can be the information configured by the network-side device in IE PUSCH-config and ConfiguredGrantConfig respectively.

[0063] Optionally, in this embodiment, for the first PUSCH being a PUSCH activated after CG PUSCH type 1 and CG PUSCH type 2 (optionally, the first PUSCH does not include the PUSCH within the first cycle after activation), the aforementioned first information can be the configuration information in ConfiguredGrantConfig; for the first PUSCH being a PUSCH within the first cycle after CG PUSCH type 2 activation and a PUSCH dynamically scheduled by DCI, the aforementioned first information can be the configuration information in PUSCH-config; for the first PUSCH being a CG PUSCH retransmission, the aforementioned first information can be the configuration information in PUSCH-config or ConfiguredGrantConfig. Optionally, the aforementioned first information can be the configuration information in PUSCH-config.

[0064] Optionally, in this embodiment of the application, when the first information is the configuration information configured for each waveform (i.e., per beam), the network-side device can configure at least one of the following for each waveform: uplink muting pattern (i.e., UL muting pattern), whether to enable uplink muting (i.e., UL muting), and the condition for enabling uplink muting. The terminal can determine whether the PUSCH should be muted uplink or the uplink muting pattern applied based on the waveform corresponding to the scheduled PUSCH.

[0065] Optionally, in this embodiment, when the first information is configuration information for each beam configuration, the network-side device configures the uplink silence style and / or whether to enable uplink silence for each TCI state when configuring the Transmission Configuration Indicator (TCI) state. The network-side device configures the TCI state used for PUSCH transmission through higher-layer configuration or DCI, and the terminal determines whether the PUSCH should be uplink silenced or whether an uplink silence style should be applied based on the correspondence between the TCI state and uplink silence. Alternatively, when configuring spatial relation information, the network-side device configures the uplink silence style and / or whether to enable uplink silence for each spatial relation. The network-side device configures the spatial relation used for PUSCH transmission through higher-layer configuration or DCI, and the terminal determines whether the PUSCH should be uplink silenced or whether an uplink silence style should be applied based on the correspondence between the spatial relation and uplink silence.

[0066] Optionally, in the embodiments of this application, for multi-transmit / receive point (TRP) scenarios, for PUSCH using Space Division Multiplexing (SDM) mode, for example, the parameter multipanelScheme is set to 'SDMscheme' and associated with the first TCI state or the second TCI state respectively (the PUSCH transmission timing scheduled or activated by DCI format 0_1 ​​or 0_2 is related to the first indicated TCI-States or TCI-UL-States, and to the second indicated TCI-States or TCI-UL-States respectively), the terminal expects the first TCI state or the second TCI state to be associated with the same uplink silence pattern, or associated with the same number of uplink silence patterns, or the same number of silenced uplink symbols, or the same uplink silence enable or disable status.

[0067] Optionally, in this embodiment of the application, for a PUSCH that is rolled back to DCI scheduling or activated, or a CG PUSCH of type 1, the first information mentioned above may be configuration information configured through higher-layer signaling; or, for a PUSCH that is not rolled back to DCI scheduling or activated, the first information mentioned above may be indication information indicated by DCI.

[0068] Optionally, in this embodiment of the application, when the first information is an indication information indicated by DCI, the network-side device configures one or more uplink silencing styles through higher-layer signaling (e.g., RRC). (Optionally, the network-side device may include disabling uplink silencing when configuring the uplink silencing style.) The network-side device indicates which uplink silencing style the scheduled PUSCH adopts or whether uplink silencing is applied (i.e., enabling or disabling uplink silencing) through the DCI of the scheduled PUSCH.

[0069] Optionally, in this embodiment, the aforementioned first information can be indicated by the Time Domain Resource Assignment (TDRA) field in the DCI. Specifically, when configuring the TDRA table through higher-layer signaling, the network-side device configures whether uplink silencing is enabled and / or the applied uplink silencing style for each row of the TDRA table. That is, for each row of the TDRA, the base station can configure K2, SLIV (i.e., length indicator), mapping type, whether uplink silencing is enabled or which uplink silencing style is applied, etc. (Optionally, the number of repetitions can also be configured). The TDRA field in the DCI indicates a row index in the TDRA table configured by higher-layer signaling, and thus can indicate the uplink silencing related information corresponding to the PUSCH scheduled by the DCI.

[0070] Optionally, in this embodiment of the application, when the first information is configuration information configured through higher-layer signaling, the terminal can determine whether a certain PUSCH is enabled for uplink silencing or which uplink silencing style is applied according to predefined rules.

[0071] For example, when a PUSCH transmission symbol overlaps with an SFBD symbol (including full or partial overlap), uplink muting is enabled; otherwise, uplink muting is disabled. When the number of PUSCH symbols is greater than X, uplink muting is enabled; otherwise, uplink muting is disabled. Here, X can be configured or indicated directly or implicitly (e.g., through the first symbol index) by the network-side device, or it can be specified by the protocol, such as 7. When a PUSCH transmission symbol overlaps with the first symbol index, uplink muting is enabled; otherwise, uplink muting is disabled.

[0072] Optionally, in this embodiment of the application, the first information mentioned above may be configuration information configured through higher-layer signaling.

[0073] The configuration information configured through higher-level signaling includes information on at least one uplink silence style.

[0074] For example, when at least one of the above-mentioned uplink silence styles includes at least two uplink silence styles, each uplink silence style may correspond to a different symbol position and / or a different frequency domain position.

[0075] Optionally, in this embodiment of the application, the configuration information of the above-mentioned at least one uplink silence style may include at least one applied uplink silence style.

[0076] In this embodiment of the application, since one or more uplink silence configuration information can be configured when the first information can be configured through higher-layer signaling, the flexibility of determining the first information can be improved.

[0077] Optionally, in the embodiments of this application, the aforementioned first information may be used for at least one of the following 1.1 to 1.8:

[0078] 1.1 Enable uplink silence;

[0079] 1.2. Enable upward silence;

[0080] 1.3 Configure the uplink silent style;

[0081] 1.4 Indicates the upward silent style;

[0082] 1.5 Configure the conditions for enabling uplink silence;

[0083] 1.6. Indicates the conditions that enable uplink silence;

[0084] 1.7 Configure the conditions to disable uplink silence;

[0085] 1.8 Instructions to enable the conditions for upward silence.

[0086] Optionally, in this embodiment of the application, the condition for enabling uplink silencing can be: the number of symbols in the PUSCH is greater than X; that is, uplink silencing is applied only for PUSCHs with a symbol count greater than X. Here, X can be configured by the network-side device.

[0087] Optionally, in the embodiments of this application, the condition for enabling uplink silence can be: the PUSCH priority is high; that is, uplink silence is applied only for high-priority PUSCHs.

[0088] Optionally, in this embodiment, the condition for enabling uplink muting can be: the PUSCH is not involved in the random access procedure. For retransmissions of PUSCH involved in the random access procedure, such as msg A PUSCH, msg 3 PUSCH, or msg A PUSCH or msg 3 PUSCH, uplink muting is not enabled.

[0089] Optionally, in this embodiment, the condition for enabling uplink muting can be: the PUSCH is a PUSCH scheduled or activated by a connected UE. For non-connected PUSCHs, such as PUSCH for small data, uplink muting is not enabled.

[0090] In this embodiment of the application, since the first information can be used for at least one of 1.1 to 1.8, different information related to uplink silence can be configured or indicated through the first information, so that the terminal can perform uplink silence-related operations according to the first information.

[0091] Optionally, in embodiments of this application, the aforementioned first information may include at least one of the following 2.1 to 2.7:

[0092] 2.1 The frequency domain location corresponding to uplink silence;

[0093] 2.2 The time domain location corresponding to uplink silence;

[0094] 2.3 The period corresponding to upward silence;

[0095] 2.4. Offset value within the period corresponding to upward silence;

[0096] 2.5. Apply the uplink silence time unit;

[0097] 2.6 Apply uplink silent PUSCH;

[0098] 2.7. Silent style for upward movement.

[0099] Optionally, in the embodiments of this application, the frequency domain position corresponding to the above-mentioned uplink silence may include a comb index, such as comb 0 or comb 1.

[0100] In this context, the position corresponding to the first PRB of combo 0 can be the lowest PRB in the frequency domain allocated resources for the scheduled or activated PUSCH (such as the first PUSCH mentioned above), or it can be the lowest PRB in the frequency domain of the ULBWP, UL subband, serving cell, or carrier corresponding to the scheduled or activated PUSCH (such as the first PUSCH mentioned above), or it can be point A of the serving cell corresponding to the scheduled or activated PUSCH (such as the first PUSCH mentioned above). Uplink silence adopts a combo 2 structure, which divides the frequency domain PRBs into two combos. The interval between adjacent PRBs in each combo is one PRB, i.e., every other PRB. It can be understood that the combo 2 structure for uplink silence can be based on the frequency domain resource allocation of the scheduled or activated PUSCH, or based on the UL BWP, UL subband, serving cell, carrier, or a reference point (such as point A) where the PUSCH is located.

[0101] For example, as shown in Figure 12, when the position corresponding to the first PRB of combo 0 is the lowest PRB with allocated frequency domain resources for the scheduled or activated PUSCH (such as the first PUSCH mentioned above), if the uplink silence index is configured as combo 0, for each PUSCH, the UE determines the position of the PRB corresponding to combo 0 based on the frequency domain resources allocated to each PUSCH. The PRB position corresponding to uplink silence may differ under different PUSCH frequency domain resource allocations.

[0102] For example, as shown in Figure 13, when the position corresponding to the first PRB of comb 0 is the lowest frequency PRB of the UL BWP, UL subband, serving cell, or carrier corresponding to the scheduled or activated PUSCH (such as the first PUSCH mentioned above), or the point A of the serving cell corresponding to the scheduled or activated PUSCH (such as the first PUSCH mentioned above), if the uplink silencing index is configured as comb 0, the position of the PRB corresponding to this comb is independent of the position of the scheduled PUSCH. For each PUSCH, if uplink silencing is enabled, the UE can obtain the PRB that needs to be uplink silenced in the PUSCH resource allocation by taking the intersection of the PRB corresponding to the comb and the PRB allocated to the PUSCH.

[0103] Optionally, in this embodiment of the application, if the time domain corresponding to the uplink silence contains two symbols, the frequency domain positions on different symbols can be different. For example, the base station can configure the comb index of the uplink silence corresponding to the two symbols respectively.

[0104] Optionally, in this embodiment of the application, the time domain position corresponding to the above-mentioned uplink silence may include a first symbol index, or may include a first symbol index and a second symbol index.

[0105] Optionally, in this embodiment of the application, the time domain position corresponding to the above-mentioned uplink silence may include a first symbol index.

[0106] The first symbol index mentioned above includes any one of the following:

[0107] The symbol index relative to the starting position of the time unit in which the scheduled or activated PUSCH is located;

[0108] The symbolic index relative to the starting position of the scheduled or activated PUSCH;

[0109] The symbolic index relative to the starting position of each actual repetition of a scheduled or activated PUSCH.

[0110] The symbolic index relative to the starting position of each nominal repetition (i.e., normal repetition) of the scheduled or activated PUSCH;

[0111] The symbol index relative to the starting symbol of each hop of the scheduled or activated PUSCH;

[0112] The symbol index relative to the starting position of the time unit where the first PUSCH is located;

[0113] The symbol index relative to the starting position of the first PUSCH mentioned above;

[0114] The symbol index relative to the starting position of each actual repetition of the first PUSCH mentioned above;

[0115] The symbol index relative to the starting position of each nominal repetition of the first PUSCH mentioned above;

[0116] The symbol index relative to the starting symbol of each hop of the first PUSCH mentioned above.

[0117] Optionally, in this embodiment of the application, the PUSCH that is scheduled or activated may be the first PUSCH.

[0118] Optionally, in the embodiments of this application, the aforementioned time unit may be a time slot or a sub-time slot, etc.

[0119] Optionally, in this embodiment of the application, when the repetition type of the first PUSCH is PUSCH repetition type B, the first symbol index may be a symbol index relative to the starting position of each actual or nominal repetition of the first PUSCH.

[0120] Optionally, in the embodiments of this application, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0121] For example, if the first symbol index is determined based on whether the first PUSCH is enabled for frequency hopping, then if the first PUSCH is not enabled for frequency hopping, the first symbol index can be the symbol index relative to the start position of the time unit in which the first PUSCH is located; if the first PUSCH is enabled for frequency hopping, then the first symbol index can be the symbol index relative to the start symbol of each hop of the first PUSCH.

[0122] For example, taking the first symbol index as determined based on the PUSCH mapping type used by the first PUSCH, if the PUSCH mapping type used by the first PUSCH is PUSCH mapping type A, then the first symbol index can be the symbol index relative to the starting position of the time unit where the first PUSCH is located, or the symbol index relative to the starting symbol of each hop of the first PUSCH; if the PUSCH mapping type used by the first PUSCH is PUSCH mapping type B, then the first symbol index can be the symbol index relative to the starting position of the first PUSCH, or the symbol index relative to the starting symbol of each hop of the first PUSCH.

[0123] In this embodiment of the application, since the first symbol index can be determined based on at least one of whether the first PUSCH is enabled for frequency hopping and the PUSCH mapping type adopted by the first PUSCH, the flexibility in determining the first symbol index can be improved.

[0124] Optionally, in this embodiment of the application, the time unit for the application uplink silence can be the uplink silence time slot indicated by a bitmap.

[0125] It should be noted that the number of time slots contained in the bitmap above can be a period, meaning the number of time slots in the period is determined by the number of bits in the bitmap. This allows the terminal to periodically determine whether uplink silence should be applied within each time slot.

[0126] Optionally, in the embodiments of this application, the above-mentioned application uplink silent PUSCH can be DG PUSCH only, high priority PUSCH, PUSCH with symbol length meeting specific requirements, or PUSCH of non-random access procedure, etc.

[0127] The PUSCH of the random access procedure includes at least one of the following: PUSCH scheduled by RAR UL grant or fallback RAR UL grant, PUSCH scheduled by TC-RNTI, Msg A PUSCH, Msg 3 PUSCH, retransmission of Msg A PUSCH, and retransmission of Msg 3 PUSCH.

[0128] In this embodiment of the application, since the first information mentioned above may include at least one of 2.1 to 2.7, the terminal can receive information of different dimensions related to uplink silence, thereby flexibly performing uplink silence-related operations.

[0129] Step 402: Based on the first information, the terminal performs uplink silent related operations on the first PUSCH.

[0130] Optionally, in the embodiments of this application, the first PUSCH described above may satisfy at least one of the following 3.1 to 3.6:

[0131] 3.1 The symbol length meets specific conditions;

[0132] 3.2 The PUSCH demodulation reference signal mapping type used is the first mapping type;

[0133] 3.3 The transmission location overlaps with the SBFD symbol;

[0134] 3.4 The Radio Network Temporary Identity (RNTI) used is a specific RNTI;

[0135] 3.5. DCI scheduling or activated PUSCH for scrambling specific RNTIs;

[0136] 3.6, for CG PUSCH.

[0137] Optionally, in the embodiments of this application, the above-mentioned specific condition can be greater than or equal to a preset symbol length.

[0138] Optionally, in this embodiment of the application, the first mapping type can be PUSCH DMRS mapping type A.

[0139] Optionally, in the embodiments of this application, the specific RNTI mentioned above can be C-RNTI, MCS-RNTI or CS-RNTI.

[0140] Optionally, in this embodiment of the application, for PUSCH that does not satisfy at least one of 3.1 to 3.6 above, the first information is not applied and the uplink silence-related operation is not performed.

[0141] In this embodiment of the application, since the first PUSCH satisfies at least one of 3.1 to 3.4 above, uplink silencing related operations can be performed only on specific PUSCHs, thereby avoiding uplink silencing related operations on all PUSCHs. This can reduce the impact of uplink silencing, such as unreasonable TBS, excessive code rate, ambiguity between base station and UE, uplink resource utilization, etc.

[0142] Optionally, in this embodiment of the application, when the first information indicates that uplink silence is enabled, the terminal can enable uplink silence for the first PUSCH based on the first information.

[0143] Optionally, in this embodiment of the application, when the first information indicates that uplink muting should be disabled, the terminal can disable uplink muting for the first PUSCH based on the first information, that is, not perform uplink muting.

[0144] Optionally, in this embodiment of the application, when the first information is used to configure or indicate the uplink silence style, the terminal can determine the uplink silence style of the first PUSCH application based on the first information.

[0145] Optionally, in this embodiment of the application, when the first information is used to configure or indicate the conditions for uplink silence, the terminal can determine whether to enable uplink silence for the first PUSCH based on the uplink silence conditions configured or indicated by the first information.

[0146] Optionally, in this embodiment of the application, when the first information is used to configure or indicate the conditions for de-silencing uplink, the terminal can determine whether to de-silence uplink on the first PUSCH based on the conditions for de-silencing uplink configured or indicated by the first information.

[0147] In the uplink silence configuration method provided in this application, since the terminal can receive configuration information or indication information related to uplink silence from the network-side device, the terminal can perform uplink silence-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink silence, or on which resources to perform uplink silence, etc.). This provides a specific scheme for configuring, indicating, or enabling uplink silence and the application of uplink silence patterns, so that the terminal can perform uplink silence when transmitting PUSCH.

[0148] Optionally, in this embodiment, the first PUSCH may include any of the following: a PUSCH repeating in a repeating PUSCH, a PUSCH in a multi-PUSCH scheduling, or a PUSCH in a Transport Block over Multi-Slot (TBoMS). Exemplarily, prior to step 402 above, the uplink silent configuration method provided in this embodiment may further include step 403 below.

[0149] Step 403: Based on the second information, the terminal determines whether the first PUSCH applies uplink silence or an applied uplink silence style.

[0150] The second piece of information mentioned above includes at least one of the following:

[0151] The time unit type of the first PUSCH mentioned above, and the time domain resources of the first PUSCH configured or indicated by the first information mentioned above;

[0152] Conditions that enable uplink silence;

[0153] The TCI state or spatial relationship associated with the first PUSCH mentioned above;

[0154] The indication of the first DCI, wherein the first DCI is the scheduling DCI or activation DCI corresponding to the first PUSCH, the indication of the first DCI is used to indicate at least one of the following: whether to apply uplink silence to all PUSCHs or PUSCH repeats scheduled by the scheduling DCI, whether to apply uplink silence to all PUSCHs or PUSCH repeats activated by the activation DCI, the uplink silence style applied to all PUSCHs or PUSCH repeats scheduled by the scheduling DCI, the uplink silence style applied to all PUSCHs or PUSCH repeats activated by the activation DCI, the first PUSCH or PUSCH repeat to which uplink silence is applied, whether to apply uplink silence to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silence, and the uplink silence style applied to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silence.

[0155] Optionally, in this embodiment of the application, when the second information includes the time unit type of the first PUSCH and the time domain resource of the first PUSCH configured or indicated by the first information, the terminal can determine whether the first PUSCH should apply uplink silence based on whether the time unit of the first PUSCH overlaps with the time domain resource configured or indicated by the first information.

[0156] For example, if the time unit for applying uplink silence is configured by RRC (e.g., the time slot for applying uplink silence is periodically indicated by bitmap as mentioned above), then the terminal can determine the time unit for applying uplink silence and the time unit where each PUSCH repetition or PUSCH is located based on the uplink silence configuration, and thus determine whether the first PUSCH should apply uplink silence.

[0157] Optionally, in this embodiment, the condition for enabling uplink silence may be configured or indicated by the first information, or it may be predefined. Optionally, in this embodiment, when the second information includes the condition for enabling uplink silence, the terminal can determine whether the first PUSCH is enabled for uplink silence based on whether the first PUSCH meets the condition for enabling uplink silence.

[0158] For example, assuming that the condition for enabling uplink silence is that the length of each actual repeat and nominal repeat in the PUSCH is greater than or equal to L, the terminal can determine whether the length of each actual repeat and nominal repeat in the first PUSCH is greater than or equal to L; if the length of each actual repeat and nominal repeat in the first PUSCH is greater than or equal to L, then the terminal determines that the first PUSCH enables uplink silence; otherwise, the terminal determines that the first PUSCH does not enable uplink silence.

[0159] Optionally, in this embodiment of the application, when the second information includes the TCI status or spatial relationship associated with the first PUSCH, the terminal can determine whether the first PUSCH applies uplink silence or the applied uplink silence style based on the association between the TCI status or spatial relationship associated with the first PUSCH and uplink silence.

[0160] In this embodiment of the application, for cases of repeated PUSCH transmission (such as PUSCH configured or indicated to be repeated), multi-PUSCH scheduling (such as multi-PUSCH scheduling, i.e., one DCI schedules multiple PUSCH transmissions, and multiple PUSCHs are used to transmit different TBs) or TBoMS (i.e., TB over multiple slots, for example, one DCI schedules multiple PUSCHs to transmit in different time slots, and multiple PUSCHs are used to transmit one TB), the terminal can determine whether each PUSCH is repeated or whether each PUSCH applies uplink silence or the applied uplink silence style based on the above-mentioned second information. Therefore, uplink silence and the applied uplink silence style can be configured, indicated or enabled in different scenarios, thereby eliminating interference between base stations in different scenarios.

[0161] The uplink silent configuration method provided in the embodiments of this application will be described exemplarily below with reference to the accompanying drawings.

[0162] For example, Figure 5 illustrates the time-domain location configuration of the uplink demodulation reference signal (DMRS) symbols and uplink muting symbols (i.e., UL muting symbols) within a time slot (taking one PRB in the frequency domain as an example). As shown in Figure 5, the PUSCH mapping type is type A, and the UL DMRS are symbols 1 and 12 within the time slot (symbol 0 represents the first symbol within the time slot). The UL muting pattern time-domain location includes two symbols, symbol 2 and symbol 9.

[0163] In one implementation, the network-side device configures the UL muting pattern as follows: UL-muting-pattern{ UL-muting-patternID MutingpatternFre ENUMERATED{comb0,comb1} MutingpatternTime1 INTEGER(0..13) MutingpatternTime2 INTEGER(0..13)OPTIONAL}

[0164] The `MutingpatternFre` parameter configures the frequency domain position of the UL muting pattern, while `MutingpatternTime1` or `MutingpatternTime2` configures the time domain position. The time domain position must contain at least one symbol and at most two symbols; that is, `MutingpatternTime2` can be omitted. If the network-side device configures `MutingpatternTime2`, it indicates that the time domain contains two symbols, and the frequency domain position of the UL muting is the same in both symbols. For `MutingpatternTime1` or `MutingpatternTime2`, the value is an integer from 0 to 13, representing the time domain symbol position of the UL muting. It can be a symbol number relative to the start position of the time slot. In another implementation, `MutingpatternTime2` represents the number of symbols offset by the second silent symbol relative to the first silent symbol. For example, 2 represents the third symbol within the time slot. In this method, the time domain position (at least the first symbol position) in the silent mode is relative to the start position of the time slot. The advantage is that when the PUSCH DMRS symbol is relative to the start position of the time slot, it is convenient for network-side devices to avoid the UL muting symbol from overlapping with the UL DMRS or PTRS symbol through configuration.

[0165] Another approach is to use the time-domain symbol relative to the starting position of the scheduled PUSCH. The advantage of this approach is that when the PUSCH DMRS symbol is relative to the starting position of the scheduled PUSCH, it is easier for network-side devices to avoid the overlap between the UL muting symbol and the UL DMRS symbol through configuration.

[0166] Another approach is to use the starting position relative to each hop of the scheduled PUSCH. The advantage of this approach is that when frequency hopping is enabled on the PUSCH, it is easier for network-side devices to avoid overlap between UL muting symbols and UL DMRS symbols through configuration.

[0167] Of course, whether MutingpatternTime1 or MutingpatternTime2 represents the start position relative to the time slot, the start position of the scheduled PUSCH, or the start position of each hop of the scheduled PUSCH can be determined based on the PUSCH mapping type, whether PUSCH frequency hopping is enabled, or the symbol length of the PUSCH. For example, if the PUSCH uses PUSCH mapping type A, then when PUSCH frequency hopping is not enabled, it is relative to the start position relative to the time slot; if PUSCH frequency hopping is enabled, then it is relative to the start position of each PUSCH hop. If the PUSCH uses PUSCH mapping type B, then when PUSCH frequency hopping is not enabled, it is relative to the start position relative to the scheduled / configured PUSCH; if PUSCH frequency hopping is enabled, then it is relative to the start position of each PUSCH hop. Optionally, this PUSCH frequency hopping is intra-slot frequency hopping.

[0168] In related technologies, the DCI (Distributed Control Interface) for scheduling PUSCHs includes a TDRA (Time Domain Representation) field, used to indicate the temporal resource allocation for PUSCH scheduling. The TDRA field in the DCI indicates a row index in the RRC (Resource Control Code) configuration or protocol-predefined TDRA table. Each row in the network-side device configuration or protocol-predefined TDRA table can contain information such as K2 and SLIV mapping type. To dynamically enable or indicate the UL muting pattern, the TDRA table can be extended; for example, a new column can be added to the TDRA table to indicate whether UL muting is enabled or to indicate the corresponding UL muting pattern. It can be understood that if UL muting is not configured, it means that the UL muting in the corresponding TDRA row is disabled.

[0169] For example, the TDRA table can be configured with the following information, as shown in Table 1 below:

[0170] Table 1

[0171] Optionally, k2 (timing from DCI to PUSCH), mapping type, and SLIV (start symbol and symbol length) can be configured in IE PUSCH-TimeDomainResourceAllocation; or each row in the TDRA table configured in IE PUSCH-TimeDomainResourceAllocation-r16 can contain k2, mapping type, SLIV or start symbol and symbol length, repetition count, TBoMS slot number, extension k2, etc.; thus, without adding bit fields in DCI, the PUSCH can be dynamically indicated by scheduling the PUSCH to determine whether UL muting or UL muting style is enabled, thereby improving the flexibility of indication.

[0172] Optionally, the IE can be extended to configure whether UL muting and / or the corresponding muting pattern are enabled. For example, the base station configures at least one UL-muting-pattern according to the IE UL-muting-patternList in the example above. UL-muting-patternList::=SEQUENCE(1,maxNrof UL-muting-pattern)OF UL-muting-pattern.

[0173] In related technologies, network-side devices can configure or indicate the TCI state used for PUSCH transmission. For example, if a unified TCI state is configured, the network-side device can indicate the TCI state adopted by the UE in the DL DCI (e.g., the Transmission Configuration Indication field). For instance, after the DL DCI indication, the UE sends an ACK, and after a predefined delay, the PUCCH or PUSCH will adopt the TCI state indicated by that DCI. Alternatively, if a unified TCI state is not configured, the network-side device can indicate (e.g., the SRS resource indicator) in the DCI for scheduling PUSCH, such as DCI format 0_1 / 0_2, indicating which spatial relation the PUSCH uses.

[0174] Optionally, when configuring TCI state or spatial relation information, the network-side device configures the UL muting pattern associated with each TCI state or spatial relation information (such as UL muting enable, UL-muting-pattern1, UL-muting-pattern2, etc.). The terminal determines whether the UL muting corresponding to the PUSCH is enabled or the corresponding UL muting pattern based on the TCI state or spatial relation indicated or configured by the network-side device. Optionally, when the PUSCH is configured to use 'SDMscheme', two PUSCHs scheduled by a DCI can use different TCI states or spatial relations. In this case, the terminal expects the UL muting associated with these two TCI states or spatial relations to meet certain conditions, such as either both having UL muting enabled, or neither having UL muting enabled, or having the same UL muting pattern, or having the same number of time-domain muted symbols in the UL muting pattern, etc.

[0175] This application provides another uplink silence configuration method. Figure 6 shows a flowchart of the uplink silence configuration method provided in this application embodiment. As shown in Figure 6, the uplink silence configuration method provided in this application embodiment may include the following step 601.

[0176] Step 601: The network-side device sends the first information related to uplink silence to the terminal.

[0177] The first information mentioned above includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0178] Optionally, in this embodiment of the application, for a PUSCH that is rolled back to DCI scheduling or activated, or a CG PUSCH of type 1, the first information mentioned above may be configuration information configured through higher-layer signaling; or, for a PUSCH that is not rolled back to DCI scheduling or activated, the first information mentioned above may be indication information indicated by DCI.

[0179] Optionally, in this embodiment of the application, the first information mentioned above may be configuration information configured through higher-layer signaling.

[0180] The configuration information configured through higher-level signaling includes at least one type of uplink silence configuration information.

[0181] Optionally, in the embodiments of this application, the aforementioned first information can be used for at least one of the following:

[0182] Enables uplink silence;

[0183] To enable upward silence;

[0184] Configure the uplink silent style;

[0185] Indicates the uplink silent style;

[0186] Configure the conditions to enable uplink silence;

[0187] Indicates the conditions that enable uplink silence;

[0188] Configure the conditions to disable uplink silence;

[0189] Instructions to enable the conditions for uplink silence.

[0190] Optionally, in embodiments of this application, the aforementioned first information may include at least one of the following:

[0191] Upward silence style;

[0192] The frequency domain position corresponding to uplink silence;

[0193] The time domain position corresponding to uplink silence;

[0194] The period corresponding to the upward silence;

[0195] The offset value within the period corresponding to the uplink silence;

[0196] Apply the uplink silence time unit;

[0197] Apply uplink silent PUSCH.

[0198] Optionally, in this embodiment of the application, the time domain position corresponding to the above-mentioned uplink silence may include a first symbol index.

[0199] The first symbol index mentioned above includes any one of the following:

[0200] The symbol index relative to the starting position of the time unit in which the scheduled or activated PUSCH is located;

[0201] The symbolic index relative to the starting position of the scheduled or activated PUSCH;

[0202] The symbolic index relative to the starting position of each actual repetition of the scheduled or activated PUSCH;

[0203] The symbol index relative to the starting position of each nominal repetition of the scheduled or activated PUSCH;

[0204] The symbol index relative to the starting symbol of each hop of the scheduled or activated PUSCH;

[0205] The symbol index relative to the starting position of the time unit where the first PUSCH is located;

[0206] The symbol index relative to the starting position of the first PUSCH mentioned above;

[0207] The symbol index relative to the starting position of each actual repetition of the first PUSCH mentioned above;

[0208] The symbol index relative to the starting position of each nominal repetition of the first PUSCH mentioned above;

[0209] The symbol index relative to the starting symbol of each hop of the first PUSCH mentioned above.

[0210] Optionally, in the embodiments of this application, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0211] In the uplink muting configuration method provided in this application, since the network-side device can send configuration information or indication information related to uplink muting to the terminal, the terminal can perform uplink muting-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink muting, or on which resources to perform uplink muting, etc.). This provides a specific scheme for configuring, indicating, or enabling uplink muting and the application of uplink muting patterns, so that the terminal can perform uplink muting when transmitting PUSCH, enabling the network-side device to obtain the covariance matrix of the interference channel to eliminate interference between base stations.

[0212] The uplink silent configuration method provided in this application can be executed by an uplink silent configuration device. This application uses the example of an uplink silent configuration device executing the uplink silent configuration method to illustrate the uplink silent configuration device provided in this application.

[0213] This application provides an uplink silence configuration device. As an example, the uplink silence configuration device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0214] The uplink silent configuration device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0215] Specifically, referring to Figure 7, when the uplink silence configuration device is a terminal or a component in the terminal, the uplink silence configuration device 70 includes: a receiving module 71 and a processing module 72.

[0216] The receiving module 71 can be used to receive first information related to uplink muting from the network-side equipment. This first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI. The processing module 72 can be used to perform uplink muting-related operations on the first PUSCH based on this first information.

[0217] In one possible implementation, the aforementioned first information can be used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring uplink muting style; indicating uplink muting style; configuring the condition for enabling uplink muting; indicating the condition for enabling uplink muting; configuring the condition for disabling uplink muting; indicating the condition for disabling uplink muting.

[0218] In one possible implementation, the first information may include at least one of the following: uplink silence pattern; frequency domain position corresponding to uplink silence; time domain position corresponding to uplink silence; period corresponding to uplink silence; offset value within the period corresponding to uplink silence; time unit for applying uplink silence; PUSCH for applying uplink silence.

[0219] In one possible implementation, the time-domain position corresponding to the aforementioned uplink silence may include a first symbol index. This first symbol index includes any of the following: a symbol index relative to the start position of the time unit where the scheduled or activated PUSCH is located; a symbol index relative to the start position of the scheduled or activated PUSCH; a symbol index relative to the start position of each actual repetition of the scheduled or activated PUSCH; a symbol index relative to the start position of each nominal repetition of the scheduled or activated PUSCH; a symbol index relative to the start symbol of each hop of the scheduled or activated PUSCH; a symbol index relative to the start position of the time unit where the first PUSCH is located; a symbol index relative to the start position of the first PUSCH; a symbol index relative to the start position of each actual repetition of the first PUSCH; a symbol index relative to the start position of each nominal repetition of the first PUSCH; a symbol index relative to the start symbol of each hop of the first PUSCH.

[0220] In one possible implementation, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0221] In one possible implementation, the first PUSCH may satisfy at least one of the following: the symbol length meets a specific condition; the PUSCH demodulation reference signal is mapped to a first mapping type; the transmission location overlaps with the SBFD symbol; the RNTI used is a specific RNTI; the PUSCH is a DCI-scheduled or activated PUSCH scrambled for the specific RNTI; or it is a CG PUSCH.

[0222] In one possible implementation, the first PUSCH may include any of the following: a PUSCH repeat in a recurring PUSCH, a PUSCH in a multi-PUSCH scheduling, or a PUSCH in TBoMS. The processing module 72 can also be used to determine, based on second information, whether uplink silencing or the applied uplink silencing style applies to the first PUSCH. The second information includes at least one of the following: the time unit type of the first PUSCH, and the time domain resources of the first PUSCH configured or indicated by the first information; the conditions for enabling uplink silencing; the TCI status or spatial relationship associated with the first PUSCH; and an indication of a first DCI, wherein the first DCI is a scheduling DCI or an active DCI corresponding to the first PUSCH, and the indication of the first DCI is used to indicate at least one of the following: whether uplink silencing is applied to all PUSCHs or PUSCH repeats scheduled by the scheduling DCI, and whether uplink silencing is applied to the active DCI. Whether uplink silencing is applied to all active PUSCH or PUSCH repeats, the uplink silencing style applied to all PUSCH or PUSCH repeats scheduled by this DCI, the uplink silencing style applied to all PUSCH or PUSCH repeats activated by this active DCI, the first PUSCH or PUSCH repeat to apply uplink silencing, whether uplink silencing is applied to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silencing, and the uplink silencing style applied to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silencing.

[0223] In one possible implementation, for a PUSCH that is scheduled or activated by a rollback DCI, or a CG PUSCH of type 1, the first information may be configuration information configured by higher-layer signaling; or, for a PUSCH that is not scheduled or activated by a rollback DCI, the first information may be indication information indicated by DCI.

[0224] In one possible implementation, the aforementioned first information can be configuration information configured via higher-layer signaling. This configuration information includes at least one uplink silence configuration.

[0225] In the uplink silence configuration apparatus provided in this application embodiment, since the uplink silence configuration apparatus can receive configuration information or indication information related to uplink silence from the network-side device, it is possible to perform uplink silence-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink silence, or on which resources to perform uplink silence, etc.). Thus, a specific scheme for configuring, indicating, or enabling uplink silence and the application of uplink silence patterns is provided to facilitate uplink silence during PUSCH transmission.

[0226] The uplink silent configuration device provided in this application embodiment can implement all the processes implemented in the above terminal-side method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0227] Referring to Figure 8, when the uplink silence configuration device is a network-side device or a component in a network-side device, the uplink silence configuration device 80 includes: a transmission module 81.

[0228] The sending module 81 can be used to send first information related to uplink silence to the terminal. The first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0229] In one possible implementation, the aforementioned first information can be used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring uplink muting style; indicating uplink muting style; configuring the condition for enabling uplink muting; indicating the condition for enabling uplink muting; configuring the condition for disabling uplink muting; indicating the condition for disabling uplink muting.

[0230] In one possible implementation, the first information may include at least one of the following: uplink silence pattern; frequency domain position corresponding to uplink silence; time domain position corresponding to uplink silence; period corresponding to uplink silence; offset value within the period corresponding to uplink silence; time unit for applying uplink silence; PUSCH for applying uplink silence.

[0231] In one possible implementation, the time-domain position corresponding to the aforementioned uplink silence may include a first symbol index. This first symbol index includes any of the following: a symbol index relative to the start position of the time unit where the scheduled or activated PUSCH is located; a symbol index relative to the start position of the scheduled or activated PUSCH; a symbol index relative to the start position of each actual repetition of the scheduled or activated PUSCH; a symbol index relative to the start position of each nominal repetition of the scheduled or activated PUSCH; a symbol index relative to the start symbol of each hop of the scheduled or activated PUSCH; a symbol index relative to the start position of the time unit where the first PUSCH is located; a symbol index relative to the start position of the first PUSCH; a symbol index relative to the start position of each actual repetition of the first PUSCH; a symbol index relative to the start position of each nominal repetition of the first PUSCH; a symbol index relative to the start symbol of each hop of the first PUSCH.

[0232] In one possible implementation, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0233] In one possible implementation, for a PUSCH that is scheduled or activated by a rollback DCI, or a CG PUSCH of type 1, the first information may be configuration information configured by higher-layer signaling; or, for a PUSCH that is not scheduled or activated by a rollback DCI, the first information may be indication information indicated by DCI.

[0234] In one possible implementation, the aforementioned first information can be configuration information configured via higher-layer signaling. This configuration information includes at least one uplink silence configuration.

[0235] In the uplink silence configuration apparatus provided in this application embodiment, since the uplink silence configuration apparatus can send configuration information or indication information related to uplink silence to the terminal, the terminal can perform uplink silence-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink silence, or on which resources to perform uplink silence, etc.). This provides a specific scheme for configuring, indicating, or enabling uplink silence and the application of uplink silence patterns, so that the terminal can perform uplink silence when transmitting PUSCH, enabling the network-side equipment to obtain the covariance matrix of the interference channel to eliminate interference between base stations.

[0236] The uplink silent configuration device provided in this application embodiment can implement all the processes implemented in the above network-side device method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0237] As shown in Figure 9, this application embodiment also provides a communication device 100, including a processor 101 and a memory 102. The memory 102 stores programs or instructions that can run on the processor 101. For example, when the communication device 100 is a terminal, the program or instructions executed by the processor 101 implement the various steps of the above-described terminal-side method embodiment and achieve the same technical effect. When the communication device 100 is a network-side device, the program or instructions executed by the processor 101 implement the various steps of the above-described network-side device method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0238] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the above-described terminal-side method embodiments. This terminal embodiment corresponds to the above-described terminal-side method embodiments; all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effects. The terminal can be the uplink silent configuration device shown in Figure 7. Specifically, Figure 10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0239] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0240] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 10 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0241] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0242] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0243] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0244] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 1010.

[0245] The radio frequency unit 1001 can be used to receive first information related to uplink silence from the network-side equipment. The first information is at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured by higher-layer signaling, and indication information indicated by DCI.

[0246] The processor 1010 can be used to perform uplink silencing related operations on the first PUSCH based on the first information.

[0247] In one possible implementation, the aforementioned first information can be used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring uplink muting style; indicating uplink muting style; configuring the condition for enabling uplink muting; indicating the condition for enabling uplink muting; configuring the condition for disabling uplink muting; indicating the condition for disabling uplink muting.

[0248] In one possible implementation, the first information may include at least one of the following: uplink silence pattern; frequency domain position corresponding to uplink silence; time domain position corresponding to uplink silence; period corresponding to uplink silence; offset value within the period corresponding to uplink silence; time unit for applying uplink silence; PUSCH for applying uplink silence.

[0249] In one possible implementation, the time-domain position corresponding to the aforementioned uplink silence may include a first symbol index. This first symbol index includes any of the following: a symbol index relative to the start position of the time unit where the scheduled or activated PUSCH is located; a symbol index relative to the start position of the scheduled or activated PUSCH; a symbol index relative to the start position of each actual repetition of the scheduled or activated PUSCH; a symbol index relative to the start position of each nominal repetition of the scheduled or activated PUSCH; a symbol index relative to the start symbol of each hop of the scheduled or activated PUSCH; a symbol index relative to the start position of the time unit where the first PUSCH is located; a symbol index relative to the start position of the first PUSCH; a symbol index relative to the start position of each actual repetition of the first PUSCH; a symbol index relative to the start position of each nominal repetition of the first PUSCH; a symbol index relative to the start symbol of each hop of the first PUSCH.

[0250] In one possible implementation, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0251] In one possible implementation, the first PUSCH may satisfy at least one of the following: the symbol length meets a specific condition; the PUSCH demodulation reference signal is mapped to a first mapping type; the transmission location overlaps with the SBFD symbol; the RNTI used is a specific RNTI; the PUSCH is a DCI-scheduled or activated PUSCH scrambled for the specific RNTI; or it is a CG PUSCH.

[0252] In one possible implementation, the first PUSCH may include any of the following: a PUSCH repeat in a recurring PUSCH, a PUSCH in a multi-PUSCH scheduling, or a PUSCH in TBoMS. The processor 1010 can also be used to determine, based on second information, whether uplink silencing or the applied uplink silencing style is applied to the first PUSCH. The second information includes at least one of the following: the time unit type of the first PUSCH, and the time domain resources of the first PUSCH configured or indicated by the first information; the conditions for enabling uplink silencing; the TCI status or spatial relationship associated with the first PUSCH; and an indication of a first DCI, wherein the first DCI is a scheduling DCI or an active DCI corresponding to the first PUSCH, and the indication of the first DCI is used to indicate at least one of the following: whether uplink silencing is applied to all PUSCHs or PUSCH repeats scheduled by the scheduling DCI, and whether uplink silencing is applied to the active DCI. Whether uplink silencing is applied to all active PUSCH or PUSCH repeats, the uplink silencing style applied to all PUSCH or PUSCH repeats scheduled by this DCI, the uplink silencing style applied to all PUSCH or PUSCH repeats activated by this active DCI, the first PUSCH or PUSCH repeat to apply uplink silencing, whether uplink silencing is applied to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silencing, and the uplink silencing style applied to the first PUSCH or PUSCH repeat that meets the conditions for enabling uplink silencing.

[0253] In one possible implementation, for a PUSCH that is scheduled or activated by a rollback DCI, or a CG PUSCH of type 1, the first information may be configuration information configured by higher-layer signaling; or, for a PUSCH that is not scheduled or activated by a rollback DCI, the first information may be indication information indicated by DCI.

[0254] In one possible implementation, the aforementioned first information can be configuration information configured via higher-layer signaling. This configuration information includes at least one uplink silence configuration.

[0255] In the terminal provided in this application embodiment, since the terminal can receive configuration information or indication information related to uplink silencing from the network-side device, it is possible to perform uplink silencing-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink silencing, or on which resources to perform uplink silencing, etc.). Thus, a specific scheme for configuring, indicating, or enabling uplink silencing and the application of uplink silencing patterns is provided to facilitate uplink silencing during PUSCH transmission.

[0256] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above terminal side method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0257] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the above-described network-side device method embodiments. This network-side device embodiment corresponds to the above-described network-side device method embodiments. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0258] Specifically, this application embodiment also provides a network-side device, which can be the uplink silent configuration device shown in FIG8. As shown in FIG11, the network-side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the radio frequency device 112. The radio frequency device 112 processes the received information and transmits it through the antenna 111.

[0259] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 113, which includes a baseband processor.

[0260] The baseband device 113 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 115 via a bus interface to call the program in the memory 115 and execute the network device operation shown in the above method embodiment.

[0261] The network-side device may also include a network interface 116, such as a Common Public Radio Interface (CPRI).

[0262] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 115 and executable on processor 114. The processor 114 calls the instructions or programs in memory 115 to execute the method executed by the network-side device and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0263] The radio frequency device 112 can be used to send first information related to uplink silence to the terminal. The first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured via higher-layer signaling, and indication information indicated by DCI.

[0264] In one possible implementation, the aforementioned first information can be used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring uplink muting style; indicating uplink muting style; configuring the condition for enabling uplink muting; indicating the condition for enabling uplink muting; configuring the condition for disabling uplink muting; indicating the condition for disabling uplink muting.

[0265] In one possible implementation, the first information may include at least one of the following: uplink silence pattern; frequency domain position corresponding to uplink silence; time domain position corresponding to uplink silence; period corresponding to uplink silence; offset value within the period corresponding to uplink silence; time unit for applying uplink silence; PUSCH for applying uplink silence.

[0266] In one possible implementation, the time-domain position corresponding to the aforementioned uplink silence may include a first symbol index. This first symbol index includes any of the following: a symbol index relative to the start position of the time unit where the scheduled or activated PUSCH is located; a symbol index relative to the start position of the scheduled or activated PUSCH; a symbol index relative to the start position of each actual repetition of the scheduled or activated PUSCH; a symbol index relative to the start position of each nominal repetition of the scheduled or activated PUSCH; a symbol index relative to the start symbol of each hop of the scheduled or activated PUSCH; a symbol index relative to the start position of the time unit where the first PUSCH is located; a symbol index relative to the start position of the first PUSCH; a symbol index relative to the start position of each actual repetition of the first PUSCH; a symbol index relative to the start position of each nominal repetition of the first PUSCH; a symbol index relative to the start symbol of each hop of the first PUSCH.

[0267] In one possible implementation, the first symbol index may be determined based on at least one of the following: whether the first PUSCH is enabled for frequency hopping, the PUSCH mapping type used by the first PUSCH, whether the scheduled or activated PUSCH is enabled for frequency hopping, and the PUSCH mapping type used by the scheduled or activated PUSCH.

[0268] In one possible implementation, for a PUSCH that is scheduled or activated by a rollback DCI, or a CG PUSCH of type 1, the first information may be configuration information configured by higher-layer signaling; or, for a PUSCH that is not scheduled or activated by a rollback DCI, the first information may be indication information indicated by DCI.

[0269] In one possible implementation, the aforementioned first information can be configuration information configured via higher-layer signaling. This configuration information includes at least one uplink silence configuration.

[0270] In the network-side device provided in this application embodiment, since the network-side device can send configuration information or indication information related to uplink silencing to the terminal, the terminal can perform uplink silencing-related operations on the transmitted PUSCH based on the configuration information or indication information (e.g., whether to perform uplink silencing, or on which resources to perform uplink silencing, etc.). This provides a specific scheme for configuring, indicating, or enabling uplink silencing and the application of uplink silencing patterns, so that the terminal can perform uplink silencing when transmitting PUSCH, enabling the network-side device to obtain the covariance matrix of the interference channel to eliminate interference between base stations.

[0271] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above network-side device method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0272] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described uplink silent configuration method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0273] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0274] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described uplink silent configuration method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0275] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0276] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described uplink silent configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0277] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal-side method as described above, and the network-side device can be used to perform the steps of the network-side device method as described above.

[0278] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0279] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0280] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

A method for uplink muting configuration, the method comprising: a terminal receiving first information related to uplink muting from a network side device, the first information being at least one of: configuration information configured for each serving cell, configuration information configured for each bandwidth part (BWP), configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for dynamic grant (DG) physical uplink shared channel (PUSCH) and configured grant (CG) PUSCH respectively, configuration information configured through higher layer signaling, and indication information indicated through downlink control information (DCI); the terminal performing an uplink muting related operation on a first PUSCH based on the first information. The method of claim 1, wherein, the first information is used for at least one of: enabling uplink muting; disabling uplink muting; configuring an uplink muting pattern; indicating an uplink muting pattern; configuring a condition for enabling uplink muting; indicating a condition for enabling uplink muting; configuring a condition for disabling uplink muting; indicating a condition for disabling uplink muting. The method according to claim 1 or 2, wherein the first information comprises at least one of: an uplink muting pattern; a frequency domain position corresponding to uplink muting; a time domain position corresponding to uplink muting; a period corresponding to uplink muting; an offset value within a period corresponding to uplink muting; a time unit for applying uplink muting; a PUSCH for applying uplink muting. The method of claim 3, wherein, the time domain position comprises a first symbol index; wherein the first symbol index comprises any one of: a symbol index relative to a starting position of a time unit where a scheduled or activated PUSCH is located; a symbol index relative to a starting position of the first PUSCH; a symbol index relative to a starting position of each actual repetition of the first PUSCH; a symbol index relative to a starting position of each nominal repetition of the first PUSCH; a symbol index relative to a starting symbol of each hop of the first PUSCH; a symbol index relative to a starting position of a time unit where the first PUSCH is located; a symbol index relative to a starting position of the first PUSCH; a symbol index relative to a starting position of each actual repetition of the first PUSCH; a symbol index relative to a starting position of each nominal repetition of the first PUSCH; a symbol index relative to a starting symbol of each hop of the first PUSCH. The method of claim 4, wherein, the first symbol index is determined according to at least one of: whether the first PUSCH is enabled with frequency hopping, a PUSCH mapping type adopted by the first PUSCH, whether a scheduled or activated PUSCH is enabled with frequency hopping, a PUSCH mapping type adopted by the scheduled or activated PUSCH. The method of any one of claims 1 to 5, wherein, the first PUSCH satisfies at least one of: a symbol length satisfying a specific condition; adopting a first mapping type for PUSCH demodulation reference signal mapping; a transmission position overlapping with a sub-band full duplex (SBFD) symbol; adopting a specific radio network temporary identifier (RNTI); a DCI scrambled for a specific RNTI scheduling or activating a PUSCH; being a CG PUSCH. The method of any one of claims 1 to 6, wherein, The first PUSCH comprises any one of the following: one PUSCH repetition in repeated transmission, one PUSCH in multi-PUSCH scheduling, one PUSCH in multi-slot bundled transport block (TBoMS); the method further comprises: The terminal determines, based on the second information, whether the first PUSCH applies uplink muting or an uplink muting pattern applied; The second information comprises at least one of the following: The time unit type in which the first PUSCH is located, and the time domain resource of the first PUSCH configured or indicated by the first information; A condition for enabling uplink muting; A transmission configuration indication (TCI) state or spatial relation associated with the first PUSCH; An indication of the first DCI, wherein the first DCI is a scheduling DCI or an activation DCI corresponding to the first PUSCH, and the indication of the first DCI indicates at least one of the following: whether uplink muting is applied to all PUSCHs or PUSCH repetitions scheduled by the scheduling DCI, whether uplink muting is applied to all PUSCHs or PUSCH repetitions activated by the activation DCI, an uplink muting pattern applied to all PUSCHs or PUSCH repetitions scheduled by the scheduling DCI, an uplink muting pattern applied to all PUSCHs or PUSCH repetitions activated by the activation DCI, a first PUSCH or PUSCH repetition to which uplink muting is applied, whether uplink muting is applied to a first PUSCH or PUSCH repetition that meets the condition for enabling uplink muting, or an uplink muting pattern applied to a first PUSCH or PUSCH repetition that meets the condition for enabling uplink muting. The method of any one of claims 1 to 7, wherein, For PUSCHs scheduled or activated by fallback DCI or type 1 CG PUSCH, the first information is configuration information configured by higher layer signaling; or for PUSCHs not scheduled or activated by fallback DCI, the first information is indication information indicated by DCI. The method of any one of claims 1 to 8, wherein, The first information is configuration information configured by higher layer signaling. The configuration information configured by higher layer signaling comprises at least one of the following uplink muting configuration information. An uplink muting configuration method, the method comprising: A network-side device sends first information related to uplink muting to a terminal; The first information comprises at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured by higher layer signaling, and indication information indicated by DCI. The method of claim 10, wherein, The first information is used for at least one of the following: Enabling uplink muting; Disabling uplink muting; Configuring an uplink muting pattern; Indicating an uplink muting pattern; Configuring a condition for enabling uplink muting; Indicating a condition for enabling uplink muting; Configuring a condition for disabling uplink muting; Indicating a condition for disabling uplink muting. The method according to claim 10 or 11, wherein The first information comprises at least one of the following: An uplink muting pattern; A frequency domain position corresponding to uplink muting; a time domain position corresponding to the uplink muting; a period corresponding to the uplink muting; an offset value in the period corresponding to the uplink muting; a time unit in which the uplink muting is applied; a PUSCH in which the uplink muting is applied. The method of claim 12, wherein, The time domain position includes a first symbol index. The first symbol index includes any of the following: a symbol index relative to a starting position of a time unit in which a scheduled or activated PUSCH is located; a symbol index relative to a starting position of the scheduled or activated PUSCH; a symbol index relative to a starting position of each actual repetition of the scheduled or activated PUSCH; a symbol index relative to a starting position of each nominal repetition of the scheduled or activated PUSCH; a symbol index relative to a starting symbol of each hop of the scheduled or activated PUSCH; a symbol index relative to a starting position of a time unit in which the first PUSCH is located; a symbol index relative to a starting position of the first PUSCH; a symbol index relative to a starting position of each actual repetition of the first PUSCH; a symbol index relative to a starting position of each nominal repetition of the first PUSCH; a symbol index relative to a starting symbol of each hop of the first PUSCH. The method of claim 13, wherein, The first symbol index is determined according to at least one of the following: whether the first PUSCH is enabled to perform frequency hopping, a PUSCH mapping type adopted by the first PUSCH, whether a scheduled or activated PUSCH is enabled to perform frequency hopping, a PUSCH mapping type adopted by the scheduled or activated PUSCH. The method of any one of claims 10 to 14, wherein, For a PUSCH scheduled or activated by fallback DCI or a CG PUSCH of type 1, the first information is configuration information configured through higher layer signaling; or for a PUSCH not scheduled or activated by fallback DCI, the first information is indication information indicated through DCI. The method of any one of claims 10 to 15, wherein, The first information is configuration information configured through higher layer signaling. The configuration information configured through higher layer signaling includes at least one of the following configuration information of uplink muting. An uplink muting configuration apparatus, the apparatus comprising: a receiving module and a processing module; The receiving module is configured to receive, from a network side device, first information related to uplink muting, the first information being at least one of the following: configuration information configured for each service cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured through higher layer signaling, and indication information indicated through DCI. The processing module is configured to perform, based on the first information, an operation related to uplink muting on a first PUSCH. The apparatus of claim 17, wherein The first information is used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring a pattern of uplink muting; indicating a pattern of uplink muting; configuring a condition for enabling uplink muting; indicating a condition for enabling uplink muting; configuring a condition for disabling uplink muting; indicating a condition for disabling uplink muting. The apparatus of claim 17 or 18, wherein The first information includes at least one of the following: a pattern of uplink muting; a frequency domain position corresponding to the uplink muting; a time domain position corresponding to the uplink muting; a period corresponding to the uplink muting; An offset value in a period corresponding to the uplink muting; A time unit in which the uplink muting is applied; A PUSCH to which the uplink muting is applied. The apparatus of any one of claims 17 to 19, wherein The first PUSCH satisfies at least one of the following conditions: A symbol length satisfying a specific condition; A PUSCH demodulation reference signal mapping adopted as a first mapping type; A transmission position overlapping with an SBFD symbol; An RNTI adopted as a specific RNTI; A PUSCH scheduled or activated by DCI scrambled for the specific RNTI; A CG PUSCH. The apparatus of any one of claims 17 to 20, wherein The first PUSCH includes any of the following: one of PUSCH repetitions in repeated transmission, one of multiple PUSCHs scheduled, one of TBoMSs; The processing module is further configured to determine, based on second information, whether the first PUSCH applies uplink muting or an uplink muting pattern applied to the first PUSCH; The second information includes at least one of the following: A time unit type in which the first PUSCH is located, and time domain resources of the first PUSCH configured or indicated by the first information; A condition for enabling uplink muting; A TCI state or spatial relation associated with the first PUSCH; An indication of a first DCI, wherein the first DCI is a scheduling DCI or an activation DCI corresponding to the first PUSCH, and the indication of the first DCI indicates at least one of the following: whether all PUSCHs or PUSCH repetitions scheduled by the scheduling DCI apply uplink muting, whether all PUSCHs or PUSCH repetitions activated by the activation DCI apply uplink muting, an uplink muting pattern applied to all PUSCHs or PUSCH repetitions scheduled by the scheduling DCI, an uplink muting pattern applied to all PUSCHs or PUSCH repetitions activated by the activation DCI, a first PUSCH or PUSCH repetition to which uplink muting is applied, whether a first PUSCH or PUSCH repetition satisfying the condition for enabling uplink muting applies uplink muting, or an uplink muting pattern applied to the first PUSCH or PUSCH repetition satisfying the condition for enabling uplink muting. The apparatus of any one of claims 17 to 21, wherein For a PUSCH scheduled or activated by a fallback DCI or a CG PUSCH of type 1, the first information is configuration information configured by higher layer signaling; or for a PUSCH scheduled or activated by a non-fallback DCI, the first information is indication information indicated by DCI. The apparatus of any one of claims 17 to 22, wherein The first information is configuration information configured by higher layer signaling. The configuration information configured by higher layer signaling includes at least one of the following pieces of uplink muting configuration information. An uplink muting configuration apparatus, the apparatus comprising: A sending module; The sending module is configured to send first information related to uplink muting to a terminal. The first information includes at least one of the following: configuration information configured for each serving cell, configuration information configured for each BWP, configuration information configured for each waveform, configuration information configured for each beam, configuration information configured for DG PUSCH and CG PUSCH respectively, configuration information configured by higher layer signaling, or indication information indicated by DCI. The apparatus of claim 24, wherein The first information is used for at least one of the following: enabling uplink muting; disabling uplink muting; configuring an uplink muting pattern; indicating an uplink muting pattern; configuring a condition for enabling uplink muting; indicating a condition for enabling uplink muting; configuring a condition for disabling uplink muting; indicating a condition for disabling uplink muting. The apparatus of claim 24 or 25, wherein, The first information includes at least one of the following: an uplink muting pattern; a frequency domain position corresponding to uplink muting; a time domain position corresponding to uplink muting; a period corresponding to uplink muting; an offset value within a period corresponding to uplink muting; a time unit for applying uplink muting; a PUSCH for applying uplink muting. The apparatus of any one of claims 24 to 26, wherein For a PUSCH scheduled or activated by fallback DCI or a CG PUSCH of type 1, the first information is configuration information configured by high layer signaling; or for a PUSCH not scheduled or activated by fallback DCI, the first information is indication information indicated by DCI. The apparatus of any one of claims 24 to 27, wherein The first information is configuration information configured by high layer signaling. The configuration information configured by high layer signaling includes at least one of the following configuration information of uplink muting. A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the uplink muting configuration method according to any one of claims 1 to 9. A network side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the uplink muting configuration method according to any one of claims 10 to 16. A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions being executed by a processor to implement the uplink muting configuration method according to any one of claims 1 to 9, or to implement the steps of the uplink muting configuration method according to any one of claims 10 to 16. A computer program product, the computer program product being executed by at least one processor to implement the steps of the uplink muting configuration method according to any one of claims 1 to 9, or to implement the steps of the uplink muting configuration method according to any one of claims 10 to 16. An electronic device, the electronic device being configured to implement the steps of the uplink muting configuration method according to any one of claims 1 to 9, or to implement the steps of the uplink muting configuration method according to any one of claims 10 to 16. A chip, the chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to run programs or instructions to implement the steps of the uplink muting configuration method according to any one of claims 1 to 9, or to implement the steps of the uplink muting configuration method according to any one of claims 10 to 16.

Images