WO2025077607A1 - Dynamic sbfd indication methods and apparatuses, device and storage medium - Google Patents

Abstract

The present application belongs to the technical field of communications. Disclosed are dynamic SBFD indication methods and apparatuses, a device and a storage medium. A dynamic SBFD indication method in an embodiment of the present application comprises: a terminal receives a first signaling from a network side device, the first signaling comprising first indication information, the first indication information being used for indicating the type actually used by a target time domain unit, the target time domain unit being a time domain unit capable of supporting a terminal-side full duplex, and the first signaling being a terminal-specific scheduling signaling or a group common signaling; and, according to the first indication information, the terminal adjusts the type of the target time domain unit.

Description

Dynamic SBFD indication method, device, equipment and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No. 202311318811.1 filed on October 11, 2023, the entire contents of which are incorporated herein by reference.

Technical Field

The present application belongs to the field of communication technology, and specifically relates to a dynamic SBFD indication method, device, equipment and storage medium.

Background Art

When deploying traditional cellular networks, frequency division duplex (FDD) or time division duplex (TDD) can be used based on available spectrum and service characteristics. In order to flexibly utilize limited spectrum resources, dynamically match service requirements, improve resource utilization efficiency, and data transmission uplink coverage, latency and other performance, a flexible duplex mode is proposed, a flexible duplex mode based on non-overlapping sub-bands in the frequency domain, such as sub-band full duplex (SBFD).

At present, SBFD based on full-duplex on the network side and half-duplex on the terminal side has been studied. For dynamic SBFD, it includes: for semi-static downlink symbols configured with an uplink subband, downlink transmission is allowed outside the downlink subband; for semi-static flexible symbols configured with an uplink subband, downlink transmission is allowed outside the downlink subband, and uplink transmission is allowed outside the uplink subband.

However, for SBFD based on full-duplex on the terminal side, dynamic SBFD also needs to support full-duplex operation on the terminal side. There is currently no corresponding solution, so it is impossible to dynamically support full-duplex operation on the terminal side, resulting in an inability to flexibly utilize available resources for uplink transmission and downlink reception. The available resources cannot flexibly and dynamically match service needs, resulting in poor performance such as service transmission delay.

Summary of the invention

The embodiments of the present application provide a dynamic SBFD indication method, apparatus, device and storage medium, which can solve the problem that full-duplex operation on the terminal side cannot be dynamically supported, and thus available resources cannot be flexibly utilized for uplink transmission and downlink reception, and available resources cannot be flexibly and dynamically matched to service requirements, resulting in poor performance such as service transmission delay.

In a first aspect, a dynamic SBFD indication method is provided, the method comprising: a terminal receives a first signaling from a network side device, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling; the terminal adjusts the type of the target time domain unit according to the first indication information.

In the second aspect, a dynamic SBFD indication method is provided, the method comprising: a network side device sends a first signaling to a terminal, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling; wherein the first indication information is used to adjust the type of the target time domain unit.

In a third aspect, a dynamic SBFD indication device is provided, the device comprising: a receiving module and an adjustment module. The receiving module is used to receive a first signaling from a network side device, the first signaling includes a first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling. The adjustment module is used to adjust the type of the target time domain unit according to the first indication information received by the receiving module.

In a fourth aspect, a dynamic SBFD indication device is provided, the device comprising: a sending module. The sending module is used to send a first signaling to a terminal, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling; wherein the first indication information is used to adjust the type of the target time domain unit.

In a fifth aspect, a terminal is provided, the terminal comprising a processor and a memory, the memory storing The program or instruction running on the processor, when the program or instruction is executed by the processor, implements the steps of the method described in the first aspect.

In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first signaling from a network side device, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling. The processor is used to adjust the type of the target time domain unit according to the first indication information.

In a seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first signaling to a terminal, the first signaling including first indication information, the first indication information being used to indicate the type of actual application of the target time domain unit, the target time domain unit being a time domain unit capable of supporting full-duplex on the terminal side, and the first signaling being a terminal-specific scheduling signaling or a group common signaling; wherein the first indication information is used to adjust the type of the target time domain unit.

In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.

In the twelfth aspect, a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the program/program product is executed by at least one processor to implement the steps of the dynamic SBFD indication method as described in the first aspect, or to implement the steps of the dynamic SBFD indication method as described in the second aspect.

In an embodiment of the present application, a terminal may receive a first signaling from a network-side device, the first signaling including first indication information, and adjust the type of a target time domain unit according to the first indication information, the first indication information being used to indicate the type of actual application of the target time domain unit, the target time domain unit being a time domain unit capable of supporting full-duplex on the terminal side, and the first signaling being a terminal-specific scheduling signaling or a group common signaling. In this solution, for SBFD based on full-duplex on the terminal side, the type of time domain unit actually applied can be dynamically adjusted for the time domain unit capable of supporting full-duplex on the terminal side to support dynamic SBFD, so that uplink transmission and downlink reception can flexibly utilize available resources, thereby enabling available resources to flexibly and dynamically match service requirements, so as to improve performance such as service transmission delay.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

FIG2 is a schematic diagram of a dynamic SBFD indication method provided in an embodiment of the present application;

FIG3 is a schematic diagram of a frequency domain pattern within a SBFD symbol provided in an embodiment of the present application;

FIG4 is a second schematic diagram of a dynamic SBFD indication method provided in an embodiment of the present application;

FIG5 is one of the structural schematic diagrams of a dynamic SBFD indicating device provided in an embodiment of the present application;

FIG6 is a second structural schematic diagram of a dynamic SBFD indicating device provided in an embodiment of the present application;

7 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

FIG8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances so that the application The embodiments can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application means at least one of the connected objects. For example, "A or B" covers three schemes, namely, scheme one: including A but not including B; scheme two: including B but not including A; scheme three: including both A and B. The character "/" generally indicates that the objects associated before and after are in an "or" relationship.

The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

The terms "at least one (item)", "at least one of" and the like in this application refer to any one, any two or a combination of more than two of the objects included therein. For example, at least one (item) of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c" and "a, b and c", where a, b, and c can be single or multiple. Similarly, "at least two (items)" refers to two or more, and its meaning is similar to that of "at least one (item)".

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

FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc. Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B (home evolved Node B), a Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

The following is an explanation of some concepts and/or terms involved in a dynamic SBFD indication method, apparatus, device, and storage medium provided in an embodiment of the present application.

1. SBFD

When deploying traditional cellular networks, based on the available spectrum and service characteristics, frequency division duplex (FDD) or time division duplex (TDD) can be used. When FDD is used, uplink and downlink transmissions are located at different frequencies, and the two do not interfere with each other and can be carried out simultaneously. When TDD is used, uplink and downlink transmissions are located at the same frequency and are carried out in a staggered manner using time division.

In order to more flexibly utilize limited spectrum resources, dynamically match business needs, improve resource utilization efficiency, and improve uplink coverage, latency and other performance of data transmission, a flexible duplex mode is proposed. A flexible duplex mode based on non-overlapping sub-band full duplex in the frequency domain is:

(1) Full-duplex on the network side

From the perspective of the network side, at the same time, uplink transmission and downlink transmission can be carried out simultaneously in different frequency domain sub-bands. To avoid interference between uplink and downlink, a certain guard band can be reserved between the frequency domain sub-bands corresponding to different transmission directions (such as uplink sub-band and downlink sub-band).

(2) Half-duplex or full-duplex on the terminal side

When the terminal side supports half-duplex, only uplink transmission or downlink transmission can be performed at the same time, and both cannot be performed at the same time. It can be understood that in this case, the uplink transmission and downlink transmission at the same time on the network side can only be for different terminals.

When the terminal side supports full-duplex, similar to the network side, at the same time, uplink transmission and downlink transmission can be performed simultaneously in different frequency domain sub-bands.

2. Dynamic SBFD

At present, SBFD based on full-duplex on the network side and half-duplex on the terminal side has been studied. Among them, for semi-static SBFD, only uplink is transmitted in the uplink subband configured on the network side, and only downlink is transmitted in the downlink subband configured on the network side. At the same time, more research has been done on Dynamic SBFD, including: for Semi-static downlink symbols (DL symbols) configured with uplink subbands (UL subbands), downlink transmission is allowed outside the downlink subband (DL subband); for Semi-static flexible symbols (flexible symbols) configured with UL subbands, downlink transmission is allowed outside the DL subband, and uplink transmission is allowed outside the UL subband.

The following describes in detail the dynamic SBFD indication method provided by the embodiment of the present application through some embodiments and application scenarios in conjunction with the accompanying drawings.

For SBFD based on full-duplex on the terminal side, dynamic SBFD also needs to support full-duplex operation on the terminal side. Currently, there is no corresponding solution, so it is impossible to dynamically support full-duplex operation on the terminal side. As a result, available resources cannot be flexibly utilized for uplink transmission and downlink reception, and available resources cannot be flexibly and dynamically matched to service needs, resulting in poor performance such as service transmission delay.

In an embodiment of the present application, the terminal may receive a first signaling from a network-side device, the first signaling including first indication information, and adjust the type of the target time domain unit according to the first indication information, the first indication information being used to indicate the type of actual application of the target time domain unit, the target time domain unit being a time domain unit capable of supporting full-duplex on the terminal side, and the first signaling being a terminal-specific scheduling signaling or a group common signaling. In this solution, for SBFD based on full-duplex on the terminal side, the type of time domain unit actually applied can be dynamically adjusted for the time domain unit capable of supporting full-duplex on the terminal side to support dynamic SBFD, so that uplink transmission and downlink reception can flexibly utilize available resources, thereby enabling available resources to flexibly and dynamically match service requirements, so as to improve performance such as service transmission latency.

The embodiment of the present application provides a dynamic SBFD indication method, and Figure 2 shows a flow chart of the dynamic SBFD indication method provided by the embodiment of the present application. As shown in Figure 2, the dynamic SBFD indication method provided by the embodiment of the present application may include the following steps 201 to 203.

Step 201: A network-side device sends a first signaling to a terminal, where the first signaling includes first indication information.

Step 202: The terminal receives a first signaling from a network-side device, where the first signaling includes first indication information.

In the embodiment of the present application, the first indication information is used to indicate the type of actual application of the target time domain unit, and the target time domain unit is a time domain unit that can support full-duplex on the terminal side. The first indication information is used to adjust the type of the target time domain unit.

Optionally, in an embodiment of the present application, the above-mentioned time domain unit can be a symbol, a time slot, a micro time slot, a frame, a subframe, etc.

In an embodiment of the present application, the above-mentioned first signaling is terminal specific scheduling signaling (UE specific scheduling signaling) or group common signaling (Group common signaling).

