Downlink reception and measurement method and apparatus and communication device

Abstract

The present application relates to the technical field of communications, and discloses a downlink reception and measurement method and apparatus and a communication device. The downlink reception and measurement method in embodiments of the present application comprises: a terminal determines, on the basis of a first time domain type corresponding to a first downlink reception, a transmission parameter corresponding to the first downlink reception, and executes, on the basis of the transmission parameter corresponding to the first downlink reception, reception corresponding to the first downlink reception; or, the terminal executes, on the basis of a second time domain type corresponding to a first measurement, at least one of the first measurement and reporting corresponding to the first measurement; wherein when the first downlink reception comprises an SSB, the transmission parameter comprises at least one of the following: a transmit power, an SSB beam related parameter, and an SSB index related parameter; when the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of the following: a QCL assumption and a TCI state; and the first measurement comprises at least one of CSI measurement and CLI measurement.

Description

Downlink reception and measurement method, apparatus and communication device

[0001] Cross Reference to Related Applications

[0002] The present application claims priority to Chinese Patent Application No. 202410471183.9, filed on April 18, 2024, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and specifically relates to a downlink reception and measurement method, apparatus and communication device. BACKGROUND

[0004] In order to more flexibly utilize limited frequency spectrum resources, to dynamically match business requirements, and to improve resource utilization efficiency, related technologies propose a flexible duplex mode. Under the flexible duplex mode, a time domain unit can correspond to or distinguish multiple time domain types. In related technologies, a terminal only needs to perform downlink reception or measurement on one time domain type, which cannot be applied to a flexible duplex scenario, which leads to the terminal not knowing how to perform downlink reception or measurement. SUMMARY

[0005] Embodiments of the present application provide a downlink reception and measurement method, apparatus and communication device, which can solve the problem of how a terminal performs downlink reception or measurement in a flexible duplex scenario.

[0006] In a first aspect, a downlink reception and measurement method is provided, which is performed by a terminal, and the method comprises:

[0007] The terminal determines transmission parameters corresponding to a first downlink reception based on a first time domain type corresponding to the first downlink reception, and performs reception corresponding to the first downlink reception according to the transmission parameters corresponding to the first downlink reception; or,

[0008] The terminal performs at least one of the first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement;

[0009] The first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS);

[0010] In the case where the first downlink reception comprises an SSB, the transmission parameters comprise at least one of the following: transmission power; related parameters of an SSB beam; and related parameters of an SSB index;

[0011] In a case where the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of: a quasi co-location (QCL) assumption; a transmission configuration indication (TCI) state.

[0012] The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0013] In a second aspect, a downlink reception and measurement method is provided, which is performed by a network side device, and the method comprises:

[0014] The network side device determines a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and performs a transmission corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or,

[0015] The network side device performs a reception of a measurement report corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0016] The first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0017] In a case where the first downlink reception comprises an SSB, the transmission parameter comprises at least one of: a transmit power; a related parameter of an SSB beam; and a related parameter of an SSB index.

[0018] In a case where the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of: a quasi co-location (QCL) assumption; and a transmission configuration indication (TCI) state.

[0019] The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0020] In a third aspect, a downlink reception and measurement apparatus is provided, which comprises:

[0021] A first processing unit is configured to: determine a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform a reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or,

[0022] Perform at least one of the first measurement and a reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0023] The first downlink reception includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0024] In a case where the first downlink reception includes the SSB, the transmission parameter includes at least one of a transmit power, a related parameter of an SSB beam, and a related parameter of an SSB index.

[0025] In a case where the first downlink reception includes at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter includes at least one of a quasi co-location (QCL) assumption and a transmission configuration indication (TCI) state.

[0026] The first measurement includes at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0027] In a fourth aspect, a downlink reception and measurement apparatus is provided, and the apparatus includes:

[0028] a processing unit configured to: determine a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform a transmission corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or

[0029] perform a reception of a measurement report corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0030] The first downlink reception includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0031] In a case where the first downlink reception includes the SSB, the transmission parameter includes at least one of a transmit power, a related parameter of an SSB beam, and a related parameter of an SSB index.

[0032] In a case where the first downlink reception includes at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter includes at least one of a quasi co-location (QCL) assumption and a transmission configuration indication (TCI) state.

[0033] The first measurement includes at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0034] In a fifth aspect, a terminal is provided, which comprises a processor and a memory, the memory storing programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement steps of the method according to the first aspect.

[0035] In a sixth aspect, a terminal is provided, which comprises a processor and a communication interface, wherein the processor is configured to:

[0036] determine transmission parameters corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform reception corresponding to the first downlink reception according to the transmission parameters corresponding to the first downlink reception; or

[0037] perform at least one of the first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement;

[0038] The first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0039] When the first downlink reception comprises an SSB, the transmission parameters comprise at least one of: a transmission power; a related parameter of an SSB beam; and a related parameter of an SSB index.

[0040] When the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameters comprise at least one of: a quasi co-location (QCL) assumption; and a transmission configuration indication (TCI) state.

[0041] The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0042] In a seventh aspect, a network-side device is provided, which comprises a processor and a memory, the memory storing programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement steps of the method according to the second aspect.

[0043] In an eighth aspect, a network-side device is provided, which comprises a processor and a communication interface, wherein the processor is configured to:

[0044] determine transmission parameters corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform transmission corresponding to the first downlink reception according to the transmission parameters corresponding to the first downlink reception; or

[0045] perform reception of a measurement report corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0046] The first downlink reception includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0047] In a case where the first downlink reception includes the SSB, the transmission parameter includes at least one of a transmit power, a related parameter of an SSB beam, and a related parameter of an SSB index.

[0048] In a case where the first downlink reception includes at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter includes at least one of a quasi co-location (QCL) assumption and a transmission configuration indication (TCI) state.

[0049] The first measurement includes at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0050] In a ninth aspect, a readable storage medium is provided, and the readable storage medium stores a program or an instruction. The program or the instruction is executed by a processor to implement steps of the method in the first aspect or implement steps of the method in the second aspect.

[0051] In a tenth aspect, a wireless communication system is provided, and the wireless communication system includes a terminal and a network side device. The terminal is configured to implement steps of the method in the first aspect, and the network side device is configured to implement steps of the method in the second aspect.

[0052] In an eleventh aspect, a chip is provided, and the chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or an instruction to implement the method in the first aspect or implement the method in the second aspect.

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

[0054] In the embodiments of the present application, the terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, and performs the reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or the terminal performs at least one of the first measurement and the reporting corresponding to the first measurement based on the second time domain type corresponding to the first measurement; wherein the first downlink reception includes at least one of SSB, PDCCH, PDSCH and CSI-RS; in the case where the first downlink reception includes SSB, the transmission parameter includes at least one of the following: transmission power; related parameters of SSB beam; related parameters of SSB index; in the case where the first downlink reception includes at least one of PDCCH, PDSCH and CSI-RS, the transmission parameter includes at least one of the following: QCL assumption; TCI state; the first measurement includes at least one of CSI measurement and CLI measurement. In this way, when the time domain unit corresponds to or distinguishes multiple time domain types, the terminal can determine the transmission parameter corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, so that the terminal can realize flexible and reliable downlink reception according to the determined transmission parameter. The terminal can also perform at least one of measurement and reporting based on the time domain type corresponding to a certain measurement, so that the terminal can realize flexible and accurate and effective measurement. It can be seen that the embodiments of the present application can realize downlink reception or measurement of the terminal in a flexible duplexing scenario. BRIEF DESCRIPTION OF DRAWINGS

[0055] FIG. 1 is a schematic diagram of a network structure to which the embodiments of the present application can be applied;

[0056] FIG. 2 is a schematic diagram of a flexible duplexing mode;

[0057] FIG. 3 is a flowchart of a downlink reception and measurement method according to an embodiment of the present application;

[0058] FIG. 4 is a flowchart of another downlink reception and measurement method according to an embodiment of the present application;

[0059] FIG. 5 is a structural diagram of a downlink reception and measurement apparatus according to an embodiment of the present application;

[0060] FIG. 6 is a structural diagram of another downlink reception and measurement apparatus according to an embodiment of the present application;

[0061] FIG. 7 is a structural diagram of a communication device according to an embodiment of the present application;

[0062] FIG. 8 is a structural diagram of a terminal according to an embodiment of the present application;

[0063] FIG. 9 is a structural diagram of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0064] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0065] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, 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", "second" are generally a class, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and including B. The character " / " generally represents that the objects before and after are in an "or" relationship.

[0066] The term "indicate" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of specific information, operations to be performed or requested results, etc. in the sent indication; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operation to be performed or the requested result according to the judgment result.

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

[0068] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a Personal Computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothing, etc. The vehicle-mounted device can also be referred to as 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 embodiments of the present application. The network-side device 12 can include an access network device or a core network device. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmission reception point (TRP), or some other suitable terminology in the art, and is not limited to a particular technical word as long as the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0069] The core network device can include, but is not limited to, at least one of the following: a core network node, a core network function, a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (or L-NEF), a binding support function (BSF), an application function (AF), and the like. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited.

[0070] Before the embodiments of the present application are described, the following first briefly introduces the flexible duplex (flexible duplex) in the related art:

[0071] When deploying a conventional cellular network, based on the available spectrum, as well as the service characteristics, etc., a duplex mode of Frequency Division Duplex (FDD) or Time Division Duplex (TDD) can be adopted. When FDD is adopted, uplink transmission and downlink transmission are located at different frequency points, and the two do not interfere with each other, and can be performed at the same time. When TDD is adopted, uplink transmission and downlink transmission are located at the same frequency point, and are staggered in time division mode. The above two duplex modes have advantages and disadvantages.

[0072] In order to more flexibly utilize limited spectrum resources, to dynamically match service requirements, to improve resource utilization efficiency, and to improve the performance of uplink coverage, latency, etc. of data transmission, a flexible duplex mode is proposed. A flexible duplex mode based on non-overlapping sub-band in frequency domain, i.e. non-overlapping sub-band full duplex (SBFD) (which can be simply referred to as sub-band full duplex) is as follows:

[0073] 1. Network side full duplex

[0074] From the perspective of the network side, at the same time, uplink transmission and downlink transmission can be performed at the same time in different frequency domain sub-bands. In order to avoid interference between uplink and downlink, a certain guard band (Guard Band) can be left between the frequency domain sub-bands corresponding to different transmission directions (such as uplink sub-band and downlink sub-band).

[0075] 2. Terminal side half duplex or full duplex

[0076] When the terminal side supports half duplex, at the same time, only uplink transmission or downlink transmission can be performed, and the two cannot be performed at the same time. It can be understood that in this case, the uplink transmission and downlink transmission of the network side at the same time can only be for different terminals.

[0077] When the terminal side supports full duplex, similar to the network side, at the same time, uplink transmission and downlink transmission can be performed at the same time in different frequency domain sub-bands.

[0078] FIG. 2 shows a schematic diagram of the above flexible duplex mode. The network side divides the frequency domain of a single carrier into three sub-bands in a part of the downlink symbol, wherein the two sides of the carrier are downlink sub-bands, and the center is an uplink sub-band, in order to reduce the interference caused to adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception, respectively.

[0079] In the scenario of flexible duplexing mode shown in FIG. 2, the time domain unit can correspond to multiple time domain types, such as SBFD symbol and non-SBFD symbol. For a serving cell or bandwidth part (BWP) enabled with SBFD, on the network side, the settings of antennas or radio frequency (RF) corresponding to SBFD symbols and non-SBFD symbols can be different to provide self-interference suppression and other capabilities for SBFD operation. Accordingly, the spatial relation or transmission configuration indicator (TCI) state corresponding to the uplink channel or signal in the SBFD symbol can also be different from that in the non-SBFD symbol. For the determination of the spatial relation / TCI state corresponding to each channel / signal, the overall idea of separate configuration has been preliminarily formed in the study item (SI) stage, but there is a lack of research and discussion on operation details and signaling design, which leads to the terminal not knowing how to perform downlink reception and measurement.

[0080] In view of this, the embodiments of the present application provide a downlink reception and measurement method, a downlink reception and measurement device, and a communication device to solve the problem of how the terminal performs downlink reception and measurement under flexible duplexing mode.

[0081] To facilitate the description of the schemes below, the following concepts and explanations are given first:

[0082] Based on the TDD pattern configuration information provided by the network side to the UE (for example, tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated provided for a certain serving cell of the UE), the following symbol types can be distinguished: downlink symbol (DL symbol), uplink symbol (UL symbol), and flexible symbol (Flexible symbol).

[0083] When tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is not provided for a certain Serving cell, each Symbol can be considered as Flexible symbol, or, follow the rules or operations corresponding to Flexible symbol.

[0084] Based on the above TDD pattern configuration information, and the SBFD configuration information provided by the network side to the UE, the following Symbol types can be further distinguished:

[0085] 1、SBFD symbol

[0086] The network side can configure some Symbols as SBFD operation can be performed, i.e., configure these Symbols as SBFD symbol, through SBFD configuration information. For example, part or all of the Symbols in a single period determined based on TDD pattern are configured as SBFD symbol. These Symbols configured as SBFD symbol can be part or all of the Symbol types distinguished based on TDD pattern configuration information.

[0087] For a certain Serving cell configured or activated for the UE, the SBFD symbol on the Serving cell can be further distinguished as the following Symbol types:

[0088] (1) SBFD symbol for duplex mode 1

[0089] For Duplex mode 1, the network side supports SBFD operation based on full duplex; the UE side only supports SBFD operation based on half duplex, i.e., the UE can only perform uplink transmission or downlink reception in a single SBFD symbol, and cannot simultaneously perform uplink transmission and downlink reception based on FDM (Frequency Division Multiplexing).

[0090] (2) SBFD symbol for duplex mode 2

[0091] For Duplex mode 2, the network side supports full-duplex based SBFD operation; the UE side can support full-duplex based SBFD operation, that is, the UE can simultaneously perform FDM based uplink transmission and downlink reception within a single SBFD symbol. Generally, a UE supporting full-duplex based SBFD operation (that is, supporting Duplex mode 2, or supporting SBFD symbol for duplex mode 2) must also support half-duplex based SBFD operation (that is, supporting Duplex mode 1, or supporting SBFD symbol for duplex mode 1).

[0092] 2、non-SBFD symbol

[0093] A symbol that is not configured (or indicated) to perform SBFD operation can be considered as a non-SBFD symbol.

[0094] In the Duplex study item of Release 18 (Rel-18), the mainstream view is that: different Symbol types (for example, SBFD symbol and non-SBFD symbol, or SBFD symbol for duplex mode 1, SBFD symbol for duplex mode 2, and non-SBFD symbol) based on SBFD configuration information can be distinguished. The parameters corresponding to each Channel / Signal can be respectively (or directly) configured or (implicitly based on frequency domain offset (Offset), respective starting reference points, etc.) derived to consider / compensate for the antenna and radio frequency configurations (including antenna positions, antenna numbers, connection relationships between antennas and RF chains, etc.), interference conditions and restrictions (including self-interference (SI), cross-link interference (CLI), and other interferences and corresponding restrictions) corresponding to different Symbol types. Accordingly, the QCL assumption / TCI state corresponding to the downlink or CLI measurement Channel / Signal in the SBFD symbol can also be different from that in the non-SBFD symbol.

[0095] The downlink reception and measurement method provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0096] FIG. 3 shows a flowchart of a downlink receiving and measuring method according to an embodiment of the present application. As shown in FIG. 3, the downlink receiving and measuring method comprises the following steps.

[0097] In step 301, the terminal determines the transmission parameter corresponding to the first downlink receiving based on the first time domain type corresponding to the first downlink receiving, and performs the receiving corresponding to the first downlink receiving according to the transmission parameter corresponding to the first downlink receiving; or,

[0098] The terminal performs at least one of the first measurement and the reporting corresponding to the first measurement based on the second time domain type corresponding to the first measurement.

[0099] The first downlink receiving can comprise at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS); in the case where the first downlink receiving comprises an SSB, the transmission parameter comprises at least one of the following: a transmission power; a related parameter of an SSB beam; a related parameter of an SSB index; in the case where the first downlink receiving comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of the following: a quasi co-location (QCL) assumption; a TCI state. For example, the related parameter of the SSB beam can comprise the number of SSB beams, the direction of the SSB beam, the width of the SSB beam, and the like.

[0100] The first measurement can comprise at least one of a channel state information (CSI) measurement and a CLI measurement. In the case where the first measurement comprises a CSI measurement, the measurement and the reporting of the CSI can be considered simultaneously, and in the case where the first measurement comprises a CLI measurement, the measurement of the CLI can be considered mainly.

[0101] The first downlink reception and the first measurement can be combined, i.e., the step 301 comprises: determining, by the terminal, a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and performing a reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; and performing, by the terminal, at least one of the first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0102] The time domain type can be understood as a type of time domain unit. For example, the time domain type can include SBFD time domain unit and non-SBFD time domain unit, and the SBFD time domain unit can include SBFD time domain unit for duplex mode 1 and SBFD time domain unit for duplex mode 2. The time domain unit can be a slot, a symbol, etc. In this application, the time domain unit is described by taking a symbol as an example. In this case, the time domain type can be referred to as a symbol type. For example, the symbol type can include SBFD symbol and non-SBFD symbol, and the SBFD symbol can include SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2. When the time domain unit is a slot, the time domain type can be referred to as a slot type, which is not limited in this application. The first time domain type and the second time domain type in the embodiments of this application can be understood with reference to the above description of the time domain type. To avoid repetition, no further description is given.

[0103] The embodiments of this application can be applied to a Serving cell / BWP enabled with SBFD. For the Serving cell / BWP enabled with SBFD, the UE can determine a QCL assumption / TCI state corresponding to a downlink Channel / Signal or a CLI measurement Channel / Signal based on a symbol type. Here, the UE can be understood as a SBFD capable UE or a SBFD aware UE.

[0104] In the embodiments of the present application, the terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, and performs the reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or the terminal performs at least one of the first measurement and the reporting corresponding to the first measurement based on the second time domain type corresponding to the first measurement; wherein the first downlink reception includes at least one of SSB, PDCCH, PDSCH and CSI-RS; in the case that the first downlink reception includes SSB, the transmission parameter includes at least one of the following: transmit power; related parameters of SSB beam; related parameters of SSB index; in the case that the first downlink reception includes at least one of PDCCH, PDSCH and CSI-RS, the transmission parameter includes at least one of the following: QCL assumption; TCI state; the first measurement includes at least one of CSI measurement and CLI measurement. In this way, when a time domain unit corresponds to or distinguishes multiple time domain types, the terminal can determine the transmission parameter corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, so that the terminal can realize flexible and reliable downlink reception according to the determined transmission parameter. The terminal can also perform at least one of measurement and reporting based on the time domain type corresponding to a certain measurement, so that the terminal can realize flexible and accurate and effective measurement. It can be seen that the embodiments of the present application can realize downlink reception or measurement of the terminal in a flexible duplexing scenario.

[0105] In some embodiments, the first downlink reception includes at least one of SSB, PDCCH and CSI-RS;

[0106] The time domain unit where the first downlink reception is located corresponds to the same time domain type; or,

[0107] The time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

[0108] Here, "can" can be understood as allowing, supporting, etc., and other same descriptions can be understood in the same way, and to avoid repetition, no further description is given.

[0109] The following describes the related implementation of SSB reception by taking SSB as an example.

[0110] In some embodiments, the first downlink reception includes SSB;

[0111] In the case that the time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types, the terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, including at least one of the following:

[0112] The terminal does not distinguish the time domain type corresponding to the time domain unit where the first downlink reception is located, and uniformly determines the transmission parameter corresponding to the first downlink reception as a first transmission parameter.

[0113] The terminal distinguishes the time domain type corresponding to the time domain unit where the first downlink reception is located, and determines the transmission parameter corresponding to the first downlink reception in the time domain unit of different time domain types based on the mapping relationship between the time domain type and the transmission parameter.

[0114] For the convenience of understanding, the embodiments of the present application exemplarily illustrate the transmission mode of SSB.

[0115] For the transmission of SSB, any one of SSB transmission mode 1 and SSB transmission mode 2 can be adopted:

[0116] SSB transmission mode 1: SSB can only be transmitted in the Symbol corresponding to a single Symbol type.

[0117] At this time, the network side can ensure (at this time, the UE expects) that the configured SSB is only located in the Symbol corresponding to the Symbol type, or the network side can configure SSB without ensuring that it only appears in the Symbol corresponding to the Symbol type, but the UE only considers the SSB located in the Symbol corresponding to the Symbol type as valid. For example, SSB can only be configured in non-SBFD symbol, or SSB can only be actually transmitted in non-SBFD symbol.

