CN118972950A

CN118972950A - Method, device, terminal, network side equipment and medium for realizing flexible duplex

Info

Publication number: CN118972950A
Application number: CN202310548880.5A
Authority: CN
Inventors: 曾超君; 王理惠
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Filing date: 2023-05-15
Publication date: 2024-11-15

Abstract

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

Description

Method, device, terminal, network side equipment and medium for realizing flexible duplex

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a method, a device, a terminal, network side equipment and a medium for realizing flexible duplex.

Background

In deploying a conventional cellular network, frequency division duplexing (Frequency Division Duplex, FDD) or time division duplexing (Time Division Duplex, TDD) modes may be employed based on available spectrum and traffic characteristics, etc. When FDD is adopted, uplink transmission and downlink transmission are located on different frequency points, and the uplink transmission and the downlink transmission are not interfered with each other and can be performed simultaneously. When TDD is adopted, the uplink transmission and the downlink transmission are positioned on the same frequency point and are staggered in a time division mode. Both duplex modes have advantages and disadvantages.

In order to more flexibly utilize limited spectrum resources to dynamically match service requirements, improve the utilization efficiency of resources, and the performances of uplink coverage, time delay and the like of data transmission, a flexible duplex mode is provided. A flexible duplex mode (non-overlapping sub-band full duplex, non-overlapping sub-band full duplex SBFD) is: full duplex at network side, that is, at the same time, uplink transmission and downlink transmission can be performed at different frequency domain positions simultaneously, and in order to avoid interference between uplink and downlink, a certain Guard Band (Guard Band) can be reserved between frequency domain positions (corresponding to duplex sub-bands) corresponding to different transmission directions; terminal side half duplex, that is, the same as TDD, can only make uplink transmission or downlink transmission at the same time, and the two can not be made simultaneously. It will be appreciated that in this duplex mode, the uplink and downlink transmissions at the same time on the network side can only be directed to different terminals.

However, relevant details for supporting SBFD operation (operation) in Synchronization SIGNAL AND PBCH block (SSB) time domain units are currently lacking.

Disclosure of Invention

The embodiment of the application provides a method, a device, a terminal, network side equipment and a medium for realizing flexible duplex, which can solve the problem of how to realize the operation support SBFD in an SSB time domain unit.

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

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

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

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

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

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

In a third aspect, an implementation apparatus of flexible duplex is provided, including:

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

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

In a fourth aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

In a fifth aspect, a terminal is provided, including a processor and a communication interface, where the processor is configured to determine a first synchronization data block SSB time domain unit; a sub-band full duplex SBFD related operation of the first SSB time domain unit is determined.

In a sixth aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the second aspect.

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

In an eighth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect or performs the steps of the method according to the second aspect.

In a ninth aspect, there is provided a wireless communication system comprising: a terminal operable to perform the steps of the method as described in the first aspect, and a network side device operable to perform the steps of the method as described in the second aspect.

In a tenth aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being for running a program or instructions to implement the method according to the first aspect or to implement the method according to the second aspect.

In an eleventh aspect, there is provided a computer program/program product stored in a storage medium, the program/program product being executable by at least one processor to perform the steps of the method according to the first or second aspect.

In the embodiment of the application, for each link of carrying out SBFD related operations in the SSB time slot unit, a corresponding solution is introduced, so that the terminal behavior under SBFD configuration/option is clarified, the performances of SSB receiving/detecting, uplink transmission of SBFD and the like can be balanced and ensured, and the flexibility of system operation is improved.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

FIG. 2 is a schematic diagram of a flexible duplex mode;

Fig. 3 is a flow chart of a method for implementing flexible duplex executed by a terminal according to an embodiment of the present application;

Fig. 4 is a flow chart of a method for implementing flexible duplex executed by a network side device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a flexible duplex implementation apparatus according to an embodiment of the present application;

FIG. 6 is a second schematic diagram of a flexible duplex implementation apparatus according to an embodiment of the present application;

Fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

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

fig. 9 is a schematic hardware structure of a network side device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms "first," "second," and the like, herein, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, the "or" in the present application means at least one of the connected objects. For example, "a or B" encompasses three schemes, scheme one: including a and excluding B; scheme II: including B and excluding a; scheme III: both a and B. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "indication" according to the application may be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). The direct indication may be understood that the sender explicitly informs the specific information of the receiver, the operation to be executed, the request result, and other contents in the sent indication; the indirect indication may be understood as that the receiving side determines corresponding information according to the indication sent by the sending side, or determines and determines an operation or a request result to be executed according to a determination result.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), or other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for exemplary purposes and the NR terminology is used in much of the description below, but the techniques are also applicable to systems other than NR systems, such as the 6th generation (6th Generation,6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a Mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer), a notebook (Personal DIGITAL ASSISTANT, PDA), a palm Computer, a netbook, an Ultra-Mobile Personal Computer (Ultra-Mobile Personal Computer, UMPC), a Mobile internet device (Mobile INTERNET DEVICE, MID), a Personal Digital Assistant (PDA), Augmented Reality (Augmented Reality, AR), virtual Reality (VR) devices, robots, wearable devices (Wearable Device), aircraft (FLIGHT VEHICLE), in-vehicle devices (Vehicle User Equipment, VUE), on-board equipment, pedestrian terminals (PEDESTRIAN USER EQUIPMENT, PUE), smart home (home appliances having wireless communication function, such as refrigerator, television, washing machine or furniture, etc.), game machine, personal computer (Personal Computer, PC), teller machine or self-service machine, etc. The wearable device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. The in-vehicle apparatus may also be referred to as an in-vehicle terminal, an in-vehicle controller, an in-vehicle module, an in-vehicle component, an in-vehicle chip, an in-vehicle unit, or the like. 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 core network device, where the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function, or a radio access network element. The Access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) Access Point (AS), or a wireless fidelity (WIRELESS FIDELITY, WIFI) node, etc. among them, the base station may be called a Node B (NB), an Evolved Node B (eNB), a next generation Node B (the next generation Node B, gNB), a New air interface Node B (New Radio Node B, NR Node B), an access point, a relay station (Relay Base Station, RBS), a serving base station (Serving Base Station, SBS), a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic service set (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), a Home Node B (HNB), a home evolved Node B (home evolved Node B), a transmission and reception point (Transmission Reception Point, TRP) or some other suitable terminology in the field, the base station is not limited to a specific technical vocabulary as long as the same technical effect is achieved, In the embodiment of the present application, only the base station in the NR system is described as an example, and the specific type of the base station is not limited.

