Methods, apparatus, equipment and storage media for determining duplex mode

Abstract

This application discloses a method, apparatus, device, and storage medium for determining duplex mode, belonging to the field of wireless communication technology. The method includes: a first device determining the target duplex mode of a UE within a SBFD time domain unit according to predefined rules and / or a duplex mode indicated by a second device; when the target duplex mode is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at the same time; when the target duplex mode is SBFD duplex mode two, the UE can perform both uplink and downlink transmission on the SBFD time domain unit at the same time; the first device performs channel and / or signal transmission and reception on the SBFD time domain unit according to the target duplex mode. This method enables the network-side device and the UE to determine and understand the target duplex mode used by the UE within the SBFD time domain unit when the UE simultaneously supports SBFD duplex mode one and SBFD duplex mode two.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, and specifically relates to a method, apparatus, device and storage medium for determining duplex mode. Background Technology

[0002] Sub-band non-overlapping full duplex (SBFD) technology, also known as sub-band full duplex, allows base stations to transmit and receive simultaneously on different sub-bands within the same spectrum. This technology combines the advantages of time-division duplex (TDD) and frequency-division duplex (FDD), providing more flexible duplexing while reducing uplink latency and improving uplink coverage performance.

[0003] For a serving cell or band width part (BWP) with SBFD enabled, when a terminal simultaneously supports duplex mode 1 and duplex mode 2, both the terminal and the base station need to determine the specific duplex mode used within the SBFD time domain unit and ensure mutual understanding between both sides to guarantee normal SBFD operation and performance. However, there is currently a lack of practically feasible solutions for determining the specific duplex mode used within the SBFD time domain unit, thus affecting SBFD deployment and configuration. Duplex mode 1 is a half-duplex mode, where the terminal can only perform uplink or downlink transmissions at any given time; both cannot occur simultaneously. Duplex mode 2 is a full-duplex mode, where the terminal can simultaneously perform uplink and downlink transmissions in different frequency subbands at any given time. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for determining duplex mode. When a terminal simultaneously supports SBFD duplex mode one and SBFD duplex mode two, it can determine the target duplex mode of the terminal within the SBFD time domain unit and ensure that both sides understand it in the same way.

[0005] In a first aspect, a method for determining a duplex mode is provided, executed by a first device. The method includes: determining a target duplex mode of a terminal within a SBFD time-domain unit; and, based on the target duplex mode, performing channel and / or signal transmission and reception within the SBFD time-domain unit. The method for determining the target duplex mode includes at least one of the following:

[0006] The target duplex mode is determined according to predefined rules;

[0007] The target duplex mode is determined according to the duplex mode indicated by the second device;

[0008] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0009] Secondly, a method for determining a duplex mode is provided, executed by a second device, the method comprising: sending first indication information to a first device, the first indication information being used to indicate the target duplex mode used by the terminal in the SBFD time domain unit;

[0010] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0011] Thirdly, a device for determining a duplex mode is provided, the device comprising:

[0012] The processing module is used to determine the target duplex mode of the terminal within the SBFD time domain unit;

[0013] A transceiver module is used to perform channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode;

[0014] The method for determining the target duplex mode includes at least one of the following:

[0015] The target duplex mode is determined according to predefined rules;

[0016] The target duplex mode is determined according to the duplex mode indicated by the second device;

[0017] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0018] Fourthly, a device for determining a duplex mode is provided, the device comprising:

[0019] The sending module is used to send first indication information to the first device, wherein the first indication information is used to indicate the target duplex mode used by the terminal in the SBFD time domain unit;

[0020] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0021] Fifthly, a duplex mode determination apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0022] In a sixth aspect, a first device is provided, the first device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0023] In a seventh aspect, a first device is provided, including a processor and a communication interface, wherein the processor is configured to determine a target duplex mode of a terminal within an SBFD time domain unit; the communication interface is configured to perform channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode; wherein the determination of the target duplex mode includes at least one of the following: determining the target duplex mode according to a predefined rule; determining the target duplex mode according to a duplex mode indicated by a second device; wherein the target duplex mode includes SBFD duplex mode one or SBFD duplex mode two, when the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time, and when the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0024] In an eighth aspect, a second device is provided, the second device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0025] In a ninth aspect, a second device is provided, including a processor and a communication interface, wherein the processor is used to run programs or instructions to implement corresponding functions, and the communication interface is used to send first indication information to a first device, the first indication information being used to indicate a target duplex mode used by a terminal in an SBFD time domain unit; wherein the target duplex mode includes SBFD duplex mode one or SBFD duplex mode two, when the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time, and when the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0026] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0027] Eleventhly, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device is configured to perform the steps of the method as described in the first aspect, and the second device is configured to perform the steps of the method as described in the second aspect.

[0028] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0029] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the method for determining a duplex mode as described in the first or second aspect.

[0030] In this embodiment, the first device determines the target duplex mode of the UE within the SBFD time domain unit according to predefined rules and / or the duplex mode indicated by the second device. When the target duplex mode is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the UE can perform both uplink and downlink transmission on the SBFD time domain unit at the same time. The first device performs channel and / or signal transmission and reception on the SBFD time domain unit according to the target duplex mode. This method enables the network-side device and the UE to determine and understand the target duplex mode used by the UE in the SBFD time domain unit when the UE simultaneously supports SBFD duplex mode one and SBFD duplex mode two. This ensures that SBFD operation can be accurately and consistently executed synchronously on both sides, reliably realizing the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage. Attached Figure Description

[0031] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied;

[0032] Figure 2 This is a schematic diagram of a flexible duplex mode;

[0033] Figure 3 This is a schematic diagram of the frequency domain pattern corresponding to various time domain unit types;

[0034] Figure 4 This is a flowchart of a method for determining a duplex mode provided in Embodiment 1 of this application;

[0035] Figure 5 This is a flowchart of a method for determining a duplex mode provided in Embodiment 2 of this application;

[0036] Figure 6 This is a signaling flowchart of a method for determining a duplex mode provided in Embodiment 3 of this application;

[0037] Figure 7 This is a signaling flowchart of a method for determining a duplex mode provided in Embodiment 4 of this application;

[0038] Figure 8 This is a signaling flowchart of a method for determining a duplex mode provided in Embodiment 5 of this application;

[0039] Figure 9 This is a schematic diagram of the structure of a duplex mode determination device provided in an embodiment of this application;

[0040] Figure 10This is a schematic diagram of the structure of a duplex mode determination device provided in an embodiment of this application;

[0041] Figure 11 This is a schematic block diagram of a communication device provided according to an embodiment of this application;

[0042] Figure 12 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application;

[0043] Figure 13 This is a schematic block diagram of a network-side device provided according to an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0045] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0046] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

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

[0048] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0049] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0050] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0051] When deploying traditional cellular networks, data transmission and reception are performed using either Frequency Division Duplex (FDD) or Time Division Duplex (TDD) methods, based on available spectrum and service characteristics. FDD uses two symmetrical spectrums for transmission and reception, isolated by a guard band; uplink and downlink transmissions can occur simultaneously without interference. TDD, on the other hand, can transmit and receive on the same spectrum using different time-domain resources, but uplink and downlink transmissions cannot occur simultaneously; a switching interval is required between uplink and downlink.

[0052] Both duplex modes have their advantages and disadvantages. FDD has low spectrum utilization when uplink and downlink traffic is asymmetrical. TDD does not require symmetrical spectrum resources and can flexibly set the ratio of uplink and downlink resources to adapt to asymmetrical service needs. However, uplink and downlink switching will bring additional transmission waiting latency, and the discontinuity of uplink resources in the time domain will also cause uplink coverage to be limited.

[0053] Subband Full Duplex (SBFD), also known as non-overlapping Subband Full Duplex, allows base stations to transmit and receive simultaneously on different subbands within the same spectrum. It combines the advantages of TDD and FDD, does not require symmetrical spectrum resources, and can reduce transmission latency and improve uplink coverage performance.

[0054] For SBFD, the network side supports full-duplex, allowing uplink and downlink transmissions to occur simultaneously in different frequency subbands. To avoid interference between uplink and downlink, a certain guard band can be reserved between the frequency subbands corresponding to different transmission directions (e.g., uplink and downlink subbands).

[0055] For SBFD, the UE side supports half-duplex or full-duplex. When the UE supports half-duplex, it can only perform uplink or downlink transmissions at any given time; the two cannot occur simultaneously. This cell duplex mode can also be called Duplex mode 1, gNB SBFD mode, SBFD duplex mode one, or half-duplex SBFD mode. Understandably, in this case, uplink and downlink transmissions on the network side can only be performed for different UEs at any given time.

[0056] When the UE supports full-duplex, similar to the network side supporting full-duplex, the UE's uplink and downlink transmissions can occur simultaneously in different frequency subbands. This cell duplex mode can also be called Duplex mode 2, UE SBFD mode, SBFD duplex mode two, or full-duplex SBFD mode.

[0057] Figure 2 This is a schematic diagram of a flexible duplex mode, such as... Figure 2 As shown, the network side semi-statically divides the frequency domain of a single carrier into three sub-bands within a portion of the downlink symbols. The sub-bands on both sides of the carrier are downlink sub-bands, and the central sub-band is the uplink sub-band, in order to reduce interference to adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception, respectively.

[0058] The time-domain units (or the granularity of time-domain units) used for duplex scheduling between the network side and the UE side can be symbols, slots, sub-slots, sub-frames, frames, etc. Taking symbols as an example, the time-domain unit type can be divided in the following ways:

[0059] Method 1: Based on the TDD pattern configuration information provided by the network-side device to the UE, the symbol is divided into the following symbol types from the perspective of link direction:

[0060] Down Link (DL) symbol;

[0061] Up Link (UL) Symbol;

[0062] Flexible symbol.

[0063] DL symbols are generally used only for downlink transmission, UL symbols are generally used only for uplink transmission, and flexible symbols can be used for either uplink or downlink transmission as needed.

[0064] TDD pattern configuration information, for example, provides tdd-UL-DL-ConfigurationCommon (general configuration) and / or tdd-UL-DL-ConfigurationDedicated (dedicated configuration) for a specific serving cell of the UE. When tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated are not provided for a specific serving cell, each symbol can be considered a flexible symbol, or the operation rules corresponding to the flexible symbol can be followed.

[0065] Method 2: Based on the SBFD configuration information provided by the network-side equipment to the UE, the symbols are divided into SBFD symbols and non-SBFD symbols from the perspective of whether SBFD is applied.

[0066] Network-side devices can configure certain symbols to perform SBFD operations using SBFD configuration information, effectively designating these symbols as SBFD symbols. For example, some or all symbols within a single period determined by the TDD pattern can be configured as SBFD symbols. These symbols configured as SBFD symbols can be some or all of the time-domain unit types distinguished from the link direction; for example, only DL symbols and / or Flexible symbols can be configured as SBFD symbols.

[0067] Any symbol that is not configured (or instructed) to perform an SBFD operation can be considered a non-SBFD symbol.

[0068] Method 3: For a certain Serving cell configured or activated for the UE, the SBFD symbol on the Serving cell can be further divided from the perspective of duplex mode into: SBFD duplex mode 1 and SBFD duplex mode 2.

[0069] For SBFD symbol for duplex mode 1, network-side equipment supports full-duplex SBFD operation; UE only supports half-duplex SBFD operation, or in other words, within a single SBFD symbol, the UE can only perform uplink transmission or downlink reception, and cannot simultaneously perform uplink transmission and downlink reception based on Frequency Division Multiplexing (FDM).

[0070] The SBFD symbol for duplex mode 1 can support one or more frequency domain patterns, which are used to indicate the frequency domain location of the SBFD symbol's uplink subband (UL subband), downlink subband (DL subband), or guard band.

[0071] The frequency domain pattern corresponding to the SBFD symbol for duplex mode 1 is referenced. Figure 3 As shown, Figure 3 This is a schematic diagram of the frequency domain pattern corresponding to various time domain unit types. Assuming the frequency domain pattern adopts the DUD mode, the frequency domain pattern will explicitly indicate the frequency domain position of each UL subband, DL subband, and Guardband, including the frequency domain start / end position and frequency domain width. Optionally, the frequency domain start / end position and frequency domain width can be represented as the Physical Resource Block (PRB) number and the number of PRBs based on the reference subcarrier spacing (SCS), or as integer or floating-point values ​​based on predefined units ([M]Hz, etc.).

[0072] For SBFD symbol for duplex mode 2, network-side equipment supports full-duplex SBFD operation; UE can support full-duplex SBFD operation, or in other words, within a single SBFD time-domain unit, the UE can simultaneously perform FDM-based uplink transmission and downlink reception. It is understandable that, generally, a UE supporting full-duplex SBFD operation (i.e., supporting Duplex mode 2, or supporting SBFD symbol for duplex mode 2) will also necessarily support half-duplex SBFD operation (i.e., supporting Duplex mode 1, or supporting SBFD symbol for duplex mode 1).

[0073] The frequency domain pattern corresponding to SBFD duplex mode 2 is referenced. Figure 3 As shown. Generally, considering the greater limitations of UE in achieving antenna / spatial isolation compared to network-side equipment, better frequency domain isolation performance may be required to achieve similar self-interference suppression performance as network-side equipment. Therefore, the UL subband, DL subband, and Guardband need to be set wider. Accordingly, in Figure 3 In this mode, the Guardband for Duplex mode 2 is wider than that for Duplex mode 1, while the UL / DL subband is narrower.

[0074] For a serving cell or BWP that has SBFD enabled, when the UE supports both SBFD duplex mode 1 and SBFD duplex mode 2, the UE can only work in one of the duplex modes at any given time for the SBFD time domain unit. Therefore, it is necessary to determine the duplex mode of the SBFD time domain unit. There is currently no feasible solution for how the UE and the network-side equipment can determine the duplex mode of the SBFD time domain unit.

[0075] This application provides a method for determining the duplex mode. When the UE simultaneously supports both SBFD duplex mode one and SBFD duplex mode two, the UE and the network-side device can determine the duplex mode of the SBFD time domain unit, and both sides have a consistent understanding. It is understood that for a given SBFD time domain unit, both the UE and the network-side device need to determine the duplex mode of that SBFD time domain unit, and the two perform signal or channel transmission and reception based on the determined and consistent duplex mode.

[0076] The method for determining the duplex mode provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios. The following embodiments can be combined with each other, and the same or similar concepts and processes may not be described again in some embodiments.

[0077] Example 1

[0078] Figure 4 This is a flowchart of a method for determining a duplex mode according to Embodiment 1 of this application. The method is applied to a first device, which can be a UE or a network-side device. Figure 4 As shown, the method provided in this embodiment includes the following steps.

[0079] S101. The first device determines the target duplex mode of the UE in the SBFD time domain unit, wherein the method of determining the target duplex mode includes at least one of the following: determining the target duplex mode according to a predefined rule; determining the target duplex mode according to the duplex mode indicated by the second device; wherein the target duplex mode includes SBFD duplex mode one or SBFD duplex mode two.

[0080] When the target duplex mode is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the UE can perform uplink and downlink transmission on the SBFD time domain unit at the same time.

[0081] In this embodiment, the UE supports SBFD duplex mode one (i.e., gNB SBFD mode) and SBFD duplex mode two (i.e., UESBFD mode).

[0082] When the target duplex mode is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the UE can perform uplink and downlink transmission on the SBFD time domain unit at the same time.

[0083] In this embodiment, the first device determines the target duplex mode of the UE in the SBFD time domain unit by any one of the following two methods:

[0084] Method 1: Determine the target duplex mode of the UE in the SBFD time domain unit according to predefined rules.

[0085] Method 2: Determine the target duplex mode of the UE in the SBFD time domain unit based on the duplex mode indicated by the second device.

[0086] When the first device is a UE, the second device is a network-side device; that is, the UE determines the duplex mode of the SBFD time-domain element according to the duplex mode indicated by the network-side device.

[0087] In some implementations of Method 1, the first device determines the target duplex mode based on the transmission configured and / or indicated within the SBFD time-domain unit. This transmission includes uplink and / or downlink transmissions; this implementation will be referred to as Rule 1 below.

[0088] In this embodiment, the configured uplink (or downlink) transmission mainly refers to uplink (or downlink) transmissions that are semi-statically configured by higher-layer signaling, and may also include uplink (or downlink) transmissions agreed upon or specified by protocols. Indicated uplink (or downlink) transmissions refer to uplink (or downlink) transmissions that require dynamic scheduling or indication, generally using Layer 1 signaling (e.g., DCI) or Layer 2 signaling (e.g., MAC CE) for dynamic scheduling or indication.

[0089] Optionally, the configured uplink transmission may include at least one of the following:

[0090] Configured Grant (CG) Physical Uplink Shared Channel (PUSCH) Type 1;

[0091] CG PUSCH Type 2 (excluding the first CG PUSCH corresponding to the activation of DCI or the CG PUSCH transmitted within the first CG PUSCH occasion);

[0092] Periodic Physical Uplink Control Channel (PUCCH);

[0093] Semi-persistent PUCCH;

[0094] Periodic sounding reference signal (SRS);

[0095] Semi-persistent SRS.

