Time domain unit type determining method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses a time domain unit type determining method and apparatus, a terminal, and a network side device. The time domain unit type determining method in embodiments of the present application comprises: when a terminal supports full-duplex operation, on the basis of first information, the terminal determines a time domain unit type corresponding to a target time domain unit, wherein the time domain unit type comprises any one of the following: a first time domain unit type, used for indicating that the terminal and a network side device only perform downlink transmission or uplink transmission in the target time domain unit; a second time domain unit type, used for indicating that the terminal only performs downlink transmission or uplink transmission in the target time domain unit and the network side device performs downlink transmission and uplink transmission at the same time in the target time domain unit; and a third time domain unit type, used for indicating that the terminal and the network side device perform downlink transmission and uplink transmission at the same time in the target time domain unit.

Description

Time domain unit type determination method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

[0003] The present application belongs to the field of communication technology, and specifically relates to a method, apparatus, terminal, and network-side equipment for determining a time domain unit type. Background Art

[0004] Currently, the network supports full-duplex mode, performing both uplink and downlink transmissions within a time domain unit. However, the terminal supports only half-duplex mode, allowing only uplink or downlink transmissions within a time domain unit. Due to full-duplex operation on the network and half-duplex operation on the terminal, transmission on the terminal within a given time domain unit can be either half-duplex on both the terminal and the network, or full-duplex on the network and half-duplex on the terminal, resulting in limited flexibility in terminal transmission.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method, apparatus, terminal, and network-side equipment for determining a time domain unit type, which can solve the problem of insufficient flexibility in the transmission mode of the terminal in related technologies.

[0007] In a first aspect, a method for determining a time-domain unit type is provided, comprising:

[0008] In the case where the terminal supports full-duplex operation, the terminal determines the time domain unit type corresponding to the target time domain unit according to the first information; wherein the first information includes at least one of the following: configuration and indication information of the network side device, and scheduling information of the target time domain unit;

[0009] The time domain unit type includes any of the following:

[0010] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0011] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0012] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0013] In a second aspect, a method for determining a time-domain unit type is provided, comprising:

[0014] The network side device sends first information to the terminal, where the first information is used by the terminal to determine the time domain unit type corresponding to the target time domain unit, and the first information includes at least one of the following: configuration and indication information of the network side device, and scheduling information of the target time domain unit;

[0015] The terminal is a terminal that supports full-duplex operation, and the time domain unit type includes any one of the following:

[0016] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0017] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0018] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0019] In a third aspect, a time domain unit type determination device is provided, which is applied to a terminal, and the device includes:

[0020] A determination module, configured to determine, when the terminal supports full-duplex operation, a time domain unit type corresponding to the target time domain unit based on first information; wherein the first information includes at least one of the following: configuration and indication information of a network-side device, and scheduling information of the target time domain unit;

[0021] The time domain unit type includes any of the following:

[0022] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0023] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0024] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0025] In a fourth aspect, a time domain unit type determination device is provided, which is applied to a network-side device, and the device includes:

[0026] A sending module, configured to send first information to a terminal, where the first information is used by the terminal to determine a time domain unit type corresponding to a target time domain unit, the first information including at least one of the following: configuration and indication information of a network-side device, and scheduling information of the target time domain unit;

[0027] The terminal is a terminal that supports full-duplex operation, and the time domain unit type includes any one of the following:

[0028] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0029] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0030] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

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

[0032] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to determine, when the terminal supports full-duplex operation, a time domain unit type corresponding to a target time domain unit based on first information; wherein the first information includes at least one of the following: configuration and indication information of a network-side device, and scheduling information of the target time domain unit; and the time domain unit type includes any one of the following:

[0033] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0034] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0035] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

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

[0037] In an eighth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to send first information to a terminal, the first information being used by the terminal to determine a time domain unit type corresponding to a target time domain unit, the first information including at least one of the following: configuration and indication information of the network-side device, and scheduling information of the target time domain unit; wherein the terminal is a terminal supporting full-duplex operation, and the time domain unit type includes any one of the following:

[0038] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0039] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0040] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

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

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

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

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

[0045] In an embodiment of the present application, when the terminal supports full-duplex operation, the terminal can determine the time domain unit type corresponding to the target time domain unit based on the configuration of the network side device, the indication information and at least one of the scheduling information of the target time domain unit, and then the terminal can select one of the first time domain unit type, the second time domain unit type and the third time domain unit type to perform corresponding transmission, which effectively improves the transmission flexibility of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0047] FIG2 is a flow chart of a method for determining a time domain unit type provided by an embodiment of the present application;

[0048] FIG3a is a schematic diagram of one scenario of a method for determining a time domain unit type provided in an embodiment of the present application;

[0049] FIG3 b is a second schematic diagram of a scenario of a method for determining a time domain unit type provided by an embodiment of the present application;

[0050] FIG3c is a third schematic diagram of a scenario of a method for determining a time domain unit type provided by an embodiment of the present application;

[0051] FIG3 d is a fourth schematic diagram of a scenario of a method for determining a time domain unit type provided in an embodiment of the present application;

[0052] FIG3e is a fifth schematic diagram of a scenario of a method for determining a time domain unit type provided in an embodiment of the present application;

[0053] FIG3f is a sixth schematic diagram of a scenario of a method for determining a time domain unit type provided in an embodiment of the present application;

[0054] FIG3g is a seventh schematic diagram of a scenario of a method for determining a time domain unit type provided in an embodiment of the present application;

[0055] FIG3h is an eighth schematic diagram of a scenario of a method for determining a time domain unit type provided by an embodiment of the present application;

[0056] FIG4 is a flow chart of another method for determining a time domain unit type provided by an embodiment of the present application;

[0057] FIG5 is a structural diagram of a time domain unit type determination device provided in an embodiment of the present application;

[0058] FIG6 is a structural diagram of another device for determining a time domain unit type provided in an embodiment of the present application;

[0059] FIG7 is a structural diagram of a communication device provided in an embodiment of the present application;

[0060] FIG8 is a structural diagram of a terminal provided in an embodiment of the present application;

[0061] FIG9 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0063] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

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

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

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

[0067] The following describes in detail the time domain unit type determination method, apparatus, terminal and other related devices provided in the embodiments of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0068] Please refer to Figure 2, which is a flow chart of a method for determining a time domain unit type provided by an embodiment of the present application, wherein the method is applied to a terminal. As shown in Figure 2, the method includes the following steps:

[0069] Step 201: When a terminal supports full-duplex operation, the terminal determines a time domain unit type corresponding to a target time domain unit according to first information.

[0070] The first information includes at least one of the following: configuration and instruction information of a network-side device, and scheduling information of the target time domain unit;

[0071] The time domain unit type includes any of the following:

[0072] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0073] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0074] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0075] It should be noted that the terminal supporting full-duplex operation may also refer to the terminal supporting full-duplex mode. The full-duplex operation or full-duplex mode means that the terminal can simultaneously perform downlink (DL) transmission and uplink (UL) transmission within one time unit.

[0076] In an embodiment of the present application, if the terminal supports full-duplex operation, the terminal can also switch to support half-duplex operation (within one time unit, the terminal can only perform uplink transmission or downlink transmission). It should be noted that when the terminal performs half-duplex operation, the network side device can be performing half-duplex operation (within one time unit, the network side device can only perform uplink transmission or downlink transmission) or performing full-duplex operation (within one time unit, the network side device can perform uplink transmission and downlink transmission at the same time). The following three transmission scenarios are involved in the embodiment of the present application: 1. Full-duplex on the terminal side and full-duplex on the network side; 2. Half-duplex on the terminal side and full-duplex on the network side; 3. Half-duplex on the terminal side and half-duplex on the network side. Under different transmission scenarios, the time domain unit type corresponding to the terminal in the target time domain unit is also different. Among them, in the scenario of half-duplex on the terminal side and half-duplex on the network side, the time domain unit type corresponding to the target time domain unit of the terminal (the first time domain unit type); in the scenario of half-duplex on the terminal side and full-duplex on the network side, the time domain unit type corresponding to the target time domain unit of the terminal (the second time domain unit type); in the scenario of full-duplex on the terminal side and full-duplex on the network side, the time domain unit type corresponding to the target time domain unit of the terminal (the third time domain unit type).