The following provides a brief description of some of the technical aspects to which the present application relates.

(1) Flexible duplex mode

Referring to fig. 2, fig. 2 is a schematic diagram of a flexible duplex mode, in which a network side semi-statically divides a frequency domain of a single carrier into three duplex subbands in a part of downlink symbols, wherein downlink duplex subbands are arranged on both sides of the carrier, and uplink duplex subbands are arranged in the center of the carrier, so as to reduce interference caused to adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception, respectively.

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

When an SSB is associated with the remaining minimum system message (REMAINING MINIMAL SYSTEM Information, RMSI), the SSB is referred to as a cell definition SSB (CD-SSB). The primary serving cell (PCell) is always associated with a CD-SBB located on a synchronization grid.

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

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

Alternatively, TDD mode is typically employed when cells (such as NR cells) are deployed on an asymmetric spectrum. At this time, TDD-UL-DL-ConfigCommon may be configured in the cell common parameters to indicate TDD frame structure information, including TDD frame period, number of complete downlink/uplink slots (slots) contained in a single frame period, number of downlink/uplink symbols (symbols) additionally contained outside the complete downlink/uplink slots, etc. Optionally, a radio resource control (Radio Resource Control, RRC) signaling independent configuration parameter TDD-UL-DL-ConfigDedicated may also be employed for each terminal for further modifying the uplink and downlink Symbol configuration of one or more slots in a single frame period on the basis of TDD-UL-DL-ConfigCommon, i.e. the initial value of the uplink and downlink Symbol configuration of a Slot is specified by TDD-UL-DL-ConfigCommon and then further modified by TDD-UL-DL-ConfigDedicated, which modification is only applied to terminals receiving this RRC signaling. However, the modification is limited to further indicating Flexible symbols (Flexible symbols) in the Slot as downlink symbols (DL symbols) or uplink symbols (UL symbols), and the DL/UL symbols in the Slot cannot be modified to other directions. The Flexible symbol is a symbol with an undefined transmission direction, and whether to use for downlink transmission or uplink transmission can be determined later according to the need.

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

The method, the device, the terminal, the network side equipment and the medium for realizing the flexible duplex provided by the embodiment of the application are described in detail through some embodiments and application scenes thereof by combining the attached drawings.

Referring to fig. 3, the present application provides a method for implementing flexible duplex, including:

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

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

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

1. The following first describes how the first SSB time domain unit is determined in step 31.

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

step 311: the terminal determines at least one first SSB;

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

a time domain unit occupied by the first SSB;

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

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

In some embodiments of the application, optionally, the first SSB comprises at least one of:

1) -SSB configured for the current serving cell (SERVING CELL);

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

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

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

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

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

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

7) SSB configured in a frequency domain range of a current downstream Bandwidth Part (BWP);

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

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

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

10 SSB that is in effect within the current downstream BWP;

11A SSB that is in effect within the current downstream BWP and of a specified type;

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

13 A) the specified SSB.

In some embodiments of the application, the first SSB may optionally be configured by protocol conventions or higher layer signaling.

cell definition SSB (CD-SSB);

non-cell defined SSB (NCD-SSB).

In some embodiments of the present application, optionally, for the transmission position of the first SSB in the time domain, the corresponding SSB period may be determined by the SSB period corresponding to each first SSB (e.g. configured by the parameter SSB-PeriodicityServingCell or SSB-Periodicity-r 17; optionally, for the NCD-SSB, further including a time offset, e.g. configured by the parameter SSB-TimeOffset-r 17). The SSB index (index) corresponding to the SSB considered for each transmission location may be determined based on any one of the following:

An SSB index corpus corresponding to all Candidate (CANDIDATE) SSB locations determined based on a predefined Pattern (Pattern) (e.g., case a/B/C/D/E specified by a protocol);

SSB index determined based on specified parameters, e.g., for CD-SSB, SSB index set is determined based on SSB-PositionsInBurst parameters in SIB1 or ServingCellConfigCommon; for NCD-SSB, a corresponding set of SSB index for the corresponding CD-SSB is used.

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

Alternatively, the first SSB may be 4), 5), or 6) above when the current serving cell is not configured with any SSB (e.g., the current SERVING CELL is SCell (secondary cell) with no SSB configured). The primary serving cell of the cell group where the current serving cell is located comprises at least one of the following: primary serving cell (PCell) of primary cell group, primary serving cell (PSCell) of secondary cell group.

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

cell definition SSB (CD-SSB);

non-cell defined SSB (NCD-SSB).

Alternatively, the specified type may be specified by a protocol or configured by higher layer signaling.

In an embodiment of the present application, the high-level signaling may include: configuration signaling for radio resource management (Radio Resource Management, RRM), radio Link Monitoring (RLM), beam measurement (Beam measurement), beam failure detection (Beam failure detection, BFD), candidate Beam detection (CANDIDATE BEAM DETECTION), the reference signal for the higher layer signaling configuration being SSB.

In some embodiments of the application, alternatively, only the specified types of SSBs are used in 2), 5), 8) or 11) above. When the specified type of SSB is not configured, any SSB is not used.