[0096] Optionally, the configured uplink transmission may also include RO.

[0097] Optionally, the indicated uplink transmission may include at least one of the following:

[0098] Dynamically scheduled PUSCH;

[0099] CG PUSCH Type 2 (The first CG PUSCH corresponding to the activation DCI or the CG PUSCH transmitted within the first CG PUSCH occasion);

[0100] Non-periodic PUCCH;

[0101] Non-periodic SRS;

[0102] The Physical Random Access Channel (PRACH) is triggered by the Physical Downlink Control Channel (PDCCH) command.

[0103] Optionally, the configured downlink transmission may include at least one of the following (a) and (b):

[0104] (a) Cell-specifically configured DL reception may include PDCCH monitored in the Type-0 / 0A / 1 / 2CSS set (Common Search Space set);

[0105] (b) UE-dedicated configured DL reception may include at least one of the following (b1) to (b6):

[0106] (b1) PDCCH monitored in Type-3 CSS set;

[0107] (b2) PDCCH monitored in the USS set (UE-specific Search Space set);

[0108] (b3) The Physical Downlink Shared Channel (PDSCH) of Semi-Persistent Scheduling (SPS), namely SPS PDSCH (excluding the SPS PDSCH transmitted within the first SPSPDSCH or the first SPS PDSCH occasion corresponding to the activation DCI).

[0109] (b4) Periodic CSI-RS;

[0110] (b5) Semi-persistent CSI-RS;

[0111] (b6) Positioning Reference Signal (PRS).

[0112] Optionally, the configured downlink transmission may also include SSB and / or CORESET0.

[0113] Optionally, the indicated downlink transmission may include at least one of the following:

[0114] Dynamically scheduled PUSCH;

[0115] SPS PDSCH (the first SPS PDSCH corresponding to the activation DCI or the SPS PDSCH transmitted within the first SPS PDSCH occasion);

[0116] Non-periodic CSI-RS.

[0117] The Random Access Channel Occasion (RO), Synchronization Signal Block (SSB), and Control-Resource Set (CORESET) can be considered as protocol-defined transmissions. RO represents uplink transmission (or, in other words, RO is involved in uplink transmission), while SSB and CORESET#0 (which can also be described as CORESET0) represent downlink transmission (or, in other words, SSB and CORESET#0 are involved in downlink transmission).

[0118] Based on the configured and / or indicated transmission, the first device can determine whether the SBFD time domain unit is used for uplink transmission, downlink transmission, or both uplink and downlink transmission. Based on the transmission situation within the SBFD time domain unit, it selects an appropriate duplex mode to ensure that some or all of the transmissions configured and / or indicated within the SBFD time domain unit can proceed normally and smoothly.

[0119] For example, when determining the target duplex mode of the UE in the SBFD time domain using rule 1, the first device may use any one of the following rules to determine the target duplex mode:

[0120] Rule 1-1: When there is no configured and / or indicated downlink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use SBFD duplex mode one.

[0121] Rule 1-2: When there is no configured and / or indicated uplink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use SBFD duplex mode one.

[0122] Rule 1-3: When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the SBFD time domain unit is determined to adopt SBFD duplex mode two.

[0123] Rule 1-4: When there is a configured uplink or downlink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use SBFD duplex mode two.

[0124] Rule 1-5 determines the duplex mode of the SBFD time domain unit occupied by the target CORESET based on the time-frequency position of the target CORESET within the protected PDCCH monitoring window (or based on the time-frequency position of the target CORESET used to monitor the target PDCCH within the protected PDCCH monitoring window).

[0125] Rules 1-6 determine the duplex mode of the SBFD time domain unit occupied by SSB or CORESET#0 based on the time-frequency position of SSB or CORESET#0.

[0126] Rules 1-7 determine the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid RO.

[0127] It should be noted that rules 1-5, 1-6, and 1-7 can belong to multiple rules for determining the target duplex mode based on transmissions configured and / or indicated within the SBFD time-domain unit. Optionally, rules 1-5, 1-6, and 1-7 can also be parallel to rules 1-1 to 1-4, meaning that rules 1-5, 1-6, and 1-7 do not belong to multiple rules for determining the target duplex mode based on transmissions configured and / or indicated within the SBFD time-domain unit. In this case, determining the target duplex mode according to predefined rules includes any one of the following:

[0128] Rule 1-5: Based on the time-frequency position of the target CORESET within the protected PDCCH monitoring window, determine the duplex mode of the SBFD time domain unit occupied by the target CORESET.

[0129] Rules 1-6 determine the duplex mode of the SBFD time domain unit occupied by SSB or CORESET#0 based on the time-frequency position of SSB or CORESET#0.

[0130] Rules 1-7 determine the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid RO.

[0131] In some other implementations of Method 1, the first device determines the duplex mode of the SBFD time domain unit based on the first information, which is used to predict the uplink and / or downlink transmission of the SBFD time domain unit. This implementation is referred to as Rule 2 below.

[0132] In this implementation, the first device predicts (i.e., predetermines or prejudges) the possible transmission situation (or data transmission requirements within the SBFD time domain unit) based on the first information. Based on the predicted transmission situation within the SBFD time domain unit, it selects an appropriate duplex mode to ensure that the data to be transmitted can be transmitted normally within the SBFD time domain unit (or to ensure that the data transmission requirements within the SBFD time domain unit are met as much as possible).

[0133] The first piece of information may include the UE's Buffer Status Report (BSR) and the UE's service characteristics (including uplink and / or downlink services). The BSR is mainly used by the UE to inform the network of the amount of data to be transmitted in its buffer. Based on the BSR, the first device can determine whether the UE has uplink data to transmit in the SBFD time domain unit in the future.

[0134] UE service characteristics include service features and Quality of Service (QoS) requirements. Service features include at least one of the following: service data packet size characteristics; service data packet periodicity characteristics; service data transmission rate characteristics. QoS requirements include at least one of the following: Packet Delay Budget (PDB), Packet Set Error Rate (PDU Set Error Rate, PSER), Packet Error Rate (PER), and Packet Set Error Rate (PDU Set Error Rate, PSER).

[0135] The first device can also determine (or roughly determine) whether the UE needs to send or receive data within the SBFD time domain unit in the future, or the expected amount of data to be sent or received within the SBFD time domain unit, based on the UE's service characteristics and / or QoS requirements. For example, the periodic characteristics of service data packets can be used to determine whether the UE needs to send or receive data within the SBFD time domain unit in the future, and the size characteristics of service data packets can be used to determine the characteristics of the amount of data to be sent or received, including the maximum / minimum / average data amount, etc.

[0136] In some implementations of Method 2, the first device receives first indication information sent by the second device, which is used to indicate the target duplex mode used by at least one SBFD time domain unit; the first device determines the duplex mode of at least one SBFD time domain unit according to the first indication information.

[0137] In some implementations of Method 2, before the first device receives the duplex mode indicated by the second device, the first device requests the duplex mode from the second device, and the second device indicates the duplex mode based on the request from the first device.

[0138] In some implementations, the first device sends a request message to the second device, which requests the duplex mode of at least one SBFD time domain unit.

[0139] In some implementations, the request message includes a second indication message that indicates the desired target duplex mode for at least one SBFD time-domain unit.

[0140] When the first device is a terminal and the second device is a network-side device, that is, when the network-side device indicates the target duplex mode to the terminal, the first indication information can be carried by downlink control information (DCI), media access control control element (MAC CE), demodulation reference signal (DM-RS or DMRS) sequence or (Channel State Information-Reference Signal, CSI-RS) resources.

[0141] When the first device is a terminal and the second device is a network-side device, the second indication information can be carried by uplink control information (UCI), MAC CE, DM-RS sequence, SRS resources or PRACH.

[0142] When the first device is a network-side device and the second device is a terminal, that is, when the terminal indicates the target duplex mode to the network-side device, the first indication information can be carried by UCI, MAC CE, DM-RS sequence, SRS resource or PRACH.

[0143] When the first device is a network-side device and the second device is a terminal, the second indication information can be carried by DCI, MAC CE, DM-RS sequence or CSI-RS resources.

[0144] The uplink resources carrying the first or second indication information can be configured by the network side, such as CGPUSCH resources or PUCCH resources. Optionally, the type of time-domain resources corresponding to the uplink resources carrying the first or second indication information can be further restricted, for example, requiring them to be non-SBFD symbols, to avoid interference within SBFD symbols or the impact of frequency domain mode changes.

[0145] Alternatively, the first or second indication information can be obtained by using a specific DM-RS sequence in the PUCCH or PUSCH transmission, actually sending a specific SRS resource, sending a PRACH (or sending a PRACH within a specific RO, and / or using a specific Preamble), etc.

[0146] In some implementations of Method 2, the first device can confirm the duplex mode indicated by the second device, that is, confirm that the duplex mode indicated by the second device has been received, or confirm that the duplex mode indicated by the second device has been adopted or is in effect.

[0147] Alternatively, based on the various implementations of Method 2, Method 2 can be divided into the following determination methods:

[0148] The network-side device indicates full-duplex mode; optionally, the UE confirms this.

[0149] The UE indicates duplex mode; optionally, the network-side device confirms this.

[0150] The UE requests full-duplex mode, indicated by the network-side device;

[0151] The network-side device requests full-duplex mode, which is indicated by the UE.

[0152] UE request for duplex mode refers to the UE sending a request message (which may include second indication information) to the network-side device to request duplex mode. The network-side device, based on the UE's request, instructs the UE to indicate the duplex mode (which may be indicated through first indication information). UE indication of duplex mode refers to the UE instructing the network-side device to indicate duplex mode, without the network-side device needing to send a request message to the UE. Optionally, in the case of UE indication of duplex mode, the network-side device can confirm the indicated duplex mode by sending confirmation information to the UE.

[0153] Network-side indication of duplex mode means that the network-side device indicates the duplex mode to the UE, and the UE does not need to send a request message to the network-side device. Network-side device request of duplex mode means that the network-side device sends a request message to the UE requesting duplex mode, and the UE indicates the duplex mode to the network-side device based on the network-side device's request. In the case of network-side indication of duplex mode, optionally, the UE confirms the indicated duplex mode by sending an acknowledgment message to the network-side device.

[0154] Optionally, when a UE requests a duplex mode, the UE can confirm the indicated duplex mode. Similarly, when a network-side device requests a duplex mode, the network-side device can confirm the indicated duplex mode.

[0155] S102. The first device performs channel and / or signal transmission and reception on the SBFD time domain unit according to the target duplex mode.

[0156] When the target duplex mode of the SBFD time domain unit is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at any given time. Optionally, based on the transmission direction of the UE on the SBFD time domain unit (i.e., uplink or downlink transmission), SBFD duplex mode one can be divided into the following two types: SBFD duplex mode one that supports (or only supports) uplink transmission and SBFD duplex mode one that supports (only supports) downlink transmission.

[0157] When the network-side device and the UE determine that the duplex mode of the SBFD time domain unit is SBFD duplex mode one that supports uplink transmission, the UE performs uplink channel and / or uplink signal transmission on the SBFD time domain unit; correspondingly, the network-side device performs uplink channel and / or uplink signal reception on the SBFD time domain unit.

[0158] When the network-side device and the UE determine that the duplex mode of the SBFD time domain unit is SBFD duplex mode one that supports downlink transmission, the network-side device performs the transmission of downlink channel and / or downlink signal on the SBFD time domain unit; correspondingly, the UE performs the reception of downlink channel and / or downlink signal on the SBFD time domain unit.

[0159] When the network-side device and the UE determine that the duplex mode of the SBFD time domain unit is SBFD duplex mode 2, the UE can perform uplink and downlink transmissions on the SBFD time domain unit at the same time; correspondingly, the network-side device can also perform uplink and downlink transmissions on the same SBFD time domain unit.

[0160] In this embodiment, the first device determines the target duplex mode of the UE within the SBFD time domain unit according to predefined rules and / or the duplex mode indicated by the second device. When the target duplex mode is SBFD duplex mode one, the UE can only perform uplink or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the UE can perform both uplink and downlink transmission on the SBFD time domain unit at the same time. The first device performs channel and / or signal transmission and reception on the SBFD time domain unit according to the target duplex mode. In this embodiment, when the UE simultaneously supports SBFD duplex mode one and SBFD duplex mode two, the network-side device and the UE can determine and understand the target duplex mode used by the UE in the SBFD time domain unit, thereby ensuring that SBFD operation can be accurately and consistently executed synchronously on both sides, so as to reliably realize the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage.

[0161] The following provides a detailed explanation of the various determination methods mentioned above. Each determination method is illustrated using the SBFD time domain unit as an example of the SBFD symbol. The type of downlink transmission configured and / or indicated is described in the aforementioned relevant descriptions, and the type of uplink transmission configured and / or indicated is described in the aforementioned relevant descriptions. These will not be repeated below.

[0162] (a) Some ways to implement rule 1:

[0163] Rule 1-1: When there is no configured and / or indicated downlink transmission in the SBFD time domain unit, the SBFD time domain unit is determined to adopt SBFD duplex mode one (i.e., gNB SBFD mode).

[0164] Taking the SBFD time domain unit as an SBFD symbol as an example, when there is no configured and / or indicated downlink transmission in the SBFD symbol, there may or may not be a configured and / or indicated uplink transmission in the SBFD symbol. Using this rule, the SBFD symbol is determined to adopt gNB SBFD mode. At this time, a wider subband can be used to obtain more frequency domain resources. At the same time, since there is at most a single-direction transmission in the SBFD symbol, adopting gNB SBFD mode can also fully meet the transmission requirements.

[0165] Optionally, when there is no configured and / or indicated downlink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use a gNB SBFD mode that supports uplink transmission.

[0166] Rule 1-2: When there is no configured and / or indicated uplink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use SBFD duplex mode one (gNB SBFD mode).

[0167] Taking the SBFD time domain unit as an SBFD symbol as an example, when there is no configured and / or indicated uplink transmission in the SBFD symbol, there may or may not be a configured or indicated downlink transmission in the SBFD symbol. Using this rule, the SBFD symbol is determined to adopt gNB SBFD mode. At this time, a wider subband can be used to obtain more frequency domain resources. At the same time, since there is at most a single-direction transmission in the SBFD symbol, adopting gNB SBFD mode can also fully meet the transmission requirements.

[0168] Optionally, when there is no configured and / or indicated uplink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to use a gNB SBFD mode that supports downlink transmission.

[0169] Rule 1-3: When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the SBFD time domain unit is determined to adopt SBFD duplex mode 2 (i.e., UE SBFD mode).

[0170] In one implementation, when both a configured and / or indicated uplink transmission and a configured and / or indicated downlink transmission exist simultaneously within the SBFD time domain unit, and the uplink transmission and / or downlink transmission satisfy a first condition, the SBFD time domain unit is determined to adopt SBFD duplex mode two, wherein the first condition includes at least one of the following:

[0171] The uplink transmission was determined to be illegal or not actually existent;

[0172] The downlink transmission was determined to be illegal or not actually existent.

[0173] Optionally, the uplink transmission is determined to be illegal or not actually existent based on the frequency domain resources occupied by the uplink transmission and the frequency domain mode corresponding to SBFD duplex mode two; the downlink transmission is determined to be illegal or not actually existent based on the frequency domain resources occupied by the downlink transmission and the frequency domain mode corresponding to SBFD duplex mode two, wherein the frequency domain mode is used to indicate the frequency domain position of the uplink sub-band, downlink sub-band and guard band of the SBFD time domain unit.

[0174] Alternatively, other methods can be used to determine whether an uplink or downlink transmission is illegal or does not actually exist. For example, the TDD pattern information configured in the current Serving cell can be used to determine whether an uplink or downlink transmission is illegal or does not actually exist. When an uplink transmission overlaps with a semi-static DL symbol (and / or, an SSB symbol), it is determined to be illegal or does not actually exist; when a downlink transmission overlaps with a semi-static UL symbol, it is determined to be illegal or does not actually exist.

[0175] Taking the SBFD time domain unit as an SBFD symbol as an example, when there are both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions in the SBFD symbol, it is determined that this SBFD symbol adopts UE SBFD mode. At this time, it is desired that the UE executes both the configured and / or indicated downlink transmissions and the configured and / or indicated uplink transmissions.

[0176] Optionally, when the downlink transmission configured and / or indicated within this SBFD symbol conflicts with the frequency domain pattern corresponding to the UE's SBFD mode (e.g., at least a portion of the frequency domain resources occupied by the configured and / or indicated downlink transmission are located outside the DL subband of the frequency domain pattern), both sides (i.e., the UE and the network-side device) determine that the configured / indicated downlink transmission is illegal or does not actually exist; or, when at least a portion of the frequency domain resources occupied by the configured / indicated downlink transmission within this SBFD symbol are located within the DL subband of the frequency domain pattern (or the number or proportion of frequency domain resources located within the DL subband of the frequency domain pattern is greater than / not less than a threshold), both sides determine that the configured / indicated downlink transmission is legal or actually exists; otherwise, it is determined to be illegal or does not actually exist. Based on these determinations, it is then determined whether rules 1-3 should be applied. Optionally, the UE expects that the indicated downlink transmission within this SBFD symbol will always be determined to be legal or actually exist.

