Flexible-duplex implementation method and apparatus, and terminal, network-side device and medium

By determining the SBFD operation in the synchronous signal block (SSB) time domain unit, the problem that SBFD is difficult to support in the prior art is solved, and interference avoidance and performance improvement in the SSB time domain unit is achieved.

WO2024235067A1PCT designated stage expired Publication Date: 2024-11-21VIVO MOBILE COMM CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091555
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-15
Filing Date
2024-05-08
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The prior art is difficult to support non-overlapping subband full duplex (SBFD) operations in the synchronous signal block (SSB) time domain unit, resulting in difficult to achieve interference and performance improvements in uplink and downlink transmissions.

Method used

By determining the SSB time domain unit in the terminal and network side devices and performing relevant SBFD operations, ensuring SBFD configuration and options within the SSB time slot unit, balancing reception and detection performance, and improving system flexibility.

Benefits of technology

It effectively avoids interference in the SSB time domain unit, improves uplink transmission performance, and enhances system flexibility and operation efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091555_21112024_PF_FP_ABST
    Figure CN2024091555_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application belongs to the technical field of wireless communications. Disclosed are a flexible-duplex implementation method and apparatus, and a terminal, a network-side device and a medium. The flexible-duplex implementation method in the embodiments of the present application comprises: a terminal or a network-side device determining a first SSB time domain unit; and determining an SBFD-related operation of the first SSB time domain unit.
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202310548880.5 filed on May 15, 2023, the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] When deploying traditional cellular networks, frequency division duplex (FDD) or time division duplex (TDD) can be used, depending on the available spectrum and service characteristics. In FDD, uplink and downlink transmissions occur on different frequencies, preventing interference and allowing simultaneous transmission. In TDD, uplink and downlink transmissions occur on the same frequency, interleaved using time division. Each duplex method has its own advantages and disadvantages.

[0005] In order to more flexibly utilize limited spectrum resources, dynamically match business needs, improve resource utilization efficiency, and improve the uplink coverage, latency and other performance of data transmission, a flexible duplex mode is proposed. One 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. To avoid interference between uplink and downlink, a certain guard band (Guard Band) can be reserved between the frequency domain positions corresponding to different transmission directions (corresponding to the duplex sub-band); 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 the two 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 targeted at different terminals.

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

[0007] Summary of the Invention

[0008] 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.

[0009] In a first aspect, a method for implementing flexible duplexing is provided, which is executed by a terminal. The method includes:

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

[0011] The terminal determines sub-band full-duplex (SBFD) related operations of the first SSB time domain unit.

[0012] In a second aspect, a method for implementing flexible duplexing is provided, which is performed by a network-side device. The method includes:

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

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

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

[0016] A first determining module is configured to determine a first SSB time domain unit;

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

[0018] 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 run 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.

[0019] 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.

[0020] 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.

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

[0022] 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.

[0023] 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.

[0024] In the tenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0026] 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, and then balancing and ensuring the performance of SSB reception / detection, as well as SBFD uplink transmission, and improving the flexibility of system operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG1 is a block diagram of a wireless communication system applicable to embodiments of the present application;

[0028] FIG2 is a schematic diagram of a flexible duplex mode;

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

[0030] 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;

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

[0032] FIG6 is a second structural diagram of the apparatus for implementing flexible duplexing according to an embodiment of the present application;

[0033] FIG7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

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