The specified type of SSB is preferably used in 3), 6), 9) or 12) above, and when the specified type of SSB is not configured, the other type of SSB (if the other type of SSB is configured) is used.

In some embodiments of the application, optionally, the validated SSB comprises at least one of:

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

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

Alternatively, the SSB that is validated within the current downstream BWP may be an SSB that is validated within the current downstream BWP based on a predefined rule. For example, a CD-SSB is a cell-specific signal configured by SIB1 or ServingCellConfigCommon, which is always active regardless of whether the active BWP contains a CD-SSB; whereas for NCD-SSB, NCD-SSB is configured in BWP-DownlinkDedicated, therefore, NCD-SSB is only valid when the active BWP is configured with NCD-SSB.

In some embodiments of the application, the specified SSB may optionally be specified by a protocol or configured by higher layer signaling.

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

In some embodiments of the application, optionally, the specified SSB is indicated by at least one of:

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

An index or Identification (ID) indicating a serving cell to which the specified SSB corresponds;

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

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

In the embodiment of the present invention, optionally, when the specified SSB is a CD-SSB under the condition of index or identification indication indicating the serving cell corresponding to the specified SSB, the specified SSB is a unique CD-SSB corresponding to the serving cell; when the specified SSB is an NCD-SSB, an index or an identification of the BWP corresponding to the specified SSB may be further indicated, for which purpose the unique NCD-SSB corresponding to the BWP.

In the embodiment of the present invention, optionally, in the case of indicating the index or the identifier of the serving cell corresponding to the specified SSB, the index in all SSBs or all CD-SSBs or all NCD-SSBs configured on the specified SSB for that serving cell may be further indicated.

In some embodiments of the application, optionally, the specified SSB satisfies at least one of:

configuring for a current serving cell;

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

takes effect in the current downstream BWP.

That is, any one of the specified SSBs (S) is configured for the current serving Cell (or P (S) Cell of the Cell group in which the current serving Cell is located when no SSB is configured for the current serving Cell), or is configured in the frequency domain of the current downlink BWP, or is in effect in the current DL BWP.

Alternatively, when any SSB is not specified, the first SSB may be determined using any one of SSB determination modes 1) to 12).

In the embodiment of the present application, after determining the first SSB, any time domain unit occupied by any determined first SSB may be regarded as a first SSB-associated time domain unit, where at least one of X (X > =1) time domain units before the first time domain unit occupied by the first SSB and Y (Y > =1) time domain units after the last time domain unit occupied by the first SSB is referred to as a first SSB time domain unit. Accordingly, within a certain first SSB time domain unit, there is at least one first SSB, which may be referred to hereinafter as the first SSB/s for which the first SSB time domain unit is/are associated.

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

SBFD mode 1:

In some embodiments of the present application, optionally, the determining SBFD related operations of the first SSB time domain unit by the terminal includes: the terminal determines that the first SSB time domain unit does not support SBFD operations if a first condition is satisfied.

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

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

In the case that the first condition is a first sub-condition, the first SSB time domain configured with the uplink sub-band is not SBFD time domain units. The terminal considers that the frequency domain resources in the first SSB time domain unit (in DL BWP) are all used for downlink. Since the configured uplink sub-band is not actually active, the frequency domain location of the uplink sub-band does not have any impact on the possible SSB reception. The uplink sub-band may not overlap in the frequency domain with any of the first SSBs associated with the first SSB time domain unit or may overlap with at least one of the first SSBs.

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

In the case that the first condition is the second sub-condition, it may also be understood that the time domain unit configured with the uplink sub-band is not allowed to overlap with the first SSB time domain unit. Typically, the time domain unit configured with the uplink sub-band defaults to SBFD time domain units.

In some embodiments of the present application, optionally, the determining, by the terminal, that the first SSB time domain unit does not support SBFD operations when the first condition is satisfied includes:

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

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

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

In the embodiment of the present application, when a first SSB time domain unit associates a plurality of first SSBs, if SSB periods corresponding to the plurality of first SSBs are identical, the "period of the first SSB associated with the first SSB time domain unit" is the identical SSB period; otherwise, the "period of the first SSB associated with the first SSB time domain unit" may be determined based on SSB periods corresponding to the plurality of first SSBs, for example, a maximum value, a least common multiple, or the like of the SSB periods corresponding to the plurality of first SSBs.

Optionally, the configuration period of the single SBFD is aligned with the start position of a single or N "periods of the first SSB associated with the first SSB time domain unit".

SBFD mode 2:

In some embodiments of the present application, optionally, the determining SBFD related operations of the first SSB time domain unit by the terminal includes: the terminal determines SBFD operations can be supported within the first SSB time domain unit.

That is, it can be appreciated that the terminal is allowed to perform SBFD operations within all or part of the time domain units within the first SSB time domain unit where the uplink sub-band is configured (or initiate uplink transmissions within the configured uplink sub-band).

In some embodiments of the present application, optionally, the determining by the terminal that SBFD operations can be supported in the first SSB time domain unit includes: the terminal determines a second SSB time domain unit supporting SBFD operations within the first SSB time domain unit.

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

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

it can be understood that, in the first SSB time domain unit, all time domain units configured with the uplink sub-band are SBFD time domain units by default.

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

2) SSB time domain unit range 2: the first SSB time domain unit is configured with a time domain unit of an uplink sub-band and meets a third condition, where the third condition includes at least one of the following:

the configured uplink sub-band is not overlapped with any first SSB associated with the first SSB time domain unit in the frequency domain;

The interval of any first SSB in the frequency domain, which is associated with the first SSB time domain unit, of the configured uplink sub-band is larger than or equal to a preset interval threshold; the preset interval threshold is used to suppress Cross link interference (Cross LINK INTERFERENCE, CLI) caused by SSB reception and uplink transmission, and the value of the interval threshold can be specified by a protocol or configured by high-layer signaling.

