CN118972950A - Flexible duplex implementation method, device, terminal, network side equipment and medium - Google Patents

Abstract

The application discloses a method, a device, a terminal, network side equipment and a medium for realizing flexible duplex, which belong to the technical field of wireless communication, and the method for realizing flexible duplex in the embodiment of the application comprises the following steps: the terminal or the network side equipment determines a first SSB time domain unit; SBFD-related operations of the first SSB time domain unit are determined.

Description

Flexible duplex implementation method, device, terminal, network side equipment and medium

Technical Field

The present application belongs to the field of wireless communication technology, and specifically relates to a method, device, terminal, network-side equipment and medium for implementing flexible duplex.

Background Art

When deploying traditional cellular networks, frequency division duplex (FDD) or time division duplex (TDD) can be used based on the available spectrum and service characteristics. 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. Both duplex methods have their own advantages and disadvantages.

In order to more flexibly utilize limited spectrum resources, dynamically match business needs, improve resource utilization efficiency, and the uplink coverage, delay and other performance of data transmission, a flexible duplex mode is proposed. A flexible duplex mode (non-overlapping sub-band full duplex, SBFD) is: full duplex on the network side, that is, at the same time, uplink transmission and downlink transmission can be carried out simultaneously at different frequency domain positions. In order to avoid interference between uplink and downlink, a certain guard band (Guard Band) can be reserved between the frequency domain positions (corresponding to the duplex sub-band) corresponding to different transmission directions; half duplex on the terminal side, that is, consistent with TDD, at the same time, only uplink transmission or downlink transmission can be carried out, and both cannot be carried out at the same time. It can be understood that in this duplex mode, the uplink transmission and downlink transmission on the network side at the same time can only be for different terminals.

However, there is currently a lack of discussion on the details of supporting SBFD operations within a synchronization signal and PBCH block (SSB) time domain unit.

Summary of the invention

The embodiments of the present application provide a method, apparatus, terminal, network-side equipment, and medium for implementing flexible duplexing, which can solve the problem of how to support SBFD operations within an SSB time domain unit.

In a first aspect, a method for implementing flexible duplex is provided, which is executed by a terminal, and the method includes:

The terminal determines a first synchronization data block SSB time domain unit;

The terminal determines sub-band full-duplex SBFD related operations of the first SSB time domain unit.

In a second aspect, a method for implementing flexible duplex is provided, which is performed by a network side device, and the method includes:

The network side device determines the first SSB time domain unit;

The network side device determines the SBFD related operations of the first SSB time domain unit.

In a third aspect, a flexible duplex implementation device is provided, including:

A first determining module, configured to determine a first SSB time domain unit;

The second determination module is used to determine the SBFD related operations of the first SSB time domain unit.

In a fourth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

In a fifth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to determine a first synchronization data block SSB time domain unit; and determine sub-band full-duplex SBFD related operations of the first SSB time domain unit.

In a sixth 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 second aspect are implemented.

In the seventh aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to determine a first synchronization data block SSB time domain unit; and determine sub-band full-duplex SBFD related operations of the first SSB time domain unit.

In an eighth 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 a ninth aspect, a wireless communication system is provided, comprising: 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 tenth 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 eleventh 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 method described in the first aspect or the second aspect.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, thereby clarifying the terminal behavior under the SBFD configuration/option, thereby balancing and ensuring the performance of SSB reception/detection and SBFD uplink transmission, and improving the flexibility of system operation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application;

FIG2 is a schematic diagram of a flexible duplex mode;

FIG3 is a schematic flow chart of a method for implementing flexible duplexing performed by a terminal according to an embodiment of the present application;

FIG4 is a flow chart of a method for implementing flexible duplexing performed by a network side device according to an embodiment of the present application;

FIG5 is a schematic diagram of a structure of a device for implementing flexible duplexing according to an embodiment of the present application;

FIG6 is a second structural diagram of a device for implementing flexible duplexing according to an embodiment of the present application;

FIG7 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

FIG8 is a schematic diagram of the hardware structure of a terminal according to an embodiment of the present application;

FIG. 9 is a schematic diagram of the hardware structure of a network-side device according to 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. of the present 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 are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character "/" generally indicates that the objects associated with each other 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.

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, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments 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 a brief description of some technical points involved in this application.

(1) Flexible duplex mode

Please refer to Figure 2, which is a schematic diagram of a flexible duplex mode. In a part of the downlink symbol, the network side semi-statically divides the frequency domain of a single carrier into three duplex sub-bands, where the two sides of the carrier are downlink duplex sub-bands and the center is uplink duplex sub-bands, so as to reduce the interference to the adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception respectively.

(2) Cell Definition SSB (CD-SSB) and Non Cell Definition SSB (NCD-SSB)

When an SSB is associated with a Remaining Minimal System Information (RMSI), the SSB is called a Cell Definition SSB (CD-SSB). The primary serving cell (PCell) is always associated with a CD-SBB located on the synchronization grid.

NCD-SSB is an SSB that is not associated with RMSI.

(3) Semi-static DL/UL/flexible time domain unit

Optionally, when a cell (such as an NR cell) is deployed on an asymmetric spectrum, a TDD mode is generally used. At this time, TDD-UL-DL-ConfigCommon can be configured in the cell common parameters to indicate TDD frame structure information, including TDD frame period, the number of complete downlink/uplink time slots (Slots) contained in a single frame period, and the number of downlink/uplink symbols (Symbol) contained in addition to the complete downlink/uplink Slot. Optionally, the radio resource control (Radio Resource Control, RRC) signaling independent configuration parameter TDD-UL-DL-ConfigDedicated can also be used for each terminal to further modify the uplink and downlink Symbol configuration of one or more Slots in a single frame period on the basis of TDD-UL-DL-ConfigCommon, that is, the initial value of the uplink and downlink Symbol configuration of the Slot is specified by TDD-UL-DL-ConfigCommon, and then further modified by TDD-UL-DL-ConfigDedicated, and this modification is only applied to the terminal receiving this RRC signaling. However, the modification here is limited to further indicating the flexible symbol in the slot as a downlink symbol (DL symbol) or an uplink symbol (UL symbol), and the DL/UL symbol in the slot time slot cannot be modified to other directions. Flexible symbols are symbols with unclear transmission directions, and whether they are used for downlink or uplink transmission can be determined later as needed.

The above-mentioned TDD-UL-DL-ConfigCommon and/or TDD-UL-DL-ConfigDedicated are optional configurations. Since these configuration information can only be semi-statically configured/modified based on RRC signaling, each Symbol in a single TDD frame period determined by these configuration information, combined with the transmission direction configured for it, is referred to as a semi-static (Semi-static) DL/UL/flexible symbol. In addition, the symbol can be further abstracted into a time domain unit, and the time domain unit can correspond to a time slot (Slot), a symbol (Symbol), etc., then a single TDD frame period can contain multiple Semi-static DL/UL/flexible time domain units based on the above-mentioned configuration information. When the above-mentioned TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated are not configured, there is no clear concept of TDD frame period. At this time, each Slot/Symbol in each wireless frame of the NR cell can be understood as a Semi-static flexible slot/symbol, or abstracted as a Semi-staticflexible time domain unit.

The following, in combination with the accompanying drawings, describes in detail the flexible duplex implementation method, apparatus, terminal, network-side equipment and medium provided in the embodiments of the present application through some embodiments and their application scenarios.

Please refer to FIG3 , the present application provides a method for implementing flexible duplex, including:

Step 31: The terminal determines the first SSB time domain unit;

In the embodiment of the present application, the time domain unit may be, for example, a time slot (Slot), a symbol (Symbol), etc.

Step 32: The terminal determines the SBFD related operations of the first SSB time domain unit.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, thereby clarifying the terminal behavior under the SBFD configuration/option, thereby balancing and ensuring the performance of SSB reception/detection and SBFD uplink transmission, and improving the flexibility of system operation.

1. The following first describes how to determine the first SSB time domain unit in the above step 31.

In some embodiments of the present application, optionally, the terminal determining the first SSB time domain unit in the above step 31 includes:

Step 311: The terminal determines at least one first SSB;

Step 312: The terminal determines the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit includes at least one of the following:

The time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, where X is an integer greater than or equal to 1;

The Y time domain units after the last time domain unit occupied by the first SSB, where Y is an integer greater than or equal to 1.

In some embodiments of the present application, optionally, the first SSB includes at least one of the following:

1) SSB configured for the current serving cell;

The current serving cell is a single serving cell corresponding to a carrier deployed with the flexible duplex mode.

2) SSB of a specified type configured for the current serving cell;

3) SSB configured for the current serving cell, wherein the SSB configured for the current cell may include: SSB of a specified type and SSB of other types except the specified type, and the priority of the SSB of the specified type is higher than that of the SSB of other types;

4) The SSB configured for the primary serving cell of the cell group where the current serving cell is located;

5) An SSB of a specified type configured for the primary serving cell of the cell group where the current serving cell is located;

6) an SSB configured for a primary serving cell of a cell group where the current serving cell is located, wherein the SSB configured for the primary serving cell of the cell group where the current serving cell is located may include: an SSB of a specified type and an SSB of other types except the specified type, and the priority of the SSB of the specified type is higher than that of the SSB of other types;

7) SSB configured within the frequency domain of the current downlink bandwidth part (Bandwidth Part, BWP);

The current downlink BWP is the activated downlink BWP (Active DL BWP) on the current serving cell.

8) SSBs of a specified type configured within the frequency domain of the current downlink BWP;

9) SSB configured within the frequency domain of the current downlink BWP, wherein the SSB configured within the frequency domain of the current downlink BWP may include: SSB of a specified type and SSB of other types except the specified type, and the priority of the SSB of the specified type is higher than that of the SSB of other types;

10) SSB effective within the current downlink BWP;

11) SSBs of a specified type that are valid in the current downlink BWP;

12) SSBs effective in the current downlink BWP, the SSBs effective in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the priority of the SSBs of the specified type is higher than that of the SSBs of other types;

13) Designated SSB.

In some embodiments of the present application, optionally, the first SSB can be configured by protocol agreement or high-level signaling.

In some embodiments of the present application, optionally, the first SSB includes at least one of the following:

Cell Definition SSB (CD-SSB);

Non-cell defined SSB (NCD-SSB).

