Uplink muting method and apparatus

Abstract

An uplink muting method and apparatus, which are applied to the technical field of communications. The method comprises: receiving first configuration information and second configuration information from a network device, wherein the first configuration information is used for configuring one or more time-domain resource assignment (TDRA) tables, and the second configuration information is used for configuring an uplink muting resource; receiving first signaling from the network device, wherein the first signaling is used for configuring or activating or scheduling the transmission of an uplink physical shared channel (PUSCH); and when there is no uplink muting enable / disable indication in a TDRA table associated with the PUSCH, not muting the transmission of the PUSCH on the uplink muting resource. On the basis of the method, when there is no uplink muting enable / disable indication in a TDRA table in use, a terminal can rationally determine whether to enable uplink muting on an uplink muting resource, thereby reducing the impact on the uplink data transmission performance.

Description

An uplink silencing method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202510127973.X, filed on January 27, 2025, entitled "An Uplink Silencing Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to an uplink silencing method and apparatus. Background Technology

[0003] In dynamic time division duplex (TDD) or subband full duplex (SBFD) systems, base station-to-base station interference (BS-to-BS interference) can occur. For example, as shown in Figure 1, in a dynamic TDD system, downlink signals transmitted by base station 1 in time slot 2 can affect uplink reception by base station 2 in time slot 2. Similarly, as shown in Figure 2, in an SBFD system, downlink signals transmitted by base station 1 in subband 1 of time slot 2 can leak into subband 2, affecting reception by base station 2 in subband 2 of time slot 2. To address BS-to-base station interference, the standard is discussing uplink resource muting, which involves not transmitting uplink data on certain uplink resources. This allows base stations to perform interference measurements on these non-transmitting uplink resources, resulting in more accurate interference measurements, which can then be canceled during reception. Network devices can indicate uplink silencing resources to terminals through semi-static configuration and enable or disable uplink silencing by indicating the uplink silencing on / off switch in the time domain resource assignment (TDRA) table using downlink control information (DCI). However, when the TDRA table in use does not contain an uplink silencing on / off switch indicator, how the terminal can reasonably determine whether to enable uplink silencing on uplink silencing resources is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides an uplink muting method and apparatus, which helps the terminal to reasonably determine whether to enable uplink muting on uplink muting resources when there is no uplink muting switch indication in the TDRA form used.

[0005] In a first aspect, embodiments of this application provide an uplink silencing method, the method comprising: receiving first configuration information and second configuration information from a network device, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information being used to configure uplink silencing resources; receiving first signaling from the network device, the first signaling being used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission; and silencing or not silencing PUSCH transmission on uplink silencing resources when there is no uplink silencing switch indication in the TDRA table associated with the PUSCH.

[0006] Based on the method described in the first aspect, when there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal defaults to silencing PUSCH transmission on uplink silence resources. This allows network devices more opportunities to measure mutual interference, and multiple measurements help network devices obtain more accurate interference information, thereby improving communication performance. Furthermore, by defaulting to silencing PUSCH transmission on uplink silence resources, additional signaling overhead is saved. Conversely, when there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal defaults to not silencing PUSCH transmission on uplink silence resources. This helps reduce the impact on uplink data transmission performance. Furthermore, by defaulting to not silencing PUSCH transmission on uplink silence resources, additional signaling overhead is saved. Therefore, based on the method described in the first aspect, when there is no uplink silence switch indication in the used TDRA table, it is beneficial for the terminal to reasonably determine whether to enable uplink silence on uplink silence resources.

[0007] In one possible embodiment, PUSCH is a configuration-authorized PUSCH; if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource.

[0008] In other words, regardless of whether there is an uplink silence switch indication in the TDRA table associated with PUSCH, the terminal defaults to either silencing or not silencing PUSCH transmission on uplink silenced resources; that is, the terminal always ignores the uplink silence switch indication in the TDRA table associated with PUSCH. Defaulting to silencing PUSCH transmission allows network devices more opportunities to measure mutual interference. Multiple measurements help network devices obtain more accurate interference information, thereby improving communication performance. Defaulting to not silencing PUSCH transmission helps reduce the impact on uplink data transmission performance. Furthermore, by defaulting to silencing or not silencing PUSCH transmission on uplink silenced resources, additional signaling overhead is saved.

[0009] Secondly, embodiments of this application provide an uplink silencing method, the method comprising: receiving first configuration information and second configuration information from a network device, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, the second configuration information being used to configure uplink silencing resources; the second configuration information further comprising an uplink silencing switch indication at the Radio Resource Control (RRC) level; receiving first signaling from the network device, the first signaling being used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission; and, if there is no uplink silencing switch indication in the TDRA table associated with the PUSCH, silencing or not silencing PUSCH transmission on the uplink silencing resources based on the switch indication in the second configuration information.

[0010] Based on the method described in the second aspect, network devices can flexibly configure uplink silence on / off indicators at the RRC level according to communication requirements. Thus, even when there is no uplink silence on / off indicator in the TDRA table associated with the PUSCH, the terminal can flexibly determine whether to silence PUSCH transmission on uplink silence resources based on the RRC-level uplink silence on / off indicator, which is beneficial for meeting actual communication needs. Therefore, based on the method described in the second aspect, when there is no uplink silence on / off indicator in the used TDRA table, it is beneficial for the terminal to reasonably determine whether to enable uplink silence on uplink silence resources.

[0011] In conjunction with the method described in the second aspect, in one possible embodiment, the PUSCH is a configured authorized PUSCH; if there is an uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information.

[0012] In other words, regardless of whether an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal always silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information. That is, the terminal always ignores the uplink silence switch indication in the TDRA table associated with the PUSCH. Thus, even when an uplink silence switch indication exists in the second configuration information, for CG PUSCH, the terminal can disregard the presence of an uplink silence switch in the TDRA table and determine whether to silence or not transmit the PUSCH on uplink silence resources solely based on the uplink silence switch indication in the second configuration information, simplifying the terminal's implementation complexity. Simultaneously, it ensures that network devices use the uplink silence switch indication in the second configuration information to indicate whether to perform uplink silence, which is beneficial for ensuring the flexible use of the uplink silence mechanism and meeting actual communication needs.

[0013] In conjunction with the method described in the second aspect, in one possible embodiment, if the second configuration information does not include an uplink silencing switch indication at the RRC level, the transmission of PUSCH on uplink silencing resources may be silenced or not silenced. Based on this possible embodiment, even if the network device does not add an uplink silencing switch indication to the second configuration information, the terminal can reasonably determine whether to silence the transmission of PUSCH on uplink silencing resources.

[0014] In conjunction with the method described in the first or second aspect, in one possible embodiment, if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

[0015] In other words, when using the method described in the first aspect, the terminal prioritizes the uplink silence switch indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence switch indication in the TDRA table associated with the PUSCH will the terminal default to not silencing or silencing the PUSCH transmission on the uplink silence resource. By prioritizing the uplink silence switch indication in the TDRA table associated with the PUSCH, the network device's initiative in enabling or disabling uplink silence is ensured.

[0016] In other words, when using the method described in the second aspect, the terminal prioritizes the uplink silence switch indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence switch indication in the TDRA table associated with the PUSCH will the PUSCH transmission be silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information. This allows for flexible enabling or disabling of uplink silence based on a combination of various signaling methods.

[0017] In conjunction with the method described in the second aspect, in one possible embodiment, if the second configuration information does not include an uplink silence switch indication at the RRC level, and the uplink silence switch indication does not exist in the TDRA table associated with the PUSCH, then the transmission of PUSCH may be silenced or not silenced on the uplink silence resource. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication to the second configuration information, the terminal can reasonably determine whether to silence the transmission of PUSCH on the uplink silence resource.

[0018] In conjunction with the methods described in the first or second aspect, in one possible embodiment, at least one of the one or more TDRA tables includes an uplink silence switch indication. Based on this possible embodiment, this facilitates network devices using DCI signaling to dynamically indicate whether to perform uplink silence, which helps ensure the flexible use of the uplink silence mechanism.

[0019] In conjunction with the methods described in the first or second aspect, in one possible embodiment, the first signaling is a downlink control information (DCI) for activating or scheduling PUSCH transmission, and the first signaling is a second type of DCI; wherein, the PUSCH scheduled or activated by the first type of DCI is never silently transmitted on the uplink silent resource. Based on this possible embodiment, different types of DCI can correspond to different uplink silent enabling or disabling schemes, allowing network devices to flexibly enable or disable uplink silent through combinations of various signaling.

[0020] In conjunction with the methods described in the first or second aspect, in one possible embodiment, the type of DCI for the scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides. Based on this possible embodiment, the type of DCI does not need to be indicated through additional signaling, which helps to save signaling overhead.

[0021] Thirdly, embodiments of this application provide an uplink silencing method, the method comprising: receiving first configuration information and second configuration information from a network device, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, the second configuration information being used to configure uplink silencing resources; receiving first signaling from the network device, the first signaling being used to configure uplink Physical Shared Channel (PUSCH) transmission; the PUSCH being a configured authorized PUSCH; and, if the first signaling includes an uplink silencing switch indication, and there is no uplink silencing switch indication in the TDRA table associated with the PUSCH, silencing or not silencing the transmission of the PUSCH on the uplink silencing resources based on the switch indication in the first signaling.

[0022] Based on the method described in the third aspect, network devices can flexibly configure whether the terminal silences PUSCH transmission on uplink silence resources in the first signaling according to communication requirements. Thus, even when there is no uplink silence on / off indication in the TDRA table associated with PUSCH, the terminal can flexibly determine whether to silence PUSCH transmission on uplink silence resources based on the uplink silence on / off indication in the first signaling, which is more conducive to meeting actual communication needs. Therefore, based on the method described in the first aspect, when there is no uplink silence on / off indication in the used TDRA table, it is beneficial for the terminal to reasonably determine whether to enable uplink silence on uplink silence resources.

[0023] In one possible embodiment, if the first signaling includes an uplink silence switch indication, and an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the PUSCH transmission is either silenced or not silenced on the uplink silence resource based on the switch indication in the first signaling. That is, if the first signaling includes an uplink silence switch indication, regardless of whether an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal always silences or does not silence the PUSCH transmission on the uplink silence resource based on the switch indication in the first signaling, and the terminal always ignores the uplink silence switch indication in the TDRA table associated with the PUSCH. In this way, when an uplink silence switch indication exists in the first signaling, for CG PUSCH, the terminal can disregard whether an uplink silence switch exists in the TDRA table and determine whether to silence or not silence PUSCH transmission on uplink silence resources based solely on the uplink silence switch indication in the first signaling, simplifying the implementation complexity of the terminal. At the same time, it can ensure that network devices indicate whether to perform uplink silence through the uplink silence switch indication in the first signaling, which is conducive to ensuring the flexible use of the uplink silence mechanism and meeting actual communication needs.

[0024] In one possible embodiment, transmission of PUSCH is muted or not muted on the uplink muted resource if the uplink muting switch indication is not included in the first signaling.

[0025] In one possible implementation, if an uplink silencing switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is either silenced or not silenced on the uplink silencing resource based on the switch indication in the TDRA table associated with the PUSCH. This allows for flexible enabling or disabling of uplink silencing based on a combination of various signaling methods.