[0035] FIG9 is a schematic diagram of the hardware structure of the network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0037] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way 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 the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0038] The term "indication" in this application can be either 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, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0039] 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 systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0040] FIG1 is 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, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, an aircraft, a vehicle user equipment (VUE), a shipboard device, a pedestrian user equipment (PUE), a smart home (a household appliance with wireless communication capabilities, such as a refrigerator, television, washing machine, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side device. 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 called 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 (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0041] The following is a brief description of some technical points involved in this application.

[0042] (1) Flexible duplex mode

[0043] Please refer to Figure 2, which illustrates a flexible duplexing scheme. Within a portion of downlink symbols, the network semi-statically divides the frequency domain of a single carrier into three duplex subbands. Downlink subbands are located on either side of the carrier, while the center is an uplink subband. This reduces interference with adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception, respectively. UE stands for user equipment, or terminal.

[0044] (2) Cell Definition SSB (CD-SSB) and Non-Cell Definition SSB (NCD-SSB)

[0045] When an SSB is associated with a Remaining Minimal System Information (RMSI), it 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.

[0046] NCD-SSB is an SSB that is not associated with RMSI.

[0047] (3) Semi-static downlink (DL) / uplink (UL) / flexible time domain unit

[0048] Optionally, when a cell (such as an NR cell) is deployed on an asymmetric spectrum, a TDD mode is generally adopted. At this time, TDD-UL-DL-ConfigCommon can be configured in the cell common parameters to indicate TDD frame structure information, including the TDD frame period, the number of complete downlink / uplink time slots (Slots) contained in a single frame period, and the number of downlink / uplink symbols (Symbols) additionally included in the complete downlink / uplink Slots. Optionally, the 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 based on 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. This modification is only applied to the terminal receiving this RRC signaling. However, this modification is limited to further designating a flexible symbol within a slot as a downlink symbol (DL symbol) or an uplink symbol (UL symbol). The DL / UL symbol within a slot cannot be modified to indicate other directions. Flexible symbols are symbols with an unspecified transmission direction; their use for downlink or uplink transmission can be determined later based on demand.

[0049] 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 respectively referred to as a semi-static DL / UL / flexible symbol. In addition, the symbol can be further abstracted into a time domain unit, which can correspond to a time slot (Slot), a symbol (Symbol), etc., and 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 radio frame of the NR cell can be understood as a semi-static flexible slot / symbol, or abstracted as a semi-static flexible time domain unit.

[0050] The following, in conjunction 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.

[0051] Referring to FIG3 , the present application provides a method for implementing flexible duplexing, including:

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

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

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

[0055] 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, and then balancing and ensuring the performance of SSB reception / detection, as well as SBFD uplink transmission, and improving the flexibility of system operation.

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

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

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

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

[0060] The time domain unit occupied by the first SSB;

[0061] 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;

[0062] 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.

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

[0064] 1) The SSB configured for the current serving cell;

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

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

[0067] 3) SSBs configured for the current serving cell, where the SSBs configured for the current cell may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

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

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

[0070] 6) The SSB configured for the primary serving cell of the 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 other than the specified type, and the SSB of the specified type has a higher priority than the SSB of other types;

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

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

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

[0074] 9) SSBs configured within the frequency domain of the current downlink BWP, where the SSBs configured within the frequency domain of the current downlink BWP may include: SSBs of a specified type and SSBs of other types other than the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0075] 10) The SSB that is effective within the current downlink BWP;

[0076] 11) SSBs of a specified type that are valid within the current downlink BWP;

[0077] 12) SSBs valid in the current downlink BWP, where the SSBs valid in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0078] 13) Designated SSB.

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

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

[0081] Cell-defined SSB (CD-SSB);

[0082] Non-Cell Defined SSB (NCD-SSB).

[0083] In some embodiments of the present application, optionally, the transmission position of the first SSB in the time domain may 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, further including a time offset, the time offset is configured by, for example, the parameter ssb-TimeOffset-r17). The SSB index corresponding to the SSB considered at each transmission position may be determined based on any of the following:

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

[0085] 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 System Information Block 1 (SIB1) or ServingCellConfigCommon; for NCD-SSB, the SSB index set corresponding to the corresponding CD-SSB is used.

[0086] 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.

[0087] 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 4), 5) or 6 above). The primary serving cell of the cell group where the current serving cell is located includes at least one of the following: the primary serving cell (PCell) of the primary cell group, and the primary serving cell (PSCell) of the secondary cell group.

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

[0089] Cell-defined SSB (CD-SSB);

[0090] Non-Cell Defined SSB (NCD-SSB).

[0091] Optionally, the designated type may be specified by a protocol or configured by high-layer signaling.

[0092] In an embodiment of the present application, high-layer signaling may include: configuration signaling for radio resource management (RRM), radio link monitoring (RLM), beam measurement, beam failure detection (BFD), and candidate beam detection. The reference signal configured in the above high-layer signaling is SSB.

[0093] 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 the specified type of SSB is not configured, no SSB is used.

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

[0095] In some embodiments of the present application, optionally, the valid SSB includes at least one of the following:

[0096] SSB configured within the frequency domain of the current downlink BWP;

[0097] 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.

[0098] Optionally, the SSB effective within the current downlink BWP may be an SSB effective within the current downlink BWP based on predefined rules. 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 effective. For NCD-SSB, NCD-SSB is configured in BWP-DownlinkDedicated. Therefore, NCD-SSB is effective only when the activated BWP is configured with NCD-SSB.

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

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

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

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

[0103] Indicates the index or identification (ID) of the serving cell corresponding to the designated SSB;

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

[0105] Indicates the indexes of all SSBs configured on the serving cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