Optionally, in an embodiment of the present application, the terminal may adjust the type of the target time domain unit through UE specific scheduling signalling explicit indication information (hereinafter referred to as indication method 1), or UE specific scheduling signalling implicit indication information (hereinafter referred to as indication method 2), or Group common signalling indication information (hereinafter referred to as indication method 3).

It should be noted that the UE specific scheduling signalling here can be scheduling downlink control information (Downlink Control Information, DCI), such as uplink scheduling DCI format 0_0/0_1/0_2, and downlink scheduling DCI format 1_0/1_1/1_2. Scheduling DCI-scheduled shared channel transmission, and/or, triggered CSI-RS/SRS transmission can be called dynamically scheduled transmission.

Optionally, in the embodiment of the present application, the dynamic SBFD indication method provided in the embodiment of the present application further includes the following step 204.

Step 204: For the same time domain unit, when determining the time domain unit type that is actually effective based on multiple scheduling DCIs or group common DCIs, the terminal performs any of the following:

Determine the time domain unit type that is actually effective for the same time domain unit based on the last DCI;

The terminal expects that the actual effective time domain unit type determined by the same time domain unit based on any DCI is the same;

The levels of the time domain unit types actually effective for the same time domain unit in the fallback hierarchy are determined based on each DCI, and the time domain unit types actually effective are determined based on the multiple levels and predefined rules.

It can be understood that for the above indication modes 1/2/3, the above step 204 can be performed for the same time domain unit.

It should be noted that the determination of the above-mentioned last DCI can follow the corresponding mechanism in the existing protocol, for example, the last DCI (Last DCI for determining HARQ-ACK codebook and/or PUCCH resource) for determining the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook and/or physical uplink control channel (PUCCH) resource.

For the predefined rule, the lowest/last level in the fallback level can be obtained, and the time domain unit type corresponding to this level can be used as the time domain unit type that actually takes effect at this time domain unit.

Optionally, in the embodiment of the present application, before the above step 201, the dynamic SBFD indication method provided in the embodiment of the present application further includes the following step 205.

Step 205: When the terminal supports subband-based full-duplex, the terminal determines the type of at least one SBFD time domain unit.

In the embodiment of the present application, the type of the SBFD time domain unit includes at least one of the following: a SBFD time domain unit of a first duplex mode and a SBFD time domain unit of a second duplex mode.

The first duplex mode is that the terminal can only perform uplink transmission or downlink reception in a single SBFD time domain unit. The second duplex mode is that the terminal can perform uplink transmission and downlink reception simultaneously in a single SBFD time domain unit.

Optionally, in an embodiment of the present application, the terminal can distinguish the following symbol types based on the TDD mode configuration information provided by the network side device (for example, tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated provided for a service cell of the terminal): downlink symbol (DL symbol), uplink symbol (UL symbol), and flexible symbol (Flexible symbol).

Optionally, in an embodiment of the present application, when tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is not provided for a certain service cell, each Symbol may be considered as a Flexible symbol, or, the rules corresponding to the Flexible symbol may be followed.

Optionally, in an embodiment of the present application, the terminal can further distinguish the following symbol types based on the TDD mode configuration information and SBFD configuration information provided by the network side device: SBFD symbol, non-SBFD symbol.

Among them, for SBFD symbols: the network side device can configure certain symbols to perform SBFD operations (operation) through SBFD configuration information, such as configuring these symbols as SBFD symbols. For example, some or all symbols in a single cycle determined based on the TDD mode are configured as SBFD symbols. These symbols configured as SBFD symbols can be some or all types of symbol types (Symbol type) distinguished based on the TDD mode configuration information.

For non-SBFD symbols: Any symbol that is not configured (or instructed) to perform SBFD operation can be considered a non-SBFD symbol.

It can be understood that when the terminal side supports subband based full duplex, For a serving cell configured or activated for a terminal, the SBFD symbol on the serving cell can be further distinguished into the following symbol types:

SBFD symbol for duplex mode 1

For Duplex mode 1, the network side supports SBFD operation based on full-duplex; the terminal side only supports SBFD operation based on half-duplex. Within a single SBFD symbol, the terminal can only perform uplink transmission or downlink reception, but cannot perform uplink transmission and downlink reception based on FDM at the same time.

SBFD symbol for duplex mode 2

For Duplex mode 2, the network side supports SBFD operation based on full duplex; the terminal side can support SBFD operation based on full duplex, and the terminal can simultaneously perform uplink transmission and downlink reception based on FDM within a single SBFD symbol. It can be understood that a terminal that supports SBFD operation based on full duplex (such as supporting Duplex mode 2, or supporting SBFD symbol for duplex mode 2) must also support SBFD operation based on half duplex (such as supporting Duplex mode 1, or supporting SBFD symbol for duplex mode 1).

Optionally, in an embodiment of the present application, the terminal does not expect the first time domain unit to be configured as an SBFD time domain unit of the second duplex mode, and the first time domain unit includes at least one of the following: a synchronization signal block (Synchronization Signal Block, SSB) time domain unit, and a SBFD time domain unit configured with a physical random access channel (Physical Random Access Channel, PRACH) opportunity.

It is understandable that the terminal does not expect the SSB symbol to be configured as the SBFD symbol for duplex mode 2 to ensure the performance of SSB-based measurement and other operations. The SSB associated with the SSB symbol here includes at least one of Cell Definition (CD)-SSB and Non-Cell Definition (NCD)-SSB.

The terminal does not expect the SBFD symbol configured with the PRACH occasion (which can be understood as the UL subband configured in this/these SBFD symbol(s) in which the PRACH occasion is mapped) to be configured as the SBFD symbol for duplex mode 2 to avoid the impact of self-interference caused by PRACH transmission on potential downlink reception/measurement performance. Alternatively, when a PRACH occasion is configured in the SBFD symbol configured as the SBFD symbol for duplex mode 2, the terminal implementation chooses whether to send PRACH or perform downlink reception/measurement. One possible implementation is that when triggered to initiate PRACH transmission (excluding Physical Downlink Control Channel (PDCCH) order-based PRACH), the terminal chooses to send PRACH; otherwise, the terminal chooses to perform downlink reception/measurement.

Optionally, in an embodiment of the present application, in the frequency domain pattern configured or applied to the SBFD time domain unit of the first duplex mode and the SBFD time domain unit of the second duplex mode, the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode is greater than or equal to the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode. In this way, the self-interference caused by the potential terminal-side full-duplex operation of Duplex mode 2 can be suppressed (Duplex mode 1 does not involve terminal-side self-interference).

Among them, the above-mentioned target object includes at least one of the following: carrier, service cell, bandwidth part (Bandwidth Part, BWP) pair.

Optionally, in the embodiment of the present application, the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the second duplex mode is located within the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the first duplex mode, and the first frequency band includes at least one of the following: an uplink sub-band and a downlink sub-band;

The frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode is located within the frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode.

Exemplarily, as shown in Figure 3, for Duplex mode 1, the frequency domain pattern configured for the terminal can be consistent with the frequency domain resources planned by the network side for SBFD operation; for Duplex mode 2, a single UL subband in the frequency domain pattern configured for the terminal is located within the frequency domain range of the UL subband planned by the network side for SBFD operation, and each DL subband is located within the frequency domain range of the corresponding DL subband planned by the network side for SBFD operation.

Optionally, in an embodiment of the present application, in the Frequency domain patterns corresponding to the two Duplex modes, the corresponding DL subbands are completely aligned (the two have the same size and position in the frequency domain), and only the corresponding UL subbands are not aligned (the two have at least different size or position in the frequency domain); or, the corresponding UL subbands are completely aligned, and only the corresponding DL subbands are not aligned.

Optionally, in the embodiment of the present application, in the Frequency domain patterns corresponding to the two Duplex modes, the center frequencies of the corresponding DL subbands are the same or aligned. Alternatively, in the Frequency domain patterns corresponding to the two Duplex modes, the center frequencies of the corresponding UL subbands are the same or aligned.

Optionally, in the embodiment of the present application, after the introduction of dynamic SBFD, Duplex mode 2 It can be further subdivided into multiple Duplex modes according to different dimensions. Accordingly, the corresponding SBFD symbol type can be determined for each Duplex mode. For example, based on whether the size and position of the guardband in the frequency domain are fixed (based on semi-static configuration) or variable (based on dynamic signaling), Duplex mode 2 can be further divided into the following Duplex modes corresponding to (1) to (3):

(1)Duplex mode 2A: The size and position of the Guardband are fixed.

Correspondingly, the size and position of DL subband and UL subband are also fixed.

(2)Duplex mode 2B: The size of the Guardband is fixed, but the position can be changed.

At this time, Guardband can occupy the frequency domain resources corresponding to the DL subband and/or UL subband planned by the network side for SBFD operation as needed.

Correspondingly, the size and position of DL subband and UL subband also change with the change of Guardband position.

(3)Duplex mode 2C: The size and position of the Guardband can be changed.

Correspondingly, the size and position of DL subband and UL subband also change with the change of Guardband position.

The terminal can report multiple Guardband sizes and applicable situations/conditions based on its own capabilities. The network side can select one of the Guardband sizes to configure the Frequency domain pattern for the terminal as needed. Based on this configured Frequency domain pattern, the network side can also use Dynamic SBFD to dynamically change the Guardband size and/or adjust the Guardband position, thereby adjusting the Frequency domain pattern actually applied.

Correspondingly, SBFD symbol for duplex mode 2A, SBFD symbol for duplex mode 2B and SBFD symbol for duplex mode 2C can be further distinguished based on the above Duplex mode.

It should be noted that whether the terminal supports SBFD, and the supported Duplex mode or SBFD symbol type when supporting SBFD can be determined based on the terminal's capability report.

Step 203: The terminal adjusts the type of the target time domain unit according to the first indication information.

Optionally, in an embodiment of the present application, the first indication information indicates whether to rewrite the SBFD mode of the target time domain unit, where the target time domain unit is a SBFD time domain unit overlapping with the dynamically scheduled transmission.

It should be noted that the overlap here can be understood as: there is a complete or partial overlap in the time domain. The SBFD time domain units that overlap with the dynamically scheduled transmission can be understood as all SBFD time domain units that completely or partially overlap with the dynamically scheduled transmission in the time domain. When the subcarrier spacing of the dynamically scheduled transmission is the same as that of the SBFD time domain unit, the overlap here can also be understood as occupation.

Exemplarily, in combination with FIG. 2 , as shown in FIG. 4 , the above step 203 may be implemented specifically through the following step 203a.

Step 203a: The terminal adjusts the type of the target time domain unit according to the first indication information and the first fallback level.

In the embodiment of the present application, the first fallback level is a fallback level for a single SBFD time domain unit specified by a protocol or configured by high-level signaling.