In some embodiments of the present application, optionally, for the transmission position of the first SSB in the time domain, it can be determined by the SSB period corresponding to each first SSB (for example, the corresponding SSB period configured by the parameter ssb-PeriodicityServingCell or ssb-Periodicity-r17; optionally, for NCD-SSB, it further includes a time offset, and the time offset is configured by the parameter ssb-TimeOffset-r17, for example). The SSB index corresponding to the SSB considered at each transmission position can be determined based on any of the following:

The complete set of SSB indexes corresponding to all candidate SSB positions determined based on a predefined pattern (e.g., Case A/B/C/D/E specified by the protocol);

The SSB index is determined based on the specified parameters. For example, for CD-SSB, the SSB index set is determined based on the ssb-PositionsInBurst parameter in SIB1 or ServingCellConfigCommon; for NCD-SSB, the SSB index set corresponding to the corresponding CD-SSB is used.

For the above 1), 2) or 3), the SSB "configured for the current serving cell" includes: the SSB configured for any DL BWP of the current serving cell.

Optionally, when the current serving cell is not configured with any SSB (for example, the current serving cell is an SCell (secondary cell) that is not configured with SSB), the first SSB may be the above 4), 5) or 6). Among them, the main serving cell of the cell group where the current serving cell is located includes at least one of the following: the main serving cell (PCell) of the main cell group, the main serving cell (PSCell) of the secondary cell group.

In some embodiments of the present application, optionally, the specified type includes at least one of the following:

Cell Definition SSB (CD-SSB);

Non-cell defined SSB (NCD-SSB).

Optionally, the specified type may be specified by a protocol or configured by high-level signaling.

In an embodiment of the present application, high-level signaling may include: configuration signaling for radio resource management (Radio Resource Management, RRM), radio link monitoring (RLM), beam measurement (Beam measurement), beam failure detection (Beam failure detection, BFD), and candidate beam detection (Candidate beam detection), and the reference signal configured by the above high-level signaling is SSB.

In some embodiments of the present application, optionally, only a specified type of SSB is used in the above 2), 5), 8) or 11). When a specified type of SSB is not configured, no SSB is used.

In the above 3), 6), 9) or 12), the specified type of SSB is used preferentially. When the specified type of SSB is not configured, other types of SSB are used (if other types of SSB are configured).

In some embodiments of the present application, optionally, the effective SSB includes at least one of the following:

SSB configured within the frequency domain of the current downlink BWP;

An SSB that is outside the frequency domain range of the current downlink BWP but is valid within the current downlink BWP; or an SSB that is not completely contained in the frequency domain range of the current downlink BWP but is valid within the current downlink BWP.

Optionally, the SSB effective in the current downlink BWP may be an SSB effective in the current downlink BWP based on a predefined rule. For example, CD-SSB is a cell-specific signal configured by SIB1 or ServingCellConfigCommon. Regardless of whether the activated BWP contains CD-SSB, CD-SSB is always valid; and for NCD-SSB, NCD-SSB is configured in BWP-DownlinkDedicated. Therefore, NCD-SSB is valid only when the activated BWP is configured with NCD-SSB.

In some embodiments of the present application, optionally, the designated SSB may be specified by a protocol or configured by high-level signaling.

The number of the specified SSBs may be one or more.

In some embodiments of the present application, optionally, the designated SSB is indicated in at least one of the following ways:

Indicates the absolute frequency point of the specified SSB; for example, indicated by the parameter ARFCN-ValueNR.

Indicates an index or identification (ID) of a serving cell corresponding to the designated SSB;

Indicates the index or identifier of the BWP corresponding to the specified SSB;

Indicates the indexes of all SSBs configured on the service cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

In an embodiment of the present invention, optionally, when the designated SSB is a CD-SSB, the designated SSB is the unique CD-SSB corresponding to this service cell by indicating the index or identifier of the service cell corresponding to the designated SSB; when the designated SSB is an NCD-SSB, the index or identifier of the BWP corresponding to the designated SSB can be further indicated, which is the unique NCD-SSB corresponding to this BWP.

In an embodiment of the present invention, optionally, in the case of indicating the index or identification indication of the service cell corresponding to the designated SSB, it can be further indicated that the designated SSB is the index of all SSBs or all CD-SSBs or all NCD-SSBs configured on this service cell.

In some embodiments of the present application, optionally, the designated SSB satisfies at least one of the following:

For the current serving cell configuration;

Configure within the frequency domain of the current downlink BWP;

It takes effect within the current downstream BWP.

That is, any SSB among the specified one or more SSBs is configured for the current service cell (or when no SSB is configured in the current service cell, it is configured for the P(S)Cell of the cell group where the current service cell is located), or is configured within the frequency domain range of the current downlink BWP, or is effective within the current DL BWP.

Optionally, when no SSB is specified, any one of SSB determination methods 1) to 12) may be used to determine the first SSB.

In the embodiment of the present application, after determining the first SSB, any time domain unit occupied by any determined first SSB, the X (X>=1) time domain units before the first time domain unit occupied by the first SSB, and at least one of the Y (Y>=1) time domain units after the last time domain unit occupied by the first SSB can be considered as the first SSB associated time domain unit, referred to as the first SSB time domain unit. Accordingly, within a first SSB time domain unit, there is at least one first SSB, and this/these first SSBs can be referred to as the first SSB associated with this first SSB time domain unit later.

2. The following describes how to determine the SBFD-related operations of the first SSB time domain unit in the above step 32.

SBFD operation mode 1:

In some embodiments of the present application, optionally, the terminal determines the SBFD-related operation of the first SSB time domain unit, including: the terminal determines that the first SSB time domain unit does not support SBFD operation when a first condition is met.

In some embodiments of the present application, optionally, the first condition is one of the following:

1) A first sub-condition, wherein the first sub-condition includes: an uplink subband (UL subband) is allowed to be configured in the first SSB time domain unit, but an uplink subband is not configured in the first SSB time domain unit, or the uplink subband configured in the first SSB time domain unit is not effective or has expired, or the terminal does not perform an SBFD operation in the uplink subband configured in the first SSB time domain unit, or the terminal is not allowed to initiate uplink transmission in the uplink subband configured in the first SSB time domain unit;

When the first condition is the first sub-condition, the first SSB time domain configured with the uplink subband is not an SBFD time domain unit. The terminal believes that the frequency domain resources within the first SSB time domain unit (within the DL BWP) are all used for downlink. Because the configured uplink subband is not actually effective, the frequency domain position of the uplink subband will not have any impact on possible SSB reception. At this time, the uplink subband may not overlap with any first SSB associated with the first SSB time domain unit in the frequency domain, or it may overlap with at least one first SSB.

2) A second sub-condition, the second sub-condition includes: no uplink subband is allowed to be configured within the first SSB time domain unit.

When the first condition is the second sub-condition, it can also be understood that the time domain unit configured with the uplink subband is not allowed to overlap with the first SSB time domain unit. Generally, the time domain unit configured with the uplink subband is a SBFD time domain unit by default.

In some embodiments of the present application, optionally, when the first condition is met, the terminal determines that the first SSB time domain unit does not support SBFD operation includes:

In a case where the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD do not satisfy the second condition, adopting the first sub-condition as the first condition;

In the case where the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD meet the second condition, adopting the second sub-condition as the first condition;

Among them, the second condition includes: the configuration period of SBFD is N times the period of the first SSB, and N is an integer greater than or equal to 1.

In an embodiment of the present application, when a first SSB time domain unit is associated with multiple first SSBs, if the SSB periods corresponding to these multiple first SSBs are consistent, then the above-mentioned "period of the first SSB associated with the first SSB time domain unit" is this consistent SSB period; otherwise, the above-mentioned "period of the first SSB associated with the first SSB time domain unit" can be determined based on the SSB periods corresponding to these multiple first SSBs, for example, the maximum value of the SSB periods corresponding to these multiple first SSBs, or the least common multiple, etc.

Optionally, the configuration period of the above-mentioned single SBFD is aligned with the starting position of a single or N "period of the first SSB associated with the first SSB time domain unit".

SBFD operation mode 2:

In some embodiments of the present application, optionally, the terminal determines the SBFD-related operations of the first SSB time domain unit, including: the terminal determines that the first SSB time domain unit can support SBFD operations.

That is, it can be understood that the terminal is allowed to perform SBFD operations in all or part of the time domain units within the first SSB time domain unit configured with the uplink subband (or initiate uplink transmission in the configured uplink subband).

In some embodiments of the present application, optionally, the terminal determines that the first SSB time domain unit can support SBFD operation, including: the terminal determines a second SSB time domain unit that supports SBFD operation within the first SSB time domain unit.

In some embodiments of the present application, optionally, the second SSB time domain unit includes at least one of the following:

1) SSB time domain unit range 1: all time domain units of the uplink subband are configured in the first SSB time domain unit;

It can be understood that all time domain units configured with the uplink subband in the first SSB time domain unit are SBFD time domain units by default.

The SSB time domain unit range 1 may be based on protocol specifications.

2) SSB time domain unit range 2: a time domain unit in which an uplink subband is configured within the first SSB time domain unit and which satisfies a third condition, wherein the third condition includes at least one of the following:

The configured uplink subband does not overlap with any first SSB associated with the first SSB time domain unit in the frequency domain;

The interval in the frequency domain between the configured uplink subband and any first SSB associated with the first SSB time domain unit is greater than or equal to a preset interval threshold; the preset interval threshold here is used to suppress cross-link interference (Cross Link Interference, CLI) caused by SSB reception and uplink transmission, and its value can be specified by the protocol or configured by high-level signaling.

Any first SSB associated with the first SSB time domain unit does not overlap with a guard band in the frequency domain;

Any first SSB associated with the first SSB time domain unit is located within the frequency domain range of a downlink subband (DL subband).

The SSB time domain unit range 2 may be based on protocol specifications.

3) SSB time domain unit range 3: time domain units that can support SBFD operation within the first SSB time domain unit indicated in the semi-static configuration information of the network side device, the semi-static configuration information is used to indicate the time domain units that can support SBFD operation within the first SSB time domain unit, or the time domain units that do not support SBFD operation;

In an embodiment of the present application, optionally, SSB time domain unit range 3 is indicated by semi-static configuration information of a network side device based on SSB time domain unit range 1 or SSB time domain unit range 2.