[0106] 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.

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

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

[0109] Configuration for the current serving cell;

[0110] Configure within the frequency domain of the current downlink BWP;

[0111] It takes effect within the current downlink BWP.

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

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

[0114] 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 a first SSB-associated time domain unit, referred to as a 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 subsequently referred to as the first SSB associated with this first SSB time domain unit.

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

[0116] SBFD operation mode 1:

[0117] 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.

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

[0119] 1) A first subcondition, the first subcondition including: 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 SBFD 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;

[0120] 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.

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

[0122] 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 the SBFD time domain unit by default.

[0123] 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:

[0124] If the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD do not meet the second condition, adopt the first sub-condition as the first condition;

[0125] If 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, the second sub-condition is adopted as the first condition;

[0126] The second condition includes: the configuration period of SBFD is N times the period of the first SSB, where N is an integer greater than or equal to 1.

[0127] In an embodiment of the present application, when the 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.

[0128] 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".

[0129] SBFD operation mode 2:

[0130] 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 can support SBFD operation.

[0131] 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).

[0132] 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.

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

[0134] 1) SSB time domain unit range 1: All time domain units of the uplink subband are configured within the first SSB time domain unit;

[0135] 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.

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

[0137] 2) SSB time domain unit range 2: time domain units that are configured with an uplink subband within the first SSB time domain unit and that meet the third condition, where the third condition includes at least one of the following:

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

[0139] 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 the 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.

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

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

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

[0143] 3) SSB time domain unit range 3: time domain units within the first SSB time domain unit that can support SBFD operations, as indicated in the semi-static configuration information of the network-side device. The semi-static configuration information is used to indicate time domain units within the first SSB time domain unit that can support SBFD operations, or time domain units that do not support SBFD operations.

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

[0145] 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).

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

[0147] 4) SSB time domain unit range 4: time domain units within the first SSB time domain unit that can support SBFD operations, as indicated in the dynamic indication information of the network-side device, where the dynamic indication information is used to indicate time domain units within the first SSB time domain unit that can support SBFD operations, or time domain units that do not support SBFD operations;

[0148] In an embodiment of the present application, optionally, SSB time domain unit range 4 is further indicated by 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, and SSB time domain unit range 5.

[0149] 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)).

[0150] 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.

[0151] The so-called self-realization refers to the decision made by the terminal itself.

[0152] In an embodiment of the present application, optionally, the SSB time domain unit range 5 is further determined by the terminal 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.

[0153] 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 within the first SSB time domain unit, a dynamic indication is made to the network side device. That is, the method further includes: 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, 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 within the first SSB time domain unit.

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

[0155] 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 within 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 within this first SSB time domain unit, and no uplink transmission is performed.

[0156] 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 SBFD operations, also referred to as an SBFD time domain unit).

[0157] Only half-duplex is supported:

[0158] 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 supports only 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, where the first SBFD operation includes at least one of the following:

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

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

[0161] Rule 3: Drop or postpone the semi-statically configured PUSCH, PUCCH, SRS or Physical Random Access Channel (PRACH) transmission that overlaps with the second SSB time domain unit.

[0162] The following content mainly explains Rule 1.

[0163] 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:

[0164] When 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;

[0165] 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;

[0166] 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;

[0167] 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.

[0168] 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.

[0169] 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 in the frequency domain of any first SSB associated with the second SSB time domain unit is greater than or not less than the preset interval threshold).

[0170] The dynamic coverage here can be understood as: using Layer 1 (L1) / Layer 2 (L2) signaling (such as DCI or MAC CE) to dynamically modify or enable / disable the uplink subbands semi-statically configured by higher-layer signaling within 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).

[0171] 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 always serves 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.

[0172] 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 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; UL-only time domain unit.

[0173] 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.

[0174] 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:

[0175] When the dynamically scheduled PUSCH or PUCCH adopts a repetition transmission mode, the terminal, during a 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);

[0176] In a 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);

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

[0178] In a case where the dynamically scheduled PUSCH adopts a TB processing over multi-slot PUSCH (TBoMS) mode, the terminal uses transmission in a first available time slot as dynamically scheduled PUSCH transmission and performs transmission in the first available time slot that overlaps with the second SSB time domain unit (i.e., applying the above rule 1);

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

[0180] 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 the other available time slots overlapping with the second SSB time domain unit (that is, the above rule 3 is applied).

[0181] 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).

[0182] The following content mainly explains Rule 2.

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

[0184] In some embodiments of the present application, optionally, when the first SBFD operation includes being capable of performing 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:

[0185] 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., applies the above rule 2);

[0186] 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. When 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);

[0187] When dynamic coverage is applied, the terminal determines that the second SSB time domain unit is an 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);

[0188] In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is an SBFD time domain unit, and when 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);

[0189] 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);

[0190] 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).

[0191] 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 within the second SSB time domain unit.

[0192] 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 this second SSB time domain unit, 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, any of the following can be applied:

[0193] The network side device may ensure that the frequency domain resources occupied by the semi-statically configured PUSCH / PUCCH / SRS are all located within 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 a preset interval threshold);

[0194] 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 the 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).

[0195] For semi-statically configured PRACH transmission:

[0196] In some embodiments of the present application, optionally, when the first SBFD operation includes being capable of performing 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:

[0197] 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 during a PRACH occasion validation process, if 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;

[0198] When dynamic coverage is applied, the terminal determines that the second SSB time domain unit is an SBFD time domain unit. During the PRACH opportunity check process, 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;

[0199] When dynamic coverage is applied, the terminal determines that the second SSB time domain unit is a time domain unit for uplink only. During the PRACH opportunity check process, 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;

[0200] 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 occasion (PRACH occasion, RO) to SSB, the corresponding operations when dynamic coverage is not applied are still used during the PRACH occasion check. However, during the PRACH occasion check, there is a first PRACH occasion that overlaps 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 judges the first PRACH occasion as possibly valid, but does not allow the first PRACH occasion to be selected to initiate PRACH transmission.

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

[0202] The following content mainly explains Rule 3.

[0203] In some embodiments of the present application, optionally, when the first SBFD operation includes dropping 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:

[0204] In a case where the semi-static configuration of the PUSCH adopts repetition type A (PUSCH repetition Type A), there is a repetition transmission overlapping with the second SSB time domain unit, and available slot counting is configured to be enabled, the terminal delaying the repetition transmission;

[0205] When the semi-static configuration PUSCH adopts repetition transmission type A, and there is a repetition 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 repetition transmission;

[0206] 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, the terminal delays the transmission or discards the any TBoMS;

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

[0208] When the semi-statically configured PUSCH is configured as a grant PUSCH, the grant PUSCH adopts repetition transmission type A, there is a repetition transmission overlapping with the second SSB time domain unit, and the available time slot count is configured to be started, the terminal delays the repetition transmission;

[0209] When the semi-statically configured PUSCH is a configured granted PUSCH, the configured granted PUSCH adopts repetition 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;

[0210] 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;

[0211] When a semi-statically configured PUCCH transmission overlaps with the second SSB time domain unit, the terminal delays the semi-statically configured PUCCH transmission;

[0212] 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;

[0213] During the PRACH opportunity verification process, the terminal uses the second SSB time domain unit when determining whether any PRACH opportunity is valid.

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

[0215] This PRACH opportunity is entirely within the uplink subband;

[0216] 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 away from the last second SSB time domain unit. gaptime domain units, where N gap It can be specified by the protocol or configured by high-level signaling.

[0217] 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 that supports SBFD operation, an SSB time domain unit that does not support SBFD operation.

[0218] Optionally, the semi-statically configured PUCCH includes a PUCCH for carrying semi-persistent scheduling (SPS) hybrid automatic repeat request acknowledgement (HARQ-ACK), periodic or semi-persistent channel state information (P / SP-CSI), and scheduling request (SR). The SPS HARQ-ACK here can be understood as HARQ-ACK for the SPS PDSCH.

[0219] 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:

[0220] 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.

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

[0222] Full-duplex support:

[0223] 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:

[0224] 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;

[0225] 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 and other possible downlink reception within the second SSB time domain unit).

[0226] 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:

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

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

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

[0230] Optionally, for UEs supporting full-duplex SBFD operations, in order to ensure SSB reception / measurement performance, only half-duplex SBFD operations may be supported within 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 details on only supporting half-duplex SBFD operations, please refer to the description in the above embodiment, which will not be repeated here.

[0231] In an 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 data transmission (RACH-Small Data Transmission, RA-SDT) or configured grant-based small data transmission (Configured Grant-Small 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.

[0232] Referring to FIG4 , an embodiment of the present application further provides a method for implementing flexible duplexing, including:

[0233] Step 41: The network-side device determines the first SSB time domain unit;

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

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

[0236] 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.

[0237] 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.

[0238] In some embodiments of the present application, optionally, the network-side device determining the first SSB time domain unit includes:

[0239] The network side device determines at least one first SSB;

[0240] 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:

[0241] The time domain unit occupied by the first SSB;

[0242] 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;

[0243] 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.

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

[0245] 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.

[0246] SSB of a specified type configured for the current serving cell;

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

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

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

[0250] 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 SSB of the specified type has a higher priority than the SSB of other types;

[0251] 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.

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

[0253] SSBs configured within the frequency domain of the current downlink BWP, where the SSBs configured within the frequency domain of the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0254] The SSB that is effective within the current downlink BWP;

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