[0077] In an embodiment of the present application, if the terminal supports full-duplex operation, the terminal can determine the time domain unit type corresponding to the target time domain unit based on the first information. For example, the terminal may determine the time domain unit type corresponding to the target time domain unit based on the configuration or indication information of the network side device, such as the network side device directly configures or indicates the time domain unit type corresponding to the terminal in the target time domain unit. For example, if the network side device configures the time domain unit type of the terminal in the target time domain unit to be the first time domain unit type, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type. For another example, if the indication information sent by the network side device indicates that the time domain unit type of the terminal in the target time domain unit is the first time domain unit type, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type. Of course, the network side device may also configure or indicate that the time domain unit type of the terminal in the target time domain unit is the second time domain unit type or the third time domain unit type, which will not be listed in detail here.

[0078] Alternatively, the terminal may also determine the time domain unit type corresponding to the target time domain unit based on the scheduling information of the target time domain unit. For example, if the target time domain unit is configured to correspond to the third time domain unit type, the terminal may determine whether to switch to the second time domain unit type or the first time domain unit type based on the overlap between the dynamically scheduled time domain resources and the guard band (GB). Of course, the terminal determines the time domain unit type corresponding to the target time domain unit based on the scheduling information of the target time domain unit, and there may be other possible situations, which will be specifically described in subsequent embodiments and will not be listed in detail here.

[0079] In the solution provided in the embodiment of the present application, when the terminal supports full-duplex operation, the terminal can determine the time domain unit type corresponding to the target time domain unit based on the configuration of the network side device, the indication information and at least one of the scheduling information of the target time domain unit, and then the terminal can select one of the first time domain unit type, the second time domain unit type and the third time domain unit type to perform corresponding transmission, which effectively improves the transmission flexibility of the terminal, and because the terminal supports full-duplex operation, it helps the terminal to reduce latency and improve throughput.

[0080] Optionally, when the first information includes scheduling information of the target time domain unit, the terminal determines, according to the first information, a time domain unit type corresponding to the target time domain unit, including at least one of the following:

[0081] In the case of a semi-statically configured transmission with only one transmission direction on the target time domain unit, the terminal determines, according to whether the scheduling information schedules a dynamically scheduled transmission opposite to the semi-statically configured transmission direction, a time domain unit type corresponding to the target time domain unit;

[0082] When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamically scheduled transmission and the guard band GB;

[0083] When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, and the dynamically scheduled transmission is located in a subband in the same transmission direction under full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0084] When the scheduling information indicates that at least one of a dynamically scheduled transmission and a semi-statically configured transmission exists on the target time domain unit, the terminal determines, according to a transmission status of at least one of the dynamically scheduled transmission and the semi-statically configured transmission, a time domain unit type corresponding to the target time domain unit;

[0085] If the scheduling information indicates that there is a dynamically scheduled uplink transmission and a dynamically scheduled downlink transmission on the target time domain unit, and the dynamically scheduled uplink transmission is an uplink subband under the full-duplex operation of the terminal, and the dynamically scheduled downlink transmission is a downlink subband under the full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0086] In a case where the scheduling information is a cancellation indication for indicating cancellation of transmission, the terminal determines, according to the cancellation indication, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type;

[0087] When the scheduling information indicates that the target time domain unit has no dynamically scheduled transmission, the terminal determines that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type;

[0088] The first type is any one of the time-domain unit types, and the second type is one of the time-domain unit types that is different from the first type.

[0089] Optionally, the terminal may determine the time domain unit type corresponding to the target time domain unit based on the configuration of the network-side device.