Optionally, the semi-static configuration information may be sent via cell-level common signaling (eg, system information block 1 (SIB1) or other system information) or via UE-specific signaling (eg, radio resource control (RRC message)).

Optionally, the semi-static configuration information may be uniformly configured based on granularities such as UE, serving cell or BWP, or may be further configured separately based on a time domain unit granularity.

4) SSB time domain unit range 4: time domain units in the first SSB time domain unit that can support SBFD operation indicated in the dynamic indication information of the network side device, the dynamic indication information is used to indicate the time domain units in the first SSB time domain unit that can support SBFD operation, or the time domain units that do not support SBFD operation;

In an embodiment of the present application, optionally, the SSB time domain unit range 4 is further indicated by the dynamic indication information of the network side device on the basis of at least one of the following SSB time domain unit ranges: SSB time domain unit range 1, SSB time domain unit range 2, SSB time domain unit range 3, SSB time domain unit range 5.

Optionally, the dynamic indication information can be indicated through a media access control control element (MAC CE) or through downlink control information (DCI). When indicated through DCI, the DCI can be either a UE-specific (dedicated) DCI (for example, a UE-specific DCI that schedules or does not schedule data transmission) or a group common (Group common) DCI (for example, an enhanced slot format indication (SFI)).

5) SSB time domain unit range 5: The time domain units supporting SBFD operations within the first SSB time domain unit determined by the terminal based on its own implementation.

The so-called self-realization refers to the determination of the terminal itself.

In an embodiment of the present application, optionally, the SSB time domain unit range 5 is further determined by the terminal implementation based on at least one of the following SSB time domain unit ranges: SSB time domain unit range 1, SSB time domain unit range 2, SSB time domain unit range 3, and SSB time domain unit range 4.

In some embodiments of the present application, optionally, after the terminal implements the time domain unit that supports SBFD operation or the time domain unit that does not support SBFD operation in the first SSB time domain unit, a dynamic indication is made to the network side device. That is, the method also includes: when the terminal determines the time domain unit that supports SBFD operation or the time domain unit that does not support SBFD operation in the first SSB time domain unit based on its own implementation, the terminal sends dynamic indication information to the network side device, and the dynamic indication information is used to notify the determined time domain unit that supports SBFD operation or the time domain unit that does not support SBFD operation in the first SSB time domain unit.

Optionally, the dynamic indication information may be sent via MAC CE or uplink control information (Uplink Control Information, UCI).

It can be understood that when it is determined based on protocol provisions (for example, the above-mentioned SSB time domain unit range 1 or SSB time domain unit range 2), semi-static configuration (for example, SSB time domain unit range 3) or dynamic indication (for example, SSB time domain unit range 4 or SSB time domain unit range 5) that a first SSB time domain unit configured with an uplink subband supports SBFD operation or serves as an SBFD time domain unit, it can be understood that uplink transmission is allowed or prioritized in this first SSB time domain unit (including dynamic scheduling of uplink transmission; optionally, including semi-static configuration of uplink transmission); otherwise, when it is determined that this first SSB time domain unit does not support SBFD operation or does not serve as an SBFD symbol, it can be understood that SSB transmission/reception/measurement is prioritized in this first SSB time domain unit, and no uplink transmission is performed.

The following describes the SBFD operations supported in the second SSB time domain unit determined above (i.e., the time domain unit in which the uplink subband is configured in the first SSB time domain unit and supports the SBFD operation, which may also be referred to as the SBFD time domain unit).

Only half-duplex is supported:

In some embodiments of the present application, optionally, the terminal determining the SBFD-related operation of the first SSB time domain unit includes: when the terminal only supports half-duplex SBFD operation in the second SSB time domain unit, the terminal determines a first SBFD operation supported by the second SSB time domain unit, and the first SBFD operation includes at least one of the following:

Rule 1: Dynamically scheduled physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH) or channel sounding reference signal (SRS) transmission overlapping with the second SSB time domain unit can be performed;

Rule 2: A semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission overlapping with the second SSB time domain unit can be performed;

Rule 3: Drop or postpone the semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission that overlaps with the second SSB time domain unit.

The following content mainly explains Rule 1.

In some embodiments of the present application, optionally, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In the case where dynamic overriding is not applied, the terminal determines that the second SSB time domain unit is always used as the SBFD time domain unit, and expects that the frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH or SRS transmission are all located in the uplink subband configured by the second SSB time domain unit;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is an SBFD time domain unit, and expects that the frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH or SRS transmission are all located in the uplink subband configured by the second SSB time domain unit;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a downlink-only (DL-only) time domain unit, and does not expect the dynamically scheduled PUSCH, PUCCH or SRS transmission in the second SSB time domain unit;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is an uplink-only (UL-only) time domain unit, and performs the dynamic scheduling of PUSCH, PUCCH or SRS transmission.

Generally, the second SSB time domain unit cannot be dynamically covered as a UL-only time domain unit to ensure that from the UE's perspective, there is still SSB transmission in this second SSB time domain unit.

When the second SSB time domain unit can be dynamically covered as a UL-only time domain unit, from the perspective of the UE, there is no SSB transmission in this SSB symbol, or the SSB transmission is canceled. At this time, if the network side device still wants to perform the corresponding SSB transmission to serve other UEs, the network side device can ensure that the frequency domain resources occupied by this dynamically scheduled PUSCH/PUCCH/SRS are all located in the uplink subband, or the frequency domain resources occupied by the dynamically scheduled PUSCH/PUCCH/SRS do not overlap with any first SSB associated with this second SSB time domain unit in the frequency domain (or the interval of any first SSB associated with the second SSB time domain unit in the frequency domain is greater than or not less than the preset interval threshold).

The dynamic coverage here can be understood as: using L1/L2 signaling (such as DCI or MAC CE) to dynamically modify or enable/disable the uplink subband semi-statically configured by high-level signaling in one or more SBFD time domain units, or dynamically converting one or more SBFD time domain units into non-SBFD time domain units (such as DL-only time domain units or UL-only time domain units).

In an embodiment of the present application, optionally, when the second SSB time domain unit is a semi-static downlink (Semi-static DL) time domain unit: when dynamic coverage is not applied, this second SSB time domain unit is always used as an SBFD time domain unit; when dynamic coverage is applied, this second SSB time domain unit is at least one of the following states: SBFD time domain unit; DL-only time domain unit.

In an embodiment of the present application, optionally, when the second SSB time domain unit is a semi-static flexible time domain unit: when dynamic coverage is not applied, this second SSB time domain unit always serves as a SBFD time domain unit; when dynamic coverage is applied, this second SSB time domain unit is at least one of the following states: SBFD time domain unit; DL-only time domain unit; UL-only time domain unit.

It can be understood that when the second SSB time domain unit is a semi-static downlink (Semi-static DL) time domain unit or a semi-static flexible (Semi-static flexible) time domain unit, and this second SSB time domain unit is converted into a DL-only time domain unit based on dynamic coverage, it will not affect the related reception/measurement operations of the first SSB associated with this second SSB time domain unit.

In some embodiments of the present application, optionally, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In the case where the dynamically scheduled PUSCH or PUCCH adopts a repetition transmission mode, the terminal, during the first repetition transmission, uses the first repetition transmission as the dynamically scheduled PUSCH or PUCCH transmission, and performs a transmission overlapping with the second SSB time domain unit and corresponding to the first repetition transmission (i.e., applying the above rule 1);

In the case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, the terminal, in other repeated transmissions except the first repeated transmission, regards the other repeated transmissions as semi-statically configured PUSCH or PUCCH transmissions, and performs transmissions overlapping with the second SSB time domain unit and corresponding to the other repeated transmissions (i.e., applying the above rule 2);

In the case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, the terminal, in other repeated transmissions except the first repeated transmission, regards the other repeated transmissions as semi-statically configured PUSCH or PUCCH transmissions, and discards or delays the transmissions overlapping with the second SSB time domain unit and corresponding to the other repeated transmissions (i.e., applying the above rule 3);

In the case where the dynamic scheduling PUSCH adopts a transmission block in multiple time slots (TB processing overmulti-slot PUSCH, TBoMS) mode, the terminal uses the transmission in the first available time slot as the dynamically scheduled PUSCH transmission, and performs the transmission in the first available time slot overlapping with the second SSB time domain unit (i.e., applying the above rule 1);

In the case where the dynamic scheduling of PUSCH adopts the TBoMS mode, the terminal uses the transmission in other available time slots except the transmission in the first available time slot as the semi-statically configured PUSCH transmission, and performs the transmission in the other available time slots overlapping with the second SSB time domain unit (that is, applying the above rule 2);

In the case where the dynamic scheduling of PUSCH adopts the TBoMS method, the terminal regards the transmission in other available time slots except the transmission in the first available time slot as semi-statically configured PUSCH transmission, and discards or delays the transmission in other available time slots overlapping with the second SSB time domain unit (that is, applying the above rule 3).

The above-mentioned dynamic scheduling of SRS can be understood as aperiodic SRS transmission triggered by DCI format 0_1/1_1/2_3, involving each time domain unit occupied by each SRS resource in each (one or more) triggered SRS resource set (resource set).

The following content mainly explains Rule 2.

For semi-statically configured PUSCH, PUCCH or SRS transmissions:

In some embodiments of the present application, optionally, when the first SBFD operation includes being able to perform semi-statically configured PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

When dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as the SBFD time domain unit, and when the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are all located in the uplink subband configured by the second SSB time domain unit, the terminal performs the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e., applying the above rule 2);

In the case where dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as the SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are not all located in the uplink subband configured by the second SSB time domain unit, the terminal discards or delays the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e., applying the above rule 3);

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is an SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are all located in the uplink subband configured by the second SSB time domain unit, the terminal performs the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e., applying the above rule 2);

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are not all located in the uplink subband configured by the second SSB time domain unit, the terminal discards or delays the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e., applying the above rule 3);

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a time domain unit used only for downlink, and discards or delays the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e., applying the above rule 3);

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a time domain unit used only for uplink, and performs the semi-static configuration of PUSCH, PUCCH or SRS transmission (ie, applying the above rule 2).