[0177] Optionally, when the uplink transmission configured / indicated within this SBFD symbol conflicts with the frequency domain pattern corresponding to the UE SBFD mode (e.g., at least a portion of the frequency domain resources occupied by the configured / indicated uplink transmission are located outside the UL subband of the frequency domain pattern), both sides determine that the configured / indicated uplink transmission is illegal or does not actually exist; or, when at least a portion of the frequency domain resources occupied by the configured / indicated uplink transmission within this SBFD symbol are located within the UL subband of the frequency domain pattern (or the number or proportion of frequency domain resources located within the UL subband of the frequency domain pattern is greater than / not less than a threshold), both sides determine that the configured / indicated uplink transmission is legal or actually exists; otherwise, it is determined to be illegal or does not actually exist. Based on these determinations, it is then determined whether to apply rules 1-3. Optionally, the UE expects that the indicated uplink transmission within this SBFD symbol will always be determined to be legal or actually exist.

[0178] Rule 1-4: When there is a configured downlink or uplink transmission within the SBFD time domain unit, the SBFD time domain unit is determined to adopt SBFD duplex mode 2 (i.e., UE SBFD mode).

[0179] In one implementation, when the configured downlink or uplink transmission meets a second condition, the SBFD time domain unit is determined to adopt SBFD duplex mode two, wherein the second condition includes at least one of the following:

[0180] The configured target type for downlink or uplink transmission;

[0181] The configured downlink or uplink transmission type belongs to the target type set;

[0182] The configured downlink or uplink transmission period does not exceed the second threshold;

[0183] The time-domain interval between adjacent transmission occcasions corresponding to the configured downlink or uplink transmissions shall not exceed the second threshold;

[0184] The maximum time-domain interval between adjacent transmission opportunities corresponding to the configured downlink or uplink transmission shall not exceed the second threshold.

[0185] This rule can be understood as follows: both sides (UE and network-side equipment) want to ensure that the configured downlink or uplink transmission is unaffected and can be executed normally, but may need to temporarily perform dynamic scheduling in the opposite transmission direction as needed. In order to ensure that the transmission in both transmission directions (i.e., the configured downlink or uplink transmission, and the temporary dynamic scheduling in the opposite transmission direction) can be executed normally in this case, the UE SBFD mode is pre-determined.

[0186] Taking the SBFD time domain unit as an SBFD symbol as an example, optionally, rules 1-4 are applied only if the downlink or uplink transmission configured in this SBFD symbol corresponds to the target type (including Channel / Signal type and time domain mode, see the enumeration item of "Configured / Indicated Uplink and Downlink Transmissions" above), or if the type of the configured downlink or uplink transmission belongs to the target type set.

[0187] For example, for a UE initiating a Virtual Reality (VR) service, the network-side equipment configures CG PUSCH resources to carry small data packets corresponding to the pose / control stream. In this case, within any SBFD symbol occupied by the CG PUSCH, both sides determine whether to use UE SBFD mode to ensure that the transmission of the CG PUSCH is not affected by mode switching. In this embodiment, mode switching refers to the UE switching between UE SBFD mode and gNB SBFD mode for an SBFD symbol.

[0188] Optionally, when the period of the downlink or uplink transmission configured for the UE (or the downlink or uplink transmission configured to meet the requirements of the target type or target type set), or the time domain interval (or maximum time domain interval) between adjacent Occasions does not exceed a predefined second threshold, both sides determine that during the duration of this configured downlink or uplink transmission (i.e., the entire time period during which the corresponding configuration is effective), all involved SBFD symbols adopt the UE SBFD mode. This ensures that the downlink or uplink transmission configured can be executed normally without being affected, while avoiding the overhead caused by frequent Modeswitching (including signaling overhead involved in Mode switching, resource unavailability caused by Switching time, etc.).

[0189] It is understood that a downlink or uplink transmission period configured for the UE may include one or more Occasions. Therefore, the Occasions corresponding to this configured downlink or uplink transmission may or may not be equally spaced. When Occasions are equally spaced, the time-domain interval between adjacent Occasions can be selected for determination. When Occasions are not equally spaced, the maximum time-domain interval between adjacent Occasions can be selected for determination.

[0190] Rule 1-5: Based on the time-frequency position of the target CORESET within the protected PDCCH monitoring window used to monitor the target PDCCH, determine the duplex mode of the SBFD time domain unit occupied by the target CORESET.

[0191] This rule assumes that the UE's monitoring behavior of the target PDCCH (including all PDCCH monitoring within the protected PDCCH monitoring window, or PDCCH monitoring that meets specific requirements) within the protected PDCCH monitoring window will not be affected by mode switching, or that the monitoring performance will not be affected by self-interference. Optionally, the PDCCH that meets specific requirements may include: PDCCH involved in the initial access process, PDCCH involved in the random access process, PDCCH monitored within a specific CORESET, PDCCH carrying uplink / downlink scheduling DCI, PDCCH carrying SFI (or DCI format 2_0), etc.

[0192] The PDCCH involved in the initial access process is, for example, the PDCCH for the initial retransmission of System Information Block Type 1 (SIB1).

[0193] The PDCCH involved in the random access process may include the PDSCH for scheduling Msg2, indicating the BFR based on Msg1, the PUSCH retransmission for scheduling Msg3, the initial retransmission of the PDSCH for scheduling Msg4, and indicating successful contention resolution.

[0194] The PDCCH monitored within a specific CORESET can include the PDCCH monitored within CORESET#0 (i.e., the CORESET with index 0).

[0195] Self-interference in a UE refers to the interference caused by the signals emitted by the UE itself on the signals it receives. Self-interference is a common problem in full-duplex communication systems. Self-interference can lead to a decline in UE reception performance; for example, it can reduce receiver sensitivity, increase the bit error rate, and reduce system capacity.

[0196] The protected PDCCH monitoring window can be defined by the protocol or configured by higher-layer signaling. For example, the protected PDCCH monitoring window can correspond to a periodically occurring time window, the period, offset, and window length of which can be defined by the protocol or configured by higher-layer signaling. Alternatively, the protected PDCCH monitoring window can be the time period corresponding to any monitoring occcasion of a PDCCH that meets specific requirements, which can be defined by the protocol or configured by higher-layer signaling.

[0197] Optionally, rule 1-5 may include the following two rules: rule 1-5-1 and rule 1-5-2.

[0198] Rule 1-5-1, based on the time-frequency location of the target CORESET, determines that the SBFD time domain unit occupied by the target CORESET adopts SBFD duplex mode one that supports downlink transmission.

[0199] Taking the SBFD time domain unit as an example, based on the time-frequency position of the target CORESET, it is possible to determine which SBFD symbols the target CORESET occupies.

[0200] This rule can be understood as follows: within the SBFD symbol occupied by the target CORESET, the UE is expected to monitor the target PDCCH and avoid uplink transmissions within these SBFD symbols to prevent self-interference from affecting the monitoring performance of the target PDCCH.

[0201] To avoid uplink transmission by the UE within the SBFD symbol occupied by the target CORESET, the UE may perform at least one of the following operations:

[0202] The UE discards or postpones uplink transmissions within the SBFD symbol occupied by the target CORESET;

[0203] The UE does not expect uplink transmissions configured / indicated within the SBFD symbol memory occupied by the target CORESET;

[0204] The UE does not expect the indicated uplink transmission to exist in the SBFD symbol occupied by the target CORESET, and will discard or postpone the configured uplink transmission in the SBFD symbol occupied by the target CORESET.

[0205] Rule 1-5-2, based on the frequency domain location of the target CORESET (including the frequency domain resources it occupies), determines the duplex mode of the SBFD time domain unit occupied by the target CORESET, including at least one of the following:

[0206] When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode two, it is determined that the first SBFD time domain unit adopts SBFD duplex mode two.

[0207] When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode one, but not all of which are located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode two, the first SBFD time domain unit is determined to use SBFD duplex mode one.

[0208] When the target CORESET occupies at least a portion of the frequency domain resources in the first SBFD time domain unit, which are located outside the downlink subband corresponding to the frequency domain mode of SBFD duplex mode one, it is determined that the first SBFD time domain unit is backed up to a downlink time domain unit or SBFD duplex mode one is adopted.

[0209] Wherein, the first SBFD time domain unit mentioned above is any SBFD time domain unit within at least one SBFD time domain unit occupied by the target CORESET.

[0210] Generally, it is necessary to ensure that all frequency domain resources occupied by the target CORESET are available. However, when the target CORESET occupies at least one SBFD time domain unit, within that at least one SBFD time domain unit, it is necessary to check the positional relationship between the frequency domain resources occupied by the target CORESET and the downlink subband corresponding to the frequency domain mode corresponding to the duplex mode, in order to check or ensure the availability of the frequency domain resources occupied by the target CORESET.

[0211] The frequency domain resources occupied by the target CORESET within the first SBFD time domain unit are not all located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode 2, including at least the following two situations: none of the frequency domain resources occupied by the target CORESET within the first SBFD time domain unit are located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode 2, or only a portion of the frequency domain resources occupied by the target CORESET within the first SBFD time domain unit are located within the downlink subband corresponding to the frequency domain mode of SBFD duplex mode 2.

[0212] After the first SBFD time domain unit falls back to the downlink time domain unit, all frequency domain resources in the current Serving cell or the current BWP can be used for downlink transmission within this time domain unit.

[0213] Taking the SBFD time-domain unit as the SBFD symbol as an example, based on the frequency domain location of the target CORESET (including the frequency domain resources it occupies), the duplex mode corresponding to the SBFD symbol occupied by the target CORESET is determined. Specifically, at least one of the following methods can be used:

[0214] When the target CORESET occupies all frequency domain resources within its occupied SBFD symbol and all of them are located within the DL subband corresponding to the frequency domain pattern of the UE SBFD mode, the UE SBFD mode is adopted.

[0215] When the target CORESET occupies all frequency domain resources within its occupied SBFD symbol, and all of these resources are located within the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode, but not all of them are located within the DL subband corresponding to the frequency domain pattern of the UE SBFD mode, the gNB SBFD mode is used.

[0216] When a target core set has at least a portion of its frequency domain resources located outside the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode within its occupied SBFD symbol, the SBFD symbol falls back to a Full DL symbol; alternatively, the gNB SBFD mode is used, and when at least a portion of the frequency domain resources occupied by a PDCCH candidate are located outside the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode, the UE does not monitor this PDCCH candidate; or, the UE expects all frequency domain resources occupied by the target core set within its occupied SBFD symbol to be located within the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode (i.e., error cases are avoided through base station configuration).

[0217] Rules 1-6 determine the duplex mode of the SBFD time domain unit occupied by SSB or CORESET#0 based on the time-frequency position of SSB or CORESET#0.

[0218] This rule assumes that the UE's SSB / CORESET#0 detection behavior must not be affected by mode switching, or that the detection performance must not be affected by self-interference.

[0219] Optionally, rule 1-6 may include the following two rules: rule 1-6-1 and rule 1-6-2.

[0220] Rule 1-6-1, based on the time-frequency position of SSB or CORESET#0, determines that the SBFD time domain unit occupied by SSB or CORESET#0 adopts SBFD duplex mode one that supports downlink transmission.

[0221] Taking the SBFD time domain unit as an example, based on the time-frequency position of SSB / CORESET#0, it can be determined which SBFD symbols SSB / CORESET#0 occupies.

[0222] This rule can be understood as follows: within the SBFD symbol occupied by SSB / CORESET#0, the UE is expected to receive SSB / CORESET#0 and avoid uplink transmissions within these SBFD symbols to prevent self-interference from affecting the reception quality of SSB / CORESET#0.

[0223] To avoid uplink transmission within the SBFD symbol occupied by SSB / CORESET#0, the UE may perform at least one of the following:

[0224] The UE discards or postpones uplink transmissions within the SBFD symbol occupied by SSB / CORESET#0;

[0225] The UE does not expect uplink transmissions configured / indicated in the SBFD symbol occupied by SSB / CORESET#0;

[0226] The UE does not expect the indicated uplink transmission to exist in the SBFD symbol occupied by SSB / CORESET#0, and will discard or postpone the configured uplink transmission in the SBFD symbol occupied by SSB / CORESET#0.

[0227] Rule 1-6-2, based on the frequency domain location (including the frequency domain resources occupied) of SSB or CORESET#0, determines the duplex mode of the SBFD time domain unit occupied by SSB or CORESET#0, which may include at least one of the following:

[0228] When the frequency domain resources occupied by SSB or CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode of SBFD duplex mode 2, it is determined that the second SBFD time domain unit adopts SBFD duplex mode 2.

[0229] When the frequency domain resources occupied by SSB or CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode of SBFD duplex mode one, but the frequency domain resources occupied are not all located in the downlink subband corresponding to the frequency domain mode of SBFD duplex mode two, the second SBFD time domain unit is determined to adopt SBFD duplex mode one.

[0230] When SSB or CORESET#0 occupies at least a portion of the frequency domain resources in the second SBFD time domain unit, which are located outside the downlink subband corresponding to the frequency domain mode of SBFD duplex mode one, the second SBFD time domain unit is determined to fall back to the downlink time domain unit.

[0231] The second SBFD time domain unit mentioned above is any one of the SBFD time domain units occupied by SSB or CORESET#0.

[0232] Generally, it is necessary to ensure that all frequency domain resources occupied by SSB or CORESET#0 are available. However, when SSB or CORESET#0 occupies at least one SBFD time domain unit, within that at least one SBFD time domain unit, it is necessary to check the positional relationship between the frequency domain resources occupied by SSB or CORESET#0 and the downlink subband corresponding to the frequency domain mode corresponding to the duplex mode, in order to check or ensure the availability of the frequency domain resources occupied by the target CORESET.

[0233] After the second SBFD time domain unit falls back to the downlink time domain unit, all frequency domain resources in the current Serving cell or the current BWP can be used for downlink transmission within this time domain unit.

[0234] Optionally, the UE expects that all frequency domain resources occupied by SSB or CORESET#0 in the second SBFD time domain unit are located in the downlink subband corresponding to the frequency domain mode of SBFD duplex mode one (i.e., to avoid Errorcase through base station configuration).

[0235] Taking the SBFD time domain unit as the SBFD symbol as an example, based on the frequency domain position of SSB / CORESET#0, the duplex mode corresponding to the SBFD symbol occupied by SSB / CORESET#0 is determined. Specifically, at least one of the following can be used:

[0236] When all frequency domain resources occupied by SSB / CORESET#0 within its occupied SBFD symbol are located within the DL subband corresponding to the frequency domain pattern of UESBFD mode, UE SBFD mode is adopted.

[0237] When all frequency domain resources occupied by SSB / CORESET#0 within its occupied SBFD symbol are located within the DL subband corresponding to the frequency domain pattern of gNBSBFD mode, but not all are located within the DL subband corresponding to the frequency domain pattern of UE SBFD mode, gNB SBFD mode is used.

[0238] When SSB / CORESET#0 occupies at least a portion of its frequency domain resources within its occupied SBFD symbol, which are located outside the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode, the SBFD symbol falls back to a Full DL symbol; or, the UE expects all frequency domain resources occupied by SSB / CORESET#0 within its occupied SBFD symbol to be located within the DL subband corresponding to the frequency domain pattern of the gNB SBFD mode (i.e., error cases are avoided through base station configuration).

[0239] Optionally, the aforementioned SSB or CORESET#0 refers to the SSB or CORESET#0 configured on the Serving cell corresponding to the SBFD carrier. Optionally, rules 1-6 apply only to the Cell-Defining Synchronization Signal Block (CD-SSB) on the serving cell and not to non-Cell-Defining SSBs (NCD-SSB).

[0240] Rules 1-7 determine the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid RO.

[0241] This rule assumes that the UE's RACH behavior must not be affected by mode switching. Generally, considering that different UEs may have different self-interference suppression capabilities, the corresponding frequency domain mode may be different when using SBFD duplex mode 2. However, the Valid RO and RO to SSB mapping within the same cell should ideally be unified for different UEs. Therefore, the Valid RO can be assumed to be determined based on the frequency domain mode corresponding to SBFD duplex mode 1.

[0242] Optionally, rules 1-7 may include the following six rules:

[0243] Rule 1-7-1, based on the time-frequency location of the valid RO, determines that the SBFD time domain unit occupied by the valid RO adopts SBFD duplex mode one that supports uplink transmission (i.e., gNB SBFD mode).

[0244] Taking SBFD time domain units as SBFD symbols as an example, this rule can be understood as follows: within any SBFD time domain unit occupied by a valid RO, it is desirable to avoid affecting the UE's RACH initiation. When using gNB SBFD mode, the UL subband is generally wider, allowing the UE to actually use more valid ROs. (It should be noted that when a valid RO occupies an SBFD symbol, the frequency domain resources occupied by this valid RO must be within the UL subband corresponding to the frequency domain pattern of the gNB SBFD mode, but some or all of the occupied frequency domain resources may be outside the UL subband corresponding to the frequency domain pattern of the UE SBFD mode. In this case, when the UE is operating in UE SBFD mode within these SBFD symbols, this valid RO is actually not allowed to be used.) Furthermore, downlink transmission within these SBFD symbols can be avoided to prevent poor control of self-interference during RACH, which could lead to poor or unstable downlink transmission performance.