[0026] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, and the uplink silence switch indication is not present in the TDRA table associated with the PUSCH, then the transmission of PUSCH may be silenced or not silenced on the uplink silence resource. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication in the first signaling, the terminal can determine whether to silence the transmission of PUSCH on the uplink silence resource.

[0027] In one possible embodiment, the second configuration information also includes an uplink silence switch indication at the RRC level. Based on this possible embodiment, even if there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the terminal can flexibly determine whether to silence PUSCH transmission on uplink silence resources based on the uplink silence switch indication in the first signaling or the second configuration information, which is more conducive to meeting actual communication needs.

[0028] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, the transmission of PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information.

[0029] In one possible embodiment, if neither the first signaling nor the second configuration information includes an uplink silence switch indication, the transmission of PUSCH on uplink silence resources may be silenced or not silenced. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication in the first signaling and the second configuration information, the terminal can reasonably determine whether to silence the transmission of PUSCH on uplink silence resources.

[0030] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, and the uplink silence switch indication is not present in the TDRA table associated with the PUSCH, the transmission of PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication in the first signaling, the terminal can flexibly determine whether to silence the transmission of PUSCH on the uplink silence resource.

[0031] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, and the PUSCH-associated TDRA table does not contain an uplink silence switch indication, and the second configuration information does not include an uplink silence switch indication, then PUSCH transmission may be silenced or not silenced on uplink silence resources. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication in the first signaling and the second configuration information, the terminal can reasonably determine whether to silence PUSCH transmission on uplink silence resources.

[0032] Fourthly, embodiments of this application provide an uplink silencing method, the method comprising: sending first configuration information and second configuration information to a terminal, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, the second configuration information being used to configure uplink silencing resources; sending first signaling to the terminal, the first signaling being used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission; and, in the absence of an uplink silencing switch indication in the TDRA table associated with the PUSCH, not receiving or receiving PUSCH transmission on the uplink silencing resources.

[0033] In one possible embodiment, the PUSCH is a configuration-authorized PUSCH; if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the PUSCH transmission is received on the uplink silence resource.

[0034] Fifthly, embodiments of this application provide an uplink silencing method, the method comprising: sending first configuration information and second configuration information to a terminal, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, the second configuration information being used to configure uplink silencing resources; the second configuration information further comprising an uplink silencing switch indication at the Radio Resource Control (RRC) level; sending a first signaling to the terminal, the first signaling being used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission; and, if there is no uplink silencing switch indication in the TDRA table associated with the PUSCH, not receiving or receiving PUSCH transmission on the uplink silencing resources based on the switch indication in the second configuration information.

[0035] In conjunction with the method described in the fifth aspect, in one possible embodiment, the PUSCH is a configured authorized PUSCH; if there is an uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is not received or is received on the uplink silence resource based on the switch indication in the second configuration information.

[0036] In conjunction with the method described in the fifth aspect, in one possible embodiment, if the second configuration information does not include an uplink silence switch indication at the RRC level, PUSCH transmissions are not received or are received on uplink silence resources.

[0037] In conjunction with the method described in the fourth or fifth aspect, in one possible embodiment, if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of PUSCH is either not received or received on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

[0038] In conjunction with the method described in the fifth aspect, in one possible embodiment, if the second configuration information does not include an uplink silence switch indication at the RRC level and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, then PUSCH transmissions are not received or are received on the uplink silence resource.

[0039] In conjunction with the methods described in the fourth or fifth aspect, in one possible embodiment, at least one of the one or more TDRA forms includes an uplink silent switch indication.

[0040] In conjunction with the method described in the fourth or fifth aspect, in one possible embodiment, the first signaling is a downlink control information (DCI) for activating or scheduling PUSCH transmission, and the first signaling is a second type of DCI; wherein the PUSCH scheduled or activated by the first type of DCI is always non-silently transmitted on the uplink silent resource.

[0041] In conjunction with the methods described in the fourth or fifth aspect, in one possible embodiment, the type of DCI for the scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

[0042] In a sixth aspect, embodiments of this application provide an uplink silencing method, the method comprising: sending first configuration information and second configuration information to a terminal, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, the second configuration information being used to configure uplink silencing resources; sending first signaling to the terminal, the first signaling being used to configure uplink Physical Shared Channel (PUSCH) transmission; the PUSCH being a configured authorized PUSCH; and, if the first signaling includes an uplink silencing switch indication, and there is no uplink silencing switch indication in the TDRA table associated with the PUSCH, then, based on the switch indication in the first signaling, either not receiving or receiving PUSCH transmission on the uplink silencing resources.

[0043] In one possible embodiment, if the first signaling includes an uplink silence switch indication and an uplink silence switch indication exists in the TDRA table associated with the PUSCH, then based on the switch indication in the first signaling, PUSCH transmissions are either not received or received on the uplink silence resource.

[0044] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, PUSCH transmissions are not received or are received on the uplink silence resource.

[0045] In one possible embodiment, if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, then based on the switch indication in the TDRA table associated with the PUSCH, either PUSCH transmissions are not received or are received on the uplink silence resource.

[0046] In one possible embodiment, if the first signaling does not include an uplink silence switch indication and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, then PUSCH transmissions are not received or are received on the uplink silence resource.

[0047] In one possible embodiment, the second configuration information also includes an uplink silence switch indication at the RRC level.

[0048] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, the transmission of PUSCH is not received or is received on the uplink silence resource based on the switch indication in the second configuration information.

[0049] In one possible embodiment, if the first signaling does not include an uplink silence switch indication and the second configuration information does not include an uplink silence switch indication, then PUSCH transmissions are not received or are received on the uplink silence resource.

[0050] In one possible embodiment, if the first signaling does not include an uplink silence switch indication and there is no uplink silence switch indication in the TDRA table associated with PUSCH, then based on the switch indication in the second configuration information, PUSCH transmissions are either not received or received on the uplink silence resource.

[0051] In one possible embodiment, if the first signaling does not include an uplink silence switch indication, and the uplink silence switch indication does not exist in the TDRA table associated with the PUSCH, and the second configuration information does not include an uplink silence switch indication, then PUSCH transmissions are not received or are received on the uplink silence resource.

[0052] The beneficial effects of aspects four through six can be found in the beneficial effects of aspects one through three, and will not be repeated here.

[0053] In a seventh aspect, this application provides a communication device that has the function of implementing the methods described in any one of the first to sixth aspects. For example, the communication device includes modules, units, or means corresponding to the operations involved in performing the methods described in any one of the first to sixth aspects. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0054] Eighthly, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions involved in the methods described in any one of the first to sixth aspects. The one or more processors can execute the computer program or instructions, which, when executed, cause the communication device to implement the methods described in any one of the first to sixth aspects. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0055] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0056] In one possible design, the communication device may also include the memory.

[0057] The aforementioned communication device may be a terminal, or a communication / processing module within a terminal, or a chip within a terminal responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module, or a circuit or chip within a terminal responsible for processing functions (such as a GPU). Alternatively, the aforementioned communication device may be a network device, or a module within a network device (e.g., a circuit, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0058] Ninthly, this application provides a communication system including a terminal and a network device. The terminal can perform the methods described in the first, second, or third aspects above, and the network device can perform the methods described in the fourth, fifth, or sixth aspects above.

[0059] In a tenth aspect, this application provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform the methods described in any one of the first to sixth aspects above.

[0060] In one aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform the methods described in any one of the first to sixth aspects above. Attached Figure Description

[0061] Figure 1 is a schematic diagram of inter-base station interference;

[0062] Figure 2 is a schematic diagram of another type of inter-base station interference;

[0063] Figure 3 is a possible, non-limiting system schematic diagram provided in an embodiment of this application;

[0064] Figure 4 is a schematic diagram of FDD, TDD, and SBFD provided in the embodiments of this application;

[0065] Figure 5 is a schematic diagram of the uplink silence pattern provided in the embodiment of this application;

[0066] Figure 6 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0067] Figure 7 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0068] Figure 8 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0069] Figure 9 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0070] Figure 10 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0071] Figure 11 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0072] Figure 12 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0073] Figure 13 is a flowchart illustrating an uplink silencing method provided in an embodiment of this application;

[0074] Figure 14 is a possible exemplary block diagram of the communication device involved in the embodiments of this application;

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

[0076] To better understand the embodiments of this application, the system architecture involved in the embodiments of this application will be described first below:

[0077] This application's embodiments can be applied to long-term evolution (LTE) systems, 5th generation mobile communication (5G) systems, 6th generation mobile communication (6G) systems, and other communication systems evolving after 5G, as well as satellite communication and short-range wireless communication systems. The wireless communication systems mentioned in this application's embodiments include, but are not limited to: the three major application scenarios of 5G / 6G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC); long-range (LoRa) systems; and vehicle-to-everything (V2X) systems. The wireless communication system may include one or more access network devices and one or more terminal devices.

[0078] Figure 3 is a possible, non-limiting system schematic diagram provided by an embodiment of this application. As shown in Figure 3, the communication system 10 includes a radio access network (RAN) 100, a core network (CN) 200, and a data network (DN) 300.

[0079] RAN 100 includes at least one RAN node (110a and 110b in Figure 3, collectively referred to as 110) and at least one terminal (120a-120j in Figure 3, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 3). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0080] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems (such as 6G mobile communication systems). RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems. RAN can also be referred to as an access network (AN).

[0081] 1. RAN Node 110

[0082] RAN node 110, sometimes also referred to as access network equipment, RAN entity, access node, access point, or network device, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 3 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 3 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0083] In one possible scenario, RAN node 110 can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6th-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. RAN node 110 can be a macro base station (as shown in Figure 3, 110a), a micro base station or indoor station (as shown in Figure 3, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. In one possible embodiment, RAN node 110 can also be a server, a wearable device, a vehicle, or an in-vehicle device. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of RAN node 110 in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). In this application, RAN node 110 can also be a logical node, logical module, or software that can implement all or part of the functions of RAN node 110.

[0084] In another possible scenario, multiple RAN nodes 110 collaborate to assist the terminal in achieving wireless access, with each RAN node 110 implementing a portion of the base station's functions. For example, a RAN node 110 can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0085] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0086] In this embodiment, the form of RAN node 110 is not limited. The device used to implement the function of RAN node 110 can be RAN node 110 itself; or it can be a device that supports RAN node 110 in implementing the function, such as a chip system. The device can be installed in RAN node 110 or used in conjunction with RAN node 110.

[0087] For ease of description, RAN node 110 will be referred to as a network device in the following text.

[0088] 2. Terminal

[0089] The terminal can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, transportation vehicle with wireless communication capabilities, communication module, head-mounted XR glasses, video player, holographic projector, etc. The embodiments of this application do not limit the device form of the terminal. The terminal typically contains a communication module, circuit, or chip that performs the corresponding communication functions. The terminal can also be configured with program instructions for performing the corresponding communication functions.

[0090] II. Core Network 200