Generally, the second SSB time domain unit cannot be dynamically covered as a UL-only time domain unit to ensure that from the perspective of the UE, there is still SSB transmission in the second SSB time domain unit.

Optionally, when the second SSB time domain unit can be dynamically covered as a UL-only time domain unit, from the perspective of the UE, there is no SSB transmission in the second SSB time domain unit, or the SSB transmission is cancelled. At this time, if the network side device still wants to perform the corresponding SSB transmission to serve other UEs, any of the following can be applied:

The network side device may ensure that the frequency domain resources occupied by the semi-statically configured PUSCH/PUCCH/SRS are all located in the uplink subband, or that any first SSB associated with the second SSB time domain unit does not overlap in the frequency domain (or the interval of any first SSB associated with the second SSB time domain unit in the frequency domain is greater than or not less than the preset interval threshold);

When the frequency domain resources occupied by this semi-statically configured PUSCH/PUCCH/SRS are not all located in the uplink subband, or at least one first SSB associated with this second SSB time domain unit overlaps in the frequency domain (or the interval in the frequency domain of at least one first SSB associated with this second SSB time domain unit is less than a preset interval threshold), the UE abandons or delays the corresponding transmission (that is, the UE cannot use the SSB transmission in this second SSB time domain unit to perform corresponding reception/measurement, but needs to consider the collision with the SSB transmission in this second SSB time domain unit when performing uplink transmission).

For semi-statically configured PRACH transmission:

In some embodiments of the present application, optionally, when the first SBFD operation includes being able to perform a semi-statically configured PRACH transmission overlapping with the second SSB time domain unit, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

When dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as the SBFD time domain unit, and in a PRACH occasion validation process, there is a first PRACH occasion overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH occasion are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines the first PRACH occasion as possibly valid;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is an SBFD time domain unit, and in the process of PRACH opportunity check, there is a first PRACH opportunity overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines the first PRACH opportunity as possibly valid;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a time domain unit used only for uplink, and in the process of PRACH opportunity check, there is a first PRACH opportunity overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines the first PRACH opportunity as possibly valid;

When dynamic coverage is applied, the terminal determines that the second SSB time domain unit is a time domain unit used only for downlink. In order to avoid affecting the mapping of PRACH opportunity (RO) to SSB, the corresponding operations when dynamic coverage is not applied are still used during the PRACH opportunity check. However, during the PRACH opportunity check, there is a first PRACH opportunity that overlaps with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit. The terminal determines that the first PRACH opportunity is possibly valid, but does not allow the first PRACH opportunity to be selected to initiate PRACH transmission.

The above-mentioned determination that the first PRACH opportunity is possibly valid means that the above-mentioned conditions may be only part of the conditions for determining that the first PRACH opportunity is valid, and other conditions may need to be met. The first PRACH opportunity is determined to be valid only when all conditions are met.

The following content mainly explains Rule 3.

In some embodiments of the present application, optionally, when the first SBFD operation includes discarding or delaying a semi-statically configured PUSCH, PUCCH, SRS, or PRACH transmission overlapping with the second SSB time domain unit, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In a case where the semi-static configuration PUSCH adopts repetition type A (PUSCH repetition Type A), and there is a repetition transmission overlapping with the second SSB time domain unit, and the configuration starts available slot counting (Available SlotCounting), the terminal delays the repetition transmission;

In a case where the semi-statically configured PUSCH adopts repetitive transmission type A, and there is a repetitive transmission overlapping with the second SSB time domain unit, and the start of the available time slot count is not configured, the terminal discards the repetitive transmission;

In the case where the semi-static configuration PUSCH adopts the TBoMS mode and there is a transmission in any TBoMS that overlaps with the second SSB time domain unit, the terminal delays the transmission, or discards the any TBoMS;

When the semi-statically configured PUSCH is a configuration grant (CG) PUSCH, and repeated transmission type A or TBoMS is not configured, and there is a configuration grant PUSCH transmission overlapping with the second SSB time domain unit, the terminal discards the configuration grant PUSCH transmission;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts repeated transmission type A, and there is repeated transmission overlapping with the second SSB time domain unit, and the configuration starts the available time slot count, the terminal delays the repeated transmission;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts repeated transmission type A, and there is a repeated transmission overlapping with the second SSB time domain unit, and the start of the available time slot count is not configured, the terminal discards the repeated transmission;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts a TBoMS mode, and there is a transmission in any TBoMS that overlaps with the second SSB time domain unit, the terminal delays the transmission, or discards the any TBoMS;

In a case where a semi-statically configured PUCCH transmission overlaps with the second SSB time domain unit, the terminal delaying the semi-statically configured PUCCH transmission;

In a case where the semi-statically configured SRS transmission overlaps with the second SSB time domain unit, the terminal discards the semi-statically configured SRS transmission;

During the PRACH opportunity verification process, when the terminal determines whether any PRACH opportunity is valid, the SSB time domain unit used by the terminal includes the second SSB time domain unit.

For example, when tdd-UL-DL-ConfigurationCommon is provided to the UE, a PRACH opportunity within a PRACH time slot is judged to be potentially valid when any of the following conditions is met:

This PRACH opportunity is entirely located within the uplink subband;

This PRACH opportunity is not located before the second SSB time domain unit in this PRACH slot, and the starting position is at least N _gap time domain units away from the last second SSB time domain unit, where N _gap can be specified by the protocol or configured by high-level signaling.

In an embodiment of the present application, optionally, the SSB time domain unit considered in the PRACH timing check may include, in addition to the second SSB time domain unit supporting SBFD operation, an SSB time domain unit that does not support SBFD operation.

Optionally, the above-mentioned semi-statically configured PUCCH includes a PUCCH for carrying a semi-persistent scheduling (Semi-Persistent Scheduling, SPS) hybrid automatic repeat request acknowledgment (HARQ-ACK), periodic or semi-persistent channel state information (P/SP-CSI), and a scheduling request (Scheduling Request, SR). The SPS HARQ-ACK here can be understood as a HARQ-ACK for the SPS PDSCH.

Optionally, when the semi-statically configured PUCCH transmission overlaps with the second SSB time domain unit, the terminal delaying the semi-statically configured PUCCH transmission includes:

For the PUCCH used to carry SPS HARQ-ACK, P/SP-CSI, and SR, regardless of whether repetition transmission is configured, when a repetition (when repetition transmission is not configured, it can be considered to contain only a single repetition) overlaps with this second SSB time domain unit, it is delayed.

For the PUCCH carrying DG HARQ-ACK, when repetition transmission is configured, for any repetition other than the first repetition, when the repetition overlaps with the second SSBsymbol, it is delayed. In the embodiment of the present application, optionally, the rules (Rule 1, Rule 2 and Rule 3) actually applied by the terminal are specified by the protocol or configured by high-level signaling.

Full-duplex support:

In some embodiments of the present application, optionally, the terminal determines the SBFD-related operation of the first SSB time domain unit includes at least one of the following:

Option 1: when the terminal supports full-duplex SBFD operation in the second SSB time domain unit, the terminal determines that uplink transmission can be performed in the uplink subband configured in the second SSB time domain unit;

Generally, within this second SSB time domain unit, uplink transmission within the uplink subband will not have a serious impact on possible SSB reception (or the impact is within a controllable range). At this time, the UE is allowed to perform uplink transmission within the uplink subband configured for the second SSB time domain unit (at this time, the UE can simultaneously perform SSB reception/measurement, as well as other possible downlink reception, within the second SSB time domain unit).

Option 2: The terminal determines a first SBFD operation supported by the second SSB time domain unit, where the first SBFD operation includes at least one of the following:

capable of performing dynamically scheduled PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit;

capable of performing semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission overlapping with the second SSB time domain unit;

Drop or delay semi-statically configured PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit.

Optionally, for UE supporting full-duplex SBFD operation, in order to ensure SSB reception/measurement performance, it may also only support half-duplex SBFD operation in the second SSB time domain unit. At this time, the UE performs the above-mentioned operations corresponding to only supporting half-duplex SBFD (ie, option 2). For only supporting half-duplex SBFD operation, please refer to the description in the above embodiment, which will not be repeated here.

In the embodiment of the present application, optionally, for a UE supporting full-duplex SBFD, whether option 1 or option 2 is executed depends on the implementation of the terminal. For example, for 4-step/2-step random access, random access-based small packet data transmission (RA-SDT) or authorization configuration-based small packet data transmission (CG-SDT), when the terminal needs to initiate uplink access/transmission (including PRACH, MsgA PUSCH, CG PUSCH, etc.), option 1 is executed; otherwise, option 2 is executed.

Referring to FIG. 4 , the embodiment of the present application further provides a method for implementing flexible duplexing, including:

Step 41: The network side device determines the first SSB time domain unit;

In the embodiment of the present application, the time domain unit may be, for example, a time slot (Slot), a symbol (Symbol), etc.

Step 42: The network side device determines the SBFD related operations of the first SSB time domain unit.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, which can balance and guarantee the performance of SSB reception/detection and SBFD uplink transmission, and improve the flexibility of system operation.

In the embodiment of the present application, the way in which the network side device determines the first SSB time domain unit can refer to the way in which the terminal determines the first SSB time domain unit.

In some embodiments of the present application, optionally, the network side device determines the first SSB time domain unit including:

The network side device determines at least one first SSB;

The network side device determines the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit includes at least one of the following:

The time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, where X is an integer greater than or equal to 1;

The Y time domain units after the last time domain unit occupied by the first SSB, where Y is an integer greater than or equal to 1.

In some embodiments of the present application, optionally, the first SSB includes at least one of the following:

The SSB configured for the current serving cell; the current serving cell is a single serving cell corresponding to a carrier deployed with flexible duplexing.

The SSB of the specified type configured for the current serving cell;

The SSB configured for the current serving cell may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

The SSB configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB of a specified type configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB configured for a primary service cell of a cell group where a current service cell is located, wherein the SSB configured for the primary service cell of the cell group where the current service cell is located may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

The SSB configured within the frequency domain of the current downlink BWP; the current downlink BWP is the activated downlink BWP (Active DL BWP) on the current serving cell.

SSBs of a specified type configured within the frequency domain of the current downlink BWP;

The SSB configured within the frequency domain of the current downlink BWP may include: a specified type of SSB and other types of SSB except the specified type, and the priority of the specified type of SSB is higher than that of the other types of SSB;

