Indication of uplink silence

Abstract

Embodiments of the present disclosure relate to uplink muting. In one aspect, a terminal device receives downlink control information (DCI) for uplink (UL) transmissions that overlap with an uplink (UL) resource muting pattern. The DCI includes indication information related to UL silence for UL transmission. The terminal device then determines whether to perform UL muting for the UL transmission based on the indication information. The terminal device performs the UL transmission based on the determination.

Description

Technical Field

[0001] Various example embodiments relate to the field of communications, and more specifically to terminal devices, network devices, methods, apparatuses, and computer-readable storage media for indicating uplink silence. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by, for example, 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards are the so-called 5G (fifth generation) and 5G-Advanced (5G-A) standards provided by 3GPP. Summary of the Invention

[0004] In general, the exemplary embodiments of this disclosure provide a scheme for an indication of uplink silence, and in particular for a dynamic indication of the applicability of uplink silence.

[0005] In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive downlink control information (DCI) for a UL transmission that overlaps with an uplink (UL) resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; determine, based on the indication information, whether to perform UL silence for the UL transmission; and perform the UL transmission based on the determination.

[0006] In a second aspect, a network device is provided. The network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: transmit downlink control information (DCI) to an end device for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and receive UL transmissions from the end device.

[0007] In a third aspect, a method is provided. The method includes: receiving downlink control information (DCI) for a UL transmission that overlaps with an uplink (UL) resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; determining, based on the indication information, whether to perform UL silence for the UL transmission; and performing the UL transmission based on the determination.

[0008] In a fourth aspect, a method is provided. The method includes: transmitting downlink control information (DCI) to a terminal device for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and receiving the UL transmissions from the terminal device.

[0009] In a fifth aspect, an apparatus is provided. The apparatus includes: components for receiving downlink control information (DCI) for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmissions; components for determining, based on the indication information, whether to perform UL silence for the UL transmissions; and components for performing UL transmissions based on the determination.

[0010] In a sixth aspect, an apparatus is provided. The apparatus includes: components for transmitting downlink control information (DCI) to a terminal device, the DCI being for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and components for receiving UL transmissions from the terminal device.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, including program instructions for causing a device to perform at least the methods of the third or fourth aspect described above.

[0012] Eighthly, a computer program is provided, including instructions that, when executed by a device, cause the device to perform at least the methods of the third or fourth aspect described above.

[0013] A ninth aspect provides a terminal device. The terminal device includes: a receiving circuitry configured to receive downlink control information (DCI) for UL transmissions overlapping with an uplink (UL) resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmissions; a determining circuitry configured to determine, based on the indication information, whether to perform UL silence for the UL transmissions; and an executing circuitry configured to perform the UL transmissions based on the determination.

[0014] A tenth aspect provides a network device. The network device includes: a transmission circuitry configured to transmit downlink control information (DCI) to an end device, the DCI being for UL transmissions overlapping with an uplink (UL) resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and a receiving circuitry configured to receive UL transmissions from the end device.

[0015] It should be understood that the summary portion of this disclosure is not intended to identify key or essential features of the embodiments thereof, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0017] Figure 1A An example network environment in which example embodiments of this disclosure may be implemented is shown;

[0018] Figure 1B Examples of SBFD and non-SBFD time slots are shown;

[0019] Figure 1C An example of co-channel cross-link interference type is shown in the example network environment shown in Figure 1;

[0020] Figure 1D An example of UL resource silencing on PUSCH is shown;

[0021] Figure 1E Examples of spectral efficiency loss due to UL silencing are shown for different PUSCH durations and for 1 or 2 OFDM symbol silencing.

[0022] Figure 2 A flowchart illustrating a process for dynamic indication of uplink silence according to some embodiments of the present disclosure is shown;

[0023] Figure 3 Another flowchart illustrates a process for dynamic indication of uplink silence according to some embodiments of this disclosure;

[0024] Figure 4 Another flowchart illustrates a process for dynamic indication of uplink silence according to some embodiments of this disclosure;

[0025] Figure 5 Another flowchart illustrates a process for dynamic indication of uplink silence according to some embodiments of this disclosure;

[0026] Figure 6 Another flowchart illustrates a process for dynamic indication of uplink silence according to some embodiments of this disclosure;

[0027] Figure 7 Another flowchart illustrates a process for dynamic indication of uplink silence according to some embodiments of this disclosure;

[0028] Figure 8A flowchart is shown illustrating a method implemented at a terminal device according to some embodiments of the present disclosure;

[0029] Figure 9 A flowchart illustrating a method implemented at a network device according to some embodiments of the present disclosure is shown;

[0030] Figure 10 A simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure is shown; and

[0031] Figure 11 A block diagram of an example computer-readable medium according to some embodiments of the present disclosure is shown.

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

[0033] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

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

[0035] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is to be noted that those skilled in the art will understand, whether explicitly described or not, that such a feature, structure, or characteristic can be combined with other embodiments.

[0036] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0037] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should be further understood that the terms “comprising,” “including,” “having,” “containing,” “comprise,” and / or “containing” as used herein specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, wherein the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0038] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementations only (such as implementations only in analog / or digital circuit systems) and (b) Combinations of hardware circuitry and software, for example (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware and (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories working together to enable a device such as a mobile phone or server to perform various functions) and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions of (multiple) microprocessors that require software (e.g., firmware) for operation (but may be absent when no software is required for operation).

[0039] This definition of circuit system applies to all instances of the term as used in this application (including any claim). As another example, as used herein, the term circuit system also encompasses implementations of hardware circuitry or processors (or processors) alone, or a portion thereof, and their accompanying software and / or firmware. The term circuit system also encompasses, for example and as applicable to specific claim elements, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0040] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G), 5G-A (5G-Advanced) communication protocols, and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be communication technologies and systems that embody future types of this disclosure. This disclosure should not be construed as limiting its scope to the aforementioned systems.