[0091] The core network 200 has three main functions: registration, connection, and session management. The core network 200 primarily includes network exposure function (NEF) network elements, policy control function (PCF) network elements, application function (AF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, and user plane function (UPF) network elements.

[0092] NEF network element: Used to expose the services and capabilities of 3GPP network functions to AF network elements, and at the same time, it allows AF network elements to provide information to 3GPP network functions.

[0093] PCF network element: Used for policy management of charging and QoS policies.

[0094] AF network element: mainly used to transmit the application side's requirements to the network side.

[0095] AMF (Automatic Mobility Management) elements are primarily used for mobility management, access authentication / authorization, and other functions. They are also responsible for transmitting user policies between the UE and the PCF (Programmable Component Filter).

[0096] SMF network element: Used to complete session management functions such as UE IP address allocation, UPF selection, billing and QoS policy control.

[0097] UPF network elements: As the interface with the data network, they perform functions such as user plane data forwarding, session / flow-based billing and statistics, and bandwidth limiting.

[0098] III. Data Network 300

[0099] Data network 300 can provide services such as fixed-line network, Internet, carrier services or third-party services.

[0100] The following explanations of some terms involved in the embodiments of this application are provided to facilitate understanding by those skilled in the art. This explanation is for the purpose of understanding only and should not be regarded as a disclosure or specific limitation of the technical solution of this application.

[0101] I. Physical Uplink Shared Channel (PUSCH) in NR

[0102] In NR, PUSCH can be divided into the following three types:

[0103] 1. PUSCH based on dynamic grant (DG PUSCH).

[0104] 2. Configured grant type 1 (Type 1 CG PUSCH): Semi-static scheduling. The terminal receives the higher-level parameter configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant, without needing to receive DCI. In the protocol, this is referred to as "configured uplink grant".

[0105] 3. Configured grant type 2 (Type 2 CG PUSCH): Similar to semi-persistent scheduling (SPS) in LTE, the terminal first receives the higher-layer parameter configuredGrantConfig which does not contain rrc-ConfiguredUplinkGrant, and then activates or deactivates it by L1 signaling. This is called "configured uplink grant based on L1 signalling".

[0106] The first type of PUSCH transmission occurs when the terminal receives an uplink schedule, and so on. The second type involves semi-persistent, or periodic, resources configured by the higher layers. The terminal can use these resources for PUSCH transmission if it needs to send uplink data; otherwise, it doesn't transmit. The third type of PUSCH transmission also involves semi-persistent, or periodic, resources configured by the higher layers, which are activated or deactivated by physical layer signaling. When activated, these resources behave similarly to the second type of PUSCH transmission; when deactivated, they are unusable.

[0107] II. Time-domain resource allocation for PUSCH

[0108] The network side will configure one or more TDRA tables for users through higher-level signaling configuration or protocol presets. Each table contains N rows, where each row is used to indicate the time domain position of a PUSCH in a slot. The time domain position of each PUSCH can be indicated by its start symbol index and length value in a slot.

[0109] For DG PUSCH and Type 2 CG PUSCH, the specific location of the PUSCH within a time slot is indicated by the TDRA indication field contained in the DCI that schedules the DG PUSCH or activates the Type 2 CG PUSCH. This TDRA indication field indicates one of the N rows in the TDRA table. The terminal can determine the time domain location of the scheduled / activated PUSCH by using the TDRA table and the corresponding TDRA indication field.

[0110] For Type 1 CG PUSCH, the network device configures a value through the RRC parameter timeDomainAllocation, which corresponds to the row index of the TDRA table and indicates the time domain location of the PUSCH within a time slot.

[0111] III. TDRA Form

[0112] 1. TDRA forms for DG PUSCH and Type 2 CG PUSCH

[0113] Depending on the scheduling method of the PUSCH and the DCI that schedules the PUSCH, the TDRA table used to determine the time domain location of the PUSCH may also be different, as specified below:

[0114] 1) MSG3 PUSCH, using the PUSCH scheduled / activated by DCI 0_0 in the CSS associated with CORESET 0:

[0115] The R15TDRA table configured in the radio resource control (RRC) parameter PUSCH-ConfigCommon is used preferentially. If it is not configured, the TDRA table predefined in the protocol is used.

[0116] 2) Using a PUSCH scheduled / activated by DCI 0_0 in a CSS not associated with CORESET 0, and using a PUSCH scheduled / activated by DCI 0_0 in a USS:

[0117] The R15 TDRA table configured in the RRC parameter PUSCH-Config is used first. If it is not configured, the R15 TDRA table configured in the RRC parameter PUSCH-ConfigCommon is used second. If it is not configured, the TDRA table predefined in the protocol is used.

[0118] 3) Use other DCI-scheduled / activated PUSCHs in the USS:

[0119] The TDRA table (*) configured in the RRC parameter PUSCH-Config is used first. If it is not configured, the R15 TDRA table configured in the RRC parameter PUSCH-ConfigCommon is used second. If it is not configured, the TDRA table predefined in the protocol is used.

[0120] Specifically, (*) for DCI format 0_1 / 0_2 / 0_3, it can be associated with the R15 TDRA table or the R15+TDRA table in PUSCH-Config, and the base station will ensure that the R15 TDRA table and the R15+TDRA table are not configured at the same time. Generally speaking, the parameters added to the TDRA table after R16 are configured in the R15+TDRA table.

[0121] 2. TDRA table for Type 1 CG PUSCH

[0122] 1) PUSCH of repeating type A:

[0123] The R15 TDRA table configured in the RRC parameter PUSCH-Config is used first. If it is not configured, the TDRA table configured in the RRC parameter PUSCH-ConfigCommon is used second. If it is not configured, the TDRA table predefined in the protocol is used.

[0124] 2) PUSCH of repeating type B:

[0125] Use the R15+TDRA table configured in the RRC parameter PUSCH-Config.

[0126] IV. Duplex in NR

[0127] Currently, NR includes frequency division duplex (FDD), time division duplex (TDD), and subband full duplex (SBFD).

[0128] 1. FDD

[0129] As shown in the left figure of Figure 4, downlink transmission can be performed on the downlink bandwidth part (DL BWP) in time slot 0, and uplink transmission can also be performed on the uplink bandwidth part (UL BWP) in time slot 0. DL BWP and UL BWP are located on different carriers and are separate in the frequency domain.

[0130] 2. TDD

[0131] As shown in the middle of Figure 4, the DL BWP and UL BWP share the same center frequency. Their bandwidths can be the same or different. At any given time, the terminal can only perform uplink or downlink transmission. For example, in time slot 0, only downlink transmission is possible; in time slot 3, only uplink transmission is possible; and time slot 2 is a flexible time slot, meaning it can be used for either uplink or downlink transmission, but not simultaneously. The smallest granularity for uplink / downlink switching is a symbol. For instance, time slot 2, being a flexible time slot, consists of 14 or 12 orthogonal frequency division multiplexing (OFDM) symbols. The first M symbols are downlink symbols, the last N symbols are uplink symbols, and the middle 14-MN (or 12-MN) symbols are flexible symbols. 0 <= M <= 14, 0 <= N <= 14, M+N <= 14. Downlink symbols are used for downlink transmission, uplink symbols are used for uplink transmission, and flexible symbols can be used for both uplink and downlink. The specific transmission direction is notified to the terminal by the network device through RRC signaling or DCI scheduling.

[0132] Compared to FDD, TDD occupies less frequency domain resources. However, because uplink and downlink transmissions cannot be performed simultaneously in TDD (for example, only downlink transmission can be performed in time slot 0, and uplink transmission cannot be performed), uplink transmission delay will increase.

[0133] 3.SBFD

[0134] To address the latency issue of TDD, flexible duplexing, also known as complementary TDD (C-TDD) or full duplexing, is being discussed in standards. Other names include SBFD, which is currently widely discussed. The core idea is that uplink and downlink transmission resources can be configured simultaneously on a specific symbol or time slot within a TDD system. For example, as shown in Figure 4 (right side), within a time slot, such as time slot 0, there exists a frequency domain resource in the downlink BWP that can be used for uplink transmission. This allows uplink transmission to occur on time slot 0, reducing uplink latency. This frequency domain resource is typically called the uplink subband. Downlink transmission can also occur on time slot 0. Network devices can perform both uplink and downlink transmissions simultaneously on time slot 0 (limited to either the uplink or downlink subband). Terminals can also perform both uplink and downlink transmissions simultaneously on time slot 0 (i.e., full-duplex terminals), or they can perform only uplink or downlink transmissions on time slot 0 (half-duplex terminals). Compared to TDD, SBFD offers more uplink resources, which can increase uplink coverage.

[0135] Based on the latest progress in standard discussions, network devices will send TDD configuration parameters and SBFD configuration parameters to terminals, including:

[0136] TDD configuration parameters may include, but are not limited to: the slot indexes of downlink slots, uplink slots, and flexible slots, and the symbol indexes of uplink symbols, downlink symbols, and flexible symbols in flexible slots.

[0137] 1) Downlink symbols in downlink time slots and flexible time slots are used for downlink data transmission;

[0138] 2) Uplink symbols in uplink time slots and flexible time slots are used for uplink data transmission;

[0139] 3) The flexible symbols in the flexible time slot can be used for both uplink and downlink data transmission.

[0140] SBFD configuration parameters may include, but are not limited to: SBFD slot / symbol position, and SBFD sub-band position within the SBFD slot.

[0141] 1) The SBFD slot / symbol position is a DL slot / symbol configured in the TDD configuration, or part or all of the slots / symbols in the flexible slot / symbol, that is, some or all of the downlink slots / symbols or flexible slots / symbols are converted into SBFD symbols.

[0142] 2) The SBFD subband position can be the frequency domain position of the UL subband and / or DL ​​subband.

[0143] V. Upward muting (UL muting)

[0144] To address interference between network devices, the standard is discussing uplink resource silencing, which involves not transmitting data on certain uplink resources. This allows network devices to more accurately measure the interference and then perform interference cancellation during reception. For example, as shown in Figure 5, the gray resources represent silencing resources. This silencing can be at the RB (Remote Block) level or the RE (Remote Array Block) level. For instance, uplink silencing patterns 1 and 2 in Figure 5 represent RE-level silencing, while uplink silencing pattern 3 represents RB-level silencing.

[0145] To enable a terminal to reasonably determine whether to enable uplink silencing on uplink silencing resources, embodiments of this application provide an uplink silencing method and apparatus. The communication method and apparatus will be further described below with reference to the accompanying drawings. It is understood that this application uses a terminal and an access network device as examples to illustrate the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the terminal in this application can also be implemented by a communication / processing module in the terminal or a circuit or chip (such as a modem chip (also known as a baseband chip), or a SoC chip containing a modem core, or a SIP chip, or a GPU) responsible for communication / processing functions in the terminal. Similarly, the method executed by the access network device in this application can also be implemented by a module (e.g., a circuit, chip, or chip system) in the access network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the access network device.

[0146] Please refer to Figure 6, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0147] 601. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more TDRA tables, and the second configuration information is used to configure uplink silent resources. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0148] For example, the first configuration information can be configured, but is not limited to, one or more of the following TDRA tables:

[0149] 1) Configure the R15 TDRA table in the RRC parameter PUSCH-ConfigCommon, which corresponds to the RRC parameter pusch-TimeDomainAllocationList in the RRC parameter PUSCH-ConfigCommon;