Any first SSB and Guard band (Guard band) associated with the first SSB time domain unit do not overlap in the frequency domain;

Any first SSB associated with the first SSB time domain unit is located in the frequency domain of the downlink sub-band (DL subband).

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

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

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

Alternatively, the semi-static configuration information may be sent either through cell-level common signaling (e.g., system information block 1 (SIB 1) or other system information) or through UE-specific signaling (e.g., radio resource control (Radio Resource Control, RRC message)).

Optionally, the semi-static configuration information may be configured uniformly based on granularity of UE, serving cell or BWP, or may be further configured separately based on granularity of time domain units.

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

In the embodiment of the present application, optionally, the 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, SSB time domain unit range 5.

Optionally, the dynamic indication information may be indicated by a medium access control unit (MEDIA ACCESS Control Control Element, MAC CE) or by downlink control information (Downlink Control Information, DCI). When indicated by DCI, the DCI may be either a UE-specific (dedicated) DCI (e.g., a UE-specific DCI that schedules or does not schedule data transmission) or a Group common (Group common) DCI (e.g., enhanced slot format indication (Slot Format Indication, SFI)).

5) SSB time domain unit range 5: the terminal implements a time domain unit supporting SBFD operations in the determined first SSB time domain unit based on itself.

The self-implementation means that the terminal itself decides.

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

In some embodiments of the present application, optionally, after the terminal itself implements the determined time domain unit supporting SBFD operations or the time domain unit not supporting SBFD operations in the first SSB time domain unit, a dynamic indication is made to the network side device. I.e. the method further comprises: in the case that the terminal determines, based on its implementation, a time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations, the terminal sends dynamic indication information to the network side device, where the dynamic indication information is used to notify the determined time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations.

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

It will be appreciated that when it is determined that a certain first SSB time domain unit configured with an uplink subband supports SBFD operations or is a SBFD time domain unit based on protocol specifications (e.g., SSB time domain unit range 1 or SSB time domain unit range 2 described above), semi-static configuration (e.g., SSB time domain unit range 3), or dynamic indication (e.g., SSB time domain unit range 4 or SSB time domain unit range 5), it may be understood that uplink transmissions are allowed or prioritized (including dynamically scheduled uplink transmissions; optionally including semi-static configuration uplink transmissions) within this first SSB time domain unit, otherwise when it is determined that this first SSB time domain unit does not support SBFD operations or is not SBFD symbols, it may be understood that SSB transmissions/reception/measurements are prioritized within this first SSB time domain unit, and uplink transmissions are not performed.

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

Supporting half duplex only case:

in some embodiments of the present application, optionally, the determining SBFD related operations of the first SSB time domain unit by the terminal includes: in the event that the terminal supports only half duplex SBFD operations within the second SSB time domain unit, the terminal determines a first SBFD operation supported by the second SSB time domain unit, the first SBFD operation comprising at least one of:

Rule 1: a dynamically scheduled Physical Uplink shared channel (Physical Uplink SHARED CHANNEL, PUSCH), a Physical Uplink control channel (Physical Uplink Control Channel, PUCCH), or a reference signal for channel Sounding (Sounding REFERENCE SIGNAL, SRS) transmission overlapping the second SSB time domain unit can be performed;

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

Rule 3: -dropping (drop) or delaying (postpone) semi-static configuration PUSCH, PUCCH, SRS or PRACH transmissions overlapping the second SSB time domain unit.

The following is mainly described for rule 1.

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

in the case of no dynamic coverage (Dynamic overriding) being applied, the terminal determines that the second SSB time domain unit is always a SBFD time domain unit, and expects that frequency domain resources occupied by the dynamically scheduled PUSCH, PUCCH, or SRS transmissions are all located within an uplink subband configured by the second SSB time domain unit;

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

In case dynamic coverage is applied, the terminal determines that the second SSB time domain unit is a downlink-only (DL-only) time domain unit and that there is no desire for the dynamic scheduling PUSCH, PUCCH or SRS transmission within the second SSB time domain unit;

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

Generally, the second SSB time domain unit cannot be dynamically covered as UL-only time domain unit to ensure that SSB transmissions still exist within this second SSB time domain unit from the UE's perspective.

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

The dynamic overlay here can be understood as: the uplink subbands semi-statically configured by higher layer signaling within the specified one or more SBFD time domain units are dynamically modified or enabled/disabled using L1/L2 signaling (e.g., DCI or MAC CE), or the one or more SBFD time domain units are dynamically converted to non-SBFD time domain units (e.g., DL-only time domain units or UL-only time domain units).

In this 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, the second SSB time domain unit is always used as 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 units; DL-only time domain unit.

In the embodiment of the present application, optionally, when the second SSB time domain unit is a Semi-static flexible (Semi-static flexible) time domain unit: when dynamic coverage is not applied, the second SSB time domain unit is always used as 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 units; a DL-only time domain unit; UL-only time domain unit.

It will be appreciated 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 the second SSB time domain unit is converted to a DL-only time domain unit based on dynamic coverage, the relevant receiving/measuring operation of the first SSB associated with the second SSB time domain unit is not affected.

When the dynamically scheduled PUSCH or PUCCH adopts a Repetition (Repetition) transmission mode, the terminal uses the first Repetition transmission as dynamically scheduled PUSCH or PUCCH transmission when performing first Repetition transmission, and performs transmission that overlaps the second SSB time domain unit and corresponds to the first Repetition transmission (i.e. applies rule 1 above);

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission manner, the terminal uses other repeated transmission as PUSCH or PUCCH transmission configured in a semi-static manner when the other repeated transmission is not the first repeated transmission, and performs transmission overlapping with the second SSB time domain unit and corresponding to the other repeated transmission (i.e. applies rule 2 above);

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission manner, the terminal uses the other repeated transmission as a PUSCH or PUCCH transmission configured in a semi-static manner when the other repeated transmission is not the first repeated transmission, and discards or delays a transmission overlapping the second SSB time domain unit and corresponding to the other repeated transmission (i.e., applies rule 3 above);