[0041] As used herein, “network device” refers to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology used, network device may refer to a base station (BS) or access point (AP) (e.g., Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB)), remote radio unit (RRU), radio head (RH), remote radio head (RRH), relay node, low-power node (such as femtosecond, picosecond), etc.

[0042] The term "terminal device" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and recycle bins, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0043] Figure 1A An example network environment 100A in which exemplary embodiments of the present disclosure may be implemented is shown. Environment 100A (which may be part of a communication network) includes terminal devices 121-126 and network devices 111-113. Figure 1A As shown, terminal devices 121 and 122 are within the coverage area of ​​network device 111 (cell 131), terminal devices 123 and 124 are within the coverage area of ​​network device 112 (cell 132), and terminal devices 123 and 124 are within the coverage area of ​​network device 112 (cell 133). Cells 132 and 133 are neighboring cells of cell 131.

[0044] It should be understood that the number of devices is for illustrative purposes only and does not imply any limitation. Environment 100A may include any suitable number of terminal devices and network devices suitable for implementing embodiments of this disclosure.

[0045] Communication in the communication environment 100A can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local area network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0046] 3GPP 5G NR currently supports two duplex modes: FDD for paired bands and TDD for unpaired bands. In TDD, the uplink and downlink phases are separated in the time domain. Depending on the TDD radio frame configuration under consideration, this can introduce unwanted latency, potentially reducing coverage and capacity. This is further exacerbated in TDD deployments due to the lower dynamism provided by scheduling; that is, in practice, the time slot structure is fixed and does not change very frequently. Furthermore, 5G NR TDD deployments focus on ensuring sufficient capacity for the required downlink traffic. This can result in a rather limited duration of uplink bandwidth in TDD.

[0047] Inspired by this, 3GPP has completed the research item in Rel-18 and confirmed a work item in Rel-19 concerning the evolution of duplex operation in NR to address the aforementioned challenges. One goal is to allow gNBs to simultaneously perform DL transmission and UL reception on different physical resource blocks (PRBs) / subbands within unpaired wideband NR carriers. In some embodiments of this disclosure, we refer to this as Subband Non-overlapping Full-Duplex (SBFD). In other sources, this duplexing scheme is also referred to as Cross-Divided Duplex (xDD) or Flexible Duplex (FDU).

[0048] Figure 1B Examples of SBFD and non-SBFD time slots according to some embodiments of this disclosure are shown. From the above description of SBFD operation, it can be observed that, as shown in Figure B, there are two time slot types for both DL and UL transmissions: The oSBFD time slot contains multiple non-overlapping DL subbands corresponding to DL resource 150-1 and multiple UL subbands corresponding to UL resource 150-2. o Non-SBFD time slots, during which the entire frequency band is used for either DL or UL (i.e., conventional / full DL / UL time slots).

[0049] In the SBFD time slot, the guard band, including guard resource 150-3, is expected to be placed between the DL resource block (RB) and the UL resource block. This provides better isolation between UL and DL transmissions and is expected to be crucial for reducing self-interference (due to gNB's own DL transmissions and gNB's own UL receptions) and the impact of cross-link interference (CLI) between UE-to-UE links and gNB-to-gNB links.

[0050] Figure 1C Examples of co-channel cross-link interference types in SBFD deployments according to some embodiments of this disclosure are shown. SBFD can introduce a new type of CLI, namely co-channel inter-subband CLI from non-overlapping frequency resources. Figure 1C As shown, cells 132 and 133 are neighboring cells of cell 131. Cell 132 has the same frequency domain allocation as cell 131. Cell 131 has a different frequency domain allocation than cell 133. Therefore, in a scenario of full-duplex operation for non-overlapping sub-band frequency resources with the same frequency domain allocation (e.g., cell 132 has the same frequency domain allocation as cell 131), cross-link interference can be better classified according to the interference source as follows: (1) gNB self-interference (140-1). (2) Intra-cell UE-to-UE common channel subband CLI (140-2). (3) Inter-UE-UE common channel subband CLI (140-3). (4) gNB to gNB common channel subband CLI (140-4).

[0051] In addition to these new CLI types, in cases where neighboring cells have different frequency domain allocations (e.g., cell 132 and cell 133 have different frequency domain allocations), the system may also suffer from co-channel CLIs transmitted on overlapping frequency resources: (5) GNB-to-GNB inter-channel CLI (140-5) from overlapping frequency resources. (6) UE-UE inter-cell common channel CLI (140-6) from overlapping frequency resources.

[0052] Several techniques for handling gNB-to-gNB CLI (such as 140-5 and / or 140-4) are proposed, among which UL resource muting is proposed to ensure that gNB-to-gNB CLI measurements and / or gNB-to-gNB channel measurements at the victim gNB are protected from UL signal interference. Regarding uplink muting (UL muting), two approaches have been discussed: transparent and non-transparent.

[0053] Transparent silence relies on gNB scheduling without specific instructions to the UE, while the non-transparent approach performs RE-level silence via gNB instructions for a specific silence mode to be applied to its UL transmission.

[0054] Specifically, regarding UL resource silencing, the indication / determination of UL resource silencing for the Physical Uplink Shared Channel (PUSCH) based on semi-static configuration assumes a combo-2 for both DFT-S-OFDM and CP-OFDM in each allocated Physical Resource Block (PRB), and at most two symbols in the time domain. It should be noted that no new DCI field / Media Access Control element (MAC CE) is introduced. Furthermore, UL resource silencing for PUSCH includes the determination of uplink control information (UCI) in the symbols in the case of silencing the RE (resource element).