[0118] SSB transmission mode 2: SSB can be transmitted (i.e., can be transmitted) in the Symbol corresponding to each (or more than one) Symbol type.

[0119] At this time, for the configuration / hypothesis of the transmission attribute (i.e., transmission parameter) of SSB, any one of SSB attribute mode 1 and SSB attribute mode 2 can be adopted:

[0120] SSB attribute mode 1: the UE assumes that the transmission attributes of SSBs transmitted in the Symbols corresponding to different Symbol types are completely consistent, or the UE does not distinguish the difference between the transmission attributes of SSBs transmitted in the Symbols corresponding to different Symbol types.

[0121] SSB attribute mode 1 can be understood as: the UE considers that the SSBs transmitted in the Symbols corresponding to different Symbol types uniformly use configuration parameters and can be uniformly processed without considering the difference.

[0122] SSB attribute manner 2: the UE considers that there can be a difference in transmission attribute between the SSBs transmitted within the symbols corresponding to different Symbol types.

[0123] The difference in SSB transmission attribute includes at least one of the following:

[0124] The number of SSB indexes or SSB beams transmitted; for example, ssb-PositionsInBurst can be independently configured for the SBFD symbol to indicate the set of SSB indexes actually transmitted within the single SSB burst set transmitted within the SBFD symbol;

[0125] The SSB transmit power; for example, ss-PBCH-BlockPower can be independently configured for the SBFD symbol to indicate the transmit power of the SSB transmitted within the SBFD symbol;

[0126] SSB beam pointing and / or width; in general, the network side sets the pointing and / or width of each SSB beam, which is transparent to the UE.

[0127] At this time, different SSB transmission attributes can be distinguished based on Symbol type. Among them, the SSB transmission attributes corresponding to each Symbol type involved in SSB transmission can be independently configured / determined, or more than one set of SSB transmission attributes is configured, and the mapping relationship between each Symbol type and each set of SSB transmission attributes is configured / determined.

[0128] Correspondingly, in the related functions based on the SSB beam selection result, the UE needs to distinguish the Symbol type and use the SSB beam corresponding to the matching Symbol type, for example, to determine the initial QCL assumption of PDSCH, to determine the mapped random access occasion (RACH Occasion, RO), etc.

[0129] Specifically, which SSB transmission manner is adopted, or when SSB transmission manner 2 is adopted, whether SSB attribute manner 1 or SSB attribute manner 2 is adopted, can be specified by the protocol or configured by high-layer signaling. For example, it is indicated in the system information block 1 (System Information Block 1, SIB1) whether SSB attribute manner 1 or SSB attribute manner 2 is adopted.

[0130] Optionally, for the transmission of SIB1 PDSCH (i.e., the PDSCH carrying the initial transmission / retransmission of SIB1), the above similar manner can also be adopted, which can specifically include at least one of the following:

[0131] SIB1 PDSCH can only be transmitted in the symbol corresponding to a single Symbol type;

[0132] SIB1 PDSCH can be transmitted in the symbol corresponding to each (or more than one) Symbol type.

[0133] The following describes the related embodiments of the general TCI state configuration corresponding to the first downlink reception including at least one of PDSCH, PDCCH and CSI-RS.

[0134] In some embodiments, the first downlink reception includes at least one of PDSCH, PDCCH and CSI-RS;

[0135] The method further includes:

[0136] The terminal receives first information from the network side device, and the first information is used to configure at least one set, each set in the at least one set including at least one transmission parameter;

[0137] The terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, including:

[0138] The terminal determines the transmission parameter corresponding to the first downlink reception from the at least one set based on the first time domain type corresponding to the first downlink reception.

[0139] Optionally, the at least one set includes at least one of:

[0140] A first set, any one transmission parameter in the first set can be used for any time domain type;

[0141] At least one second set, the time domain type corresponding to each transmission parameter in the at least one second set is determined by the configuration information of the transmission parameter;

[0142] A third set, the time domain type corresponding to each transmission parameter in the third set is determined by the position of the transmission parameter in the third set;

[0143] At least one fourth set, all transmission parameters in each fourth set correspond to the same time domain type, and different fourth sets correspond to different time domain types.

[0144] Optionally, the configuration information of the transmission parameter includes at least one of:

[0145] The identification of the transmission parameter, the time domain type corresponding to each transmission parameter in the at least one second set is determined by the value of the identification of the transmission parameter;

[0146] a first indication of the transmission parameters, the first indication being used to indicate a time domain type, and each of the transmission parameters in the at least one second set corresponds to the time domain type indicated by the first indication of the transmission parameters.

[0147] Optionally, the third set comprises one or more subsets, and each subset of the third set satisfies at least one of the following conditions:

[0148] Each subset of the third set is ordered according to a predetermined order, and the predetermined order represents an order of the time domain types.

[0149] The number of transmission parameters included in each subset of the third set is allocated in a predefined manner, or is directly configured or indicated.

[0150] For the convenience of understanding, the embodiments of the present application exemplarily illustrate the configuration mode of the general TCI state corresponding to the downlink reception.

[0151] For the configuration of the TCI state corresponding to the downlink reception (including PDSCH, PDCCH and NZP CSI-RS) (when the joint mode is adopted, it is also applicable to the uplink transmission, which will not be described below, and the uplink transmission includes PUSCH, PUCCH and SRS), any one of the general TCI state configuration mode 1 and the general TCI state configuration mode 2 can be adopted:

[0152] General TCI state configuration mode 1: without distinguishing the Symbol type, a unified configured TCI state set (i.e. the first set) is applied.

[0153] The general TCI state configuration mode 1 can be understood as follows: for any downlink reception corresponding to a Symbol type (or, within a Symbol corresponding to a Symbol type; when joint mode is adopted, it can be extended to further include uplink transmission, i.e., uplink transmission corresponding to the Symbol type, or uplink transmission within the Symbol corresponding to the Symbol type), any TCI state in the configured TCI state set can be applied as needed; or, any TCI state in the configured TCI state set is not limited to the Symbol type corresponding to the downlink reception (when joint mode is adopted, further including uplink transmission) to which it is applied. The unified configured TCI state set can be determined based on tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config, and when joint mode is adopted, it can be determined based on downlink-joint TCI state addition / modification list (such as dl-OrJointTCI-StateToAddModList-r17) and downlink-joint TCI state release list (such as dl-OrJointTCI-StateToReleaseList-r17) in PDSCH-Config.

[0154] The general TCI state configuration mode 2: distinguish the respective configured TCI state set for each Symbol type.

[0155] In the general TCI state configuration mode 2, any of the general TCI state configuration mode 2-1 to general TCI state configuration mode 2-3 can be adopted when determining the configured TCI state set corresponding to the Symbol type:

[0156] The general TCI state configuration mode 2-1: in the configuration information of each TCI state, distinguish the Symbol type corresponding to the TCI state.

[0157] At this time, the TCI state corresponding to each Symbol type can still be placed in a unified configured TCI state set (i.e., the second set). For a certain Symbol type, a subset of TCI states corresponding to it can be screened from the configured TCI state set as the configured TCI state set corresponding to the Symbol type. Specifically, any of the modes 1 to 2 can be adopted:

[0158] Manner 1: Determine the Symbol type corresponding to a TCI state based on the value range of TCI-StateId in which the TCI-StateId of this TCI state locates. Here it is assumed that each Symbol type corresponds to an independent value range of TCI-StateId, which can be specified by the protocol or configured by higher layer signaling; the value ranges of TCI-StateId corresponding to different Symbol types do not intersect with each other. When a TCI state corresponding to a certain Symbol type is configured, the TCI-StateId of this TCI state is required to be located in the value range of TCI-StateId corresponding to this Symbol type;

[0159] Manner 2: Introduce a new parameter (i.e., the first indication) in the configuration information of each TCI state to indicate the Symbol type corresponding to this TCI state.

[0160] Manner 2-2: Determine the Symbol type corresponding to a TCI state based on the position of this TCI state in the unified set of configured TCI states.

[0161] Here, it is assumed that the TCI states corresponding to each Symbol type are placed in a unified configured TCI state set (i.e., the third set), and this unified configured TCI state set is an ordered set determined based on tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config (when joint mode is adopted, it can be determined based on dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 in PDSCH-Config). For example, the first configured tci-StatesToAddModList (when joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17) is taken as the initial set of this unified configured TCI state set; the newly added TCI states in the subsequently configured tci-StatesToAddModList (when joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17) are sequentially added to the tail of this unified configured TCI state set in the order of their appearance in tci-StatesToAddModList; the modified TCI states can either overwrite the corresponding TCI states in this unified configured TCI state set or be sequentially added to the tail of this unified configured TCI state set in the order of their appearance in tci-StatesToAddModList (in this case, the corresponding TCI states in this unified configured TCI state set need to be deleted; the modified TCI states can be placed before or after the newly added TCI states, or be sequentially added to the tail of this unified configured TCI state set together with the newly added TCI states in the order of their appearance in tci-StatesToAddModList (in this case, the newly added TCI states and the modified TCI states added to the tail of this unified configured TCI state set can be intermingled or alternated)); and the corresponding TCI states are deleted from this unified configured TCI state set based on the configured tci-StatesToReleaseList (when joint mode is adopted, it can be dl-OrJointTCI-StateToReleaseList-r17).

[0162] Further, determine the position region of the TCI states corresponding to a certain Symbol type in the above ordered set; all the TCI states in this position region constitute the configured TCI state set corresponding to this Symbol type. For example, the first N1 TCI states in this ordered set correspond to Symbol type 1 (e.g. non-SBFD symbol) and the remaining N2 TCI states correspond to Symbol type 2 (e.g. SBFD symbol) according to the protocol or higher layer signaling. When determining N1 and N2, assuming that there are N TCI states in this ordered set, any of the following methods 3 and 4 can be used:

[0163] Method 3: N1 = floor(N / 2) (i.e. lower rounding) or N1 = ceiling(N / 2) (i.e. upper rounding) is agreed, and N2 = N - N1, i.e. the TCI states in this ordered set are divided into two parts or approximately divided into two parts, and the two parts obtained correspond to two Symbol types respectively;

[0164] Method 4: N1 is configured or indicated, and N2 = N - N1.

[0165] General TCI state configuration method 2-3: respectively configure and / or maintain the configured TCI state set (i.e. the fourth set) corresponding to each Symbol type.

[0166] When the configuration parameters corresponding to each Symbol type are provided / determined based on a single / shared PDSCH-Config, the corresponding TCI state addition / modification list (e.g., tci-StatesToAddModList) and / or TCI state release list (e.g., tci-StatesToReleaseList) can be separately configured for each Symbol type in PDSCH-Config. When joint mode is adopted, the corresponding dl-OrJointTCI-StateToAddModList-r17 and / or dl-OrJointTCI-StateToReleaseList-r17 can be separately configured for each Symbol type in PDSCH-Config; the configuration TCI state set corresponding to a certain Symbol type is maintained based on the tci-StatesToAddModList and tci-StatesToReleaseList (when joint mode is adopted, the configuration TCI state set corresponding to a certain Symbol type can be maintained based on the dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17) corresponding to the Symbol type. For example, new tci-StatesToAddModList and / or tci-StatesToReleaseList (when joint mode is adopted, new dl-OrJointTCI-StateToAddModList-r17 and / or dl-OrJointTCI-StateToReleaseList-r17) are introduced in PDSCH-Config for SBFD symbol, and the existing tci-StatesToAddModList and tci-StatesToReleaseList (when joint mode is adopted, the existing dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17) are used for the maintenance of the configuration TCI state set corresponding to non-SBFD symbol.

[0167] When the configuration parameters corresponding to each Symbol type are provided / determined based on the respective PDSCH-Config, the configuration TCI state set corresponding to a certain Symbol type is maintained based on tci-StatesToAddModList and tci-StatesToReleaseList in the PDSCH-Config corresponding to the Symbol type (when the joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 in the PDSCH-Config).

[0168] The following describes the related embodiments of PDCCH reception by taking the first downlink reception including PDCCH corresponding to the first CORESET as an example.

[0169] In some embodiments, the first downlink reception includes PDCCH corresponding to the first CORESET;

[0170] The time domain unit where the reception occasion of the first CORESET is located corresponds to the same time domain type; or,

[0171] The time domain unit where the reception occasion of the first CORESET is located can correspond to multiple time domain types or all time domain types.

[0172] That is, in the case where the first downlink reception includes PDCCH corresponding to the first CORESET, the time domain unit where the first downlink reception is located corresponds to the same time domain type; or, the time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

[0173] Optionally, in the case where the time domain unit where the reception occasion of the first CORESET is located corresponds to the same time domain type, the time domain type to which the time domain unit where the reception occasion of the first CORESET is located corresponds is determined by at least one of the following:

[0174] The configuration information of the first CORESET;

[0175] The configuration information of each search space in the search space (Search Space) associated with the first CORESET;

[0176] The protocol stipulates;

[0177] The higher layer parameter.

[0178] In the case that the time domain type corresponding to the time domain unit where the reception occasion of the first CORESET is located is determined by the configuration information of the first CORESET (i.e., the first item described above), and the configuration information of each search space in the search space associated with the first CORESET (i.e., the second item described above), the determination operation of the time domain type can be understood as including the following operation: the UE determines the time domain type corresponding to the time domain unit where all reception occasions of the first CORESET are located based on all search spaces associated with the first CORESET.

[0179] Optionally, the configuration information of the first CORESET includes at least one of the following:

[0180] The identification of the first CORESET, a value of the identification of the first CORESET being used to determine the time domain type corresponding to the time domain unit where the reception occasion of the first CORESET is located;

[0181] The second indication of the first CORESET, the second indication being used to indicate the time domain type, and the time domain type corresponding to the time domain unit where the reception occasion of the first CORESET is located being the time domain type indicated by the second indication.

[0182] Optionally, the configuration information of each search space includes at least one of the following:

[0183] The identification of each search space, a value of the identification of each search space being used to determine the time domain type corresponding to the time domain unit where the reception occasion of each search space is located respectively;

[0184] The third indication of each search space, the third indication being used to indicate the time domain type, and the time domain type corresponding to the time domain unit where the reception occasion of each search space is located being the time domain type indicated by the third indication of each search space.

[0185] Here, the identification of a search space can be used to indicate the Symbol type corresponding to the reception occasion of the CORESET associated with the search space. That is, in the case that the search space is associated with the first CORESET, the Symbol type of the reception occasion of the first CORESET can be indicated by the identification of the search space.

[0186] Correspondingly, the third indication of a search space can be used to indicate the Symbol type corresponding to the reception occasion of the CORESET associated with the search space. That is, in the case that the search space is associated with the first CORESET, the Symbol type of the reception occasion of the first CORESET can be indicated by the third indication of the search space.

[0187] Optionally, the method further comprises:

[0188] The terminal receives second information from the network side device, and the second information is used to indicate at least one of the following:

[0189] The transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET, M being an integer greater than or equal to 1.

[0190] The transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET, M being an integer greater than or equal to 1.

[0191] Optionally, the transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET are indicated by the same MAC CE; or,

[0192] The transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET are indicated by different MAC CEs.

[0193] Here, the transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET are indicated by different MAC CEs, which can be understood as using independent MAC CEs to respectively indicate the transmission parameters corresponding to the receiving occasions of each time domain type.

[0194] Optionally, in the case of indicating the transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET by the same MAC CE, the MAC CE comprises at least one of the following:

[0195] M first indication domains, the M first indication domains being used to respectively indicate the transmission parameters corresponding to the receiving occasions of each time domain type in the M time domain types;

[0196] A second indication domain, the second indication domain being used to jointly indicate the transmission parameters corresponding to the receiving occasions of each time domain type in the M time domain types.

[0197] Optionally, in the case of indicating the transmission parameters corresponding to the receiving occasions of each time domain type corresponding to the first CORESET by different MAC CEs, the MAC CE comprises at least one of the following:

[0198] A third indication domain, used to indicate the time domain type corresponding to the MAC CE;

[0199] A fourth indication domain, used to indicate the transmission parameters corresponding to the corresponding time domain type;

[0200] a fifth indication field, used for indicating an activation state or a deactivation state of a transmission parameter corresponding to a time domain type.

[0201] For the convenience of understanding, the embodiments of the present application exemplarily illustrate the CORESET Occasion configuration mode.

[0202] For a certain CORESET (such as the first CORESET), based on its usage situation (for example, its association situation with one or more Search Spaces, and the time domain monitoring configuration situation of these associated Search Spaces), it can correspond to multiple Occasions (or at least one Occasion) in the time domain.

[0203] For the configuration of the time-frequency location of a certain CORESET, any one of the CORESET Occasion configuration mode 1 and the CORESET Occasion configuration mode 2 can be adopted:

[0204] CORESET Occasion configuration mode 1: the Occasion corresponding to the CORESET can only be located in the Symbol corresponding to a single Symbol type.

[0205] Here, the single Symbol type (assuming a given Symbol type (i.e. the first time domain type)) can be determined by one of the following (1) to (4):

[0206] (1) Based on the ControlResourceSetId value range in which the ControlResourceSetId of the CORESET is located, the given Symbol type is determined. Here, it is assumed that each Symbol type corresponds to an independent ControlResourceSetId value range, which can be specified by the protocol or configured by the high layer signaling; the ControlResourceSetId value ranges corresponding to different Symbol types do not intersect with each other. When configuring a CORESET corresponding to a certain Symbol type, the ControlResourceSetId of the CORESET is required to be located in the ControlResourceSetId value range corresponding to the Symbol type.

[0207] (2) In the configuration information of each CORESET, a new parameter is introduced to indicate the Symbol type corresponding to the CORESET.

[0208] (3) Take the Symbol type corresponding to at least one Search Space associated with the CORESET as the given Symbol type. Here, it is assumed or required that the Symbol types corresponding to each of the at least one associated Search Space are the same. When determining the Symbol type corresponding to a certain Search Space, one of (3.1) to (3.3) can be used:

[0209] (3.1) Determine the given Symbol type based on the SearchSpaceId value range in which the SearchSpaceId of the Search Space is located. Here, it is assumed that each of the Symbol types corresponds to an independent SearchSpaceId value range, which can be specified by the protocol or configured by high-layer signaling; the SearchSpaceId value ranges corresponding to different Symbol types do not intersect with each other. When configuring a Search Space corresponding to a certain Symbol type, the SearchSpaceId of the Search Space is required to be located in the SearchSpaceId value range corresponding to the Symbol type.

[0210] (3.2) Introduce a new parameter in the configuration information of each Search Space to indicate the Symbol type corresponding to the Search Space.

[0211] (3.3) Determine the Symbol type corresponding to the Symbol in which the CORESET Occasion is located based on the configuration information of the CORESET and the Search Space.

[0212] (4) The given Symbol type is specified by the protocol or configured by a high-layer parameter. For example, it is specified by the protocol that the Occasion corresponding to CORESET#0 can only be located in a non-SBFD symbol.

[0213] At this time, either the network side can ensure in configuration that all Occasions corresponding to the CORESET are located only in the Symbol corresponding to the given Symbol type, or the network side does not ensure in configuration that any Occasion corresponding to the CORESET only occurs in the Symbol corresponding to the given Symbol type, but the UE only considers that the Occasion located in the Symbol corresponding to the given Symbol type (completely located in the Symbol corresponding to the given Symbol type, or the number of Symbols located in the Symbol corresponding to the given Symbol type is not less than M, or the proportion of the Symbol located in the Symbol corresponding to the given Symbol type is not less than N) is valid, or considers that the Occasion not located in the Symbol corresponding to the given Symbol type (not completely located in the Symbol corresponding to the given Symbol type, or the number of Symbols located in the Symbol corresponding to the given Symbol type is less than M, or the proportion of the Symbol located in the Symbol corresponding to the given Symbol type is less than N) is invalid.

[0214] CORESET Occasion configuration mode 2: the Occasion corresponding to the CORESET can be located in the Symbol corresponding to each (or more than one) Symbol type.

[0215] The CORESET Occasion configuration mode 2 can be understood as that the network side does not need to pay attention to or ensure in configuration which Symbol type the Occasion corresponding to the CORESET is located in. For example, the Occasion corresponding to the CORESET can be located in the SBFD symbol, or in the non-SBFD symbol, or part of the Occasion is located in the SBFD symbol and part of the Occasion is located in the non-SBFD symbol.

[0216] Optionally, for a certain Occasion of the CORESET, the Symbol type corresponding to the Symbol where the Occasion is located is taken as the Symbol type corresponding to the Occasion.

[0217] For a CORESET with Index not equal to 0, it can be further configured (e.g. configured based on tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in ControlResourceSet) with a set of available TCI states, each TCI state included in the set of available TCI states can be selected from the set of configured TCI states configured for downlink reception from network side.