[0245] To avoid downlink transmission within the SBFD symbol occupied by the Valid RO, the UE may perform at least one of the following:

[0246] The UE discards downlink transmissions within the SBFD symbol occupied by the Valid RO;

[0247] The UE does not expect downlink transmissions configured / indicated within the SBFD symbol memory occupied by the Valid RO;

[0248] The UE does not expect any downlink transmissions to exist within the SBFD symbol occupied by the Valid RO and will discard any downlink transmissions configured within the SBFD symbol occupied by the Valid RO.

[0249] Rule 1-7-2, based on the time-frequency resources of the valid RO, determines that the SBFD time domain unit occupied by the target valid RO adopts SBFD duplex mode one that supports uplink transmission. The target valid RO is the RO in the valid RO that the UE expects to transmit PRACH.

[0250] The expectation of a UE to actually transmit a PRACH within a certain Valid RO can be understood as the UE selecting this Valid RO based on the received PDCCHorder or triggered by a higher-layer event and expecting to actually transmit a PRACH within this Valid RO.

[0251] Furthermore, downlink transmissions within the SBFD symbol occupied by this Valid RO can be avoided. For specific UE operations, please refer to the corresponding description in Rule 1-7-1.

[0252] Rule 1-7-3, based on the time-frequency location of the valid RO, determines the duplex mode of the SBFD time-domain unit occupied by the valid RO, including at least one of the following:

[0253] When all the frequency domain resources occupied by the valid ROs configured in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode of SBFD duplex mode 2, it is determined that the third SBFD time domain unit adopts SBFD duplex mode 2.

[0254] When all the frequency domain resources occupied by all the configured valid ROs in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode corresponding to SBFD duplex mode one, but the frequency domain resources occupied by all the configured valid ROs are not located in the uplink subband corresponding to the frequency domain mode corresponding to SBFD duplex mode two, it is determined that the third SBFD time domain unit adopts SBFD duplex mode one.

[0255] The third SBFD time-domain unit is any SBFD time-domain unit configured with at least one valid RO.

[0256] Taking the SBFD time domain unit as an SBFD symbol as an example, for a certain SBFD symbol configured with Valid ROs, the Duplex mode corresponding to this SBFD symbol is determined based on the frequency domain positions (including the frequency domain resources occupied) of all configured Valid ROs within this SBFD symbol. Specifically, at least one of the following methods can be used:

[0257] When all frequency domain resources occupied by all configured Valid ROs within this SBFD symbol are located within the UL subband corresponding to the Frequency domain pattern of the UE SBFD mode, the UE SBFD mode is adopted.

[0258] When all frequency domain resources occupied by all configured Valid ROs within this SBFD symbol are located within the UL subband corresponding to the frequency domain pattern of the gNB SBFD mode, but not all are located within the UL subband corresponding to the frequency domain pattern of the UE SBFD mode, the gNB SBFD mode is used. It is important to note that all frequency domain resources occupied by each Valid RO configured within the SBFD symbol must be located within the UL subband corresponding to the frequency domain pattern of the gNB SBFD mode, as guaranteed by the RO validation rule.

[0259] Rule 1-7-4, based on the time-frequency location of the valid RO, determines the duplex mode of the SBFD time-domain unit occupied by the valid RO, including at least one of the following:

[0260] When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode two.

[0261] When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of SBFD duplex mode one, but the frequency domain resources occupied by the target valid RO are not all located within the uplink subband corresponding to the frequency domain mode of SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode one.

[0262] Wherein, the target valid RO is any valid RO in the valid RO in which the UE expects to transmit PRACH.

[0263] Taking the SBFD time domain unit as an example, when the UE expects to actually transmit PRACH within a certain Valid RO, the Duplex mode corresponding to the SBFD symbol occupied by this Valid RO is determined based on the frequency domain location of this Valid RO (including the frequency domain resources occupied).

[0264] Here, it is assumed that the UE first selects the Valid RO; when the selected Valid RO occupies an SBFD symbol or overlaps with the SBFD symbol in the time domain, the Duplex mode corresponding to the occupied / overlapping SBFD symbol is determined. Specifically, at least one of the following can be used:

[0265] When all frequency domain resources occupied by this Valid RO are located within the UL subband corresponding to the Frequencydomain pattern of the UE SBFD mode, the UE SBFD mode is adopted.

[0266] When all frequency domain resources occupied by this Valid RO are located within the UL subband corresponding to the Frequencydomain pattern of the gNB SBFD mode, but not all of them are located within the UL subband corresponding to the Frequencydomain pattern of the UE SBFD mode, the gNB SBFD mode is used.

[0267] Rule 1-7-5, based on the time-frequency location of the valid RO, determines the duplex mode of the SBFD time-domain unit occupied by the valid RO, including at least one of the following:

[0268] When a downlink transmission is configured and / or indicated within the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts SBFD duplex mode two;

[0269] When there is no configured and / or indicated downlink transmission in the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts SBFD duplex mode one that supports uplink transmission;

[0270] The fourth SBFD time-domain unit is any SBFD time-domain unit configured with at least one valid RO.

[0271] Taking the SBFD time domain unit as an example, when there is downlink transmission configured / indicated in the memory of an SBFD symbol with at least one Valid RO, this SBFD symbol adopts UE SBFD mode; otherwise, it adopts gNB SBFD mode and uplink transmission mode.

[0272] Optionally, when this SBFD symbol is determined to be using UE SBFD mode, the UE expects all frequency domain resources occupied by any Valid RO (or at least one Valid RO) configured in this SBFD symbol to be located within the UL subband corresponding to the frequency domain pattern of the UE SBFD mode.

[0273] Rule 1-7-6, based on the time-frequency location of the valid RO, determines the duplex mode of the SBFD time-domain unit occupied by the valid RO, including at least one of the following:

[0274] When a downlink transmission is configured and / or indicated within the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts SBFD duplex mode two;

[0275] When there is no configured and / or indicated downlink transmission in the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts the SBFD duplex mode one;

[0276] The fifth SBFD time domain unit is any SBFD time domain unit occupied by the target valid RO, which is any valid RO among the valid ROs that the UE expects to transmit PRACH.

[0277] Taking the SBFD time domain unit as an example, when the UE expects to actually transmit PRACH within a certain Valid RO, and the memory of a certain SBFD symbol occupied by this Valid RO is in the configured / indicated downlink transmission, this SBFD symbol adopts the UE SBFD mode; otherwise, this SBFD symbol adopts the gNB SBFD mode and adopts the uplink transmission mode.

[0278] Optionally, when this SBFD symbol is determined to be in UE SBFD mode, the UE expects all frequency domain resources occupied by this Valid RO to be located within the ULsubband corresponding to the frequency domain pattern of the UE SBFD mode.

[0279] Optionally, the above rules 1-7-2, 1-7-4, or 1-7-6 can be applied to all situations in which the UE expects to actually transmit PRACH within a certain Valid RO, or only to situations where RACH is triggered based on PDCCH order or triggered by a higher layer event. These rules can be specified by the protocol or configured by higher layer signaling.

[0280] (ii) Some ways to implement rule 2:

[0281] In Rule 2, the target duplex mode is determined based on the first information, which is used to predict uplink and / or downlink transmissions within the SBFD time domain unit.

[0282] Optionally, the first information may include the UE's BSR, or the characteristics of uplink and / or downlink services.

[0283] Taking the SBFD time domain unit as an SBFD symbol as an example, Rule 2 does not directly base its prediction on the uplink and downlink transmissions already configured / indicated within the SBFD symbol. Instead, it uses other information or factors affecting uplink and downlink data transmission to predict the uplink and downlink data transmission status within the SBFD symbol, thereby determining the matching Duplex mode. It is understandable that this prediction is performed in advance. For example, based on information acquired or updated at a certain time t, the Duplex mode corresponding to the SBFD symbol starting from t+Δt is determined, or the Duplex mode corresponding to the SBFD symbol within a time window starting from t+Δt. The length of this time window can be specified by the protocol or configured by higher-layer signaling.

[0284] Specifically, rule 2 may include at least one of the following: rule 2-1 and rule 2-2.

[0285] Rule 2-1: Based on the BSR information reported by the UE, determine the target duplex mode corresponding to the subsequent SBFD time domain unit.

[0286] Optionally, rule 2-1 may include at least one of the following:

[0287] Rule 2-1-1: When the UE does not report BSR within the first time period, it is determined that the SBFD time domain unit adopts SBFD duplex mode 1 that supports downlink transmission. This SBFD time domain unit can be any SBFD time domain unit in the future second time period.

[0288] Taking the SBFD time domain unit as the SBFD symbol as an example, when the UE has not reported BSR for a recent period of time (e.g., the first time period mentioned above), both sides believe that the SBFD symbol in the next time window (e.g., the second time period mentioned above) will all adopt gNB SBFD mode and downlink transmission mode.

[0289] The length of "recent period" here can be specified by the protocol or configured by higher-level signaling. Rule 2-1-1 can actually be implemented using a sliding window approach, executing at each predefined decision time point. The next time window can be understood as starting from a certain decision time point.

[0290] Based on the NR protocol, if the UE has uplink data to be transmitted, at least a Regular BSR will be triggered. When the UE does not report a BSR, it can be assumed that the UE currently has no uplink data to be transmitted. Here, we further predict that there will be no uplink data to be transmitted in the next time window.

[0291] Rule 2-1-2 states that when the BSR reported by the UE indicates that there is no uplink data to be transmitted or no uplink data to be transmitted that meets the predefined requirements, the SBFD time domain unit is determined to adopt SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the future third time period.

[0292] Taking the SBFD time domain unit as the SBFD symbol as an example, when the BSR reported by the UE indicates that there is no data to be transmitted uplink, or no data to be transmitted that meets the predefined requirements, both sides assume that the SBFD symbol in the next time window adopts gNB SBFD mode and downlink transmission mode.

[0293] Optionally, predefined requirements must be met, including meeting at least one of the following data requirements:

[0294] Data Requirement 1: The characteristics and / or parameters of the radio bearer, logical channel, or logical channel group (LCG) corresponding to the uplink data to be transmitted meet the first requirement.

[0295] For example, the RB / Logical channel / LCG is used to carry data of a specific service type or attribute (such as XR service, or I Frame of XR service), or the configuration of the RB / Logical channel / LCG meets predefined QoS requirements (for example, assuming the predefined QoS requirement is PDB <= X ms, it can be determined whether this PDB requirement is met based on the Discard Timer configured for the RB, for example, when the Discard Timer is configured to <= X ms, it is considered that this QoS requirement is met).

[0296] Data Requirement 2: The attributes and / or requirements of the data packets, Protocol Data Units (PDUs), or PDU sets corresponding to the uplink data to be transmitted must meet the second requirement.

[0297] Here, a PDU Set can be understood as a collection of one or more PDUs with the same transmission requirements. For example, a specific requirement is that the PDU or PDU Set corresponding to the service data corresponds to an I Frame or I Slice.

[0298] "No data to be transmitted" can be understood as indicating that the corresponding data quantity is 0 in the received BSR MAC CE, or that there is no corresponding data quantity indication.

[0299] Based on the NR protocol, the BSR MAC CE only indicates the current uplink buffer data to be transmitted in the UE's uplink buffer. Optionally, the received BSR MAC CE may further indicate the expected uplink data to be transmitted in the subsequent period (or the received BSR MAC CE may only indicate the expected uplink data to be transmitted in the subsequent period). Both sides apply rule 2-1-2 based on the expected uplink data to be transmitted in the subsequent period indicated in the BSR MAC CE.

[0300] The next time window can start from the start / end time of the first PUSCH transmission of the TB carrying the BSR MAC CE (or the start / end time of the time slot in which this first PUSCH transmission is located) + delta. The delta can be specified by the protocol or configured by higher layer signaling, mainly taking into account the latency of TB's HARQ transmission, decoding and decapsulation, for example, 3ms.

[0301] Rule 2-2: Determine the target duplex mode of the SBFD time domain unit based on the characteristics of the UE's uplink and / or downlink services.

[0302] The characteristics of uplink and / or downlink services include at least one of service features and QoS requirements, which can be obtained by the gNB from the CN, or reported by the UE (e.g., the UE includes relevant information on uplink and downlink service characteristics in the UE Assistance Information (UAI) message).

[0303] For example, business characteristics may include at least one of the following:

[0304] The size characteristics of business data packets may include the maximum / minimum / average size of PDUs, the maximum / minimum / average number of PDUs in a PDU set, and the maximum / minimum / average amount of data in a PDU set.

[0305] The periodic characteristics of business data can be aperiodic, periodic, or quasi-periodic; when periodic, it can be further included with period and offset; when quasi-periodic, it can be further included with period, offset, jitter range, etc.

[0306] Data rate characteristics of business data, including instantaneous maximum / minimum / average data rates.

[0307] QoS requirements include at least one of the following: PDB, PSDB, PER, and PSER.

[0308] In some implementations, the target duplex mode of the SBFD time domain unit is determined based on the characteristics of the UE's uplink and / or downlink services, including at least one of the following:

[0309] When the characteristics of uplink and / or downlink services meet the preset third condition, the SBFD time domain unit is determined to adopt SBFD duplex mode two.

[0310] When the characteristics of uplink and / or downlink services do not meet the third condition, the SBFD time domain unit is determined to adopt SBFD duplex mode one.

[0311] The SBFD time-domain unit used to determine the duplex mode in this rule can be understood as any one of the SBFD time-domain units configured for the UE. That is, for any one of the SBFD time-domain units configured for the UE, its duplex mode can be determined using rule 2-2.

[0312] Taking the SBFD time domain unit as the SBFD symbol as an example, the SBFD symbol is determined to use UE SBFD mode when the characteristics of the uplink or downlink service meet at least one of the following conditions; otherwise, gNB SBFD mode is used:

[0313] The business data packets are relatively small; for example, the size of the PDU or the amount of data contained in the PDU set is no greater than or less than a predefined threshold.

[0314] Business data packets arrive frequently, for example, when it is a periodic or quasi-periodic business, the period is no greater than or less than a predefined threshold;

[0315] The latency requirements for business data packets are urgent, for example, the PDB or PSDB must be no greater than or less than a predefined threshold.

[0316] (III) Some implementation methods for determining the target duplex mode based on the duplex mode indicated by the second device:

[0317] In some implementations, the first device receives first indication information sent by the second device. The first indication information is used to indicate the target duplex mode used by the SBFD time domain unit. The first device determines the target duplex mode of the SBFD time domain unit based on the first indication information.

[0318] In some implementations, before the first device receives the first instruction information sent by the second device, the first device sends a request message to the second device, which is used to request the duplex mode of the SBFD time domain unit.

[0319] In some implementations, the request message includes a second indication message, which indicates the target duplex mode that the SBFD time-domain unit expects to use.

[0320] Optionally, the SBFD time-domain unit requested in the request information may not be exactly the same as or completely overlap with the SBFD time-domain unit indicated in the first indication information. For example, the network-side device may only consider the request information reported by the UE as one factor, and combine it with other factors that need to be considered to determine and indicate the duplex mode of at least one consecutive SBFD time-domain unit.

[0321] In some implementations, the first instruction information includes N instruction items, where N is a positive integer; the second instruction information includes M instruction items, where M is a positive integer. M and N may be the same or different.

[0322] Assuming that M and N have the same value, and taking the SBFD time domain unit as the SBFD symbol as an example, generally, the request / instruction information (e.g., the second instruction information / the first instruction information) contains N (N>=1) pieces of the following information:

[0323] Information n (e.g., the nth indicator): at least one consecutive SBFD symbol starting from time reference point n (or, later than / no earlier than time reference point n; or, starting from the first SBFD symbol after time reference point n) adopts the target Duplex mode n (1<=n<=N).

[0324] Alternatively, a bitmap can be used to indicate which SBFD symbols within a single time range adopt which duplex mode, and the corresponding frequency domain pattern. Each bit in the bitmap corresponds to K (K>=1) consecutive SBFD symbols. However, considering that network / UE requests / indications of duplex modes are generally based on semi-static changing information or factors, such as service characteristics and the amount of data to be transmitted, predicting the duplex mode for a subsequent period, there is generally no need to indicate rapid changes or interleaved duplex modes. Furthermore, using a bitmap for indication is costly; therefore, this application will not elaborate on the bitmap indication method.

[0325] It should be noted that, in the embodiments of this application, "request information" is used when the first device requests the target duplex mode of the SBFD time domain unit from the second device, and "instruction information" is used when the second device instructs the first device on the target duplex mode of the SBFD time domain unit.

[0326] When the first device is a UE, the second device is a network-side device. When the second device is a network-side device, the first device is a UE.

[0327] When the network-side device indicates the Duplex mode corresponding to the SBFD symbol to the UE, the first indication information can be carried by DCI or MAC CE, where DCI is carried by PDCCH and MAC CE is carried by PDSCH. Optionally, the first indication information can also be carried by using a specific DM-RS sequence or actually sending specific CSI-RS resources during PDCCH / PDSCH transmission.