in the case that the dynamically scheduled PUSCH uses a mode that one transport block is sent (TB processing over multi-slot PUSCH, TBoMS) in multiple time slots, the terminal uses the transmission in the first available time slot as dynamically scheduled PUSCH transmission, and performs the transmission in the first available time slot overlapped with the second SSB time domain unit (i.e. applies rule 1 above);

in the case that the dynamically scheduled PUSCH adopts TBoMS mode, the terminal uses the transmission in other available time slots except the transmission in the first available time slot as the PUSCH transmission with semi-static configuration, and performs the transmission in the other available time slots overlapped with the second SSB time domain unit (i.e. applies rule 2 above);

In the case that the dynamically scheduled PUSCH uses TBoMS, the terminal uses the transmission in the other available time slots except the transmission in the first available time slot as the PUSCH transmission in the semi-static configuration, and discards or delays the transmission in the other available time slots overlapping the second SSB time domain unit (i.e. applies rule 3 above).

The above dynamically scheduled SRS may be understood as an aperiodic SRS transmission triggered by DCI format 0_1/1_1/2_3, and refers to each time domain unit occupied by each SRS resource (resource) in each triggered SRS resource set (resource set).

The following is mainly described for rule 2.

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

In some embodiments of the present application, optionally, where the first SBFD operation includes enabling semi-statically configured PUSCH, PUCCH, or SRS transmissions 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:

Under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be a SBFD time domain unit all the time, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are all located in an uplink subband configured by the second SSB time domain unit, the terminal executes the semi-static configuration PUSCH, PUCCH or SRS transmission (i.e. applies rule 2 above);

under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be a SBFD time domain unit all the time, and under the condition that frequency domain resources occupied by the semi-static configuration PUSCH, PUCCH or SRS are not all located in an uplink subband configured by the second SSB time domain unit, the terminal discards or delays the semi-static configuration PUSCH, PUCCH or SRS transmission (i.e. applies rule 3 above);

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

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

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

in case of applying dynamic coverage, the terminal determines the second SSB time domain unit to be an uplink-only time domain unit and performs the semi-statically configured PUSCH, PUCCH or SRS transmission (i.e. applies rule 2 above).

Typically, the second SSB time domain unit cannot be dynamically covered as UL-only time domain unit to ensure that SSB transmissions still exist within the second SSB time domain unit from the UE perspective.

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

The network side equipment can ensure that the frequency domain resources occupied by the semi-static configuration PUSCH/PUCCH/SRS are all located in an uplink sub-band, or any first SSB associated with the second SSB time domain unit is not overlapped in the frequency domain (or the interval of any first SSB associated with the second SSB time domain unit in the frequency domain is larger than or not smaller than a preset interval threshold);

When the frequency domain resources occupied by the semi-statically configured PUSCH/PUCCH/SRS are not all located in the uplink sub-band, or there is an overlap in the frequency domain of at least one first SSB associated with the second SSB time domain unit (or the interval between the at least one first SSB associated with the second SSB time domain unit in the frequency domain is smaller than the preset interval threshold), the UE discards or delays the corresponding transmission (i.e. the UE cannot perform the corresponding reception/measurement by using the SSB transmission in the second SSB time domain unit, but needs to consider the collision situation of the SSB transmission in the second SSB time domain unit when performing the uplink transmission).

For semi-statically configured PRACH transmissions:

in some embodiments of the application, optionally, where the first SBFD operation includes being capable of performing semi-statically configured PRACH transmissions overlapping 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:

Under the condition that dynamic coverage is not applied, the terminal determines the second SSB time domain unit to be taken as SBFD time domain unit all the time, and under the condition that a first PRACH opportunity overlapped with the second SSB time domain unit exists in the PRACH opportunity checking (occasion validation) process and frequency domain resources occupied by the first PRACH opportunity are all located in an uplink sub-band configured by the second SSB time domain unit, the terminal judges the first PRACH opportunity to be possible to be effective;

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

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

In the case of applying dynamic coverage, the terminal determines that the second SSB time domain unit is a time domain unit only for downlink, in order to avoid affecting mapping (mapping) of PRACH occasions (RO) to SSBs, when the PRACH occasions are checked, the corresponding operation is still performed along with the case of applying no dynamic coverage, but when there is a first PRACH occasion overlapping the second SSB time domain unit in the process of checking the PRACH occasions, and when all frequency domain resources occupied by the first PRACH occasion are located in an uplink subband configured by the second SSB time domain unit, the terminal determines that the first PRACH occasion is possible to be valid, but does not allow the first PRACH occasion to be selected to initiate PRACH transmission.

The above-mentioned determination of the first PRACH timing as being possibly valid means that the above-mentioned condition may be only a partial condition for determining that the first PRACH timing is valid, and other conditions may also need to be satisfied, and the first PRACH timing is determined to be valid when all the conditions are satisfied.

The following is mainly described for rule 3.

In some embodiments of the application, optionally, where the first SBFD operation includes dropping or delaying semi-static configuration PUSCH, PUCCH, SRS or PRACH transmissions that overlap with the second SSB time domain unit, the terminal determines that the first SBFD operation supported by the second SSB time domain unit includes at least one of:

In case the semi-static configuration PUSCH employs a repeat transmission type A (PUSCH repetition Type A) and there is a repeat transmission overlapping the second SSB time domain unit and a configuration start available slot count (Available Slot Counting), the terminal delays the repeat transmission;

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

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

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

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

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

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

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

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

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