[0256] The SSBs valid in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0257] Designated SSB.

[0258] 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.

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

[0260] Indicates the absolute frequency of the specified SSB;

[0261] Indicates the index or identifier of the serving cell corresponding to the designated SSB;

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

[0263] Indicates the indexes of all SSBs configured on the serving cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

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

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

[0266] 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 unit that supports SBFD operation within the first SSB time domain unit determined by the terminal based on its own implementation, or the time domain unit that does not support SBFD operation, and the third indication information is sent through dynamic indication information.

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

[0268] Referring to FIG5 , an embodiment of the present application further provides a flexible duplexing implementation apparatus 50 , including:

[0269] A first determining module 51 is configured to determine a first SSB time domain unit;

[0270] The first determining module 52 is configured to determine the SBFD related operations of the first SSB time domain unit.

[0271] 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, and then balancing and ensuring the performance of SSB reception / detection, as well as SBFD uplink transmission, and improving the flexibility of system operation.

[0272] In this embodiment of the present application, optionally, the first determining module 51 is configured to determine at least one first SSB; and 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:

[0273] The time domain unit occupied by the first SSB;

[0274] 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;

[0275] 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.

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

[0277] SSB configured for the current serving cell;

[0278] SSB of a specified type configured for the current serving cell;

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

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

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

[0282] 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 SSB of the specified type has a higher priority than the SSB of other types;

[0283] SSB configured within the frequency domain of the current downlink BWP;

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

[0285] SSBs configured within the frequency domain of the current downlink BWP, where the SSBs configured within the frequency domain of the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0286] The SSB that is effective within the current downlink BWP;

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

[0288] The SSBs valid in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0289] Designated SSB.

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

[0291] Cell definition SSB;

[0292] Non-cell defined SSB.

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

[0294] SSB configured within the frequency domain of the current downlink BWP;

[0295] 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.

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

[0297] Indicates the absolute frequency of the specified SSB;

[0298] Indicates the index or identifier of the serving cell corresponding to the designated SSB;

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

[0300] Indicates the indexes of all SSBs configured on the serving cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

[0301] In an embodiment of the present application, optionally, the designated SSB satisfies at least one of the following:

[0302] Configuration for the current serving cell;

[0303] Configure within the frequency domain of the current downlink BWP;

[0304] It takes effect within the current downlink BWP.

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

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

[0307] A first sub-condition, the first sub-condition including: an uplink 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;

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

[0309] 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, including:

[0310] If the period of the first SSB associated with the first SSB time domain unit and the configuration period of the SBFD do not meet the second condition, adopt the first sub-condition as the first condition;

[0311] If 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, the second sub-condition is adopted as the first condition;

[0312] The second condition includes: the configuration period of SBFD is N times the period of the first SSB, where N is an integer greater than or equal to 1.

[0313] In an embodiment of the present application, optionally, the second determination module 52 is used to determine whether SBFD operation can be supported within the first SSB time domain unit.

[0314] In an 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.

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

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

[0317] An uplink subband is configured in the first SSB time domain unit and a time domain unit that meets 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 between the configured uplink subband and any first SSB associated with the first SSB time domain unit in the frequency domain 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 a guard band in the frequency domain; and any first SSB associated with the first SSB time domain unit is located within the frequency domain range of a downlink subband;

[0318] The time domain unit capable of supporting the 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 being used to indicate the time domain unit capable of supporting the SBFD operation, or the time domain unit not supporting the SBFD operation, within the first SSB time domain unit;

[0319] The time domain unit that can support the SBFD operation within the first SSB time domain unit indicated in the dynamic indication information of the network side device, the dynamic indication information is used to indicate the time domain unit that can support the SBFD operation within the first SSB time domain unit, or the time domain unit that does not support the SBFD operation;

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

[0321] 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 the 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. 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.

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

[0323] When 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:

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

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

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

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

[0328] When the terminal supports full-duplex SBFD operation in the second SSB time domain unit, determining that uplink transmission can be performed in the uplink subband configured in the second SSB time domain unit, or determining, by the terminal, a first SBFD operation supported by the second SSB time domain unit, where the first SBFD operation includes at least one of the following:

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

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

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

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