The SSB that is effective within the current downlink BWP;

The SSB of the specified type that is valid in the current downlink BWP;

The SSBs effective in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the priority of the SSBs of the specified type is higher than that of the SSBs of other types;

Designated SSB.

In some embodiments of the present application, optionally, the method further includes: the network side device sends first indication information to the terminal, and the first indication information includes the designated SSB.

In some embodiments of the present application, optionally, the network side device indicates the designated SSB in at least one of the following ways:

Indicates the absolute frequency of the specified SSB;

Indicating an index or identifier of a serving cell corresponding to the designated SSB;

Indicates the index or identifier of the BWP corresponding to the specified SSB;

Indicates the indexes of all SSBs configured on the service cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

In an embodiment of the present application, the way in which the network side device determines the SBFD-related operations of the first SSB time domain unit can refer to the way in which the terminal determines the SBFD-related operations of the first SSB time domain unit.

In some embodiments of the present application, optionally, the method further includes: the network side device sends second indication information to the terminal, where the second indication information is used to indicate a time domain unit that can support SBFD operation in the first SSB time domain unit, or a time domain unit that does not support SBFD operation; the second indication information is sent through semi-static configuration information, or through dynamic indication information;

In some embodiments of the present application, optionally, the method further includes: the network side device receives third indication information sent by the terminal, the second indication information is used to indicate the time domain units that support SBFD operations within the first SSB time domain units determined by the terminal based on its own implementation, or, the time domain units that do not support SBFD operations, and the third indication information is sent via dynamic indication information.

The implementation method of flexible duplex provided in the embodiment of the present application can be executed by a flexible duplex implementation device. In the embodiment of the present application, the implementation method of flexible duplex implemented by the flexible duplex implementation device is taken as an example to illustrate the flexible duplex implementation device provided in the embodiment of the present application.

Referring to FIG. 5 , the embodiment of the present application further provides a flexible duplex implementation device 50, including:

A first determining module 51, configured to determine a first SSB time domain unit;

The first determination module 52 is used to determine the SBFD related operation of the first SSB time domain unit.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, thereby clarifying the terminal behavior under the SBFD configuration/option, thereby balancing and ensuring the performance of SSB reception/detection and SBFD uplink transmission, and improving the flexibility of system operation.

In the embodiment of the present application, optionally, the first determination module 51 is used to determine at least one first SSB; determine the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit includes at least one of the following:

The time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, where X is an integer greater than or equal to 1;

The Y time domain units after the last time domain unit occupied by the first SSB, where Y is an integer greater than or equal to 1.

In the embodiment of the present application, optionally, the first SSB includes at least one of the following:

The SSB configured for the current serving cell;

The SSB of the specified type configured for the current serving cell;

The SSB configured for the current serving cell may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

The SSB configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB of a specified type configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB configured for a primary service cell of a cell group where a current service cell is located, wherein the SSB configured for the primary service cell of the cell group where the current service cell is located may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

SSB configured within the frequency domain of the current downlink BWP;

SSBs of a specified type configured within the frequency domain of the current downlink BWP;

The SSB configured within the frequency domain of the current downlink BWP may include: a specified type of SSB and other types of SSB except the specified type, and the priority of the specified type of SSB is higher than that of the other types of SSB;

The SSB that is effective within the current downlink BWP;

The SSB of the specified type that is valid in the current downlink BWP;

The SSBs effective in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the priority of the SSBs of the specified type is higher than that of the SSBs of other types;

Designated SSB.

In the embodiment of the present application, optionally, the specified type includes at least one of the following:

The cell defines SSB;

Non-cell defined SSB.

In the embodiment of the present application, optionally, the effective SSB includes at least one of the following:

SSB configured within the frequency domain of the current downlink BWP;

An SSB that is outside the frequency domain range of the current downlink BWP but is valid within the current downlink BWP; or an SSB that is not completely contained in the frequency domain range of the current downlink BWP but is valid within the current downlink BWP.

In the embodiment of the present application, optionally, the designated SSB is indicated in at least one of the following ways:

Indicates the absolute frequency of the specified SSB;

Indicating an index or identifier of a serving cell corresponding to the designated SSB;

Indicates the index or identifier of the BWP corresponding to the specified SSB;

Indicates the indexes of all SSBs configured on the service cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

In the embodiment of the present application, optionally, the specified SSB satisfies at least one of the following:

For the current serving cell configuration;

Configure within the frequency domain of the current downlink BWP;

It takes effect within the current downstream BWP.

In the embodiment of the present application, optionally, the second determination module 52 is used to determine that the first SSB time domain unit does not support SBFD operation when the first condition is met.

In the embodiment of the present application, optionally, the first condition is one of the following:

a first sub-condition, wherein the first sub-condition includes: an uplink subband is allowed to be configured in the first SSB time domain unit, but the uplink subband is not configured in the first SSB time domain unit, or the uplink subband configured in the first SSB time domain unit is not effective or has expired, or the terminal does not perform an SBFD operation in the uplink subband configured in the first SSB time domain unit, or the terminal is not allowed to initiate uplink transmission in the uplink subband configured in the first SSB time domain unit;

The second sub-condition includes: no uplink subband is allowed to be configured within the first SSB time domain unit.

In the embodiment of the present application, optionally, when the first condition is met, the terminal determines that the first SSB time domain unit does not support SBFD operation includes:

In a case where the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD do not satisfy the second condition, adopting the first sub-condition as the first condition;

In the case where the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD meet the second condition, adopting the second sub-condition as the first condition;

Among them, the second condition includes: the configuration period of SBFD is N times the period of the first SSB, and N is an integer greater than or equal to 1.

In the embodiment of the present application, optionally, the second determination module 52 is used to determine whether the first SSB time domain unit can support SBFD operation.

In the embodiment of the present application, optionally, determining that the first SSB time domain unit can support SBFD operation includes: determining a second SSB time domain unit that supports SBFD operation within the first SSB time domain unit.

In this embodiment of the present application, optionally, the second SSB time domain unit includes at least one of the following:

All time domain units of the uplink subband are configured in the first SSB time domain unit;

The first SSB time domain unit is configured with an uplink subband and a time domain unit that satisfies a third condition, wherein the third condition includes at least one of the following: the configured uplink subband and any first SSB associated with the first SSB time domain unit do not overlap in the frequency domain; the interval in the frequency domain between the configured uplink subband and any first SSB associated with the first SSB time domain unit is greater than or equal to a preset interval threshold; any first SSB associated with the first SSB time domain unit does not overlap with the guard band in the frequency domain; any first SSB associated with the first SSB time domain unit is located within the frequency domain range of the downlink subband;

a time domain unit capable of supporting SBFD operation within the first SSB time domain unit indicated in the semi-static configuration information of the network side device, wherein the semi-static configuration information is used to indicate the time domain unit capable of supporting SBFD operation within the first SSB time domain unit, or the time domain unit not supporting SBFD operation;

a time domain unit capable of supporting SBFD operation in the first SSB time domain unit indicated in the dynamic indication information of the network side device, wherein the dynamic indication information is used to indicate the time domain unit capable of supporting SBFD operation or the time domain unit not supporting SBFD operation in the first SSB time domain unit;

The terminal determines the time domain unit supporting SBFD operation within the first SSB time domain unit based on its own implementation.

In an embodiment of the present application, optionally, the flexible duplex implementation device 50 also includes: a sending module, which is used to send dynamic indication information to a network side device when the terminal determines the time domain unit that supports SBFD operation or the time domain unit that does not support SBFD operation within the first SSB time domain unit based on its own implementation, and the dynamic indication information is used to notify the determined time domain unit that supports SBFD operation or the time domain unit that does not support SBFD operation within the first SSB time domain unit.

In the embodiment of the present application, optionally, the determining of the SBFD-related operation of the first SSB time domain unit includes:

In a case where the terminal supports only a half-duplex SBFD operation in the second SSB time domain unit, determining a first SBFD operation supported by the second SSB time domain unit, where the first SBFD operation includes at least one of the following:

capable of performing dynamically scheduled PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit;

capable of performing semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission overlapping with the second SSB time domain unit;

Drop or delay semi-statically configured PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit.

In the embodiment of the present application, optionally, the determining of the SBFD-related operation of the first SSB time domain unit includes:

In a case where the terminal supports full-duplex SBFD operation in the second SSB time domain unit, it is determined that uplink transmission can be performed in an uplink subband configured by the second SSB time domain unit, or the terminal determines a first SBFD operation supported by the second SSB time domain unit, where the first SBFD operation includes at least one of the following:

capable of performing dynamically scheduled PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit;

capable of performing semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission overlapping with the second SSB time domain unit;

Drop or delay semi-statically configured PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit.

In the embodiment of the present application, optionally, the determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In the case where dynamic coverage is not applied, determining that the second SSB time domain unit is always used as an SBFD time domain unit, and expecting that the frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH or SRS transmission are all located in the uplink subband configured by the second SSB time domain unit;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is a SBFD time domain unit, and expecting that the frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH or SRS transmission are all located in the uplink subband configured by the second SSB time domain unit;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is a time domain unit used only for downlink, and not expecting the dynamically scheduled PUSCH, PUCCH or SRS transmission in the second SSB time domain unit;

In the case of applying dynamic coverage, the second SSB time domain unit is determined to be a time domain unit used only for uplink, and the dynamic scheduling of PUSCH, PUCCH or SRS transmission is performed.

In the embodiment of the present application, optionally, the determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In the case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, during the first repeated transmission, the first repeated transmission is used as the dynamically scheduled PUSCH or PUCCH transmission, and a transmission overlapping with the second SSB time domain unit and corresponding to the first repeated transmission is performed;

In the case where the dynamic scheduling of PUSCH or PUCCH adopts a repeated transmission mode, in other repeated transmissions except the first repeated transmission, the other repeated transmissions are used as semi-statically configured PUSCH or PUCCH transmissions, and transmissions overlapping with the second SSB time domain unit and corresponding to the other repeated transmissions are performed;

In the case where the dynamic scheduling of PUSCH or PUCCH adopts a repeated transmission mode, in other repeated transmissions except the first repeated transmission, the other repeated transmissions are used as semi-statically configured PUSCH or PUCCH transmissions, and the transmissions overlapping with the second SSB time domain unit and corresponding to the other repeated transmissions are discarded or delayed;