[0090] Exemplarily, please refer to Figure 3a. The network-side device configures UE1 to be a full DL time domain unit type (the first time domain unit type) in the target time domain unit, and UE1 can only perform DL reception in the target time domain unit. The network-side device configures UE2 to be a full UL time domain unit type (the first time domain unit type) in the target time domain unit, and UE2 can only perform UL transmission in the target time domain unit. The network-side device configures UE3 to be a second time domain unit type in the target time domain unit (at this time, the scheduled or configured DL transmission resources need to be limited to the DL subband on the network side, and the scheduled or configured UL transmission resources need to be limited to the UL subband on the network side. The DL subband or UL subband on the network side is also a subband for reception or transmission configured or indicated by the network to the terminal. In order to distinguish it from the full-duplex subband on the terminal side, it is referred to as the DL subband or UL subband on the network side. In this target time domain unit, UE3 can only perform UL transmission or DL ​​reception. The network-side device configures UE4 and UE5 to use the third time domain unit type in the target time domain unit (at this time, the scheduled or configured DL transmission resources need to be limited to the DL subband on the UE side, and the scheduled or configured UL transmission resources need to be limited to the UL subband on the UE side. The DL subband and UL subband here are for full-duplex operation on the terminal side, and are configured by the network side, referred to as UE-side subbands). Within this target time domain unit, UE4 or UE5 can perform UL transmission in the UL subband and DL reception in the DL subband. Among them, the GBs of UE4 and UE5 may be different, which may be related to UE capabilities.

[0091] In the embodiment of the present application, the network side device can configure different time domain unit types for the terminal to meet the different delay requirements and throughput requirements of the terminal.

[0092] Optionally, the method further includes:

[0093] The terminal receives a target configuration parameter of the time domain unit type, where the target configuration parameter includes at least one of the following:

[0094] a first configuration parameter, the first configuration parameter corresponding to the first time-domain unit type;

[0095] a second configuration parameter, the second configuration parameter corresponding to the second time-domain unit type;

[0096] A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

[0097] Exemplarily, the network-side device can configure corresponding configuration parameters for different time domain unit types. The target configuration parameters include downlink transmission parameters and uplink transmission parameters for dynamic or semi-static transmission or reception, as well as measurement. It should be noted that the first configuration parameter, the second configuration parameter, and the third configuration parameter can be different or the same.

[0098] For example, for a time domain unit configured as a first time domain unit type, which is a DL, UL or flexible time domain unit (slot or symbol), the network side device can configure first configuration parameters for the UE, including associated DL transmission parameters and UL transmission parameters, for dynamic or semi-static transmission or reception, and measurement. For example, the network side device can configure semi-static semi-persistent scheduling (SPS) transmission and channel state information reference signal (CSI-RS) reception for the UE based on the first configuration parameters; the network side device can configure semi-static configured grant (CG) transmission and sounding reference signal (SRS) transmission and corresponding power control parameters for the UE based on the first configuration parameters.

[0099] For a time domain unit configured as the second time domain unit type, the network-side device may configure second configuration parameters for the UE, including associated DL transmission parameters and UL transmission parameters, for dynamic or semi-static transmission or reception, and measurement. For example, the network-side device may configure the UE with semi-static SPS transmission and CSI-RS reception based on the second configuration parameters; and may configure the UE with semi-static CG transmission and SRS transmission and corresponding power control parameters based on the second configuration parameters.

[0100] For a time domain unit configured as the third time domain unit type, the network-side device may configure third configuration parameters for the UE, including associated DL transmission parameters and UL transmission parameters, for dynamic or semi-static transmission or reception, and measurement. For example, the network-side device may configure the UE with semi-static SPS transmission and CSI-RS reception based on the third configuration parameters; and may configure the UE with semi-static CG transmission and SRS transmission and corresponding power control parameters based on the third configuration parameters.

[0101] Optionally, for terminals that support full-duplex operation, the time domain and frequency domain resources for full-duplex operation can be configured by the network side equipment, such as the period of the time domain resources and whether each time slot (slot) and / or symbol within the period is full-duplex operation on the network side or full-duplex operation on the terminal side, so that the network side equipment can configure the time domain unit type corresponding to different time slots and / or symbols of the terminal.

[0102] As shown in Figure 3b, the network side device configures slot 3 and slot 9 for the UE as the second time domain unit type. In these time slots, the network side device can apply full-duplex operation, and the UE side applies half-duplex operation; the network side device configures slot 1, slot 4, and slot 6 for the UE as the third time domain unit type. In these time slots, the network side device applies full-duplex operation, and the UE side applies full-duplex operation; for other slots, such as slot 0, slot 2, slot 5, slot 7, and slot 8, the UE performs half-duplex operation (corresponding to the first time domain unit type). In these time slots, they are full DL or full UL or flexible slots (according to the tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated indication), and can serve legacy UEs.

[0103] Optionally, the terminal may also receive indication information sent by the network-side device, and determine the time domain unit type corresponding to the target time domain unit based on the indication information.

[0104] For example, the network-side device can dynamically indicate the time domain unit type for the terminal. For a UE that supports full-duplex, the network-side device can dynamically instruct the UE to switch between different time domain unit types, such as indicating whether the time domain unit type is the first time domain unit type, the second time domain unit type, or the third time domain unit type.

[0105] Optionally, the indication information includes at least one of the following:

[0106] UE-specific downlink control information (DCI);

[0107] Group common DCI (group common DCI).

[0108] Optionally, the dedicated DCI or group common DCI includes a time domain unit type indication field, and the time domain unit type indication field is used to indicate the time domain unit type corresponding to the target time domain unit.

[0109] For example, for UE-specific DCI, the network side device may add a time domain unit type indication field in the UE's scheduling DCI or dedicated DCI, which may indicate a time domain unit type corresponding to a target time domain unit configured or indicated by the network side. The target time domain unit may be at least one of the following:

[0110] Scheduling time domain resources;

[0111] The slot or subslot where the scheduled time domain resource is located;

[0112] A time length configured by the network, for example, from the start symbol of the scheduled time domain resource to the next n symbols or time slot length, where n is configured by the network;

[0113] The time domain resource is scheduled from the start time of the slot or subslot to the length of m symbols or time slots thereafter, where m is configured by the network.

[0114] Exemplarily, the dedicated DCI or group common DCI may add 2 bits as a time domain unit type indication field. For example, the dedicated DCI or group common DCI may indicate different time domain unit types through different indexes, as shown in Table 1 below:

[0115] Table 1. Indication of time domain unit type in DCI

[0116] As shown in Table 1 above, if the index carried in the proprietary DCI or group-common DCI (e.g., UE-specific DCI) is 00, it means that the DCI indicates the first time domain unit type; if the index carried in the proprietary DCI or group-common DCI is 01, the DCI indicates the second time domain unit type; if the index carried in the proprietary DCI or group-common DCI is 10, the DCI indicates the third time domain unit type.

[0117] It should be noted that the direction of the time domain unit may be determined according to the transmission direction of the scheduled resources. For example, if the scheduled resources are downlink transmissions, the direction of the time domain unit is also the downlink direction.

[0118] Optionally, the network side device may also configure a group common DCI to indicate (carry) the time domain unit type for a group of UEs to determine the time domain unit type, and the UE determines the time domain unit type of at least one time domain unit according to the indication of the group common DCI.

[0119] For example, the network-side device configures or indicates the time domain unit index that can perform full-duplex operation (terminal-side full-duplex or network-side full-duplex), and then uses the group-common DCI to update the time domain unit type. As shown in Figure 3b, the network-side device configures the time domain unit type corresponding to slot 1, slot 3, slot 4, slot 6, and slot 9 as a time slot that supports full-duplex operation. The network-side device can indicate through the group-common DCI, for example, 10110, indicating that the time domain unit type corresponding to slot 1, slot 4, and slot 6 is the third time domain unit type (supporting terminal-side full-duplex operation in these time slots), and the time domain unit type corresponding to slot 3 and slot 9 is the second time domain unit type (supporting network-side full-duplex operation in these time slots).

[0120] Optionally, when the indication information includes the group-common DCI, the group-common DCI satisfies at least one of the following:

[0121] The group common DCI includes at least one first index, where the first index is used to indicate a time domain unit type corresponding to at least one symbol, and the target time domain unit includes the at least one symbol;

[0122] The group common DCI includes at least one second index, where the second index is used to indicate a time domain unit type corresponding to at least one time slot, and the target time domain unit includes the at least one time slot.

[0123] Exemplarily, the network-side device may indicate the time domain unit type with a symbol as the granularity through the group common DCI.

[0124] As shown in the following table, the network side device can configure the group common DCI to include multiple indexes, and one index can be used to indicate the time domain unit type corresponding to multiple symbols:

[0125] Table 2. Different indices indicate the time domain unit type of the symbol

[0126] Here, D or U represents the first time domain unit type, gNB FD represents the second time domain unit type, and UE FD represents the third time domain unit type. Thus, a single index can indicate the time domain unit type corresponding to each symbol, while different indices can indicate the time domain unit types corresponding to multiple time slots.

[0127] For example, as shown in Figure 3c, the network-side device can indicate that slot 1 applies to index 0', slot 3 applies to index 1', slot 4 applies to index p', slot 6 applies to index k', and slot 9 applies to index n'. Taking slot 1' as an example, the time domain unit types corresponding to symbols 0 to 13 in this time slot are D, D, D, UE FD, UE FD, UE FD, UE FD, ... U (as shown in Table 3 below).

[0128] Optionally, the network side device may also indicate the time domain unit type with time slot as the granularity through the group common DCI.

[0129] As shown in Table 3 below, the network side device may configure the group common DCI to include multiple indexes, where one index may be used to indicate the time domain unit type corresponding to each of the multiple time slots:

[0130] Table 3. Indication of time domain unit type for different indexes of time slot

[0131] k' and m' are network-configurable. D or U represents the first time domain unit type, gNB FD represents the second time domain unit type, and UE FD represents the third time domain unit type. Thus, a single index can indicate the time domain unit type corresponding to different time slots.

[0132] Optionally, the group common DCI further includes a third index, and the third index is used to indicate at least one of the first indexes or at least one of the second indexes. In other words, the network side device can configure the third index, and the third index is used to indicate at least one of the first indexes or at least one of the second indexes.

[0133] For example, the third index is index A, and index A is used to indicate index 0, index 1, index p, index k, and index n; through index A, multiple first indexes can be indicated at the same time.

[0134] Optionally, the time domain unit type can be extended to indicate both network side full duplex and UE side full duplex. The network side device can be configured with a slot that performs only full-duplex operation, and indicates through an index whether each symbol in a slot performs UE side full duplex (third time domain unit type) or network side full duplex (second time domain unit type), as shown in Table 4 below:

[0135] Table 4. Index indication of time domain unit type for slots and symbols

[0136] Among them, gNB FD represents network-side full-duplex and the second time domain unit type, and UE FD represents UE-side full-duplex and the third time domain unit type.

[0137] Optionally, the network-side device may further configure a monitoring period and offset of the DCI (terminal-specific DCI and group-common DCI) carrying the time domain unit type indication.

[0138] Illustratively, the monitoring period may be [1, 2, 4, 5, 8, 10, 16, 20, 40, 80, 160, 320, 640, 1280, 2560] slot, or a symbol granularity, such as 2 symbols, 7 symbols, etc.

[0139] The size of the DCI carrying the time domain unit type indication can be the same as the size of other DCI payloads, for example, aligned with the time slot format indication (SFI) payload size, for example, a maximum of n bits, where n can be 128 bits. If a DCI carrying the time domain unit type indication does not match the aligned DCI payload size, padding bits can be used to achieve bit alignment. If the size of the DCI carrying the time domain unit type indication is the same as the size of other DCI, the network side can configure a Radio Network Temporary Identifier (RNTI) for scrambling the DCI, for example, using the time domain unit type indication RNTI for scrambling. The RNTI is used to distinguish the DCI carrying the time domain unit type indication from other DCIs of the same payload size.

[0140] In the embodiment of the present application, the terminal may also determine the time domain unit type according to whether there is dynamic scheduling in the opposite direction. The network may configure the terminal to activate or deactivate this behavior.

[0141] Optionally, the terminal determines, according to whether the scheduling information schedules a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission, a time domain unit type corresponding to the target time domain unit, including any one of the following:

[0142] If the terminal does not receive a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission, the terminal determines that the time domain unit type of the target time domain unit is switched from the first type to the second type;

[0143] If the terminal receives a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission direction, the terminal determines that the time domain unit type of the target time domain unit is not switched.

[0144] Alternatively, if the scheduling information indicates that there is dynamically scheduled uplink transmission and dynamically scheduled downlink transmission on the target time domain unit, and the dynamically scheduled uplink transmission is an uplink subband under the full-duplex operation of the terminal, and the dynamically scheduled downlink transmission is a downlink subband under the full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type.

[0145] For example, for a terminal that supports full-duplex operation, the network-side device configures the time domain unit type corresponding to the target slot of the terminal to be a third time domain unit type (the target time slot applies the third configuration parameter accordingly). If the terminal has only one semi-statically configured DL transmission in the target slot that falls within the downlink subband of the terminal's full-duplex operation, such as SPS Config 3 or CSI-RS Config 3, if the UE does not receive a dynamically scheduled UL transmission, the terminal switches to the second time domain unit type (the configuration parameter is switched to the second configuration parameter accordingly), for example, the UE receives according to SPS Config 2 or CSI-RS Config 2; if the UE receives a dynamically scheduled UL transmission that falls within the UL subband of the terminal's full-duplex operation, the UE does not switch the time domain unit type, so that the UE still maintains the third time domain unit type, and the UE still receives or sends according to the third configuration parameter.

[0146] Alternatively, for a terminal that supports full-duplex operation, if the network side device configures the terminal to use the first time domain unit type or the second time domain unit type corresponding to the target slot, if the terminal receives two dynamic schedules in opposite directions, such as receiving a dynamically scheduled uplink transmission and a dynamically scheduled downlink transmission, and the dynamically scheduled uplink transmission is the uplink subband under the full-duplex operation of the terminal, and the dynamically scheduled downlink transmission is the downlink subband under the full-duplex operation of the terminal, then the terminal switches to the third time domain unit type.

[0147] In an embodiment of the present application, when the terminal is configured with semi-static configuration transmission, it can determine the time domain unit type based on whether there is dynamic scheduling in the opposite direction, for example, it can flexibly switch the time domain unit type, effectively improving the terminal's transmission flexibility.

[0148] Alternatively, the terminal may also determine the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamically scheduled target time domain resources and the GB.

[0149] Optionally, when the scheduling information indicates that there is dynamic scheduling transmission on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamic scheduling transmission and the guard band GB, including any one of the following:

[0150] In a case where the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the frequency domain resources of the dynamically scheduled transmission overlap only with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the second time domain unit type;

[0151] In the case that the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the dynamically scheduled transmission is not located in the terminal side subband of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side subband of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side subband of the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, and the terminal performs the dynamically scheduled transmission.

[0152] Alternatively, when the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, and the dynamically scheduled transmission is located in the subband of the same transmission direction under the full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type.

[0153] For example, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit as the third time domain unit type. When the UE only receives dynamically scheduled DL transmission, the terminal determines the time domain unit type of the target time domain unit in the following cases:

[0154] 1) If a dynamically scheduled DL transmission (e.g., a physical downlink shared channel (PDSCH) or CSI-RS) falls on a DL subband on the UE side, the UE determines that the target time domain unit corresponds to a third time domain unit type, applies a third configuration parameter for reception in the target time domain unit, and receives the dynamically scheduled DL transmission;