Optionally, in the embodiment of the present application, the first fallback level satisfies any of the following:

The lower or later the fallback level is, the less frequency domain resources the guard band occupies;

The lower or later the fallback level is, the more frequency domain resources can be used in the corresponding transmission direction.

Optionally, in the embodiment of the present application, the above step 203a can be specifically implemented by the following step 203a1.

Step 203a1: If the first indication information indicates to rewrite the SBFD mode, the terminal judges layer by layer from high to low or from front to back according to the first fallback level until the first level that meets the predetermined conditions is found, and then determines that the target time domain unit is rewritten to the time domain unit type corresponding to the first level.

In the embodiment of the present application, the above-mentioned predetermined condition is: based on the time domain unit type corresponding to the first level, there is no overlap between the dynamically scheduled transmission and any sub-band and guard band in the opposite direction in the frequency domain.

For example, for the above-mentioned indication method 1, one case may adopt the following indication method 1-1: the scheduling DCI only indicates whether the SBFD pattern is overridden for the overlapped SBFD symbol, and 1 bit may be used for indication. The SBFD pattern here may be understood as the time domain and/or frequency domain information configured for the SBFD operation, such as the SBFD configuration information mentioned above.

Specifically, we can distinguish the following situations and perform corresponding operations respectively (Case 1 and Case 2):

Case 1: When the scheduling DCI indicates to rewrite the SBFD pattern for the overlapped SBFD symbol, perform at least one of the following operations 1-1 and 1-2:

Operation 1-1: Dynamically scheduled transmission occupies the reverse direction subband (including possible guardband) Any resource element (RE) is judged to be valid. In other words, the time-frequency resources occupied by the dynamically scheduled transmission in each overlapped SBFD symbol are judged to be valid.

For the frequency domain resources occupied by dynamically scheduled transmissions, the physical uplink shared channel (PUSCH) or physical downlink shared channel (PDSCH) transmission can be indicated by the frequency domain resource allocation (FDRA) field in the scheduling DCI, while the channel state information reference signal (CSI-RS) or sounding reference signal (SRS) transmission is configured using the resource granularity by the radio resource control (RRC) signaling.

Operation 1-2: Determine the frequency domain pattern actually applied/effective in each overlapped SBFD symbol. You can use any of the following (1) to (3):

(1) The overlapping opposite direction Subband (including possible Guardband) within this overlapped SBFD symbol is Overridden to the direction corresponding to the dynamically scheduled transmission.

At this time, the Guardband between the same-direction Subband and the opposite-direction Subband that overlap with the dynamically scheduled transmission no longer exists/is effective.

(2) The entire frequency domain pattern within the currently activated BWP (including all reverse direction subbands and possible guardbands) is overwritten (Override/Convert) in this overlapped SBFD symbol to the direction corresponding to the dynamically scheduled transmission (changing the symbol type).

At this time, it can also be understood that the overlapped SBFD symbol is Override/Converted to a non-SBFD symbol. For example, when the dynamically scheduled transmission corresponds to the uplink, the overlapped SBFD symbol is Override/Converted to a full (Full) UL symbol (which can also be understood as a UL symbol and a non-SBFD symbol); when the dynamically scheduled transmission corresponds to the downlink, the overlapped SBFD symbol is Override/Converted to a Full DL symbol (which can also be understood as a DL symbol and a non-SBFD symbol).

(3) Determine the target Symbol type of this overlapped SBFD symbol based on the layer-by-layer fallback mechanism.

Specifically, the following operations may be included:

The fallback level for a single SBFD symbol is specified by the protocol or configured by high-level signaling, for example: SBFD symbol for duplex mode 2->SBFD symbol for duplex mode 1->non-SBFD symbol (for example, downlink/uplink/flexible symbols configured based on the traditional TDD mode). When specifying/configuring the above fallback levels, the fallback levels may be uniformly specified/configured regardless of the transmission direction, or the fallback levels may be specified/configured separately for different transmission directions. Optionally, the above fallback levels satisfy certain rules, for example, the lower/later the level, the fewer frequency domain resources occupied by the Guardband, or the more frequency domain resources available for a given transmission direction.

For this overlapped SBFD symbol, if the scheduling DCI indicates Override SBFD pattern, then based on the specified/configured fallback layer, the layer-by-layer judgment is made from high to low/from front to back until the layer that meets the predefined conditions is found (for the first time), and then it is judged that this overlapped SBFD symbol is Override/Converted to the Symbol type corresponding to this layer. The predefined conditions here can be: based on the Symbol type corresponding to this layer, the dynamically scheduled transmission does not overlap with any reverse direction Subband and Guardband in the frequency domain.

Optionally, Case 1 can be further divided into the following two cases:

Case 1-1: The dynamically scheduled transmission overlaps with the opposite subband (including possible guardband) in the frequency domain pattern configured in the overlapped SBFD symbol;

Case 1-2: The dynamically scheduled transmission does not overlap with the opposite subband (including possible guardband) in the frequency domain pattern configured within the overlapped SBFD symbol(s).

For Case 1-1, perform at least one of the above operations 1-1 and 1-2. For Case 1-2, the dynamically scheduled transmission can be directly judged as Valid, and there is no need to perform the above operations 1-1 or 1-2.

Case 2: When the scheduling DCI indicates that the SBFD pattern should not be rewritten for the overlapped SBFD symbol, any one of the following operations 2-1, 2-2, and 2-3 can be performed:

Operation 2-1: When a dynamically scheduled transmission overlaps with a reverse subband (including possible guardband) in the frequency domain pattern configured in the overlapped SBFD symbol, any RE occupied by the dynamically scheduled transmission in the reverse subband (including possible guardband) is judged to be invalid. When executing this dynamically scheduled transmission, the terminal may perform rate matching or puncturing for the invalid RE.

Operation 2-2: When a dynamically scheduled transmission overlaps with the opposite direction Subband (including possible Guardband) in the frequency domain pattern configured in the overlapped SBFD symbol, the dynamically scheduled transmission is judged as Invalid and the terminal does not perform the dynamically scheduled transmission.

Operation 2-3: The terminal does not expect the dynamically scheduled transmission to overlap the frequency domain configured in the SBFD symbol The opposite direction Subbands (including possible Guardbands) in the pattern overlap.

Optionally, in an embodiment of the present application, the above-mentioned first indication information indicates a target time domain unit type of a target time domain unit, and the target time domain unit is a time domain unit that overlaps with a dynamically scheduled transmission, or a time domain unit that overlaps with a time slot where a dynamically scheduled transmission is located; the number of indication bits of the above-mentioned first indication information is determined according to the number of candidate target time domain unit types in a set of candidate target time domain unit types.

The above candidate target time domain unit type set is specified by a protocol or configured by high-level signaling.

Optionally, in an embodiment of the present application, the above-mentioned first indication information indicates the common target time domain unit type of each time domain unit that overlaps with the dynamically scheduled transmission or the time slot where the transmission is located; or, the above-mentioned first indication information only indicates the common target time domain unit type of each SBFD time domain unit that overlaps with the dynamically scheduled transmission.

Optionally, in an embodiment of the present application, when the frequency domain resources occupied by the dynamically scheduled transmission overlap with the reverse subband in the frequency domain pattern corresponding to the target time domain unit type, any one of the following operations is performed:

Any RE occupied by dynamically scheduled transmission in the reverse subband is judged as invalid. When performing dynamically scheduled transmission, the terminal can perform rate matching or puncturing operations on the invalid REs;

The dynamically scheduled transmission is judged to be invalid, and the terminal does not perform the dynamically scheduled transmission;

The terminal does not expect the dynamically scheduled transmission to overlap with the reverse subband in the frequency domain pattern configured in the target time domain unit.

Exemplarily, for the above-mentioned indication method 1, another situation may adopt the following indication method 1-2: the scheduling DCI directly indicates the target symbol type of the symbol occupied by the dynamically scheduled transmission or the time slot in which the transmission is located, and the number of indication bits depends on the size of the candidate target symbol type set, or the number of candidate target symbol types in the set.

Among them, the candidate target symbol type set can be specified by the protocol or configured by high-level signaling, such as Example 1 and Example 2 below (when actually determining the candidate target symbol type set, the candidate target symbol type set or a subset thereof corresponding to these examples can be selected, or other candidate target symbol type sets can be selected).

Specifically, any of the following indication methods 1-2-1 and 1-2-2 may be used:

Indication method 1-2-1: uniformly indicating the common target symbol type of each symbol occupied by the dynamically scheduled transmission or the time slot where the transmission is located.

A dynamically scheduled transmission or a time slot in which a transmission is located may overlap with multiple symbol types in the time domain. In other words, the Symbol occupied by a dynamically scheduled transmission or a time slot in which a transmission is located may correspond to more than one symbol type before the indicated common target symbol type is applied, and the corresponding symbol type may be different from the indicated common target symbol type.

This approach makes it easy to treat dynamically scheduled transmissions or time slots in which transmissions are located as a whole and uniformly apply configuration parameters corresponding to a common target symbol type.

Indication method 1-2-2: Only indicates the common target symbol type of each SBFD symbol occupied by dynamically scheduled transmissions.

Compared with indication method 1-2-1, indication method 1-2-2 only applies the indicated common target symbol type to the SBFD symbol occupied by dynamically scheduled transmission. This is mainly because in some scenarios, it is not allowed/desirable to dynamically adjust the symbol type corresponding to the Symbol that is not configured with SBFD operation, and Dynamic SBFD is limited to the SBFD symbol range.

It should be noted that the above indication method 1-2-2 can be implemented by the base station to ensure parameter consistency/compatibility between the symbols occupied by the dynamically scheduled transmission.

Optionally, for the above-mentioned indication mode 1-2-1 and indication mode 1-2-2, the above-mentioned operation 2-1, operation 2-2 or operation 2-3 can be further performed based on the overlap of the frequency domain resources occupied by the dynamically scheduled transmission and the reverse direction Subband (including possible Guardband) in the frequency domain pattern corresponding to the target symbol type.

Optionally, in an embodiment of the present application, the above-mentioned first indication information indicates the target time domain unit type corresponding to the target time range; the number of indication bits of the above-mentioned first indication information depends on the size of the candidate target time domain unit type set, or the number of candidate target time domain unit types in the candidate target time domain unit type set.

Optionally, in an embodiment of the present application, the target time range may be determined according to the starting time and the application duration. The application duration is indicated by the DCI, or configured by high-level signaling, or is a duration in a duration list configured by high-level signaling.

The starting time is any of the following:

The start time of the scheduled DCI transmission;

The start time of the time slot in which the DCI scheduled transmission is located;

Determined by the end time and scheduled duration of the scheduled DCI.

Optionally, in an embodiment of the present application, the terminal expects that all DCI-scheduled transmissions are within a target time range.