[0150] 2) Configure the R15 TDRA table in the RRC parameter PUSCH-Config, which corresponds to the RRC parameter pusch-TimeDomainAllocationList in the RRC parameter PUSCH-Config;

[0151] 3) Configure the R15+TDRA table in the RRC parameter PUSCH-Config, corresponding to the RRC parameter pusch-TimeDomainAllocationListDCI-0-2-r16, pusch-TimeDomainAllocationListDCI-0-1-r16, or pusch-TimeDomainAllocationListForMultiPUSCH-r16 in the RRC parameter PUSCH-Config.

[0152] Optionally, the R15+TDRA table may include an uplink silence switch indicator (i.e., an uplink silence ON / OFF indicator). For example, a new column can be added to the R15+TDRA table, including the uplink silence switch indicator, so that each row in the R15+TDRA table corresponds to one uplink silence switch indicator. As another example, the RRC parameters corresponding to the R15+TDRA table (pusch-TimeDomainAllocationListDCI-0-2-r16, pusch-TimeDomainAllocationListDCI-0-1-r16, or pusch-TimeDomainAllocationListForMultiPUSCH-r16) are configured through the RRC parameter PUSCH-TimeDomainResourceAllocationList-r16, which contains information configured by one or more RRC parameters PUSCH-TimeDomainResourceAllocation-r16. The list consists of multiple sub-parameters for each RRC parameter PUSCH-TimeDomainResourceAllocation-r16, including the starting symbol of PUSCH in a time slot, the number of symbols occupied by PUSCH in a time slot, and the number of repetitions of PUSCH. A new sub-parameter can be added to the RRC parameter PUSCH-TimeDomainResourceAllocation-r16, which includes an uplink silence switch indicator. In this way, each PUSCH-TimeDomainResourceAllocation-r16 in the RRC parameter PUSCH-TimeDomainResourceAllocationList-r16 corresponding to the R15+TDRA table will have an uplink silence switch indicator.

[0153] Optionally, a new TDRA table can be added, in which a column contains an uplink silence switch indication, or each RRC sub-parameter in the corresponding RRC parameter list of the TDRA table contains an uplink silence switch indication.

[0154] Optionally, the second configuration information can configure, but is not limited to, the following parameters: the frequency domain position of the uplink silence and the time domain position of the uplink silence. For example, the second configuration information can configure the frequency domain position of the uplink silence, and the time domain position of the uplink silence can be predefined by the protocol, or the terminal can determine the time domain position of the uplink silence through preset rules. As another example, the second configuration information can configure the time domain position of the uplink silence, and the frequency domain position of the uplink silence can be predefined by the protocol, or the terminal can determine the frequency domain position of the uplink silence through preset rules. Furthermore, the second configuration information can configure both the frequency domain position and the time domain position of the uplink silence. Optionally, the frequency domain position of the uplink silence can be the frequency domain position of pattern 2 in Figure 5.

[0155] Optionally, the network device may also send TDD configuration parameters to the terminal device. That is, the embodiments of this application can be applied to a TDD system. TDD configuration parameters may include, but are not limited to: slot indices for downlink slots, uplink slots, and flexible slots; and symbol indices for uplink symbols, downlink symbols, and flexible symbols within the flexible slots. Wherein:

[0156] 1) Downlink symbols in downlink time slots and flexible time slots are used for downlink data transmission;

[0157] 2) Uplink symbols in uplink time slots and flexible time slots are used for uplink data transmission;

[0158] 3) The flexible symbols in the flexible time slot can be used for both uplink and downlink data transmission.

[0159] Optionally, the network device may also send SBFD configuration parameters to the terminal device. That is, the embodiments of this application can be applied to an SBFD system. SBFD configuration parameters may include, but are not limited to, the following parameters: SBFD timeslot / symbol position, and SBFD sub-band position within the SBFD timeslot. Wherein:

[0160] 1) The SBFD slot / symbol position is a DL slot / symbol configured in the TDD configuration, or part or all of the slots / symbols in the flexible slot / symbol, that is, some or all of the downlink slots / symbols or flexible slots / symbols are converted into SBFD symbols.

[0161] 2) The SBFD subband position can be the frequency domain position of the UL subband and / or DL ​​subband.

[0162] In this embodiment, the order in which the first configuration information and the second configuration information are sent is not limited. For example, the first configuration information can be sent first, followed by the second configuration information. Alternatively, the second configuration information can be sent first, followed by the first configuration information. Or, the first configuration information and the second configuration information can be sent simultaneously.

[0163] 602. The network device sends a first signaling message to the terminal, which is used to configure, activate, or schedule PUSCH transmission. Accordingly, the terminal may receive the first signaling message.

[0164] In one possible embodiment, the PUSCH can be a DG PUSCH, and the first signaling can be a DCI for scheduling DG PUSCH transmission. Alternatively, the PUSCH can be a Type 2 CG PUSCH, and the first signaling can be a DCI for activating Type 2 CG PUSCH transmission.

[0165] In another possible embodiment, the PUSCH may be a Type 1 CG PUSCH, and the first signaling may be RRC signaling for configuring the transmission of the Type 1 CG PUSCH.

[0166] Optionally, when the time-domain resource of the PUSCH is on an SBFD symbol, the method described in Figure 6 is used to determine whether to silence the transmission of the PUSCH on the SBFD symbol on the uplink silence resource. When the time-domain resource of the PUSCH is not on an SBFD symbol, the method described in Figure 6 may not be used to determine whether to silence the transmission of the PUSCH on the uplink silence resource; for example, the transmission of the PUSCH may never be silenced.

[0167] In this embodiment, the order in which the "first configuration information and second configuration information" and the first signaling are sent is not limited. For example, the "first configuration information and second configuration information" and the first signaling can be sent simultaneously, that is, sent in a large signaling packet. Alternatively, the "first configuration information and second configuration information" can be sent first, followed by the first signaling. Or, the first configuration information and the first signaling can be sent first, which is equivalent to configuring the PUSCH resource first, but not configuring the uplink silent resource. The second configuration information is then sent at a later time to configure the uplink silent resource.

[0168] 603. If there is no uplink mute switch indication in the TDRA table associated with PUSCH, the terminal mutees or does not mute the transmission of PUSCH on the uplink mute resource.

[0169] In this embodiment, the TDRA table associated with a PUSCH refers to the TDRA table that determines the time-domain resource usage of the PUSCH. For details on how to determine the TDRA table associated with a PUSCH, please refer to point three of the terminology section, which will not be repeated here.

[0170] 604. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device will not receive or will receive PUSCH transmissions on the uplink silence resource.

[0171] If the terminal silences PUSCH transmissions on uplink silent resources when there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device will not receive PUSCH transmissions on uplink silent resources when there is no uplink silence switch indication in the TDRA table associated with PUSCH.

[0172] In other words, if the terminal does not have an uplink silence switch indication in the TDRA table associated with PUSCH, it will silence PUSCH transmission on uplink silence resources by default. This allows network devices more opportunities to measure mutual interference. Multiple measurements help network devices obtain more accurate interference information, thereby improving communication performance. Furthermore, by defaulting to silencing PUSCH transmission on uplink silence resources, it helps save additional signaling overhead.

[0173] If the terminal does not silence the transmission of PUSCH on the uplink silent resource when there is no uplink silence switch indication in the TDRA table associated with PUSCH, then the network device will receive the transmission of PUSCH on the uplink silent resource when there is no uplink silence switch indication in the TDRA table associated with PUSCH.

[0174] In other words, if the terminal does not have an uplink silencing switch indication in the TDRA table associated with PUSCH, it will by default not silence PUSCH transmission on uplink silencing resources. This helps reduce the impact on uplink data transmission performance. Furthermore, by defaulting to not silencing PUSCH transmission on uplink silencing resources, it helps save additional signaling overhead.

[0175] In one possible embodiment, the default behavior of the terminal and network device when there is no uplink silence switch indication in the TDRA table associated with the DG PUSCH or Type 2 CG PUSCH may be the same as or different from the default behavior of the terminal and network device when there is no uplink silence switch indication in the TDRA table associated with the Type 1 CG PUSCH.

[0176] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with DG PUSCH or Type 2 CG PUSCH, it will not silence the transmission of DG PUSCH or Type 2 CG PUSCH on the uplink silence resource. Accordingly, the network device will receive the transmission of DG PUSCH or Type 2 CG PUSCH on that uplink silence resource. Similarly, if the terminal does not have an uplink silence switch indication in the TDRA table associated with Type 1 CG PUSCH, it will not silence the transmission of Type 1 CG PUSCH on the uplink silence resource. Accordingly, the network device will receive the transmission of Type 1 CG PUSCH on that uplink silence resource.

[0177] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with DG PUSCH or Type 2 CG PUSCH, it silences the transmission of DG PUSCH or Type 2 CG PUSCH on the uplink silence resource. Accordingly, the network device does not receive the transmission of DG PUSCH or Type 2 CG PUSCH on that uplink silence resource. Similarly, if the terminal does not have an uplink silence switch indication in the TDRA table associated with Type 1 CG PUSCH, it silences the transmission of Type 1 CG PUSCH on the uplink silence resource. Accordingly, the network device does not receive the transmission of Type 1 CG PUSCH on that uplink silence resource.

[0178] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with DG PUSCH or Type 2 CG PUSCH, it will not silence the transmission of DG PUSCH or Type 2 CG PUSCH on the uplink silence resource. Correspondingly, the network device will receive the transmission of DG PUSCH or Type 2 CG PUSCH on that uplink silence resource. If the terminal does not have an uplink silence switch indication in the TDRA table associated with Type 1 CG PUSCH, it will silence the transmission of Type 1 CG PUSCH on the uplink silence resource. Correspondingly, the network device will not receive the transmission of Type 1 CG PUSCH on that uplink silence resource.

[0179] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with DG PUSCH or Type 2 CG PUSCH, it silences the transmission of DG PUSCH or Type 2 CG PUSCH on the uplink silence resource. Accordingly, the network device does not receive the transmission of DG PUSCH or Type 2 CG PUSCH on that uplink silence resource. If the terminal does not have an uplink silence switch indication in the TDRA table associated with Type 1 CG PUSCH, it does not silence the transmission of Type 1 CG PUSCH on the uplink silence resource. Accordingly, the network device receives the transmission of Type 1 CG PUSCH on that uplink silence resource.

[0180] In another possible embodiment, the default behavior of the terminal and network device when there is no uplink silence switch indication in the TDRA table associated with the DG PUSCH may be the same as or different from the default behavior of the terminal and network device when there is no uplink silence switch indication in the TDRA table associated with the Type 1 CG PUSCH or Type 2 CG PUSCH.

[0181] In one possible embodiment, if the terminal has an uplink silence switch indication in the TDRA table associated with the PUSCH, it silences or does not silence PUSCH transmissions on uplink silence resources based on the switch indication in the TDRA table associated with the PUSCH. Correspondingly, if the network device has an uplink silence switch indication in the TDRA table associated with the PUSCH, it either does not receive or receives PUSCH transmissions on uplink silence resources based on the switch indication in the TDRA table associated with the PUSCH.