[0155] 2) Referring to Figure 3f, when the UE is configured with the third time domain unit type and applies the third configuration parameters for transmission, if a dynamically scheduled DL transmission is received, and the frequency domain resources of the dynamically scheduled DL transmission (e.g., the dynamically scheduled PDSCH or CSI-RS) overlap only with the frequency domain resources between the GB on the network side and the DL subband on the UE side outside the DL subband on the UE side, then the UE determines that the target time domain unit is switched to the second time domain unit type, and the second configuration parameters can be applied for transmission in the target time domain unit;

[0156] 3) Please refer to Figures 3g(a) to (e). If the dynamically scheduled DL transmission (for example, the dynamically scheduled PDSCH or CSI-RS) is not located in the DL subband on the UE side, and the frequency domain resources of the dynamically scheduled DL transmission overlap with other frequency domain resources outside the DL subband on the UE side except the frequency domain resources between the GB on the network side and the DL subband on the UE side, for example, overlapping with the GB on the network side (for example, as shown in Figure 3g(a)), or overlapping with the frequency domain resources between the GB on the network side and the UL subband on the UE side (for example, as shown in Figure 3g(b)), or overlapping with the UL subband on the UE side (for example, as shown in Figure 3g(c) and (e)), or falling in the UE-side subband in the opposite direction (for example, as shown in Figure 3g(d)), etc., for situations other than 1) and 2) above, the UE determines that the target time domain unit corresponds to the first time domain unit type, and the first configuration parameters can be applied for transmission in the target time domain unit, and the dynamically scheduled DL transmission is received based on the first configuration parameters.

[0157] It should be noted that the above description is based on the example of dynamically scheduled DL transmission on the UE side. When the UE side receives dynamically scheduled UL transmission, the same mechanism as above can also be applied for processing.

[0158] Optionally, when the scheduling information indicates that at least one of dynamically scheduled transmission and semi-statically configured transmission exists on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the transmission status of at least one of the dynamically scheduled transmission and the semi-statically configured transmission, including at least one of the following:

[0159] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, and the scheduling information indicates that there is a semi-statically configured transmission in one transmission direction on the target time domain unit, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0160] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, and the scheduling information indicates that semi-static downlink transmission and semi-static uplink transmission exist on the target time domain unit, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0161] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that there are semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the terminal determines the time domain unit type corresponding to the target time domain unit based on the frequency domain resource position of the dynamic scheduling transmission.

[0162] For example, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit as the third time domain unit type. When the UE is only configured with semi-static DL transmission (such as SPS, PDSCH or CSI-RS), the UE determines that the target time domain unit is the third time domain unit type, and the UE can apply the third configuration parameters for receiving and sending.

[0163] Alternatively, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit as the third time domain unit type. When the UE is configured with semi-static DL transmission and semi-static UL transmission at the same time, the UE determines that the target time domain unit is the third time domain unit type, and the UE can apply the third configuration parameters for receiving and sending.

[0164] Optionally, the method further includes:

[0165] If the configured semi-persistent transmission overlaps with any GB or overlaps with a subband in the opposite transmission direction, the terminal discards the semi-persistent transmission or only transmits frequency domain resources within the terminal-side subband in the same transmission direction.

[0166] For example, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit to be the third time domain unit type. When the UE is only configured with semi-static DL transmission, if the semi-static DL transmission overlaps with any GB (GB on the network side or GB on the terminal side) or overlaps with the UL subband, the UE can choose to discard the semi-static DL transmission, or only transmit the frequency domain resources falling within the terminal side DL subband, for example, it can be based on rate matching or puncture for transmission.

[0167] Alternatively, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit to be the third time domain unit type. When the UE is configured with semi-static DL transmission and semi-static UL transmission at the same time, if the semi-static DL transmission overlaps with any GB (GB on the network side or GB on the terminal side), or the semi-static DL transmission overlaps with the UL subband, the terminal discards the semi-static DL transmission, or only transmits the frequency domain resources falling within the terminal side DL subband; or, if the semi-static UL transmission overlaps with any GB (GB on the network side or GB on the terminal side), or the semi-static UL transmission overlaps with the DL subband, the terminal discards the semi-static UL transmission, or only transmits the frequency domain resources falling within the terminal side UL subband.

[0168] It should be noted that, for the semi-static transmission that does not overlap with the GB and the sub-band in the opposite direction, the terminal may apply the third configuration parameter to receive or send the non-overlapping semi-static transmission.

[0169] Optionally, when the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that there is semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the terminal determines the time domain unit type corresponding to the target time domain unit according to the frequency domain resource position of the dynamic scheduling transmission, including any one of the following:

[0170] If the dynamically scheduled transmission is located in the terminal-side subband of the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type, and performs the dynamically scheduled transmission; as shown in Figure 3h, the terminal receives a dynamically scheduled DL transmission (e.g., a dynamically scheduled PDSCH or CSI-RS) in the target time domain unit. If the dynamically scheduled DL transmission is located in the DL subband on the UE side, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0171] If the frequency domain resources of the dynamically scheduled transmission overlap only with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the second time domain unit type, and discards the semi-static transmission;

[0172] If the dynamically scheduled transmission is not located in the terminal side sub-band of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side sub-band of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side sub-band of the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, the terminal performs the dynamically scheduled transmission, and discards the semi-static transmission.

[0173] For example, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit as the third time domain unit type. If the UE is configured with semi-static DL transmission and dynamically scheduled UL transmission at the same time, the UE determines that the time domain unit type corresponding to the target time domain unit may include the following cases:

[0174] 1) If the dynamically scheduled UL transmission falls within the UL subband on the UE side, the UE determines that the target time domain unit corresponds to the third time domain unit type, and the UE may apply the third configuration parameter for reception or transmission and perform the dynamically scheduled UL transmission;

[0175] 2) If the frequency domain resources of the dynamically scheduled UL transmission overlap only with the frequency domain resources between the GB on the network side and the UL subband on the UE side outside the UL subband on the UE side, the UE determines that the target time domain unit corresponds to the second time domain unit type, and the UE can apply the second configuration parameter for reception or transmission, and perform the dynamically scheduled UL transmission, and discard the semi-static DL transmission;

[0176] 3) If the dynamically scheduled UL transmission does not fall within the UL subband on the UE side, and the frequency domain resources of the dynamically scheduled UL transmission overlap with other frequency domain resources outside the UL subband on the UE side except the frequency domain resources between the GB on the network side and the UL subband on the UE side, such as overlapping with the GB on the network side, or overlapping with the DL subband on the UE side, etc., for other cases of dynamically scheduled UL transmission other than 1) and 2) above, the UE determines that the target time domain unit corresponds to the first time domain unit type, and the UE can apply the first configuration parameters for receiving or sending, and discard the semi-static DL transmission.