Exemplarily, for the above-mentioned indication method 1, another situation may adopt the following indication method 1-3: directly indicating the target symbol type corresponding to the target time range in the scheduling DCI, and the number of indication bits depends on the size of the candidate target symbol type set, or the number of candidate target symbol types in the set.

The determination of the candidate target symbol type set may adopt the corresponding description in the above indication method 1-2.

The above starting time can be any of the following:

The start time of the earliest transmission scheduled by the DCI;

For example, when the scheduling DCI only schedules a single transmission, the start time here is the start time of the first Symbol occupied by this transmission; when the scheduling DCI schedules multiple transmissions, the start time here is the start time of the first Symbol occupied by the transmission with the earliest start time.

The start time of the time slot where the earliest transmission scheduled by the DCI is located;

Determined by the end time of the scheduled DCI and the predefined duration.

Optionally, in an embodiment of the present application, the above-mentioned predefined duration may be specified by a protocol or configured by a high-level signaling; or, the above-mentioned predefined duration may be directly indicated in the DCI, or indicate one of the duration lists configured by the high-level signaling. It should be noted that when determining the predefined duration, the capability of the terminal may be considered.

Optionally, in an embodiment of the present application, the terminal expects that all transmissions scheduled by the DCI are within a target time range.

Optionally, in an embodiment of the present application, in the first case, the above-mentioned candidate target time domain unit type set includes at least one of the following: a non-SBFD time domain unit (non-SBFD symbol), a SBFD time domain unit for the first duplex mode (SBFD symbol for duplex mode 1), and a SBFD time domain unit for the second duplex mode (SBFD symbol for duplex mode 2).

The first situation is to only allow selection of turning on or off the SBFD operation, and selection of the operation type when turning on the SBFD operation.

Example 1 (first case): Only pay attention to whether the Symbol supports SBFD operation, and the operation type when supporting SBFD operation; TDD mode configuration maintains the existing mechanism unchanged. At this time, you can only choose to turn on/off SBFD operation, and the operation type when turning on SBFD operation.

For example, the non-SBFD symbol can be a DL/UL/Flexible symbol based on legacy TDD pattern configuration.

Optionally, in an embodiment of the present application, when Duplex mode 2 is further subdivided into multiple Duplex modes according to different dimensions, the SBFD symbol for duplex mode 2 here can be further replaced by SBFD symbol types corresponding to these multiple Duplex modes, for example, SBFD symbol for duplex mode 2A, SBFD symbol for duplex mode 2B and SBFD symbol for duplex mode 2C.

Optionally, in the embodiment of the present application, in the second case, the candidate target time domain unit type set includes at least one of the following:

Downlink non-SBFD time domain unit (DL non-SBFD symbol);

Uplink non-SBFD time domain unit (UL non-SBFD symbol);

Flexible non-SBFD symbol;

Downlink SBFD time domain unit supporting the first duplex mode (DL SBFD symbol supporting duplex mode 1);

Uplink SBFD time domain unit supporting the first duplex mode (UL SBFD symbol supporting duplex mode 1);

Flexible SBFD time domain unit supporting duplex mode 1 (Flexible SBFD symbol supporting duplex mode 1);

Downlink SBFD time domain unit supporting the second duplex mode (DL SBFD symbol supporting duplex mode 2);

Uplink SBFD time domain unit supporting the second duplex mode (UL SBFD symbol supporting duplex mode 2);

Flexible SBFD time domain unit supporting duplex mode 2 (Flexible SBFD symbol supporting duplex mode 2).

The second situation is to allow the selection of turning on or off the SBFD operation, to select the operation type when the SBFD operation is turned on, and to modify the time domain unit type determined based on the TDD mode configuration information.

It should be noted that a DL non-SBFD symbol can be understood as a non-SBFD symbol, and this symbol only supports downlink reception, and can also be understood as a Full DL symbol.

A UL non-SBFD symbol can be understood as a non-SBFD symbol, and this symbol only supports uplink transmission, and can also be understood as a Full UL symbol.

A Flexible non-SBFD symbol can be understood as a non-SBFD symbol, and this symbol only supports the operations corresponding to the Flexible symbol in the protocol specifications of 3GPP Rel-15/16/17. It can also be understood as a Full flexible symbol.

A DL SBFD symbol supporting duplex mode 1 can be understood as an SBFD symbol, which supports Duplex mode 1 and the Frequency domain pattern applied in this symbol follows the SBFD pattern configured for Duplex mode 1 of the DL symbol (for the understanding of DL symbol, see the corresponding description in the previous text).

A UL SBFD symbol supporting duplex mode 1 can be understood as an SBFD symbol, which supports Duplex mode 1 and the Frequency domain pattern applied in this symbol follows the SBFD pattern configured for Duplex mode 1 of the UL symbol (for the understanding of UL symbol, see the corresponding description in the previous text).

A Flexible SBFD symbol supporting duplex mode 1 can be understood as an SBFD symbol that supports Duplex mode 1 and the Frequency domain pattern applied in this symbol follows the SBFD pattern configured for Duplex mode 1 of the Flexible symbol (for the understanding of Flexible symbol, see the corresponding description in the previous text).

A DL SBFD symbol supporting duplex mode 2 can be understood as an SBFD symbol, which supports Duplex mode 2 and the Frequency domain pattern applied in this symbol follows the SBFD pattern configured for Duplex mode 2 of the DL symbol (for the understanding of DL symbol, see the corresponding description in the previous text).

A UL SBFD symbol supporting duplex mode 2 can be understood as an SBFD symbol, Duplex mode 2 is supported within this symbol, and the Frequency domain pattern applied within this symbol follows the SBFD pattern configured for Duplex mode 2 of the UL symbol (for the understanding of UL symbol, see the corresponding description in the previous text).

A Flexible SBFD symbol supporting duplex mode 2 can be understood as an SBFD symbol that supports Duplex mode 2 and the Frequency domain pattern applied in this symbol follows the SBFD pattern configured for Duplex mode 2 of the Flexible symbol (for the understanding of Flexible symbol, see the corresponding description in the previous text).

Example 2 (Second Case): Focus on SBFD operation on/off/operation type, and all possible combinations of symbol types involved in the existing TDD pattern configuration information. In addition to being able to choose to turn on/off SBFD operation, and the operation type when turning on SBFD operation, you can also modify the symbol type determined based on the TDD pattern configuration information.

Optionally, in an embodiment of the present application, when Duplex mode 2 is further subdivided into multiple Duplex modes according to different dimensions, each candidate target time domain unit type corresponding to Duplex mode 2 can be further replaced by the SBFD symbol types corresponding to these multiple Duplex modes, for example, replacing DL SBFD symbol supporting duplex mode 2 with DL SBFD symbol supporting duplex mode 2A, DL SBFD symbol supporting duplex mode 2B and DL SBFD symbol supporting duplex mode 2C.

It should be noted that, for the above-mentioned indication mode 2 (UE specific scheduling signaling implicit indication), the protocol may specify or the high-level signaling may configure the scheduling DCI to rewrite the SBFD pattern for the overlapped SBFD symbol and perform the operations corresponding to the above-mentioned Case 1.

For example, for the above indication method 3: indicating through Group common signalling. Specifically, any of the following indication methods 3-1 and 3-2 may be used:

Indication method 3-1: Introducing/using indication information dedicated to indicating the target symbol type.

The indication information here can be carried using the newly introduced DCI format or the existing DCI format (such as DCI format 2_0). The indication information can directly indicate the target symbol type and the time range of application.

Optionally, in the embodiment of the present application, for a semi-statically configured SBFD time domain unit, the first indication information indicates any one of the following:

The type of the SBFD time domain unit is a SBFD time domain unit of the first duplex mode or a SBFD time domain unit of the second duplex mode;

Fallback is a non-SBFD time domain unit.

Optionally, in the embodiment of the present application, when a specific SBFD symbol type (SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2) is indicated in the semi-static configuration, the specific SBFD symbol type can be switched, and the semi-statically configured SBFD symbol for duplex mode 1 is switched to SBFD symbol for duplex mode 2 or switch the semi-statically configured SBFD symbol for duplex mode 2 to SBFD symbol for duplex mode 1.

Optionally, in an embodiment of the present application, for a semi-statically configured non-SBFD time domain unit, the target time domain unit type indicated by the first indication information is the same as the semi-statically configured time domain unit type.

Optionally, in an embodiment of the present application, the above-mentioned first indication information is also used to indicate a semi-static flexible time domain unit (Semi-static flexible symbol) as an uplink time domain unit or a downlink time domain unit, or to indicate a non-SBFD time domain unit as a SBFD time domain unit.

It should be noted that here, the non-SBFD symbol is indicated as an SBFD symbol, which only indicates that it is an SBFD symbol, or indicates a specific SBFD symbol type.

Indication method 3-2: Extend/reinterpret the indication information of the Slot Format Indication (SFI) in DCI format 2_0.

Optionally, in an embodiment of the present application, for a semi-statically configured SBFD time domain unit, a target time domain unit type corresponding to a first value in a time slot format indicated in an SFI specified by a protocol or configured by high-level signaling includes at least one of the following: D, F, U.

Optionally, in an embodiment of the present application, for a semi-static downlink time domain unit configured with an uplink subband (Semi-static DL symbol with UL subband):

The first value D corresponds to a complete downlink time domain unit;

The first value F corresponds to the SBFD time domain unit of the second duplex mode;

The first value U corresponds to the SBFD time domain unit of the first duplex mode.

Optionally, in an embodiment of the present application, for a semi-static flexible symbol with UL subband:

The first value D corresponds to a complete downlink time domain unit;

The first value F corresponds to the SBFD time domain unit;

The first value U corresponds to a complete uplink time domain unit.

Optionally, in the embodiment of the present application, the first value F corresponds to a SBFD time domain unit, and may be further configured by high-level signaling or indicated by DCI as whether it is a SBFD time domain unit of the first duplex mode or a SBFD time domain unit of the second duplex mode.

Optionally, in the embodiment of the present application, for the semi-statically configured non-SBFD symbol, the SFI mechanism in the protocol specification of 3GPP Rel-15/16/17 may be used. Optionally, the non-SBFD symbol may be indicated as a SBFD symbol (only indicating that it is a SBFD symbol, or indicating a specific SBFD symbol type).

Optionally, in the embodiment of the present application, for the above indication mode 1/2/3 (and the sub-indication modes included therein), the adjustment of the time domain unit type includes at least one of the following:

Allows changing the duplex mode corresponding to the SBFD time domain unit;

Allows SBFD time domain units to be indicated or reverted to non-SBFD time domain units;

It is not allowed to indicate a non-SBFD time domain unit as a SBFD time domain unit.