For example, when tdd-UL-DL-ConfigurationCommon is provided to the UE, a certain PRACH occasion within a certain PRACH slot (slot) is judged to be likely valid when any of the following is satisfied:

the PRACH opportunity is entirely located in the uplink sub-band;

The PRACH occasion is not located before the second SSB time domain unit in the PRACH slot, and the start position and the last second SSB time domain unit are separated by at least N _gap time domain units, where N _gap may be specified by a protocol or configured by higher layer signaling.

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

Optionally, the Semi-persistent configuration PUCCH includes a PUCCH for carrying Semi-persistent scheduling (Semi-PERSISTENT SCHEDULING, SPS) hybrid automatic repeat request acknowledgement (Hybrid automatic repeat request acknowledgement, HARQ-ACK), periodic or Semi-persistent channel state information (P/SP-CSI), and scheduling request (Scheduling Request, SR). Here, SPS HARQ-ACK may be understood as HARQ-ACK for SPS PDSCH.

Optionally, in a case where the semi-static configuration PUCCH transmission overlaps with the second SSB time domain unit, the delaying, by the terminal, the semi-static configuration PUCCH transmission includes:

for PUCCHs used to carry SPS HARQ-ACKs, P/SP-CSI, SRs, whether or not Repetition (Repetition) transmissions are configured, a delay is incurred when a certain Repetition (which may be considered to contain only a single Repetition when no Repetition transmission is configured) overlaps with this second SSB time-domain unit.

For PUCCH carrying DG HARQ-ACK, when configuration employs repetition transmission, for any of the other repetitions other than the first repetition, this repetition is delayed when overlapping with this second SSB symbol. In the embodiment of the present application, optionally, the rules actually applied by the terminal (rule 1, rule 2 and rule 3) are specified by the protocol or configured by the higher layer signaling.

Full duplex enabled case:

in some embodiments of the present application, optionally, the SBFD-related operations of the terminal to determine the first SSB time domain unit include at least one of:

option 1: in the case that 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;

Generally, in this second SSB time domain unit, the uplink transmission in the uplink sub-band does not have a serious impact (or impact within a controllable range) on the possible SSB reception, and the UE is allowed to perform uplink transmission in the uplink sub-band configured by the second SSB time domain unit (in this case, the UE may perform SSB reception/measurement in the second SSB time domain unit at the same time, and other possible downlink reception).

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

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

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

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

Alternatively, for the UE supporting the full duplex SBFD operation, to ensure the SSB receiving/measuring performance, only the half duplex SBFD operation may be supported in the second SSB time domain unit, where the UE performs the operation corresponding to only the half duplex SBFD (i.e. option 2) and only the half duplex SBFD operation is described in the above embodiments, and will not be repeated here.

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

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

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

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

In the embodiment of the application, corresponding solutions are introduced for each link of performing SBFD related operations in the SSB time slot unit, so that performances of SSB receiving/detecting, uplink transmission of SBFD and the like can be balanced and ensured, and the flexibility of system operation is improved.

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

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

The network side equipment determines at least one first SSB;

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

a time domain unit occupied by the first SSB;

SSB configured for the current serving cell; the current serving cell is a single serving cell corresponding to a carrier in which the flexible duplex mode is deployed.

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

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

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

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

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

SSB configured in a frequency domain range of a current downlink BWP; the current downlink BWP is the active downlink BWP (Active DL BWP) on the current serving cell.

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

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

SSBs that take effect within the current downstream BWP;

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

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

A specified SSB.

In some embodiments of the application, optionally, the method further comprises: the network side equipment sends first indication information to the terminal, wherein the first indication information comprises the appointed SSB.

In some embodiments of the present application, optionally, the network side device indicates the specified SSB by at least one of:

indicating an absolute frequency point of the specified SSB;

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

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

In the 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 may refer to the manner in which the terminal determines the SBFD related operations of the first SSB time domain unit.

In some embodiments of the application, optionally, the method further comprises: the network side equipment sends second indication information to a terminal, wherein the second indication information is used for indicating a time domain unit capable of supporting SBFD operation or a time domain unit not supporting SBFD operation in the first SSB time domain unit; the second indication information is sent through semi-static configuration information or dynamic indication information;

In some embodiments of the application, optionally, the method further comprises: the network side equipment receives third indication information sent by a terminal, wherein the second indication information is used for indicating a time domain unit supporting SBFD operation or a time domain unit not supporting SBFD operation in the first SSB time domain unit which is determined based on the terminal, and the third indication information is sent through dynamic indication information.

The implementation method of the flexible duplex provided by the embodiment of the application can be implemented by the implementation main body as a device for realizing the flexible duplex. In the embodiment of the application, the implementation method of the flexible duplex implemented by the implementation device of the flexible duplex is taken as an example, and the implementation device of the flexible duplex provided by the embodiment of the application is described.

Referring to fig. 5, an embodiment of the present application further provides a device 50 for implementing flexible duplex, including:

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

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

In an embodiment of the present application, optionally, the first determining module 51 is configured to determine at least one first SSB; determining the first SSB time domain unit according to the at least one first SSB, wherein the first SSB time domain unit comprises at least one of the following:

a time domain unit occupied by the first SSB;

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

SSB configured for the current serving cell;

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

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

SSBs that take effect within the current downstream BWP;

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

A specified SSB.

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

Cell definition SSB;

the non-cell defines SSB.

In an embodiment of the present application, optionally, the validated SSB includes at least one of:

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

In an embodiment of the present application, optionally, the specified SSB is indicated by at least one of the following means:

indicating an absolute frequency point of the specified SSB;

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

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

configuring for a current serving cell;

takes effect in the current downstream BWP.