[0333] In a 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;

[0334] In the case of applying dynamic coverage, determining that the second SSB time domain unit is 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;

[0335] 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;

[0336] When dynamic coverage is applied, 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.

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

[0338] In a case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, during a first repeated transmission, the first repeated transmission is used as a 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;

[0339] In a case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, in other repeated transmissions except the first repeated transmission, the other repeated transmissions are regarded 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;

[0340] In a case where the dynamically scheduled 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 discarded or delayed;

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

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

[0343] 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.

[0344] In this embodiment of the present application, optionally, 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; and determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

[0345] When dynamic coverage is not applied, determining that the second SSB time domain unit is always used as an 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;

[0346] When dynamic coverage is not applied, determining 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 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;

[0347] In the case of applying dynamic coverage, determining that the second SSB time domain unit is an SBFD time domain unit, and in a 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;

[0348] In the case of applying dynamic coverage, determining that the second SSB time domain unit is an SBFD time domain unit, and in a case where 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;

[0349] 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 discarding or delaying the semi-statically configured PUSCH, PUCCH or SRS transmission;

[0350] When dynamic coverage is applied, 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.

[0351] In this embodiment of the present application, optionally, the first SBFD operation includes being capable of performing a semi-statically configured PRACH transmission that overlaps with the second SSB time domain unit; and determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

[0352] When 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 during the PRACH opportunity check process, 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;

[0353] When dynamic coverage is applied, determining that the second SSB time domain unit is an SBFD time domain unit, and during the PRACH opportunity check process, if 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;

[0354] When dynamic coverage is applied, determining that the second SSB time domain unit is a time domain unit for uplink only, and during the PRACH opportunity check process, if 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;

[0355] When dynamic coverage is applied, the second SSB time domain unit is determined to be 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 judges the first PRACH opportunity as possibly valid, but does not allow the first PRACH opportunity to be selected to initiate PRACH transmission.

[0356] In this embodiment of the present application, optionally, the first SBFD operation includes dropping or delaying a semi-statically configured PUSCH, PUCCH, SRS, or PRACH transmission overlapping with the second SSB time domain unit; and determining the first SBFD operation supported by the second SSB time domain unit includes at least one of the following:

[0357] In a case where the semi-static configuration PUSCH adopts repetition transmission type A, there is repetition transmission overlapping with the second SSB time domain unit, and the available time slot count is configured to be started, delaying the repetition transmission;

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

[0359] When the semi-static configuration of the PUSCH adopts the 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;

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

[0361] When the semi-statically configured PUSCH is a configured granted PUSCH, the configured granted PUSCH adopts repeated transmission type A, and there is repeated transmission overlapping with the second SSB time domain unit, and the available time slot count is configured to be started, delaying the repeated transmission;

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

[0363] 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;

[0364] When a semi-statically configured PUCCH transmission overlaps with the second SSB time domain unit, the terminal delays the semi-statically configured PUCCH transmission;

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

[0366] 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.

[0367] The flexible duplexing implementation device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiments of the present application.

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

[0369] Referring to FIG6 , an embodiment of the present application further provides a flexible duplexing implementation apparatus 60 , including:

[0370] A first determining module 61 is configured to determine a first SSB time domain unit;

[0371] The second determining module 62 is configured to determine the SBFD related operations of the first SSB time domain unit.

[0372] 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.

[0373] In this embodiment of the present application, optionally, the first determining module 61 is configured to determine at least one first SSB; and 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:

[0374] The time domain unit occupied by the first SSB;

[0375] 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;

[0376] 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.

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

[0378] SSB configured for the current serving cell;

[0379] SSB of a specified type configured for the current serving cell;

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

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

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

[0383] 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 SSB of the specified type has a higher priority than the SSB of other types;

[0384] SSB configured within the frequency domain of the current downlink BWP;

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

[0386] SSBs configured within the frequency domain of the current downlink BWP, where the SSBs configured within the frequency domain of the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0387] The SSB that is effective within the current downlink BWP;

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

[0389] The SSBs valid in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority than the SSBs of other types;

[0390] Designated SSB.

[0391] In an embodiment of the present application, optionally, the flexible duplex implementation device 60 further includes: a first sending module, configured to send first indication information to the terminal, wherein the first indication information includes the designated SSB.

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

[0393] Indicates the absolute frequency of the specified SSB;

[0394] Indicates the index or identifier of the serving cell corresponding to the designated SSB;

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