[0218] When adopting the general TCI state configuration manner 1 (without distinguishing whether to adopt the CORESET Occasion configuration manner 1 or the CORESET Occasion configuration manner 2), a TCI state can be selected from the unified set of configured TCI states as the set of available TCI states for the CORESET.

[0219] When adopting the general TCI state configuration manner 2, it can be divided into the following two cases:

[0220] When adopting the CORESET Occasion configuration manner 1, a TCI state can be selected from the set of configured TCI states corresponding to the given Symbol type as the set of available TCI states for the CORESET.

[0221] When adopting the CORESET Occasion configuration manner 2, for each (or any) Symbol type, a TCI state can be selected from the set of configured TCI states corresponding to the Symbol type as the set of available TCI states for the CORESET for the Symbol type. It can be understood that for the CORESET, there is a corresponding set of available TCI states for each involved Symbol type. Accordingly, corresponding configuration parameters can be introduced in ControlResourceSet. For example, tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in ControlResourceSet are used to configure the set of available TCI states for non-SBFD symbol, and new parameters are introduced to configure the set of available TCI states for SBFD symbol.

[0222] For ease of understanding, the embodiments of the present application exemplarily illustrate the PDCCH TCI state indication manner of CORESET Occasion.

[0223] For the indication of the corresponding TCI state of PDCCH detection within the CORESET Occasion, any one of the PDCCH TCI state indication manner 1 and the PDCCH TCI state indication manner 2 can be adopted:

[0224] The PDCCH TCI state indication manner 1: without distinguishing the Symbol type, indicating that all Occasions of the CORESET uniformly use / cross Symbol type share the TCI state.

[0225] The PDCCH TCI state indication manner 1 corresponds to the general TCI state configuration manner 1 (the two manners correspond to each other, which can be understood as the two manners are used in combination; the same understanding is followed hereinafter), and can be applied to the CORESET Occasion configuration manner 1 and the CORESET Occasion configuration manner 2 at the same time.