[0055] An uplink control information (UCI) message may consist of at least one of the following: (1) Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) (2) Channel State Information (CSI), which consists of CSI Part 1 and CSI Part 2. The former has a fixed payload size and is used to identify the number of information bits in the latter. Therefore, CSI Part 1 must be fully transmitted before CSI Part 2. (3) Scheduling Request (SR)

[0056] UCI messages can be encoded and transmitted via PUCCH, or multiplexed on PUSCH. Only HARQ-ACK and CSI are multiplexed on PUSCH. SR is not multiplexed on PUSCH because PUSCH can transmit Buffer Status Reports (BSRs), which contain more detailed information about the UE's uplink buffer status than SRs.

[0057] To calculate the number of coded modulation symbols per layer for each UCI type, there is a step of calculating the number of coded modulation symbols per layer for each UCI type before the step of mapping the coded modulation symbols to REs. The UE uses a higher-layer parameter called the β parameter (or beta offset) to determine the amount of resources (implemented in terms of the number of coded modulation symbols per layer) within the PUSCH dedicated to UCI in the case of multiplexing.

[0058] In some examples, in order to determine the number of encoded bits dedicated to UCI and how to account for REs due to uplink silence, there is a method using two different beta offsets: one beta offset for signs that conflict with the UL silence mode and one beta offset for signs that do not conflict with the UL silence mode.

[0059] Figure 1D An example of UL resource silencing on PUSCH is shown. It is assumed that UL resource silencing for PUSCH is based on a semi-static configuration and that each allocated physical resource block (PRB) has a combo-2 for both DFT-S-OFDM and CP-OFDM, and at most 2 symbols in the time domain.

[0060] Figure 1D The following scenarios, considered in some embodiments of this disclosure, are illustrated, where the UL silent mode is configured to occur periodically. When UL silent is expected, and if a PUSCH transmission 160-1 overlaps with the UL silent mode, data will be rate-matched around the silent resource (e.g., silent resource 160-2). PUSCH transmission 160-1 may include remaining resources (160-3) for data, reference signals, and UCI. However, there may be cases where the gNB prefers to prioritize UL transmissions over UL silent (and subsequent gNB-to-gNB CLIs (such as 140-4 and 140-5) / channel measurements). This could be if the gNB wants to maximize the number of REs dedicated to PUSCH. Note that a consensus has been reached regarding comb-2 silent, where one out of every two subcarriers is silent in a given symbol, which can result in a large loss of spectral efficiency (which will be referred to later). Figure 1E (Describe it).

[0061] Figure 1E Examples of spectral efficiency loss due to UL silencing are shown for different PUSCH durations and for silencing 1 or 2 OFDM symbols.

[0062] Curve 170-1 represents the silence of one OFDM symbol, and curve 170-2 represents the silence of two OFDM symbols. From Figure 1EIt can be seen that silencing one or two OFDM symbols can lead to a large loss of spectral efficiency. In particular, if the number of symbols allocated for PUSCH is low, the loss of spectral efficiency is extremely high.

[0063] To address this issue, some embodiments of this disclosure propose a method for the gNB to dynamically instruct the UE on signal transmission silence modes (e.g., dynamic indication of uplink silence applicability). In other words, it proposes a UL grant method to instruct the UE that pre-configured (and periodic) UL silence should not be applied to scheduled PUSCHes. In some scenarios, the gNB can provide the UE with a set of rules indicating that UL silence should be applied. For spectral efficiency considerations, the gNB can utilize a DCI with dynamic indication to stop the application of UL silence. This dynamic indication is useful when the gNB prefers to prioritize UL reception over measuring gNB-to-gNB CLI (such as 140-5 and / or 140-4) and / or estimating the gNB-to-gNB channel.

[0064] Now for reference Figure 2 This illustrates a process 200 for dynamic indication of uplink silence according to an embodiment of the present disclosure. For purposes of discussion, reference will be made to... Figure 1A and Figure 1C Describe the process 200. Although Figure 2 The interaction between terminal device 121 and network device 111 is shown, but it will be understood that process 200 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0065] Terminal device 121 can receive a DCI from network device 111 receiving 210, which is for UL transmissions overlapping with UL resource silence modes. This DCI includes indication information related to UL silence for UL transmissions. See later. Figures 4-7 Describe the details of the instruction information.

[0066] Terminal device 121 can determine, based on indication information, whether 215 determines whether to perform UL silence for UL transmission. (See later...) Figures 4-7 Describe the specific details.

[0067] Terminal device 121 can perform UL transmission related to PUSCH 220 to network device 111.

[0068] In this way, network devices can utilize the dynamic indication of UL silent mode to dedicate more resource elements (REs) to PUSCH transmission. This can reduce spectral efficiency loss and improve the efficiency of UL transmission.

[0069] Now for reference Figure 3 This illustrates a process 300 for dynamic indication of uplink silence according to another embodiment of this disclosure. For discussion purposes, reference will be made to... Figure 1A and Figure 1C Describe the process 300. Although Figure 3 The interaction between terminal device 121 and network device 111 is shown, but it is understood that process 300 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0070] Before receiving the DCI with indication information, terminal device 121 can receive 305SBFD configuration, UL resource silent mode configuration, and PUSCH configuration from network device 111. The PUSCH configuration (e.g., PUSCH RRC configuration) may include a beta offset field.

[0071] Regarding the beta offsets supported in the protocol, there are two distinct UE behaviors. Specifically, as part of the PUSCH configuration, which can be associated with the betaOffsets field, the UE can be configured to be semi-static and dynamic. The PUSCH configuration can be defined in TS 38.331 as follows:

[0072] Terminal device 121 can receive 310DCI, which is for UL transmissions (PUSCH) that overlap with UL resource silence mode. The DCI includes indication information on whether UL silence should be applied.

[0073] Terminal device 121 can determine whether 315 should apply UL silence for a given PUSCH based on the information in the DCI. Furthermore, terminal device 121 can map data (and UCI, if any) bits to available resources based on the DCI.

[0074] Then, terminal device 121 can perform a 320UL transmission (PUSCH) to network device 111.

[0075] There are two options for the instruction information. Option 1: The instruction information may include new or additional fields for reusing DCI. Option 2: The indication information may include reused fields in the DCI (e.g., existing fields).

[0076] Compared to Option 1, Option 2 avoids introducing a new DCI field, making it more suitable for the 3GPP protocol. It remains unclear whether the above protocol description (avoiding a new DCI field / MAC CE) applies only to UL silent activation / configuration or also to deactivation (as proposed in Option 1). However, both Option 1 and Option 2 can achieve dynamic indication of uplink silence.

[0077] In cases where the indication information may include reused fields (e.g., existing fields). Now refer to Figure 4 This illustrates a process 400 for dynamic indication of uplink silence according to another embodiment of this disclosure. For discussion purposes, reference will be made to... Figure 1A and Figure 1C Describe process 400. Although Figure 4 The interaction between terminal device 121 and network device 111 is shown, but it will be understood that process 400 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0078] Before receiving the DCI, which includes indication information such as reuse fields (existing fields of the DCI), the terminal device 121 can receive the 405SBFD configuration, the UL resource silent mode configuration, and the PUSCH configuration from the network device 111. The PUSCH configuration (e.g., the PUSCH RRC configuration) may include a semi-static beta offset configuration. This PUSCH configuration may indicate a semi-static beta offset.

[0079] After receiving the PUSCH configuration, SBFD configuration, and UL resource silent mode configuration, including the semi-static beta offset configuration, from network device 111, terminal device 121 can be configured with the semi-static beta offset configuration and UL silent mode. Terminal device 121 can always expect (and read) the beta offset indicator field in the DCI.

[0080] Then, terminal device 121 can receive 410DCI from network device 111, which is for UL transmissions that overlap with UL resource silence mode. The DCI includes a beta offset indicator field for indicating whether UL silence will be applied to UL transmissions.

[0081] The beta offset indicator field can include a single bit. This bit can have two distinct values, such as 1 or 0.

[0082] Terminal device 121 can determine whether UL silence is performed for UL transmission based on indication information (beta offset indicator). As an example, the beta offset indicator may include one bit. Terminal device 121 may apply UL silence when the beta offset indicator value is 1, and not apply UL silence when the beta offset indicator value is 0.

[0083] The beta offset indicator field can be defined in DCI format 0_1. This DCI format 0_1 ​​can be defined as follows:

[0084] It should be understood that in some embodiments, terminal device 121 may apply UL silence when the beta offset indicator value is 0, and not apply UL silence when the beta offset indicator value is 1.

[0085] Terminal device 121 can perform 420UL transmission. For example, terminal device 121 can map data (and UCI (if any)) bits to available resources according to DCI and perform UL transmission (PUSCH).

[0086] Now for reference Figure 5 This illustrates a process 500 for dynamic indication of uplink silence according to another embodiment of this disclosure. For discussion purposes, reference will be made to... Figure 1A and Figure 1C Describe the process 500. Although... Figure 5 The interaction between terminal device 121 and network device 111 is shown, but it is understood that process 500 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0087] Before receiving the DCI, which includes indication information such as reuse fields (existing fields of the DCI), the terminal device 121 may receive the 505SBFD configuration, the UL resource silent mode configuration, and the PUSCH configuration from the network device 111. The PUSCH configuration (e.g., the PUSCH RRC configuration) may include a dynamic beta offset configuration.

[0088] After receiving the PUSCH configuration, SBFD configuration, and UL resource silent mode configuration, including the dynamic beta offset configuration, from network device 111, terminal device 121 can be configured with the dynamic beta offset configuration and UL silent mode. Terminal device 121 can expect (and read) the beta offset indicator field in the DCI of the scheduled PUSCH.

[0089] Then, terminal device 121 can receive 510DCI from network device 111, which is for UL transmissions that overlap with UL resource silence mode. The DCI includes a beta offset indicator field for indicating whether UL silence will be applied to UL transmissions.

[0090] The beta offset indicator field may include a first beta offset indicator value and a second beta offset indicator value. The first portion of the bit sequence in the DCI indicates the first beta offset indicator value. The second portion of the bit sequence in the DCI indicates the second beta offset indicator value. The first and second beta offset indicator values ​​are included in the beta offset indicator field of the DCI.

[0091] In some embodiments, one of the first beta offset indicator values ​​is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode, and the other of the first beta offset indicator values ​​is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0092] In some embodiments, the second beta offset indicator value is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode, and another of the first or second beta offset indicator values ​​is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0093] Terminal device 121 can determine whether 515 performs UL silencing for UL transmissions based on indication information (beta offset indicator). In some embodiments, terminal device 121 may not apply UL silencing when the first beta offset indicator value is equal to the second beta offset indicator value (i.e., terminal device 121 assumes no silencing is applied to the scheduled PUSCH), and terminal device 121 may apply UL silencing when the first beta offset indicator value is different from the second beta offset indicator value (i.e., terminal device 121 assumes UL silencing is applied to the scheduled PUSCH). In this way, if the beta offset indicator value for overlapping symbols is the same as the beta offset indicator value for non-overlapping symbols, network device 111 can implicitly instruct terminal device 121 not to apply silencing.

[0094] Terminal device 121 can perform 520 UL transmission. For example, terminal device 121 can map data (and UCI (if any)) bits to available resources according to DCI and perform UL transmission (PUSCH).