[0182] In other words, the terminal prioritizes the uplink silence on / off indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence on / off indication in the TDRA table associated with the PUSCH will the terminal default to not silencing or silencing the PUSCH transmission on the uplink silence resource. By prioritizing the uplink silence on / off indication in the TDRA table associated with the PUSCH, the network device's initiative in enabling or disabling uplink silence is ensured.

[0183] For example, assuming the uplink silence switch indicator in the TDRA table associated with PUSCH indicates that uplink silence is enabled (e.g., the uplink silence switch indicator is ON in the TDRA table associated with PUSCH), then the terminal silences PUSCH transmission on the uplink silence resource. Accordingly, the network device does not receive PUSCH on the uplink silence resource. Conversely, assuming the uplink silence switch indicator in the TDRA table associated with PUSCH indicates that uplink silence is disabled (e.g., the uplink silence switch indicator is OFF in the TDRA table associated with PUSCH), then the terminal does not silence PUSCH transmission on the uplink silence resource. Accordingly, the network device receives PUSCH on the uplink silence resource.

[0184] In one possible embodiment, at least one of the one or more TDRA tables includes an uplink silencing switch indication. This facilitates network devices to use DCI signaling to dynamically indicate whether to perform uplink silencing, which helps to ensure the flexible use of the uplink silencing mechanism.

[0185] In one possible embodiment, the first signaling is a downlink control information (DCI) for activating or scheduling PUSCH transmission, and the first signaling is a second type of DCI; wherein, the PUSCH scheduled or activated by the first type of DCI is never silent on the uplink silent resource. In this way, different types of DCI can correspond to different uplink silent enabling or disabling schemes, allowing network devices to flexibly enable or disable uplink silent through a combination of various signaling.

[0186] For example, the PUSCH mentioned above could be a DG PUSCH, and the first signaling could be a DCI used to schedule DG PUSCH transmission. Alternatively, the PUSCH mentioned above could be a Type 2 CG PUSCH, and the first signaling could be a DCI used to activate Type 2 CG PUSCH transmission.

[0187] In other words, for the two types of DCI operations used for scheduling or activation of PUSCH:

[0188] Type 1 DCI scheduled or active PUSCH: Never silent transmission on uplink silent resources.

[0189] The second type of DCI-scheduled or activated PUSCH: silent or non-silent transmission on uplink silent resources according to the rules shown in Figure 6.

[0190] In one possible embodiment, the type of DCI for a scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides. Based on this possible embodiment, the type of DCI does not need to be indicated through additional signaling, which helps to save signaling overhead.

[0191] 1) The type of DCI for the scheduled or activated PUSCH is related to the DCI format.

[0192] For example, DCI format 0_0 belongs to the first type of DCI, while other DCI formats belong to the second type of DCI.

[0193] 2) The type of DCI for a scheduled or activated PUSCH is related to the search space in which the DCI resides.

[0194] For example, DCI in the common search space (CSS) belongs to the first type of DCI, while DCI in the user-specific search space (USS) belongs to the second type of DCI.

[0195] 3) The type of DCI for a scheduled or activated PUSCH is related to the set of control resources associated with the search space where the DCI resides.

[0196] For example, the DCI in the SS associated with CORESET 0 belongs to the first type of DCI, while the DCI in the SS associated with other CORESETs belongs to the second type of DCI.

[0197] 4) The type of DCI for a scheduled or activated PUSCH is related to the following: DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

[0198] For example, the DCI in the CSS associated with CORESET 0 belongs to the first type of DCI, while the DCI in other SS belongs to the second type of DCI.

[0199] For example, in the SS associated with CORESET 0, DCI format 0_0 belongs to the first type of DCI, while other DCIs belong to the second type of DCI.

[0200] For example, in the CSS associated with CORESET 0, DCI format 0_0 belongs to the first type of DCI, while other DCIs belong to the second type of DCI.

[0201] As can be seen, based on the method described in Figure 6, when there is no uplink silence switch indication in the TDRA table used, it is helpful for the terminal to reasonably determine whether to enable uplink silence on uplink silence resources.

[0202] Please refer to Figure 7, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0203] 701. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an RRC-level uplink silence on / off indicator. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0204] The difference between steps 701 and 601 is that in step 701, the second configuration information also includes an RRC-level uplink silence switch indication. The inclusion of an RRC-level uplink silence switch indication in the second configuration information can also be understood as the second configuration information including an uplink silence switch indication, and the second configuration information being carried within the RRC signaling. Further descriptions of step 701 can be found in the description of step 601, and will not be repeated here.

[0205] 702. The network device sends a first signaling message to the terminal, which is used to configure, activate, or schedule PUSCH transmission. Accordingly, the terminal may receive the first signaling message.

[0206] Step 702 can be found in the description of step 602, and will not be repeated here.

[0207] 703. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal silences or does not silence the transmission of PUSCH on the uplink silence resource based on the switch indication in the second configuration information.

[0208] 704. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device shall not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the second configuration information.

[0209] For example, if there is no uplink silencing switch indication in the TDRA table associated with PUSCH, assuming the switch indication in the second configuration information is used to indicate enabling uplink silencing (e.g., the switch indication in the second configuration information is ON), then the terminal silences PUSCH transmission on the uplink silencing resource. Accordingly, the network device does not receive PUSCH on the uplink silencing resource. Conversely, assuming the switch indication in the second configuration information is used to indicate disabling uplink silencing (e.g., the switch indication in the second configuration information is OFF), then the terminal does not silence PUSCH transmission on the uplink silencing resource. Accordingly, the network device receives PUSCH on the uplink silencing resource.

[0210] In one possible embodiment, if the second configuration information does not include an uplink silencing switch indication at the RRC level, the terminal may silence or not silence PUSCH transmissions on uplink silencing resources. Correspondingly, the network device may not receive or may receive PUSCH transmissions on uplink silencing resources. Based on this possible embodiment, even if the network device does not add an uplink silencing switch indication to the second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silencing resources.

[0211] In one possible embodiment, if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal silences or does not silence PUSCH transmissions on uplink silence resources based on the switch indication in the TDRA table associated with the PUSCH. Correspondingly, if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the network device either does not receive or receives PUSCH transmissions on uplink silence resources based on the switch indication in the TDRA table associated with the PUSCH.

[0212] In other words, the terminal prioritizes the uplink silence switch indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence switch indication in the TDRA table associated with the PUSCH will the terminal silence or not silence the PUSCH transmission on the uplink silence resource based on the switch indication in the second configuration information. This allows for flexible enabling or disabling of uplink silence based on a combination of various signaling methods.

[0213] In other words, the terminal has the following two types of capabilities:

[0214] 1) Supports enabling / disabling semi-static uplink mute: Supports enabling / disabling uplink mute using RRC-level uplink mute switch indicators, such as configuring RRC-level uplink mute switch indicators.

[0215] 2) Supports dynamic uplink silence enabling / disabling: Supports using the TDRA field in DCI to indicate uplink silence enabling / disabling.

[0216] Supporting semi-static uplink muting is a basic capability of a terminal to support uplink muting, while supporting dynamic uplink muting is an enhanced capability of the terminal. That is, a terminal that supports dynamic uplink muting must also support semi-static uplink muting.

[0217] In one possible embodiment, if the second configuration information does not include an uplink silence switch indication at the RRC level, and the uplink silence switch indication does not exist in the TDRA table associated with the PUSCH, the terminal silences or does not silence PUSCH transmissions on uplink silence resources. Accordingly, the network device either does not receive or receives PUSCH transmissions on uplink silence resources. Based on this possible embodiment, even if the network device does not add an uplink silence switch indication to the second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silence resources.

[0218] In one possible embodiment, at least one of the one or more TDRA tables includes an uplink silencing switch indication. This facilitates network devices to use DCI signaling to dynamically indicate whether to perform uplink silencing, which helps to ensure the flexible use of the uplink silencing mechanism.

[0219] In one possible embodiment, the first signaling is a downlink control information (DCI) used to activate or schedule PUSCH transmission, and the first signaling is a second type of DCI; wherein, the PUSCH scheduled or activated by the first type of DCI is never silent on uplink silent resources. In this way, different types of DCI can correspond to different uplink silent enabling or disabling schemes, allowing network devices to flexibly enable or disable uplink silent through combinations of various signaling. A description of this possible embodiment can be found in the relevant description under the embodiment corresponding to Figure 6, and will not be repeated here.

[0220] In one possible embodiment, the type of DCI for the scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides. Based on this possible embodiment, the type of DCI does not need to be indicated through additional signaling, which helps to save signaling overhead. A description of this possible embodiment can be found in the relevant description under the embodiment corresponding to Figure 6, and will not be repeated here.

[0221] As can be seen, based on the method described in Figure 7, network devices can flexibly configure uplink muting switch indications at the RRC level according to communication requirements. Thus, even when there is no uplink muting switch indication in the TDRA table associated with the PUSCH, the terminal can flexibly determine whether to mute PUSCH transmission on uplink muting resources based on the RRC-level uplink muting switch indication, which is beneficial for meeting actual communication needs.

[0222] Please refer to Figure 8, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0223] 801. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0224] Step 801 can be found in the description of step 601, and will not be repeated here.

[0225] 802. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0226] In this embodiment of the application, the first signaling can be RRC signaling, and the PUSCH is a configuration authorization PUSCH. The first signaling includes the configuration authorization configuration (i.e., CG configuration) of the PUSCH. For example, the PUSCH can be a Type 1 CG PUSCH. As another example, the PUSCH can be a Type 2 CG PUSCH.

[0227] The order of sending "first configuration information and second configuration information" and the first signaling can be found in the description under step 602, and will not be repeated here.

[0228] 803. If the first signaling includes an uplink mute switch indication and there is no uplink mute switch indication in the TDRA table associated with PUSCH, the terminal mutes or does not mute the transmission of PUSCH on the uplink mute resource based on the switch indication in the first signaling.

[0229] The signaling for configuring Type 1 CG PUSCH transmission may include an uplink silence switch indication only, while the signaling for configuring Type 2 CG PUSCH transmission may not include an uplink silence switch indication. In other words, the first signaling in steps 802 and 803 is used to configure Type 1 CG PUSCH transmission.

[0230] Alternatively, the signaling used to configure Type 1 CG PUSCH transmission may include an uplink silence switch indication, and the signaling used to configure Type 2 CG PUSCH transmission may also include an uplink silence switch indication. That is, the first signaling in steps 802 and 803 is used to configure either Type 1 CG PUSCH or Type 2 CG PUSCH transmission.

[0231] In this embodiment of the application, the first signaling including the uplink mute switch indication can be understood as the CG configuration of the first signaling including the uplink mute switch indication.

[0232] 804. If the network device includes an uplink silence switch indication in the first signaling and there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device will not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the first signaling.

[0233] For example, if there is no uplink silencing switch indication in the TDRA table associated with PUSCH, assuming the switch indication in the first signaling is used to indicate enabling uplink silencing (e.g., the switch indication in the first signaling is ON), then the terminal silences PUSCH transmission on the uplink silencing resource. Accordingly, the network device does not receive PUSCH on the uplink silencing resource. Conversely, assuming the switch indication in the first signaling is used to indicate disabling uplink silencing (e.g., the switch indication in the first signaling is OFF), then the terminal does not silence PUSCH transmission on the uplink silencing resource. Accordingly, the network device receives PUSCH on the uplink silencing resource.