[0328] When a UE requests / indicates the Duplex mode corresponding to an SBFD symbol to the network-side device, the request / indication information can be carried by a UCI or a MAC CE, where the UCI is carried by a PUCCH or PUSCH, and the MAC CE is carried by a PUSCH. The uplink resources carrying the request / indication information can be configured by the network side, for example, as CG PUSCH resources or PUCCH resources. Optionally, the Symbol type corresponding to the uplink resources carrying the request / indication information can be further restricted, for example, requiring it to be a non-SBFD symbol, to avoid interference within the SBFD symbol or the impact of frequency domain pattern changes. Optionally, the request / indication information can also be carried by using a specific DM-RS sequence in PUCCH / PUSCH transmission, actually sending specific SRS resources, sending PRACH (or sending PRACH within a specific RO, and / or using a specific Preamble), etc.

[0329] In some implementations, the first instruction information includes N instruction items, where N is a positive integer, and each instruction item includes at least one of the following:

[0330] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0331] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0332] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0333] Auxiliary information.

[0334] In some implementations, the second instruction information includes M instruction items, where M is a positive integer, and each instruction item includes at least one of the following:

[0335] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0336] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0337] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0338] Auxiliary information.

[0339] It is understandable that the information indicated by different indicators in N or M indicator items can be the same or different. If the information indicated by different indicators in N or M indicator items is the same, it means that each indicator item includes the same content. However, the values ​​of each content in different indicator items are different. For example, each indicator item may include time reference point information, target SBFD time domain element indication information, target duplex mode indication information, and auxiliary information; or, each indicator item may include time reference point and target duplex mode indication information.

[0340] The different information indicated by different indicators in N or M indicators means that at least two indicators in N or M indicators include different contents. For example, indicator 1 in N indicators only includes time reference point information, indicator 2 includes time reference point and target duplex mode indication information, and indicator 3 only includes auxiliary information, etc.

[0341] When the first device is a terminal and the second device is a network-side device, the first indication information is carried by DCI, MAC CE, DM-RS sequence or CSI-RS resources.

[0342] When the first device is a network-side device and the second device is a terminal, the first indication information is carried by UCI, MAC CE, DM-RS sequence, SRS resource or PRACH.

[0343] When the first device is a terminal and the second device is a network-side device, the second indication information is carried by UCI, MAC CE, DM-RS sequence, SRS resource or PRACH.

[0344] When the first device is a network-side device and the second device is a terminal, the second indication information is carried by DCI, MAC CE, DM-RS sequence or CSI-RS resources.

[0345] When the first indication information is carried by DCI, the time reference point information includes any one of the following:

[0346] The start time of transmission scheduled by DCI;

[0347] The earliest start time of transmission scheduled by DCI;

[0348] The start time of the time slot in which the DCI-scheduled transmission occurs;

[0349] The start time of the time slot where the earliest transmission in the DCI schedule is located;

[0350] The time determined based on the first moment and the first predefined duration is any one of the following: the start time of the DCI, the end time of the DCI, the start time of the time slot where the DCI is located, the end time of the time slot where the DCI is located, the start time of the next time slot of the time slot where the DCI is located, and the end time of the next moment of the time slot where the DCI is located.

[0351] Taking the SBFD time domain unit as an SBFD symbol as an example, when the DCI schedules only a single transmission, the time reference point here is the start time of the first Symbol occupied by this transmission; when the DCI schedules multiple transmissions, the time reference point here is the start time of the first Symbol occupied by the transmission with the earliest start time.

[0352] The first predefined duration can be specified by the protocol or configured by higher-level signaling; alternatively, the first predefined duration can be directly indicated in the DCI, or indicated by one of the durations in the configuration list of higher-level signaling.

[0353] Optionally, the UE's processing capacity can be considered when determining the first predefined duration.

[0354] When the first or second indication information is carried by UCI, DM-RS sequence, CSI-RS resource, SRS resource, or PRACH, the time reference point information includes any one of the following:

[0355] The third moment;

[0356] The time is determined based on the third moment and the third predefined duration.

[0357] Alternatively, the third time step can be any of the following:

[0358] The start time of the target channel or target signal;

[0359] The end time of the target channel or target signal;

[0360] The start time of the time slot where the target channel or target signal is located;

[0361] The end time of the time slot where the target channel or target signal is located;

[0362] The start time of the next time slot after the time slot where the target channel or target signal is located;

[0363] The end time of the next time slot following the time slot where the target channel or target signal is located.

[0364] Optionally, the target channel is any one of the following: the PUCCH or PUSCH where the UCI is located; the PDCCH, PDSCH, PUCCH or PUSCH where the DM-RS sequence is located; or the PRACH.

[0365] Optionally, the target signal is a CSI-RS resource or an SRS resource.

[0366] Optionally, the third predefined duration can be specified by the protocol or configured by higher-level signaling; or, the third predefined duration can be directly indicated in the indication / request information, or indicate one of the durations in the duration list configured by higher-level signaling.

[0367] Optionally, when determining the third predefined duration, the processing capabilities of the UE or network-side equipment for decoding the target Channel / Signal and the application target Duplex mode are mainly considered.

[0368] When the first or second indication information is carried by the MAC CE, the time reference point information includes: a time determined based on a second time and a second predefined duration. Optionally, the second time is any one of the following:

[0369] The start time of the first shared channel transmission;

[0370] The end time of the first shared channel transmission;

[0371] The start time of the time slot in which the first shared channel transmission occurs;

[0372] The end time of the time slot in which the first shared channel transmission occurs;

[0373] The first shared channel transmission is the first shared channel transmission carrying the target transport block (TB); the target TB is the TB carrying the MAC CE.

[0374] The first shared channel is PXSCH. Downlink PXSCH transmission is PDSCH transmission, and uplink PXSCH transmission is PUSCH transmission.

[0375] When the first indication information / second indication information is carried by the MAC CE, the time reference point information can be: starting from the start / end time of the first PXSCH transmission of the TB carrying the MAC CE (or the start / end time of the time slot in which this first PXSCH transmission is located) + delta (e.g., a second predefined duration). Specifically, when the MAC CE is sent from the network-side device to the UE, the PXSCH is PDSCH; when the MAC CE is sent from the UE to the network-side device, the PXSCH is PUSCH.

[0376] Optionally, the second predefined duration can be specified by the protocol or configured by higher-layer signaling, mainly taking into account the latency of TB's Hybrid Automatic Repeat reQuest (HARQ) transmission, decoding and decapsulation, for example, 3ms.

[0377] Optionally, the determination of the above time reference point only applies to the case where N=1 (i.e., the request / instruction information contains only a single message n (n=0)), or the first message (i.e., message n (n=0)) included in the request / instruction information in the case where N>0. For any other message (i.e., message n (n>0)) included in the request / instruction information in the case where N>0, the time reference point can be explicitly indicated in message n, or it can be the end time of the previous message (i.e., message n-1) (for example, when using SBFD symbol indication method 1, it is the end time of the time window corresponding to message n; when using SBFD symbol indication method 2, it is the end time of the last SBFD symbol corresponding to message n, or the start time of the next SBFD symbol after this last SBFD symbol).

[0378] Optionally, the target SBFD time-domain element indication information includes any one of the following:

[0379] The number of at least one consecutive SBFD time-domain units;

[0380] Within the time range, all SBFD time-domain units within the time range adopt the indicated target duplex mode.

[0381] Taking the SBFD time domain unit as the SBFD symbol as an example, when indicating at least one consecutive SBFD symbol (i.e., the target SBFD symbol), one of the following SBFD symbol indication methods 1 and SBFD symbol indication method 2 can be used:

[0382] SBFD symbol indication mode 1: Indicates a time window length (or time range) within which all SBFD symbols (or all SBFD symbols configured as DL / Flexible symbols by TDD pattern configuration information) adopt the target Duplex mode.

[0383] The starting time of this time window is the time reference point. Optionally, a time interval can be indicated, which is the time interval between the starting time of this time window and the reference time point.

[0384] When indicating the duration of a time window, you can indicate it directly or indicate one of the durations in the list configured by higher-level signaling.

[0385] Optionally, the temporal granularity of the window length is one of the following:

[0386] System time-domain units, such as slot, sub-slot, symbol, etc.;

[0387] Absolute time units, such as ms (milliseconds), s (seconds), etc.

[0388] The duration of the cycle is determined based on the TDD pattern configuration information.

[0389] The period determined based on the TDD pattern configuration information refers to the period determined based on pattern1 (optionally, further including pattern2) in tdd-UL-DL-ConfigurationCommon and referenceSubcarrierSpacing.

[0390] Optionally, when it is desired that the time window will appear periodically in the future, another period can be applied, which is the time interval between the start or end times of two adjacent time windows. The length of this period can be specified by the protocol or configured by higher-layer signaling; or, the length of this period can be directly indicated in information n, or indicated by one of the durations in the duration list configured by higher-layer signaling.

[0391] Optionally, the number of times this time window occurs periodically can be further determined. This number can be specified by the protocol or configured by higher-level signaling; or, the number can be directly indicated in information n, or indicate one of the number of times configured by higher-level signaling.

[0392] Optionally, the number of consecutive SBFD symbols using the target Duplex mode within each time window can be indicated, assuming that only the first number of consecutive SBFD symbols in each time window use the target Duplex mode.

[0393] SBFD symbol indication mode 2: Indicates the number of consecutive SBFD symbols.

[0394] When indicating the number of consecutive SBFD symbols, you can directly indicate a value, or indicate one of the values ​​in the higher-level signaling configuration list. The value here must be a positive integer. The indicated value can be the number of consecutive SBFD symbols directly, or the indicated value can be multiplied by M (a positive integer) to obtain the number of consecutive SBFD symbols.

[0395] When information n does not indicate at least one consecutive SBFD symbol, it can be assumed that the end position of the consecutive SBFD symbols has not yet been determined. The target duplex mode can be applied to all SBFD symbols no earlier than the time reference point until the end position of the consecutive SBFD symbols is determined by subsequent signaling. Alternatively, when information n is enabled / activated, an effective duration timer can be started. When the timer expires, information n is considered no longer effective. In this case, the default or default duplex mode can be used for the SBFD symbols.

[0396] The target Duplex mode indicated in the first or second indication information can be gNB SBFD mode or UE SBFD mode.

[0397] Optionally, when the target duplex mode is UE SBFD mode, if the network-side device has configured multiple frequency domain patterns for the UE's UE SBFD mode, it can further indicate which of these multiple frequency domain patterns (assuming it is the target frequency domain pattern) to apply. This can be indicated by the ID of the target frequency domain pattern, or by its index / subscript in the list of configured frequency domain patterns. Optionally, when the target frequency domain pattern is not explicitly indicated, the target frequency domain pattern is the default frequency domain pattern, which can be specified by the protocol or configured by higher-layer signaling. When specified by the protocol, it can be the frequency domain pattern with the smallest / largest ID among the configured frequency domain patterns, or the frequency domain pattern whose index / subscript in the list of configured frequency domain patterns is a predefined value (e.g., 0).

[0398] Optionally, the auxiliary information in the first and second indication information may include at least one of the following:

[0399] When operating in target Duplex mode, the uplink Transmission Configuration Indication (TCI) state / spatial relation and / or downlink TCI state / quasi-colocation (QCL) assumption are applied.

[0400] The uplink power control parameters used when operating in the target Duplex mode include P0, Alpha, and maximum transmit power.

[0401] Generally, the network-side device's indication of Duplex mode, and the UE's indication / request of Duplex mode, can be determined based on the implementation. Optionally, the UE triggers the indication / request of Duplex mode only when at least one of the following predefined conditions is met:

[0402] The UE detects a change in the characteristics of the uplink / downlink service or at least one of the characteristics (see Rule 2-2 for a description of the uplink / downlink service characteristics), or the magnitude of the change is greater than or not less than a predefined threshold.

[0403] The UE detects a change in the on / off state of a specific uplink / downlink transmission (e.g., activation / deactivation of CG PUSCH Type 2 / SPS PDSCH) and / or attribute (e.g., the number / location of CG PUSCH / SPS PDSCH frequency domain resources), or the magnitude of the change is greater than or not less than a predefined threshold.

[0404] The UE detects changes in channel / interference measurement results, such as Radio Resource Management (RRM) measurement, CSI measurement, Cross Link Interference (CLI) measurement, and self-interference measurement, or the magnitude of the change is greater than or not less than a predefined threshold.

[0405] Among them, RRM measurement results are, for example, Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ); CSI measurement results are, for example, Rank Indication (RI), Precoding Matrix Indicator (PMI), or Channel Quality Indicator (CQI), Layer 1 RSRP (L1-RSRP), Layer 1 RSRQ (L1-RSRQ); CLI measurement results are, for example, CLI Received Signal Strength Indicator (CLI-RSSI), CLI Sounding Reference Signal RSRP (CLI-SRS-RSRP).

[0406] In some implementations, after the first device receives the first indication information sent by the second device, the first device sends an acknowledgment message for the first indication information to the second device. This acknowledgment message is used to confirm the target Duplex mode sent by the second device.

[0407] When the first device is a UE and the second device is a network-side device, the UE sends confirmation information to the network-side device using any of the following methods:

[0408] When the first indication information is carried by DCI, the UE sends the HARQ acknowledgment information (i.e., HARQ-ACK) corresponding to the DCI to the network-side device;

[0409] The UE sends a confirmation MAC CE (Confirmation MAC CE) to the network-side device;

[0410] The UE sends an SRS to the network-side device;

[0411] The UE sends an aperiodic CSI (i.e., A-CSI) to the network-side equipment, and the A-CSI may carry acknowledgment information.

[0412] When the first indication information is carried by a DCI, assuming the DCI is a UE-specific DCI, the UE can provide the corresponding HARQ-ACK for this DCI. For example, when using a Type-2 codebook and the DCI does not schedule PDSCH, after correctly receiving this DCI, the UE will set the HARQ-ACK bit corresponding to this DCI in the provided Type-2 codebook to ACK.

[0413] When the first device is a network-side device and the second device is a UE, the network-side device sends confirmation information to the UE using any of the following methods:

[0414] The network-side device sends a confirmation MAC CE to the UE terminal;

[0415] The network-side device sends a UE-specific DCI or a group-common DCI to the UE without scheduling a PDSCH.

[0416] The network-side device sends downlink assignment information (DL assignment) or uplink grant information (UL grant) to the UE. The DL assignment or UL grant includes confirmation information, or is described as the network-side device explicitly indicating confirmation information through DL assignment or UL grant.

[0417] The network-side device sends a DL assignment or UL grant to the UE. The DL assignment includes the type of time-domain element of the scheduled PDSCH, and the UL grant includes the type of time-domain element of the scheduled PUSCH. This confirmation information is implicitly indicated by the type of time-domain element.

[0418] For example, confirmation information can be implicitly indicated by indicating the Symbol type of the scheduled PDSCH / PUSCH (e.g., the scheduled PDSCH / PUSCH occupies at least one SBFD symbol involved in the UE's Duplex mode indication, and the Duplex mode corresponding to the Symbol type indicated by the DL assignment / UL grant is the same as the Duplex mode indicated in the UE's Duplex mode indication for this at least one SBFD symbol).

[0419] Example 2

[0420] Figure 5This is a flowchart of a method for determining a duplex mode according to Embodiment 2 of this application. This method is applied to a second device, which can be a UE or a network-side device. Figure 5 As shown, the method provided in this embodiment includes the following steps.

[0421] S201. The second device sends a first indication message to the first device. The first indication message is used to indicate the target duplex mode used by the UE in the SBFD time domain unit. The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the UE can only perform uplink transmission or downlink transmission in the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the UE can perform uplink transmission and downlink transmission in the SBFD time domain unit at the same time.

[0422] The second device can be a UE or a network-side device. When the second device is a network-side device, the first device is a UE; when the second device is a UE, the second device is a network-side device.

[0423] The SBFD time-domain unit includes at least one continuous SBFD time-domain unit, and the target duplex mode used by the target SBFD time-domain unit can be either SBFD duplex mode one or SBFD duplex mode two.

[0424] In one implementation, the second device actively sends the first instruction information to the second device based on its own implementation.

[0425] In another implementation, before the second device sends the first instruction information to the first device, the second device receives a request message sent by the first device, which is used to request the duplex mode of the target SBFD time domain unit.

[0426] In one implementation, the request message includes second indication information, which indicates the target duplex mode that the SBFD time-domain unit expects to use.

[0427] In some implementations, the first instruction information includes N instruction items, where N is a positive integer, and each instruction item includes at least one of the following:

[0428] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0429] Target SBFD time-domain element indication information, used to indicate the target SBFD time-domain element, wherein the target SBFD time-domain element includes at least one consecutive SBFD time-domain element;

[0430] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0431] Auxiliary information.

[0432] In some implementations, the second instruction information includes M instruction items, where M is a positive integer, and each instruction item includes at least one of the following:

[0433] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0434] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0435] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0436] Auxiliary information.

[0437] Optionally, after the second device sends the first instruction information to the first device, the second device receives an acknowledgment message for the first instruction information sent by the first device. This acknowledgment message is used to confirm receipt of the target duplex mode or to confirm the use of the target duplex mode.