[0095] Now for reference Figure 6This illustrates a process 600 for dynamic indication of uplink silence according to another embodiment of this disclosure. For discussion purposes, reference will be made to... Figure 1A and Figure 1C Describe the process 600. Although... Figure 6 The interaction between terminal device 121 and network device 111 is shown, but it is understood that process 600 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0096] Before receiving the DCI, which includes indication information such as reuse fields (existing fields of the DCI), the terminal device 121 can receive the 605SBFD configuration, the UL resource silent mode configuration, and the PUSCH configuration from the network device 111. The PUSCH configuration (e.g., the PUSCH RRC configuration) may include a dynamic beta offset configuration. The dynamic beta offset configuration can indicate a dynamic beta offset.

[0097] After receiving the PUSCH configuration, SBFD configuration, and UL resource silent mode configuration, including the dynamic beta offset configuration, from network device 111, terminal device 121 can be configured with the dynamic beta offset configuration and UL silent mode. Terminal device 121 can expect (and read) the beta offset indicator field in the DCI of the scheduled PUSCH.

[0098] Then, terminal device 121 can receive 610 DCI from network device 111, which is for UL transmissions that overlap with the UL resource silent mode. The DCI includes two beta offset indicator values ​​for overlapping and non-overlapping symbols.

[0099] In some embodiments, terminal device 121 may receive two beta offset indicator values ​​to be applied to overlapping UL / SBFD symbols and non-overlapping UL / SBFD symbols. If the UL silence mode indicates that the symbol will be silenced, a symbol may be represented as overlapping. Otherwise, the symbol is defined as non-overlapping. To account for the reduced number of available REs due to silencing, terminal device 121 may anticipate that the beta offset for overlapping symbols is lower than the beta offset for non-overlapping symbols.

[0100] For example, the UE can receive two beta offset indicator values ​​as part of the DCI. The bit sequence in the DCI is split to indicate the two beta offsets; for example, the LSB bit is used to indicate non-overlapping beta offsets, and the MSB bit is used to indicate overlapping beta offsets. If the scheduled PUSCH does not overlap with the UL silence, the UE interprets the beta offset indicator as conventional.

[0101] Alternatively, the size of the beta offset indicator field in the DCI can be increased to accommodate a larger number of bits, i.e., twice the size of the current field. It should be noted that the current beta offset indicator field size is either 1 bit or 2 bits.

[0102] Terminal device 121 can determine whether 615 performs UL silencing for UL transmissions based on indication information (beta offset indicators). In some embodiments, terminal device 121 may not apply UL silencing when the two indicated beta offset indicators have the same value (i.e., terminal device 121 assumes no silencing is applied to the scheduled PUSCH), and terminal device 121 may apply UL silencing when the two indicated beta offset indicators have different values ​​(i.e., terminal device 121 assumes UL silencing is applied to the scheduled PUSCH). In this way, if the beta offset indicator value for overlapping symbols is the same as the beta offset indicator value for non-overlapping symbols, network device 111 can implicitly instruct terminal device 121 not to apply silencing.

[0103] Terminal device 121 can perform 620UL transmission. For example, terminal device 121 can map data (and (if any)) bits to available resources according to DCI and perform UL transmission (PUSCH).

[0104] In cases where the indication information may include new or additional fields for reused DCIs (such as existing DCIs), refer now. Figure 7 This illustrates a process 700 for dynamic indication of uplink silence according to another embodiment of this disclosure. For discussion purposes, reference will be made to... Figure 1A and Figure 1C Describe process 700. Although Figure 7 The interaction between terminal device 121 and network device 111 is shown, but it will be understood that process 700 can also be performed by, for example, terminal device 122 and network device 111, terminal device 123 and network device 112, etc.

[0105] Before receiving the DCI with indication information including the new fields, the terminal device 121 can receive the 705SBFD configuration, UL resource silent mode configuration, and PUSCH configuration from the network device 111.

[0106] Then, terminal device 121 can receive 710DCI from network device 111, which is for UL transmissions that overlap with UL resource silencing modes. This DCI includes a new field (e.g., skipULmutingIndicator) for indicating whether UL silencing is applied to the UL transmission. This field may include one bit. The value of this bit can be 1 or 0. It will be understood that in some other embodiments, the new field may have more than one bit.

[0107] Terminal device 121 can determine whether 715 performs UL silence for UL transmission based on indication information (new field). As an example, terminal device 121 can apply UL silence when the new field value is 1, and not apply UL silence when the new field value is 0.

[0108] It should be understood that in some embodiments, terminal device 121 may apply UL silence when the new field value is 0, and not apply UL silence when the new field value is 1.

[0109] Terminal device 121 can perform 720UL transmission. For example, terminal device 121 can map data (and UCI (if any)) bits to available resources according to DCI and perform UL transmission.

[0110] This is the most straightforward option, and it is simply proposed that the terminal device will receive an indication in the DCI that schedules the PUSCH, which indicates whether the UE should consider UL silence in that time slot (or a set of time slots for the configured license, TB across multiple time slots, or repeated cases).

[0111] In some embodiments, the UL transmissions in processes 200-700 are performed in at least one SBFD time slot or symbol. In some embodiments, the UL transmissions in processes 200-700 are performed in at least one Dynamic Time Division Duplex (TDD) time slot or symbol, and therefore UL silencing can also be used there to ensure that the UL signal does not interfere with gNB-to-gNB CLI measurements at the victim network device. It is understood that when UL transmissions are performed in at least one Dynamic TDD time slot or symbol, terminal device 121 may first receive a Dynamic TDD configuration from network device 111.