[0396] Indicates the indexes of all SSBs configured on the serving cell corresponding to the specified SSB or the indexes of all SSBs of a specified type.

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

[0398] or,

[0399] The receiving module is used to receive the third indication information sent by the terminal, where the second indication information is used to indicate the time domain unit that supports SBFD operation within the first SSB time domain unit determined by the terminal based on its own implementation, or the time domain unit that does not support SBFD operation, and the third indication information is sent through dynamic indication information.

[0400] 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 a component in the electronic device, such as an integrated circuit or a chip.

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

[0402] As shown in Figure 7, an embodiment of the present application further provides a communication device 70, including a processor 71 and a memory 72. The memory 72 stores 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, when executed by the processor 71, implements the various steps of the embodiment of the method for implementing flexible duplexing executed on the terminal side, and can achieve the same technical effect. When the communication device 70 is a network-side device, the program or instruction, when executed by the processor 71, implements the various steps of the embodiment of the method for implementing flexible duplexing executed on the network-side device side, and can achieve the same technical effect. To avoid repetition, they are not described here.

[0403] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0404] 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.

[0405] Those skilled in the art will appreciate that the terminal 80 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG8 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0406] It should be understood that in an embodiment of the present application, the input unit 84 may include a graphics processing unit (GPU) 841 and a microphone 842, and the graphics processing unit 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.

[0407] In the embodiment of the present application, after receiving downlink data from the network-side device, the radio frequency unit 81 can transmit the data to the processor 810 for processing. In addition, the radio frequency unit 81 can send uplink data to the network-side device. Generally, the radio frequency unit 81 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0408] 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. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 89 may include a volatile memory or a non-volatile memory. 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 random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM 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.

[0409] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

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

[0411] 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, and then balancing and ensuring the performance of SSB reception / detection, as well as SBFD uplink transmission, and improving the flexibility of system operation.

[0412] 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.

[0413] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG4 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0414] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 9, 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. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0415] 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.

[0416] The baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the network device operations shown in the above method embodiment.

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

[0418] 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 of execution of each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0419] 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, the various processes of the above-mentioned flexible duplex implementation method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0420] 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-transitory readable storage medium.

[0421] 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.

[0422] 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.

[0423] An 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.

[0424] 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.

[0425] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising 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 a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments 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 the opposite 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.

[0426] Through the description of the above embodiments, 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-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0427] 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 this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for implementing flexible duplexing, comprising: 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.

2. The method according to claim 1, wherein: The terminal determining the first SSB time domain unit includes: 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 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.

3. The method according to claim 2, wherein: 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 bandwidth part 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 that are effective in the current downlink BWP may include: SSBs of a specified type and SSBs of other types except the specified type, and the SSBs of the specified type have a higher priority. for the other types of SSBs described above; Designated SSB.

4. The method according to claim 3, wherein: The specified type includes at least one of the following: The cell defines SSB; Non-cell defined SSB.

5. The method according to claim 3, wherein: 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.

6. The method according to claim 3, wherein: The designated SSB is indicated by at least one of the following methods: 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.

7. The method according to claim 3 or 6, wherein: 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.

8. The method according to claim 1 or 2, wherein: The terminal determines the SBFD-related operation of the first SSB time domain unit including: When the first condition is met, the terminal determines that the first SSB time domain unit does not support SBFD operation.

9. The method according to claim 8, wherein: 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.

10. The method according to claim 9, wherein: When the first condition is met, the terminal determines that the first SSB time domain unit does not support the SBFD operation, including: 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.

11. The method according to claim 1 or 2, wherein: The terminal determines the SBFD-related operation of the first SSB time domain unit including: The terminal determines that SBFD operation can be supported within the first SSB time domain unit.

12. The method according to claim 11, wherein: The terminal determining that the first SSB time domain unit can support the SBFD operation includes: The terminal determines a second SSB time domain unit supporting SBFD operation within the first SSB time domain unit.

13. The method according to claim 12, wherein: 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; A time domain unit in which an uplink subband is configured in the first SSB time domain unit and 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, based on its own implementation, a time domain unit within the first SSB time domain unit that supports SBFD operation.

14. The method according to claim 13, further comprising: When the terminal determines, based on its own implementation, the time domain units within the first SSB time domain unit that support SBFD operations, or the time domain units that do not support SBFD operations, the terminal sends dynamic indication information to the network side device, and the dynamic indication information is used to notify the determined time domain units within the first SSB time domain unit that support SBFD operations, or the time domain units that do not support SBFD operations.