In the case where the dynamically scheduled PUSCH adopts a TBoMS mode of sending one transmission block in multiple time slots, the transmission in the first available time slot is used as the dynamically scheduled PUSCH transmission, and the transmission in the first available time slot overlapping with the second SSB time domain unit is performed;

In the case where the dynamic scheduling of PUSCH adopts the TBoMS mode, the transmission in other available time slots except the transmission in the first available time slot is used as the semi-statically configured PUSCH transmission, and the transmission in the other available time slots overlapping with the second SSB time domain unit is performed;

In the case where the dynamic scheduling of PUSCH adopts the TBoMS method, the transmission in other available time slots except the transmission in the first available time slot is used as semi-statically configured PUSCH transmission, and the transmission in the other available time slots overlapping with the second SSB time domain unit is discarded or delayed.

In an embodiment of the present application, optionally, the first SBFD operation includes being able to perform a semi-statically configured PUSCH, PUCCH, or SRS transmission overlapping with the second SSB time domain unit; the first SBFD operation supported by the second SSB time domain unit is determined to include at least one of the following:

In the case where dynamic coverage is not applied, determining that the second SSB time domain unit is always used as an SBFD time domain unit, and in the case where the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are all located in the uplink subband configured by the second SSB time domain unit, the terminal performs the semi-statically configured PUSCH, PUCCH or SRS transmission;

In the case where dynamic coverage is not applied, determining that the second SSB time domain unit is always used as an SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are not all located in the uplink subband configured by the second SSB time domain unit, the terminal discards or delays the semi-statically configured PUSCH, PUCCH or SRS transmission;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is an SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are all located in the uplink subband configured by the second SSB time domain unit, the terminal performs the semi-statically configured PUSCH, PUCCH or SRS transmission;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is an SBFD time domain unit, and in the case that the frequency domain resources occupied by the semi-statically configured PUSCH, PUCCH or SRS are not all located in the uplink subband configured by the second SSB time domain unit, the terminal discards or delays the semi-statically configured PUSCH, PUCCH or SRS transmission;

In the case of applying dynamic coverage, determining the second SSB time domain unit as a time domain unit used only for downlink, and discarding or delaying the semi-statically configured PUSCH, PUCCH or SRS transmission;

In the case of applying dynamic coverage, the second SSB time domain unit is determined to be a time domain unit used only for uplink, and the semi-static configuration of PUSCH, PUCCH or SRS transmission is performed.

In the embodiment of the present application, optionally, the first SBFD operation includes being able to perform a semi-statically configured PRACH transmission overlapping with the second SSB time domain unit; the determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

In the case where dynamic coverage is not applied, it is determined that the second SSB time domain unit is always used as the SBFD time domain unit, and in the process of PRACH opportunity check, there is a first PRACH opportunity overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines that the first PRACH opportunity is possibly valid;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is an SBFD time domain unit, and in the process of PRACH opportunity check, when there is a first PRACH opportunity overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines that the first PRACH opportunity is possibly valid;

In the case of applying dynamic coverage, determining that the second SSB time domain unit is a time domain unit used only for uplink, and in the process of PRACH opportunity check, when there is a first PRACH opportunity overlapping with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit, the terminal determines that the first PRACH opportunity is possibly valid;

In the case of applying dynamic coverage, it is determined that the second SSB time domain unit is a time domain unit used only for downlink. During the PRACH opportunity check, there is a first PRACH opportunity that overlaps with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH opportunity are all located in the uplink subband configured by the second SSB time domain unit. The terminal determines that the first PRACH opportunity is possibly valid, but does not allow the first PRACH opportunity to be selected to initiate PRACH transmission.

In an embodiment of the present application, optionally, the first SBFD operation includes discarding or delaying a semi-statically configured PUSCH, PUCCH, SRS or PRACH transmission overlapping with the second SSB time domain unit; the first SBFD operation supported by the second SSB time domain unit is determined to include at least one of the following:

In the case where the semi-static configuration PUSCH adopts repetitive transmission type A, and there is a repetitive transmission overlapping with the second SSB time domain unit, and the configuration starts the available time slot count, delaying the repetitive transmission;

In a case where the semi-statically configured PUSCH adopts repetitive transmission type A, and there is a repetitive transmission overlapping with the second SSB time domain unit, and the start of the available time slot count is not configured, discarding the repetitive transmission;

When the semi-static configuration PUSCH adopts the TBoMS mode and there is a transmission in any TBoMS that overlaps with the second SSB time domain unit, delay the transmission, or discard the any TBoMS;

When the semi-statically configured PUSCH is a configured authorized PUSCH, and repeated transmission type A or TBoMS is not configured, and there is a configured authorized PUSCH transmission that overlaps with the second SSB time domain unit, discard the configured authorized PUSCH transmission;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts repeated transmission type A, and there is repeated transmission overlapping with the second SSB time domain unit, and the configuration starts the available time slot count, delaying the repeated transmission;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts repeated transmission type A, and there is a repeated transmission overlapping with the second SSB time domain unit, and the start of the available time slot count is not configured, the repeated transmission is discarded;

When the semi-statically configured PUSCH is a configured authorized PUSCH, the configured authorized PUSCH adopts a TBoMS mode, and there is a transmission in any TBoMS that overlaps with the second SSB time domain unit, delaying the transmission, or discarding the any TBoMS;

In a case where a semi-statically configured PUCCH transmission overlaps with the second SSB time domain unit, the terminal delaying the semi-statically configured PUCCH transmission;

In the case where the semi-statically configured SRS transmission overlaps with the second SSB time domain unit, discarding the semi-statically configured SRS transmission;

During the PRACH opportunity verification process, when determining whether any PRACH opportunity is valid, the SSB time domain unit used includes the second SSB time domain unit.

The implementation device of flexible duplex in the embodiment of the present application can 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 electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

The flexible duplex implementation device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

Referring to FIG. 6 , the embodiment of the present application further provides a flexible duplex implementation device 60, including:

A first determining module 61, configured to determine a first SSB time domain unit;

The second determination module is used to determine the SBFD related operations of the first SSB time domain unit.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, thereby balancing and ensuring the performance of SSB reception/detection and SBFD uplink transmission, and improving the flexibility of system operation.

In the embodiment of the present application, optionally, the first determination module 61 is used to determine at least one first SSB; determine the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit includes at least one of the following:

The time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, where X is an integer greater than or equal to 1;

The Y time domain units after the last time domain unit occupied by the first SSB, where Y is an integer greater than or equal to 1.

In the embodiment of the present application, optionally, the first SSB includes at least one of the following:

The SSB configured for the current serving cell;

The SSB of the specified type configured for the current serving cell;

The SSB configured for the current serving cell may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

The SSB configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB of a specified type configured for the primary serving cell of the cell group where the current serving cell is located;

An SSB configured for a primary service cell of a cell group where a current service cell is located, wherein the SSB configured for the primary service cell of the cell group where the current service cell is located may include: an SSB of a specified type and an SSB of other types except the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

SSB configured within the frequency domain of the current downlink BWP;

SSBs of a specified type configured within the frequency domain of the current downlink BWP;

The SSB configured within the frequency domain of the current downlink BWP may include: a specified type of SSB and other types of SSB except the specified type, and the priority of the specified type of SSB is higher than that of the other types of SSB;

The SSB that is effective within the current downlink BWP;

The SSB of the specified type that is valid in the current downlink BWP;

The SSBs effective in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the priority of the SSBs of the specified type is higher than that of the SSBs of other types;

Designated SSB.

In the embodiment of the present application, optionally, the flexible duplex implementation device 60 also includes: a first sending module, used to send first indication information to the terminal, and the first indication information includes the designated SSB.

In the embodiment of the present application, optionally, the first sending module indicates the designated SSB in at least one of the following ways:

Indicates the absolute frequency of the specified SSB;

Indicating an index or identifier of a serving cell corresponding to the designated SSB;

Indicates the index or identifier of the BWP corresponding to the specified SSB;

Indicates the indexes of all SSBs configured on the service cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

In the embodiment of the present application, optionally, the flexible duplex implementation device 60 further includes: a second sending module, configured to send second indication information to the terminal, wherein the second indication information is used to indicate a time domain unit that can support SBFD operation in the first SSB time domain unit, or a time domain unit that does not support SBFD operation; the second indication information is sent through semi-static configuration information, or through dynamic indication information;

or,

A receiving module is used to receive third indication information sent by a terminal, wherein the second indication information is used to indicate the time domain units that support SBFD operations within the first SSB time domain units determined by the terminal based on its own implementation, or the time domain units that do not support SBFD operations, and the third indication information is sent via dynamic indication information.

The flexible duplexing implementation device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or a chip.

The flexible duplex implementation device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 4 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 70, including a processor 71 and a memory 72, the memory 72 storing programs or instructions that can be run on the processor 71, for example, when the communication device 70 is a terminal, the program or instruction is executed by the processor 71 to implement the various steps of the flexible duplex implementation method embodiment executed by the terminal side, and can achieve the same technical effect. When the communication device 70 is a network side device, the program or instruction is executed by the processor 71 to implement the various steps of the flexible duplex implementation method embodiment executed by the network side device side, and can achieve the same technical effect, to avoid repetition, it will not be 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 method embodiment shown in Figure 3. 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 80 includes but is not limited to: a radio frequency unit 81, a network module 82, an audio output unit 83, an input unit 84, a sensor 85, a display unit 86, a user input unit 87, an interface unit 88, a memory 89 and at least some of the components of the processor 810.

Those skilled in the art will appreciate that the terminal 80 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 x 10 through a power management system, so that the power management system can realize functions such as managing charging, discharging, and power consumption management. 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 in the figure, 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 84 may include a graphics processing unit (GPU) 841 and a microphone 842, and the graphics processor 841 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 86 may include a display panel 861, and the display panel 861 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 87 includes a touch panel 871 and at least one of other input devices 872. The touch panel 871 is also called a touch screen. The touch panel 871 may include two parts: a touch detection device and a touch controller. Other input devices 872 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, 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 81 can transmit it to the processor 810 for processing; in addition, the RF unit 81 can send uplink data to the network side device. Generally, the RF unit 81 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