[0112] Figure 8 A flowchart of an example method 800 implemented at a terminal device according to some embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 1A and Figure 1C Method 800 is described from the perspective of terminal device 121.

[0113] At block 810, terminal device 121 may receive downlink control information (DCI) for UL transmissions that overlap with uplink (UL) resource silencing modes, wherein the DCI includes indication information related to UL silencing for the UL transmissions. At block 820, terminal device 121 may determine, based on the indication information, whether to perform UL silencing for the UL transmissions. At block 830, terminal device 121 may perform UL transmissions based on this determination.

[0114] In some embodiments, the terminal device 121 is configured with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field, which is used to indicate whether UL silence will be applied to UL transmission.

[0115] In some embodiments, the beta offset indicator field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0116] In some embodiments, the terminal device 121 is configured with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0117] In some embodiments, whether to perform UL silence for a UL transmission is determined by: determining that UL silence is not performed for a UL transmission based on the determination that a first beta offset indicator value is equal to a second beta offset indicator value.

[0118] In some embodiments, whether to perform UL silence for a UL transmission is determined by: determining that a first beta offset indicator value is different from a second beta offset indicator value.

[0119] In some embodiments, a first portion of the bit sequence in the DCI indicates a first beta offset indicator value. In some embodiments, a second portion of the bit sequence in the DCI indicates a second beta offset indicator value.

[0120] In some embodiments, the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0121] In some embodiments, one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode. In some embodiments, the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0122] In some embodiments, the indication information in the DCI includes a field defined to indicate whether UL silence will be applied to UL transmissions.

[0123] In some embodiments, the field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0124] In some embodiments, UL transmission is performed in at least one of the following: at least one SBFD time slot or symbol, or at least one dynamic TDD time slot or symbol.

[0125] Figure 9 A flowchart illustrating a method implemented at a network device according to some embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 1A and Figure 1C Method 900 is described from the perspective of network device 111.

[0126] At block 910, network device 111 can transmit downlink control information (DCI) to terminal device 121 for UL transmissions that overlap with uplink (UL) resource quiescent modes, wherein the DCI includes indication information indicating whether UL quiescent will be applied to UL transmissions. At block 920, network device 111 can receive UL transmissions from terminal device 121.

[0127] In some embodiments, method 900 further includes: network device 111 may configure terminal device 121 with a semi-static beta offset configuration, and the indication information in DCI includes a beta offset indicator field, which is used to indicate whether UL silence will be applied to UL transmission.

[0128] In some embodiments, the beta offset indicator field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0129] In some embodiments, method 900 further includes: network device 111 can configure terminal device 121 with dynamic beta offset configuration, and the indication information in DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0130] In some embodiments, a first beta offset indicator value equal to a second beta offset indicator value indicates that UL silence will not be applied to UL transmissions.

[0131] In some embodiments, a first beta offset indicator value different from a second beta offset indicator value indicates that UL silence will be applied to UL transmission.

[0132] In some embodiments, a first portion of the bit sequence in the DCI indicates a first beta offset indicator value. In some embodiments, a second portion of the bit sequence in the DCI indicates a second beta offset indicator value.

[0133] In some embodiments, the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0134] In some embodiments, one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode. In some embodiments, the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0135] In some embodiments, the indication information in the DCI includes a field defined to indicate whether UL silence will be applied to UL transmissions.

[0136] In some embodiments, the field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0137] In some embodiments, UL transmissions are received in at least one of the following: at least one subband non-overlapping full-duplex (SBFD) slot or symbol, or at least one dynamic time-division duplex (TDD) slot or symbol.

[0138] In some embodiments, an apparatus capable of performing any of the methods 800 (e.g., terminal device 121) may include components for performing the corresponding steps of method 800. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0139] In some embodiments, the apparatus includes components for providing downlink control information (DCI) at a terminal device for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; components for determining, based on the indication information, whether to perform UL silence for the UL transmission; and components for performing the UL transmission based on the determination.

[0140] In some embodiments, the terminal device is configured with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field, which is used to indicate whether UL silence will be applied to UL transmission.

[0141] In some embodiments, the beta offset indicator field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0142] In some embodiments, the terminal device is configured with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0143] In some embodiments, the component for determining whether to perform UL silence for a UL transmission includes: a component for determining whether to perform UL silence for a UL transmission based on determining that a first beta offset indicator value is equal to a second beta offset indicator value.

[0144] In some embodiments, the component for determining whether to perform UL silence for UL transmission includes: a component for determining whether to perform UL silence for UL transmission based on determining that a first beta offset indicator value is different from a second beta offset indicator value.

[0145] In some embodiments, a first portion of the bit sequence in the DCI indicates a first beta offset indicator value; and a second portion of the bit sequence in the DCI indicates a second beta offset indicator value.

[0146] In some embodiments, the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0147] In some embodiments, one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode; and the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0148] In some embodiments, the indication information in the DCI includes a field defined to indicate whether UL silence will be applied to UL transmissions.

[0149] In some embodiments, the field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0150] In some embodiments, UL transmission is performed in at least one of the following: at least one subband non-overlapping full-duplex (SBFD) slot or symbol, or at least one dynamic time-division duplex (TDD) slot or symbol.

[0151] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 800. In some embodiments, the components include at least one processor and at least one memory, the at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0152] In some embodiments, an apparatus capable of performing any of the methods 900 (e.g., network device 111) may include components for performing the corresponding steps of method 900. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0153] In some embodiments, the apparatus includes: components for transmitting downlink control information (DCI) at a network device to an end device, the DCI being for UL transmissions that overlap with an uplink (UL) resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and components for receiving UL transmissions from the end device.

[0154] In some embodiments, the network device configures the terminal device with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field, which is used to indicate whether UL silence will be applied to UL transmission.