Optionally, in an embodiment of the present application, when the duplex mode corresponding to the SBFD time domain unit is allowed to be changed, it can be understood as indicating/modifying the SBFD symbol for duplex mode 1 to the SBFD symbol for duplex mode 2, or indicating/modifying the SBFD symbol for duplex mode 2 to the SBFD symbol for duplex mode 1.

Optionally, in an embodiment of the present application, it is allowed to indicate or modify the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode. The terminal operates in Duplex mode 2 by default in the SBFD symbol to improve transmission flexibility and latency performance, and only falls back to Duplex mode 1 when needed or when specific conditions are met.

Optionally, in an embodiment of the present application, when an SBFD time domain unit is indicated or rolled back to a non-SBFD time domain unit, the time domain unit type is determined based on TDD mode configuration information.

It should be noted that the specific time domain unit type here (specifically DL/UL/Flexible time domain unit) is determined based on the TDD pattern configuration information. Please refer to the corresponding description in the above embodiment and will not be repeated here.

Optionally, in an embodiment of the present application, when the SBFD time domain unit meets a predetermined condition, the SBFD time domain unit is allowed to be indicated or rolled back to a non-SBFD time domain unit, and the predetermined condition includes at least one of the following:

PRACH opportunities are not mapped in the SBFD time domain unit;

The SBFD time domain unit is a SBFD time domain unit of the first duplex mode or the second duplex mode.