[0177] The frequency domain resources of the semi-static DL transmission at least partially overlap with the DL subband on the UE side, or completely fall within the DL subband.

[0178] Optionally, the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that the terminal has semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions. The method further includes any one of the following:

[0179] If the semi-static configuration transmission is located in the terminal-side subband of the same transmission direction, the terminal performs the semi-static configuration transmission;

[0180] If the semi-statically configured transmission partially overlaps with the terminal-side subband in the same transmission direction, the terminal discards the semi-statically configured transmission or only transmits frequency domain resources within the terminal-side subband in the same transmission direction.

[0181] For example, for the target time domain unit, the network side device configures the time domain unit type corresponding to the target time domain unit to the third time domain unit type. If the UE is configured with semi-static DL transmission and dynamically scheduled UL transmission at the same time, if the semi-static DL transmission is located in the DL subband on the UE side, the UE performs the semi-static DL transmission; if the semi-static DL transmission partially overlaps with the DL subband on the UE side, the UE discards the semi-static DL transmission, or transmits the transmission that falls within the DL subband on the UE side (which can be transmitted based on rate matching or puncture).

[0182] It should be noted that the above is only an example. When the UE is configured with semi-static UL transmission and dynamically scheduled DL transmission at the same time, the same mechanism as the above method can also be applied for processing.

[0183] In an embodiment of the present application, the UE can determine the time domain unit type corresponding to the target time domain unit based on the transmission status of at least one of the dynamic scheduling transmission and the semi-static configuration transmission, and determine the transmission behavior of the terminal based on the determined time domain unit type, thereby effectively improving the transmission flexibility of the terminal.

[0184] In an embodiment of the present application, when the terminal receives a cancellation instruction for instructing to cancel transmission, the terminal may also determine, based on the cancellation instruction, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type. For example, the network-side device may instruct the terminal to cancel transmission in one direction in the target time domain unit, and the terminal, upon receiving the instruction, deems that the time domain unit type of the time domain unit is switched from the first type to the second type.

[0185] It should be noted that the cancellation indication can be a group-common DCI or a UE-specific DCI. For example, the network-side device can configure a group-common DCI or a UE-specific DCI to cancel transmission in one direction. When the UE receives the DCI, it considers that the time domain unit type of the target time domain unit needs to be switched, for example, from the third time domain unit type to the second time domain unit type or the first time domain unit type. It should be noted that the DCI is used to indicate the cancellation of all UL transmissions or all DL transmissions of the target time domain unit.

[0186] Optionally, the cancellation indication is used to indicate at least one of the length and granularity of the target time domain unit for cancellation of transmission. Exemplarily, the network side device can configure or indicate the length and granularity of the target time domain unit. For example, the network side device indicates that the length of the target time domain unit is L, the granularity is M, and the target time domain unit is configured as the third time domain unit type. As shown in Figure 3d, assuming that M=3 (the first three parts of L), the cancellation indication is used to indicate the cancellation of UL transmission, then the first three parts of the target time domain unit are switched to the second time domain unit type, and the fourth part is still the third time domain unit type. Furthermore, by configuring the length and granularity of the target time domain unit through the network side device, the terminal can be more refined and flexible in switching the time domain unit type.

[0187] It should be noted that L may be a processing time length related to UE capabilities configured by a network-side device, for example, L=Tproc2+d, where Tproc2 is the UE PUSCH preparation time and d is a value related to UE capabilities.

[0188] Optionally, the terminal determining, according to the cancellation indication, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type includes:

[0189] The terminal determines, based on an overlap between the area indicated by the cancellation indication and the GB, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type.

[0190] For example, assuming that the cancellation indication is used to indicate the cancellation of the UL transmission of the target time domain unit, if the UL transmission overlaps with the GB on the network side, the UE that receives the cancellation indication considers that the time domain unit type of the target time domain unit is switched from the first type to the second type, for example, from the third time domain unit type to the first time domain unit type.

[0191] In an embodiment of the present application, the terminal may also determine the time domain unit type of the target time domain unit based on whether a dynamically scheduled transmission is received. Specifically, when the terminal receives indication information indicating that the target time domain unit does not have dynamically scheduled transmission, the terminal determines, based on the indication information, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type.

[0192] Exemplarily, when the terminal supports full-duplex operation, the network-side device may indicate or configure whether the time domain unit supporting full-duplex operation of the terminal has dynamically scheduled transmission. If the network-side device indicates that there is no dynamically scheduled transmission (including dynamically scheduled DL transmission or dynamically scheduled UL transmission) in the target time domain unit, the terminal considers that the time domain unit type of the target time domain unit is switched from the first type to the second type. Optionally, the indication information may be a group-common DCI or a UE-specific DCI, such as the network-side device may indicate that the target time domain unit has no dynamically scheduled transmission through a group-common DCI or a UE-specific DCI.

[0193] For example, please refer to Figure 3e. The network side device configures the time domain unit type corresponding to slot 1, slot 3, slot 4, slot 6, and slot 9 for the UE supporting full-duplex as the third time domain unit type. The network side device configures a group common DCI or UE-specific DCI for the UE to indicate whether a slot has UL scheduling or DL ​​scheduling. For example, for slot 3 and slot 9, the network side device indicates that there is no UL scheduling through the above DCI, then the UE can consider that these two time slots are switched from the third time domain unit type to the second time domain unit type, and use the second configuration parameters to receive DL transmission in these two time slots.

[0194] In the embodiment of the present application, by indicating whether the target time domain unit has a dynamically scheduled transmission in one direction, the terminal can determine the time domain unit type corresponding to the target time domain unit, thereby effectively improving the terminal's transmission flexibility.

[0195] In this embodiment of the present application, the frequency domain configuration corresponding to the full-duplex operation supported by the terminal satisfies at least one of the following:

[0196] The GB on the terminal side is the GB configured by the network side device for full-duplex operation on the terminal side;

[0197] The GB of the network side device is a GB configured by the network side device for full-duplex operation on the network side;

[0198] The sub-band on the terminal side is an uplink sub-band or a downlink sub-band configured by the network side device for full-duplex operation on the terminal side;

[0199] The sub-band of the network side device is an uplink sub-band or a downlink sub-band configured by the network side device for full-duplex operation on the network side;

[0200] The uplink subband size of the terminal side is a subset of the uplink subband size of the network side device;

[0201] The downlink subband size of the terminal side is a subset of the downlink subband size of the network side device;

[0202] The GB on the terminal side is a superset of the GB of the network side device.

[0203] For example, the network device may configure the UE-side UL subband frequency domain location to be the same as the network-side full-duplex UL subband frequency domain location. Rather than configuring a UE-specific UL subband frequency domain location for each UE, the network device may simply configure a UE-specific GB size (frequency domain location). It should be noted that configuring UE-specific UL subbands and UE-specific GBs by the network device is beneficial for supporting UEs with different bandwidth capabilities.

[0204] In the embodiment of the present application, the effective time of the time domain unit type is located after the last symbol of a first physical downlink control channel (PDCCH), and the first PDCCH is used to indicate the time domain unit type.

[0205] For the Physical Uplink Shared Channel (PUSCH) processing capability 2, the last symbol T′ proc,2It can be obtained according to the following formula: proc,2 =max((N2+d 2,1 )(2048+144)·κ2 -μ · T C ,d 2,2 )

[0206] Among them, T proc,2 is the last symbol interval, d offset The subcarrier spacing and minimum subcarrier configuration μ for PDCCH UL The minimum value of μ UL Provided by the scs-SpecificCarrierList parameter of the higher-layer parameter FrequencyInfoUL or FrequencyInfoUL-SIB. The UE does not expect to receive the last symbol interval T of the control resource set (CORESET) of the PDCCH carrying the time domain unit type. proc,2 (Assuming d 2,1 =0) before canceling PUSCH transmission or SRS transmission.

[0207] In the embodiment of the present application, the network side device may further configure the terminal to switch the time domain unit type of the target time domain unit from the first type to the second type when a predefined condition is met.

[0208] It should be noted that the UE may have some bursty UL services that the network-side device is unaware of. For example, when the network-side device schedules or configures DL transmission, if the UE needs to send a physical random access channel (PRACH), a scheduling request (SR) or a buffer status report (BSR) at the same time, for UEs that support full-duplex operation, the UE can be triggered to switch to the third time domain unit type through predefined conditions.