[0234] In this embodiment of the application, when the first signaling includes an uplink silence switch indication, and an uplink silence switch indication exists in the TDRA table associated with PUSCH, there are two possible implementation methods:

[0235] 1) Based on the switch indication in the first signaling, the terminal may mute or not mute the transmission of PUSCH on the uplink mute resource. Correspondingly, the network device may not receive or receive the transmission of PUSCH on the uplink mute resource based on the switch indication in the first signaling.

[0236] In other words, when the first signaling includes an uplink silence switch indication, regardless of whether the uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal always silences or does not silence PUSCH transmission on uplink silenced resources based on the switch indication in the first signaling. The terminal always ignores the uplink silence switch indication in the TDRA table associated with the PUSCH. Thus, when the first signaling includes an uplink silence switch indication, for CG PUSCH, the terminal can disregard the presence of an uplink silence switch in the TDRA table and determine whether to silence or not silence PUSCH transmission on uplink silenced resources solely based on the uplink silence switch indication in the first signaling, simplifying the terminal's implementation complexity. Simultaneously, it ensures that network devices use the uplink silence switch indication in the first signaling to indicate whether to perform uplink silence, which is beneficial for ensuring the flexible use of the uplink silence mechanism and meeting actual communication needs.

[0237] Optionally, if the first signaling does not include an uplink silence switch indication, the terminal may silence or not silence PUSCH transmissions on uplink silence resources. Correspondingly, if the first signaling does not include an uplink silence switch indication, the network device may not receive or may receive PUSCH transmissions on uplink silence resources. That is, the network device can add an uplink silence switch indication to the first signaling based on communication requirements. If the network device does not add an uplink silence switch indication to the first signaling, the terminal defaults to silencing or not silencing PUSCH transmissions on uplink silence resources. Therefore, based on this optional approach, even if the network device does not add an uplink silence switch indication to the first signaling, the terminal can determine whether to silence PUSCH transmissions on uplink silence resources.

[0238] 2) The terminal silences or does not silence PUSCH transmissions on uplink silent resources based on the switch indication in the TDRA table associated with PUSCH. Correspondingly, the network device does not receive or receives PUSCH transmissions on uplink silent resources based on the switch indication in the TDRA table associated with PUSCH.

[0239] In other words, the terminal prioritizes the uplink silence on / off indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence on / off indication in the TDRA table associated with the PUSCH does it determine whether to silence PUSCH transmission on uplink silence resources based on the uplink silence on / off indication in the first signaling. This allows for flexible enabling or disabling of uplink silence based on a combination of various signaling methods.

[0240] Optionally, if the first signaling does not include an uplink silence switch indication, and the TDRA table associated with the PUSCH does not contain an uplink silence switch indication, the terminal may silence or not silence PUSCH transmissions on the uplink silence resource. Correspondingly, if the first signaling does not include an uplink silence switch indication, and the TDRA table associated with the PUSCH does not contain an uplink silence switch indication, the network device may not receive or may receive PUSCH transmissions on the uplink silence resource. Based on this optional approach, even if the network device does not add an uplink silence switch indication in the first signaling, the terminal can determine whether to silence PUSCH transmissions on the uplink silence resource.

[0241] As can be seen, based on the method described in Figure 8, network devices can flexibly configure whether the terminal silences PUSCH transmission on uplink silent resources in the first signaling according to communication requirements. Thus, even when there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal can flexibly determine whether to silence PUSCH transmission on uplink silent resources based on the uplink silence switch indication in the first signaling, which is more conducive to meeting actual communication needs.

[0242] Please refer to Figure 9, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0243] 901. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0244] Step 901 can be found in the description of step 601, and will not be repeated here.

[0245] 902. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0246] Step 902 can be found in the description of step 802, and will not be repeated here.

[0247] 903. If the terminal does not have an uplink mute switch indication in the TDRA table associated with PUSCH, it will mute or not mute the transmission of PUSCH on the uplink mute resource.

[0248] 904. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device will not receive or will receive PUSCH transmissions on the uplink silence resource.

[0249] 905. When the terminal has an uplink mute switch indication in the TDRA table associated with PUSCH, it mutes or does not mute the transmission of PUSCH on the uplink mute resource.

[0250] 906. When the network device has an uplink silence switch indication in the TDRA table associated with PUSCH, it will not receive or will receive PUSCH transmissions on uplink silence resources.

[0251] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it silences PUSCH transmissions on uplink silence resources. If the network device does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it does not receive PUSCH transmissions on uplink silence resources. If the terminal has an uplink silence switch indication in the TDRA table associated with the PUSCH, it silences PUSCH transmissions on uplink silence resources. If the network device has an uplink silence switch indication in the TDRA table associated with the PUSCH, it does not receive PUSCH transmissions on uplink silence resources.

[0252] In other words, regardless of whether there is an uplink silence switch indication in the TDRA table associated with PUSCH, the terminal always silences PUSCH transmission on uplink silence resources by default, i.e., the terminal always ignores the uplink silence switch indication in the TDRA table associated with PUSCH. This allows network devices more opportunities to measure mutual interference. Multiple measurements can help network devices obtain more accurate interference information, thereby improving communication performance. Furthermore, by defaulting to silencing PUSCH transmission on uplink silence resources, this helps save additional signaling overhead.

[0253] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will not silence PUSCH transmissions on uplink silence resources. If the network device does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will receive PUSCH transmissions on uplink silence resources. If the terminal has an uplink silence switch indication in the TDRA table associated with the PUSCH, it will not silence PUSCH transmissions on uplink silence resources. If the network device has an uplink silence switch indication in the TDRA table associated with the PUSCH, it will receive PUSCH transmissions on uplink silence resources.

[0254] In other words, regardless of whether there is an uplink silence switch indication in the TDRA table associated with PUSCH, the terminal defaults to never silencing PUSCH transmission on uplink silence resources; that is, the terminal always ignores the uplink silence switch indication in the TDRA table associated with PUSCH. This helps to reduce the impact on uplink data transmission performance. Furthermore, by defaulting to not silencing PUSCH transmission on uplink silence resources, it helps to save additional signaling overhead.

[0255] Please refer to Figure 10, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0256] 1001. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0257] Step 1001 can be found in the description of step 601, and will not be repeated here.

[0258] 1002. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0259] Step 1002 can be found in the description below step 802, and will not be repeated here.

[0260] 1003. If there is no uplink mute switch indication in the TDRA table associated with PUSCH, the terminal mutees or does not mute the transmission of PUSCH on the uplink mute resource.

[0261] 1004. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device will not receive or will receive PUSCH transmissions on the uplink silence resource.

[0262] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will silence the transmission of PUSCH on the uplink silence resource. If the network device does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will not receive the transmission of PUSCH on the uplink silence resource.

[0263] For example, if the terminal does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will not silence the transmission of PUSCH on the uplink silence resource. If the network device does not have an uplink silence switch indication in the TDRA table associated with the PUSCH, it will receive the transmission of PUSCH on the uplink silence resource.

[0264] 1005. If the terminal has an uplink silence switch indication in the TDRA table associated with PUSCH, it will silence or not silence the transmission of PUSCH on the uplink silence resource based on the switch indication in the TDRA table associated with PUSCH.

[0265] 1006. If the network device has an uplink silence switch indication in the TDRA table associated with PUSCH, it will not receive or will receive PUSCH transmissions on uplink silence resources based on the switch indication in the TDRA table associated with PUSCH.

[0266] In other words, the terminal prioritizes the uplink silence on / off indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence on / off indication in the TDRA table associated with the PUSCH will the terminal default to not silencing or silencing the PUSCH transmission on the uplink silence resource. By prioritizing the uplink silence on / off indication in the TDRA table associated with the PUSCH, the network device's initiative in enabling or disabling uplink silence is ensured.

[0267] Please refer to Figure 11, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0268] 1101. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an RRC-level uplink silence on / off indicator. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0269] Step 1101 can be found in the description of step 701, and will not be repeated here.

[0270] 1102. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0271] Step 1102 can be found in the description of step 802, and will not be repeated here.

[0272] 1103. If the first signaling includes an uplink silence switch indication and there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal silences or does not silence PUSCH transmission on the uplink silence resource based on the switch indication in the first signaling.

[0273] 1104. If the network device includes an uplink silence switch indication in the first signaling and there is no uplink silence switch indication in the TDRA table associated with PUSCH, it will not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the first signaling.

[0274] In this embodiment of the application, when the first signaling includes an uplink silence switch indication, and an uplink silence switch indication exists in the TDRA table associated with PUSCH, there are two possible implementation methods:

[0275] 1) Based on the switch indication in the first signaling, the terminal may mute or not mute the transmission of PUSCH on the uplink mute resource. Correspondingly, the network device may not receive or receive the transmission of PUSCH on the uplink mute resource based on the switch indication in the first signaling.

[0276] In other words, when the first signaling includes an uplink silence switch indication, regardless of whether the uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal always silences or does not silence PUSCH transmission on uplink silenced resources based on the switch indication in the first signaling. The terminal always ignores the uplink silence switch indication in the TDRA table associated with the PUSCH. Thus, when the first signaling includes an uplink silence switch indication, for CG PUSCH, the terminal can disregard the presence of an uplink silence switch in the TDRA table and determine whether to silence or not silence PUSCH transmission on uplink silenced resources solely based on the uplink silence switch indication in the first signaling, simplifying the terminal's implementation complexity. Simultaneously, it ensures that network devices use the uplink silence switch indication in the first signaling to indicate whether to perform uplink silence, which is beneficial for ensuring the flexible use of the uplink silence mechanism and meeting actual communication needs.

[0277] Optionally, if the first signaling does not include an uplink silence switch indication, the terminal silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information. Correspondingly, if the first signaling does not include an uplink silence switch indication, the network device does not receive or receives PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information. That is, the network device can add an uplink silence switch indication to the first signaling based on communication requirements. If the network device does not add an uplink silence switch indication to the first signaling, the terminal silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information. Therefore, based on this optional approach, even if the network device does not add an uplink silence switch indication to the first signaling, the terminal can flexibly determine whether to silence PUSCH transmission on uplink silence resources.

[0278] Optionally, if neither the first signaling nor the second configuration information includes an uplink silence switch indication, the terminal may silence or not silence PUSCH transmissions on uplink silence resources. Correspondingly, the network device may either not receive or receive PUSCH transmissions on uplink silence resources. Based on this optional approach, even if the network device does not add an uplink silence switch indication in the first signaling and second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silence resources.

[0279] 2) The terminal silences or does not silence PUSCH transmissions on uplink silent resources based on the switch indication in the TDRA table associated with PUSCH. Correspondingly, the network device does not receive or receives PUSCH transmissions on uplink silent resources based on the switch indication in the TDRA table associated with PUSCH.