15. The method according to claim 12, wherein: The terminal determines the SBFD-related operation of the first SSB time domain unit including: In a case where the terminal supports only a 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, where the first SBFD operation includes at least one of the following: Capable of performing dynamic scheduling of 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; Capable of performing semi-static configuration of PUSCH, PUCCH, SRS or PRACH overlapping with the second SSB time domain unit transmission; Drop or delay semi-statically configured PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit.

16. The method according to claim 12, wherein: The terminal determines the SBFD-related operation of the first SSB time domain unit including: In a case where the terminal supports full-duplex SBFD operation in the second SSB time domain unit, the terminal determines 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.

17. The method according to claim 15 or 16, wherein: The terminal determines, by the second SSB time domain unit, that the first SBFD operation supported includes at least one of the following: In the case where dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as 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 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 time domain unit used only for downlink, 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 a time domain unit used only for uplink, and performs the dynamic scheduling of PUSCH, PUCCH or SRS transmission.

18. The method according to claim 15 or 16, wherein: The terminal determines, by the second SSB time domain unit, that the first SBFD operation supported includes at least one of the following: In a case where the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, the terminal, during the first repeated transmission, uses the first repeated 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 repeated transmission; 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; In the case where the dynamic scheduling of PUSCH or PUCCH adopts a repeated transmission mode, the terminal When other repeated transmissions other than repeated transmissions are performed, 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 discarded or delayed; In the case where the dynamically scheduled PUSCH adopts a TBoMS mode of sending a transmission block in multiple time slots, 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; 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; 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 the other available time slots overlapping with the second SSB time domain unit.

19. The method according to claim 15 or 16, wherein: The first SBFD operation includes being capable of performing a semi-statically configured PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit; The terminal determines, by the second SSB time domain unit, that the first SBFD operation supported 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 an 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; When dynamic coverage is not applied, the terminal determines that the second SSB time domain unit is always used as an SBFD time domain unit, and when 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, 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; 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 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, 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; 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 unit, and performs the semi-static configuration of PUSCH, PUCCH or SRS transmission.

20. The method according to claim 15 or 16, wherein: The first SBFD operation includes being capable of performing a semi-statically configured PRACH transmission overlapping with the second SSB time domain unit; The terminal determines, by the second SSB time domain unit, that the first SBFD operation supported 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 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, 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. During the PRACH timing check, there is a first PRACH timing that overlaps with the second SSB time domain unit, and the frequency domain resources occupied by the first PRACH timing are all located in the uplink subband configured by the second SSB time domain unit. The terminal determines that the first PRACH timing is possibly valid, but does not allow the first PRACH timing 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 a semi-statically configured PUSCH, PUCCH, SRS, or PRACH transmission that overlaps 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 repetitive transmission type A, and there is a repetitive transmission overlapping with the second SSB time domain unit, and the available time slot count is configured to be started, the terminal delays 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, 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 configured authorized PUSCH, and repeated transmission type A or TBoMS is not configured, and there is a configured authorized PUSCH transmission overlapping with the second SSB time domain unit, the terminal discards 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, 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 delays 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.

22. A method for implementing flexible duplex, the method comprising: 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.

23. The method according to claim 22, wherein: 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.

24. The method according to claim 23, wherein: 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 bandwidth part 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.

25. The method according to claim 24, further comprising: The network side device sends first indication information to the terminal, and the first indication information includes the designated SSB.

26. The method according to claim 25, wherein: 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.

27. The method according to claim 22, further comprising: The network side device sends second indication information to the terminal, where the second indication information is used to indicate a time domain unit in the first SSB time domain unit that can support the SBFD operation, or a time domain unit that does not support the SBFD operation; the second indication information is sent through semi-static configuration information, or through dynamic indication information; or, The network side device receives the third indication information sent by the terminal, where 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.

28. A device for implementing flexible duplex, the device comprising: 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.

29. A communication device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, wherein: When the program or instruction is executed by the processor, the steps of the method for implementing flexible duplexing as described in any one of claims 1 to 21 are implemented, or when the program or instruction is executed by the processor, the steps of the method for implementing flexible duplexing as described in any one of claims 22 to 27 are implemented.

30. A readable storage medium storing a program or an instruction, wherein: When the program or instruction is executed by the processor, the steps of the method for implementing flexible duplexing as described in any one of claims 1 to 21 are implemented, or when the program or instruction is executed by the processor, the steps of the method for implementing flexible duplexing as described in any one of claims 22 to 27 are implemented.

Citation Information

Patent Citations

  • Transmission control method and device, terminal and readable storage medium

    CN115333704A

  • Communication system

    GB202216500D0