[0209] For example, for a target time domain unit configured as the second time domain unit type, if the frequency domain resources of the DL transmission scheduled or configured for the UE fall in the DL subband of the target time domain unit, or a semi-statically configured UL transmission such as PRACH, CG PUSCH, the frequency domain resources of the PUCCH configured to carry SR fall in the UL subband of the target time domain unit, then the terminal switches the target time domain unit from the second time domain unit type to the third time domain unit type.

[0210] The solution provided in the embodiment of the present application is that for a terminal supporting full-duplex operation, the terminal can determine the time domain unit type corresponding to the target time domain unit based on the above-mentioned multiple situations, so that the terminal can switch between different time domain unit types, effectively improving the terminal's transmission flexibility. Compared with a terminal that can only perform half-duplex operation, the terminal supporting full-duplex operation in the present application can also effectively improve system resource utilization and reduce latency.

[0211] Please refer to Figure 4, which is a flowchart of another method for determining the time domain unit type provided by an embodiment of the present application, and the method is applied to a network-side device. As shown in Figure 4, the method includes the following steps:

[0212] Step 401: A network-side device sends first information to a terminal, where the first information is used by the terminal to determine a time domain unit type corresponding to a target time domain unit.

[0213] The first information includes at least one of the following: configuration and instruction information of a network-side device, and scheduling information of the target time domain unit; the terminal is a terminal supporting full-duplex operation, and the time domain unit type includes any one of the following:

[0214] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0215] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0216] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0217] Optionally, the indication information is used to indicate at least one of the following:

[0218] The time domain unit type corresponding to the target time domain unit of the terminal;

[0219] canceling transmission in a target transmission direction, where the target transmission direction includes an uplink transmission direction and a downlink transmission direction;

[0220] The target time domain unit has no dynamically scheduled transmission.

[0221] Optionally, the method further includes:

[0222] The network-side device sends a target configuration parameter of the time domain unit type to the terminal, where the target configuration parameter includes at least one of the following:

[0223] a first configuration parameter, the first configuration parameter corresponding to the first time-domain unit type;

[0224] a second configuration parameter, the second configuration parameter corresponding to the second time-domain unit type;

[0225] A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

[0226] The method provided in the embodiment of the present application is applied to the network side device, which corresponds to the above-mentioned method applied to the terminal side. The relevant behaviors, specific execution processes and related concepts and principles of the network side device in the embodiment of the present application can be referred to the description in the above-mentioned terminal side method embodiment, and will not be repeated here.

[0227] In an embodiment of the present application, the network side device sends the first information to the terminal, so that the terminal can determine the time domain unit type of the target time domain unit based on the first information, thereby effectively improving the transmission flexibility of the terminal. If the terminal supports full-duplex operation and the network side device also supports full-duplex operation, the resource utilization of the system can be effectively improved.

[0228] The time domain unit type determination method provided in the embodiment of the present application can be executed by a time domain unit type determination device. In the embodiment of the present application, the time domain unit type determination device performing the time domain unit type determination method is used as an example to illustrate the time domain unit type determination device provided in the embodiment of the present application.

[0229] Please refer to Figure 5, which is a structural diagram of a time domain unit type determination device provided in an embodiment of the present application, wherein the device is applied to a terminal. As shown in Figure 5, the time domain unit type determination device 500 includes:

[0230] A determination module 501 is configured to determine, when the terminal supports full-duplex operation, a time domain unit type corresponding to a target time domain unit based on first information; wherein the first information includes at least one of the following: configuration and indication information of a network-side device, and scheduling information of the target time domain unit;

[0231] The time domain unit type includes any of the following:

[0232] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0233] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0234] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0235] Optionally, when the first information includes scheduling information of the target time domain unit, the determining module 501 is further configured to perform at least one of the following:

[0236] In the case of a semi-statically configured transmission with only one transmission direction on the target time domain unit, the terminal determines, according to whether the scheduling information schedules a dynamically scheduled transmission opposite to the semi-statically configured transmission direction, a time domain unit type corresponding to the target time domain unit;

[0237] When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamically scheduled transmission and the guard band GB;

[0238] When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, and the dynamically scheduled transmission is located in a subband in the same transmission direction under full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0239] When the scheduling information indicates that at least one of a dynamically scheduled transmission and a semi-statically configured transmission exists on the target time domain unit, the terminal determines, according to a transmission status of at least one of the dynamically scheduled transmission and the semi-statically configured transmission, a time domain unit type corresponding to the target time domain unit;

[0240] If the scheduling information indicates that there is a dynamically scheduled uplink transmission and a dynamically scheduled downlink transmission on the target time domain unit, and the dynamically scheduled uplink transmission is an uplink subband under the full-duplex operation of the terminal, and the dynamically scheduled downlink transmission is a downlink subband under the full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0241] In a case where the scheduling information is a cancellation indication for indicating cancellation of transmission, the terminal determines, according to the cancellation indication, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type;

[0242] When the scheduling information indicates that the target time domain unit has no dynamically scheduled transmission, the terminal determines that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type;

[0243] The first type is any one of the time-domain unit types, and the second type is one of the time-domain unit types that is different from the first type.

[0244] Optionally, the indication information includes at least one of the following:

[0245] Terminal-specific downlink control information DCI;

[0246] Group common DCI.

[0247] Optionally, the dedicated DCI or the group common DCI includes a time domain unit type indication field, and the time domain unit type indication field is used to indicate the time domain unit type corresponding to the target time domain unit.

[0248] Optionally, when the indication information includes the group-common DCI, the group-common DCI satisfies at least one of the following:

[0249] The group common DCI includes at least one first index, where the first index is used to indicate a time domain unit type corresponding to at least one symbol, and the target time domain unit includes the at least one symbol;

[0250] The group common DCI includes at least one second index, where the second index is used to indicate a time domain unit type corresponding to at least one time slot, and the target time domain unit includes the at least one time slot.

[0251] Optionally, the group common DCI further includes a third index, and the third index is used to indicate at least one of the first index or at least one of the second index.

[0252] Optionally, the determining module 501 is further configured to perform any one of the following:

[0253] If the terminal does not receive a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission, determining that the time domain unit type of the target time domain unit is switched from the first type to the second type;

[0254] If the terminal receives a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission direction, it is determined that the time domain unit type of the target time domain unit is not switched.

[0255] Optionally, when the scheduling information indicates that there is dynamic scheduled transmission on the target time domain unit, the determining module 501 is further configured to perform any one of the following:

[0256] In a case where the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the frequency domain resources of the dynamically scheduled transmission overlap only with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, determining that the time domain unit type corresponding to the target time domain unit is the second time domain unit type;

[0257] In the case that the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the dynamically scheduled transmission is not located in the terminal side subband of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side subband of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side subband of the same transmission direction, it is determined that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, and the terminal performs the dynamically scheduled transmission.

[0258] Optionally, when the scheduling information indicates that at least one of dynamically scheduled transmission and semi-statically configured transmission exists on the target time domain unit, the determining module 501 is further configured to perform at least one of the following:

[0259] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type and the scheduling information indicates that there is only semi-static configuration transmission in one transmission direction on the target time domain unit, determining that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0260] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type and the scheduling information indicates that semi-static downlink transmission and semi-static uplink transmission exist on the target time domain unit, determining that the time domain unit type corresponding to the target time domain unit is the third time domain unit type;

[0261] When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that there are semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the time domain unit type corresponding to the target time domain unit is determined according to the frequency domain resource position of the dynamic scheduling transmission.

[0262] Optionally, the device further comprises:

[0263] The execution module is configured to discard the semi-static transmission or transmit only frequency domain resources within the terminal-side subband in the same transmission direction if the configured semi-static transmission overlaps with any GB or overlaps with a subband in the opposite transmission direction.

[0264] Optionally, the determining module 501 is further configured to perform any one of the following:

[0265] If the dynamically scheduled transmission is located in a terminal-side subband in the same transmission direction, determining that the time domain unit type corresponding to the target time domain unit is the third time domain unit type, and performing the dynamically scheduled transmission;

[0266] If the frequency domain resources of the dynamically scheduled transmission only overlap with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, determine that the time domain unit type corresponding to the target time domain unit is the second time domain unit type, and discard the semi-static transmission;

[0267] If the dynamically scheduled transmission is not located in the terminal side sub-band of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side sub-band of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side sub-band of the same transmission direction, determine that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, perform the dynamically scheduled transmission, and discard the semi-static transmission.

[0268] Optionally, when the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that the terminal has semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the execution module is further used to perform any one of the following:

[0269] If the semi-static configuration transmission is located in the terminal-side subband of the same transmission direction, executing the semi-static configuration transmission;