The memory 89 can be used to store software programs or instructions and various data. The memory 89 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 89 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 89 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

The processor 810 may include one or more processing units; optionally, the processor 810 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 810.

Among them, the processor 810 is used for the terminal to determine the first SSB time domain unit; determine the SBFD related operations of the first SSB time domain unit.

In an embodiment of the present application, corresponding solutions are introduced for each link of performing SBFD-related operations within the SSB time slot unit, thereby clarifying the terminal behavior under the SBFD configuration/option, thereby balancing and ensuring the performance of SSB reception/detection and SBFD uplink transmission, and improving the flexibility of system operation.

It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment executed on the above-mentioned terminal side, and achieve the same or corresponding technical effect. 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 method embodiment shown in Figure 4. The network side device embodiment corresponds to the above-mentioned network side device 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 90 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94 and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92. The radio frequency device 92 processes the received information and sends it out through the antenna 91.

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

The baseband device 93 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 95 through a bus interface to call a program in the memory 95 and execute the network device operations shown in the above method embodiment.

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

Specifically, the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by the modules shown in Figure 6 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 flexible duplex implementation 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 flexible duplex implementation 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 flexible duplex implementation method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the flexible duplex implementation method executed by the terminal side as described above, and the network side device can be used to execute the steps of the flexible duplex implementation method executed by the network side device side as 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 (30)

1. A method for implementing flexible duplexing, comprising:

the terminal determines a first synchronous data block SSB time domain unit;

The terminal determines a sub-band full duplex SBFD related operation of the first SSB time domain unit.

2. The method of claim 1, wherein the determining, by the terminal, the first SSB time domain unit comprises:

the terminal determines at least one first SSB;

The terminal determines the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit comprises at least one of the following:

a time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, wherein X is an integer greater than or equal to 1;

and Y time domain units after the last time domain unit occupied by the first SSB, wherein Y is an integer greater than or equal to 1.

3. The method of claim 2, wherein the first SSB comprises at least one of:

SSB configured for the current serving cell;

SSBs configured for the current serving cell and of a specified type;

SSB configured for the current serving cell, the SSB configured for the current cell can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSB configured for a main serving cell of a cell group where a current serving cell is located;

SSB configured for a main serving cell of a cell group where a current serving cell is located and of a specified type;

The SSB configured for the primary serving cell of the cell group where the current serving cell is located can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSB configured in a frequency domain range of the current downlink bandwidth part BWP;

SSB configured in a frequency domain range of a current downlink BWP and of a specified type;

SSBs configured in the frequency domain of the current downstream BWP, the SSB configured in the frequency domain of the current downlink BWP can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSBs that take effect within the current downstream BWP;

SSBs that are valid within the current downstream BWP and of a specified type;

SSBs that are effective within the current downstream BWP, the SSBs that are effective within the current downstream BWP can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

A specified SSB.

4. A method according to claim 3, wherein the specified type comprises at least one of:

Cell definition SSB;

the non-cell defines SSB.

5. A method according to claim 3, wherein the validated SSB comprises at least one of:

SSB configured in a frequency domain range of a current downlink BWP;

SSBs that are outside the frequency domain of the current downstream BWP but are valid within the current downstream BWP; or is not completely contained in the frequency domain of the current downlink BWP but is an SSB valid in the current downlink BWP.

6. A method according to claim 3, wherein the specified SSB is indicated by at least one of:

indicating an absolute frequency point of the specified SSB;

an index or an identification of a serving cell corresponding to the designated SSB is indicated;

An index or identity indicating the BWP corresponding to the specified SSB;

And indicating indexes of all SSBs configured on the service cell corresponding to the specified SSB or indexes of all SSBs of the specified type.

7. The method of claim 3 or 6, wherein the specified SSB satisfies at least one of:

configuring for a current serving cell;

Configuration is carried out in the frequency domain range of the current downlink BWP;

takes effect in the current downstream BWP.

8. The method according to claim 1 or 2, wherein the determining SBFD related operations of the first SSB time domain unit by the terminal comprises:

the terminal determines that the first SSB time domain unit does not support SBFD operations if a first condition is satisfied.

9. The method of claim 8, wherein the first condition is one of:

A first sub-condition, the first sub-condition comprising: allowing configuration of an uplink sub-band in the first SSB time domain unit, but not configuring an uplink sub-band in the first SSB time domain unit, or not validating or failing the uplink sub-band configured in the first SSB time domain unit, or not performing SBFD operations in the uplink sub-band configured in the first SSB time domain unit by the terminal, or not allowing uplink transmission to be initiated in the uplink sub-band configured in the first SSB time domain unit by the terminal;

A second sub-condition, the second sub-condition comprising: and the uplink sub-band is not allowed to be configured in the first SSB time domain unit.

10. The method of claim 9, wherein the determining, by the terminal, that the first SSB time domain unit does not support SBFD operations if a first condition is met comprises:

in a case that a period of a first SSB associated with the first SSB time domain unit and a configuration period of SBFD do not satisfy a second condition, adopting the first sub-condition as the first condition;

in a case that a period of a first SSB associated with the first SSB time domain unit and a configuration period of SBFD satisfy a second condition, adopting the second sub-condition as the first condition;

Wherein the second condition includes: SBFD is a configuration period that is N times the period of the first SSB, N being an integer greater than or equal to 1.

11. The method according to claim 1 or 2, wherein the determining SBFD related operations of the first SSB time domain unit by the terminal comprises:

The terminal determines SBFD operations can be supported within the first SSB time domain unit.

12. The method of claim 11, wherein the determining by the terminal that SBFD operations can be supported in the first SSB time domain unit comprises:

the terminal determines a second SSB time domain unit supporting SBFD operations within the first SSB time domain unit.

13. The method of claim 12, wherein the second SSB time domain unit comprises at least one of:

all time domain units of an uplink sub-band are configured in the first SSB time domain unit;

The first SSB time domain unit is configured with a time domain unit of an uplink sub-band and meets a third condition, where the third condition includes at least one of the following: the configured uplink sub-band is not overlapped with any first SSB associated with the first SSB time domain unit in the frequency domain; the interval of any first SSB in the frequency domain, which is associated with the first SSB time domain unit, of the configured uplink sub-band is larger than or equal to a preset interval threshold; any first SSB and guard band associated with the first SSB time domain unit do not overlap in the frequency domain; any first SSB associated with the first SSB time domain unit is located within a frequency domain range of a downlink subband;

a time domain unit capable of supporting SBFD operations in the first SSB time domain unit indicated in the semi-static configuration information of the network side device, where the semi-static configuration information is used to indicate a time domain unit capable of supporting SBFD operations or a time domain unit not supporting SBFD operations in the first SSB time domain unit;

A time domain unit capable of supporting SBFD operations in the first SSB time domain unit indicated in dynamic indication information of the network side device, where the dynamic indication information is used to indicate a time domain unit capable of supporting SBFD operations or a time domain unit not supporting SBFD operations in the first SSB time domain unit;

The terminal implements a time domain unit supporting SBFD operations in the determined first SSB time domain unit based on itself.

14. The method as recited in claim 13, further comprising:

In the case that the terminal determines, based on its implementation, a time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations, the terminal sends dynamic indication information to the network side device, where the dynamic indication information is used to notify the determined time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations.

15. The method of claim 12, wherein the determining SBFD related operations of the first SSB time domain unit by the terminal comprises:

In the event that the terminal supports only half duplex SBFD operations within the second SSB time domain unit, the terminal determines a first SBFD operation supported by the second SSB time domain unit, the first SBFD operation comprising at least one of:

A dynamically scheduled physical uplink shared channel PUSCH, physical uplink control channel PUCCH, or reference signal SRS transmission for channel sounding overlapping the second SSB time domain unit can be performed;

a semi-static configuration PUSCH, PUCCH, SRS or PRACH transmission that overlaps with the second SSB time domain unit can be performed;

Semi-static configuration PUSCH, PUCCH, SRS or PRACH transmissions overlapping the second SSB time domain unit are discarded or delayed.

16. The method of claim 12, wherein the determining SBFD related operations of the first SSB time domain unit by the terminal comprises:

In the case that the terminal supports full duplex SBFD operation within the second SSB time domain unit, the terminal determines that uplink transmission can be performed in an uplink sub-band configured by the second SSB time domain unit, or the terminal determines a first SBFD operation supported by the second SSB time domain unit, the first SBFD operation including at least one of:

Dynamically scheduled PUSCH, PUCCH, or SRS transmissions overlapping the second SSB time domain unit can be performed;

a semi-static configuration PUSCH, PUCCH, SRS or PRACH transmission that overlaps with the second SSB time domain unit can be performed;

Semi-static configuration PUSCH, PUCCH, SRS or PRACH transmissions overlapping the second SSB time domain unit are discarded or delayed.

17. The method according to claim 15 or 16, wherein the terminal determining the first SBFD operations supported by the second SSB time domain unit comprises at least one of:

Under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be taken as SBFD time domain unit all the time, and expects that frequency domain resources occupied by the dynamic scheduling PUSCH, PUCCH or SRS transmission are all located in an uplink sub-band configured by the second SSB time domain unit;

in the case of dynamic coverage, the terminal determines that the second SSB time domain unit is SBFD time domain units, and expects that frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH, or SRS transmission are all located in an uplink subband configured by the second SSB time domain unit;

in the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a downlink-only time domain unit, and the dynamic scheduling PUSCH, PUCCH, or SRS transmission is not expected to exist in the second SSB time domain unit;

in case of applying dynamic coverage, the terminal determines the second SSB time domain unit as an uplink-only time domain unit and performs the dynamic scheduling PUSCH, PUCCH, or SRS transmission.

18. The method according to claim 15 or 16, wherein the terminal determining the first SBFD operations supported by the second SSB time domain unit comprises at least one of:

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission manner, the terminal uses the first repeated transmission as dynamically scheduled PUSCH or PUCCH transmission when performing first repeated transmission, and performs transmission overlapping with the second SSB time domain unit and corresponding to the first repeated transmission;

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission manner, the terminal uses the other repeated transmission as a semi-statically configured PUSCH or PUCCH transmission when the terminal performs other repeated transmission except the first repeated transmission, and performs transmission overlapping with the second SSB time domain unit and corresponding to the other repeated transmission;