In this embodiment of the present application, optionally, the second determining module 52 is configured to determine that the first SSB time domain unit does not support SBFD operations when the first condition is satisfied.

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

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

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

In this embodiment of the present application, optionally, the determining, by the terminal, that the first SSB time domain unit does not support SBFD operations when the first condition is satisfied includes:

In the embodiment of the present application, optionally, the second determining module 52 is configured to determine that SBFD operations can be supported in the first SSB time domain unit.

In an embodiment of the present application, optionally, the determining that SBFD operations can be supported in the first SSB time domain unit includes: a second SSB time domain unit supporting SBFD operations within the first SSB time domain unit is determined.

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

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

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

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

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

The terminal realizes the time domain unit supporting SBFD operation in the determined first SSB time domain unit based on the terminal.

In an embodiment of the present application, optionally, the apparatus 50 for implementing flexible duplex further includes: a sending module, configured to send, when the terminal determines, based on its implementation, that a time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations, dynamic indication information to a network side device, where the dynamic indication information is used to notify, to the network side device, the determined time domain unit supporting SBFD operations in the first SSB time domain unit, or a time domain unit not supporting SBFD operations.

In this embodiment of the present application, optionally, the SBFD related operations for determining the first SSB time domain unit include:

in the case that the terminal supports only half duplex SBFD operations within the second SSB time domain unit, determining a first SBFD operation supported by the second SSB time domain unit, the first SBFD operation including at least one of:

In the case that the terminal supports full duplex SBFD operation within the second SSB time domain unit, determining that uplink transmission can be performed within 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, the first SBFD operation including at least one of:

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

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

Under the condition of applying dynamic coverage, determining the second SSB time domain unit as SBFD time domain units, wherein the frequency domain resources occupied by the dynamic scheduling PUSCH, PUCCH or SRS transmission are expected to be located in an uplink sub-band configured by the second SSB time domain unit;

In the case of applying dynamic coverage, determining the second SSB time domain unit as a downlink-only time domain unit, and not expecting the dynamic scheduling PUSCH, PUCCH, or SRS transmissions to exist within the second SSB time domain unit;

in case of applying dynamic coverage, the second SSB time domain unit is determined to be an uplink-only time domain unit and the dynamically scheduled PUSCH, PUCCH or SRS transmission is performed.

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission mode, the first repeated transmission is used as the dynamically scheduled PUSCH or PUCCH transmission in the first repeated transmission, and the transmission overlapping the second SSB time domain unit and corresponding to the first repeated transmission is performed;

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

When the dynamically scheduled PUSCH or PUCCH adopts a repeated transmission manner, when other repeated transmissions except for the first repeated transmission are used, the other repeated transmissions are used as semi-statically configured PUSCH or PUCCH transmissions, and the transmissions which overlap with the second SSB time domain unit and correspond to the other repeated transmissions are discarded or delayed;

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

in the case that the dynamically scheduled PUSCH adopts TBoMS mode, taking the transmission in other available time slots except the transmission in the first available time slot as the semi-statically configured PUSCH transmission, and executing the transmission in the other available time slots overlapped with the second SSB time domain unit;

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

In the embodiment of the present application, optionally, the first SBFD operations include enabling to perform semi-static configuration PUSCH, PUCCH or SRS transmission overlapping with the second SSB time domain unit; the determining that the second SSB time domain unit supports the first SBFD operations includes at least one of:

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

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

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

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

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

In case of applying dynamic coverage, the second SSB time domain unit is determined to be an uplink-only time domain unit, and the semi-statically configuring PUSCH, PUCCH, or SRS transmission is performed.

In an embodiment of the present application, optionally, the first SBFD operations include enabling semi-static configuration PRACH transmission overlapping with the second SSB time domain unit to be performed; the determining that the second SSB time domain unit supports the first SBFD operations includes at least one of:

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

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

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

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

In an embodiment of the present application, optionally, the first SBFD operation includes discarding or delaying a semi-static configuration PUSCH, PUCCH, SRS or PRACH transmission overlapping the second SSB time domain unit; the determining that the second SSB time domain unit supports the first SBFD operations includes at least one of:

Delaying the repeated transmission when the semi-static configuration PUSCH adopts the repeated transmission type a, the repeated transmission overlapped with the second SSB time domain unit exists, and the configuration starts the available time slot count;

Discarding the repeated transmission when the semi-statically configured PUSCH adopts a repeated transmission type a, and there is a repeated transmission overlapping with the second SSB time domain unit, and the available time slot count is not configured to be started;

Delaying the transmission or discarding any TBoMS in the case that the semi-static configuration PUSCH adopts TBoMS mode and there is a transmission overlapping with the second SSB time domain unit in any TBoMS;

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

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

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

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

discarding the semi-statically configured SRS transmission if the semi-statically configured SRS transmission overlaps the second SSB time domain unit;

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

The device for implementing flexible duplex in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, the terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the present application are not limited in detail.

The device for implementing flexible duplex provided by the embodiment of the application can implement each process implemented by the method embodiment of fig. 3 and achieve the same technical effects, and in order to avoid repetition, the description is omitted here.

Referring to fig. 6, an embodiment of the present application further provides a device 60 for implementing flexible duplex, including:

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

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

a time domain unit occupied by the first SSB;

SSB configured for the current serving cell;

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

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

SSBs that take effect within the current downstream BWP;

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

A specified SSB.

In an embodiment of the present application, optionally, the apparatus 60 for implementing flexible duplex further includes: the first sending module is used for sending first indication information to the terminal, wherein the first indication information comprises the appointed SSB.

In an embodiment of the present application, optionally, the first sending module indicates the specified SSB by at least one of the following manners:

indicating an absolute frequency point of the specified SSB;

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