For example, for the unmapped PRACH occasion in the SBFD time domain unit, in order to avoid the failure of the PRACH occasion configured in the UL subband (which leads to different terminals (including legacy terminals) to understand whether this PRACH occasion is effective, and/or the mapping between SSB and PRACH occasion/preamble is different It may be required that the SBFD symbol mapped with the PRACH occasion cannot be indicated/fall back to a non-SBFD symbol, and only when the PRACH occasion is not mapped in the SBFD symbol, it is allowed to be indicated/fall back to a non-SBFD symbol.

Optionally, in the embodiment of the present application, when the non-SBFD time domain unit satisfies a predetermined condition, the non-SBFD time domain unit is allowed to be indicated as a SBFD time domain unit (and/or, further indicated as a SBFD symbol for duplex mode 1 or a SBFD symbol for duplex mode 2), and the predetermined condition includes at least one of the following:

It is not an SSB time domain unit;

Not a protected time domain unit.

Optionally, in the embodiment of the present application, only non-SBFD time domain units are allowed to be indicated as SBFD time domain units of the first duplex mode, so as to avoid the influence of terminal side self-interference.

It should be noted that, for the case where the predetermined conditions include not being an SSB time domain unit, the SSB time domain unit here can be understood as: any time domain unit occupied by any cell definition (Cell Definition, CD)-SSB and/or non-cell definition (Non-Cell Definition, NCD)-SSB configured for any serving cell/current serving cell/current BWP pair (or DL BWP) in the current cell group. Here, it is avoided to dynamically indicate the SSB symbol as an SBFD symbol to ensure the performance of operations such as SSB-based measurements. Optionally, it is allowed to dynamically indicate the SSB time domain unit as an SBFD time domain unit, but the UL subband configured in the time domain unit is actually not effective, or the terminal is not allowed to initiate uplink transmission in the UL subband configured in the time domain unit.

For the case where the predetermined conditions include not being a protected time domain unit, the protected time domain unit here can be determined based on the protocol provisions or high-level signaling configuration. For example, the protocol stipulates that the SSB time domain unit, the time domain unit occupied by the CORESET corresponding to the public search space such as CORESET#0, the time domain unit occupied by the CSI-RS configured for wireless link monitoring/link recovery (including beam failure detection, beam failure recovery, etc.) measurement, and the time domain unit mapped with the PRACH occasion are protected time domain units. For another example, the high-level signaling configures the channel/signal type, or the channel/signal type list, and any time domain unit occupied by this or these types of channels/signals is a protected time domain unit; or, the high-level signaling configures one or more time windows that appear periodically, and any time domain unit within the time window is a protected time domain unit. By avoiding indicating the protected time domain unit as an SBFD time domain unit, the corresponding functions and processes can be prevented from being affected by cross-link interference (Cross Link Interference, CLI) between terminals.

Optionally, in the embodiment of the present application, for the adjustment of the time domain unit type, corresponding terminal capability information is introduced to indicate to the network side the dynamic adjustment operation of the time domain unit type supported or not supported by the terminal. Exemplarily, the dynamic SBFD indication method provided in the embodiment of the present application also includes the following steps 301 and 302.

Step 301: The terminal reports capability information to the network.

Step 302: The network-side device receives capability information from the terminal.

In the embodiment of the present application, the capability information is used to indicate a dynamic adjustment operation for a time domain unit type supported or not supported by the terminal, and the dynamic adjustment operation includes at least one of the following:

Indicating or modifying the SBFD time domain unit of the first duplex mode to the SBFD time domain unit of the second duplex mode;

Indicating or modifying the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode;

Indicating or reverting the SBFD time domain unit of the first duplex mode to a non-SBFD time domain unit;

Indicating or reverting the SBFD time domain unit of the second duplex mode to a non-SBFD time domain unit;

indicating the non-SBFD time domain unit as a SBFD time domain unit of the first duplex mode;

The non-SBFD time domain unit is indicated as a SBFD time domain unit of the second duplex mode.

Optionally, in the embodiment of the present application, the dynamic SBFD indication method provided in the embodiment of the present application further includes the following step 303.

Step 303: When the capability information indicates that the terminal does not support the first dynamic adjustment operation, the terminal performs any of the following:

The terminal does not expect to receive dynamic signaling from the network side to indicate the first dynamic adjustment operation;

In a case where the terminal receives dynamic signaling from the network side to indicate a first dynamic adjustment operation, the terminal ignores the dynamic signaling;

When the terminal receives dynamic signaling from the network side to indicate the first dynamic adjustment operation, the terminal executes a predefined operation specified by the protocol or configured by the high-layer signaling.

For example, when the terminal does not support the indication/fallback of the SBFD symbol for duplex mode 2 to a non-SBFD symbol, if the dynamic signaling from the network side indicates that a certain SBFD symbol for duplex mode 2 is to be fallen back to a non-SBFD symbol, the terminal falls back the SBFD symbol for duplex mode 2 to only SBFD symbol for duplex mode 1 (predefined operation).

Optionally, in an embodiment of the present application, the type of actual application determined for the target time domain unit based on the first indication information is applied to at least one of the following within the target time domain unit: dynamically scheduled transmission, semi-statically configured transmission.

Optionally, in an embodiment of the present application, when the type of actual application determined for the target time domain unit based on the first indication information is applied to the transmission of the semi-static configuration within the target time domain unit, any one of the following operations is performed for the transmission of the semi-static configuration:

Any RE occupied by the semi-statically configured transmission in the reverse subband is judged to be invalid. When the terminal performs the semi-statically configured transmission, it can perform rate matching or puncturing operations on the invalid REs.

The transmission of the semi-static configuration is judged to be invalid, and the terminal does not perform the transmission of the semi-static configuration;

The terminal does not expect the semi-statically configured transmission to overlap with the opposite subband in the frequency domain pattern configured in the target time domain unit.

Optionally, in an embodiment of the present application, when for a first type of transmission, corresponding configuration parameters are configured or indicated for different time domain unit types, when a first transmission corresponding to the first type of transmission is performed in a second time domain unit, a first configuration parameter is applied for the first transmission, wherein the first configuration parameter is a configuration parameter configured or indicated when the first type of transmission is transmitted in a time domain unit of the first time domain unit type, and the first time domain unit type is the type actually applied to the second time domain unit.

Optionally, in an embodiment of the present application, the above-mentioned first type of transmission may include semi-statically configured PUCCH transmission, dynamically scheduled PUSCH transmission, etc.

It should be noted that the time domain unit type actually effective determined for a time domain unit based on the above indication mode 1/2 can at least be applied to dynamically scheduled transmission. Optionally, the determined time domain unit type actually effective can also be applied to semi-statically configured transmission within the time domain unit.

The actually effective time domain unit type determined for a certain time domain unit based on the above indication mode 3 can be applied to both dynamically scheduled transmission and semi-statically configured transmission.

When the time domain unit type that actually takes effect is applied to the transmission of the semi-static configuration, any one of the above operations 2-1/2-2/2-3 may be performed for the transmission of the semi-static configuration.

An embodiment of the present application provides a dynamic SBFD indication method, and a terminal can receive a first signaling from a network-side device, the first signaling includes a first indication information, and according to the first indication information, adjust the type of the target time domain unit, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling. In this solution, for SBFD based on full-duplex on the terminal side, the time domain unit type actually applied can be dynamically adjusted for the time domain unit that can support full-duplex on the terminal side to support dynamic SBFD, so that uplink transmission and downlink reception can flexibly utilize available resources, so that available resources can be flexibly and dynamically matched to service needs, so as to improve performance such as service transmission delay.

Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation method can be determined according to actual usage requirements, and the embodiments of the present application do not limit this.

The dynamic SBFD indication method provided in the embodiment of the present application may be executed by a dynamic SBFD indication device. In the embodiment of the present application, the dynamic SBFD indication method executed by a dynamic SBFD indication device is taken as an example to illustrate the dynamic SBFD indication device provided in the embodiment of the present application.

FIG5 shows a possible structural diagram of a dynamic SBFD indicating device involved in an embodiment of the present application. As shown in FIG5 , a dynamic SBFD indicating device 40 may include: a receiving module 41 and an adjusting module 42 .

The receiving module 41 is used to receive a first signaling from a network side device, the first signaling includes a first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling. The adjustment module 42 is used to adjust the type of the target time domain unit according to the first indication information received by the receiving module 41.

An embodiment of the present application provides a dynamic SBFD indication device. For SBFD based on terminal-side full-duplex, the dynamic SBFD indication device can dynamically adjust the time domain unit type actually applied for the time domain unit that can support terminal-side full-duplex to support dynamic SBFD, so that uplink transmission and downlink reception can flexibly utilize available resources, thereby making available resources flexibly and dynamically match business needs to improve performance such as business transmission delay.

In a possible implementation, the dynamic SBFD indication device provided in the embodiment of the present application further includes: a determination module. The determination module is configured to determine, before the receiving module 41 obtains the first indication information, In the case of full duplex of the sub-band, determining a type of at least one SBFD time domain unit;

The type of the SBFD time domain unit includes at least one of the following: a SBFD time domain unit of a first duplex mode, a SBFD time domain unit of a second duplex mode;

Among them, the first duplex mode is that within a single SBFD time domain unit, the terminal can only perform uplink transmission or downlink reception; the second duplex mode is that within a single SBFD time domain unit, the terminal can perform uplink transmission and downlink reception at the same time.

In a possible implementation manner, the terminal does not expect the first time domain unit to be configured as an SBFD time domain unit of the second duplex mode, and the first time domain unit includes at least one of the following: an SSB time domain unit, and an SBFD time domain unit configured with a PRACH opportunity.

In a possible implementation, within the same target object, in the frequency domain pattern configured or applied to the SBFD time domain unit of the first duplex mode and the SBFD time domain unit of the second duplex mode, the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode is greater than or equal to the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode;

The target object includes at least one of the following: a carrier, a serving cell, and a BWP pair.

In a possible implementation, the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the second duplex mode is located within the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the first duplex mode, and the first frequency band includes at least one of the following: an uplink sub-band and a downlink sub-band;

The frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode is located within the frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode.

In a possible implementation, the first indication information indicates whether to rewrite the SBFD mode of the target time domain unit, which is an SBFD time domain unit overlapping with the dynamically scheduled transmission; the adjustment module 42 is specifically used to adjust the type of the target time domain unit according to the first indication information and the first fallback level, and the first fallback level is a fallback level for a single SBFD time domain unit specified by the protocol or configured by high-level signaling.

In a possible implementation, the first fallback level satisfies any of the following:

The lower or later the fallback level is, the less frequency domain resources the guard band occupies;

The lower or later the fallback level is, the more frequency domain resources can be used in the corresponding transmission direction.

In a possible implementation, the adjustment module 42 is specifically configured to, if the first indication information indicates rewriting the SBFD mode, then the terminal judges layer by layer from high to low or from front to back according to the first fallback level until the first level that meets the predetermined condition is found, and then determine that the target time domain unit is rewritten to the time domain unit type corresponding to the first level;

The predetermined condition is that: based on the time domain unit type corresponding to the first level, there is no overlap between the dynamically scheduled transmission and any sub-band and guard band in the opposite direction in the frequency domain.

In a possible implementation manner, the first indication information indicates a target time domain unit type of the target time domain unit, and the target time domain unit is a time domain unit overlapping with the dynamically scheduled transmission, or a time domain unit overlapping with the time slot where the dynamically scheduled transmission is located;

The number of indication bits of the first indication information is determined according to the number of candidate target time domain unit types in the candidate target time domain unit type set;

The candidate target time domain unit type set is specified by a protocol or configured by a high-level signaling.

In a possible implementation manner, the first indication information indicates a common target time domain unit type of each time domain unit overlapping with the dynamically scheduled transmission or the time slot in which the transmission is located;

Alternatively, the first indication information only indicates the common target time domain unit type of each SBFD time domain unit overlapping with the dynamically scheduled transmission.

In a possible implementation manner, when the frequency domain resources occupied by the dynamically scheduled transmission overlap with the reverse direction subband in the frequency domain pattern corresponding to the target time domain unit type, any one of the following operations is performed:

Any resource unit RE occupied by the dynamically scheduled transmission in the reverse subband is judged to be invalid. When the terminal performs the dynamically scheduled transmission, it can perform rate matching or puncturing operations on the invalid RE;

The dynamically scheduled transmission is judged to be invalid, and the terminal does not perform the dynamically scheduled transmission;

The terminal does not expect the dynamically scheduled transmission to overlap with the reverse subband in the frequency domain pattern configured in the target time domain unit.

In a possible implementation, the first indication information indicates the target time domain unit type corresponding to the target time range; the number of indication bits of the first indication information depends on the size of the candidate target time domain unit type set, or the number of candidate target time domain unit types in the candidate target time domain unit type set.

In a possible implementation, the target time range may be determined based on the starting time and application duration;

The application duration is indicated by downlink control information DCI, or configured by higher-layer signaling, or is a duration in a duration list configured by higher-layer signaling;

The starting time is any of the following:

The start time of the scheduled DCI transmission;

The start time of the time slot in which the DCI scheduled transmission is located;

Determined by the end time and scheduled duration of the scheduled DCI.

In a possible implementation, the terminal expects that all transmissions scheduled by the DCI are within a target time range.

In a possible implementation, in a first case, the candidate target time domain unit type set includes at least one of the following: a non-SBFD time domain unit, a SBFD time domain unit of a first duplex mode, and a SBFD time domain unit of a second duplex mode;

The first case allows only the selection of turning on or off the SBFD operation, and the selection of the operation type when turning on the SBFD operation.

In a possible implementation, in the second case, the candidate target time-domain unit type set includes at least one of the following:

Downlink non-SBFD time domain unit;

Uplink non-SBFD time domain unit;

Flexible non-SBFD time domain unit;

A downlink SBFD time domain unit supporting the first duplex mode;

An uplink SBFD time domain unit supporting the first duplex mode;

Flexible SBFD time domain unit supporting the first duplex mode;

Downlink SBFD time domain unit supporting the second duplex mode;

Uplink SBFD time domain unit supporting the second duplex mode;

Flexible SBFD time domain unit supporting second duplex mode;

The second case allows the selection of turning on or off the SBFD operation, and the selection of the operation type when the SBFD operation is turned on, and the modification of the time domain unit type determined based on the TDD mode configuration information.

In a possible implementation manner, for a semi-statically configured SBFD time domain unit, the first indication information indicates any one of the following:

The type of the SBFD time domain unit is a SBFD time domain unit of the first duplex mode or a SBFD time domain unit of the second duplex mode;

Fallback to non-SBFD time domain units.

In a possible implementation manner, for a semi-statically configured non-SBFD time domain unit, the target time domain unit type indicated by the first indication information is the same as the semi-statically configured time domain unit type.

In a possible implementation manner, the first indication information is further used to indicate that the semi-static flexible time domain unit is an uplink time domain unit or a downlink time domain unit, or to indicate that the non-SBFD time domain unit is an SBFD time domain unit.

In a possible implementation, for a semi-statically configured SBFD time domain unit, the target time domain unit type corresponds to a first value in a time slot format indicated in a time slot format indicator SFI specified by a protocol or configured by high-level signaling, and the first value includes at least one of the following: D, F, U.

In a possible implementation, for a semi-static downlink time domain unit configured with an uplink subband:

The first value D corresponds to a complete downlink time domain unit;

The first value F corresponds to the SBFD time domain unit of the second duplex mode;

The first value U corresponds to the SBFD time domain unit of the first duplex mode.

In a possible implementation, for a semi-static flexible time domain unit configured with an uplink subband:

The first value D corresponds to a complete downlink time domain unit;

The first value F corresponds to the SBFD time domain unit;

The first value U corresponds to a complete uplink time domain unit.

In a possible implementation manner, the adjustment of the time domain unit type includes at least one of the following:

Allows changing the duplex mode corresponding to the SBFD time domain unit;

Allows SBFD time domain units to be indicated or reverted to non-SBFD time domain units;

It is not allowed to indicate a non-SBFD time domain unit as a SBFD time domain unit.

In a possible implementation manner, it is allowed to indicate or modify the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode.

In a possible implementation manner, when the SBFD time domain unit is indicated or rolled back to a non-SBFD time domain unit, the time domain unit type is determined based on the TDD mode configuration information.

In a possible implementation, when the SBFD time domain unit meets a predetermined condition, the SBFD time domain unit is allowed to be indicated or rolled back to a non-SBFD time domain unit, and the predetermined condition includes at least one of the following:

PRACH opportunities are not mapped in the SBFD time domain unit;

The SBFD time domain unit is a SBFD time domain unit of the first duplex mode or the second duplex mode.

In a possible implementation, when a non-SBFD time domain unit satisfies a predetermined condition, the non-SBFD time domain unit is allowed to be indicated as a SBFD time domain unit, and the predetermined condition includes at least one of the following:

It is not an SSB time domain unit;

Not a protected time domain unit.

In a possible implementation, only non-SBFD time domain units are allowed to be indicated as SBFD time domain units of the first duplex mode.

In a possible implementation, the dynamic SBFD indication device provided in the embodiment of the present application further includes: a sending module. The sending module is used to report capability information to the network side, and the capability information is used to indicate the dynamic adjustment operation of the time domain unit type supported or not supported by the terminal, and the dynamic adjustment operation includes at least one of the following:

Indicating or modifying the SBFD time domain unit of the first duplex mode to the SBFD time domain unit of the second duplex mode;

Indicating or modifying the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode;

Indicating or reverting the SBFD time domain unit of the first duplex mode to a non-SBFD time domain unit;

Indicating or reverting the SBFD time domain unit of the second duplex mode to a non-SBFD time domain unit;

indicating the non-SBFD time domain unit as a SBFD time domain unit of the first duplex mode;

The non-SBFD time domain unit is indicated as a SBFD time domain unit of the second duplex mode.

In a possible implementation, the dynamic SBFD indication device provided in the embodiment of the present application further includes: an execution module. The execution module is configured to execute any one of the following when the capability information indicates that the terminal does not support the first dynamic adjustment operation:

Not expecting to receive dynamic signaling from the network side to indicate the first dynamic adjustment operation;

In a case where the terminal receives dynamic signaling from the network side to indicate a first dynamic adjustment operation, ignoring the dynamic signaling;

When the terminal receives dynamic signaling from the network side to indicate a first dynamic adjustment operation, a predefined operation specified by a protocol or configured by a high-layer signaling is executed.

In a possible implementation, the dynamic SBFD indication device provided in the embodiment of the present application further includes: an execution module. The execution module is configured to, for the same time domain unit, perform any of the following when determining the time domain unit type that is actually effective based on multiple scheduling DCIs or group common DCIs:

Determine the time domain unit type that is actually effective for the same time domain unit based on the last DCI;

It is expected that the actually effective time domain unit type determined based on any DCI for the same time domain unit is the same;

The levels of the time domain unit types actually effective for the same time domain unit in the fallback hierarchy are determined based on each DCI, and the time domain unit types actually effective are determined based on the multiple levels and predefined rules.

In a possible implementation manner, the type of actual application determined for the target time domain unit based on the first indication information is applied to at least one of the following items in the target time domain unit: dynamically scheduled transmission and semi-statically configured transmission.

In a possible implementation manner, when the type of actual application determined for the target time domain unit based on the first indication information is applied to the transmission of the semi-static configuration in the target time domain unit, any one of the following operations is performed for the transmission of the semi-static configuration:

Any resource unit RE occupied by the semi-statically configured transmission in the reverse subband is judged to be invalid. When the terminal performs the semi-statically configured transmission, it can perform rate matching or puncturing operations on the invalid RE;

The transmission of the semi-static configuration is judged to be invalid, and the terminal does not perform the transmission of the semi-static configuration;

The terminal does not expect the semi-statically configured transmission to overlap with the opposite subband in the frequency domain pattern configured in the target time domain unit.

In one possible implementation, for a first type of transmission, when corresponding configuration parameters are configured or indicated for different time domain unit types, when a first transmission corresponding to the first type of transmission is performed in a second time domain unit, a first configuration parameter is applied for the first transmission, wherein the first configuration parameter is a configuration parameter configured or indicated when the first type of transmission is transmitted in a time domain unit of the first time domain unit type, and the first time domain unit type is the type actually applied by the second time domain unit.

The dynamic SBFD indicating device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The terminal may also be other devices other than the terminal. For example, the terminal may include but is not limited to the types of the terminal 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiments of the present application.

The dynamic SBFD indication device provided in the embodiment of the present application can implement each process implemented in the above-mentioned dynamic SBFD indication method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

Fig. 6 shows a possible structural diagram of a dynamic SBFD indicating device involved in an embodiment of the present application. As shown in Fig. 6 , a dynamic SBFD indicating device 50 may include: a sending module 51 .

Among them, the sending module 51 is used to send a first signaling to the terminal, and the first signaling includes first indication information, and the first indication information is used to indicate the type of actual application of the target time domain unit. The target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is a terminal-specific scheduling signaling or a group common signaling; wherein, the first indication information is used to adjust the type of the target time domain unit.

An embodiment of the present application provides a dynamic SBFD indication device. For SBFD based on terminal-side full-duplex, the dynamic SBFD indication device can send first indication information to the terminal, so that the terminal dynamically adjusts the time domain unit type actually applied for the time domain unit that can support terminal-side full-duplex to support dynamic SBFD, so that uplink transmission and downlink reception can flexibly utilize available resources, thereby making available resources flexibly and dynamically match business needs to improve performance such as business transmission delay.

In a possible implementation manner, the first indication information indicates whether to rewrite the SBFD mode of the target time domain unit, where the target time domain unit is a SBFD time domain unit overlapping with the dynamically scheduled transmission;

The first indication information is specifically used to adjust the type of the target time domain unit according to the first fallback level, where the first fallback level is a fallback level for a single SBFD time domain unit specified by the protocol or configured by high-layer signaling.

In a possible implementation manner, the first indication information indicates a target time domain unit type of the target time domain unit, and the target time domain unit is a time domain unit overlapping with the dynamically scheduled transmission, or a time domain unit overlapping with the time slot where the dynamically scheduled transmission is located;

The number of indication bits of the first indication information is determined according to the number of candidate target time domain unit types in the candidate target time domain unit type set;

The candidate target time domain unit type set is specified by a protocol or configured by a high-level signaling.

In a possible implementation, the first indication information indicates the target time domain unit type corresponding to the target time range; the number of indication bits of the first indication information depends on the size of the candidate target time domain unit type set, or the number of candidate target time domain unit types in the candidate target time domain unit type set.

In a possible implementation, the dynamic SBFD indication device provided in the embodiment of the present application further includes: a receiving module. The receiving module is used to receive capability information from a terminal, where the capability information is used to indicate a dynamic adjustment operation of a time domain unit type supported or not supported by the terminal, where the dynamic adjustment operation includes at least one of the following:

Indicating or modifying the SBFD time domain unit of the first duplex mode to the SBFD time domain unit of the second duplex mode;

Indicating or modifying the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode;

Indicating or reverting the SBFD time domain unit of the first duplex mode to a non-SBFD time domain unit;

Indicating or reverting the SBFD time domain unit of the second duplex mode to a non-SBFD time domain unit;

indicating the non-SBFD time domain unit as a SBFD time domain unit of the first duplex mode;

The non-SBFD time domain unit is indicated as a SBFD time domain unit of the second duplex mode.

The dynamic SBFD indication device provided in the embodiment of the present application can implement each process implemented in the above-mentioned dynamic SBFD indication method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

As shown in FIG7 , the embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002, and the memory 5002 stores a program or instruction that can be run on the processor 5001. For example, when the communication device 5000 is the above-mentioned terminal, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned terminal side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 5000 is the above-mentioned network side device, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned network side device side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

The embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the above-mentioned dynamic SBFD indication method embodiment. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of a processor 7010.

Those skilled in the art will appreciate that the terminal 7000 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 7010 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system. The terminal structure shown in FIG8 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown, or combine certain components, or arrange components differently, which will not be described in detail here.

It should be understood that in the embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 7001 can transmit the data to the processor 7010 for processing; in addition, the RF unit 7001 can send uplink data to the network side device. Generally, the RF unit 7001 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

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

The processor 7010 may include one or more processing units; optionally, the processor 7010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 7010.

The terminal provided in the embodiment of the present application can implement the various processes implemented by the terminal in the above method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above dynamic SBFD indication method embodiment. To avoid repetition, it will not be repeated here.

The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the above-mentioned dynamic SBFD indication method embodiment. The network side device embodiment corresponds to the above-mentioned network side device side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a network side device. As shown in FIG9 , the network side device 600 includes: an antenna 61, a radio frequency device 62, a baseband device 63, a processor 64 and a memory 65. The antenna 61 is connected to the radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information through the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be sent and sends it to the radio frequency device 62. The radio frequency device 62 processes the received information and sends it out through the antenna 61.

The method executed by the network-side device in the above embodiment may be implemented in the baseband device 63, which includes a baseband processor.

The baseband device 63 may include, for example, at least one baseband board, on which a plurality of chips are arranged, as shown in FIG. 9 , wherein one of the chips is, for example, a baseband processor, which is connected to the memory 65 through a bus interface to call a program in the memory 65 and execute the network device operations shown in the above method embodiment.

The network side device may also include a network interface 66, which is, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 65 and executable on the processor 64. The processor 64 calls the instructions or programs in the memory 65 to execute the methods executed by each module shown in the above-mentioned dynamic SBFD indication device and achieve the same technical effect. To avoid repetition, it will not be repeated here.

An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned dynamic SBFD indication method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned dynamic SBFD indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

The embodiment of the present application further provides a computer program/program product, which is stored in a storage medium. The computer program/program product is executed by at least one processor to implement the various processes of the above-mentioned dynamic SBFD indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

An embodiment of the present application further provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the dynamic SBFD indication method described above, and the network side device can be used to execute the steps of the dynamic SBFD indication method described above.

It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims (38)

A dynamic sub-band full-duplex SBFD indication method, comprising: The terminal receives a first signaling from a network side device, where the first signaling includes first indication information, where the first indication information is used to indicate a type of actual application of a target time domain unit, where the target time domain unit is a time domain unit capable of supporting full-duplex on the terminal side, and where the first signaling is a terminal-specific scheduling signaling or a group common signaling; The terminal adjusts the type of the target time domain unit according to the first indication information. The method according to claim 1, wherein, before the terminal obtains the first indication information, the method further comprises: In a case where the terminal supports subband-based full-duplex, the terminal determines a type of at least one SBFD time domain unit; The type of the SBFD time domain unit includes at least one of the following: a SBFD time domain unit of a first duplex mode, and a SBFD time domain unit of a second duplex mode; The first duplex mode is that within a single SBFD time domain unit, the terminal can only perform uplink transmission or downlink reception; the second duplex mode is that within a single SBFD time domain unit, the terminal can perform uplink transmission and downlink reception at the same time. The method according to claim 2, wherein the method further comprises: The terminal does not expect the first time domain unit to be configured as an SBFD time domain unit of the second duplex mode, wherein the first time domain unit includes at least one of the following: a synchronization signal block SSB time domain unit, and a SBFD time domain unit configured with a physical random access channel PRACH opportunity. The method according to claim 2 or 3, wherein, within the same target object, in the frequency domain pattern configured or applied to the SBFD time domain unit of the first duplex mode and the SBFD time domain unit of the second duplex mode, the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode is greater than or equal to the bandwidth corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode; The target object includes at least one of the following: a carrier, a serving cell, and a bandwidth part BWP pair. The method according to any one of claims 2 to 4, wherein the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the second duplex mode is located within the frequency domain range corresponding to the first sub-band corresponding to the SBFD time domain unit of the first duplex mode, and the first frequency band includes at least one of the following: an uplink sub-band and a downlink sub-band; The frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the first duplex mode is located within the frequency domain range corresponding to the guard band corresponding to the SBFD time domain unit of the second duplex mode. The method according to any one of claims 1 to 5, wherein the first indication information indicates whether to rewrite the SBFD mode of the target time domain unit, the target time domain unit being a SBFD time domain unit overlapping with the dynamically scheduled transmission; The terminal adjusting, according to the first indication information, the type of the target time domain unit, includes: The terminal adjusts the type of the target time domain unit according to the first indication information and a first fallback level, where the first fallback level is a fallback level for a single SBFD time domain unit specified by a protocol or configured by a high-layer signaling. The method according to claim 6, wherein the first fallback level satisfies any of the following: The lower or later the fallback level is, the less frequency domain resources the guard band occupies; The lower or later the fallback level is, the more frequency domain resources can be used in the corresponding transmission direction. The method according to claim 6 or 7, wherein the terminal adjusts the type of the target time domain unit according to the first indication information and the first fallback level, comprising: If the first indication information indicates to rewrite the SBFD mode, the terminal judges layer by layer from high to low or from front to back according to the first fallback layer until a first layer that meets the predetermined condition is found, and then determines that the target time domain unit is rewritten to the time domain unit type corresponding to the first layer; The predetermined condition is that: based on the time domain unit type corresponding to the first layer, there is no overlap between the dynamically scheduled transmission and any sub-band and guard band in the opposite direction in the frequency domain. The method according to any one of claims 1 to 5, wherein the first indication information indicates a target time domain unit type of the target time domain unit, and the target time domain unit is a time domain unit overlapping with a dynamically scheduled transmission, or a time domain unit overlapping with a time slot where a dynamically scheduled transmission is located; The number of indication bits of the first indication information is determined according to the number of candidate target time domain unit types in the candidate target time domain unit type set; The candidate target time domain unit type set is specified by a protocol or configured by high-level signaling. The method according to claim 9, wherein the first indication information indicates a common target time domain unit type of each time domain unit overlapping with the dynamically scheduled transmission or the time slot in which the transmission is located; Alternatively, the first indication information only indicates the common target time domain unit type of each SBFD time domain unit overlapping with the dynamically scheduled transmission. The method according to claim 10, wherein, when the frequency domain resources occupied by the dynamically scheduled transmission overlap with the reverse subband in the frequency domain pattern corresponding to the target time domain unit type, any one of the following operations is performed: Any resource unit RE occupied by the dynamically scheduled transmission in the reverse subband is judged to be invalid, and the terminal may perform rate matching or puncturing operations on the invalid RE when performing the dynamically scheduled transmission; The dynamically scheduled transmission is determined to be invalid, and the terminal does not perform the dynamically scheduled transmission; The terminal does not expect the dynamically scheduled transmission to overlap with a reverse subband in a frequency domain pattern configured in the target time domain unit. The method according to any one of claims 1 to 5, wherein the first indication information indicates the target time domain unit type corresponding to the target time range; the number of indication bits of the first indication information depends on the size of the candidate target time domain unit type set, or the number of candidate target time domain unit types in the candidate target time domain unit type set. The method according to claim 12, wherein the target time range can be determined based on a starting time and an application duration; The application duration is indicated by downlink control information DCI, or configured by high-level signaling, or is a duration in a duration list configured by high-level signaling; The starting time is any one of the following: The start time of the scheduled DCI transmission; The start time of the time slot in which the DCI scheduled transmission is located; Determined by the end time and scheduled duration of the scheduled DCI. The method according to claim 13, wherein the terminal expects that all transmissions scheduled by the DCI are within the target time range. The method according to any one of claims 9 to 14, wherein, in a first case, the set of candidate target time domain unit types includes at least one of the following: a non-SBFD time domain unit, a SBFD time domain unit of a first duplex mode, and a SBFD time domain unit of a second duplex mode; The first situation is to only allow selection of turning on or off the SBFD operation, and to select the operation type when turning on the SBFD operation. The method according to any one of claims 9 to 14, wherein, in the second case, the set of candidate target time domain unit types includes at least one of the following: Downlink non-SBFD time domain unit; Uplink non-SBFD time domain unit; Flexible non-SBFD time domain unit; A downlink SBFD time domain unit supporting the first duplex mode; An uplink SBFD time domain unit supporting the first duplex mode; Flexible SBFD time domain unit supporting the first duplex mode; Downlink SBFD time domain unit supporting the second duplex mode; Uplink SBFD time domain unit supporting the second duplex mode; Flexible SBFD time domain unit supporting second duplex mode; The second case allows selection of turning on or off the SBFD operation, selection of the operation type when the SBFD operation is turned on, and modification of the time domain unit type determined based on the TDD mode configuration information. The method according to claim 1, wherein, for a semi-statically configured SBFD time domain unit, the first indication information indicates any one of the following: The type of the SBFD time domain unit is the SBFD time domain unit of the first duplex mode or the SBFD time domain unit of the second duplex mode. SBFD time domain unit; Fallback to non-SBFD time domain units. The method according to claim 1, wherein, for a semi-statically configured non-SBFD time domain unit, the target time domain unit type indicated by the first indication information is the same as the semi-statically configured time domain unit type. The method according to claim 1, wherein, for a semi-statically configured SBFD time domain unit, a target time domain unit type corresponding to a first value in a time slot format indicated in a time slot format indicator SFI specified by a protocol or configured by high-level signaling, wherein the first value includes at least one of the following: D, F, U. The method according to claim 19, wherein, for a semi-static downlink time domain unit configured with an uplink subband: The first value D corresponds to a complete downlink time domain unit; The first value F corresponds to the SBFD time domain unit of the second duplex mode; The first value U corresponds to a SBFD time domain unit of a first duplex mode; For a semi-static flexible time domain unit with an uplink subband configured: The first value D corresponds to a complete downlink time domain unit; The first value F corresponds to a SBFD time domain unit; The first value U corresponds to a complete uplink time domain unit. The method according to claim 1, wherein the adjustment of the time domain unit type comprises at least one of the following: Allows changing the duplex mode corresponding to the SBFD time domain unit; Allows SBFD time domain units to be indicated or reverted to non-SBFD time domain units; It is not allowed to indicate a non-SBFD time domain unit as a SBFD time domain unit. The method according to claim 21, wherein the SBFD time domain unit of the second duplex mode is allowed to be indicated or modified as the SBFD time domain unit of the first duplex mode. The method according to claim 21, wherein when the SBFD time domain unit satisfies a predetermined condition, the SBFD time domain unit is allowed to be indicated or rolled back to a non-SBFD time domain unit, and the predetermined condition includes at least one of the following: PRACH opportunities are not mapped in the SBFD time domain unit; The SBFD time domain unit is a SBFD time domain unit of the first duplex mode or the second duplex mode; Alternatively, when the non-SBFD time domain unit satisfies a predetermined condition, the non-SBFD time domain unit is allowed to be indicated as a SBFD time domain unit, wherein the predetermined condition includes at least one of the following: It is not an SSB time domain unit; Not a protected time domain unit. The method according to claim 1, wherein the method further comprises: The terminal reports capability information to the network side, where the capability information is used to indicate a dynamic adjustment operation of a time domain unit type supported or not supported by the terminal, where the dynamic adjustment operation includes at least one of the following: Indicating or modifying the SBFD time domain unit of the first duplex mode to the SBFD time domain unit of the second duplex mode; Indicating or modifying the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode; Indicating or reverting the SBFD time domain unit of the first duplex mode to a non-SBFD time domain unit; Indicating or reverting the SBFD time domain unit of the second duplex mode to a non-SBFD time domain unit; indicating the non-SBFD time domain unit as a SBFD time domain unit of the first duplex mode; The non-SBFD time domain unit is indicated as a SBFD time domain unit of the second duplex mode. The method according to claim 24, wherein the method further comprises: When the capability information indicates that the terminal does not support the first dynamic adjustment operation, the terminal performs any one of the following: The terminal does not expect to receive dynamic signaling from the network side to indicate the first dynamic adjustment operation; In a case where the terminal receives dynamic signaling from the network side to indicate the first dynamic adjustment operation, the terminal ignores the dynamic signaling; In a case where the terminal receives dynamic signaling from the network side to instruct the first dynamic adjustment operation, the terminal executes a predefined operation specified by a protocol or configured by a high-layer signaling. The method according to claim 1, wherein the method further comprises: For the same time domain unit, when the time domain unit type that is actually effective is determined based on multiple scheduling DCIs or group common DCIs, the terminal performs any of the following: Determine, based on the last DCI, the time domain unit type that is actually effective for the same time domain unit; The terminal expects that the actually effective time domain unit types determined by the same time domain unit based on any DCI are the same; The levels of the time domain unit types actually effective for the same time domain unit in the fallback hierarchy are determined based on each DCI respectively, and the time domain unit types actually effective are determined based on the multiple levels and predefined rules. The method according to claim 1, wherein, when the type of actual application determined for the target time domain unit based on the first indication information is applied to the transmission of the semi-static configuration within the target time domain unit, any one of the following operations is performed for the transmission of the semi-static configuration: Any resource unit RE occupied by the transmission of the semi-static configuration in the reverse sub-band is judged to be invalid, and the terminal may perform rate matching or puncturing operations on the invalid RE when performing the transmission of the semi-static configuration; The transmission of the semi-static configuration is judged to be invalid, and the terminal does not perform the transmission of the semi-static configuration; The terminal does not expect the semi-statically configured transmission to overlap with a reverse subband in a frequency domain pattern configured in the target time domain unit. The method according to claim 1, wherein, for a first type of transmission, when corresponding configuration parameters are configured or indicated for different time domain unit types, when a first transmission corresponding to the first type of transmission is performed in a second time domain unit, a first configuration parameter is applied for the first transmission, wherein the first configuration parameter is a configuration parameter configured or indicated when the first type of transmission is transmitted in a time domain unit of a first time domain unit type, and the first time domain unit type is a type actually applied to the second time domain unit. A dynamic sub-band full-duplex SBFD indication method, comprising: The network side device sends a first signaling to the terminal, where the first signaling includes first indication information, where the first indication information is used to indicate the type of actual application of the target time domain unit, where the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and where the first signaling is terminal-specific scheduling signaling or group common signaling; The first indication information is used to adjust the type of the target time domain unit. The method according to claim 29, wherein the first indication information indicates whether to rewrite the SBFD mode of the target time domain unit, the target time domain unit being a SBFD time domain unit overlapping with the dynamically scheduled transmission; The first indication information is specifically used to adjust the type of the target time domain unit according to a first fallback level, where the first fallback level is a fallback level for a single SBFD time domain unit specified by a protocol or configured by a high-layer signaling. The method according to claim 29, wherein the first indication information indicates a target time domain unit type of the target time domain unit, and the target time domain unit is a time domain unit overlapping with a dynamically scheduled transmission, or a time domain unit overlapping with a time slot where a dynamically scheduled transmission is located; The number of indication bits of the first indication information is determined according to the number of candidate target time domain unit types in the candidate target time domain unit type set; The candidate target time domain unit type set is specified by a protocol or configured by high-level signaling. The method according to claim 29, wherein the first indication information indicates the target time domain unit type corresponding to the target time range; the number of indication bits of the first indication information depends on the size of the candidate target time domain unit type set, or the number of candidate target time domain unit types in the candidate target time domain unit type set. The method according to any one of claims 29 to 32, wherein the method further comprises: The network side device receives capability information from the terminal, where the capability information is used to indicate a dynamic adjustment operation of a time domain unit type supported or not supported by the terminal, where the dynamic adjustment operation includes at least one of the following: Indicating or modifying the SBFD time domain unit of the first duplex mode to the SBFD time domain unit of the second duplex mode; Indicating or modifying the SBFD time domain unit of the second duplex mode to the SBFD time domain unit of the first duplex mode; Indicating or reverting the SBFD time domain unit of the first duplex mode to a non-SBFD time domain unit; Indicating or reverting the SBFD time domain unit of the second duplex mode to a non-SBFD time domain unit; indicating the non-SBFD time domain unit as a SBFD time domain unit of the first duplex mode; The non-SBFD time domain unit is indicated as a SBFD time domain unit of the second duplex mode. A dynamic sub-band full-duplex SBFD indication device comprises: a receiving module and an adjustment module; The receiving module is used to receive a first signaling from a network side device, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is terminal-specific scheduling signaling or group common signaling; The adjustment module is used to adjust the type of the target time domain unit according to the first indication information received by the receiving module. A dynamic sub-band full-duplex SBFD indication device comprises: a sending module; The sending module is used to send a first signaling to the terminal, the first signaling includes first indication information, the first indication information is used to indicate the type of actual application of the target time domain unit, the target time domain unit is a time domain unit that can support full-duplex on the terminal side, and the first signaling is terminal-specific scheduling signaling or group common signaling; The first indication information is used to adjust the type of the target time domain unit. A terminal comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the dynamic sub-band full-duplex (SBFD) indication method as described in any one of claims 1 to 28 are implemented. A network side device comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the dynamic sub-band full-duplex (SBFD) indication method as described in any one of claims 29 to 33 are implemented. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the dynamic sub-band full-duplex SBFD indication method as described in any one of claims 1 to 28, or implements the steps of the dynamic SBFD indication method as described in any one of claims 29 to 33.