When the dynamic scheduling PUSCH or PUCCH adopts a repeated transmission manner, the terminal uses the other repeated transmission as a PUSCH or PUCCH transmission configured in a semi-static manner when the terminal performs other repeated transmission except the first repeated transmission, and discards or delays transmission overlapping the second SSB time domain unit and corresponding to the other repeated transmission;

In the case that the dynamically scheduled PUSCH uses a transmission block to transmit TBoMS in a plurality of time slots, the terminal uses the transmission in a first available time slot as the dynamically scheduled PUSCH transmission, and performs the transmission in the first available time slot overlapping with the second SSB time domain unit;

in the case that the dynamic scheduling PUSCH adopts TBoMS mode, the terminal uses the transmission in other available time slots except the transmission in the first available time slot as the PUSCH transmission of semi-static configuration, and performs the transmission in the other available time slots overlapped with the second SSB time domain unit;

In the case that the dynamically scheduled PUSCH adopts TBoMS mode, the terminal uses the transmission in other available time slots except the transmission in the first available time slot as the semi-statically configured PUSCH transmission, and discards or delays the transmission in the other available time slots overlapped with the second SSB time domain unit.

19. The method according to claim 15 or 16, wherein,

The first SBFD operations include enabling semi-statically configured PUSCH, PUCCH, or SRS transmissions overlapping with the second SSB time domain unit;

The terminal determining that the first SBFD operations supported by the second SSB time domain unit include at least one of:

Under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be taken as SBFD time domain unit all the time, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are all located in an uplink sub-band configured by the second SSB time domain unit, the terminal executes the semi-static configuration PUSCH, PUCCH or SRS transmission;

Under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be taken as SBFD time domain unit all the time, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are not all located in an uplink sub-band configured by the second SSB time domain unit, the terminal discards or delays the semi-static configuration PUSCH, PUCCH or SRS transmission;

Under the condition of dynamic coverage application, the terminal determines that the second SSB time domain unit is SBFD time domain units, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are all located in an uplink sub-band configured by the second SSB time domain unit, the terminal executes the semi-static configuration PUSCH, PUCCH or SRS transmission;

Under the condition of dynamic coverage application, the terminal determines that the second SSB time domain unit is SBFD time domain units, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are not all located in an uplink sub-band configured by the second SSB time domain unit, the terminal discards or delays transmission of the semi-static configuration PUSCH, PUCCH or SRS;

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a downlink-only time domain unit, and discards or delays the semi-statically configured PUSCH, PUCCH, or SRS transmission;

In case of applying dynamic coverage, the terminal determines the second SSB time domain unit as a time domain unit for uplink only and performs the semi-statically configured PUSCH, PUCCH or SRS transmission.

20. The method according to claim 15 or 16, wherein,

The first SBFD operations include enabling semi-static configuration PRACH transmissions overlapping the second SSB time domain unit to be performed;

The terminal determining that the first SBFD operations supported by the second SSB time domain unit include at least one of:

under the condition that dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as SBFD time domain unit, and under the condition that a first PRACH opportunity overlapped with the second SSB time domain unit exists in the PRACH opportunity checking process and frequency domain resources occupied by the first PRACH opportunity are all located in an uplink sub-band configured by the second SSB time domain unit, the terminal judges the first PRACH opportunity as possible valid;

Under the condition of dynamic coverage, the terminal determines that the second SSB time domain unit is SBFD time domain units, and determines that the first PRACH time is possible to be effective under the condition that a first PRACH time overlapped with the second SSB time domain unit exists in the PRACH time verification process and frequency domain resources occupied by the first PRACH time are all located in an uplink sub-band configured by the second SSB time domain unit;

Under the condition of dynamic coverage application, the terminal determines that the second SSB time domain unit is a time domain unit only used for uplink, and judges the first PRACH time to be possible to be effective under the condition that a first PRACH time overlapped with the second SSB time domain unit exists in the PRACH time verification process and frequency domain resources occupied by the first PRACH time are located in an uplink sub-band configured by the second SSB time domain unit;

Under the condition that dynamic coverage is applied, the terminal determines that the second SSB time domain unit is a time domain unit only used for downlink, and under the condition that a first PRACH opportunity overlapped with the second SSB time domain unit exists in the PRACH opportunity checking process and frequency domain resources occupied by the first PRACH opportunity are located in an uplink sub-band configured by the second SSB time domain unit, the terminal judges the first PRACH opportunity as possible to be effective but does not allow the first PRACH opportunity to be selected to initiate PRACH transmission.

21. The method according to claim 15 or 16, wherein,

The first SBFD operation includes dropping or delaying semi-static configuration PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit;

the terminal determining that the first SBFD operations supported by the second SSB time domain unit include at least one of:

In the case that the semi-static configuration PUSCH adopts a retransmission type a, and there is a retransmission overlapping with the second SSB time domain unit, and the configuration starts an available time slot count, the terminal delays the retransmission;

In the case that the semi-static configuration PUSCH adopts a retransmission type a, and there is a retransmission overlapping with the second SSB time domain unit, and the available time slot count is not configured to be started, the terminal discards the retransmission;

In the case that the semi-static configuration PUSCH adopts TBoMS mode and there is transmission overlapping with the second SSB time domain unit in any TBoMS, the terminal delays the transmission or discards any TBoMS;

In the case that the semi-static configuration PUSCH is a configuration grant PUSCH, and the configuration grant PUSCH is not configured in a repeated transmission type a or TBoMS mode, and there is a configuration grant PUSCH transmission overlapping with the second SSB time domain unit, the terminal discards the configuration grant PUSCH transmission;

When the semi-static configuration PUSCH is a configuration grant PUSCH, the configuration grant PUSCH adopts a repeated transmission type a, and when there is repeated transmission overlapped with the second SSB time domain unit, and the configuration starts an available time slot count, the terminal delays the repeated transmission;

When the semi-static configuration PUSCH is a configuration grant PUSCH, the configuration grant PUSCH adopts a repeated transmission type a, and when repeated transmission overlapped with the second SSB time domain unit exists, and an available time slot count is not configured to be started, the terminal discards the repeated transmission;

when the semi-static configuration PUSCH is a configuration grant PUSCH, the configuration grant PUSCH adopts TBoMS mode, and when transmission overlapped with the second SSB time domain unit exists in any TBoMS, the terminal delays the transmission, or discards any TBoMS;

In the case that a semi-static configuration PUCCH transmission overlaps the second SSB time domain unit, the terminal delays the semi-static configuration PUCCH transmission;

in the case that a semi-statically configured SRS transmission overlaps the second SSB time domain unit, the terminal discards the semi-statically configured SRS transmission;

In the PRACH opportunity checking process, when the terminal determines whether any PRACH opportunity is valid, the used SSB time domain unit comprises the second SSB time domain unit.

22. A method for implementing flexible duplexing, comprising:

the network side equipment determines a first SSB time domain unit;

the network side device determines SBFD related operations of the first SSB time domain unit.

23. The method of claim 22, wherein the network-side device determining the first SSB time domain unit comprises:

The network side equipment determines at least one first SSB;

the network side equipment determines the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit comprises at least one of the following:

a time domain unit occupied by the first SSB;

X time domain units before the first time domain unit occupied by the first SSB, wherein X is an integer greater than or equal to 1;

and Y time domain units after the last time domain unit occupied by the first SSB, wherein Y is an integer greater than or equal to 1.

24. The method of claim 23, wherein the first SSB comprises at least one of:

SSB configured for the current serving cell;

SSBs configured for the current serving cell and of a specified type;

SSB configured for the current serving cell, the SSB configured for the current cell can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSB configured for a main serving cell of a cell group where a current serving cell is located;

SSB configured for a main serving cell of a cell group where a current serving cell is located and of a specified type;

The SSB configured for the primary serving cell of the cell group where the current serving cell is located can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSB configured in a frequency domain range of the current downlink bandwidth part BWP;

SSB configured in a frequency domain range of a current downlink BWP and of a specified type;

SSBs configured in the frequency domain of the current downstream BWP, the SSB configured in the frequency domain of the current downlink BWP can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

SSBs that take effect within the current downstream BWP;

SSBs that are valid within the current downstream BWP and of a specified type;

SSBs that are effective within the current downstream BWP, the SSBs that are effective within the current downstream BWP can include: a specified type of SSB and other types of SSBs than the specified type, and the specified type of SSB has a higher priority than the other types of SSBs;

A specified SSB.

25. The method as recited in claim 24, further comprising:

The network side equipment sends first indication information to the terminal, wherein the first indication information comprises the appointed SSB.

26. The method of claim 25, wherein the network-side device indicates the specified SSB by at least one of:

indicating an absolute frequency point of the specified SSB;

an index or an identification of a serving cell corresponding to the designated SSB is indicated;

An index or identity indicating the BWP corresponding to the specified SSB;

And indicating indexes of all SSBs configured on the service cell corresponding to the specified SSB or indexes of all SSBs of the specified type.

27. The method as recited in claim 22, further comprising:

The network side equipment sends second indication information to a terminal, wherein the second indication information is used for indicating a time domain unit capable of supporting SBFD operation or a time domain unit not supporting SBFD operation in the first SSB time domain unit; the second indication information is sent through semi-static configuration information or dynamic indication information;

Or alternatively

The network side equipment receives third indication information sent by a terminal, wherein the second indication information is used for indicating a time domain unit supporting SBFD operation or a time domain unit not supporting SBFD operation in the first SSB time domain unit which is determined based on the terminal, and the third indication information is sent through dynamic indication information.

28. An apparatus for implementing flexible duplexing, comprising:

A first determining module, configured to determine a first SSB time domain unit;

A second determining module, configured to determine SBFD related operations of the first SSB time domain unit.

29. A communication device comprising a processor and a memory storing a program or instructions executable on the processor, the program or instructions implementing the steps of the method of implementing flexible duplexing according to any of claims 1 to 21 when executed by the processor, or the program or instructions implementing the steps of the method of implementing flexible duplexing according to any of claims 22 to 27 when executed by the processor.

30. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps of the method for implementing flexible duplexing according to any one of claims 1 to 21 or the steps of the method for implementing flexible duplexing according to any one of claims 22 to 27.