[0226] When the Index of the CORESET is 0 (i.e., CORESET#0), a Medium Access Control (MAC) Control Element (CE) that is independent of the Symbol type (or does not consider the influence of the Symbol type) can be used to indicate a certain TCI state in the set of configured TCI states as the TCI state that is uniformly used / cross Symbol type shared by all Occasions of the CORESET; when the Index of the CORESET is not 0, the MAC CE that is independent of the Symbol type (or does not consider the influence of the Symbol type) can be used to indicate a certain TCI state in the set of available TCI states configured for the CORESET as the TCI state that is uniformly used / cross Symbol type shared by all Occasions of the CORESET.

[0227] The MAC CE here can be understood as the TCI State Indication for UE-specific PDCCH MAC CE, or a MAC CE that has the same or similar function.

[0228] For PDCCH TCI state indication manner 1, the existing format definition of TCI State Indication for UE-specific PDCCH MAC CE can be followed. Based on the single TCI state indicated by this MAC CE for this CORESET, it can be applied for PDCCH detection within the Occasions corresponding to any Symbol type for this CORESET, or in other words, it does not restrict the Symbol type corresponding to the Occasions for which the indicated TCI state is applied for PDCCH detection.

[0229] PDCCH TCI state indication manner 2: Indicate respective TCI states for the Occasions corresponding to different Symbol types for this CORESET.

[0230] Generally, PDCCH TCI state indication manner 2 corresponds to general TCI state configuration manner 2. Alternatively, PDCCH TCI state indication manner 2 can also correspond to general TCI state configuration manner 1. PDCCH TCI state indication manner 2 is mainly applied for CORESET Occasion configuration manner 2, and can also be applied for CORESET Occasion configuration manner 1.

[0231] When using MAC CE to indicate the TCI state corresponding to each Symbol type to indicate that the PDCCH detection within the Occasions corresponding to each Symbol type for this CORESET respectively applies the TCI state, either of PDCCH TCI state indication manner 2-1 and PDCCH TCI state indication manner 2-2 can be adopted:

[0232] PDCCH TCI state indication manner 2-1: Use the same MAC CE to indicate the TCI state corresponding to each (or at least one) Symbol type.

[0233] PDCCH TCI state indication manner 2-1 can be understood as that a single MAC CE can be used to indicate the TCI state corresponding to more than one Symbol type.

[0234] Specifically, one possible implementation is (assuming it is implementation 1): adjust the existing format definition of TCI State Indication for UE-specific PDCCH MAC CE, or introduce a new MAC CE, in which the TCI state indication field (i.e., the first indication field) corresponding to each Symbol type is set separately in the MAC CE. Wherein, the TCI state indication field corresponding to a certain Symbol type is based on any one of (5) and (6), indicating the TCI state corresponding to the Symbol type:

[0235] (5) TCI-StateId. When the general TCI state configuration mode 2 is adopted, when the Index of the CORESET is 0 (i.e., CORESET#0), the network side needs to ensure that the TCI state corresponding to the TCI-StateId is located in the configuration TCI state set corresponding to the Symbol type; when the Index of the CORESET is not 0, the network side needs to ensure that the TCI state corresponding to the TCI-StateId is located in the available TCI state set corresponding to the Symbol type.

[0236] (6) The position in the configuration / available TCI state set. Here, the "position in the configuration / available TCI state set" can be understood as the serial number or subscript of the indicated TCI state in the unified configuration TCI state set (when applied to the general TCI state configuration mode 1 and the Index of the CORESET is 0), or the serial number or subscript in the available TCI state set configured for the CORESET (when applied to the general TCI state configuration mode 1 and the Index of the CORESET is not 0), or the serial number or subscript in the configuration / available TCI state set corresponding to the Symbol type (when applied to the general TCI state configuration mode 2) (the TCI state set in these cases is required to be maintained in the form of an ordered set). When the Index of the CORESET is 0 (i.e., CORESET#0), the configuration TCI state set is used; when the Index of the CORESET is not 0, the available TCI state set is used.

[0237] The TCI state indication field corresponding to each Symbol type can be arranged in sequence in the MAC CE based on the order of Symbol types. The order of Symbol types can be specified by the protocol or configured by higher layer signaling. For example, it is specified by the protocol that the TCI state indication field corresponding to non-SBFD symbol appears first in a certain MAC CE, and then the TCI state indication field corresponding to SBFD symbol appears after it.

[0238] When implementation 1 is adopted, PDCCH TCI state indication mode 2-1 can be applied to general TCI state configuration mode 1, general TCI state configuration mode 2-1, general TCI state configuration mode 2-2, and general TCI state configuration mode 2-3.

[0239] Another possible implementation is (assuming implementation 2): follow the existing format definition of TCI State Indication for UE-specific PDCCH MAC CE, or use a similar format definition, and only set a single TCI state indication field in the MAC CE, which is used to indicate a single TCI-StateId or a single position in the configured / available TCI state set. Optionally, based on the single ID or single position indicated by this indication and a pre-defined rule, determine N IDs or N positions (assuming that the number of Symbol types corresponding to the TCI state that needs to be indicated is N). For example, if the first ID / position is indicated in the MAC CE, then the determined N IDs / positions are: the first ID / position+i, i=0,…,N–1; or if the last ID / position is indicated in the MAC CE, then the determined N IDs / positions are: the last ID / position-i, i=0,…,N–1. Optionally, a modulo operation can be further introduced to avoid ID / position overflow. For example, each of the N IDs / positions determined above is further taken modulo (max ID+1) / total number of positions to obtain the final N IDs / positions (assuming that each ID / position is numbered from 0).

[0240] When implementation 2 is adopted, PDCCH TCI state indication mode 2-1 can be applied to general TCI state configuration mode 1, general TCI state configuration mode 2-1, general TCI state configuration mode 2-2, and general TCI state configuration mode 2-3.

[0241] When applied to the general TCI state configuration mode 1, a predefined rule can be introduced to determine the respective Symbol type corresponding to each of the N TCI states corresponding to the N IDs / positions determined by the implementation mode 2. The predefined rule can be that the N TCI states are sequentially corresponding to the N Symbol types based on the order of the TCI-StateId or the position in the configured / available TCI state set in ascending or descending order (see the corresponding description in the foregoing). For example, in the 2 TCI states, the TCI state with a smaller TCI-StateId corresponds to a non-SBFD symbol, and the TCI state with a larger TCI-StateId corresponds to an SBFD symbol.

[0242] When applied to the general TCI state configuration mode 2-1, based on the configuration information of each of the N TCI states corresponding to the N IDs / positions determined by the implementation mode 2, the Symbol type corresponding to each TCI state can be determined.

[0243] When applied to the general TCI state configuration mode 2-2, based on the position of each of the N TCI states corresponding to the N IDs / positions determined by the implementation mode 2 in the unified configured / available TCI state set, the Symbol type corresponding to each TCI state can be determined.

[0244] When applied to the general TCI state configuration mode 2-3:

[0245] When the implementation mode 2 indicates only a single ID, it is only applicable to the case where the ID space of the TCI states corresponding to different Symbol types allows overlap (i.e., the ID of the TCI state in the configured TCI state set corresponding to each Symbol type only requires not to be repeated in the configured TCI state set corresponding to the same Symbol type (i.e., the ID is required to be unique within a single Symbol type), and is allowed to be repeated in the configured TCI state set corresponding to different Symbol types (i.e., the ID space of different Symbol types allows overlap)), and at this time, based on the single ID indicated, a single TCI state corresponding to the single ID is determined in the configured TCI state set corresponding to each Symbol type, respectively, as the TCI state corresponding to each Symbol type.

[0246] When the implementation 2 indicates only a single location, based on the indicated single location, a single TCI state corresponding to the single location is determined in the configuration TCI state set corresponding to each Symbol type respectively, as the TCI state corresponding to each Symbol type respectively.

[0247] When the implementation 2 determines N IDs / locations, the N IDs / locations can be corresponded to the N Symbol types one by one based on ascending order or descending order based on the order of the Symbol types (see the corresponding description in the foregoing), and then based on the ID / location corresponding to each Symbol type respectively, a single TCI state corresponding to the ID / location is determined in the configuration TCI state set corresponding to each Symbol type respectively, as the TCI state corresponding to each Symbol type respectively.

[0248] PDCCH TCI state indication mode 2-2: use independent MAC CE to indicate the TCI state corresponding to each (or certain) Symbol type.

[0249] The PDCCH TCI state indication mode 2-2 can be understood as that a single MAC CE is only used to indicate the TCI state corresponding to a single Symbol type, and the MAC CE contains information / fields for indicating the Symbol type.

[0250] When a certain MAC CE is used to indicate the TCI state corresponding to a certain Symbol type, the TCI state indication field (i.e., the fourth indication field or the fifth indication field) in the MAC CE indicates the TCI state corresponding to the Symbol type based on any one of (7) and (8):

[0251] (7) TCI-StateId. When the general TCI state configuration mode 2 is adopted, when the Index of the CORESET is 0 (i.e., CORESET#0), it is required to be guaranteed by the network side that the TCI state corresponding to the TCI-StateId is located in the configuration TCI state set corresponding to the Symbol type; when the Index of the CORESET is not 0, it is required to be guaranteed by the network side that the TCI state corresponding to the TCI-StateId is located in the available TCI state set corresponding to the Symbol type.

[0252] (8) Position in the configured / available TCI state set. Here, the "Position in the configured / available TCI state set" can be understood as the serial number or index of the indicated TCI state in the unified configured TCI state set (when applied to the general TCI state configuration method 1 and the Index of this CORESET is 0), the available TCI state set configured for this CORESET (when applied to the general TCI state configuration method 1 and the Index of this CORESET is not 0), or the configured / available TCI state set corresponding to this Symbol type (when applied to the general TCI state configuration method 2) (it is required that the TCI state set in these cases is maintained in the form of an ordered set). When the Index of this CORESET is 0 (i.e., CORESET#0), the configured TCI state set is used; when the Index of this CORESET is not 0, the available TCI state set is used.

[0253] PDCCH TCI state indication method 2-1 can be applied to the general TCI state configuration method 1, the general TCI state configuration method 2-1, the general TCI state configuration method 2-2, and the general TCI state configuration method 2-3.

[0254] For the PDCCH reception / detection (or PDCCH reception / detection within this Occasion) corresponding to a certain Occasion of CORESET#0 (assuming that the Symbol type corresponding to it is a given Symbol type), when determining the QCL assumption / TCI state corresponding to it, the following two cases (Case) are considered:

[0255] Case1: If the UE receives a MAC CE activation command indicating the application of the TCI state for CORESET#0, the TCI state indicated by this MAC CE activation command is used when performing the PDCCH reception / detection;

[0256] Case2: If the UE does not receive a MAC CE activation command indicating the application of the TCI state for CORESET#0 after the last random access procedure (which can further require that this random access procedure is not initiated by the PDCCH command for triggering the contention-free random access procedure), the QCL assumption corresponding to the SSB identified by the UE in this last random access procedure is used.

[0257] When the PDCCH reception / detection corresponding to this Occasion is determined to correspond to the TCI state based on Case 1, for the judgment of “MAC CE activation command indicating the applied TCI state for CORESET#0”, the description is as follows:

[0258] When PDCCH TCI state indication manner 1 is adopted, as long as the UE receives any one or more MAC CE activation commands indicating the applied TCI state for CORESET#0, it is considered to satisfy Case 1.

[0259] When PDCCH TCI state indication manner 2 is adopted, only when the UE receives at least one MAC CE activation command indicating the applied TCI state for CORESET#0 and for a given Symbol type (for example, when PDCCH TCI state indication manner 2-1 is adopted, and one MAC CE is received, and the TCI state corresponding to the given Symbol type is indicated in the MAC CE, or when PDCCH TCI state indication manner 2-2 is adopted, and one MAC CE for the given Symbol type is received), it is considered to satisfy Case 1.

[0260] When the PDCCH reception / detection corresponding to this Occasion is determined to correspond to the QCL assumption based on Case 2, for the judgment of “MAC CE activation command indicating the applied TCI state for CORESET#0”, the above description can be followed, and for the judgment of “the last random access procedure (which can further require that this random access procedure is not initiated by the PDCCH command for triggering the contention-free random access procedure)”, the description is as follows:

[0261] When SSB transmission manner 1 is adopted, any of the following (I) and (II) can be adopted:

[0262] (I) Ignore the impact of Symbol type, always consider that the judgment for “the last random access procedure (which can further require that this random access procedure is not initiated by the PDCCH command for triggering the contention-free random access procedure)” needs to be considered;

[0263] (II) Only when the given Symbol type is the same as the single Symbol type corresponding to the SSB transmission, the judgment for “the last random access procedure (which can further require that this random access procedure is not initiated by the PDCCH command for triggering the contention-free random access procedure)” needs to be considered, otherwise this judgment does not need to be considered;

[0264] When the judgment for "the latest random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" is not required to be considered, it can be understood that if the UE does not receive the MAC CE activation command indicating the applied TCI state for CORESET#0, it is considered to satisfy the judgment condition of Case 2, at this time when determining the corresponding QCL assumption / TCI state of the PDCCH reception / detection corresponding to this Occasion, the UE can use the QCL assumption corresponding to the SSB identified in the latest random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure), or the QCL assumption corresponding to the SSB identified by the UE in the initial access procedure, or the predefined QCL assumption / TCI state (which can be specified by the protocol or configured by the high layer signaling);

[0265] When the judgment for "the latest random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" is required to be considered, the operation in the above Case 2 can be followed (at this time there is only one set of SSB to RO mapping, and the random access procedure does not need to be distinguished by Symbol type again).

[0266] When SSB transmission mode 2 is adopted, if SSB attribute mode 1 is adopted, the operation when SSB transmission mode 1 is adopted can be followed; if SSB attribute mode 2 is adopted, any one of the following (III) and (IV) can be adopted:

[0267] (III) Any random access procedure (may further require that the random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure) satisfies the judgment for "the latest random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" (i.e. matches "random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" in this judgment);

[0268] (IV) Only the random access procedure (may further require that the random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure) corresponding to the given Symbol type satisfies the judgment for "the latest random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" (i.e. matches "random access procedure (may further require that this random access procedure is not initiated by the PDCCH command for triggering contention-free random access procedure)" in this judgment).

[0269] Here, the "random access procedure corresponding to the given Symbol type" can be understood as the SSB selection based on the SSB transmission properties corresponding to the given Symbol type, and / or the random access procedure initiated by the RO resource corresponding to the given Symbol type (generally, there is a mapping of SSB to RO corresponding to the given Symbol type).

[0270] For the PDCCH reception / detection corresponding to a CORESET with Index not equal to 0 (assuming its corresponding Symbol type is the given Symbol type) (or, the PDCCH reception / detection within the CORESET), when determining its corresponding QCL assumption / TCI state, when adopting SSB property way 2, at least one of the following (V) and (VI) is included:

[0271] (V) If the network side device does not provide the UE with the configuration of the TCI state for the CORESET through tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList, or the network side device has provided the UE with the initial configuration containing more than one TCI state for the CORESET through tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList, but the UE does not receive the MAC CE activation command for activating one of the TCI states for the CORESET, the UE assumes that the dedicated demodulation reference signals (DM-RS) antenna port associated with the PDCCH reception is quasi co-located with the SSB identified by the UE in the initial access process and corresponding to the given Symbol type;

[0272] (VI) If the network-side device has provided the UE with a configuration containing more than one TCI state for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList as a Reconfiguration with sync procedure, but the UE does not receive a MAC CE activation command activating one of the TCI states for the CORESET, the UE assumes that the DM-RS antenna ports associated with PDCCH reception are quasi co-located with the SSB or CSI-RS resource identified by the UE in the random access procedure initiated by the Reconfiguration with sync procedure and corresponding to the given Symbol type.

[0273] The following describes the related embodiments of PDSCH reception by taking the first downlink reception including PDSCH as an example.

[0274] In some embodiments, the first downlink reception includes PDSCH.

[0275] The method further includes:

[0276] The terminal receives third information from the network-side device, and the third information is used to indicate at least one of the following:

[0277] The activated transmission parameters corresponding to all time domain units corresponding to the first downlink reception;

[0278] Among the N time domain types corresponding to the first downlink reception, the activated transmission parameters corresponding to the time domain units corresponding to each time domain type respectively, and N is an integer greater than or equal to 1.

[0279] Optionally, among the N time domain types corresponding to the first downlink reception, the activated transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by the same MAC CE; or,

[0280] Among the N time domain types corresponding to the first downlink reception, the activated transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs.

[0281] Here, the activated transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs, which can be understood as using independent MAC CEs to respectively indicate the activated transmission parameters corresponding to the time domain units corresponding to each time domain type.

[0282] Optionally, in the case that the N time domain types corresponding to the first downlink reception are indicated by the same MAC CE, and each time domain unit corresponding to each time domain type corresponds to an activated transmission parameter, the MAC CE comprises at least one of the following:

[0283] N sixth indication fields, the N sixth indication fields are used to respectively indicate the activated transmission parameter corresponding to each time domain type in the N time domain types;

[0284] a seventh indication field, the seventh indication field is used to jointly indicate the activated transmission parameter corresponding to each time domain type in the N time domain types.

[0285] Optionally, in the case that the N time domain types corresponding to the first downlink reception are indicated by different MAC CEs, and each time domain unit corresponding to each time domain type corresponds to an activated transmission parameter, the MAC CE comprises at least one of the following:

[0286] an eighth indication field, used to indicate the time domain type corresponding to the MAC CE;

[0287] a ninth indication field, used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.

[0288] Optionally, the terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, comprising at least one of the following:

[0289] in the case that the first downlink reception needs to apply the transmission parameter indicated by the third information, the terminal selects the transmission parameter whose time domain type is the same as the time domain type corresponding to the first downlink reception from the transmission parameter indicated by the third information as the transmission parameter corresponding to the first downlink reception;

[0290] in the case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is the same as the time domain type corresponding to the CORESET of the PDCCH, the terminal determines the transmission parameter corresponding to the CORESET of the PDCCH as the transmission parameter corresponding to the first downlink reception;

[0291] in the case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, the terminal determines the default transmission parameter or the predefined transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception;

[0292] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and at least one time domain type corresponding to the CORESET of the PDCCH does not contain the time domain type corresponding to the first downlink reception, the terminal determines the default transmission parameter corresponding to the first time domain type or the predefined transmission parameter as the transmission parameter corresponding to the first downlink reception.

[0293] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and at least one time domain type corresponding to the CORESET of the PDCCH contains the time domain type corresponding to the first downlink reception, the terminal selects the transmission parameter with the same time domain type as the time domain type corresponding to the first downlink reception from the transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameter corresponding to the first downlink reception.

[0294] In a case that the first downlink reception needs to apply the default transmission parameter, the terminal determines the default transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception.

[0295] In a case that the first downlink reception needs to apply the initial transmission parameter, the terminal determines the initial transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception.

[0296] For the convenience of understanding, the embodiments of the present application exemplarily illustrate the TCI state activation (Activation) / deactivation (Deactivation) mode corresponding to the PDSCH reception.

[0297] For the activation / deactivation of the TCI state corresponding to the PDSCH reception, any one of the PDSCH TCI state activation mode 1 and the PDSCH TCI state activation mode 2 can be adopted:

[0298] The PDSCH TCI state activation mode 1: without distinguishing the Symbol type, the activated TCI states (the activated TCI states can be understood as one or more activated TCI states, or at least one activated TCI state; the following is based on the understanding here, and will not be repeated) are determined to be used uniformly / shared across the Symbol type.

[0299] The PDSCH TCI state activation mode 1 can correspond to the general TCI state configuration mode 1.

[0300] The MAC CE that is independent of (or does not consider the impact of) the Symbol type can be used to activate / deactivate each TCI state in the unified configured TCI state set to determine the activated TCI states that are uniformly used / shared across the Symbol types. The MAC CE here can be understood as the MAC CE for activating / deactivating the TCI states of the PDSCH of a specific UE (TCI States Activation / Deactivation for UE-specific PDSCH MAC CE), or a MAC CE that is the same as or similar to the function thereof.

[0301] For PDSCH TCI state activation mode 1, the existing format definition of the MAC CE for activating / deactivating the TCI states of the PDSCH of a specific UE can be followed. A certain TCI state in the activated TCI states determined based on the MAC CE can be applied to the PDSCH reception corresponding to any Symbol type, or in other words, the PDSCH reception corresponding to the Symbol type to which the activated TCI states are applied is not limited.

[0302] PDSCH TCI state activation mode 2: determine the respective activated TCI states for different Symbol types.

[0303] Generally, PDSCH TCI state activation mode 2 corresponds to general TCI state configuration mode 2. Alternatively, PDSCH TCI state activation mode 2 can also correspond to general TCI state configuration mode 1.

[0304] When using the MAC CE to activate / deactivate the TCI states corresponding to each Symbol type to determine the respective activated TCI states corresponding to each Symbol type, either of PDSCH TCI state activation mode 2-1 and PDSCH TCI state activation mode 2-2 can be adopted:

[0305] PDSCH TCI state activation mode 2-1: use the same MAC CE to activate / deactivate the TCI states corresponding to each (or at least one) Symbol type.

[0306] PDSCH TCI state activation manner 2-1 can be understood as a single MAC CE can be used to activate / deactivate more than one TCI state corresponding to different Symbol types. Specifically, any one of PDSCH TCI state activation manner 2-1-1 to PDSCH TCI state activation manner 2-1-3 can be adopted:

[0307] PDSCH TCI state activation manner 2-1-1: in the case that the TCI-StateId values of the TCI states corresponding to different Symbol types do not conflict with each other, the existing format definition of TCI States Activation / Deactivation for UE-specific PDSCH MAC CE is followed, and each TCI state activation / deactivation status indication bit in the MAC CE corresponds to a certain configured TCI state based on TCI-StateId.

[0308] PDSCH TCI state activation manner 2-1-1 can be applied to general TCI state configuration manner 2-1, general TCI state configuration manner 2-2 and general TCI state configuration manner 2-3.

[0309] PDSCH TCI state activation manner 2-1-2: adjust the existing format definition of TCI States Activation / Deactivation for UE-specific PDSCH MAC CE, or introduce a new MAC CE, and the TCI state activation / deactivation status indication bits in the MAC CE are not explicitly distinguished Symbol type respectively set, and each TCI state activation / deactivation status indication bit corresponds to a certain configured TCI state based on the position in the unified configured TCI state set.

[0310] Here, the position in the unified configured TCI state set can be understood as the serial number or subscript of each TCI state in the set (which is required to be maintained in the form of an ordered set).

[0311] PDSCH TCI state activation manner 2-1-2 can be applied to general TCI state configuration manner 2-1 and general TCI state configuration manner 2-2.

[0312] PDSCH TCI state activation manner 2-1-3: adjust the existing format definition of TCI States Activation / Deactivation for UE-specific PDSCH MAC CE, or introduce a new MAC CE, and distinguish the Symbol type in the MAC CE to set the TCI state activation / deactivation state indication bit corresponding to each Symbol type respectively.

[0313] For the TCI state activation / deactivation state indication bit corresponding to a certain Symbol type, each bit can correspond to a certain TCI state applicable to the Symbol type based on any one of (9) and (10):

[0314] (9) TCI-StateId;

[0315] (10) the position in the configured TCI state set.

[0316] The TCI state activation / deactivation state indication bits corresponding to each Symbol type can be arranged in sequence in the MAC CE based on the order of the Symbol type. The order of the Symbol type can be specified by the protocol or configured by the high layer signaling. For example, it is specified by the protocol that in a certain MAC CE, the TCI state activation / deactivation state indication bits corresponding to the non-SBFD symbol appear first, and then the TCI state activation / deactivation state indication bits corresponding to the SBFD symbol appear after that.

[0317] PDSCH TCI state activation manner 2-1-3 can be applied to general TCI state configuration manner 1, general TCI state configuration manner 2-1, general TCI state configuration manner 2-2 and general TCI state configuration manner 2-3, and the related operation is described as follows:

[0318] Firstly, based on the correspondence of TCI-StateId.

[0319] When corresponding based on TCI-StateId, for a certain Symbol type, the first bit in the corresponding TCI state activation / deactivation status indication bit (which can be referred to as the first bit sequence) can correspond to the TCI-StateId with a value of 0, and the remaining bits in the first bit sequence correspond to the TCI-StateId with other values in turn (i.e., the second bit in the first bit sequence corresponds to the TCI-StateId with a value of 1, and so on). The length of the first bit sequence is configured by the higher layer signaling, or is determined based on the maximum value of the TCI-StateId configured for the Symbol type (for example, the length = TCI-StateId maximum value + 1), or is determined based on the maximum value of the TCI-StateId specified by the protocol.

[0320] Optionally, if in the general TCI state configuration mode 2-1, each Symbol type corresponds to a different range of TCI-StateId values, the first bit in the first bit sequence can correspond to the minimum TCI-StateId in the range of TCI-StateId values (which can be referred to as the first ID range) corresponding to the Symbol type, and the remaining bits in the first bit sequence correspond to the remaining TCI-StateId in the first ID range in turn (correspondingly, the length of the first bit sequence is the number of TCI-StateId contained in the first ID range); if in the general TCI state configuration mode 2-1, the Symbol type is distinguished based on the new parameter of the TCI state, for a certain Symbol type, the minimum TCI-StateId in the configured TCI state set (which can be referred to as the first TCI state set) corresponding to the Symbol type can correspond to the first bit in the first bit sequence, and the remaining TCI states in the first TCI state set can correspond to the remaining bits in the first bit sequence in turn based on the order of TCI-StateId from small to large.

[0321] Secondly, based on the correspondence of the position in the configured TCI state set.

[0322] When the correspondence is based on the position in the configured TCI state set, for a certain Symbol type, the first bit in the corresponding TCI state activation / deactivation status indication bits (may be referred to as the second bit sequence) can correspond to the first TCI state in the unified configured TCI state set (when applied to the general TCI state configuration method 1), or correspond to the first TCI state in the configured TCI state set corresponding to the Symbol type (when applied to the general TCI state configuration method 2), and the remaining bits in the second bit sequence correspond to the other TCI states in the set in turn (i.e. the second bit in the second bit sequence corresponds to the next TCI state in the set, and so on; here it is assumed that the unified configured TCI state set or the configured TCI state set corresponding to each Symbol type is an ordered set). The length of the second bit sequence is configured by the higher layer signaling, or determined based on the maximum number of TCI states allowed to be configured for a single Symbol type.

[0323] PDSCH TCI state activation method 2-2: use independent MAC CEs to activate / deactivate the TCI state corresponding to each (or a certain) Symbol type.

[0324] PDSCH TCI state activation method 2-2 can be understood as a single MAC CE is only used to activate / deactivate the TCI state corresponding to a single Symbol type, and contains information / fields for indicating the Symbol type in the MAC CE.

[0325] When a certain MAC CE is used to activate / deactivate the TCI state corresponding to a certain Symbol type, each TCI state activation / deactivation status indication bit in the MAC CE can correspond to a certain TCI state based on any one of (11) and (12):

[0326] (11) TCI-StateId;

[0327] (12) the position in the configured TCI state set.

[0328] PDSCH TCI state activation method 2-2 can be applied to general TCI state configuration method 1, general TCI state configuration method 2-1, general TCI state configuration method 2-2 and general TCI state configuration method 2-3, and the related operation is described as follows:

[0329] One, based on TCI-StateId correspondence.

[0330] When based on TCI-StateId correspondence, the first bit in the TCI state activation / deactivation status indication bit (which can be referred to as the third bit sequence) in the MAC CE can correspond to the TCI-StateId with a value of 0, and the remaining bits in the third bit sequence correspond to the TCI-StateId with other values in turn (i.e., the second bit in the third bit sequence corresponds to the TCI-StateId with a value of 1, and so on). The length of the third bit sequence is configured by the higher layer signaling, or determined based on the maximum value of the TCI-StateId configured for the Symbol type (for example, the length = TCI-StateId maximum value + 1), or determined based on the maximum value of the TCI-StateId specified by the protocol.

[0331] Optionally, if each Symbol type corresponds to a different range of TCI-StateId values in the general TCI state configuration method 2-1, the first bit in the third bit sequence can correspond to the minimum TCI-StateId in the range of TCI-StateId values (which can be referred to as the second ID range) corresponding to the Symbol type, and the remaining bits in the third bit sequence correspond to the remaining TCI-StateId in the second ID range in turn (correspondingly, the length of the third bit sequence is the number of TCI-StateId contained in the second ID range); if the Symbol type is distinguished based on the new parameter of the TCI state in the general TCI state configuration method 2-1, the minimum TCI-StateId in the configured TCI state set (which can be referred to as the second TCI state set) corresponding to the Symbol type can correspond to the first bit in the third bit sequence, and the remaining TCI states in the second TCI state set can correspond to the remaining bits in the third bit sequence in turn based on the order of TCI-StateId from small to large.

[0332] Two, based on the position in the configured TCI state set.

[0333] When corresponding to the location in the configured TCI state set, the first bit in the TCI state activation / deactivation status indication bits (may be referred to as the fourth bit sequence) in the MAC CE can correspond to the first TCI state in the unified configured TCI state set (when applied to the general TCI state configuration mode 1) or the configured TCI state set corresponding to the Symbol type (when applied to the general TCI state configuration mode 2), and the remaining bits in the fourth bit sequence correspond to the other TCI states in the set in turn (i.e. the second bit in the fourth bit sequence corresponds to the next TCI state in the set, and so on; here it is assumed that the unified configured TCI state set or the configured TCI state set corresponding to each Symbol type is an ordered set). The length of the fourth bit sequence is configured by higher layer signaling or determined based on the maximum number of TCI states allowed to be configured for a single Symbol type.

[0334] For a QCL assumption / TCI state applied for a certain PDSCH reception, at least one of (a) to (d) is included:

[0335] (a) For the case where the indicated TCI state is applied.

[0336] The "case where the indicated TCI state is applied" can include the case where there is a TCI indication field in the downlink scheduling DCI (including DCI format 1_1 / 1_2, etc.), and the time offset between the downlink scheduling DCI and the scheduled PDSCH is greater than or equal to a pre-defined threshold (for example, indicated by the parameter timeDurationForQCL).

[0337] When the general TCI state configuration manner 1 is adopted, and the PDSCH TCI state activation manner 1 is adopted, the PDSCH reception corresponding to any Symbol type all shares the unified configured TCI state set and the same set of activated TCI states. At this time, for the case of applying the TCI state indicated in the scheduling DCI (for example, the typical case of applying the TCI state indicated in the scheduling DCI includes: a certain PDSCH is scheduled by the DCI with the TCI indication field, and the time offset between the reception of the DCI and the PDSCH is equal to or greater than a pre-defined threshold timeDurationForQCL; this pre-defined threshold is determined based on the reported UE capability), no matter which Symbol type (or which Symbol type corresponding Symbol) the PDSCH reception corresponds to, the relevant indication field (for example, the TCI indication field) in the scheduling DCI always indicates the TCI state(s) applied by the PDSCH reception from the set of activated TCI states.

[0338] When the general TCI state configuration manner 2 is adopted, and the PDSCH TCI state activation manner 2 is adopted, each Symbol type can correspond to a respective configured TCI state set and a respective activated TCI state. At this time, for the case of applying the TCI state indicated in the scheduling DCI, the relevant indication field in the scheduling DCI indicates the TCI state(s) applied by the PDSCH reception from the activated TCI states corresponding to the Symbol type corresponding to the PDSCH reception (or the Symbol type corresponding to the Symbol(s) where the PDSCH reception is located).

[0339] (b) For the case of applying the QCL assumption / TCI state of PDCCH.

[0340] The case of "applying the QCL assumption / TCI state of PDCCH" can include the case where there is no TCI indication field in the downlink scheduling DCI (including DCI format 1_0 / 1_1 / 1_2, etc.), and the time offset between the downlink scheduling DCI and the scheduled PDSCH is greater than or equal to a pre-defined threshold (for example, indicated by the parameter timeDurationForQCL).

[0341] When the general TCI state configuration method 1 is adopted, and the PDCCH TCI state indication method 1 is adopted, the TCI state of the CORESET does not need to be distinguished according to the Symbol type, and the operation defined in the related specification (i.e., operation 0 in the following) can be followed.

[0342] When the general TCI state configuration method 2 is adopted, and the PDCCH TCI state indication method 2 is adopted, the TCI state of the CORESET needs to be determined according to the Symbol type. At this time, any one of (b1) and (b2) can be adopted:

[0343] (b1) The UE expects that the PDSCH reception and the corresponding PDCCH are respectively corresponding to the same Symbol type;

[0344] At this time, the network side ensures that the PDSCH reception and the corresponding PDCCH are respectively corresponding to the same Symbol type. Accordingly, the UE can follow the operation defined in the related specification (i.e., operation 0 in the following).

[0345] (b2) The PDSCH reception and the corresponding PDCCH are allowed to be respectively corresponding to different Symbol types;

[0346] When the PDSCH reception and the corresponding PDCCH are respectively corresponding to the same Symbol type, the above operation (i.e., operation 0 in the following) is followed.

[0347] When the PDSCH reception and the corresponding PDCCH are respectively corresponding to different Symbol types, any one of (b21) to (b23) can be adopted:

[0348] (b21) Operation 1 is performed;

[0349] (b22) When the CORESET of the PDCCH does not contain the Symbol type corresponding to the PDSCH reception in at least one Symbol type corresponding to the Occasion, operation 1 is performed;

[0350] (b23) When the CORESET of the PDCCH contains the Symbol type corresponding to the PDSCH reception in at least one Symbol type corresponding to the Occasion, operation 2 is performed.

[0351] The above operations 0 / 1 / 2 are described as follows (assuming that the Symbol type corresponding to the PDSCH reception is the first Symbol type):

[0352] Operation 0: The PDSCH reception applies the QCL assumption / TCI state of the corresponding PDCCH.

[0353] Operation 0 can be understood as: the UE assumes that the TCI state or QCL assumption of the PDSCH is the same as the TCI state or QCL assumption of the CORESET applied to the corresponding PDCCH reception.

[0354] It can be further required that the above-mentioned TCI state or QCL assumption of the CORESET applied to the corresponding PDCCH reception is the QCL assumption / TCI state of the CORESET applied in the symbol where the PDSCH reception is located.

[0355] Operation 1: The PDSCH reception applies the default QCL assumption corresponding to the first symbol type, or applies the predefined TCI state.

[0356] The default QCL assumption is described in the relevant description below.

[0357] The predefined TCI state can be specified by the protocol or configured by the high layer signaling; it can be determined separately for different symbol types, or determined uniformly without distinguishing the symbol types.

[0358] Operation 2: The PDSCH reception applies the TCI state corresponding to the CORESET corresponding to the corresponding PDCCH and the first symbol type.

[0359] Operation 2 can be understood as: if a certain PDSCH is scheduled by a DCI without a TCI indication field, and the time offset between the reception of the DCI and the PDSCH is equal to or greater than a predefined threshold timeDurationForQCL (this predefined threshold is determined based on the reported UE capability), when determining the quasi co-location of the antenna port of the PDSCH, the UE assumes that the QCL assumption / TCI state of the PDSCH is the same as the target QCL assumption / TCI state; here, the target QCL assumption / TCI state is the QCL assumption / TCI state corresponding to the first symbol type among the QCL assumption / TCI state applied to the CORESET used for the PDCCH reception carrying the DCI.

[0360] It can be further required that the above-mentioned target QCL assumption / TCI state is the QCL assumption / TCI state corresponding to the first symbol type among the QCL assumption / TCI state applied to the CORESET in the symbol where the PDSCH reception is located.

[0361] (c) For the case of applying the initial QCL assumption.

[0362] The case of applying initial QCL assumption can include the case that the time offset between the downlink scheduling DCI (including DCI format 1_0 / 1_1 / 1_2, etc.) and the scheduled PDSCH is less than a pre-defined threshold (e.g., indicated by parameter timeDurationForQCL).

[0363] When SSB transmission mode 1 is adopted, or SSB transmission mode 2 and SSB property mode 1 are adopted, the operation defined in the relevant specification can be followed (i.e., the scheduled PDSCH is quasi co-located with the SSB determined by the UE in the initial access procedure).

[0364] When SSB transmission mode 2 and SSB property mode 2 are adopted, if for the CORESET scheduling the PDSCH (i.e., the PDCCH carrying the DCI scheduling the PDSCH is detected by the UE in this CORESET), tci-PresentInDCI is set to 'enabled' or the tci-PresentDCI-1-2 parameter is configured, and the time offset between the DCI reception and the corresponding PDSCH is equal to or greater than timeDurationForQCL, before the UE receives the initial higher layer configuration for the TCI state and before receiving the activation command, the UE can assume that the DM-RS ports of the PDSCH are quasi co-located with the SSB determined in the initial access procedure and corresponding to the given Symbol type, the quasi co-location type (QCL Type, which can correspond to the parameter qcl-Type) is type A ('typeA'), and if applicable, the quasi co-location type is also type D ('typeD').

[0365] (d) For the case of applying default QCL assumption.

[0366] When the general TCI state configuration mode 1 and the PDCCH TCI state indication mode 1 are adopted, the TCI state of the CORESET does not need to be distinguished by Symbol type, at which time the operation defined in the relevant specification can be followed.

[0367] When the general TCI state configuration mode 2 is adopted, and the PDCCH TCI state indication mode 2 is adopted, it is necessary to distinguish the symbol type to determine the TCI state applicable to the CORESET. At this time, assuming that the corresponding symbol type of the PDSCH reception is the first symbol type, the UE determines that the PDSCH reception applies the default QCL assumption corresponding to the first symbol type on the serving cell (the default QCL assumption corresponding to the first symbol type on the serving cell of the PDSCH reception is: the quasi co-location of the RS involved / corresponding to the QCL parameter used for PDCCH QCL indication of the target CORESET in the target slot; here, the target slot is the latest slot corresponding to the first symbol type, in which the UE needs to monitor one or more CORESETs in the activated BWP of the serving cell of the PDSCH reception; and the target CORESET is the CORESET with the smallest controlResourceSetId among one or more CORESETs that need to be monitored in the target slot). The specific operation includes:

[0368] In the RRC connected mode, regardless of how tci-PresentInDCI and tci-PresentDCI-1-2 are configured (or in other words, independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2), if the network side device does not provide the UE with dl-OrJointTCI-StateList-r17, and the time offset between the reception of the DCI and the corresponding PDSCH is less than the pre-defined threshold timeDurationForQCL, and the network side device configures at least one TCI state with qcl-Type set to 'typeD' for the serving cell of the scheduled PDSCH, the UE performs at least one of the following (e) and (f):

[0369] (e) The UE can assume that the DM-RS port of the PDSCH is quasi co-located with the RS involved / corresponding to the QCL parameter used for PDCCH QCL indication of the target CORESET in the target slot, wherein the target slot is the latest slot corresponding to the symbol type corresponding to the PDSCH, in which the UE needs to monitor one or more CORESETs in the activated BWP of the serving cell of the PDSCH, and the target CORESET is the CORESET with the smallest controlResourceSetId among one or more CORESETs that need to be monitored in the target slot.

[0370] (f) If the network-side device configures the UE with enableDefaultTCI-StatePerCoresetPoolIndex, and in the high-layer parameter PDCCH-Config configured for the UE, two different coresetPoolIndex values are involved / contained in different ControlResourceSet, the UE can assume that the DM-RS ports of the PDSCH associated with a certain coresetPoolIndex value (i.e. the CORESET where the PDCCH scheduling the PDSCH is received is associated with the coresetPoolIndex value) and the QCL parameter used for PDCCH QCL indication of the target CORESET in the target slot are quasi co-located, wherein the target slot is the latest slot corresponding to the Symbol type corresponding to the PDSCH, and the target CORESET is the CORESET associated with the coresetPoolIndex value and the smallest controlResourceSetId among the one or more CORESETs that the UE needs to monitor in the active BWP of the serving cell where the PDSCH is located.

[0371] The following describes the related embodiments of the reception of the CSI-RS corresponding to the first NZP CSI-RS resource by taking the first downlink reception including the CSI-RS corresponding to the first NZP CSI-RS resource as an example.

[0372] In some embodiments, the first downlink reception includes the CSI-RS corresponding to the first NZP CSI-RS resource.

[0373] In the case where the first NZP CSI-RS resource is a periodic or semi-persistent resource, the time domain units where the reception occasions corresponding to the first NZP CSI-RS resource are located correspond to the same time domain type, or the time domain units where the reception occasions corresponding to the first NZP CSI-RS resource are located can correspond to multiple time domain types or all time domain types.

[0374] Optionally, the method further includes:

[0375] The terminal receives fourth information from the network-side device, and the fourth information is used to indicate at least one of the following:

[0376] The transmission parameters corresponding to all the reception occasions corresponding to the first NZP CSI-RS resource;

[0377] In the S time-domain types corresponding to the first NZP CSI-RS resource, each time-domain type corresponds to a receiving occasion, and each receiving occasion corresponds to a transmission parameter, and S is an integer greater than or equal to 1.

[0378] Optionally, the terminal determines the transmission parameter corresponding to the first downlink reception based on a first time-domain type corresponding to the first downlink reception, including:

[0379] In a case where the first NZP CSI-RS resource is an aperiodic resource, and a CSI-RS corresponding to the first NZP CSI-RS resource needs to apply a default transmission parameter, the terminal determines the default transmission parameter corresponding to the first time-domain type as the transmission parameter corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.

[0380] For ease of understanding, the embodiments of the present application exemplarily illustrate the configuration and determination manner of the TCI state corresponding to the NZP CSI-RS reception.

[0381] The NZP CSI-RS is generally configured and used in the granularity of NZP CSI-RS resource, and the NZP CSI-RS resource can be further distinguished into three resource types of periodic (Periodic), semi-persistent (Semi-persistent) and aperiodic (Aperiodic). In more application scenarios, the NZP CSI-RS resource is generally further organized into the form of NZP CSI-RS resource set for use (including triggering transmission, reference, etc.).

[0382] For the NZP CSI-RS resource of the resource type of Periodic or Semi-persistent, a plurality of Occasions (or at least one Occasion) can be corresponded in the time domain. Correspondingly, for the configuration of the time-frequency position of a certain Periodic / Semi-persistent NZP CSI-RS resource, any one of the CSI-RS Occasion configuration mode 1 and the CSI-RS Occasion configuration mode 2 can be adopted:

[0383] The CSI-RS Occasion configuration mode 1: the Occasion corresponding to the NZP CSI-RS resource can only be located in a Symbol corresponding to a single Symbol type.

[0384] The single Symbol type (given Symbol type) here can be determined by any one of (g) to (j):

[0385] (g) Determine the given Symbol type based on the NZP-CSI-RS-ResourceId value range that the NZP-CSI-RS-ResourceId of the NZP CSI-RS resource belongs to. Here it is assumed that each Symbol type corresponds to an independent NZP-CSI-RS-ResourceId value range, which can be specified by the protocol or configured by high layer signaling; the NZP-CSI-RS-ResourceId value ranges corresponding to different Symbol types do not intersect with each other. When a NZP CSI-RS resource corresponding to a certain Symbol type is configured, the NZP-CSI-RS-ResourceId of the NZP CSI-RS resource is required to be located in the NZP-CSI-RS-ResourceId value range corresponding to the Symbol type.

[0386] (h) Introduce a new parameter in the configuration information of each NZP CSI-RS resource to indicate the Symbol type corresponding to the NZP CSI-RS resource.

[0387] (i) Determine the Symbol type corresponding to the Symbol in which the NZP CSI-RS resource Occasion is located based on the configuration / activation information of the NZP CSI-RS resource.

[0388] (j) The given Symbol type is specified by the protocol or configured by high layer parameters. For example, it is specified by the protocol that the Occasion corresponding to the NZP CSI-RS resource can only be located in the non-SBFD symbol.

[0389] At this time, either the network side can ensure that all Occasions corresponding to the NZP CSI-RS resource are located only in the Symbol corresponding to the given Symbol type at the time of configuration / activation, or the network side can not ensure that any Occasion corresponding to the NZP CSI-RS resource only occurs in the Symbol corresponding to the given Symbol type at the time of configuration, but the UE only considers that the Occasion located in the Symbol corresponding to the given Symbol type (completely located in the Symbol corresponding to the given Symbol type, or the number of Symbols located in the Symbol corresponding to the given Symbol type is not less than M, or the proportion of the Symbol located in the Symbol corresponding to the given Symbol type is not less than N) is effective, or considers that the Occasion not located in the Symbol corresponding to the given Symbol type (not completely located in the Symbol corresponding to the given Symbol type, or the number of Symbols located in the Symbol corresponding to the given Symbol type is less than M, or the proportion of the Symbol located in the Symbol corresponding to the given Symbol type is less than N) is invalid.

[0390] CSI-RS Occasion configuration mode 2: the Occasion corresponding to the NZP CSI-RS resource can be located in the Symbol corresponding to each (or more than one) Symbol type.

[0391] The CSI-RS Occasion configuration mode 2 can be understood as that the network side does not need to pay attention to or ensure in which Symbol corresponding to the Symbol type the Occasion corresponding to the NZP CSI-RS resource is located at the time of configuration. For example, the Occasion corresponding to the NZP CSI-RS resource can all be located in the SBFD symbol, or all be located in the non-SBFD symbol, or part of the Occasion is located in the SBFD symbol and part of the Occasion is located in the non-SBFD symbol.

[0392] Optionally, for a certain Occasion of the NZP CSI-RS resource, the Symbol type corresponding to the Symbol where the Occasion is located is taken as the Symbol type corresponding to the Occasion.

[0393] For Periodic NZP CSI-RS, TCI state is configured independently for each NZP CSI-RS resource; for Semi-persistent NZP CSI-RS, when a certain Semi-persistent NZP CSI-RS resource set is activated by SP CSI-RS / CSI-IM Resource Set Activation / Deactivation MAC CE, the corresponding TCI State for each Semi-persistent NZP CSI-RS resource in this Set is indicated respectively. For Serving cell / BWP with SBFD enabled, when a certain Periodic / Semi-persistent NZP CSI-RS resource is configured / indicated with TCI state (it can be understood as that the TCI state for this Periodic NZP CSI-RS resource is configured by higher layer signaling, or the TCI state for this Semi-persistent NZP CSI-RS resource is indicated by MAC CE), either of the following two ways can be adopted:

[0394] CSI-RS TCI state determination way 1: without distinguishing Symbol type, the TCI state used by all Occasions of this NZP CSI-RS resource is configured / indicated uniformly / shared across Symbol types.

[0395] CSI-RS TCI state determination way 1 corresponds to general TCI state configuration way 1, and can be applied to both CSI-RS Occasion configuration way 1 and CSI-RS Occasion configuration way 2.

[0396] For CSI-RS TCI state determination way 1, for Periodic NZP CSI-RS resource, it can be configured as NZP-CSI-RS-Resource->qcl-InfoPeriodicCSI-RS (here, “->” is used to represent a certain field in the previous message or field, for example, the parameter NZP-CSI-RS-Resource->qcl-InfoPeriodicCSI-RS represents the qcl-InfoPeriodicCSI-RS parameter in the NZP-CSI-RS-Resource field, and similar expressions throughout the text follow the interpretation here); for Semi-persistent NZP CSI-RS resource, the indication field in MAC CE can be followed, for example, TCI State IDi. Based on the existing configuration parameters for this Periodic NZP CSI-RS resource, or based on the MAC CE indication field for this Semi-persistent NZP CSI-RS resource, the single TCI state indicated by the indication field can be applied to the Occasion corresponding to the NZP CSI-RS resource and any Symbol type, or in other words, the Occasion corresponding to the Symbol type to which the NZP CSI-RS resource applies the configured TCI state is not limited.

[0397] CSI-RS TCI state determination way 2: configure / indicate a respective TCI state for the NZP CSI-RS resource and the Occasion corresponding to different Symbol types.

[0398] Generally, CSI-RS TCI state determination way 2 corresponds to general TCI state configuration way 2. Alternatively, CSI-RS TCI state determination way 2 can also correspond to general TCI state configuration way 1. CSI-RS TCI state determination way 2 is mainly applied to CSI-RS Occasion configuration way 2, and can also be applied to CSI-RS Occasion configuration way 1.

[0399] When general TCI state configuration way 2 is adopted, it is necessary to ensure by the network side that the TCI state configured / indicated for a certain Symbol type is located in the configuration TCI state set corresponding to the Symbol type.

[0400] For Aperiodic NZP CSI-RS, each Aperiodic NZP CSI-RS resource used for Channel measurement is independently configured with TCI state in the configuration information of each trigger state (e.g., corresponding configuration parameter CSI-AperiodicTriggerState). For Serving cell / BWP with SBFD enabled, when configuring TCI state for a certain Aperiodic NZP CSI-RS resource, either of the following two CSI-RS TCI state configuration methods can be adopted:

[0401] CSI-RS TCI state configuration method 1: without distinguishing Symbol type, configure the TCI state used by this NZP CSI-RS resource.

[0402] CSI-RS TCI state configuration method 1 corresponds to general TCI state configuration method 1.

[0403] For CSI-RS TCI state configuration method 1, the single TCI state configured for this Aperiodic NZP CSI-RS resource by CSI-AssociatedReportConfigInfo->resourcesForChannel->nzp-CSI-RS->qcl-info applies to the single Occasion (which can correspond to any Symbol type) where this NZP CSI-RS resource is triggered.

[0404] CSI-RS TCI state configuration method 2: configure respective TCI states for the Occasions corresponding to different Symbol types for this NZP CSI-RS resource.

[0405] Generally, CSI-RS TCI state configuration method 2 corresponds to general TCI state configuration method 2. Alternatively, CSI-RS TCI state configuration method 2 can also correspond to general TCI state configuration method 1.

[0406] Based on the Symbol type corresponding to the single Occasion that the NZP CSI-RS resource is triggered, the TCI state corresponding to the Symbol type is used. Optionally, only the TCI state corresponding to the Symbol type that the Occasion that the NZP CSI-RS resource is expected to be triggered is configured (when there are multiple Symbol types expected based on possible triggering cases, the corresponding TCI state is configured for each Symbol type respectively).

[0407] When the general TCI state configuration method 2 is adopted, it is necessary to ensure by the network side that the TCI state configured / indicated for a certain Symbol type is located in the configured TCI state set corresponding to the Symbol type.

[0408] In addition, for the case of applying the default QCL assumption for Aperiodic NZP CSI-RS: when the general TCI state configuration method 1 and the CSI-RS TCI state configuration method 1 are adopted, the TCI state of the Aperiodic NZP CSI-RS does not need to be distinguished by Symbol type, at which time the operation defined in the related specification can be followed; when the general TCI state configuration method 2 and the CSI-RS TCI state configuration method 2 are adopted, the Symbol type needs to be distinguished to determine the TCI state applicable to the Aperiodic NZP CSI-RS. At this time, assuming that the Symbol type corresponding to the Aperiodic NZP CSI-RS reception is the first Symbol type, the UE determines that the Aperiodic NZP CSI-RS reception applies the default QCL assumption corresponding to the first Symbol type on the serving cell (the default QCL assumption corresponding to the first Symbol type on the serving cell of the Aperiodic NZP CSI-RS reception is: the QCL assumption used by the target CORESET in the target slot; here, the target slot is the latest slot corresponding to the first Symbol type that the UE needs to monitor one or more CORESETs in the activated BWP of the serving cell of the Aperiodic NZP CSI-RS reception; here, the target CORESET is the CORESET associated with the search space that needs to be monitored, and with the smallest controlResourceSetId, among one or more CORESETs that need to be monitored in the target slot). The specific operation includes:

[0409] If the scheduling offset between the last symbol of the PDCCH carrying the trigger DCI for the Aperiodic NZP CSI-RS reception and the first symbol of the non-periodic CSI-RS resource in the NZP-CSI-RS-ResourceSet corresponding to the Aperiodic NZP CSI-RS reception is less than a target threshold, the following operation is performed: If the network side device does not provide the UE with dl-OrJointTCI-StateList, and at least one CORESET is configured in the BWP where the Aperiodic NZP CSI-RS is received, the UE applies the QCL assumption used by the target CORESET in the target slot when receiving the Aperiodic NZP CSI-RS, the target slot is the slot in which the UE needs to monitor one or more CORESETs in the active BWP of the serving cell where the Aperiodic NZP CSI-RS is received, and the latest slot corresponding to the first symbol type, the target CORESET is the CORESET with the smallest controlResourceSetId among the one or more CORESETs that need to be monitored in the target slot and associated with the search space that needs to be monitored.

[0410] The above-mentioned target threshold can be specified by the protocol or configured by the higher layer signaling. For example,

[0411] When the threshold value beamSwitchTiming reported by the UE is one of the values, and the network side device does not provide the UE with enableBeamSwitchTiming, the target threshold is the threshold value beamSwitchTiming reported by the UE.

[0412] When the UE reports beamSwitchTiming-r16, and the network side device provides the UE with enableBeamSwitchTiming, and the higher layer parameter repetition is configured for the NZP-CSI-RS-ResourceSet and set to 'off', or the higher layer parameter repetition is not configured for the NZP-CSI-RS-ResourceSet, the target threshold is

[0413] ​When the network-side device provides the UE with the enableBeamSwitchTiming, and the high-layer parameter repetition is configured for the NZP-CSI-RS-ResourceSet and is set to 'on', the target threshold is the threshold value beamSwitchTiming-r16 reported by the UE.

[0414] The following takes the first measurement including CSI measurement as an example to describe the related embodiments corresponding to the CSI measurement.

[0415] In some embodiments, the first measurement includes CSI measurement.

[0416] The method further includes:

[0417] In the case where the reporting of the first measurement needs to distinguish the time domain types, the terminal determines a target CSI reference resource corresponding to a target CSI report;

[0418] The terminal performs at least one of the following operations:

[0419] Based on whether at least one target CSI-RS receiving occasion is received, it is determined whether to report the target CSI report;

[0420] In the case where the target CSI report is a periodic or semi-persistent CSI report, based on the latest target CSI-RS receiving occasion, a starting time of CPU occupation is determined;

[0421] Using at least one target CSI-RS receiving occasion, target information contained in the first measurement is determined; the target information includes at least one of layer 1 (L1) reference signal received power (RSRP), L1 signal-to-noise and interference ratio (SINR), and channel quality indicator (CQI).

[0422] Wherein, the target CSI report corresponds to a second time domain type; the target CSI-RS receiving occasion corresponds to the second time domain type, and the target CSI-RS receiving occasion is not later than the target CSI reference resource.

[0423] For ease of understanding, the application embodiments exemplarily describe the related operations of CSI reporting corresponding to CSI measurement.

[0424] When the Symbol type is differentiated for CSI reporting, after determining the CSI reference resource corresponding to a certain CSI report corresponding to a given Symbol type, at least one of the following operations (k) to (m) is included:

[0425] (k) determining whether to ignore the CSI reporting;

[0426] After CSI report configuration or reconfiguration, serving cell activation, BWP change, or SP-CSI activation, the UE will report the CSI report corresponding to the given Symbol type only when it is received corresponding to the given Symbol type, and no later than at least one CSI-RS transmission occasion for channel measurement, and CSI-RS and / or CSI interference measurement (CSI-IM) occasion for interference measurement of the CSI reference resource; otherwise, the CSI report will be discarded.

[0427] When discontinuous reception (DRX) is configured, the UE will report the CSI report corresponding to the given Symbol type only when it is received corresponding to the given Symbol type within the DRX activation time, and no later than at least one CSI-RS transmission occasion for channel measurement, and CSI-RS and / or CSI-IM occasion for interference measurement of the CSI reference resource; otherwise, the CSI report will be discarded.

[0428] (l) determining the CPU occupation;

[0429] When the CSI report is periodic or semi-persistent, the starting time of the CPU occupation is the first symbol of the earliest occasion in the latest CSI-RS / CSI-IM / SSB occasion of the corresponding CSI reference resource, where each CSI-RS / CSI-IM / SSB resource for channel measurement or interference measurement corresponds to the given Symbol type.

[0430] (m) determining the CSI parameters; specifically, at least one of (m1) to (m3) is included:

[0431] (m1) determining the L1-RSRP;

[0432] The UE derives the channel measurement value corresponding to the L1-RSRP value reported in the uplink slot n based on the following occasions:

[0433] The occasion corresponding to the SSB or NZP CSI-RS resource associated with the CSI resource setting, which corresponds to the given Symbol type, and which is no later than the CSI reference resource:

[0434] The most recent single occasion (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to "Configured"); or,

[0435] Any one or more occasions (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to "notConfigured").

[0436] (m2) determining the L1-SINR;

[0437] The UE derives the channel measurement value for computing the L1-SINR reported in uplink slot n based on the following occasions:

[0438] The occasion corresponding to the SSB or NZP CSI-RS resource associated with the CSI resource setting, which corresponds to the given Symbol type, and which is no later than the CSI reference resource:

[0439] The most recent single occasion (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to 'configured'); or,

[0440] Any one or more occasions (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to 'notConfigured').

[0441] The UE derives the interference measurement value for computing the L1-SINR reported in uplink slot n based on the following occasions:

[0442] The occasion corresponding to the CSI-IM or NZP CSI-RS resource for interference measurement or NZP CSI-RS resource for both channel and interference measurement associated with the CSI resource setting, which corresponds to the given Symbol type, and which is no later than the CSI reference resource:

[0443] the most recent single occasion (if timeRestrictionForInterferenceMeasurements in CSI-ReportConfig corresponding to the CSI report is set to 'configured'); or,

[0444] any one or more occasions (if timeRestrictionForInterferenceMeasurements in CSI-ReportConfig corresponding to the CSI report is set to 'notConfigured').

[0445] (m3) determining CQI;

[0446] The UE derives the channel measurement values for computing the CSI values reported in uplink slot n based on the following occasions:

[0447] the occasion corresponding to the given Symbol type and no later than the CSI reference resource, among the occasions corresponding to the NZP CSI-RS resources associated with the CSI resource setting:

[0448] the most recent single occasion (if timeRestrictionForChannelMeasurements in CSI-ReportConfig corresponding to the CSI report is set to "Configured"); or,

[0449] any one or more occasions (if timeRestrictionForChannelMeasurements in CSI-ReportConfig corresponding to the CSI report is set to "notConfigured").

[0450] The UE derives the interference measurement values for computing the CSI values reported in uplink slot n based on the following occasions:

[0451] the occasion corresponding to the given Symbol type and no later than the CSI reference resource, among the occasions corresponding to the NZP CSI-RS resources associated with the CSI resource setting and / or the CSI-IM and / or NZP CSI-RS resources for interference measurement:

[0452] the most recent single occasion (if timeRestrictionForInterferenceMeasurements in CSI-ReportConfig corresponding to the CSI report is set to "Configured"); or,

[0453] Any one or more occasions (if timeRestrictionForInterferenceMeasurements in CSI-ReportConfig corresponding to the CSI report is set as "notConfigured").

[0454] The following takes the first measurement including CLI measurement as an example to illustrate the related embodiments corresponding to the CLI measurement.

[0455] In some embodiments, the first measurement includes CLI measurement;

[0456] In the case of performing the first measurement based on the CLI measurement resource within the time domain unit corresponding to the second time domain type, the transmission parameter corresponding to the CLI measurement resource includes at least one of the following:

[0457] The transmission parameter corresponding to the latest received PDSCH within the time domain unit corresponding to the second time domain type;

[0458] The transmission parameter corresponding to the latest received PDSCH corresponding to the second time domain type;

[0459] The transmission parameter corresponding to the latest monitored CORESET within the time domain unit corresponding to the second time domain type;

[0460] The transmission parameter corresponding to the latest monitored CORESET corresponding to the second time domain type;

[0461] The transmission parameter corresponding to the later one of the latest received PDSCH and the latest monitored CORESET within the time domain unit corresponding to the second time domain type;

[0462] The transmission parameter corresponding to the later one of the latest received PDSCH and the latest monitored CORESET corresponding to the second time domain type.

[0463] Optionally, the transmission parameter corresponding to the CLI measurement resource includes a QCL assumption, and a type of the QCL assumption includes type D.

[0464] For ease of understanding, the embodiments of the present application exemplarily illustrate the CLI measurement.

[0465] Generally, CLI can be assumed to be measured only for SBFD symbol (e.g., inter-UE inter-subband CLI can be measured within SBFD symbol), or, CLI can be measured separately for SBFD symbol and non-SBFD symbol (e.g., adjacent channel or Co-channel CLI can be measured for Dynamic TDD within non-SBFD symbol, etc.).

[0466] When CLI is measured for a given Symbol (assuming its corresponding Symbol type is a given Symbol type, corresponding to the second time-domain type described above), the UE can assume that the CLI measurement resource (including SRS resource, CLI-RSSI resource, etc.) configured within the given Symbol is QCLed (i.e., apply its corresponding QCL assumption / TCI state) with one of the following:

[0467] the latest received PDSCH within the Symbol corresponding to the given Symbol type;

[0468] the latest received PDSCH corresponding to the given Symbol type;

[0469] the latest monitored CORESET within the Symbol corresponding to the given Symbol type;

[0470] the latest monitored CORESET corresponding to the given Symbol type;

[0471] the later one between the latest received PDSCH and the latest monitored CORESET within the Symbol corresponding to the given Symbol type;

[0472] the later one between the latest received PDSCH and the latest monitored CORESET corresponding to the given Symbol type.

[0473] Optionally, the above QCL is of TypeD.

[0474] Optionally, the above assumption is for CLI measurement only for FR2.

[0475] In summary, for the Serving cell / BWP enabled with SBFD, the determination (including configuration, activation, indication, etc.) of the QCL assumption / TCI state corresponding to the downlink Channel / Signal or measurement Channel / Signal, the embodiments of the present application give various feasible determination methods and corresponding UE behaviors, so as to match different SBFD deployment scenarios, and to flexibly and efficiently realize the SBFD operation. It can be seen that the embodiments of the present application can realize the downlink reception or measurement of the terminal in the flexible duplexing scenario.

[0476] FIG. 4 shows a flowchart of a downlink reception and measurement method provided by the embodiments of the present application. As shown in FIG. 4, the downlink reception and measurement method comprises:

[0477] Step 401: The network side device determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, and performs the sending corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or,

[0478] The network side device performs the reception of the measurement report corresponding to the first measurement based on the second time domain type corresponding to the first measurement;

[0479] The first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0480] In the case where the first downlink reception comprises an SSB, the transmission parameter comprises at least one of the following: a transmission power; a related parameter of an SSB beam; a related parameter of an SSB index.

[0481] In the case where the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of the following: a quasi co-location (QCL) assumption; a transmission configuration indication (TCI) state.

[0482] The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0483] Optionally, the first downlink reception comprises at least one of an SSB, a PDCCH, and a CSI-RS.

[0484] The time domain unit where the first downlink reception is located corresponds to one same time domain type; or,

[0485] The time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

[0486] Optionally, the first downlink reception comprises a SSB.

[0487] In a case that the time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types, the network-side device determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, comprising at least one of the following:

[0488] The network-side device does not distinguish the time domain type corresponding to the time domain unit where the first downlink reception is located, and uniformly determines the transmission parameter corresponding to the first downlink reception as the first transmission parameter.

[0489] The network-side device distinguishes the time domain type corresponding to the time domain unit where the first downlink reception is located, and determines the transmission parameter corresponding to the first downlink reception in the time domain unit of different time domain types based on the mapping relationship between the time domain type and the transmission parameter.

[0490] Optionally, the first downlink reception comprises at least one of a PDSCH, a PDCCH and a CSI-RS.

[0491] The method further comprises:

[0492] The network-side device sends first information to the terminal, and the first information is used for configuring at least one set, each set in the at least one set comprising at least one transmission parameter.

[0493] The network-side device determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, comprising:

[0494] The network-side device determines the transmission parameter corresponding to the first downlink reception from the at least one set based on the first time domain type corresponding to the first downlink reception.

[0495] Optionally, the at least one set comprises at least one of the following:

[0496] A first set, any one transmission parameter in the first set can be used for any time domain type;

[0497] At least one second set, the time domain type corresponding to each transmission parameter in the at least one second set is determined by the configuration information of the transmission parameter;

[0498] A third set, the time domain type corresponding to each transmission parameter in the third set is determined by the position of the transmission parameter in the third set;

[0499] At least one fourth set, all transmission parameters in each fourth set correspond to the same time domain type, and different fourth sets correspond to different time domain types.

[0500] Optionally, the configuration information of the transmission parameter comprises at least one of the following:

[0501] an identity of the transmission parameter, the time domain type corresponding to each transmission parameter in the at least one second set being determined by a value of the identity of the transmission parameter;

[0502] a first indication of the transmission parameter, the first indication being used to indicate the time domain type, and the time domain type corresponding to each transmission parameter in the at least one second set being the time domain type indicated by the first indication of the transmission parameter.

[0503] Optionally, the third set comprises one or more subsets, and each subset of the third set satisfies at least one of the following:

[0504] each subset of the third set is ordered according to a predetermined order, and the predetermined order represents an order of the time domain types;

[0505] a number of transmission parameters included in each subset of the third set is allocated in a predefined manner, or is directly configured or indicated.

[0506] Optionally, the first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET);

[0507] a time domain unit where a reception occasion of the first CORESET corresponds to a same time domain type; or

[0508] a time domain unit where the reception occasion of the first CORESET corresponds to multiple time domain types or all time domain types.

[0509] Optionally, in a case where the time domain unit where the reception occasion of the first CORESET corresponds to the same time domain type, the time domain type corresponding to the time domain unit where the reception occasion of the first CORESET is determined by at least one of the following:

[0510] configuration information of the first CORESET;

[0511] configuration information of each search space in a search space associated with the first CORESET;

[0512] a protocol;

[0513] a higher layer parameter.

[0514] Optionally, the configuration information of the first CORESET comprises at least one of the following:

[0515] an identifier of the first CORESET, a value of the identifier being used to determine a time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located;

[0516] a second indication of the first CORESET, the second indication being used to indicate a time domain type, the time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located being the time domain type indicated by the second indication.

[0517] Optionally, the configuration information of each search space comprises at least one of the following:

[0518] an identifier of each search space, a value of the identifier being used to determine a time domain type corresponding to a time domain unit in which a receiving occasion of each search space is located;

[0519] a third indication of each search space, the third indication being used to indicate a time domain type, the time domain type corresponding to a time domain unit in which a receiving occasion of each search space is located being the time domain type indicated by the third indication of each search space.

[0520] Optionally, the first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET);

[0521] The method further comprises:

[0522] The network-side device sends, to the terminal, second information, the second information being used to indicate at least one of the following:

[0523] transmission parameters corresponding to all receiving occasions of the first CORESET;

[0524] of the M time domain types corresponding to the first CORESET, a transmission parameter corresponding to each receiving occasion of each time domain type, M being an integer greater than or equal to 1.

[0525] Optionally, of the M time domain types corresponding to the first CORESET, a transmission parameter corresponding to each receiving occasion of each time domain type is indicated by a same MAC CE; or,

[0526] of the M time domain types corresponding to the first CORESET, a transmission parameter corresponding to each receiving occasion of each time domain type is indicated by a different MAC CE.

[0527] Optionally, in a case where a transmission parameter corresponding to each receiving occasion of each time domain type of the M time domain types corresponding to the first CORESET is indicated by a same MAC CE, the MAC CE comprises at least one of the following:

[0528] M first indication fields, the M first indication fields being used for respectively indicating transmission parameters corresponding to a receiving occasion of each of the M time domain types;

[0529] a second indication field, the second indication field being used for jointly indicating transmission parameters corresponding to a receiving occasion of each of the M time domain types.

[0530] Optionally, in a case that the transmission parameters corresponding to the receiving occasion of each of the M time domain types corresponding to the first CORESET are indicated by different MAC CEs, the MAC CEs comprise at least one of the following:

[0531] a third indication field, used for indicating a time domain type corresponding to the MAC CE;

[0532] a fourth indication field, used for indicating the transmission parameters corresponding to the corresponding time domain type;

[0533] a fifth indication field, used for indicating an activation state or a deactivation state of the transmission parameters corresponding to the corresponding time domain type.

[0534] Optionally, the first downlink reception comprises a PDSCH.

[0535] The method further comprises:

[0536] The network-side device sends third information to the terminal, the third information being used for indicating at least one of the following:

[0537] activation transmission parameters corresponding to all time domain units corresponding to the first downlink reception;

[0538] activation transmission parameters corresponding to a time domain unit corresponding to each of the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1.

[0539] Optionally, the activation transmission parameters corresponding to the time domain unit corresponding to each of the N time domain types corresponding to the first downlink reception are indicated by a same MAC CE; or,

[0540] the activation transmission parameters corresponding to the time domain unit corresponding to each of the N time domain types corresponding to the first downlink reception are indicated by different MAC CEs.

[0541] Optionally, in a case that the activation transmission parameters corresponding to the time domain unit corresponding to each of the N time domain types corresponding to the first downlink reception are indicated by a same MAC CE, the MAC CE comprises at least one of the following:

[0542] N sixth indication fields, respectively, indicating the activated transmission parameters corresponding to each of the N time domain types;

[0543] a seventh indication field, jointly indicating the activated transmission parameters corresponding to each of the N time domain types.

[0544] Optionally, in the case that each of the N time domain types corresponding to the first downlink reception corresponds to the activated transmission parameters corresponding to the time domain unit corresponding to each of the N time domain types, the MAC CE comprises at least one of the following:

[0545] an eighth indication field, indicating the time domain type corresponding to the MAC CE;

[0546] a ninth indication field, indicating the activation state or deactivation state of the transmission parameters corresponding to the corresponding time domain type.

[0547] Optionally, the network side device determines the transmission parameters corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, comprising at least one of the following:

[0548] In the case that the first downlink reception needs to apply the transmission parameters indicated by the third information, the network side device selects the transmission parameters with the same time domain type as the time domain type corresponding to the first downlink reception from the transmission parameters indicated by the third information as the transmission parameters corresponding to the first downlink reception;

[0549] In the case that the first downlink reception needs to apply the transmission parameters of the PDCCH, and the time domain type corresponding to the first downlink reception is the same as the time domain type corresponding to the CORESET of the PDCCH, the network side device determines the transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameters corresponding to the first downlink reception;

[0550] In the case that the first downlink reception needs to apply the transmission parameters of the PDCCH, and the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, the network side device determines the default transmission parameters or the predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;

[0551] In the case that the first downlink reception needs to apply the transmission parameters of the PDCCH, and at least one time domain type corresponding to the CORESET of the PDCCH does not contain the time domain type corresponding to the first downlink reception, the network side device determines the default transmission parameters or the predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;

[0552] In a case where the first downlink reception needs to apply a transmission parameter of a PDCCH, and at least one time domain type corresponding to a CORESET of the PDCCH includes a time domain type corresponding to the first downlink reception, the network-side device selects, from transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter of a same time domain type as the time domain type corresponding to the first downlink reception as a transmission parameter corresponding to the first downlink reception.

[0553] In a case where the first downlink reception needs to apply a default transmission parameter, the network-side device determines a default transmission parameter corresponding to the first time domain type as a transmission parameter corresponding to the first downlink reception.

[0554] In a case where the first downlink reception needs to apply an initial transmission parameter, the network-side device determines an initial transmission parameter corresponding to the first time domain type as a transmission parameter corresponding to the first downlink reception.

[0555] Optionally, the first downlink reception includes a CSI-RS corresponding to a first non-zero power (NZP) CSI-RS resource.

[0556] In a case where the first NZP CSI-RS resource is a periodic or semi-persistent resource, time domain units in which reception occasions corresponding to the first NZP CSI-RS resource are located correspond to a same time domain type, or time domain units in which the reception occasions corresponding to the first NZP CSI-RS resource are located can correspond to multiple time domain types or all time domain types.

[0557] Optionally, the method further includes:

[0558] The network-side device sends fourth information to a terminal, and the fourth information is used to indicate at least one of the following:

[0559] a transmission parameter corresponding to all reception occasions corresponding to the first NZP CSI-RS resource;

[0560] of the S time domain types corresponding to the first NZP CSI-RS resource, a transmission parameter corresponding to a reception occasion corresponding to each time domain type, S being an integer greater than or equal to 1.

[0561] Optionally, the network-side device determines a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, including:

[0562] In a case where the first NZP CSI-RS resource is a non-periodic resource and a CSI-RS corresponding to the first NZP CSI-RS resource needs to apply a default transmission parameter, the network side device determines a default transmission parameter corresponding to the first time domain type as a transmission parameter corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.

[0563] The related description of the embodiments of the present application can refer to the related description of the method embodiments of FIG. 3, and the same technical effects can be achieved. To avoid repetition, this will not be described here.

[0564] The execution subject of the downlink receiving and measuring method provided by the embodiments of the present application can be a downlink receiving and measuring device. In the embodiments of the present application, the downlink receiving and measuring device is taken as an example to illustrate the downlink receiving and measuring device provided by the embodiments of the present application.

[0565] Referring to FIG. 5, the embodiments of the present application further provide a downlink receiving and measuring device. As shown in FIG. 5, the downlink receiving and measuring device 500 includes:

[0566] The first processing unit 501 is configured to: determine a transmission parameter corresponding to the first downlink receiving based on a first time domain type corresponding to the first downlink receiving, and perform receiving corresponding to the first downlink receiving according to the transmission parameter corresponding to the first downlink receiving; or,

[0567] perform at least one of the first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement;

[0568] The first downlink receiving includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0569] In a case where the first downlink receiving includes an SSB, the transmission parameter includes at least one of: a transmission power; a related parameter of an SSB beam; and a related parameter of an SSB index.