[0438] In this embodiment, the second device sends a first indication message to the first device. This first indication message indicates the target duplex mode used by the SBFD time domain unit. By sending the first indication message, the second device enables the first device to determine the target duplex mode used by the SBFD time domain unit based on the first indication message. The target duplex mode can be either SBFD duplex mode one or SBFD duplex mode two. This ensures that when the UE simultaneously supports SBFD duplex mode one and SBFD duplex mode two, the network-side device and the UE can determine and agree on the target duplex mode used by the UE in the SBFD time domain unit. This guarantees that the SBFD operation can be accurately and consistently executed synchronously on both sides, reliably achieving the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage.

[0439] The above embodiment one describes in detail the method executed on the first device side of this application, and this embodiment two describes in detail the method executed on the second device side. It should be understood that the first device side embodiment and the second device side embodiment correspond to each other, and similar descriptions can be referred to the first device side embodiment, which will not be repeated here.

[0440] Example 3

[0441] Figure 6This is a signaling flowchart of a duplex mode determination method provided in Embodiment 3 of this application. The duplex mode is indicated by the network-side device. This embodiment is mainly used to describe the signaling interaction between the UE and the network-side device. Figure 6 As shown, the method provided in this embodiment includes the following steps.

[0442] S301. The network-side device sends a first indication information to the UE, which is used to indicate the target duplex mode used by the SBFD time domain unit.

[0443] S302, The UE sends a confirmation message for the first instruction information to the network-side device.

[0444] S303, the UE determines the target duplex mode of the SBFD time domain unit based on the first indication information.

[0445] It should be noted that step S302 is an optional step. In some implementations, the UE may not send confirmation information for the first indication information to the network-side device, and the network-side device assumes that the UE has received the first indication information. When step S302 exists, steps S302 and S303 are not executed in any order. Step S302 can be executed before S303, or after S303, or steps S302 and S303 can be executed simultaneously.

[0446] S304. The UE performs channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode.

[0447] In this embodiment, the network-side device sends a first indication message to the UE, indicating the target duplex mode used by the target SBFD time domain unit. The UE determines the target duplex mode used by the target SBFD time domain unit based on the indication from the network-side device. The target duplex mode can be either SBFD duplex mode one or SBFD duplex mode two. This ensures that when the UE supports both SBFD duplex mode one and SBFD duplex mode two, the network-side device and the UE can determine the target duplex mode used by the UE in the SBFD time domain unit and understand it in a consistent manner. This ensures that the SBFD operation can be executed accurately and consistently on both sides synchronously, so as to reliably realize the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage.

[0448] Example 4

[0449] Figure 7 This is a signaling flowchart of a duplex mode determination method provided in Embodiment 4 of this application. The duplex mode is indicated by the UE. This embodiment is mainly used to describe the signaling interaction between the UE and the network-side equipment. Figure 7 As shown, the method provided in this embodiment includes the following steps.

[0450] S401, the UE sends a first indication message to the network-side device, which is used to indicate the target duplex mode used by the SBFD time domain unit.

[0451] S402. The network-side device sends a confirmation message for the first instruction information to the UE.

[0452] S403, the UE determines the target duplex mode of the SBFD time domain unit based on the first indication information.

[0453] It should be noted that step S402 is an optional step. In some implementations, the network-side device may not send confirmation information for the first indication information to the UE, and the UE assumes that the network-side device has received the first indication information. When step S402 exists, steps S402 and S403 are not executed in any order. Step S402 can be executed before S403, or after S403, or steps S402 and S403 can be executed simultaneously.

[0454] S404. The UE performs channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode.

[0455] In this embodiment, the UE sends a first indication message to the network-side device, indicating the target duplex mode used by the SBFD time domain unit. The network-side device determines the target duplex mode used by the SBFD time domain unit based on the UE's indication. The target duplex mode can be either SBFD duplex mode one or SBFD duplex mode two. This ensures that when the UE supports both SBFD duplex mode one and SBFD duplex mode two, the network-side device and the UE can determine the target duplex mode used by the UE in the SBFD time domain unit and understand it in a consistent manner. This ensures that the SBFD operation can be executed accurately and consistently on both sides synchronously, so as to reliably realize the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage.

[0456] Example 5

[0457] Figure 8 This is a signaling flowchart of a duplex mode determination method provided in Embodiment 5 of this application. The UE requests the duplex mode. This embodiment mainly describes the signaling interaction between the UE and the network-side equipment. Figure 8 As shown, the method provided in this embodiment includes the following steps.

[0458] S501, the UE sends a request message to the network-side device. The request message includes second indication information, which is used to indicate the target duplex mode that the SBFD time domain unit expects to use.

[0459] S502, The network-side device sends a first indication information to the UE. The first indication information is used to indicate the target duplex mode used by the SBFD time domain unit.

[0460] The network-side device determines the target duplex mode actually used by the SBFD time-domain unit based on the target duplex mode expected to be used by the UE's requested SBFD time-domain unit.

[0461] Optionally, the SBFD time-domain unit indicated in the second indication information is not exactly the same as or does not completely overlap with the SBFD time-domain unit indicated in the first indication information. For example, the network-side device only considers the request information reported by the terminal as one factor, and combines it with other factors that need to be considered to determine and indicate the duplex mode of at least one consecutive SBFD time-domain unit.

[0462] S503, the UE determines the target duplex mode used by the SBFD time domain unit based on the first instruction information.

[0463] S504. The UE performs channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode.

[0464] In this embodiment, the UE sends a request message to the network-side device. This request message is used to request the duplex mode of the SBFD time domain unit. Based on the UE's request information, the network-side device determines the target duplex mode used by the SBFD time domain unit and instructs it to the UE. The target duplex mode can be either SBFD duplex mode one or SBFD duplex mode two. This ensures that when the UE supports both SBFD duplex mode one and SBFD duplex mode two, the network-side device and the UE can determine the target duplex mode used by the UE in the SBFD time domain unit and understand it in a consistent manner. This ensures that the SBFD operation can be executed accurately and consistently on both sides synchronously, so as to reliably realize the performance benefits of SBFD operation, such as reduced uplink transmission latency and improved uplink coverage.

[0465] The duplex mode determination method provided in this application embodiment can be executed by a duplex mode determination entity. Pack Place The determination of duplex mode in this application embodiment. Device Taking the method for determining the duplex mode as an example, the duplex mode determination apparatus provided in the embodiments of this application is described.

[0466] This application provides a duplex mode determination device. As an example, the duplex mode determination device can be a communication device or a component in a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0467] The device for determining the duplex mode includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: a transceiver, pins, circuits, a bus, and a radio frequency unit.

[0468] For details, see Figure 9 When the duplex mode determination device is a first device (which may be a terminal or a network-side device) or a component of the first device, the duplex mode determination device 600 includes a processing module 601, used to determine the target duplex mode of the terminal in the SBFD time domain unit; and a transceiver module 602, used to perform channel and / or signal transmission and reception in the SBFD time domain unit according to the target duplex mode; wherein, the method of determining the target duplex mode includes at least one of the following: determining the target duplex mode according to a predefined rule; determining the target duplex mode according to the duplex mode indicated by a second device; wherein, the target duplex mode includes SBFD duplex mode one or SBFD duplex mode two, when the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission in the SBFD time domain unit at the same time, and when the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission in the SBFD time domain unit at the same time.

[0469] In some implementations, the processing module 601 is specifically used to: determine the target duplex mode based on the transmission configured and / or indicated within the SBFD time-domain unit.

[0470] In some implementations, the processing module 601 determines that the target duplex mode includes any one of the following:

[0471] When there is no configured and / or indicated downlink transmission in the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode one;

[0472] When there is no configured and / or indicated uplink transmission in the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode one;

[0473] When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two.

[0474] When a configured downlink or uplink transmission exists within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two.

[0475] Based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window, the duplex mode of the SBFD time domain unit occupied by the target CORESET is determined.

[0476] Based on the time-frequency position of the synchronization signal block SSB or CORESET#0, determine the duplex mode of the SBFD time domain unit occupied by the SSB or CORESET#0;

[0477] Based on the time-frequency location of the RO during a valid random access event, the duplex mode of the SBFD time domain unit occupied by the valid RO is determined.

[0478] In some implementations, when there is no configured and / or indicated downlink transmission within the SBFD time domain unit, determining the target duplex mode as SBFD duplex mode one includes:

[0479] When there is no configured and / or indicated downlink transmission in the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode one that supports uplink transmission.

[0480] In some implementations, when there is no configured and / or indicated uplink transmission within the SBFD time domain unit, determining the target duplex mode as SBFD duplex mode one includes:

[0481] When there is no configured and / or indicated uplink transmission in the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode one that supports downlink transmission.

[0482] In some implementations, when both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode two, including:

[0483] When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, and the uplink transmissions and / or the downlink transmissions satisfy a first condition, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two, wherein the condition includes at least one of the following:

[0484] The uplink transmission was determined to be illegal or not actually exist;

[0485] The downlink transmission was determined to be illegal or not actually existent.

[0486] In some implementations, the uplink transmission is determined to be illegal or not actually existent, including: the uplink transmission is determined to be illegal or not actually existent based on the frequency domain resources occupied by the uplink transmission and the frequency domain mode corresponding to the SBFD duplex mode two;

[0487] The downlink transmission is determined to be illegal or not actually existent, including:

[0488] The downlink transmission is determined to be illegal or not actually exist based on the frequency domain resources occupied by the downlink transmission and the frequency domain mode corresponding to the SBFD duplex mode two;

[0489] The frequency domain mode is used to indicate the frequency domain positions of the uplink sub-band, downlink sub-band, and guard band of the SBFD time domain unit.

[0490] In some implementations, when a configured downlink or uplink transmission exists within the SBFD time-domain unit, the target duplex mode is determined to be SBFD duplex mode two, including:

[0491] When the configured downlink or uplink transmission meets the second condition, the target duplex mode is determined to be the SBFD duplex mode two, wherein the second condition includes at least one of the following:

[0492] The configured downlink or uplink transmission corresponds to the target type;

[0493] The configured downlink or uplink transmission type belongs to the target type set;

[0494] The period of the configured downlink or uplink transmission does not exceed the second threshold;

[0495] The time-domain interval between adjacent transmission opportunities corresponding to the configured downlink or uplink transmission does not exceed the second threshold;

[0496] The maximum time-domain interval between adjacent transmission opportunities corresponding to the configured downlink or uplink transmission does not exceed the second threshold.

[0497] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the target CORESET based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window includes:

[0498] The target CORESET occupies an SBFD time domain unit that uses the SBFD duplex mode one that supports downlink transmission.

[0499] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the target CORESET based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window includes at least one of the following:

[0500] When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the first SBFD time domain unit adopts the SBFD duplex mode two.

[0501] When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode one, but not all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the first SBFD time domain unit adopts the SBFD duplex mode one.

[0502] When the target CORESET occupies at least a portion of the frequency domain resources in the first SBFD time domain unit, which are located outside the downlink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, it is determined that the first SBFD time domain unit falls back to the downlink time domain unit or adopts the first SBFD duplex mode.

[0503] Wherein, the first SBFD time domain unit is any one of the at least one SBFD time domain units occupied by the target CORESET.

[0504] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the SSB or CORESET#0 based on the time-frequency position of the synchronization signal block SSB or CORESET#0 includes:

[0505] It is determined that the SBFD time domain unit occupied by the SSB or CORESET#0 adopts the SBFD duplex mode one that supports downlink transmission.

[0506] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the SSB or CORESET#0 based on the time-frequency position of the synchronization signal block SSB or CORESET#0 includes at least one of the following:

[0507] When the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, it is determined that the second SBFD time domain unit adopts the second SBFD duplex mode.

[0508] When the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, but the frequency domain resources occupied are not all located in the downlink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, it is determined that the second SBFD time domain unit adopts the first SBFD duplex mode.

[0509] When at least a portion of the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are located outside the downlink subband corresponding to the frequency domain mode corresponding to the SBFD duplex mode one, the second SBFD time domain unit is determined to fall back to the downlink time domain unit.

[0510] Wherein, the second SBFD time domain unit is any one of the SBFD time domain units within at least one SBFD time domain unit occupied by the SSB or the CORESET#0.

[0511] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid random access opportunity (RO) includes:

[0512] The SBFD time domain unit occupied by the valid RO is determined to be in SBFD duplex mode one that supports uplink transmission.

[0513] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid random access opportunity (RO) includes:

[0514] The SBFD time domain unit occupied by the target valid RO is determined to be in SBFD duplex mode one that supports uplink transmission. The target valid RO is any valid RO among the valid ROs for which the terminal expects to transmit the random access channel PRACH.

[0515] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid random access opportunity (RO) includes at least one of the following:

[0516] When all the frequency domain resources occupied by all the valid ROs configured in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode of the second SBFD duplex mode, it is determined that the third SBFD time domain unit adopts the second SBFD duplex mode.

[0517] When all the frequency domain resources occupied by all the configured valid ROs in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, but the frequency domain resources occupied by all the configured valid ROs are not located in the uplink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, the third SBFD time domain unit is determined to adopt the first SBFD duplex mode.

[0518] The third SBFD time-domain unit is any SBFD time-domain unit configured with at least one valid RO.

[0519] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid random access opportunity (RO) includes at least one of the following:

[0520] When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode two.

[0521] When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode one, but the frequency domain resources occupied by the target valid RO are not all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode one.

[0522] Wherein, the target valid RO is any valid RO among the valid ROs for which the terminal expects to transmit PRACH.

[0523] In some implementations, determining the duplex mode of the SBFD time domain unit occupied by the valid RO based on the time-frequency location of the valid random access opportunity (RO) includes at least one of the following:

[0524] When a downlink transmission configured and / or indicated exists in the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts the SBFD duplex mode two;

[0525] When there is no configured and / or indicated downlink transmission in the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts the SBFD duplex mode one that supports uplink transmission;

[0526] When a downlink transmission is configured and / or indicated within the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts the SBFD duplex mode two;

[0527] When there is no configured and / or indicated downlink transmission in the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts the SBFD duplex mode one;

[0528] Wherein, the fourth SBFD time domain unit is any SBFD time domain unit configured with at least one valid RO, the fifth SBFD time domain unit is any SBFD time domain unit occupied by the target valid RO, and the target valid RO is any valid RO among the valid ROs for which the terminal expects to transmit PRACH.

[0529] In some implementations, the processing module 601 is specifically used to: determine the target duplex mode based on first information, wherein the first information is used to predict uplink and / or downlink transmissions within the SBFD time domain unit.

[0530] In some implementations, the first information includes the terminal's buffer status report (BSR), and determining the target duplex mode based on the first information includes at least one of the following:

[0531] When the terminal does not report BSR within the first time period, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the second time period in the future.

[0532] When the BSR reported by the terminal indicates that there is no uplink data to be transmitted or no uplink data to be transmitted that meets the predefined requirements, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the future third time period.

[0533] In some implementations, the first information includes characteristics of uplink and / or downlink services, and determining the target duplex mode based on the first information includes at least one of the following:

[0534] When the characteristics of the uplink and / or downlink services meet the preset third condition, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two.

[0535] When the characteristics of the uplink and / or downlink services do not meet the third condition, the SBFD time domain unit is determined to adopt the SBFD duplex mode one.

[0536] In some implementations, the characteristics of the uplink and / or downlink services include at least one of the service characteristics and quality of service (QoS) requirements;

[0537] The business characteristics include at least one of the following:

[0538] Size characteristics of business data packets;

[0539] Periodic characteristics of business data;

[0540] Data rate characteristics of business data;

[0541] The QoS requirements include at least one of the following: Packet Delay Budget (PDB), Packet Set Delay Budget (PSDB), Packet Error Rate (PER), and Packet Set Error Rate (PSER).

[0542] In some implementations, the transceiver module 602 is further configured to: receive first indication information sent by the second device, the first indication information being used to indicate the target duplex mode used by the SBFD time domain unit;

[0543] The processing module 601 is specifically used to: determine the target duplex mode of the SBFD time domain unit according to the first indication information.

[0544] In some implementations, the first indication information includes N indication items, where N is a positive integer, and each indication item includes at least one of the following:

[0545] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0546] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0547] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0548] Auxiliary information.

[0549] In some implementations, the transceiver module 602 is further configured to:

[0550] Before receiving the first indication information sent by the second device, a request message is sent to the second device, the request message being used to request the duplex mode of the SBFD time domain unit.

[0551] In some implementations, the request message includes second indication information, which indicates the target duplex mode that the SBFD time-domain unit expects to use.

[0552] In some implementations, the second indication information includes M indication items, where M is a positive integer, and each indication item includes at least one of the following:

[0553] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0554] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0555] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0556] Auxiliary information.

[0557] In some implementations, when the first device is a terminal and the second device is a network-side device, the first indication information is carried by downlink control information (DCI), media access control unit (MAC CE), demodulation reference signal (DM-RS) sequence, or channel state information reference signal (CSI-RS) resource.

[0558] When the first device is a network-side device and the second device is a terminal, the first indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources or physical random access channel PRACH.