[0155] In some embodiments, the beta offset indicator field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0156] In some embodiments, the network device configures the terminal device with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0157] In some embodiments, a first beta offset indicator value equal to a second beta offset indicator value indicates that UL silence will not be applied to UL transmissions.

[0158] In some embodiments, a first beta offset indicator value different from a second beta offset indicator value indicates that UL silence will be applied to UL transmission.

[0159] In some embodiments, a first portion of the bit sequence in the DCI indicates a first beta offset indicator value; and a second portion of the bit sequence in the DCI indicates a second beta offset indicator value.

[0160] In some embodiments, the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0161] In some embodiments, one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol overlaps with the UL resource silent mode; and the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the UL transmitted symbol does not overlap with the UL resource silent mode.

[0162] In some embodiments, the indication information in the DCI includes a field defined to indicate whether UL silence will be applied to UL transmissions.

[0163] In some embodiments, the field includes a bit, the first value of which indicates that UL silence will be applied to UL transmissions, and the second value of which indicates that UL silence will not be applied to UL transmissions.

[0164] In some embodiments, UL transmissions are received in at least one of the following: at least one subband non-overlapping full-duplex (SBFD) slot or symbol, or at least one dynamic time-division duplex (TDD) slot or symbol.

[0165] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 900. In some embodiments, the components include at least one processor and at least one memory, the at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0166] Figure 10 This is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. The device 1000 may be configured to implement a communication device, for example, as... Figure 1A and Figure 1CThe device shown is a terminal device or a network device. As shown, device 1000 includes one or more processors 1010, one or more memories 1020 coupled to processor 1010, and one or more communication modules 1040 coupled to processor 1010.

[0167] The communication module 1040 is used for bidirectional communication. The communication module 1040 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0168] Processor 1010 can be any type suitable for a local technology network and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 1000 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with a main processor.

[0169] Memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact optical disc (CD), digital video optical disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that will not be retained during power outages.

[0170] Computer program 1030 includes computer-executable instructions that are executed by the associated processor 1010. Program 1030 may be stored in ROM 1024. Processor 1010 may perform any suitable actions and processes by loading program 1030 into RAM 1022.

[0171] Embodiments of this disclosure can be implemented using program 1030, enabling device 1000 to perform as described in the reference. Figures 2 to 7 Any process 200-700 of this disclosure discussed herein. Embodiments of this disclosure may also be implemented in hardware or in a combination of hardware and software.

[0172] In some embodiments, program 1030 may be tangibly contained in a computer-readable medium, which may be contained in device 1000 (e.g., memory 1020) or other storage device accessible by device 1000. Device 1000 may load program 1030 from the computer-readable medium into RAM 1022 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 11 An example of a computer-readable medium 1100 in the form of a CD or DVD is shown. A program 1030 is stored on this computer-readable medium.

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

[0174] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in a program module that executes on a device on a target real or virtual processor, to perform as referenced above. Figures 2 to 7 Methods 800 and 900 are described. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

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

[0176] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0177] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. As used herein, the term “non-transient” is a limitation of the medium itself (i.e., tangible, not signaling), and not a limitation of data storage persistence (e.g., RAM versus ROM).

[0178] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order or sequence shown, or that all the operations shown be performed to achieve the desired result. In certain situations, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Specific features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

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

[0180] Furthermore, various implementations of this disclosure can be described with reference to the following entries, and their features can be combined in any reasonable manner.

[0181] Item 1. A terminal device, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: receive downlink control information (DCI) for a UL transmission that overlaps with an uplink UL resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; determine, based on the indication information, whether to perform UL silence for the UL transmission; and perform the UL transmission based on the determination.

[0182] Item 2. The terminal device according to Item 1, wherein the terminal device is configured with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field, the beta offset indicator field being used to indicate whether the UL silence will be applied to the UL transmission.

[0183] Item 3. The terminal device according to Item 2, wherein the beta offset indicator field includes a bit, a first value of which indicates that the UL silence will be applied to the UL transmission, and a second value of which indicates that the UL silence will not be applied to the UL transmission.

[0184] Item 4. The terminal device according to Item 1, wherein the terminal device is configured with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0185] Item 5. The terminal device according to Item 4, wherein the terminal device is configured to determine whether to perform the UL silence for the UL transmission by: determining that the UL silence is not performed for the UL transmission based on determining that the first beta offset indicator value is equal to the second beta offset indicator value.

[0186] Item 6. The terminal device according to Item 4, wherein the terminal device is configured to determine whether to perform the UL silence for the UL transmission by: determining that the UL silence is performed for the UL transmission based on determining that the first beta offset indicator value is different from the second beta offset indicator value.

[0187] Item 7. The terminal device according to any one of items 4 to 6, wherein: a first portion of the bit sequence in the DCI indicates the first beta offset indicator value; and a second portion of the bit sequence in the DCI indicates the second beta offset indicator value.

[0188] Item 8. The terminal device according to any one of Items 4 to 6, wherein the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0189] Item 9. The terminal device according to any one of Items 4 to 8, wherein: one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the symbol of the UL transmission overlaps with the UL resource silent mode; and the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the symbol of the UL transmission does not overlap with the UL resource silent mode.

[0190] Item 10. The terminal device according to Item 1, wherein the indication information in the DCI includes a field defined for indicating whether the UL silence will be applied to the UL transmission.

[0191] Item 11. The terminal device according to Item 10, wherein the field includes a bit, a first value of the bit indicating that the UL silence will be applied to the UL transmission, and a second value of the bit indicating that the UL silence will not be applied to the UL transmission.

[0192] Item 12. The terminal device according to any one of Items 1 to 11, wherein the UL transmission is performed in at least one of the following: at least one subband non-overlapping full-duplex SBFD time slot or symbol, or at least one dynamic time-division duplex TDD time slot or symbol.