[0270] If the semi-statically configured transmission partially overlaps with the terminal-side subband in the same transmission direction, the semi-statically configured transmission is discarded or only frequency domain resources in the terminal-side subband in the same transmission direction are transmitted.

[0271] Optionally, the cancellation indication is used to indicate cancellation of at least one of a length and a granularity of the target time domain unit for transmission.

[0272] Optionally, the determining module 501 is further configured to:

[0273] According to an overlap between the area indicated by the cancellation instruction and the GB, it is determined that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type.

[0274] Optionally, the device further comprises:

[0275] A receiving module is configured to receive a target configuration parameter of the time domain unit type, where the target configuration parameter includes at least one of the following:

[0276] a first configuration parameter, the first configuration parameter corresponding to the first time-domain unit type;

[0277] a second configuration parameter, the second configuration parameter corresponding to the second time-domain unit type;

[0278] A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

[0279] Optionally, the frequency domain configuration corresponding to the full-duplex operation supported by the terminal satisfies at least one of the following:

[0280] The GB on the terminal side is the GB configured by the network side device for full-duplex operation on the terminal side;

[0281] The GB of the network side device is a GB configured by the network side device for full-duplex operation on the network side;

[0282] The sub-band on the terminal side is an uplink sub-band or a downlink sub-band configured by the network side device for full-duplex operation on the terminal side;

[0283] The sub-band of the network side device is an uplink sub-band or a downlink sub-band configured by the network side device for full-duplex operation on the network side;

[0284] The uplink subband size of the terminal side is a subset of the uplink subband size of the network side device;

[0285] The downlink subband size of the terminal side is a subset of the downlink subband size of the network side device;

[0286] The GB on the terminal side is a superset of the GB of the network side device.

[0287] Optionally, the validity time of the time domain unit type is located after the last symbol of the first PDCCH, and the first PDCCH is used to indicate the time domain unit type.

[0288] The device provided in the embodiment of the present application effectively improves the transmission flexibility of the terminal, and if the terminal supports full-duplex operation, it helps the terminal reduce latency and improve throughput, effectively improving the resource utilization of the system.

[0289] The time domain unit type determination device 500 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0290] The time domain unit type determination device 500 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0291] Please refer to Figure 6, which is a structural diagram of another time domain unit type determination device provided in an embodiment of the present application, and the device is applied to a network side device. As shown in Figure 6, the time domain unit type determination device 600 includes:

[0292] A sending module 601 is configured to send first information to a terminal, where the first information is used by the terminal to determine a time domain unit type corresponding to a target time domain unit, and the first information includes at least one of the following: configuration and instruction information of a network-side device, and scheduling information of the target time domain unit;

[0293] The terminal is a terminal that supports full-duplex operation, and the time domain unit type includes any one of the following:

[0294] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0295] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0296] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0297] Optionally, the indication information is used to indicate at least one of the following:

[0298] The time domain unit type corresponding to the target time domain unit of the terminal;

[0299] canceling transmission in a target transmission direction, where the target transmission direction includes an uplink transmission direction and a downlink transmission direction;

[0300] The target time domain unit has no dynamically scheduled transmission.

[0301] Optionally, the sending module 601 is further configured to:

[0302] Sending a target configuration parameter of the time domain unit type to the terminal, where the target configuration parameter includes at least one of the following:

[0303] a first configuration parameter, the first configuration parameter corresponding to the first time-domain unit type;

[0304] a second configuration parameter, the second configuration parameter corresponding to the second time-domain unit type;

[0305] A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

[0306] In an embodiment of the present application, the device sends first information to the terminal, so that the terminal can determine the time domain unit type of the target time domain unit based on the first information, thereby effectively improving the transmission flexibility of the terminal. If the terminal supports full-duplex operation, the network side device can also support full-duplex operation, thereby effectively improving the resource utilization of the system.

[0307] The time domain unit type determination device 600 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0308] As shown in Figure 7, an embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction, when executed by the processor 701, implements the various steps of the method embodiment described in Figure 2 above, and can achieve the same technical effect. When the communication device 700 is a network-side device, the program or instruction, when executed by the processor 701, implements the various steps of the method embodiment described in Figure 4 above, and can achieve the same technical effect. To avoid repetition, they are not repeated here.

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

[0310] The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of the processor 810.

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

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

[0313] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

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

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

[0316] The processor 810 is configured to determine, when the terminal supports full-duplex operation, a time domain unit type corresponding to the target time domain unit according to first information; wherein the first information includes at least one of the following: configuration and indication information of a network-side device, and scheduling information of the target time domain unit;

[0317] The time domain unit type includes any of the following:

[0318] A first time domain unit type, where the first time domain unit type is used to instruct the terminal and the network side device to perform only downlink transmission or uplink transmission in the target time domain unit;

[0319] A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit;

[0320] A third time domain unit type, wherein the third time domain unit type is used to instruct the terminal and the network side device to perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

[0321] The terminal provided in the embodiment of the present application can determine the time domain unit type corresponding to the target time domain unit based on the configuration of the network side device, the indication information and at least one of the scheduling information of the target time domain unit, and then the terminal can select one of the first time domain unit type, the second time domain unit type and the third time domain unit type to perform corresponding transmission, which effectively improves the transmission flexibility of the terminal. If the terminal supports full-duplex operation, it helps the terminal to reduce latency and improve throughput, effectively improving the resource utilization of the system.

[0322] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in the method embodiment of Figure 2 above, and can achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

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

[0324] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 9, the network-side device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

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

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

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

[0328] Specifically, the network side device 900 of an embodiment of the present invention also includes: instructions or programs stored in the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by the modules shown in FIG6 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0329] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the method embodiment of Figure 2 or Figure 4 above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0331] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiments of Figure 2 or Figure 4 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0333] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the method embodiment of Figure 2 or Figure 4 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0334] An embodiment of the present application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the method described in Figure 2 above, and the network-side device can be used to execute the steps of the method described in Figure 4 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0336] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

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

Claims

1. A method for determining a time domain unit type, comprising: In the case where the terminal supports full-duplex operation, the terminal determines the time domain unit type corresponding to the target time domain unit according to the first information; wherein the first information includes at least one of the following: configuration and indication information of a network side device, and scheduling information of the target time domain unit; The time domain unit type includes any of the following: A first time domain unit type, where the first time domain unit type is used to indicate that the terminal and the network side device only perform downlink transmission or uplink transmission in the target time domain unit; A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit; A third time domain unit type is used to indicate that the terminal and the network side device perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

2. The method according to claim 1, wherein: In a case where the first information includes scheduling information of the target time domain unit, the terminal determines, according to the first information, a time domain unit type corresponding to the target time domain unit, including at least one of the following: In the case of a semi-statically configured transmission with only one transmission direction on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to whether the scheduling information schedules a dynamically scheduled transmission opposite to the semi-statically configured transmission direction; When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamically scheduled transmission and the guard band GB; When the scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, and the dynamically scheduled transmission is located in a subband of the same transmission direction under full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type; When the scheduling information indicates that at least one of a dynamic scheduling transmission and a semi-static configuration transmission exists on the target time domain unit, the terminal determines the time domain unit type corresponding to the target time domain unit according to the transmission situation of at least one of the dynamic scheduling transmission and the semi-static configuration transmission; If the scheduling information indicates that there is a dynamically scheduled uplink transmission and a dynamically scheduled downlink transmission on the target time domain unit, and the dynamically scheduled uplink transmission is an uplink subband under the full-duplex operation of the terminal, and the dynamically scheduled downlink transmission is a downlink subband under the full-duplex operation of the terminal, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type; In a case where the scheduling information is a cancellation indication for indicating cancellation of transmission, the terminal determines, according to the cancellation indication, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type; When the scheduling information indicates that the target time domain unit has no dynamically scheduled transmission, the terminal determines that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type; The first type is any one of the time domain unit types, and the second type is any one of the time domain unit types. one of the types that is different from the first type.

3. The method according to claim 1, wherein: The indication information includes at least one of the following: Terminal-specific downlink control information DCI; Group common DCI.

4. The method according to claim 3, wherein: The dedicated DCI or the group common DCI includes a time domain unit type indication field, and the time domain unit type indication field is used to indicate the time domain unit type corresponding to the target time domain unit.

5. The method according to claim 3, wherein: In a case where the indication information includes the group common DCI, the group common DCI satisfies at least one of the following: The group common DCI includes at least one first index, where the first index is used to indicate a time domain unit type corresponding to at least one symbol, and the target time domain unit includes the at least one symbol; The group common DCI includes at least one second index, where the second index is used to indicate a time domain unit type corresponding to at least one time slot, and the target time domain unit includes the at least one time slot.