[0570] In a case where the first downlink receiving includes at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter includes at least one of: a quasi co-location (QCL) assumption; and a transmission configuration indication (TCI) state.

[0571] The first measurement includes at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0572] Optionally, the first downlink receiving includes at least one of an SSB, a PDCCH, and a CSI-RS.

[0573] The time domain unit where the first downlink reception is located corresponds to a same time domain type; or

[0574] The time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

[0575] Optionally, the first downlink reception includes an SSB.

[0576] In a case where the time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types, the first processing unit is specifically configured to at least one of the following:

[0577] Without distinguishing the time domain types to which the time domain unit where the first downlink reception is located corresponds, the transmission parameter corresponding to the first downlink reception is uniformly determined as a first transmission parameter.

[0578] The time domain types to which the time domain unit where the first downlink reception is located corresponds are distinguished, and based on a mapping relationship between time domain types and transmission parameters, the transmission parameters corresponding to the first downlink reception in the time domain units of different time domain types are determined.

[0579] Optionally, the first downlink reception includes at least one of a PDSCH, a PDCCH and a CSI-RS.

[0580] The apparatus further includes:

[0581] A first receiving unit, configured to receive first information from a network side device, the first information being used for configuring at least one set, each set in the at least one set including at least one transmission parameter.

[0582] The first processing unit is specifically configured to:

[0583] Based on a first time domain type corresponding to the first downlink reception, determine the transmission parameter corresponding to the first downlink reception from the at least one set.

[0584] Optionally, the at least one set includes at least one of the following:

[0585] A first set, any one transmission parameter in the first set being applicable to any time domain type.

[0586] At least one second set, each transmission parameter in the at least one second set corresponding to a time domain type determined by configuration information of the transmission parameter.

[0587] A third set, each transmission parameter in the third set corresponding to a time domain type determined by a position of the transmission parameter in the third set.

[0588] At least one fourth set, all transmission parameters in each of the fourth set correspond to a same time domain type, different fourth sets correspond to different time domain types.

[0589] Optionally, the configuration information of the transmission parameter comprises at least one of:

[0590] An identity of the transmission parameter, the time domain type corresponding to each transmission parameter in the at least one second set is determined by a value of the identity of the transmission parameter;

[0591] A first indication of the transmission parameter, the first indication is used to indicate a time domain type, and the time domain type corresponding to each transmission parameter in the at least one second set is the time domain type indicated by the first indication of the transmission parameter.

[0592] Optionally, the third set comprises one or more subsets, and each subset of the third set satisfies at least one of the following:

[0593] Each subset of the third set is sorted according to a predetermined order, and the predetermined order represents an order of the time domain types;

[0594] The number of transmission parameters included in each subset of the third set is allocated in a predefined manner or directly configured or indicated.

[0595] Optionally, the first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET);

[0596] The time domain unit where the reception occasion of the first CORESET is located corresponds to a same time domain type; or

[0597] The time domain unit where the reception occasion of the first CORESET is located can correspond to multiple time domain types or all time domain types.

[0598] Optionally, in the case where the time domain unit where the reception occasion of the first CORESET is located corresponds to a same time domain type, the time domain type corresponding to the time domain unit where the reception occasion of the first CORESET is located is determined by at least one of the following:

[0599] Configuration information of the first CORESET;

[0600] Configuration information of each search space in a search space associated with the first CORESET;

[0601] A protocol;

[0602] A high-layer parameter.

[0603] Optionally, the configuration information of the first CORESET comprises at least one of the following:

[0604] an identity of the first CORESET, a value of the identity of the first CORESET being used to determine a time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located;

[0605] a second indication of the first CORESET, the second indication being used to indicate a time domain type, a time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located being the time domain type indicated by the second indication.

[0606] Optionally, the configuration information of the respective search spaces comprises at least one of:

[0607] an identity of the respective search spaces, a value of the identity of the respective search spaces being used to respectively determine a time domain type corresponding to a time domain unit in which a receiving occasion of the respective search spaces is located;

[0608] a third indication of the respective search spaces, the third indication being used to indicate a time domain type, a time domain type corresponding to a time domain unit in which a receiving occasion of the respective search spaces is located being the time domain type indicated by the third indication of the respective search spaces.

[0609] Optionally, the first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET);

[0610] The apparatus further comprises:

[0611] a second receiving unit, configured to receive second information from a network side device, the second information being used to indicate at least one of:

[0612] transmission parameters corresponding to all receiving occasions of the first CORESET;

[0613] of the M time domain types corresponding to the first CORESET, a respective receiving occasion of each time domain type corresponding to transmission parameters corresponding to the respective receiving occasion of the each time domain type, M being an integer greater than or equal to 1.

[0614] Optionally, of the M time domain types corresponding to the first CORESET, a respective receiving occasion of each time domain type corresponding to transmission parameters corresponding to the respective receiving occasion of the each time domain type is indicated by a same MAC CE; or,

[0615] of the M time domain types corresponding to the first CORESET, a respective receiving occasion of each time domain type corresponding to transmission parameters corresponding to the respective receiving occasion of the each time domain type is indicated by different MAC CEs.

[0616] Optionally, in a case that the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by one same MAC CE, the MAC CE comprises at least one of the following:

[0617] M first indication fields, the M first indication fields are used for respectively indicating the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types;

[0618] a second indication field, the second indication field is used for jointly indicating the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types.

[0619] Optionally, in a case that the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by different MAC CEs, the MAC CE comprises at least one of the following:

[0620] a third indication field, used for indicating the time domain type corresponding to the MAC CE;

[0621] a fourth indication field, used for indicating the transmission parameter corresponding to the corresponding time domain type;

[0622] a fifth indication field, used for indicating an activation state or a deactivation state of the transmission parameter corresponding to the corresponding time domain type.

[0623] Optionally, the first downlink reception comprises a PDSCH.

[0624] The apparatus further comprises:

[0625] a third receiving unit, configured to receive third information from a network side device, the third information being used for indicating at least one of the following:

[0626] the activation transmission parameters corresponding to all time domain units corresponding to the first downlink reception;

[0627] the activation transmission parameters corresponding to the time domain units corresponding to each of the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1.

[0628] Optionally, the activation transmission parameters corresponding to the time domain units corresponding to each of the N time domain types corresponding to the first downlink reception are indicated by one same MAC CE; or,

[0629] the activation transmission parameters corresponding to the time domain units corresponding to each of the N time domain types corresponding to the first downlink reception are indicated by different MAC CEs.

[0630] Optionally, in a case that the N time domain types corresponding to the first downlink reception are indicated by one same MAC CE, and each time domain unit corresponding to each time domain type corresponds to an activated transmission parameter, the MAC CE comprises at least one of the following:

[0631] N sixth indication fields, the N sixth indication fields are used for respectively indicating an activated transmission parameter corresponding to each time domain type in the N time domain types;

[0632] a seventh indication field, the seventh indication field is used for jointly indicating the activated transmission parameter corresponding to each time domain type in the N time domain types.

[0633] Optionally, in a case that the N time domain types corresponding to the first downlink reception are indicated by different MAC CEs, and each time domain unit corresponding to each time domain type corresponds to an activated transmission parameter, the MAC CE comprises at least one of the following:

[0634] an eighth indication field, used for indicating a time domain type corresponding to the MAC CE;

[0635] a ninth indication field, used for indicating an activated state or a deactivated state of a transmission parameter corresponding to a corresponding time domain type.

[0636] Optionally, the first processing unit is specifically used for at least one of the following:

[0637] in a case that the first downlink reception needs to apply the transmission parameter indicated by the third information, selecting, from the transmission parameter indicated by the third information, a transmission parameter with a same time domain type as the time domain type corresponding to the first downlink reception, as the transmission parameter corresponding to the first downlink reception;

[0638] in a case that the first downlink reception needs to apply a transmission parameter of a PDCCH, and a time domain type corresponding to the first downlink reception is same as a time domain type corresponding to a CORESET of the PDCCH, determining a transmission parameter corresponding to the CORESET of the PDCCH as the transmission parameter corresponding to the first downlink reception;

[0639] in a case that the first downlink reception needs to apply a transmission parameter of a PDCCH, and a time domain type corresponding to the first downlink reception is different from a time domain type corresponding to a CORESET of the PDCCH, determining a default transmission parameter or a predefined transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception;

[0640] In a case that the first downlink reception needs to apply transmission parameters of a PDCCH, and at least one time domain type corresponding to a CORESET of the PDCCH does not contain a time domain type corresponding to the first downlink reception, a default transmission parameter corresponding to the first time domain type or a predefined transmission parameter is determined as the transmission parameter corresponding to the first downlink reception.

[0641] In a case that the first downlink reception needs to apply transmission parameters of a PDCCH, and at least one time domain type corresponding to a CORESET of the PDCCH contains a time domain type corresponding to the first downlink reception, a transmission parameter with a same time domain type as the time domain type corresponding to the first downlink reception is selected from transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameter corresponding to the first downlink reception.

[0642] In a case that the first downlink reception needs to apply a default transmission parameter, a default transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0643] In a case that the first downlink reception needs to apply an initial transmission parameter, an initial transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0644] Optionally, the first downlink reception comprises a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource.

[0645] In a case that the first NZP CSI-RS resource is a periodic or semi-persistent resource, a time domain unit where a reception occasion corresponding to the first NZP CSI-RS resource is located corresponds to a same time domain type, or the time domain unit where the reception occasion corresponding to the first NZP CSI-RS resource is located can correspond to multiple time domain types or all time domain types.

[0646] Optionally, the first downlink reception comprises a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource.

[0647] The apparatus further comprises:

[0648] A fourth receiving unit, configured to receive fourth information from a network side device, the fourth information being used for indicating at least one of the following:

[0649] Transmission parameters corresponding to all reception occasions corresponding to the first NZP CSI-RS resource;

[0650] Transmission parameters corresponding to reception occasions corresponding to each of S time domain types corresponding to the first NZP CSI-RS resource, S being an integer greater than or equal to 1.

[0651] Optionally, the first processing unit is specifically used for:

[0652] In a case where the first NZP CSI-RS resource is aperiodic resource and a CSI-RS corresponding to the first NZP CSI-RS resource needs to apply a default transmission parameter, the default transmission parameter corresponding to the first time domain type is determined as a transmission parameter corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.

[0653] Optionally, the first measurement includes a CSI measurement;

[0654] The apparatus further includes:

[0655] A second processing unit, configured to determine a target CSI reference resource corresponding to a target CSI report in a case where reporting of the first measurement needs to be distinguished by time domain types;

[0656] A third processing unit, configured to perform at least one of the following operations:

[0657] Determine whether to report the target CSI report based on whether at least one target CSI-RS receiving occasion is received;

[0658] In a case where the target CSI report is a periodic or semi-persistent CSI report, determine a starting time point of CPU occupation based on the latest target CSI-RS receiving occasion;

[0659] Determine target information contained in the first measurement using at least one target CSI-RS receiving occasion; the target information includes at least one of L1-RSRP, L1-SINR and CQI;

[0660] The target CSI report corresponds to a second time domain type; the target CSI-RS receiving occasion corresponds to the second time domain type, and the target CSI-RS receiving occasion is not later than the target CSI reference resource.

[0661] Optionally, the first measurement includes a CLI measurement;

[0662] In a case where the first measurement is performed based on a CLI measurement resource within a time domain unit corresponding to the second time domain type, a transmission parameter corresponding to the CLI measurement resource includes at least one of the following:

[0663] A transmission parameter corresponding to a latest received PDSCH within the time domain unit corresponding to the second time domain type;

[0664] a transmission parameter corresponding to a latest received PDSCH corresponding to the second time domain type;

[0665] a transmission parameter corresponding to a latest monitored CORESET corresponding to the second time domain type;

[0666] a transmission parameter corresponding to a latest monitored CORESET corresponding to the second time domain type;

[0667] a transmission parameter corresponding to a later one of a latest received PDSCH and a latest monitored CORESET within a time domain unit corresponding to the second time domain type;

[0668] a transmission parameter corresponding to a later one of a latest received PDSCH and a latest monitored CORESET corresponding to the second time domain type.

[0669] The downlink receiving and measuring apparatus in the embodiments of the present application can be an electronic device, for example, an electronic device with an operating system, or a component in an electronic device, for example, an integrated circuit or a chip. The electronic device can be a terminal or other device than a terminal. Exemplarily, the terminal can include, but is not limited to, the types of the terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which are not limited in the embodiments of the present application.

[0670] The downlink receiving and measuring apparatus provided in the embodiments of the present application can implement each process implemented by the method embodiment of FIG. 3 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0671] Referring to FIG. 6, the embodiments of the present application further provide a downlink receiving and measuring apparatus. As shown in FIG. 6, the downlink receiving and measuring apparatus 600 includes:

[0672] The processing unit 601 is configured to: determine a transmission parameter corresponding to the first downlink receiving based on a first time domain type corresponding to the first downlink receiving, and perform the first downlink receiving corresponding to the transmission parameter corresponding to the first downlink receiving; or

[0673] perform receiving of a measurement report corresponding to the first measurement based on a second time domain type corresponding to the first measurement;

[0674] The first downlink receiving includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0675] In a case where the first downlink reception comprises an SSB, the transmission parameter comprises at least one of: a transmit power; a related parameter of an SSB beam; a related parameter of an SSB index.

[0676] In a case where the first downlink reception comprises at least one of a PDCCH, a PDSCH and a CSI-RS, the transmission parameter comprises at least one of: a quasi co-location, QCL, assumption; a transmission configuration indication, TCI, state.

[0677] The first measurement comprises at least one of a channel state information, CSI, measurement and a cross-link interference, CLI, measurement.

[0678] Optionally, the first downlink reception comprises at least one of an SSB, a PDCCH and a CSI-RS.

[0679] The time domain unit where the first downlink reception is located corresponds to one same time domain type; or

[0680] The time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

[0681] Optionally, the first downlink reception comprises an SSB.

[0682] In a case where the time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types, the processing unit is specifically configured to perform at least one of:

[0683] Without distinguishing the time domain type to which the time domain unit where the first downlink reception is located corresponds, the transmission parameter corresponding to the first downlink reception is uniformly determined as a first transmission parameter;

[0684] Distinguishing the time domain type to which the time domain unit where the first downlink reception is located corresponds, based on a mapping relationship between a time domain type and a transmission parameter, determining the transmission parameter corresponding to the first downlink reception in the time domain unit of different time domain types.

[0685] Optionally, the first downlink reception comprises at least one of a PDSCH, a PDCCH and a CSI-RS.

[0686] The apparatus further comprises:

[0687] A first sending unit, configured to send first information to a terminal, the first information being used for configuring at least one set, each set in the at least one set comprising at least one transmission parameter.

[0688] The processing unit is specifically configured to:

[0689] Based on a first time domain type corresponding to the first downlink reception, determining the transmission parameter corresponding to the first downlink reception from the at least one set.

[0690] Optionally, the at least one set comprises at least one of:

[0691] a first set, any one of the transmission parameters in the first set is applicable to any time domain type;

[0692] at least one second set, a time domain type corresponding to each of the transmission parameters in the at least one second set is determined by configuration information of the transmission parameter;

[0693] a third set, a time domain type corresponding to each of the transmission parameters in the third set is determined by a position of the transmission parameter in the third set;

[0694] at least one fourth set, all the transmission parameters in each of the fourth sets correspond to a same time domain type, and different fourth sets correspond to different time domain types.

[0695] Optionally, the configuration information of the transmission parameter comprises at least one of:

[0696] an identifier of the transmission parameter, a time domain type corresponding to each of the transmission parameters in the at least one second set is determined by a value of the identifier of the transmission parameter;

[0697] a first indication of the transmission parameter, the first indication is used to indicate a time domain type, and a time domain type corresponding to each of the transmission parameters in the at least one second set is a time domain type indicated by the first indication of the transmission parameter.

[0698] Optionally, the third set comprises one or more subsets, and each subset of the third set satisfies at least one of:

[0699] each subset of the third set is sorted according to a predetermined order, and the predetermined order represents an order of the time domain types;

[0700] a number of the transmission parameters included in each subset of the third set is allocated in a predefined manner, or is directly configured or indicated.

[0701] Optionally, the first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET);

[0702] a time domain unit in which a reception occasion of the first CORESET corresponds to a same time domain type; or

[0703] a time domain unit in which the reception occasion of the first CORESET can correspond to multiple time domain types or all time domain types.

[0704] Optionally, in a case where the time domain unit where the reception occasion of the first CORESET is located corresponds to a same time domain type, the time domain type to which the time domain unit where the reception occasion of the first CORESET is located corresponds is determined by at least one of the following:

[0705] configuration information of the first CORESET;

[0706] configuration information of each search space in a search space associated with the first CORESET;

[0707] a protocol specification;

[0708] a higher layer parameter.

[0709] Optionally, the configuration information of the first CORESET includes at least one of the following:

[0710] an identifier of the first CORESET, a value of the identifier of the first CORESET being used to determine the time domain type to which the time domain unit where the reception occasion of the first CORESET is located corresponds;

[0711] a second indication of the first CORESET, the second indication being used to indicate a time domain type, the time domain type to which the time domain unit where the reception occasion of the first CORESET is located corresponds being the time domain type indicated by the second indication.

[0712] Optionally, the configuration information of each search space includes at least one of the following:

[0713] an identifier of each search space, a value of the identifier of each search space being used to determine the time domain type to which the time domain unit where the reception occasion of each search space is located corresponds;

[0714] a third indication of each search space, the third indication being used to indicate a time domain type, the time domain type to which the time domain unit where the reception occasion of each search space is located corresponds being the time domain type indicated by the third indication of each search space.

[0715] Optionally, the first downlink reception includes a PDCCH corresponding to a first control resource set (CORESET);

[0716] The apparatus further includes:

[0717] a second sending unit, configured to send second information to a terminal, the second information being used to indicate at least one of the following:

[0718] transmission parameters corresponding to all reception occasions of the first CORESET;

[0719] The transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET, M being an integer greater than or equal to 1.

[0720] Optionally, the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by the same MAC CE.

[0721] The transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by different MAC CEs.

[0722] Optionally, in the case where the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by the same MAC CE, the MAC CE comprises at least one of the following:

[0723] M first indication fields, the M first indication fields being used to respectively indicate the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types;

[0724] A second indication field, the second indication field being used to jointly indicate the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types.

[0725] Optionally, in the case where the transmission parameters corresponding to the reception occasions corresponding to each of the M time domain types corresponding to the first CORESET are indicated by different MAC CEs, the MAC CE comprises at least one of the following:

[0726] A third indication field, used to indicate the time domain type corresponding to the MAC CE;

[0727] A fourth indication field, used to indicate the transmission parameter corresponding to the corresponding time domain type;

[0728] A fifth indication field, used to indicate an activation state or a deactivation state of the transmission parameter corresponding to the corresponding time domain type.

[0729] Optionally, the first downlink reception comprises a PDSCH.

[0730] The apparatus further comprises:

[0731] A third sending unit, configured to send third information to the terminal, the third information being used to indicate at least one of the following:

[0732] The activated transmission parameters corresponding to all time domain units corresponding to the first downlink reception;

[0733] Each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception respectively corresponds to an activated transmission parameter.

[0734] Optionally, each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception respectively corresponds to an activated transmission parameter, which is indicated by a same MAC CE.

[0735] Each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception respectively corresponds to an activated transmission parameter, which is indicated by different MAC CEs.

[0736] Optionally, in the case that each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception respectively corresponds to an activated transmission parameter, which is indicated by a same MAC CE, the MAC CE comprises at least one of the following:

[0737] N sixth indication fields, the N sixth indication fields are used to respectively indicate the activated transmission parameter corresponding to each time domain type in the N time domain types;

[0738] A seventh indication field, the seventh indication field is used to jointly indicate the activated transmission parameter corresponding to each time domain type in the N time domain types.

[0739] Optionally, in the case that each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception respectively corresponds to an activated transmission parameter, which is indicated by different MAC CEs, the MAC CE comprises at least one of the following:

[0740] An eighth indication field, used to indicate the time domain type corresponding to the MAC CE;

[0741] A ninth indication field, used to indicate the activated state or the deactivated state of the transmission parameter corresponding to the corresponding time domain type.

[0742] Optionally, the processing unit is specifically used for at least one of the following:

[0743] In the case that the first downlink reception needs to apply the transmission parameter indicated by the third information, from the transmission parameter indicated by the third information, a transmission parameter with the same time domain type as the time domain type corresponding to the first downlink reception is selected as the transmission parameter corresponding to the first downlink reception;

[0744] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is same as the time domain type corresponding to the CORESET of the PDCCH, the transmission parameter corresponding to the CORESET of the PDCCH is determined as the transmission parameter corresponding to the first downlink reception.

[0745] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, the default transmission parameter or the predefined transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0746] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and at least one time domain type corresponding to the CORESET of the PDCCH does not contain the time domain type corresponding to the first downlink reception, the default transmission parameter or the predefined transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0747] In a case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and at least one time domain type corresponding to the CORESET of the PDCCH contains the time domain type corresponding to the first downlink reception, from the transmission parameters corresponding to the CORESET of the PDCCH, the transmission parameter with the same time domain type as the time domain type corresponding to the first downlink reception is selected as the transmission parameter corresponding to the first downlink reception.

[0748] In a case that the first downlink reception needs to apply the default transmission parameter, the default transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0749] In a case that the first downlink reception needs to apply the initial transmission parameter, the initial transmission parameter corresponding to the first time domain type is determined as the transmission parameter corresponding to the first downlink reception.

[0750] Optionally, the first downlink reception comprises a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource.

[0751] In a case that the first NZP CSI-RS resource is a periodic or semi-persistent resource, the time domain units where the reception occasions corresponding to the first NZP CSI-RS resource are located correspond to a same time domain type, or the time domain units where the reception occasions corresponding to the first NZP CSI-RS resource are located can correspond to multiple time domain types or all time domain types.

[0752] Optionally, the apparatus further comprises:

[0753] a fourth sending unit, configured to send fourth information to the terminal, the fourth information being used for indicating at least one of the following:

[0754] the transmission parameters corresponding to the receiving occasions corresponding to each of the S time domain types corresponding to the first NZP CSI-RS resource, S being an integer greater than or equal to 1.

[0755] the transmission parameters corresponding to the receiving occasions corresponding to each of the S time domain types corresponding to the first NZP CSI-RS resource, S being an integer greater than or equal to 1.

[0756] Optionally, the processing unit is specifically configured to:

[0757] in a case where the first NZP CSI-RS resource is a non-periodic resource and the CSI-RS corresponding to the first NZP CSI-RS resource needs to apply a default transmission parameter, determining the default transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.

[0758] The downlink receiving and measuring apparatus in the embodiments of the present application can be an electronic device, for example, an electronic device with an operating system, or a component in an electronic device, for example, an integrated circuit or a chip. The electronic device can be a terminal or other device than a terminal. Exemplarily, the terminal can include, but is not limited to, the types of the terminal 11 listed above, and the other device can be a server, a Network Attached Storage (NAS) or the like, which is not limited in the embodiments of the present application.

[0759] The downlink receiving and measuring apparatus provided in the embodiments of the present application can realize each process achieved by the method embodiment of FIG. 4 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0760] As shown in FIG. 7, the embodiments of the present application further provide a communication device 700, which includes a processor 701 and a memory 702, the memory 702 storing programs or instructions executable on the processor 701. For example, when the communication device 700 is a terminal, the programs or instructions are executed by the processor 701 to realize each step of the terminal-side method embodiments described above and achieve the same technical effects. When the communication device 700 is a network-side device, the programs or instructions are executed by the processor 701 to realize each step of the network-side device-side method embodiments described above and achieve the same technical effects. To avoid repetition, details are not described herein.

[0761] The embodiment of the present application further provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used to run programs or instructions to realize the steps in the method embodiment shown in Fig. 3. The terminal embodiment corresponds to the terminal-side method embodiment described above, and each implementation process and implementation manner of the method embodiment described above can be applied to the terminal embodiment and the same technical effects can be achieved. Specifically, Fig. 8 is a schematic diagram of the hardware structure of a terminal for implementing the embodiment of the present application.

[0762] The terminal 800 comprises, but is not limited to, at least part of components such as 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 a processor 810.

[0763] Those skilled in the art can understand that the terminal 800 can further comprise a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected with the processor 810 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. The terminal structure shown in Fig. 8 does not constitute a limitation on the terminal, and the terminal can comprise more or fewer components than those shown, or some components can be combined, or different components can be arranged, which will not be described here.

[0764] It should be understood that in the embodiment of the present application, the input unit 804 can comprise a graphics processor (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes image data of a still picture or a 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 can comprise a display panel 8061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 807 comprises at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 can comprise a touch detection device and a touch controller. The other input devices 8072 can comprise, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, etc., which will not be described here.

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

[0766] The memory 809 can be used to store software programs or instructions and various data. The memory 809 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 809 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 809 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0767] The processor 810 can include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 810.

[0768] The processor 810 is configured to:

[0769] determine a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform a reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or

[0770] perform at least one of the first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement.

[0771] The first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS).

[0772] In a case where the first downlink reception comprises the SSB, the transmission parameter comprises at least one of: a transmit power; a related parameter of an SSB beam; and a related parameter of an SSB index.

[0773] In a case where the first downlink reception comprises at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter comprises at least one of: a quasi co-location (QCL) assumption; and a transmission configuration indication (TCI) state.

[0774] The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

[0775] In the embodiments of the present application, when a time domain unit corresponds to or distinguishes multiple time domain types, the terminal can determine the transmission parameter corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, so that the terminal can realize flexible and reliable downlink reception according to the determined transmission parameter. The terminal can also perform at least one of measurement and reporting based on the time domain type corresponding to the measurement, so that the terminal can realize flexible and accurate and effective measurement. It can be seen that the embodiments of the present application can realize downlink reception or measurement of the terminal in a flexible duplexing scenario.

[0776] It can be understood that the implementation processes of each implementation mode mentioned in the embodiments can refer to the related descriptions of the downlink reception and measurement method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here.

[0777] The embodiments of the present application also provide a network side device comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to realize the steps of the method embodiments shown in FIG. 4. The network side device embodiments correspond to the network side device method embodiments described above, and each implementation process and implementation mode of the above method embodiments can be applied to the network side device embodiments, and can achieve the same technical effects.

[0778] Specifically, the embodiment of the present application also provides a network side device. As shown in FIG. 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. The antenna 91 is connected with the radio frequency device 92. In the downlink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends the information to the radio frequency device 92, and the radio frequency device 92 processes the received information and sends the information out through the antenna 91.

[0779] The method performed by the network side device in the above embodiment can be implemented in the baseband device 93, and the baseband device 93 includes a baseband processor.

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

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

[0782] Specifically, the network side device 900 of the embodiment of the present application also includes instructions or programs stored in the memory 95 and executable on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to perform the method performed by each module shown in FIG. 6 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0783] The embodiment of the present application also provides a readable storage medium, and the readable storage medium stores programs or instructions, which are executed by a processor to implement each process of the above downlink receiving and measuring method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

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

[0785] The chip provided by the embodiment of the present application also can be called a system chip, a chip system, a system on chip, or the like.

[0786] It should be understood that the chip mentioned in the embodiment of the present application can also be called a system chip, a chip system, a system on chip, or the like.

[0787] The embodiment of the present application further provides a computer program / program product stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the processes of the above-mentioned downlink receiving and measurement method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0788] The embodiment of the present application further provides a communication system, including a terminal and a network side device. The terminal can be used to execute the steps of the above-mentioned downlink receiving and measurement method, and the network side device can be used to execute the steps of the above-mentioned downlink receiving and measurement method.