[0280] In other words, the terminal prioritizes the uplink silence on / off indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence on / off indication in the TDRA table associated with the PUSCH does it determine whether to silence PUSCH transmission on uplink silence resources based on the uplink silence on / off indication in the first signaling. This allows for flexible enabling or disabling of uplink silence based on a combination of various signaling methods.

[0281] Optionally, if the first signaling does not include an uplink silence switch indication, and the uplink silence switch indication is not present in the TDRA table associated with the PUSCH, the terminal silences or does not silence PUSCH transmissions on uplink silence resources based on the switch indication in the second configuration information. If the first signaling does not include an uplink silence switch indication, and the uplink silence switch indication is not present in the TDRA table associated with the PUSCH, the network device does not receive or receives PUSCH transmissions on uplink silence resources based on the switch indication in the second configuration information. Based on this optional approach, even if the network device does not add an uplink silence switch indication in the first signaling, the terminal can flexibly determine whether to silence PUSCH transmissions on uplink silence resources.

[0282] Optionally, if the first signaling does not include an uplink silence switch indication, and the PUSCH-associated TDRA table does not contain an uplink silence switch indication, and the second configuration information does not include an uplink silence switch indication, the terminal may silence or not silence PUSCH transmissions on uplink silence resources. Accordingly, the network device may not receive or may receive PUSCH transmissions on uplink silence resources. Based on this optional approach, even if the network device does not add an uplink silence switch indication in the first signaling and second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silence resources.

[0283] As can be seen, based on the method described in Figure 11, when there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal can flexibly determine whether to silence the transmission of PUSCH on the uplink silence resource based on the uplink silence switch indication in the first signaling or the second configuration information, which is more conducive to meeting actual communication needs.

[0284] Please refer to Figure 12, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0285] 1201. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an RRC-level uplink silence on / off indicator. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0286] Step 1201 can be found in the description of step 701, and will not be repeated here.

[0287] 1202. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0288] Step 1202 can be found in the description below step 802, and will not be repeated here.

[0289] 1203. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal silences or does not silence the transmission of PUSCH on the uplink silence resource based on the switch indication in the second configuration information.

[0290] 1204. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device shall not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the second configuration information.

[0291] 1205. If the terminal has an uplink silence switch indication in the TDRA table associated with PUSCH, it will silence or not silence the transmission of PUSCH on the uplink silence resource based on the switch indication in the TDRA table associated with PUSCH.

[0292] 1206. If the network device has an uplink silent switch indication in the TDRA table associated with PUSCH, it will not receive or will receive PUSCH transmissions on the uplink silent resource based on the switch indication in the TDRA table associated with PUSCH.

[0293] In other words, the terminal prioritizes the uplink silence switch indication in the TDRA table associated with the PUSCH. Only when there is no uplink silence switch indication in the TDRA table associated with the PUSCH will the terminal silence or not silence the PUSCH transmission on the uplink silence resource based on the switch indication in the second configuration information. This allows for flexible enabling or disabling of uplink silence based on a combination of various signaling methods.

[0294] Optionally, if there is no uplink silence switch indication in the TDRA table associated with PUSCH, and the second configuration information does not include an uplink silence switch indication, the terminal may silence or not silence PUSCH transmissions on uplink silence resources. Correspondingly, the network device may not receive or may receive PUSCH transmissions on uplink silence resources. Based on this optional approach, even if the network device does not add an uplink silence switch indication in the second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silence resources.

[0295] Please refer to Figure 13, which is a flowchart illustrating an uplink silencing method provided in an embodiment of this application, wherein:

[0296] 1301. The network device sends first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an RRC-level uplink silence on / off indicator. Accordingly, the terminal can receive the first configuration information and the second configuration information.

[0297] Step 1301 can be found in the description of step 701, and will not be repeated here.

[0298] 1302. The network device sends a first signaling message to the terminal. This first signaling message is used to configure PUSCH transmission, and the PUSCH is a configuration authorization PUSCH. Accordingly, the terminal can receive this first signaling message.

[0299] Step 1302 can be found in the description of step 802, and will not be repeated here.

[0300] 1303. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the terminal silences or does not silence the transmission of PUSCH on the uplink silence resource based on the switch indication in the second configuration information.

[0301] 1304. If there is no uplink silence switch indication in the TDRA table associated with PUSCH, the network device shall not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the second configuration information.

[0302] 1305. If the terminal has an uplink silence switch indication in the TDRA table associated with PUSCH, it silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information.

[0303] 1306. If the network device has an uplink silence switch indication in the TDRA table associated with PUSCH, it shall not receive or receive PUSCH transmissions on uplink silence resources based on the switch indication in the second configuration information.

[0304] In other words, regardless of whether an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the terminal always silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information. That is, the terminal always ignores the uplink silence switch indication in the TDRA table associated with the PUSCH. Thus, even when an uplink silence switch indication exists in the second configuration information, for CG PUSCH, the terminal can disregard the presence of an uplink silence switch in the TDRA table and determine whether to silence or not transmit the PUSCH on uplink silence resources solely based on the uplink silence switch indication in the second configuration information, simplifying the terminal's implementation complexity. Simultaneously, it ensures that network devices use the uplink silence switch indication in the second configuration information to indicate whether to perform uplink silence, which is beneficial for ensuring the flexible use of the uplink silence mechanism and meeting actual communication needs.

[0305] Optionally, if the second configuration information does not include an uplink silencing switch indication, the terminal may silence or not silence PUSCH transmissions on uplink silencing resources. Correspondingly, the network device may not receive or may receive PUSCH transmissions on uplink silencing resources. Based on this optional approach, even if the network device does not add an uplink silencing switch indication in the second configuration information, the terminal can reasonably determine whether to silence PUSCH transmissions on uplink silencing resources.

[0306] Figure 14 is a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 14, the communication device 1400 may include modules or units for implementing the method embodiments described above. In one possible design, the communication device 1400 includes a processing unit 1402 and a communication unit 1403. Optionally, the communication device 1400 may further include a storage unit 1401 for storing device program code and / or data.

[0307] The communication device 1400 can be a terminal-side device in any of the embodiments corresponding to Figures 6 to 13 above, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0308] For example, in one embodiment, the communication unit 1403 is used for:

[0309] Receive first configuration information and second configuration information from the network device, the first configuration information being used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information being used to configure uplink muting resources; receive first signaling from the network device, the first signaling being used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission; and, if there is no uplink muting switch indication in the TDRA table associated with the PUSCH, not mute the transmission of PUSCH on the uplink muting resources.

[0310] In one possible embodiment, PUSCH is a configuration-authorized PUSCH; the communication unit 1403 is also used to: not silence the transmission of PUSCH on the uplink silence resource when there is an uplink silence switch indication in the TDRA table associated with the PUSCH.

[0311] For example, in one embodiment, the communication unit 1403 is used for:

[0312] The system receives first configuration information and second configuration information from a network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an uplink silence switch indication at the Radio Resource Control (RRC) level. The system receives first signaling from a network device, which is used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission. If there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the system silences or does not silence PUSCH transmission on uplink silence resources based on the switch indication in the second configuration information.

[0313] In one possible embodiment, the PUSCH is a configuration-authorized PUSCH; the communication unit 1403 is further configured to: mute or not mute the transmission of the PUSCH on the uplink mute resource based on the switch indication in the second configuration information, if there is an uplink mute switch indication in the TDRA table associated with the PUSCH.

[0314] In one possible embodiment, the communication unit 1403 is further configured to: mute or not mute the transmission of PUSCH on the uplink mute resource based on the switch indication in the TDRA table associated with PUSCH, if there is an uplink mute switch indication in the TDRA table associated with PUSCH.

[0315] In one possible embodiment, at least one of the one or more TDRA forms includes an uplink silence switch indication.

[0316] In one possible embodiment, the first signaling is a downlink control information (DCI) for activating or scheduling PUSCH transmission, and the first signaling is a second type of DCI; wherein, the PUSCH scheduled or activated by the first type of DCI is always non-silently transmitted on the uplink silent resource.

[0317] In one possible embodiment, the type of DCI for a scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

[0318] For example, in one embodiment, the communication unit 1403 is used for:

[0319] The system receives first configuration information and second configuration information from a network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink muting resources. The system also receives first signaling from a network device, which is used to configure uplink Physical Shared Channel (PUSCH) transmission. The PUSCH is a configured authorized PUSCH. If the first signaling includes an uplink muting switch indication, and there is no uplink muting switch indication in the TDRA table associated with the PUSCH, the system mutes or does not mute the transmission of the PUSCH on the uplink muting resources based on the switch indication in the first signaling.

[0320] In one possible embodiment, the communication unit 1403 is further configured to: mute or not mute the transmission of PUSCH on the uplink mute resource based on the switch indication in the first signaling, provided that the first signaling includes an uplink mute switch indication and an uplink mute switch indication exists in the TDRA table associated with the PUSCH.

[0321] In one possible embodiment, the communication unit 1403 is further configured to: mute or not mute the transmission of PUSCH on the uplink mute resource based on the switch indication in the TDRA table associated with PUSCH, if there is an uplink mute switch indication in the TDRA table associated with PUSCH.

[0322] In one possible embodiment, the communication unit 1403 is further configured to: mute or not mute the transmission of PUSCH on the uplink mute resource when the first signaling does not include an uplink mute switch indication and there is no uplink mute switch indication in the TDRA table associated with PUSCH.

[0323] In one possible embodiment, the second configuration information also includes an uplink silence switch indication at the RRC level.

[0324] In one possible embodiment, the communication unit 1403 is further configured to: mute or not mute the transmission of PUSCH on the uplink mute resource based on the switch indication in the second configuration information, provided that the first signaling does not include an uplink mute switch indication and there is no uplink mute switch indication in the TDRA table associated with PUSCH.

[0325] In one possible embodiment, when the communication device 1400 is a terminal or a communication module within a terminal, the function of the processing unit 1402 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 1403 can be implemented by transceiver circuitry.

[0326] In one possible embodiment, when the communication device 1400 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1402 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 1403 can be implemented by an interface circuit or data transceiver circuit on the aforementioned chip.

[0327] In one possible embodiment, when the communication device 1400 is a terminal or a processing module within a terminal, the function of the processing unit 1402 can be implemented by one or more processors. Specifically, the processor may include a GPU, or a system-on-a-chip (SoC) chip or a SIP chip containing a GPU. The function of the communication unit 1403 can be implemented by transceiver circuitry.

[0328] In one possible embodiment, when the communication device 1400 is a circuit or chip in a terminal responsible for processing functions, such as a GPU or a system-on-a-chip (SoC) or SIP chip containing a GPU, the function of the processing unit 1402 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 1403 can be implemented by interface circuitry or data transceiver circuitry on the aforementioned chip.

[0329] The communication device 1400 can be a network-side device in any of the embodiments corresponding to Figures 6 to 13 above, such as a network device or a communication module in a network device, or a circuit or chip in a network device that is responsible for communication functions.

[0330] For example, in one embodiment, the communication unit 1403 is used for:

[0331] Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Send first signaling to the terminal. The first signaling is used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission. If there is no uplink silent switch indication in the TDRA table associated with the PUSCH, receive PUSCH transmission on the uplink silent resources.