In an embodiment of the present application, optionally, the apparatus 60 for implementing flexible duplex further includes: a second sending module, configured to send second indication information to a terminal, where the second indication information is used to indicate a time domain unit capable of supporting SBFD operations or a time domain unit not supporting SBFD operations in the first SSB time domain unit; the second indication information is sent through semi-static configuration information or dynamic indication information;

Or alternatively

The receiving module is configured to receive third indication information sent by a terminal, where the second indication information is used to indicate a time domain unit supporting SBFD operations or a time domain unit not supporting SBFD operations in the first SSB time domain unit determined by the terminal based on self implementation, and the third indication information is sent through dynamic indication information.

The device for implementing flexible duplex in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip.

The device for implementing flexible duplex provided by the embodiment of the application can implement each process implemented by the method embodiment of fig. 4 and achieve the same technical effects, and in order to avoid repetition, the description is omitted here.

As shown in fig. 7, the embodiment of the present application further provides a communication device 70, including a processor 71 and a memory 72, where the memory 72 stores a program or an instruction that can be executed on the processor 71, for example, when the communication device 70 is a terminal, the program or the instruction is executed by the processor 71 to implement the steps of the embodiment of the method for implementing flexible duplex executed on the terminal side, and the same technical effects can be achieved. When the communication device 70 is a network side device, the program or the instruction, when executed by the processor 71, implements the steps of the method embodiment for implementing flexible duplex executed by the network side device, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the steps in the embodiment of the method shown in fig. 3. The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 8 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 80 includes, but is not limited to: at least some of the components of the radio frequency unit 81, the network module 82, the audio output unit 83, the input unit 84, the sensor 85, the display unit 86, the user input unit 87, the interface unit 88, the memory 89, and the processor 810.

Those skilled in the art will appreciate that the terminal 80 may also include a power source (e.g., a battery) for powering the various components, which may be logically connected to the processor x 10 by a power management system to perform functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 8 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 84 may include a graphics processing unit (Graphics Processing Unit, GPU) 841 and a microphone 842, with the graphics processor 841 processing image data of still pictures or video obtained by an image capture device (e.g., 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, or the like. The user input unit 87 includes at least one of a touch panel 871 and 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 (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving the downlink data from the network side device, the radio frequency unit 81 may transmit the downlink data to the processor 810 for processing; in addition, the radio frequency unit 81 may send uplink data to the network side device. Typically, 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, and the like.

The memory 89 may be used to store software programs or instructions as well as various data. The memory 89 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 89 may include volatile memory or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDRSDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCH LINK DRAM, SLDRAM), and Direct random access memory (DRRAM). Memory 89 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, etc., and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 810.

Wherein the processor 810 is configured to determine a first SSB time domain unit by the terminal; SBFD-related operations of the first SSB time domain unit are determined.

It can be understood that, the implementation process of each implementation manner mentioned in this embodiment may refer to the related description of the method embodiment executed by the terminal side and achieve the same or corresponding technical effects, which are not repeated herein.

The embodiment of the application also provides network side equipment, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the steps of the method embodiment shown in fig. 4. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 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. The antenna 91 is connected to a radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information via the antenna 91, and transmits the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes information to be transmitted, and transmits the processed information to the radio frequency device 92, and the radio frequency device 92 processes the received information and transmits the processed information through the antenna 91.

The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 93, and the baseband apparatus 93 includes a baseband processor.

The baseband device 93 may, for example, comprise at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 9, where one chip, for example, a baseband processor, is connected to the memory 95 through a bus interface, so as to invoke a program in the memory 95 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 96, such as a common public radio interface (Common Public Radio Interface, CPRI).

Specifically, the network side device 900 of the embodiment of the present application further includes: instructions or programs stored in the memory 95 and executable on the processor 94, the processor 94 invokes the instructions or programs in the memory 95 to perform the methods performed by the modules shown in fig. 6 and achieve the same technical effects, and are not repeated here.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above-mentioned embodiment of the method for implementing flexible duplex, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

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

The embodiment of the application further provides a chip, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the processes of the embodiment of the implementation method of the flexible duplex, and the same technical effects can be achieved, so that repetition is avoided, and the description is omitted here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the above-mentioned embodiment of the method for implementing flexible duplex, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated here.

The embodiment of the application also provides a wireless communication system, which comprises: the terminal can be used for executing the steps of the method for realizing the flexible duplex executed by the terminal side, and the network side equipment can be used for executing the steps of the method for realizing the flexible duplex executed by the network side equipment.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the description of the embodiments above, it will be apparent to those skilled in the art that the above-described example methods may be implemented by means of a computer software product plus a necessary general purpose hardware platform, but may also be implemented by hardware. The computer software product is stored on a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes instructions for causing a terminal or network side device to perform the methods according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms of embodiments may be made by those of ordinary skill in the art without departing from the spirit of the application and the scope of the claims, which fall within the protection of the present application.

Claims

1. A method for implementing flexible duplexing, comprising:

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

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

the terminal determines at least one first SSB;

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

a time domain unit occupied by the first SSB;

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

SSB configured for the current serving cell;

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

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

SSBs that take effect within the current downstream BWP;

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

A specified SSB.

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

Cell definition SSB;

the non-cell defines SSB.

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

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

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

indicating an absolute frequency point of the specified SSB;

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

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

configuring for a current serving cell;

takes effect in the current downstream BWP.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

22. A method for implementing flexible duplexing, comprising:

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

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

The network side equipment determines at least one first SSB;

a time domain unit occupied by the first SSB;

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

SSB configured for the current serving cell;

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

SSBs that take effect within the current downstream BWP;

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

A specified SSB.

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

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

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

indicating an absolute frequency point of the specified SSB;

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

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

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

Or alternatively

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

28. An apparatus for implementing flexible duplexing, comprising:

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

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