[0559] In some implementations, when the first device is a terminal and the second device is a network-side device, the second indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources, or PRACH.

[0560] In some implementations, when the first indication information is carried by a DCI, the time reference point includes any one of the following:

[0561] The start time of transmission scheduled by DCI;

[0562] The earliest start time of transmission scheduled by DCI;

[0563] The start time of the time slot in which the DCI-scheduled transmission occurs;

[0564] The start time of the time slot where the earliest transmission in the DCI schedule is located;

[0565] The time determined based on the first moment and the first predefined duration is any one of the following: the start time of the DCI, the end time of the DCI, the start time of the time slot where the DCI is located, the end time of the time slot where the DCI is located, the start time of the next time slot of the time slot where the DCI is located, and the end time of the next moment of the time slot where the DCI is located.

[0566] In some implementations, when the first indication information or the second indication information is carried by a MAC CE, the time reference point includes: a time determined based on a second moment and a second predefined duration, wherein the second moment is any one of the following:

[0567] The start time of the first shared channel transmission;

[0568] The end time of the first shared channel transmission;

[0569] The start time of the time slot in which the first shared channel transmission occurs;

[0570] The end time of the time slot in which the first shared channel transmission occurs;

[0571] Wherein, the first shared channel transmission is the first shared channel transmission carrying the target transport block TB; the target TB is the TB carrying the MAC CE.

[0572] In some implementations, when the first indication information or the second indication information is carried by uplink control information UCI, DM-RS sequence, CSI-RS resource, SRS resource or PRACH, the time reference point includes any one of the following:

[0573] The third moment;

[0574] The time determined based on the third moment and the third predefined duration;

[0575] The third moment can be any one of the following:

[0576] The start time of the target channel or target signal;

[0577] The end time of the target channel or target signal;

[0578] The start time of the time slot where the target channel or target signal is located;

[0579] The end time of the time slot where the target channel or target signal is located;

[0580] The start time of the next time slot after the time slot where the target channel or target signal is located;

[0581] The end time of the next time slot following the time slot where the target channel or target signal is located;

[0582] The target channel is any one of the following:

[0583] The UCI is located in the PUCCH or PUSCH;

[0584] The DM-RS sequence is located in the PDCCH, PDSCH, PUCCH, or PUSCH.

[0585] PRACH;

[0586] The target signal is the CSI-RS resource or the SRS resource.

[0587] In some implementations, the target SBFD time-domain element indication information includes any one of the following:

[0588] The number of at least one consecutive SBFD time-domain units;

[0589] The time range in which the SBFD time domain units all adopt the indicated target duplex mode.

[0590] In some implementations, when the target duplex mode adopted by the target SBFD time domain unit is the SBFD duplex mode two, each of the indication items further includes: the target frequency domain mode corresponding to the SBFD duplex mode two, the identifier of the target frequency domain mode, or the index of the target frequency domain mode.

[0591] In some implementations, the transceiver module 602 is further configured to:

[0592] After receiving the first instruction information sent by the second device, a confirmation message for the first instruction information is sent to the second device.

[0593] In some implementations, when the first device is a terminal and the second device is a network-side device, the terminal sends the confirmation information to the network-side device using any of the following methods:

[0594] When the first indication information is carried by DCI, the terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) corresponding to the DCI to the network-side device.

[0595] The terminal sends a confirmation MAC CE to the network-side device;

[0596] The terminal sends an SRS to the network-side device;

[0597] The terminal sends an aperiodic CSI to the network-side device.

[0598] In some implementations, when the first device is a network-side device and the second device is a terminal, the network-side device sends the confirmation information to the terminal using any of the following methods:

[0599] The network-side device sends a MAC CE confirmation to the terminal.

[0600] The network-side device sends a UE-specific DCI or a group-general DCI that does not schedule PDSCH to the terminal.

[0601] The network-side device sends downlink allocation information or uplink authorization information to the terminal, and the downlink allocation information or uplink authorization information includes the confirmation information;

[0602] The network-side device sends downlink allocation information or uplink authorization information to the terminal. The downlink allocation information includes the type of time domain unit of the scheduled PDSCH, and the uplink authorization information includes the type of time domain unit of the scheduled PUSCH. The acknowledgment information is implicitly indicated by the type of the time domain unit.

[0603] The duplex mode determination device 600 in this embodiment determines the target duplex mode of the terminal within the SBFD time domain unit through the processing module 601, based on predefined rules or the duplex mode indicated by the second device. Specifically, when the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink or downlink transmission on the SBFD time domain unit at any given time; when the target duplex mode is SBFD duplex mode two, the terminal can perform both uplink and downlink transmission on the SBFD time domain unit at any given time. This allows the first device to determine the target duplex mode used by the UE in the SBFD time domain unit when the UE simultaneously supports both SBFD duplex mode one and SBFD duplex mode two.

[0604] See Figure 10 When the duplex mode determination device is a second device (which can be a terminal or a network-side device) or a component of the second device, the duplex mode determination device 700 includes a sending module 701, used to send first indication information to the first device. The first indication information is used to indicate the target duplex mode used by the terminal in the SBFD time domain unit. The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0605] In some implementations, the device 700 further includes a receiving module for receiving a request message sent by the first device, the request message being used to request the duplex mode of the SBFD time domain unit.

[0606] In some implementations, the request message includes second indication information, which indicates the target duplex mode that the SBFD time-domain unit expects to use.

[0607] In some implementations, the device 700 further includes a receiving module for receiving confirmation information of the first indication information sent by the first device.

[0608] In some implementations, the first indication information includes N indication items, where N is a positive integer, and each indication item includes at least one of the following:

[0609] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0610] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0611] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0612] Auxiliary information.

[0613] In some implementations, the second indication information includes M indication items, where M is a positive integer, and each indication item includes at least one of the following:

[0614] Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information;

[0615] The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element;

[0616] Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit;

[0617] Auxiliary information.

[0618] In some implementations, when the first device is a terminal and the second device is a network-side device, the first indication information is carried by downlink control information (DCI), media access control unit (MAC CE), demodulation reference signal (DM-RS) sequence, or channel state information reference signal (CSI-RS) resource.

[0619] When the first device is a network-side device and the second device is a terminal, the first indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources or physical random access channel PRACH.

[0620] In some implementations, when the first device is a terminal and the second device is a network-side device, the second indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources, or PRACH.

[0621] In some implementations, when the first indication information is carried by a DCI, the time reference point information includes any one of the following:

[0622] The start time of transmission scheduled by DCI;

[0623] The earliest start time of transmission scheduled by DCI;

[0624] The start time of the time slot in which the DCI-scheduled transmission occurs;

[0625] The start time of the time slot where the earliest transmission in the DCI schedule is located;

[0626] The time determined based on the first moment and the first predefined duration is any one of the following: the start time of the DCI, the end time of the DCI, the start time of the time slot where the DCI is located, the end time of the time slot where the DCI is located, the start time of the next time slot of the time slot where the DCI is located, and the end time of the next moment of the time slot where the DCI is located.

[0627] In some implementations, when the first indication information or the second indication information is carried by a MAC CE, the time reference point information includes: a time determined based on a second time and a second predefined duration, wherein the second time is any one of the following:

[0628] The start time of the first shared channel transmission;

[0629] The end time of the first shared channel transmission;

[0630] The start time of the time slot in which the first shared channel transmission occurs;

[0631] The end time of the time slot in which the first shared channel transmission occurs;

[0632] Wherein, the first shared channel transmission is the first shared channel transmission carrying the target transport block TB; the target TB is the TB carrying the MAC CE.

[0633] In some implementations, when the first indication information or the second indication information is carried by uplink control information UCI, DM-RS sequence, CSI-RS resource, SRS resource or PRACH, the time reference point includes any one of the following:

[0634] The third moment;

[0635] The time determined based on the third moment and the third predefined duration;

[0636] The third moment can be any one of the following:

[0637] The start time of the target channel or target signal;

[0638] The end time of the target channel or target signal;

[0639] The start time of the time slot where the target channel or target signal is located;

[0640] The end time of the time slot where the target channel or target signal is located;

[0641] The start time of the next time slot after the time slot where the target channel or target signal is located;

[0642] The end time of the next time slot following the time slot where the target channel or target signal is located;

[0643] The target channel is any one of the following:

[0644] The UCI is located in the PUCCH or PUSCH;

[0645] The DM-RS sequence is located in the PDCCH, PDSCH, PUCCH, or PUSCH.

[0646] PRACH;

[0647] The target signal is the CSI-RS resource or the SRS resource.

[0648] In some implementations, the target SBFD time-domain element indication information includes any one of the following:

[0649] The number of at least one consecutive SBFD time-domain units;

[0650] The time range in which the SBFD time domain units all adopt the indicated target duplex mode.

[0651] In some implementations, when the target duplex mode adopted by the target SBFD time domain unit is the SBFD duplex mode two, each of the indication items further includes: the target frequency domain mode corresponding to the SBFD duplex mode two, the identifier of the target frequency domain mode, or the index of the target frequency domain mode.

[0652] In some implementations, when the first device is a terminal and the second device is a network-side device, the terminal sends the confirmation information to the network-side device using any of the following methods:

[0653] When the first indication information is carried by DCI, the terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) corresponding to the DCI to the network-side device.

[0654] The terminal sends a confirmation MAC CE to the network-side device;

[0655] The terminal sends an SRS to the network-side device;

[0656] The terminal sends an aperiodic CSI to the network-side device.

[0657] In some implementations, when the first device is a network-side device and the second device is a terminal, the network-side device sends the confirmation information to the terminal using any of the following methods:

[0658] The network-side device sends a MAC CE confirmation to the terminal.

[0659] The network-side device sends a UE-specific DCI or a group-general DCI that does not schedule PDSCH to the terminal.

[0660] The network-side device sends downlink allocation information or uplink authorization information to the terminal, and the downlink allocation information or uplink authorization information includes the confirmation information;

[0661] The network-side device sends downlink allocation information or uplink authorization information to the terminal. The downlink allocation information includes the type of time domain unit of the scheduled PDSCH, and the uplink authorization information includes the type of time domain unit of the scheduled PUSCH. The acknowledgment information is implicitly indicated by the type of the time domain unit.

[0662] The duplex mode determination device 700 provided in this embodiment sends first indication information to a first device through a sending module. The first indication information is used to indicate the target duplex mode used by the terminal in the target SBFD time domain unit. This method enables the first device to determine the target duplex mode used by the terminal in the SBFD time domain unit when the terminal supports both SBFD duplex mode one and SBFD duplex mode two at the same time.

[0663] The duplex mode determination device provided in this application embodiment can achieve Figures 4 to 8 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0664] like Figure 11 As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instructions that can run on the processor 801. For example, when the communication device 800 is a first device, when the program or instructions are executed by the processor 801, they implement the various steps of the above-described duplex mode determination method embodiment and achieve the same technical effect. When the communication device 800 is a second device, when the program or instructions are executed by the processor 801, they implement the various steps of the above-described duplex mode determination method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0665] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figures 4-8 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the method embodiments on the first device side or the second device side described above. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 9 The device shown is for determining the duplex mode. Specifically, Figure 12 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0666] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0667] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 12 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0668] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0669] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0670] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0671] Processor 910 may include one or more processing units; optionally, processor 910 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0672] Wherein, when the terminal is a first device, the processor 910 is used for the terminal's target duplex mode within the SBFD time domain unit; the radio frequency unit 901 is used for performing channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode; wherein, the method for determining the target duplex mode includes at least one of the following:

[0673] The target duplex mode is determined according to predefined rules;

[0674] The target duplex mode is determined based on the duplex mode indicated by the network-side device;

[0675] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0676] When the terminal is a second device, the radio frequency unit 901 is used to: send first indication information to the network-side device, the first indication information being used to indicate the target duplex mode used by the terminal in the SBFD time domain unit; wherein the target duplex mode includes SBFD duplex mode one or SBFD duplex mode two, when the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time, when the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0677] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant descriptions of method embodiments one to five, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0678] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figures 5-8 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the first device-side or second device-side method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0679] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 10 The device for determining the duplex mode shown. For example... Figure 13As shown, the network-side device 1000 includes: an antenna 101, a radio frequency (RF) device 102, a baseband device 103, a processor 104, and a memory 105. The antenna 101 is connected to the RF device 102. In the uplink direction, the RF device 102 receives information through the antenna 101 and transmits the received information to the baseband device 103 for processing. In the downlink direction, the baseband device 103 processes the information to be transmitted and sends it to the RF device 102. The RF device 102 processes the received information and transmits it through the antenna 101.

[0680] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 103, which includes a baseband processor.

[0681] The baseband device 103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 13 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 105 via a bus interface to call the program or instructions in the memory 105 to execute the network-side device operations shown in the above method embodiment.

[0682] The network-side device may also include a network interface 106, such as a Common Public Radio Interface (CPRI).

[0683] When the network-side device is the first device, the processor 104 is used to determine the target duplex mode of the terminal within the subband non-overlapping full-duplex (SBFD) time domain unit; the radio frequency device 102 is used to perform channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode; wherein the method for determining the target duplex mode includes at least one of the following:

[0684] The target duplex mode is determined according to predefined rules;

[0685] The target duplex mode is determined according to the duplex mode indicated by the second device;

[0686] The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0687] When the network-side device is the second device, the radio frequency device 102 is used to send first indication information to the terminal. The first indication information is used to indicate the target duplex mode used by the terminal in the SBFD time domain unit. The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

[0688] Furthermore, the network-side device 1000 in this embodiment of the application also includes: a program or instructions stored in the memory 105 and executable on the processor 104, wherein the processor 104 calls the program or instructions in the memory 105 to execute. Figure 10 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0689] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figures 4-8 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0690] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0691] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the above. Figures 4-8 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0692] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0693] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the above. Figure 8-Figure 8 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0694] This application also provides a system comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the duplex mode determination method described above, and the network-side device can be used to perform the steps of the duplex mode determination method described above.

[0695] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0696] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0697] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for determining a duplex mode, characterized in that, include: The first device determines the target duplex mode of the terminal within the subband non-overlapping full-duplex SBFD time domain unit; The first device performs channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode; The method for determining the target duplex mode includes at least one of the following: The target duplex mode is determined according to predefined rules; The target duplex mode is determined according to the duplex mode indicated by the second device; The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

2. The method according to claim 1, characterized in that, Determining the target duplex mode according to predefined rules includes: The target duplex mode is determined based on the transmission configured and / or indicated within the SBFD time-domain unit.

3. The method according to claim 2, characterized in that, The transmission based on the configuration and / or indication within the SBFD time domain unit determines the target duplex mode to include any one of the following: When there is no configured and / or indicated downlink transmission in the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode one; When there is no configured and / or indicated uplink transmission in the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode one; When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two. When a configured downlink or uplink transmission exists within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two. Based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window, the duplex mode of the SBFD time domain unit occupied by the target CORESET is determined. Based on the time-frequency position of the synchronization signal block SSB or CORESET#0, determine the duplex mode of the SBFD time domain unit occupied by the SSB or CORESET#0; Based on the time-frequency location of the RO during a valid random access event, the duplex mode of the SBFD time domain unit occupied by the valid RO is determined.

4. The method according to claim 3, characterized in that, When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two, including: When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, and the uplink transmissions and / or the downlink transmissions satisfy a first condition, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two, wherein the first condition includes at least one of the following: The uplink transmission was determined to be illegal or not actually exist; The downlink transmission was determined to be illegal or not actually existent.

5. The method according to claim 4, characterized in that, The uplink transmission is determined to be illegal or not actually existent, including: The uplink transmission is determined to be illegal or not actually exist based on the frequency domain resources occupied by the uplink transmission and the frequency domain mode corresponding to the SBFD duplex mode two; The downlink transmission is determined to be illegal or not actually existent, including: The downlink transmission is determined to be illegal or not actually exist based on the frequency domain resources occupied by the downlink transmission and the frequency domain mode corresponding to the SBFD duplex mode two; The frequency domain mode is used to indicate the frequency domain positions of the uplink sub-band, downlink sub-band, and guard band of the SBFD time domain unit.

6. The method according to claim 3, characterized in that, When a configured downlink or uplink transmission exists within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two, including: When the configured downlink or uplink transmission meets the second condition, the target duplex mode is determined to be the SBFD duplex mode two, wherein the second condition includes at least one of the following: The configured downlink or uplink transmission corresponds to the target type; The configured downlink or uplink transmission type belongs to the target type set; The period of the configured downlink or uplink transmission does not exceed the second threshold; The time-domain interval between adjacent transmission opportunities corresponding to the configured downlink or uplink transmission does not exceed the second threshold; The maximum time-domain interval between adjacent transmission opportunities corresponding to the configured downlink or uplink transmission does not exceed the second threshold.