[0332] In one possible embodiment, PUSCH is a configuration-authorized PUSCH; the communication unit 1403 is also configured to: receive the transmission of PUSCH on the uplink silent resource when there is an uplink silent switch indication in the TDRA table associated with the PUSCH.

[0333] For example, in one embodiment, the communication unit 1403 is used for:

[0334] Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. The second configuration information also includes an uplink silent switch indication at the Radio Resource Control (RRC) level. Send a first signaling to the terminal. The first signaling is used to configure, activate, or schedule uplink Physical Shared Channel (PUSCH) transmission. If there is no uplink silent switch indication in the TDRA table associated with the PUSCH, based on the switch indication in the second configuration information, do not receive or receive PUSCH transmission on the uplink silent resources.

[0335] In one possible embodiment, PUSCH is a configuration-authorized PUSCH; the communication unit 1403 is further configured to: if there is an uplink silence switch indication in the TDRA table associated with the PUSCH, based on the switch indication in the second configuration information, not receive or receive the transmission of PUSCH on the uplink silence resource.

[0336] In one possible embodiment, the communication unit 1403 is further configured to: if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, to either not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

[0337] In one possible embodiment, at least one of the one or more TDRA forms includes an uplink silence switch indication.

[0338] In one possible embodiment, the first signaling is a downlink control information (DCI) for activating or scheduling PUSCH transmission, and the first signaling is a second type of DCI; wherein, the PUSCH scheduled or activated by the first type of DCI is always non-silently transmitted on the uplink silent resource.

[0339] In one possible embodiment, the type of DCI for a scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

[0340] For example, in one embodiment, the communication unit 1403 is used for:

[0341] Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Send first signaling to the terminal. The first signaling is used to configure uplink Physical Shared Channel (PUSCH) transmission. The PUSCH is a configured authorized PUSCH. If the first signaling includes an uplink silent switch indication, and there is no uplink silent switch indication in the TDRA table associated with the PUSCH, then based on the switch indication in the first signaling, either PUSCH transmission is not received or is received on the uplink silent resources.

[0342] In one possible embodiment, the communication unit 1403 is further configured to: in the case that the first signaling includes an uplink silence switch indication and an uplink silence switch indication exists in the TDRA table associated with the PUSCH, based on the switch indication in the first signaling, either not receive or receive the transmission of PUSCH on the uplink silence resource.

[0343] In one possible embodiment, the communication unit 1403 is further configured to: if an uplink silence switch indication exists in the TDRA table associated with the PUSCH, to either not receive or receive PUSCH transmissions on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

[0344] In one possible embodiment, the communication unit 1403 is further configured to: not receive or receive PUSCH transmissions on uplink silent resources when the first signaling does not include an uplink silence switch indication and there is no uplink silence switch indication in the TDRA table associated with PUSCH.

[0345] In one possible embodiment, the second configuration information also includes an uplink silence switch indication at the RRC level.

[0346] In one possible embodiment, the communication unit 1403 is further configured to: not receive or receive PUSCH transmissions on the uplink silent resource based on the switch indication in the second configuration information, provided that the first signaling does not include an uplink silence switch indication and there is no uplink silence switch indication in the TDRA table associated with PUSCH.

[0347] It is understood that the division of units in the above-described device is merely a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated onto a single physical entity, or distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for specific applications, but such implementations should not be considered beyond the scope of this application.

[0348] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0349] In one example, storage unit 1401 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0350] As shown in Figure 15, the communication device 1500 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input / output interface. Optionally, the communication device 1500 may also include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions.

[0351] When the communication device 1500 is used to implement the method shown in any one of Figures 6 to 13, the processor 1510 is used to implement the function of the processing unit 1402, and the interface circuit 1520 is used to implement the function of the communication unit 1403.

[0352] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is sent to the terminal by the network device; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is sent to the network device by the terminal.

[0353] When the aforementioned communication device is a module applied to a network device, the network device module implements the functions of the network device in the above method embodiments. The network device module receives information from other modules (such as a radio frequency module or antenna) in the network device, which is information sent by the terminal to the network device; or, the network device module sends information to other modules (such as a radio frequency module or antenna) in the network device, which is information sent by the network device to the terminal. Here, the network device module can be the baseband chip of the network device, or a DU (Digital Unit) or other modules. The DU can be a DU under an Open Radio Access Network (O-RAN) architecture.

[0354] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0355] It is understood that the processor in the embodiments of this application can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0356] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, optical discs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an application-specific integrated circuit (ASIC). Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0357] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0358] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0359] In this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C. It is understood that the various numerical designations involved in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above processes does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. An uplink silencing method, characterized in that, The method includes: Receive first configuration information and second configuration information from the network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Receive a first signaling from a network device, the first signaling being used to configure, activate, or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink mute switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is not muted on the uplink mute resource.

2. The method according to claim 1, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink mute switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is not muted on the uplink mute resource.

3. An uplink silencing method, characterized in that, The method includes: Receive first configuration information and second configuration information from the network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Receive a first signaling from a network device, the first signaling being used to configure, activate, or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink mute switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is muted on the uplink mute resource.

4. The method according to claim 3, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink mute switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is muted on the uplink mute resource.

5. An uplink silencing method, characterized in that, The method includes: The system receives first configuration information and second configuration information from a network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an uplink silence on / off indicator at the Radio Resource Control (RRC) level. Receive a first signaling from a network device, the first signaling being used to configure, activate, or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information.

6. The method according to claim 5, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information.

7. The method according to claim 1, 3, or 5, characterized in that, The method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

8. The method according to any one of claims 1 to 7, characterized in that, At least one of the one or more TDRA forms includes an uplink silent switch indication.

9. The method according to any one of claims 1 to 8, characterized in that, The first signaling is a downlink control information (DCI) used to activate or schedule PUSCH transmission, and the first signaling is a second type of DCI; Among them, PUSCH scheduled or activated by the first type of DCI is always non-silent on the uplink silent resource.

10. The method according to claim 9, characterized in that, The type of DCI for a scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

11. An uplink silencing method, characterized in that, The method includes: Receive first configuration information and second configuration information from the network device. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Receive a first signaling message from a network device, the first signaling message being used to configure uplink physical shared channel (PUSCH) transmission; the PUSCH is a configuration licensed PUSCH. If the first signaling includes an uplink silence switch indication, and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the first signaling.

12. The method according to claim 11, characterized in that, The method further includes: If the first signaling includes an uplink silence switch indication, and an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the first signaling.

13. The method according to claim 11, characterized in that, The method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the TDRA table associated with the PUSCH.

14. The method according to any one of claims 11 to 13, characterized in that, The method further includes: If the first signaling does not include an uplink mute switch indication, and there is no uplink mute switch indication in the TDRA table associated with the PUSCH, then the transmission of the PUSCH is either muted or not muted on the uplink mute resource.

15. The method according to any one of claims 11 to 13, characterized in that, The second configuration information also includes an uplink silence switch indication at the RRC level.

16. The method according to claim 15, characterized in that, The method further includes: If the first signaling does not include an uplink silence switch indication, and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is silenced or not silenced on the uplink silence resource based on the switch indication in the second configuration information.

17. An uplink silencing method, characterized in that, The method includes: Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Send a first signaling message to the terminal, the first signaling message being used to configure, activate or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH is received on the uplink silence resource.

18. The method according to claim 17, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH is received on the uplink silence resource.

19. An uplink silencing method, characterized in that, The method includes: Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Send a first signaling message to the terminal, the first signaling message being used to configure, activate or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH will not be received on the uplink silence resource.

20. The method according to claim 19, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the transmission of the PUSCH will not be received on the uplink silence resource.

21. An uplink silencing method, characterized in that, The method includes: Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silence resources. The second configuration information also includes an uplink silence on / off indicator at the Radio Resource Control (RRC) level. A first signaling is sent to the terminal, the first signaling being used to configure, activate, or schedule uplink physical shared channel (PUSCH) transmission; If there is no uplink silence switch indication in the TDRA table associated with the PUSCH, the transmission of the PUSCH will not be received or will be received on the uplink silence resource based on the switch indication in the second configuration information.

22. The method according to claim 21, characterized in that, The PUSCH is a configuration authorization PUSCH; the method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, the PUSCH transmission will not be received or will be received on the uplink silence resource based on the switch indication in the second configuration information.

23. The method according to claim 17, 19, or 21, characterized in that, The method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, then based on the switch indication in the TDRA table associated with the PUSCH, either the transmission of the PUSCH is not received or is received on the uplink silence resource.

24. The method according to any one of claims 17 to 23, characterized in that, At least one of the one or more TDRA forms includes an uplink silent switch indication.

25. The method according to any one of claims 17 to 24, characterized in that, The first signaling is a downlink control information (DCI) used to activate or schedule PUSCH transmission, and the first signaling is a second type of DCI; Among them, PUSCH scheduled or activated by the first type of DCI is always non-silent on the uplink silent resource.

26. The method according to claim 25, characterized in that, The type of DCI for a scheduled or activated PUSCH is related to one or more of the following: the DCI format, the search space in which the DCI resides, and the set of control resources associated with the search space in which the DCI resides.

27. An uplink silencing method, characterized in that, The method includes: Send first configuration information and second configuration information to the terminal. The first configuration information is used to configure one or more Time Domain Resource Allocation (TDRA) tables, and the second configuration information is used to configure uplink silent resources. Send a first signaling message to the terminal, the first signaling message being used to configure uplink physical shared channel (PUSCH) transmission; the PUSCH is a configuration licensed PUSCH. If the first signaling includes an uplink silence switch indication, and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, then based on the switch indication in the first signaling, the transmission of the PUSCH is either not received or received on the uplink silence resource.

28. The method according to claim 27, characterized in that, The method further includes: If the first signaling includes an uplink silence switch indication, and an uplink silence switch indication exists in the TDRA table associated with the PUSCH, then based on the switch indication in the first signaling, the transmission of the PUSCH is either not received or received on the uplink silence resource.

29. The method according to claim 27, characterized in that, The method further includes: If an uplink silence switch indication exists in the TDRA table associated with the PUSCH, then based on the switch indication in the TDRA table associated with the PUSCH, either the transmission of the PUSCH is not received or is received on the uplink silence resource.

30. The method according to any one of claims 27 to 29, characterized in that, The method further includes: If the first signaling does not include an uplink silence switch indication, and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, then the transmission of the PUSCH is not received or is received on the uplink silence resource.

31. The method according to any one of claims 27 to 29, characterized in that, The second configuration information also includes an uplink silence switch indication at the RRC level.

32. The method according to claim 31, characterized in that, The method further includes: If the first signaling does not include an uplink silence switch indication, and there is no uplink silence switch indication in the TDRA table associated with the PUSCH, then based on the switch indication in the second configuration information, the transmission of the PUSCH is either not received or received on the uplink silence resource.

33. A communication device comprising a module for performing the method as claimed in any one of claims 1 to 16, or comprising a module for performing the method as claimed in any one of claims 17 to 32.

34. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 16 through logic circuits or executable code instructions, or the processor is used to implement the method as described in any one of claims 17 to 32 through logic circuits or executable code instructions.

35. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 16, or implement the method as described in any one of claims 17 to 32.

36. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1 to 16, or when the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 17 to 32.

Images