[0193] Item 13. A network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: transmit downlink control information (DCI) to an end device, the DCI being for UL transmissions that overlap with an uplink UL resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmissions; and receive the UL transmissions from the end device.

[0194] Item 14. The network device according to Item 13, wherein the network device configures the terminal device with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field for indicating whether the UL silence will be applied to the UL transmission.

[0195] Item 15. The network device according to Item 14, wherein the beta offset indicator field includes bits, a first value of which indicates that the UL silence will be applied to the UL transmission, and a second value of which indicates that the UL silence will not be applied to the UL transmission.

[0196] Item 16. The network device according to Item 13, wherein the network device configures the terminal device with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

[0197] Item 17. The network device according to Item 16, wherein the first beta offset indicator value is equal to the second beta offset indicator value indicating that the UL silence will not be applied to the UL transmission.

[0198] Item 18. The network device according to Item 16, wherein the first beta offset indicator value is different from the second beta offset indicator value indicating that the UL silence will be applied to the UL transmission.

[0199] Item 19. A network device according to any one of items 16 to 18, wherein: a first portion of the bit sequence in the DCI indicates the first beta offset indicator value; and a second portion of the bit sequence in the DCI indicates the second beta offset indicator value.

[0200] Item 20. The network device according to any one of Items 16 to 18, wherein the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

[0201] Item 21. The network device according to any one of items 16 to 20, wherein: one of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the symbol of the UL transmission overlaps with the UL resource silent mode; and the other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the symbol of the UL transmission does not overlap with the UL resource silent mode.

[0202] Item 22. The network device according to Item 13, wherein the indication information in the DCI includes a field defined for indicating whether the UL silence will be applied to the UL transmission.

[0203] Item 23. The network device according to Item 22, wherein the field includes a bit, a first value of which indicates that the UL silence will be applied to the UL transmission, and a second value of which indicates that the UL silence will not be applied to the UL transmission.

[0204] Item 24. A network device according to any one of Items 13 to 23, wherein the UL transmission is received in at least one of the following: at least one subband non-overlapping full-duplex SBFD time slot or symbol, or at least one dynamic time-division duplex TDD time slot or symbol.

[0205] Item 25. A method comprising: receiving downlink control information (DCI) for a UL transmission that overlaps with an uplink UL resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; determining, based on the indication information, whether to perform UL silence for the UL transmission; and performing the UL transmission based on the determination.

[0206] Item 26. A method comprising: transmitting downlink control information (DCI) to a terminal device, the DCI being for a UL transmission that overlaps with an uplink UL resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmission; and receiving the UL transmission from the terminal device.

[0207] Item 27. An apparatus comprising: components for receiving downlink control information (DCI) for a UL transmission that overlaps with an uplink UL resource silence mode, wherein the DCI includes indication information related to UL silence for the UL transmission; components for determining, based on the indication information, whether to perform UL silence for the UL transmission; and components for performing the UL transmission based on the determination.

[0208] Item 28. An apparatus comprising: components for transmitting downlink control information (DCI) to a terminal device, the DCI being for a UL transmission that overlaps with an uplink UL resource silence mode, wherein the DCI includes indication information indicating whether UL silence will be applied to the UL transmission; and components for receiving the UL transmission from the terminal device.

[0209] Item 29. A computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method described according to Item 25 or 26.

Claims

1. A terminal device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: Receive downlink control information (DCI) for UL transmissions that overlap with uplink UL resource silence modes, wherein the DCI includes indication information related to UL silence for the UL transmissions. Based on the indication information, determine whether to perform UL silence for the UL transmission; The UL transmission is performed based on the determination.

2. The terminal device according to claim 1, wherein the terminal device is configured with a semi-static beta offset configuration, and the indication information in the DCI includes a beta offset indicator field, the beta offset indicator field being used to indicate whether the UL silence will be applied to the UL transmission.

3. The terminal device of claim 2, wherein the beta offset indicator field includes a bit, a first value of the bit indicating that the UL silence will be applied to the UL transmission, and a second value of the bit indicating that the UL silence will not be applied to the UL transmission.

4. The terminal device according to claim 1, wherein the terminal device is configured with a dynamic beta offset configuration, and the indication information in the DCI includes a first beta offset indicator value and a second beta offset indicator value.

5. The terminal device of claim 4, wherein the terminal device is configured to determine whether to perform the UL silence for the UL transmission by: Based on the determination that the first beta offset indicator value is equal to the second beta offset indicator value, it is determined that the UL silence will not be performed for the UL transmission.

6. The terminal device of claim 4, wherein the terminal device is configured to determine whether to perform the UL silence for the UL transmission by: Based on the determination that the first beta offset indicator value is different from the second beta offset indicator value, it is determined that the UL silence will be performed for the UL transmission.

7. The terminal device according to any one of claims 4 to 6, wherein: The first portion of the bit sequence in the DCI indicates the first beta offset indicator value; and The second portion of the bit sequence in the DCI indicates the second beta offset indicator value.

8. The terminal device according to any one of claims 4 to 6, wherein the first beta offset indicator value and the second beta offset indicator value are included in the beta offset indicator field of the DCI.

9. The terminal device according to any one of claims 4 to 6, wherein: One of the first beta offset indicator value and the second beta offset indicator value is applied based on the following condition: the symbol of the UL transmission overlaps with the UL resource silent mode; and The other of the first beta offset indicator value and the second beta offset indicator value is applied based on the condition that the symbol of the UL transmission does not overlap with the UL resource silent mode.

10. The terminal device of claim 1, wherein the indication information in the DCI includes a field defined for indicating whether the UL silence will be applied to the UL transmission.

Images