7. The method according to claim 3, characterized in that, The determination of the duplex mode of the SBFD time domain unit occupied by the target CORESET based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window includes at least one of the following: The target CORESET occupies an SBFD time domain unit that uses the SBFD duplex mode one that supports downlink transmission; When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the first SBFD time domain unit adopts the SBFD duplex mode two. When the target CORESET occupies frequency domain resources within the first SBFD time domain unit, all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode one, but not all of which are located within the downlink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the first SBFD time domain unit adopts the SBFD duplex mode one. When the target CORESET occupies at least a portion of the frequency domain resources in the first SBFD time domain unit, which are located outside the downlink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, it is determined that the first SBFD time domain unit falls back to the downlink time domain unit or adopts the first SBFD duplex mode. Wherein, the first SBFD time domain unit is any one of the at least one SBFD time domain units occupied by the target CORESET.

8. The method according to claim 3, characterized in that, The determination of the duplex mode of the SBFD time domain unit occupied by the SSB or the CORESET#0 based on the time-frequency position of the synchronization signal block SSB or CORESET#0 includes at least one of the following: Determine that the SBFD time domain unit occupied by the SSB or CORESET#0 adopts the SBFD duplex mode one that supports downlink transmission; When the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, it is determined that the second SBFD time domain unit adopts the second SBFD duplex mode. When the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are all located in the downlink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, but the frequency domain resources occupied are not all located in the downlink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, it is determined that the second SBFD time domain unit adopts the first SBFD duplex mode. When at least a portion of the frequency domain resources occupied by the SSB or the CORESET#0 in the second SBFD time domain unit are located outside the downlink subband corresponding to the frequency domain mode corresponding to the SBFD duplex mode one, the second SBFD time domain unit is determined to fall back to the downlink time domain unit. Wherein, the second SBFD time domain unit is any one of the SBFD time domain units occupied by the SSB or the CORESET#0.

9. The method according to claim 3, characterized in that, The determination of the duplex mode of the SBFD time domain unit occupied by the effective RO based on the time-frequency location of the effective random access location includes at least one of the following: The SBFD time domain unit occupied by the effective RO is determined to be in SBFD duplex mode one that supports uplink transmission; The SBFD time domain unit occupied by the target valid RO is determined to be in SBFD duplex mode one that supports uplink transmission; When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode two. When the frequency domain resources occupied by the target valid RO are all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode one, but the frequency domain resources occupied by the target valid RO are not all located within the uplink subband corresponding to the frequency domain mode of the SBFD duplex mode two, it is determined that the SBFD time domain unit occupied by the target valid RO adopts the SBFD duplex mode one. Wherein, the target valid RO is any valid RO in the valid RO in which the terminal expects to transmit the random access channel PRACH.

10. The method according to claim 3, characterized in that, The determination of the duplex mode of the SBFD time domain unit occupied by the effective RO based on the time-frequency location of the effective random access location includes at least one of the following: When all the frequency domain resources occupied by all the valid ROs configured in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode of the second SBFD duplex mode, it is determined that the third SBFD time domain unit adopts the second SBFD duplex mode. When all the frequency domain resources occupied by all the configured valid ROs in the third SBFD time domain unit are located in the uplink subband corresponding to the frequency domain mode corresponding to the first SBFD duplex mode, but the frequency domain resources occupied by all the configured valid ROs are not located in the uplink subband corresponding to the frequency domain mode corresponding to the second SBFD duplex mode, the third SBFD time domain unit is determined to adopt the first SBFD duplex mode. When a downlink transmission configured and / or indicated exists in the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts the SBFD duplex mode two; When there is no configured and / or indicated downlink transmission in the fourth SBFD time domain unit, it is determined that the fourth SBFD time domain unit adopts the SBFD duplex mode one that supports uplink transmission; When a downlink transmission configured and / or indicated exists in the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts the SBFD duplex mode two; When there is no configured and / or indicated downlink transmission in the fifth SBFD time domain unit, it is determined that the fifth SBFD time domain unit adopts the SBFD duplex mode one; Wherein, the third SBFD time domain unit is any SBFD time domain unit configured with at least one valid RO, the fourth SBFD time domain unit is any SBFD time domain unit configured with at least one valid RO, the fifth SBFD time domain unit is any SBFD time domain unit occupied by the target valid RO, and the target valid RO is any valid RO among the valid ROs for which the terminal expects to transmit PRACH.

11. The method according to claim 1, characterized in that, Determining the target duplex mode according to predefined rules includes: Based on the first information, the target duplex mode is determined, and the first information is used to predict the uplink and / or downlink transmission within the SBFD time domain unit.

12. The method according to claim 11, characterized in that, The first information includes the terminal's buffer status report (BSR), and determining the target duplex mode based on the first information includes at least one of the following: When the terminal does not report BSR within the first time period, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the second time period in the future. When the BSR reported by the terminal indicates that there is no uplink data to be transmitted or no uplink data to be transmitted that meets the predefined requirements, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the future third time period.

13. The method according to claim 11, characterized in that, The first information includes the characteristics of uplink and / or downlink services, and determining the target duplex mode based on the first information includes at least one of the following: When the characteristics of the uplink and / or downlink services meet the preset third condition, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two. When the characteristics of the uplink and / or downlink services do not meet the third condition, the SBFD time domain unit is determined to adopt the SBFD duplex mode one.

14. The method according to claim 13, characterized in that, The characteristics of the uplink and / or downlink services include at least one of the service characteristics and QoS requirements; The business characteristics include at least one of the following: Size characteristics of business data packets; Periodic characteristics of business data; Data rate characteristics of business data; The QoS requirements include at least one of the following: Packet Delay Budget (PDB), Packet Set Delay Budget (PSDB), Packet Error Rate (PER), and Packet Set Error Rate (PSER).

15. The method according to claim 1, characterized in that, Determining the target duplex mode based on the duplex mode indicated by the second device includes: The first device receives a first indication message sent by the second device, the first indication message being used to indicate the target duplex mode used by the SBFD time domain unit; The first device determines the target duplex mode corresponding to the SBFD time domain unit based on the first indication information.

16. The method according to claim 15, characterized in that, The first instruction information includes N instruction items, where N is a positive integer, and each instruction item includes at least one of the following: Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information; The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element; Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit; Auxiliary information.

17. The method according to claim 1, 15, or 16, characterized in that, Before the first device receives the first indication information sent by the second device, the method further includes: The first device sends a request message to the second device, the request message being used to request the duplex mode of the SBFD time domain unit.

18. The method according to claim 17, characterized in that, The request message includes a second indication information, which is used to indicate the target duplex mode that the SBFD time domain unit expects to use.

19. The method according to claim 18, characterized in that, The second instruction information includes M instruction items, where M is a positive integer, and each instruction item includes at least one of the following: Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information; The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element; Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit; Auxiliary information.

20. The method according to claim 16 or 19, characterized in that, When the first device is a terminal and the second device is a network-side device, the first indication information is carried by downlink control information (DCI), media access control unit (MACCE), demodulation reference signal (DM-RS) sequence, or channel state information reference signal (CSI-RS) resource. When the first device is a network-side device and the second device is a terminal, the first indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources or physical random access channel PRACH.

21. The method according to claim 16 or 19, characterized in that, When the first device is a terminal and the second device is a network-side device, the second indication information is carried by uplink control information UCI, MAC CE, DM-RS sequence, SRS resources or PRACH.

22. The method according to claim 21, characterized in that, When the first indication information is carried by DCI, the time reference point information includes any one of the following: The start time of transmission scheduled by DCI; The earliest start time of transmission scheduled by DCI; The start time of the time slot in which the DCI-scheduled transmission occurs; The start time of the time slot where the earliest transmission in the DCI schedule is located; The time determined based on the first moment and the first predefined duration is any one of the following: the start time of the DCI, the end time of the DCI, the start time of the time slot where the DCI is located, the end time of the time slot where the DCI is located, the start time of the next time slot of the time slot where the DCI is located, and the end time of the next moment of the time slot where the DCI is located.

23. The method according to claim 20 or 21, characterized in that, When the first indication information or the second indication information is carried by a MAC CE, the time reference point information includes: a time determined based on a second time and a second predefined duration, wherein the second time is any one of the following: The start time of the first shared channel transmission; The end time of the first shared channel transmission; The start time of the time slot in which the first shared channel transmission occurs; The end time of the time slot in which the first shared channel transmission occurs; Wherein, the first shared channel transmission is the first shared channel transmission carrying the target transport block TB; the target TB is the TB carrying the MAC CE.

24. The method according to claim 20 or 21, characterized in that, When the first indication information or the second indication information is carried by uplink control information UCI, DM-RS sequence, CSI-RS resource, SRS resource or PRACH, the time reference point information includes any one of the following: The third moment; The time determined based on the third moment and the third predefined duration; The third moment can be any one of the following: The start time of the target channel or target signal; The end time of the target channel or target signal; The start time of the time slot where the target channel or target signal is located; The end time of the time slot where the target channel or target signal is located; The start time of the next time slot after the time slot where the target channel or target signal is located; The end time of the next time slot following the time slot where the target channel or target signal is located; The target channel is any one of the following: The UCI is located in the PUCCH or PUSCH; The DM-RS sequence is located in the PDCCH, PDSCH, PUCCH, or PUSCH. PRACH; The target signal is the CSI-RS resource or the SRS resource.

25. The method according to claim 16 or 19, characterized in that, The target SBFD time-domain element indication information includes any one of the following: The number of at least one consecutive SBFD time-domain units; The time range in which the SBFD time domain units all adopt the indicated target duplex mode.

26. The method according to claim 16 or 19, characterized in that, When the target duplex mode adopted by the target SBFD time domain unit is the SBFD duplex mode two, each of the indication items further includes: the target frequency domain mode corresponding to the SBFD duplex mode two, the identifier of the target frequency domain mode, or the index of the target frequency domain mode.

27. The method according to any one of claims 15-26, characterized in that, After the first device receives the first indication information sent by the second device, the method further includes: The first device sends a confirmation message of the first instruction information to the second device.

28. The method according to claim 27, characterized in that, When the first device is a terminal and the second device is a network-side device, the terminal sends the confirmation information to the network-side device using any of the following methods: When the first indication information is carried by DCI, the terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) corresponding to the DCI to the network-side device. The terminal sends a confirmation MAC CE to the network-side device; The terminal sends an SRS to the network-side device; The terminal sends an aperiodic CSI to the network-side device.

29. The method according to claim 27, characterized in that, When the first device is a network-side device and the second device is a terminal, the network-side device sends the confirmation information to the terminal using any of the following methods: The network-side device sends a MAC CE confirmation to the terminal. The network-side device sends a UE-specific DCI or a group-general DCI that does not schedule PDSCH to the terminal. The network-side device sends downlink allocation information or uplink authorization information to the terminal, and the downlink allocation information or uplink authorization information includes the confirmation information; The network-side device sends downlink allocation information or uplink authorization information to the terminal. The downlink allocation information includes the type of time domain unit of the scheduled PDSCH, and the uplink authorization information includes the type of time domain unit of the scheduled PUSCH. The acknowledgment information is implicitly indicated by the type of the time domain unit.

30. A method for determining a duplex mode, characterized in that, include: The second device sends a first indication message to the first device, the first indication message being used to indicate the target duplex mode used by the terminal in the SBFD time domain unit; The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

31. The method according to claim 30, characterized in that, Before the second device sends the first instruction information to the first device, it also includes: The second device receives a request message sent by the first device, the request message being used to request the duplex mode of the target SBFD time domain unit.

32. The method according to claim 31, characterized in that, The request message includes a second indication information, which is used to indicate the target duplex mode that the SBFD time domain unit expects to use.

33. The method according to any one of claims 30-32, characterized in that, After the second device sends the first instruction information to the first device, it also includes: The second device receives confirmation information of the first instruction information sent by the first device.

34. A device for determining a duplex mode, characterized in that, include: The processing module is used to determine the target duplex mode of the terminal within the subband non-overlapping full-duplex SBFD time domain unit: A transceiver module is used to perform channel and / or signal transmission and reception within the SBFD time domain unit according to the target duplex mode; The method for determining the target duplex mode includes at least one of the following: The target duplex mode is determined according to predefined rules; The target duplex mode is determined according to the duplex mode indicated by the second device; The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

35. The apparatus according to claim 34, characterized in that, The processing module is specifically used for: The target duplex mode is determined based on the transmission configured and / or indicated within the SBFD time-domain unit.

36. The apparatus according to claim 35, characterized in that, The processing module determines that the target duplex mode includes any one of the following: When there is no configured and / or indicated downlink transmission in the SBFD time domain unit, the target duplex mode is determined to be the SBFD duplex mode one; When there is no configured and / or indicated uplink transmission in the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode one; When both configured and / or indicated uplink transmissions and configured and / or indicated downlink transmissions exist simultaneously within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two. When a configured downlink or uplink transmission exists within the SBFD time domain unit, the target duplex mode is determined to be SBFD duplex mode two. Based on the time-frequency position of the target control resource set CORESET within the protected physical downlink control channel (PDCCH) monitoring window, the duplex mode of the SBFD time domain unit occupied by the target CORESET is determined. Based on the time-frequency position of the synchronization signal block SSB or CORESET#0, determine the duplex mode of the SBFD time domain unit occupied by the SSB or CORESET#0; Based on the time-frequency location of the RO during a valid random access event, the duplex mode of the SBFD time domain unit occupied by the valid RO is determined.

37. The apparatus according to claim 34, characterized in that, The processing module is specifically used for: Based on the first information, the target duplex mode is determined, and the first information is used to predict the uplink and / or downlink transmission within the SBFD time domain unit.

38. The apparatus according to claim 37, characterized in that, The first information includes the terminal's buffer status report (BSR). Based on the first information, the processing module determines the target duplex mode, including at least one of the following: When the terminal does not report BSR within the first time period, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the second time period in the future. When the BSR reported by the terminal indicates that there is no uplink data to be transmitted or no uplink data to be transmitted that meets the predefined requirements, it is determined that the SBFD time domain unit adopts the SBFD duplex mode one that supports downlink transmission, and the SBFD time domain unit is any SBFD time domain unit in the future third time period.

39. The apparatus according to claim 37, characterized in that, The first information includes the characteristics of uplink and / or downlink services. Based on the first information, the processing module determines the target duplex mode, including at least one of the following: When the characteristics of the uplink and / or downlink services meet the preset third condition, it is determined that the SBFD time domain unit adopts the SBFD duplex mode two. When the characteristics of the uplink and / or downlink services do not meet the third condition, the SBFD time domain unit is determined to adopt the SBFD duplex mode one.

40. The apparatus according to claim 34, characterized in that, The transceiver module is also used for: Receive first indication information sent by the second device, the first indication information being used to indicate the target duplex mode used by the SBFD time domain unit; The processing module is specifically used to: determine the target duplex mode corresponding to the SBFD time domain unit based on the first indication information.

41. The apparatus according to claim 40, characterized in that, The first instruction information includes N instruction items, where N is a positive integer, and each instruction item includes at least one of the following: Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information; The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element; Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit; Auxiliary information.

42. The apparatus according to claim 34, 40 or 41, characterized in that, The transceiver module is also used for: Before receiving the first indication information sent by the second device, a request message is sent to the second device, the request message being used to request the duplex mode of the SBFD time domain unit.

43. The apparatus according to claim 42, characterized in that, The request message includes a second indication information, which is used to indicate the target duplex mode that the SBFD time domain unit expects to use.

44. The apparatus according to claim 43, characterized in that, The second instruction information includes M instruction items, where M is a positive integer, and each instruction item includes at least one of the following: Time reference point information is used to determine the start time of the application target SBFD time domain unit indication information; The target SBFD time-domain element indication information is used to indicate the target SBFD time-domain element, which includes at least one consecutive SBFD time-domain element; Target duplex mode indication information is used to indicate the target duplex mode adopted by the target SBFD time domain unit; Auxiliary information.

45. The apparatus according to any one of claims 40-44, characterized in that, The transceiver module is also used for: After receiving the first instruction information sent by the second device, a confirmation message for the first instruction information is sent to the second device.

46. ​​A device for determining a duplex mode, characterized in that, include: The sending module is used to send first indication information to the first device, wherein the first indication information is used to indicate the target duplex mode used by the terminal in the SBFD time domain unit; The target duplex mode includes SBFD duplex mode one or SBFD duplex mode two. When the target duplex mode is SBFD duplex mode one, the terminal can only perform uplink transmission or downlink transmission on the SBFD time domain unit at the same time. When the target duplex mode is SBFD duplex mode two, the terminal can perform uplink transmission and downlink transmission on the SBFD time domain unit at the same time.

47. The apparatus according to claim 46, characterized in that, Also includes: The receiving module is used to receive a request message sent by the first device, the request message being used to request the duplex mode of the SBFD time domain unit.

48. The apparatus according to claim 47, characterized in that, The request message includes a second indication information, which is used to indicate the target duplex mode that the SBFD time domain unit expects to use.

49. The apparatus according to any one of claims 46-48, characterized in that, Also includes: The receiving module is used to receive confirmation information of the first indication information sent by the first device.

50. A communication device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining a duplex mode as described in any one of claims 1 to 29.

51. A communication device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining a duplex mode as described in any one of claims 30 to 33.

52. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions, which, when executed by a processor, implement the method for determining a duplex mode as described in any one of claims 1-29, or implement the steps of the method for determining a duplex mode as described in any one of claims 30-33.

Images