6. The method according to claim 5, wherein: The group common DCI also includes a third index, and the third index is used to indicate at least one of the first index or at least one of the second index.

7. The method according to claim 2, wherein: The terminal determines, according to whether the scheduling information schedules a dynamic scheduling transmission in a direction opposite to the semi-statically configured transmission, a time domain unit type corresponding to the target time domain unit, including any one of the following: If the terminal does not receive a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission, the terminal determines that the time domain unit type of the target time domain unit is switched from the first type to the second type; If the terminal receives a dynamically scheduled transmission in a direction opposite to the semi-statically configured transmission direction, the terminal determines that the time domain unit type of the target time domain unit is not switched.

8. The method according to claim 2, wherein: The scheduling information indicates that there is a dynamically scheduled transmission on the target time domain unit, and the terminal determines the time domain unit type corresponding to the target time domain unit according to the overlap between the dynamically scheduled transmission and the guard band GB, including any one of the following: In a case where the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the frequency domain resources of the dynamically scheduled transmission overlap only with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the second time domain unit type; In the case that the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, if the dynamically scheduled transmission is not located in the terminal side subband of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side subband of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side subband of the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, and the terminal performs the dynamically scheduled transmission.

9. The method according to claim 2, wherein: When the scheduling information indicates that at least one of a dynamic scheduling transmission and a semi-static configuration transmission exists on the target time domain unit, the terminal determines, according to a transmission situation of at least one of the dynamic scheduling transmission and the semi-static configuration transmission, a time domain unit type corresponding to the target time domain unit, including at least one of the following: When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, and the scheduling information indicates that there is only a semi-statically configured transmission in one transmission direction on the target time domain unit, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type; When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, and the scheduling information indicates that there is semi-static downlink transmission and semi-static uplink transmission on the target time domain unit, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type; When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that there are semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the terminal determines the time domain unit type corresponding to the target time domain unit according to the frequency domain resource position of the dynamic scheduling transmission.

10. The method according to claim 9, further comprising: If the configured semi-static transmission overlaps with any GB or overlaps with a subband in the opposite transmission direction, the terminal discards the semi-static transmission or only transmits frequency domain resources within the terminal-side subband in the same transmission direction.

11. The method according to claim 9, wherein: The terminal determines, according to the frequency domain resource position of the dynamically scheduled transmission, a time domain unit type corresponding to the target time domain unit, including any one of the following: If the dynamically scheduled transmission is located in a terminal-side subband in the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the third time domain unit type, and performs the dynamically scheduled transmission; If the frequency domain resources of the dynamically scheduled transmission only overlap with the frequency domain resources between the GB on the network side and the terminal side subband in the same transmission direction outside the terminal side subband in the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the second time domain unit type, and discards the semi-static transmission; If the dynamically scheduled transmission is not located in the terminal side subband of the same transmission direction, and the frequency domain resources of the dynamically scheduled transmission overlap with other frequency domain resources outside the terminal side subband of the same transmission direction except the frequency domain resources between the GB on the network side and the terminal side subband of the same transmission direction, the terminal determines that the time domain unit type corresponding to the target time domain unit is the first time domain unit type, the terminal performs the dynamically scheduled transmission, and discards the semi-static transmission.

12. The method according to claim 9, wherein: When the time domain unit type corresponding to the target time domain unit is configured as the third time domain unit type, the scheduling information indicates that the terminal has semi-static configuration transmission and dynamic scheduling transmission on the target time domain unit, and the semi-static configuration transmission and the dynamic scheduling transmission are in opposite directions, the method further includes any one of the following: If the semi-static configuration transmission is located in a terminal-side subband in the same transmission direction, the terminal performs the semi-static configuration transmission; If the semi-statically configured transmission partially overlaps with the terminal-side subband in the same transmission direction, the terminal discards the semi-statically configured transmission or only transmits frequency domain resources in the terminal-side subband in the same transmission direction.

13. The method according to claim 2, wherein: The cancellation indication is used to indicate cancellation of at least one of a length and a granularity of the target time domain unit for transmission.

14. The method according to claim 2, wherein: The terminal determines, according to the cancellation indication, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type, including: The terminal determines, according to an overlap between the area indicated by the cancellation indication and the GB, that the time domain unit type corresponding to the target time domain unit is switched from the first type to the second type.

15. The method according to any one of claims 1 to 14, further comprising: The terminal receives a target configuration parameter of the time domain unit type, where the target configuration parameter includes at least one of the following: a first configuration parameter, the first configuration parameter corresponding to the first time domain unit type; a second configuration parameter, the second configuration parameter corresponding to the second time domain unit type; A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

16. The method according to any one of claims 1 to 14, wherein: The frequency domain configuration corresponding to the full-duplex operation supported by the terminal satisfies at least one of the following: The GB on the terminal side is a GB configured by the network side device for full-duplex operation on the terminal side; The GB of the network side device is a GB configured by the network side device for full-duplex operation on the network side; The subband on the terminal side is an uplink subband or a downlink subband configured by the network side device for full-duplex operation on the terminal side; The subband of the network side device is an uplink subband or a downlink subband configured by the network side device for full-duplex operation on the network side; The uplink subband size of the terminal side is a subset of the uplink subband size of the network side device; The downlink subband size of the terminal side is a subset of the downlink subband size of the network side device; The GB on the terminal side is a superset of the GB on the network side device.

17. The method according to any one of claims 1 to 14, wherein: The effective time of the time domain unit type is located after the last symbol of the first physical downlink control channel PDCCH, and the first PDCCH is used to indicate the time domain unit type.

18. A method for determining a time domain unit type, comprising: The network side device sends first information to the terminal, where the first information is used by the terminal to determine the time domain unit type corresponding to the target time domain unit, and the first information includes at least one of the following: configuration and indication information of the network side device, and scheduling information of the target time domain unit; The terminal is a terminal supporting full-duplex operation, and the time domain unit type includes any one of the following: A first time domain unit type, where the first time domain unit type is used to indicate that the terminal and the network side device only perform downlink transmission or uplink transmission in the target time domain unit; A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit; A third time domain unit type is used to indicate that the terminal and the network side device perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

19. The method according to claim 18, wherein: The indication information is used to indicate at least one of the following: The time domain unit type corresponding to the target time domain unit of the terminal; cancelling transmission in a target transmission direction, wherein the target transmission direction includes an uplink transmission direction and a downlink transmission direction; The target time domain unit has no dynamically scheduled transmission.

20. The method according to claim 18, further comprising: The network side device sends a target configuration parameter of the time domain unit type to the terminal, where the target configuration parameter includes at least one of the following: a first configuration parameter, the first configuration parameter corresponding to the first time domain unit type; a second configuration parameter, the second configuration parameter corresponding to the second time domain unit type; A third configuration parameter, the third configuration parameter corresponds to the third time domain unit type.

21. A device for determining a time domain unit type, applied to a terminal, the device comprising: A determination module, configured to determine, when the terminal supports full-duplex operation, a time domain unit type corresponding to the target time domain unit according to first information; wherein the first information includes at least one of the following: configuration of a network-side device, indication information, and scheduling information of the target time domain unit; The time domain unit type includes any of the following: A first time domain unit type, where the first time domain unit type is used to indicate that the terminal and the network side device only perform downlink transmission or uplink transmission in the target time domain unit; A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit; A third time domain unit type is used to indicate that the terminal and the network side device perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

22. A device for determining a time domain unit type, applied to a network side device, the device comprising: A sending module, configured to send first information to a terminal, wherein the first information is used by the terminal to determine a time domain unit type corresponding to a target time domain unit, and the first information includes at least one of the following: configuration and indication information of a network side device, and scheduling information of the target time domain unit; The terminal is a terminal supporting full-duplex operation, and the time domain unit type includes any one of the following: A first time domain unit type, where the first time domain unit type is used to indicate that the terminal and the network side device only perform downlink transmission or uplink transmission in the target time domain unit; A second time domain unit type, where the second time domain unit type is used to indicate that the terminal performs only downlink transmission or uplink transmission in the target time domain unit, and the network side device performs both downlink transmission and uplink transmission in the target time domain unit; A third time domain unit type is used to indicate that the terminal and the network side device perform downlink transmission and uplink transmission simultaneously in the target time domain unit.

23. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the time domain unit type determination method according to any one of claims 1 to 17 are implemented.

24. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the time domain unit type determination method according to any one of claims 18 to 20 are implemented.

25. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the time domain unit type determination method according to any one of claims 1 to 17, or implements the steps of the time domain unit type determination method according to any one of claims 18 to 20.

Images