[0789] It should be noted that in this document, the terms "comprising", "including", or any other variant thereof are intended to cover non-exclusive inclusions, so that processes, methods, articles, or devices that include a series of elements not only include those elements, but also include other elements not explicitly listed, or include elements inherent to such processes, methods, articles, or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article, or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to the order of performing functions as shown or discussed, and can also include performing functions in a substantially simultaneous manner or in reverse order, for example, the described method can be performed in an order different from that described, and various steps can also be added, omitted, or combined. In addition, the features described with reference to certain examples can be combined in other examples.

[0790] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of computer software products and general hardware platforms, and of course, can also be realized by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disc, optical disc, etc.), and includes a plurality of instructions for making the terminal or network side device execute the method described in each embodiment of the present application.

[0791] The embodiments of the present application are described above with reference to the accompanying drawings, but the present application is not limited to the above-described specific embodiments, and the above-described specific embodiments are merely illustrative, but not restrictive, and a person of ordinary skill in the art can make many forms of embodiments under the inspiration of the present application without departing from the purpose of the present application and the scope protected by the claims, and these embodiments all belong to the protection of the present application.

Claims

1. A method for downlink reception and measurement, comprising: determining, by a terminal, transmission parameters corresponding to a first downlink reception based on a first time domain type corresponding to the first downlink reception, and performing reception corresponding to the first downlink reception according to the transmission parameters corresponding to the first downlink reception; or, performing, by the terminal, at least one of the following: a first measurement and reporting corresponding to the first measurement, based on a second time domain type corresponding to the first measurement; wherein the first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS); in a case where the first downlink reception comprises an SSB, the transmission parameters comprise at least one of: a transmission power; a related parameter of an SSB beam; and a related parameter of an SSB index; in a case where the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameters comprise at least one of: a quasi co-location (QCL) assumption; and a transmission configuration indication (TCI) state; the first measurement comprises at least one of a channel state information (CSI) measurement and a cross link interference (CLI) measurement. the first measurement comprises a CSI measurement; 2. The method of any one of claim 1, wherein, the method further comprises: in a case where reporting of the first measurement needs to distinguish time domain types, determining, by the terminal, a target CSI reference resource corresponding to a target CSI report; performing, by the terminal, at least one of the following operations: determining whether to report the target CSI report based on whether at least one target CSI-RS reception occasion is received; in a case where the target CSI report is a periodic or semi-persistent CSI report, determining a starting time of CPU occupancy based on a latest target CSI-RS reception occasion; determining target information contained in the first measurement using at least one target CSI-RS reception occasion; the target information comprises at least one of L1-RSRP, L1-SINR, and CQI; wherein the target CSI report corresponds to a second time domain type; the target CSI-RS reception occasion corresponds to the second time domain type, and the target CSI-RS reception occasion is not later than the target CSI reference resource. the first downlink reception comprises at least one of an SSB, a PDCCH, and a CSI-RS; 3. The method of claim 1, wherein, a time domain unit in which the first downlink reception is located corresponds to a same time domain type; or, a time domain unit in which the first downlink reception is located can correspond to multiple time domain types or all time domain types. the first downlink reception comprises an SSB; 4. The method of claim 3, wherein, in a case where a time domain unit in which the first downlink reception is located can correspond to multiple time domain types or all time domain types, determining, by the terminal, transmission parameters corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception comprises at least one of the following: the terminal does not distinguish time domain types corresponding to the time domain unit in which the first downlink reception is located, and uniformly determines transmission parameters corresponding to the first downlink reception as first transmission parameters; ​ The terminal distinguishes a time domain type corresponding to a time domain unit in which the first downlink reception is located, and determines a transmission parameter corresponding to the first downlink reception in a time domain unit of different time domain types based on a mapping relationship between the time domain type and the transmission parameter.

5. The method of claim 1, wherein, The first downlink reception includes at least one of a PDSCH, a PDCCH, and a CSI-RS. The method further includes: The terminal receives first information from a network side device, and the first information is used to configure at least one set, each set in the at least one set including at least one transmission parameter; The terminal determines the transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, including: The terminal determines the transmission parameter corresponding to the first downlink reception from the at least one set based on the first time domain type corresponding to the first downlink reception.

6. The method of claim 5, wherein, The at least one set includes at least one of the following: A first set, any transmission parameter in the first set being applicable to any time domain type; At least one second set, a time domain type corresponding to each transmission parameter in the at least one second set being determined by configuration information of the transmission parameter; A third set, a time domain type corresponding to each transmission parameter in the third set being determined by a position of the transmission parameter in the third set; At least one fourth set, all transmission parameters in each fourth set corresponding to a same time domain type, and different fourth sets corresponding to different time domain types.

7. The method of claim 6, wherein, The configuration information of the transmission parameter includes at least one of the following: An identifier of the transmission parameter, a time domain type corresponding to each transmission parameter in the at least one second set being determined by a value of the identifier of the transmission parameter; A first indication of the transmission parameter, the first indication being used to indicate a time domain type, and a time domain type corresponding to each transmission parameter in the at least one second set being the time domain type indicated by the first indication of the transmission parameter.

8. The method of claim 7, wherein, The third set includes one or more subsets, and each subset of the third set satisfies at least one of the following: Each subset of the third set is sorted in a predetermined order, and the predetermined order represents an order of the time domain types; A number of transmission parameters included in each subset of the third set is allocated in a predefined manner or directly configured or indicated.

9. The method of any one of claims 3, 5-8, wherein, The first downlink reception includes a PDCCH corresponding to a first control resource set (CORESET); A time domain unit in which a reception occasion of the first CORESET is located corresponds to a same time domain type; or A time domain unit in which the reception occasion of the first CORESET is located can correspond to multiple time domain types or all time domain types.

10. The method of claim 9, wherein, In a case where the time domain unit in which the reception occasion of the first CORESET is located corresponds to the same time domain type, the time domain type corresponding to the time domain unit in which the reception occasion of the first CORESET is located is determined by at least one of the following: Configuration information of the first CORESET; Configuration information of each search space in a search space associated with the first CORESET; A protocol stipulation; A high-layer parameter.

11. The method of claim 10, wherein, The configuration information of the first CORESET includes at least one of the following: an identity of the first CORESET, a value of the identity of the first CORESET being used to determine a time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located; a second indication of the first CORESET, the second indication being used to indicate a time domain type, the time domain type corresponding to a time domain unit in which a receiving occasion of the first CORESET is located being the time domain type indicated by the second indication; or, the configuration information of the respective search spaces including at least one of the following: identities of the respective search spaces, values of the identities of the respective search spaces being used to respectively determine a time domain type corresponding to a time domain unit in which a receiving occasion of the respective search spaces is located; third indications of the respective search spaces, the third indications being used to indicate a time domain type, the time domain type corresponding to a time domain unit in which a receiving occasion of the respective search spaces is located being the time domain type indicated by the third indications of the respective search spaces.

12. The method of at least one of claims 3, 5-11, further comprising: receiving, by the terminal, second information from a network-side device, the second information being used to indicate at least one of the following: transmission parameters corresponding to all receiving occasions of the first CORESET; of the M time domain types corresponding to the first CORESET, transmission parameters corresponding to a receiving occasion of each of the M time domain types, M being an integer greater than or equal to 1.

13. The method of claim 12, wherein, of the M time domain types corresponding to the first CORESET, transmission parameters corresponding to a receiving occasion of each of the M time domain types being indicated by a same MAC CE; or, of the M time domain types corresponding to the first CORESET, transmission parameters corresponding to a receiving occasion of each of the M time domain types being indicated by different MAC CEs.

14. The method of claim 13, wherein, in a case that transmission parameters corresponding to a receiving occasion of each of the M time domain types corresponding to the first CORESET are indicated by a same MAC CE, the MAC CE including at least one of the following: M first indication fields, the M first indication fields being used to respectively indicate transmission parameters corresponding to a receiving occasion of each of the M time domain types; a second indication field, the second indication field being used to jointly indicate transmission parameters corresponding to a receiving occasion of each of the M time domain types.

15. The method of claim 14, wherein, in a case that transmission parameters corresponding to a receiving occasion of each of the M time domain types corresponding to the first CORESET are indicated by different MAC CEs, the MAC CEs including at least one of the following: a third indication field, the third indication field being used to indicate a time domain type corresponding to the MAC CE; a fourth indication field, the fourth indication field being used to indicate transmission parameters corresponding to the time domain type corresponding to the MAC CE; a fifth indication field, the fifth indication field being used to indicate an activation state or a deactivation state of the transmission parameters corresponding to the time domain type corresponding to the MAC CE.

16. The method of any one of claims 5 to 15, wherein, the first downlink reception including a PDSCH; the method further comprising: receiving, by the terminal, third information from a network-side device, the third information being used to indicate at least one of the following: The activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1. The activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1.

17. The method of claim 16, wherein, The activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1. The activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception, N being an integer greater than or equal to 1.

18. The method of claim 17, wherein, In the case that the activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception is indicated by the same MAC CE, the MAC CE includes at least one of the following: N sixth indication fields, the N sixth indication fields being used to respectively indicate the activation transmission parameter corresponding to each time domain type in the N time domain types; A seventh indication field, the seventh indication field being used to jointly indicate the activation transmission parameter corresponding to each time domain type in the N time domain types.

19. The method of claim 17, wherein, In the case that the activation transmission parameter corresponding to each time domain unit corresponding to each time domain type in the N time domain types corresponding to the first downlink reception is indicated by different MAC CEs, the MAC CE includes at least one of the following: An eighth indication field, used to indicate the time domain type corresponding to the MAC CE; A ninth indication field, used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.

20. The method of any one of claims 16-19, wherein, The terminal determines the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, including at least one of the following: In the case that the first downlink reception needs to apply the transmission parameter indicated by the third information, the terminal selects the transmission parameter with the same time domain type as the time domain type corresponding to the first downlink reception from the transmission parameter indicated by the third information as the transmission parameter corresponding to the first downlink reception; In the case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is the same as the time domain type corresponding to the CORESET of the PDCCH, the terminal determines the transmission parameter corresponding to the CORESET of the PDCCH as the transmission parameter corresponding to the first downlink reception; In the case that the first downlink reception needs to apply the transmission parameter of the PDCCH, and the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, the terminal determines the default transmission parameter or the predefined transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception; In a case where the first downlink reception needs to apply a transmission parameter of a PDCCH, and at least one time domain type corresponding to a CORESET of the PDCCH does not contain a time domain type corresponding to the first downlink reception, the terminal determines a default transmission parameter corresponding to the first time domain type or a predefined transmission parameter as the transmission parameter corresponding to the first downlink reception. In a case where the first downlink reception needs to apply a transmission parameter of a PDCCH, and at least one time domain type corresponding to a CORESET of the PDCCH contains a time domain type corresponding to the first downlink reception, the terminal selects, from transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter of which time domain type is the same as the time domain type corresponding to the first downlink reception, as the transmission parameter corresponding to the first downlink reception. In a case where the first downlink reception needs to apply a default transmission parameter, the terminal determines a default transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception. In a case where the first downlink reception needs to apply an initial transmission parameter, the terminal determines an initial transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception.

21. The method of any one of claims 3, 5 to 8, wherein, The first downlink reception includes a CSI-RS corresponding to a first non-zero power (NZP) CSI-RS resource. In a case where the first NZP CSI-RS resource is a periodic or semi-persistent resource, time domain units in which reception occasions corresponding to the first NZP CSI-RS resource are located correspond to a same time domain type, or time domain units in which the reception occasions corresponding to the first NZP CSI-RS resource are located can correspond to multiple time domain types or all time domain types.

22. The method of claim 3 or 21, further comprising: The terminal receives fourth information from a network side device, the fourth information being used to indicate at least one of the following: a transmission parameter corresponding to all reception occasions corresponding to the first NZP CSI-RS resource; a transmission parameter corresponding to a reception occasion corresponding to each of the S time domain types corresponding to the first NZP CSI-RS resource, S being an integer greater than or equal to 1.

23. The method of claim 3 or 21, wherein, The terminal determines a transmission parameter corresponding to the first downlink reception based on a first time domain type corresponding to the first downlink reception, comprising: In a case where the first NZP CSI-RS resource is an aperiodic resource, and a CSI-RS corresponding to the first NZP CSI-RS resource needs to apply a default transmission parameter, the terminal determines a default transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.

24. The method of claim 1, wherein, The first measurement includes a CLI measurement; In a case where the first measurement is performed based on a CLI measurement resource within a time domain unit corresponding to the second time domain type, a transmission parameter corresponding to the CLI measurement resource includes at least one of the following: a transmission parameter corresponding to a latest-received PDSCH within a time domain unit corresponding to the second time domain type; a transmission parameter corresponding to a latest-received PDSCH corresponding to the second time domain type; a transmission parameter corresponding to a latest-monitored CORESET within a time domain unit corresponding to the second time domain type; a transmission parameter corresponding to a latest-monitored CORESET corresponding to the second time domain type; a transmission parameter corresponding to a later one of a latest-received PDSCH and a latest-monitored CORESET within a time domain unit corresponding to the second time domain type; a transmission parameter corresponding to a later one of a latest-received PDSCH and a latest-monitored CORESET corresponding to the second time domain type.

25. The method of claim 24, wherein, The transmission parameter corresponding to the CLI measurement resource includes a QCL assumption, and a type of the QCL assumption includes a type D.

26. A downlink receiving and measurement method, comprising: a network-side device determining a transmission parameter corresponding to a first downlink reception based on a first time domain type corresponding to the first downlink reception, and performing a sending corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or, the network-side device performing a receiving of a measurement report corresponding to a first measurement based on a second time domain type corresponding to the first measurement; wherein the first downlink reception includes at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS); in a case where the first downlink reception includes the SSB, the transmission parameter includes at least one of a transmission power, a related parameter of an SSB beam, and a related parameter of an SSB index; in a case where the first downlink reception includes at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter includes at least one of a quasi-co-location (QCL) assumption and a transmission configuration indication (TCI) state; the first measurement includes at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

27. The method of claim 26, wherein, the first downlink reception includes at least one of the SSB, the PDCCH, and the CSI-RS; a time domain unit where the first downlink reception is located corresponds to a same time domain type; or, a time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

28. The method of claim 26, wherein, the first downlink reception includes at least one of the PDSCH, the PDCCH, and the CSI-RS; the method further comprises: the network-side device sending, to a terminal, first information used for configuring at least one set, each set in the at least one set including at least one transmission parameter; the network-side device determining the transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception, includes: the network-side device determining the transmission parameter corresponding to the first downlink reception from the at least one set based on the first time domain type corresponding to the first downlink reception.

29. The method of claim 28, wherein, the at least one set includes at least one of: a first set, any one transmission parameter in the first set is applicable to any time domain type; at least one second set, each transmission parameter in the at least one second set corresponds to a time domain type determined by configuration information of the transmission parameter; a third set, each transmission parameter in the third set corresponds to a time domain type determined by a position of the transmission parameter in the third set; at least one fourth set, all transmission parameters in each of the fourth sets correspond to a same time domain type, and different fourth sets correspond to different time domain types.

30. The method of claim 28 or 29, wherein, the first downlink reception comprises a PDCCH corresponding to a first control resource set CORESET; the method further comprises: the network-side device sends second information to the terminal, the second information being used for indicating at least one of the following: transmission parameters corresponding to all reception occasions of the first CORESET; of M time domain types corresponding to the first CORESET, transmission parameters corresponding to reception occasions of each time domain type, M being an integer greater than or equal to 1.

31. The method of any one of claims 28-30, wherein, the first downlink reception comprises a PDSCH; the method further comprises: the network-side device sends third information to the terminal, the third information being used for indicating at least one of the following: active transmission parameters corresponding to all time domain units corresponding to the first downlink reception; of N time domain types corresponding to the first downlink reception, active transmission parameters corresponding to time domain units of each time domain type, N being an integer greater than or equal to 1.

32. The method of any one of claims 26 to 29, wherein, the first downlink reception comprises a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource; the method further comprises: the network-side device sends fourth information to the terminal, the fourth information being used for indicating at least one of the following: transmission parameters corresponding to all reception occasions corresponding to the first NZP CSI-RS resource; of S time domain types corresponding to the first NZP CSI-RS resource, transmission parameters corresponding to reception occasions of each time domain type, S being an integer greater than or equal to 1.

33. A downlink reception and measurement apparatus, the apparatus comprising: a first processing unit configured to: determine transmission parameters corresponding to a first downlink reception based on a first time domain type corresponding to the first downlink reception, and perform reception corresponding to the first downlink reception according to the transmission parameters corresponding to the first downlink reception; or, perform at least one of a first measurement and reporting corresponding to the first measurement based on a second time domain type corresponding to the first measurement; wherein the first downlink reception comprises at least one of a synchronization signal block SSB, a physical downlink control channel PDCCH, a physical downlink shared channel PDSCH, and a channel state information reference signal CSI-RS; in a case where the first downlink reception comprises an SSB, the transmission parameters comprise at least one of: a transmission power; a related parameter of an SSB beam; and a related parameter of an SSB index. In a case where the first downlink reception comprises at least one of a PDCCH, a PDSCH, and a CSI-RS, the transmission parameter comprises at least one of: a quasi co-location (QCL) assumption; a transmission configuration indication (TCI) state. The first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement.

34. The apparatus of claim 33, wherein, The first downlink reception comprises at least one of a SSB, a PDCCH, and a CSI-RS. The time domain unit where the first downlink reception is located corresponds to one same time domain type; or, The time domain unit where the first downlink reception is located can correspond to multiple time domain types or all time domain types.

35. The apparatus of claim 33, wherein, The first downlink reception comprises at least one of a PDSCH, a PDCCH, and a CSI-RS. The apparatus further comprises: A first receiving unit, configured to receive first information from a network side device, the first information being used for configuring at least one set, each set in the at least one set comprising at least one transmission parameter; The first processing unit is specifically configured to: determine, based on a first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception from the at least one set.

36. The apparatus of claim 34 or 35, wherein, The first downlink reception comprises a PDCCH corresponding to a first control resource set (CORESET); The apparatus further comprises: A second receiving unit, configured to receive second information from a network side device, the second information being used for indicating at least one of: a transmission parameter corresponding to all reception occasions of the first CORESET; for M time domain types corresponding to the first CORESET, a transmission parameter corresponding to each of the reception occasions of a time domain type, M being an integer greater than or equal to 1.

37. The apparatus of claim 35, wherein, The first downlink reception comprises a PDSCH; The apparatus further comprises: A third receiving unit, configured to receive third information from a network side device, the third information being used for indicating at least one of: an active transmission parameter corresponding to all time domain units corresponding to the first downlink reception; for N time domain types corresponding to the first downlink reception, an active transmission parameter corresponding to each of the time domain units of a time domain type, N being an integer greater than or equal to 1.

38. The apparatus of claim 34 or 35, wherein, The first downlink reception comprises a CSI-RS corresponding to a first non-zero power (NZP) CSI-RS resource; The apparatus further comprises: A fourth receiving unit, configured to receive fourth information from a network side device, the fourth information being used for indicating at least one of: a transmission parameter corresponding to all reception occasions corresponding to the first NZP CSI-RS resource; for S time domain types corresponding to the first NZP CSI-RS resource, a transmission parameter corresponding to each of the reception occasions of a time domain type, S being an integer greater than or equal to 1.

39. A downlink reception and measurement apparatus, the apparatus comprising: a processing unit, configured to: determine, based on a first time domain type corresponding to a first downlink reception, a transmission parameter corresponding to the first downlink reception, and perform transmission corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or, performing, based on a second time domain type corresponding to the first measurement, reception of a measurement report corresponding to the first measurement; wherein the first downlink reception comprises at least one of a synchronization signal block (SSB), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a channel state information reference signal (CSI-RS); in a case where the first downlink reception comprises the SSB, the transmission parameter comprises at least one of a transmit power, a related parameter of an SSB beam, and a related parameter of an SSB index; in a case where the first downlink reception comprises at least one of the PDCCH, the PDSCH, and the CSI-RS, the transmission parameter comprises at least one of a quasi co-location (QCL) assumption and a transmission configuration indication (TCI) state. the first measurement comprises at least one of a channel state information (CSI) measurement and a cross-link interference (CLI) measurement. 40.A communication device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the downlink reception and measurement method according to any one of claims 1 to 25, or implement steps of the downlink reception and measurement method according to any one of claims 26 to 32. 41.A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement steps of the downlink reception and measurement method according to any one of claims 1 to 25, or implement steps of the downlink reception and measurement method according to any one of claims 26 to 32. 42.A computer program product comprising computer instructions, the computer instructions, when executed by a processor, implement steps of the downlink reception and measurement method according to any one of claims 1 to 25, or implement steps of the downlink reception and measurement method according to any one of claims 26 to 32.

Images