WO2025218586A1 - 下行接收和测量方法、装置及通信设备 - Google Patents

下行接收和测量方法、装置及通信设备

Info

Publication number
WO2025218586A1
WO2025218586A1 PCT/CN2025/088420 CN2025088420W WO2025218586A1 WO 2025218586 A1 WO2025218586 A1 WO 2025218586A1 CN 2025088420 W CN2025088420 W CN 2025088420W WO 2025218586 A1 WO2025218586 A1 WO 2025218586A1
Authority
WO
WIPO (PCT)
Prior art keywords
time domain
downlink reception
reception
csi
transmission parameters
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/088420
Other languages
English (en)
French (fr)
Inventor
曾超君
陈晓航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025218586A1 publication Critical patent/WO2025218586A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a downlink reception and measurement method, apparatus, and communication equipment.
  • time domain units can correspond to or distinguish between multiple time domain types.
  • related technologies only require terminals to perform downlink reception or measurements in one time domain type, making them unsuitable for flexible duplexing scenarios. This can lead to terminals being confused about how to perform downlink reception or measurements.
  • the embodiments of the present application provide a downlink reception and measurement method, apparatus, and communication equipment, which can solve the problem of how a terminal performs downlink reception or measurement in a flexible duplex scenario.
  • a downlink reception and measurement method is provided, which is performed by a terminal.
  • the method includes:
  • the terminal determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, and performs reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or
  • the terminal performs, based on the second time domain type corresponding to the first measurement, at least one of the first measurement and the reporting corresponding to the first measurement;
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a downlink reception and measurement method is provided, which is performed by a network-side device.
  • the method includes:
  • the network-side device determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, and performs transmission corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or
  • the network-side device receives a measurement report corresponding to the first measurement based on the second time domain type corresponding to the first measurement;
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a downlink receiving and measuring device comprising:
  • a first 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 reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a downlink receiving and measuring device 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
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
  • a terminal including a processor and a communication interface, wherein the processor is configured to:
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a network side device which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.
  • a network-side device including a processor and a communication interface, wherein the processor is configured to:
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
  • a wireless communication system comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.
  • a chip which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.
  • a computer program/program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the downlink reception and measurement method as described in the first aspect, or to implement the steps of the downlink reception and measurement method as described in the second aspect.
  • the terminal determines the transmission parameters 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 parameters 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; when the first downlink reception includes SSB, the transmission parameters include at least one of the following: transmit power; related parameters of the SSB beam; related parameters of the SSB index; when the first downlink reception includes at least one of PDCCH, PDSCH, and CSI-RS, the transmission parameters include at least one of the following: QCL assumption; TCI state; the first measurement includes at least one of CSI measurement and CLI measurement.
  • the terminal can determine the transmission parameters corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, so that the terminal can achieve flexible and reliable downlink reception according to the determined transmission parameters.
  • 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 achieve flexible, accurate and effective measurement. It can be seen that the embodiment of the present application can achieve downlink reception or measurement of the terminal in a flexible duplex scenario.
  • FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application.
  • FIG2 is a schematic diagram of a flexible duplex mode
  • FIG3 is a flow chart of a downlink receiving and measuring method provided in an embodiment of the present application.
  • FIG4 is a flowchart of another downlink receiving and measuring method provided in an embodiment of the present application.
  • FIG5 is a structural diagram of a downlink receiving and measuring device provided in an embodiment of the present application.
  • FIG6 is a structural diagram of another downlink receiving and measuring device provided in an embodiment of the present application.
  • FIG7 is a structural diagram of a communication device provided in an embodiment of the present application.
  • FIG8 is a structural diagram of a terminal provided in an embodiment of the present application.
  • FIG9 is a structural diagram of a network-side device provided in an embodiment of the present application.
  • first, second, etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by “first” and “second” are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more.
  • “or” in this application represents at least one of the connected objects. For example, “A or B” covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B.
  • the character "/" generally indicates that the objects associated before and after are in an "or” relationship.
  • indication in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication).
  • a direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent;
  • an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • FIG1 shows a block diagram of a wireless communication system applicable to embodiments of the present application.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), a flight vehicle, a vehicle user equipment (VUE), a ship-borne equipment, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (PC), an ATM or a self-service machine and other terminal-side devices.
  • PC personal computer
  • ATM an ATM or a self-service machine and other terminal
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.
  • the network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit.
  • the access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.
  • WLAN wireless Local Area Network
  • AP Access Point
  • WiFi wireless Fidelity
  • the base station can be called Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, base The Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, transmission reception point (TRP) or other appropriate terms in the relevant field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiments of the present application, only the base station in the NR system is introduced as an example, and the specific type of the base station is not limited.
  • the core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (Edge Application Server Discovery Function), etc. ion, EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc.
  • MME mobility management entity
  • AMF access mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • PCF policy and charging rules function unit
  • edge application service discovery function Edge Application Server Discovery Function
  • EASDF Edge Application Server Discovery Function
  • UDM Unified Data Management
  • UDR
  • frequency division duplex FDD
  • TDD time division duplex
  • a flexible duplexing scheme based on non-overlapping sub-bands in the frequency domain namely non-overlapping sub-band full duplex (SBFD) (also referred to as sub-band full duplex), is as follows:
  • uplink and downlink transmissions can occur simultaneously within different frequency sub-bands.
  • a guard band can be reserved between the frequency sub-bands corresponding to different transmission directions (e.g., uplink and downlink sub-bands).
  • the terminal side supports half-duplex, only uplink transmission or downlink transmission can be performed at the same time, and both cannot be performed at the same time. It is understandable that in this case, the uplink transmission and downlink transmission on the network side at the same time can only be directed to different terminals.
  • uplink transmission and downlink transmission can be performed simultaneously in different frequency domain sub-bands.
  • Figure 2 illustrates the flexible duplexing scheme described above.
  • the network semi-statically divides the frequency domain of a single carrier into three subbands. Downlink subbands are located on either side of the carrier, while the center is an uplink subband. This reduces interference with adjacent carriers.
  • UE1 transmits uplink
  • UE2 receives downlink.
  • a time-domain unit can correspond to multiple time-domain types, such as SBFD symbols and non-SBFD symbols.
  • the network may use different antenna or radio frequency (RF) settings for SBFD and non-SBFD symbols to provide self-interference mitigation for SBFD operation.
  • RF radio frequency
  • the spatial correlation (Spatial Relation) or Transmission Configuration Indicator (TCI) state for the uplink channel or signal within an SBFD symbol may also differ from that for a non-SBFD symbol.
  • RF radio frequency
  • TCI Transmission Configuration Indicator
  • the embodiments of the present application provide a downlink reception and measurement method, a downlink reception and measurement apparatus, and a communication device to solve the problem of how a terminal performs downlink reception and measurement in a flexible duplex mode.
  • the following Symbol types can be distinguished: downlink symbol (DL symbol), uplink symbol (UL symbol), and flexible symbol.
  • each Symbol can be considered as a Flexible symbol, or the rules or operations corresponding to the Flexible symbol are followed.
  • the network can use SBFD configuration information to configure certain symbols to perform SBFD operations, effectively configuring these symbols as SBFD symbols. For example, some or all symbols within a single cycle determined by the TDD pattern can be configured as SBFD symbols. These symbols can be some or all of the symbol types identified by the TDD pattern configuration information.
  • the SBFD symbol on the Serving cell can be further distinguished by the following Symbol type:
  • the network side supports SBFD operation based on full-duplex; the UE side only supports SBFD operation based on half-duplex, that is, within a single SBFD symbol, the UE can only perform uplink transmission or downlink reception, and cannot simultaneously perform uplink transmission and downlink reception based on FDM (Frequency Division Multiplexing).
  • FDM Frequency Division Multiplexing
  • the network supports full-duplex SBFD operation; the UE can also support full-duplex SBFD operation, meaning that the UE can simultaneously perform FDM-based uplink transmission and downlink reception within a single SBFD symbol.
  • a UE that supports full-duplex SBFD operation i.e., Duplex mode 2, or the SBFD symbol for duplex mode 2
  • must also support half-duplex SBFD operation i.e., Duplex mode 1, or the SBFD symbol for duplex mode 1).
  • a symbol that is not configured (or instructed) to perform an SBFD operation can be considered a non-SBFD symbol.
  • the mainstream view is that: for different Symbol types distinguished by SBFD configuration information (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), the parameters corresponding to each Channel/Signal can be configured separately (or directly) or derived (implicitly based on frequency domain offset (Offset), respective starting reference points, etc.) to consider/compensate for the antenna and RF configuration (including antenna position, number of antennas, connection relationship between antenna and RF chain, etc.), interference conditions and limitations (including self-interference (SI), cross-link interference (CLI) and corresponding limitations) corresponding to different Symbol types.
  • the QCL assumption/TCI state corresponding to the downlink or CLI measurement Channel/Signal in the SBFD symbol may also be different from that of the non-SBFD symbol.
  • FIG3 shows a flow chart of a downlink receiving and measuring method provided by an embodiment of the present application. As shown in FIG3 , the downlink receiving and measuring method includes:
  • Step 301 The terminal determines, based on a first time domain type corresponding to a first downlink reception, a transmission parameter corresponding to the first downlink reception, and performs 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.
  • the first downlink reception may include 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).
  • SSB synchronization signal block
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • CSI-RS channel state information reference signal
  • the transmission parameters include at least one of the following: transmit power; parameters related to the SSB beam; and parameters related to the SSB index.
  • the transmission parameters include at least one of the following: a quasi co-location (QCL) assumption; and a TCI state.
  • the parameters related to the SSB beam may include, for example, the number of SSB beams, the direction of the SSB beam, and the width of the SSB beam.
  • the first measurement may include at least one of a channel state information (CSI) measurement and a CLI measurement.
  • CSI channel state information
  • CLI CLI measurement
  • step 301 includes: the terminal determines the transmission parameters 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 parameters corresponding to the first downlink reception; and 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.
  • the time domain type can be understood as the type of time domain unit.
  • the time domain type can include two types: SBFD time domain unit and non-SBFD time domain unit.
  • SBFD time domain unit can further include SBFD time domain unit for duplex mode 1 and SBFD time domain unit for duplex mode 2.
  • a time domain unit can be a time slot, a symbol, or the like. In this application, the time domain unit is described using a symbol as an example. In this case, the time domain type can be referred to as a symbol type.
  • the symbol type can include two types: SBFD symbol and non-SBFD symbol. SBFD symbol can further include SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2.
  • the time domain type can be referred to as a slot type, which is not limited in this application.
  • the first and second time domain types in the embodiments of this application can be understood with reference to the relevant description of the time domain type above. To avoid repetition, this description is not repeated.
  • Embodiments of the present application are applicable to SBFD-enabled serving cells/BWPs.
  • the UE can determine the QCL assumption/TCI state corresponding to the downlink channel/signal or the CLI measurement channel/signal based on the symbol type.
  • the UE here can be understood as an SBFD-capable UE or an SBFD-aware UE.
  • the terminal determines the transmission parameters 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 parameters 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; when the first downlink reception includes SSB, the transmission parameters include at least one of the following: transmit power; related parameters of the SSB beam; related parameters of the SSB index; when the first downlink reception includes at least one of PDCCH, PDSCH, and CSI-RS, the transmission parameters include at least one of the following: QCL assumption; TCI state; the first measurement includes at least one of CSI measurement and CLI measurement.
  • the terminal can determine the transmission parameters corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, so that the terminal can achieve flexible and reliable downlink reception according to the determined transmission parameters.
  • 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 achieve flexible, accurate and effective measurement. It can be seen that the embodiment of the present application can achieve downlink reception or measurement of the terminal in a flexible duplex scenario.
  • the first downlink reception includes at least one of an SSB, a PDCCH, and a CSI-RS;
  • the time domain units where the first downlink reception is performed correspond 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.
  • the following describes the relevant implementation methods of SSB reception by taking the first downlink reception including SSB as an example.
  • the first downlink reception includes SSB
  • the terminal determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including at least one of the following:
  • 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 parameters corresponding to the first downlink reception as the first transmission parameters;
  • the terminal distinguishes the time domain type corresponding to the time domain unit where the first downlink reception is located, and determines the transmission parameters corresponding to the first downlink reception in time domain units of different time domain types based on the mapping relationship between the time domain type and the transmission parameters.
  • the embodiments of the present application provide an illustrative example of the SSB transmission method.
  • SSB transmission mode 1 For SSB transmission, either SSB transmission mode 1 or SSB transmission mode 2 can be used:
  • SSB transmission mode 1 SSB can only be transmitted within the symbol corresponding to a single symbol type.
  • the network can either guarantee (and the UE expects) that configured SSBs are only within the symbol corresponding to that symbol type, or the network can configure SSBs without guaranteeing that they appear only within the symbol corresponding to that symbol type, but the UE will only consider SSBs within the symbol corresponding to that symbol type to be valid.
  • SSBs can only be configured within non-SBFD symbols, or SSBs can only be transmitted within non-SBFD symbols.
  • SSB transmission mode 2 SSB can be transmitted within the symbol corresponding to each (or more than one) symbol type.
  • SSB attribute mode 1 For the configuration/assumption of the SSB transmission attributes (ie, transmission parameters), either SSB attribute mode 1 or SSB attribute mode 2 may be used:
  • SSB attribute mode 1 The UE assumes that the transmission attributes of the SSBs transmitted in symbols corresponding to different symbol types are exactly the same, or the UE does not distinguish the differences in transmission attributes between the SSBs transmitted in symbols corresponding to different symbol types.
  • SSB attribute mode 1 can be understood as: the UE believes that the SSBs transmitted in symbols corresponding to different symbol types use unified configuration parameters and can be processed uniformly without considering the differences.
  • SSB attribute mode 2 The UE believes that there may be differences in transmission attributes between SSBs transmitted in Symbols corresponding to different Symbol types.
  • Differences in SSB transmission attributes include at least one of the following:
  • ssb-PositionsInBurst can be configured independently for an SBFD symbol to indicate the set of SSB indices actually transmitted within a single SSB burst set transmitted within the SBFD symbol;
  • SSB transmit power for example, ss-PBCH-BlockPower can be configured independently for the SBFD symbol to indicate the transmit power of the SSB transmitted within the SBFD symbol;
  • the network side sets the direction and/or width of each SSB beam, which is transparent to the UE.
  • different SSB transmission attributes can be distinguished based on the symbol type.
  • the SSB transmission attributes corresponding to each symbol type involved in the SSB transmission can be independently configured/determined, or more than one set of SSB transmission attributes can be configured, and the mapping relationship between each symbol type and each set of SSB transmission attributes can be configured/determined.
  • 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 the PDSCH, determine the mapped random access opportunity (RACH Occasion, RO), etc.
  • the specific SSB transmission mode to be used, or, when SSB transmission mode 2 is used, whether to use SSB attribute mode 1 or SSB attribute mode 2, may be specified by the protocol or configured by higher-layer signaling.
  • the use of SSB attribute mode 1 or SSB attribute mode 2 may be indicated in System Information Block 1 (SIB1).
  • SIB1 System Information Block 1
  • SIB1 PDSCH i.e., the PDSCH carrying the initial/retransmission of SIB1
  • SIB1 PDSCH i.e., the PDSCH carrying the initial/retransmission of SIB1
  • SIB1 PDSCH can only be transmitted within a symbol corresponding to a single symbol type
  • SIB1 PDSCH can be transmitted within the Symbol corresponding to each (or more than one) Symbol type.
  • the following describes the implementation methods of the general TCI state configuration corresponding to downlink reception by taking the first downlink reception including at least one of PDSCH, PDCCH and CSI-RS as an example.
  • the first downlink reception includes at least one of a PDSCH, a PDCCH, and a CSI-RS;
  • the method further comprises:
  • the terminal receives first information from a network-side device, where 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 determining, based on a first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception includes:
  • the terminal determines, from the at least one set, a transmission parameter corresponding to the first downlink reception based on the first time domain type corresponding to the first downlink reception.
  • the at least one set includes at least one of the following:
  • any transmission parameter in the first set can be used for any time domain type
  • the time domain type corresponding to each transmission parameter in the at least one second set is determined by configuration information of the transmission parameter
  • At least one fourth set all transmission parameters in each of the fourth sets correspond to the same time domain type, and different fourth sets correspond to different time domain types.
  • the configuration information of the transmission parameters includes at least one of the following:
  • a first indication of a transmission parameter where 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.
  • the third set includes one or more subsets, and each subset of the third set satisfies at least one of the following:
  • the subsets of the third set are sorted according to a predetermined order, where the predetermined order represents the order of the time domain types;
  • 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.
  • the embodiments of the present application provide an illustrative example of the configuration method of the general TCI state corresponding to downlink reception.
  • the TCI state configuration corresponding to the downlink reception can be configured using either General TCI State Configuration Mode 1 or General TCI State Configuration Mode 2:
  • General TCI state configuration method 1 Regardless of the Symbol type, a unified configuration TCI state set (i.e. the first set) is applied.
  • General TCI state configuration mode 1 can be understood as, for the downlink reception corresponding to any Symbol type (or, the downlink reception within the Symbol corresponding to any Symbol type; when the joint mode is adopted, it can be expanded to further include the uplink transmission, that is, the uplink transmission corresponding to the Symbol type, or, the uplink transmission within the Symbol corresponding to the Symbol type), any TCI state in this configured TCI state set can be applied as needed; in other words, there is no restriction on the Symbol type corresponding to the downlink reception (when the joint mode is adopted, it further includes the uplink transmission) applied by any TCI state in this configured TCI state set.
  • the unified configuration TCI state set here can be determined based on the tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config.
  • joint mode it can be determined based on the 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.
  • General TCI state configuration method 2 Distinguish the configuration TCI state set of each Symbol type application.
  • General TCI state configuration method 2-1 In the configuration information of each TCI state, distinguish the Symbol type corresponding to this TCI state.
  • the TCI states corresponding to each Symbol type can still be placed in a unified configuration TCI state set (i.e., the second set).
  • the corresponding TCI state subset can be filtered from this configuration TCI state set to serve as the configuration TCI state set corresponding to that Symbol type.
  • Method 1 or Method 2 can be used:
  • Method 1 Determine the Symbol type corresponding to each TCI state based on the TCI-StateId value range of each TCI state. It is assumed here that each Symbol type corresponds to an independent TCI-StateId value range, which can be specified by the protocol or configured by high-level signaling; the TCI-StateId value ranges corresponding to different Symbol types do not overlap. When configuring the TCI state corresponding to a certain Symbol type, the TCI-StateId of this TCI state must be within the TCI-StateId value range corresponding to the Symbol type.
  • Method 2 In the configuration information of each TCI state, introduce a new parameter (i.e., the first indication) to indicate the Symbol type corresponding to this TCI state.
  • General TCI state configuration method 2-2 Based on the position of a certain TCI state in the unified configuration TCI state set, determine the Symbol type corresponding to this TCI state.
  • TCI state corresponding to each Symbol type is placed in a unified configuration TCI state set (i.e., the third set), and this unified configuration TCI state set is an ordered set, which is 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).
  • the first configured tci-StatesToAddModList (when joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17) is used as the initial set of this unified configuration TCI state set; the newly added TCI state in the subsequent configured tci-StatesToAddModList (when joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17) is added to the end of this unified configuration TCI state set in the order of appearance in tci-StatesToAddModList.
  • the modified TCI state can either overwrite the corresponding TCI state in this unified configuration TCI state set, or be added to this unified configuration TCI state set in the order of appearance in tci-StatesToAddModList.
  • the tail of a unified configuration TCI state set (at this time, the corresponding TCI state in this unified configuration TCI state set needs to be deleted; the modified TCI state can be placed before or after the newly added TCI state, or it can be added to the tail of this unified configuration TCI state set together with the newly added TCI state in the order of appearance in tci-StatesToAddModList (at this time, the newly added TCI state and the modified TCI state added to the tail of this unified configuration TCI state set may be mixed or alternated)); based on the configured tci-StatesToReleaseList (when joint mode is used, it can be dl-OrJointTCI-StateToReleaseList-r17), the corresponding TCI state is deleted from
  • the location area of the TCI state corresponding to a certain Symbol type is determined; all TCI states in this location area constitute the configured TCI state set corresponding to the Symbol type.
  • the first N1 TCI states of this ordered set correspond to Symbol type 1 (e.g., non-SBFD symbols), and the remaining N2 TCI states correspond to Symbol type 2 (e.g., SBFD symbols).
  • Symbol type 1 e.g., non-SBFD symbols
  • Symbol type 2 e.g., SBFD symbols
  • General TCI state configuration method 2-3 Configure and/or maintain the configuration TCI state set corresponding to each Symbol type (i.e. the fourth set).
  • the corresponding TCI state add/modify list (such as tci-StatesToAddModList) and/or TCI state release list (such as tci-StatesToReleaseList) can be set for each Symbol type in the PDSCH-Config.
  • the corresponding dl-OrJointTCI-StateToAddModList-r17 and/or dl-OrJointTCI-StateToReleaseList-r17 can be set for each Symbol type in PDSCH-Config; based on the tci-StatesToAddModList and tci-StatesToReleaseList corresponding to a certain Symbol type (when joint mode is adopted, the dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 corresponding to a certain Symbol type can be used to maintain the configuration TCI state set corresponding to the Symbol type.
  • a new tci-StatesToAddModList and/or tci-StatesToReleaseList is introduced in PDSCH-Config for the SBFD symbol (when joint mode is adopted, a new dl-OrJointTCI-StateToAddModList-r17 and/or dl-OrJointTCI-StateToReleaseList-r17 can be introduced in PDSCH-Config for the 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 to maintain the configuration TCI state set corresponding to the non-SBFD symbol.
  • the configuration TCI state set corresponding to the Symbol type is maintained based on the tci-StatesToAddModList and tci-StatesToReleaseList in the PDSCH-Config corresponding to a certain Symbol type (when joint mode is adopted, it can be dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 in PDSCH-Config).
  • the following describes relevant implementation methods of PDCCH reception by taking the case where the first downlink reception includes a PDCCH corresponding to the first CORESET as an example.
  • the first downlink reception includes a PDCCH corresponding to the first CORESET
  • the time domain units where the reception opportunities of the first CORESET are located correspond to the same time domain type; or,
  • the time domain unit where the reception opportunity of the first CORESET is located can correspond to multiple time domain types or all time domain types.
  • 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.
  • the time domain type corresponding to the time domain unit where the reception timing of the first CORESET is located is determined by at least one of the following:
  • the time domain type determination operation can be understood as including the following operations: the UE determines the time domain type corresponding to the time domain units where all reception opportunities corresponding to the first CORESET are located based on all search spaces associated with the first CORESET.
  • the configuration information of the first CORESET includes at least one of the following:
  • an identifier of the first CORESET wherein a value of the identifier of the first CORESET is used to determine a time domain type corresponding to a time domain unit where a reception opportunity of the first CORESET is located;
  • the second indication of the first CORESET is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of the first CORESET is located is the time domain type indicated by the second indication.
  • the configuration information of each search space includes at least one of the following:
  • the identifiers of the search spaces where the values of the identifiers of the search spaces are used to respectively determine the time domain types corresponding to the time domain units where the reception opportunities of the search spaces are located;
  • the third indication of each search space is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of each search space is located is the time domain type indicated by the third indication of each search space.
  • the search space identifier can be used to indicate the symbol type corresponding to the reception occasion (occasion) of the CORESET associated with this search space.
  • the search space identifier can be used to indicate the symbol type of the reception occasion of the first CORESET.
  • the third indication of the search space can be used to indicate the symbol type corresponding to the reception timing of the CORESET associated with this search space.
  • the third indication of the search space can be used to indicate the symbol type of the reception timing of the first CORESET.
  • the method further includes:
  • the terminal receives second information from a network-side device, where the second information is used to indicate at least one of the following:
  • the receiving opportunities corresponding to each time domain type respectively correspond to transmission parameters, where M is an integer greater than or equal to 1.
  • the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types are indicated by the same MAC CE; or,
  • the transmission parameters corresponding to the receiving moments corresponding to each time domain type are indicated by different MAC CEs.
  • the transmission parameters corresponding to the receiving opportunities corresponding to each time domain type are indicated by different MAC CEs. It can be understood that independent MAC CEs are used to respectively indicate the transmission parameters corresponding to the receiving opportunities corresponding to each time domain type.
  • the MAC CE includes at least one of the following:
  • M first indication fields the M first indication fields being used to respectively indicate transmission parameters corresponding to receiving opportunities corresponding to respective time domain types in the M time domain types;
  • the second indication field is used to jointly indicate the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types in the M time domain types.
  • the MAC CE when different MAC CEs are used to indicate transmission parameters corresponding to reception opportunities corresponding to respective time domain types in the M time domain types corresponding to the first CORESET, the MAC CE includes at least one of the following:
  • the third indication field is used to indicate the time domain type corresponding to the MAC CE
  • the fourth indication field is used to indicate the transmission parameters corresponding to the corresponding time domain type
  • the fifth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • a certain CORESET (such as the first CORESET), based on its usage (for example, its association with one or more Search Spaces, and the time domain monitoring configuration of these associated Search Spaces), it can correspond to multiple Occasions (or at least one Occasion) in the time domain.
  • CORESET Occasion Configuration Mode 1 For the configuration of the time-frequency position of a CORESET, either CORESET Occasion Configuration Mode 1 or CORESET Occasion Configuration Mode 2 can be used:
  • the Occasion corresponding to the CORESET can only be located in the Symbol corresponding to a single Symbol type.
  • a single Symbol type (assuming a given Symbol type (i.e., the first time domain type)) can be determined using one of the following (1) to (4):
  • the Symbol type corresponding to at least one Search Space associated with the CORESET is used as the given Symbol type. This assumes or requires that the Symbol types corresponding to each Search Space in the at least one associated Search Space are the same.
  • one of the methods (3.1) to (3.3) can be used:
  • the symbol type is specified by the protocol or configured by higher-level parameters.
  • the protocol specifies that the Occasion corresponding to CORESET#0 can only be located within a non-SBFD symbol.
  • the network side can either ensure that all Occasions corresponding to the CORESET are only located in the Symbol corresponding to the given Symbol type during configuration, or the network side can not ensure that any Occasion corresponding to the CORESET appears only in the Symbol corresponding to the given Symbol type during configuration, but the UE only considers it to be located in the Symbol corresponding to the given Symbol type (completely located in the Symbol corresponding to the given Symbol type, or located in the Symbol corresponding to the given Symbol type).
  • Occasions that are not within the Symbol corresponding to the given Symbol type are valid.
  • Occasions that are not within the Symbol corresponding to the given Symbol type are invalid.
  • the Occasion corresponding to the CORESET can be located in the Symbol corresponding to each (or more than one) Symbol type.
  • CORESET Occasion Configuration Method 2 means that the network side does not need to worry about or guarantee which symbol types the CORESET's corresponding Occasions are located within during configuration.
  • the CORESET's corresponding Occasions may all be located within SBFD symbols, or all within non-SBFD symbols, or some Occasions may be located within SBFD symbols and some within non-SBFD symbols.
  • the Symbol type corresponding to the Symbol where the Occasion is located is used as the Symbol type corresponding to this Occasion.
  • an available TCI state set can be further configured (for example, based on the tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList configurations in the ControlResourceSet).
  • the various TCI states contained in this available TCI state set can be selected from the configured TCI state set configured by the network side for downlink reception.
  • a TCI state can be selected from the configured TCI state set corresponding to each Symbol type (or any Symbol corresponding to the Occasion corresponding to the CORESET) as the available TCI state set for the CORESET for that Symbol type. It can be understood that for the CORESET, there is a corresponding available TCI state set for each Symbol type involved. Accordingly, corresponding configuration parameters can be introduced in the ControlResourceSet.
  • tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the ControlResourceSet are used to configure the available TCI state set corresponding to the non-SBFD symbol, and new parameters are introduced to configure the available TCI state set corresponding to the SBFD symbol.
  • the embodiments of the present application provide an illustrative example of the PDCCH TCI state indication method for CORESET Occasion.
  • PDCCH TCI state indication mode 1 For the TCI state indication corresponding to PDCCH detection within a CORESET Occasion, either PDCCH TCI state indication mode 1 or PDCCH TCI state indication mode 2 can be used:
  • PDCCH TCI state indication method 1 does not distinguish between Symbol types, and indicates that all Occasions of the CORESET use the TCI state uniformly/shared across Symbol types.
  • PDCCH TCI state indication mode 1 corresponds to general TCI state configuration mode 1 (the two modes correspond to each other and can be understood as the two modes being used together; the same understanding will be used below), and can be applied to CORESET Occasion configuration mode 1 and CORESET Occasion configuration mode 2 at the same time.
  • MAC Medium Access Control
  • CE Medium Access Control Element
  • the MAC CE here can be understood as the MAC CE with TCI state indication for UE-specific PDCCH (TCI State Indication for UE-specific PDCCH MAC CE), or a MAC CE with the same or similar functions.
  • PDCCH TCI state indication mode 1 For PDCCH TCI state indication mode 1, the existing format definition of TCI State Indication for UE-specific PDCCH MAC CE can be used. Based on the single TCI state indicated by this MAC CE for the CORESET, it can be applied to PDCCH detection within the occurrence corresponding to any symbol type of the CORESET. In other words, the CORESET is not restricted to use the indicated TCI state for PDCCH detection within the occurrence corresponding to any symbol type.
  • PDCCH TCI state indication method 2 Indicate the respective TCI states for the CORESET and the Occasion corresponding to different Symbol types.
  • PDCCH TCI state indication mode 2 corresponds to general TCI state configuration mode 2.
  • PDCCH TCI state indication mode 2 can also correspond to general TCI state configuration mode 1.
  • PDCCH TCI state indication mode 2 is mainly used in CORESET Occasion configuration mode 2, and can also be used in CORESET Occasion configuration mode 1.
  • PDCCH TCI state indication method 2-1 When using MAC CE to indicate the TCI state corresponding to each Symbol type to indicate the TCI state to be applied to the PDCCH detection within the Occasion corresponding to the CORESET and each Symbol type, either PDCCH TCI state indication method 2-1 or PDCCH TCI state indication method 2-2 can be used:
  • PDCCH TCI state indication method 2-1 Use the same MAC CE to indicate the TCI state corresponding to each (or at least one) Symbol type.
  • PDCCH TCI state indication method 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.
  • one possible implementation method is (assuming implementation method 1): adjust the existing format definition of TCI State Indication for UE-specific PDCCH MAC CE, or introduce a new MAC CE, distinguish the Symbol type in the MAC CE and set the TCI state indication field (i.e., the first indication field) corresponding to each Symbol type.
  • the TCI state indication field corresponding to a certain Symbol type indicates the TCI state corresponding to the Symbol type based on any one of (5) and (6):
  • TCI-StateId When the general TCI state configuration mode 2 is adopted, when the Index of the CORESET is 0 (that is, CORESET#0), the network side needs to ensure that the TCI state corresponding to the TCI-StateId is located in the configured 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.
  • Position in the configuration/available TCI state set can be understood as the sequence number or index 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 sequence number or index 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 sequence number or index in the configuration/available TCI state set corresponding to the Symbol type (when applied to the general TCI state configuration mode 2) (TCI state sets in these cases are required to be maintained in an ordered set).
  • the Index of the CORESET is 0 (that is, 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.
  • the TCI state indicator fields corresponding to each symbol type may be arranged sequentially in the MAC CE based on the order of the symbol types.
  • the order of the symbol types may be specified by the protocol or configured by higher-layer signaling. For example, the protocol may specify that the TCI state indicator field corresponding to the non-SBFD symbol appears first in a MAC CE, followed by the TCI state indicator field corresponding to the SBFD symbol.
  • PDCCH TCI state indication method 2-1 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.
  • Another possible implementation is to continue using the existing format definition of the TCI State Indication for UE-specific PDCCH MAC CE, or a similar format definition, and provide only a single TCI state indication field in the MAC CE to indicate a single TCI-State ID or a single position in the configured/available TCI state set.
  • N IDs or N positions are determined (assuming the number of Symbol types that need to indicate the corresponding TCI state is N).
  • a modulo operation can be further introduced to prevent ID/position overflow.
  • each of the N IDs/positions determined above is further modulo (maximum ID+1)/total number of positions to obtain the final N IDs/positions (assuming that each ID/position is numbered starting from 0).
  • PDCCH TCI state indication method 2-1 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.
  • predefined rules can be introduced to determine the symbol type corresponding to each of the N TCI states corresponding to the N IDs/positions determined using implementation method 2.
  • the predefined rules can be: the N TCI states are sorted in ascending or descending order based on TCI-StateId or position in the configured/available TCI state set, corresponding one-to-one to the order of the N symbol types based on symbol type (see the corresponding description above). For example, of two TCI states, the TCI state with the smaller TCI-StateId corresponds to the non-SBFD symbol, and the TCI state with the larger TCI-StateId corresponds to the SBFD symbol.
  • the Symbol type corresponding to each TCI state can be known.
  • the Symbol type corresponding to each TCI state can be known based on the position of each TCI state in the unified configuration/available TCI state set among the N TCI states corresponding to the N IDs/positions determined by implementation method 2.
  • implementation method 2 indicates only a single ID, it is only applicable to the situation where the ID space of TCI states corresponding to different Symbol types is allowed to overlap (that is, the ID of the TCI state in the configuration TCI state set corresponding to each Symbol type is only required to not appear repeatedly in the configuration TCI state set corresponding to the same Symbol type (that is, the ID is required to be unique within a single Symbol type), and is allowed to be repeated in the configuration TCI state sets corresponding to different Symbol types (that is, the ID space corresponding to different Symbol types is allowed to overlap)).
  • the single TCI state corresponding to this single ID is determined as the TCI state corresponding to each Symbol type.
  • implementation method 2 indicates only a single position, based on the indicated single position, a single TCI state corresponding to this single position is determined in the configured TCI state set corresponding to each Symbol type, and is used as the TCI state corresponding to each Symbol type.
  • the N IDs/positions can be mapped one by one to the order of the N Symbol types based on the Symbol type (see the corresponding description in the previous text) based on ascending or descending order. Then, based on the ID/position corresponding to each Symbol type, a single TCI state corresponding to the ID/position can be determined in the configuration TCI state set corresponding to each Symbol type as the TCI state corresponding to each Symbol type.
  • PDCCH TCI state indication method 2-2 Use an independent MAC CE to indicate the TCI state corresponding to each (or a certain) Symbol type.
  • PDCCH TCI state indication method 2-2 can be understood as a single MAC CE is only used to indicate the TCI state corresponding to a single Symbol type, and the MAC CE contains information/field used to indicate the 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):
  • 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 configured 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.
  • Position in the configuration/available TCI state set can be understood as the sequence number or index 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), 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 configuration/available TCI state set corresponding to the Symbol type (when applied to the general TCI state configuration mode 2) (TCI state sets in these cases are required to be maintained in an ordered set).
  • the Index of the CORESET is 0 (that is, 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.
  • 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.
  • Case 1 If the UE receives a MAC CE activation command indicating the applied TCI state for CORESET#0, it uses the TCI state indicated by this MAC CE activation command when performing the PDCCH reception/detection;
  • Case 2 If the UE does not receive a MAC CE activation command indicating the applied TCI state for CORESET#0 after the most recent random access procedure (it may be further required that this random access procedure is not initiated by a PDCCH command used to trigger a contention-free random access procedure), the QCL assumption corresponding to the SSB identified by the UE in this most recent random access procedure is used.
  • Case 1 is considered to be satisfied as long as the UE receives any one or more MAC CE activation commands indicating the TCI state of the application for CORESET#0.
  • Case 1 is considered to be met only when the UE receives at least one MAC CE activation command for a given Symbol type and indicating the applied TCI state for CORESET#0 (for example, when PDCCH TCI state indication mode 2-1 is adopted and a MAC CE is received, and the MAC CE indicates the TCI state corresponding to the given Symbol type, or when PDCCH TCI state indication mode 2-2 is adopted and a MAC CE is received for the given Symbol type).
  • the UE may use the QCL hypothesis corresponding to the SSB identified in the most recent random access procedure (it may be further required that this random access procedure is not initiated by a PDCCH command used to trigger a contention-free random access procedure), or the QCL hypothesis corresponding to the SSB identified by the UE in the initial access procedure, or a predefined QCL hypothesis/TCI state (which may be specified by the protocol or configured by higher-layer signaling);
  • any random access procedure (which may further require that the random access procedure is not initiated by a PDCCH command used to trigger a contention-free random access procedure) satisfies the judgment of “the most recent random access procedure (which may further require that the random access procedure is not initiated by a PDCCH command used to trigger a contention-free random access procedure)” (i.e., matches the “random access procedure (which may further require that the random access procedure is not initiated by a PDCCH command used to trigger a contention-free random access procedure)” in this judgment);
  • the random access process corresponding to the given Symbol type (it may be further required that the random access process is not initiated by the PDCCH command used to trigger the contention-free random access process) satisfies the judgment of "the most recent random access process (it may be further required that this random access process is not initiated by the PDCCH command used to trigger the contention-free random access process)" (i.e., it matches the "random access process (it may be further required that this random access process is not initiated by the PDCCH command used to trigger the contention-free random access process)" in this judgment).
  • the "random access process corresponding to a given Symbol type” can be understood as the random access process initiated based on the SSB selection based on the SSB transmission attributes corresponding to the given Symbol type, and/or the RO resources corresponding to the given Symbol type (generally, there is a corresponding SSB to RO mapping for a given Symbol type).
  • the following describes relevant implementation methods of PDSCH reception by taking the first downlink reception including PDSCH as an example.
  • the first downlink reception includes a PDSCH
  • the method further comprises:
  • the terminal receives third information from the network-side device, where the third information is used to indicate at least one of the following:
  • the time domain units corresponding to each time domain type respectively have corresponding activation transmission parameters, where N is an integer greater than or equal to 1.
  • activation transmission parameters corresponding to time domain units corresponding to respective time domain types are indicated by the same MAC CE; or,
  • the activation transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs.
  • the activation transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs. It can be understood that independent MAC CEs are used to respectively indicate the activation transmission parameters corresponding to the time domain units corresponding to each time domain type.
  • the MAC CE when indicating, through the same MAC CE, activation transmission parameters corresponding to time domain units corresponding to respective time domain types in N time domain types corresponding to the first downlink reception, includes at least one of the following:
  • N sixth indication fields where the N sixth indication fields are used to respectively indicate activation transmission parameters corresponding to each of the N time domain types
  • a seventh indication field wherein the seventh indication field is used to jointly indicate the activation transmission parameters corresponding to each time domain type in the N time domain types.
  • the MAC CE when different MAC CEs are used to indicate, among the N time domain types of the first downlink reception, activation transmission parameters corresponding to time domain units corresponding to respective time domain types, the MAC CE includes at least one of the following:
  • An eighth indication field is used to indicate the time domain type corresponding to the MAC CE
  • the ninth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the terminal determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including at least one of the following:
  • the terminal selects, from the transmission parameters indicated by the third information, a transmission parameter having the 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;
  • the terminal determines the transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameters corresponding to the first downlink reception;
  • the terminal determines the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • the terminal determines the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • the terminal selects, from the transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter having the 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;
  • the terminal determines the default transmission parameter corresponding to the first time domain type as the transmission parameter corresponding to the first downlink reception;
  • the terminal determines the initial transmission parameters corresponding to the first time domain type as transmission parameters corresponding to the first downlink reception.
  • the embodiments of the present application provide an illustrative example of the TCI state activation/deactivation method corresponding to PDSCH reception.
  • PDSCH TCI state activation mode 1 To activate/deactivate the TCI state corresponding to PDSCH reception, either PDSCH TCI state activation mode 1 or PDSCH TCI state activation mode 2 can be used:
  • PDSCH TCI state activation method 1 determine the activated (Activated) TCI states for unified use/shared use across Symbol types (Activated TCI states can be understood as one or more activated TCI states, or at least one activated TCI state; the following will follow the understanding here and will not be repeated).
  • PDSCH TCI state activation mode 1 can correspond to general TCI state configuration mode 1.
  • a MAC CE that is independent of the Symbol type (or does not consider the influence of the Symbol type) can be used to activate/deactivate each TCI state in a unified configured TCI state set to determine the activated TCI states that are used uniformly or shared across Symbol types.
  • the MAC CE here can be understood as the MAC CE for activating/deactivating the TCI states for the PDSCH of a specific UE (TCI States Activation/Deactivation for UE-specific PDSCH MAC CE), or a MAC CE with the same or similar functionality.
  • the existing format definition of the MAC CE for activating/deactivating the PDSCH TCI state for a specific UE can be used.
  • a TCI state from the Activated TCI states determined based on this MAC CE can be applied to PDSCH reception corresponding to any symbol type. In other words, there is no restriction on the symbol type corresponding to PDSCH reception to which any TCI state from the Activated TCI states can be applied.
  • PDSCH TCI state activation method 2 Determine the activated TCI states for different symbol types.
  • PDSCH TCI state activation mode 2 corresponds to general TCI state configuration mode 2.
  • PDSCH TCI state activation mode 2 can also correspond to general TCI state configuration mode 1.
  • PDSCH TCI state activation method 2-1 When using MAC CE to activate/deactivate the TCI state corresponding to each Symbol type to determine the activated TCI states corresponding to each Symbol type, either PDSCH TCI state activation method 2-1 or PDSCH TCI state activation method 2-2 can be used:
  • PDSCH TCI state activation method 2-1 Use the same MAC CE to activate/deactivate the TCI state corresponding to each (or at least one) Symbol type.
  • PDSCH TCI state activation method 2-1 can be understood as a single MAC CE can be used to activate/deactivate the TCI state corresponding to more than one symbol type. Specifically, any of PDSCH TCI state activation methods 2-1-1 to 2-1-3 can be used:
  • PDSCH TCI state activation method 2-1-1 When 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 used. Each TCI state activation/deactivation status indication bit in the MAC CE corresponds to a configured TCI state based on TCI-StateId.
  • PDSCH TCI state activation mode 2-1-1 can be applied to general TCI state configuration mode 2-1, general TCI state configuration mode 2-2 and general TCI state configuration mode 2-3.
  • PDSCH TCI state activation method 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.
  • the TCI state activation/deactivation status indication bit in the MAC CE is set separately without explicitly distinguishing the Symbol type.
  • Each TCI state activation/deactivation status indication bit corresponds to a certain configured TCI state based on its position in a unified configured TCI state set.
  • the position in the unified configuration TCI state set can be understood as the serial number or subscript of each TCI state in the unified configuration TCI state set in the set (which is required to be maintained in the form of an ordered set).
  • PDSCH TCI state activation mode 2-1-2 can be applied to general TCI state configuration mode 2-1 and general TCI state configuration mode 2-2.
  • PDSCH TCI state activation method 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 to distinguish the Symbol type in the MAC CE and set the TCI state activation/deactivation status indication bit corresponding to each Symbol type.
  • each bit can correspond to a TCI state applicable to the Symbol type based on any of (9) and (10):
  • the TCI state activation/deactivation status indication bits corresponding to each symbol type may be arranged sequentially in the MAC CE based on the order of the symbol types.
  • the order of the symbol types may be specified by the protocol or configured by higher-layer signaling.
  • the protocol may specify that in a MAC CE, the TCI state activation/deactivation status indication bits corresponding to the non-SBFD symbol appear first, followed by the TCI state activation/deactivation status indication bits corresponding to the SBFD symbol.
  • PDSCH TCI state activation mode 2-1-3 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. The relevant operations are described as follows:
  • the first bit in the corresponding TCI state activation/deactivation status indication bits (referred to as the first bit sequence) may correspond to a TCI-StateId value of 0, and the remaining bits in the first bit sequence may correspond to other TCI-StateId values in sequence (i.e., the second bit in the first bit sequence corresponds to a TCI-StateId value of 1, and so on).
  • the first bit in the first bit sequence can correspond to the minimum TCI-StateId in the TCI-StateId value range corresponding to the Symbol type (which can be called the first ID range), and the remaining bits in the first bit sequence can correspond one-to-one with the remaining TCI-StateId in the first ID range (correspondingly, the length of the first bit sequence is the number of TCI-StateIds contained in the first ID range);
  • the minimum TCI-StateId in the configured TCI state set corresponding to the Symbol type (which can be called the first TCI state set) can correspond to the first bit in the first bit sequence, and the remaining TCI states in the first TCI state set can correspond one-to-one with the remaining bits
  • the first bit of its corresponding TCI state activation/deactivation status indication bits may correspond to the first TCI state in the unified configured TCI state set (when applied to general TCI state configuration mode 1), or to the first TCI state in the configured TCI state set corresponding to the symbol type (when applied to general TCI state configuration mode 2).
  • the remaining bits in the second bit sequence correspond to the remaining TCI states in the set (i.e., the second bit in the second bit sequence corresponds to the next TCI state in the set, and so on; it is assumed here that the unified configured TCI state set or the configured TCI state sets corresponding to each symbol type are ordered sets).
  • the length of the second 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.
  • PDSCH TCI state activation method 2-2 Use independent MAC CE to activate/deactivate the TCI state corresponding to each (or a certain) Symbol type.
  • 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 the MAC CE contains information/field for indicating the Symbol type.
  • each TCI state activation/deactivation status indication bit in the MAC CE can correspond to a TCI state based on any of (11) and (12):
  • PDSCH TCI state activation mode 2-2 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. The relevant operations are described as follows:
  • the first bit of the TCI state activation/deactivation status indication bits (referred to as the third bit sequence) in the MAC CE may correspond to a TCI-StateId value of 0, and the remaining bits in the third bit sequence may correspond to other TCI-StateId values in sequence (i.e., the second bit in the third bit sequence corresponds to a TCI-StateId value of 1, and so on).
  • the first bit in the third bit sequence can correspond to the minimum TCI-StateId in the TCI-StateId value range corresponding to the Symbol type (which can be called the second ID range), and the remaining bits in the third bit sequence can correspond one by one to the remaining TCI-StateId in the second ID range (correspondingly, the length of the third bit sequence is the number of TCI-StateIds contained in the second ID range);
  • the Symbol type is distinguished based on the new parameter of TCI state
  • the minimum TCI-StateId in the configured TCI state set corresponding to the Symbol type (which can be called the second TCI state set) can correspond to the first bit in the third bit sequence
  • the remaining TCI states in the second TCI state set can correspond one by one to the remaining bits in the third bit sequence based on the order of
  • the first bit of the TCI state activation/deactivation status indication bits (referred to as the fourth bit sequence) in the MAC CE may correspond to the first TCI state in the unified configured TCI state set (when applied to general TCI state configuration mode 1) or the configured TCI state set corresponding to the symbol type (when applied to general TCI state configuration mode 2).
  • the remaining bits in the fourth bit sequence correspond to the remaining TCI states in the set (i.e., the second bit in the fourth bit sequence corresponds to the next TCI state in the set, and so on; it is assumed here that the unified configured TCI state set or the configured TCI state sets corresponding to each symbol type are ordered sets).
  • 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.
  • the QCL assumption/TCI state applied to a PDSCH reception application includes at least one of (a) to (d):
  • the situation where the indicated TCI state is applied may include the situation where a TCI indication field exists 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 predefined threshold (for example, indicated by the parameter timeDurationForQCL).
  • a predefined threshold for example, indicated by the parameter timeDurationForQCL.
  • PDSCH reception corresponding to any symbol type shares a unified set of configured TCI states and a single set of Activated TCI states.
  • a typical situation where the TCI state indicated in the scheduling DCI applies includes: a PDSCH is scheduled by a DCI with 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 capabilities), regardless of the symbol type (or within which the PDSCH is received), the relevant indication field (e.g., the TCI indication field) in the scheduling DCI always indicates the TCI state(s) applied for this PDSCH reception from the set of Activated TCI states.
  • each Symbol type can correspond to its own configured TCI state set and its own activated TCI states.
  • the relevant indication field in the scheduling DCI indicates the TCI state(s) applied for this 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) in which the PDSCH is received).
  • the situation where the QCL assumption/TCI state of PDCCH is applied may include the situation 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 predefined threshold (for example, indicated by the parameter timeDurationForQCL).
  • a predefined threshold for example, indicated by the parameter timeDurationForQCL.
  • the TCI state of CORESET does not need to distinguish the Symbol type.
  • the operations defined in the relevant specifications i.e., operation 0 below can be used.
  • the network side ensures that the symbol type of the PDSCH received is the same as that of the corresponding PDCCH. Accordingly, the UE can continue to use the operation defined in the relevant specifications (i.e., operation 0 below).
  • Operation 0 may 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.
  • the TCI state or QCL assumption of the CORESET applied to the corresponding PDCCH reception mentioned above is the QCL assumption/TCI state applied by the CORESET within the Symbol where the PDCCH reception corresponding to the PDSCH is located.
  • Operation 1 PDSCH reception applies the default QCL assumption corresponding to the first Symbol type, or applies a predefined TCI state.
  • the predefined TCI state can be specified by the protocol or configured by high-level signaling; it can be determined separately by Symbol type, or uniformly determined without distinguishing Symbol type.
  • Operation 2 PDSCH receives the CORESET corresponding to the PDCCH corresponding to the application and the TCI state corresponding to the first Symbol type.
  • Operation 2 can be understood as follows: if a 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 the 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; the target QCL assumption/TCI state here is the QCL assumption/TCI state corresponding to the first Symbol type in the QCL assumption/TCI state applied by the CORESET for receiving the PDCCH carrying the DCI.
  • this predefined threshold is determined based on the reported UE capability
  • the target QCL hypothesis/TCI state mentioned above is the QCL hypothesis/TCI state corresponding to the first Symbol type within the Symbol where the PDSCH is received by the CORESET.
  • the situation where the initial QCL assumption is applied may include the situation where 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 predefined threshold (for example, indicated by the parameter timeDurationForQCL).
  • a predefined threshold for example, indicated by the parameter timeDurationForQCL.
  • the operations defined in the relevant specifications can be used (that is, the scheduled PDSCH and the SSB quasi-co-location determined by the UE during the initial access process).
  • the UE may assume that the DM-RS port of the PDSCH is quasi-co-located with the SSB corresponding to the given Symbol type determined during the initial access procedure, and the quasi-co-location type (QCL Type, which may correspond to the parameter qcl-Type) is type A ('typeA'), and if available, the quasi-co-location type is also type D ('typeD').
  • QCL Type which may correspond to the parameter qcl-Type
  • the quasi-co-location type is also type D ('typeD').
  • the TCI state of CORESET does not need to distinguish the Symbol type.
  • the operations defined in the relevant specifications can be used.
  • the UE determines the default QCL assumption corresponding to the first Symbol type on the serving cell where the PDSCH reception is applied (the default QCL assumption corresponding to the first Symbol type on the serving cell where the PDSCH reception is applied is: the RS involved/corresponding to the QCL parameters used for PDCCH QCL indication by the target CORESET in the target time slot is quasi-co-located; the target time slot here is the latest time slot corresponding to the first Symbol type that the UE needs to monitor one or more CORESETs within the activated BWP of the serving cell where the PDSCH is received; the target CORESET here is, among the one or more CORESETs to be monitored in the target time slot, the CORESET with the smallest controlResourceSetId that
  • the network device In RRC connected mode, regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 (or, independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2), if the network device does not provide dl-OrJointTCI-StateList-r17 to the UE, and the time offset between the reception of the DCI and the corresponding PDSCH is less than the predefined threshold timeDurationForQCL, and the network device has configured at least one TCI state with qcl-Type set to 'typeD' for the serving cell where the scheduled PDSCH is located, the UE performs at least one of the following (e) and (f):
  • the UE may assume that the DM-RS port of the PDSCH is quasi-co-located with the RS involved in/corresponding to the QCL parameters indicated by the PDCCH QCL of the target CORESET in the target time slot, where the target time slot is the latest time slot in which the UE needs to monitor one or more CORESETs within the activated BWP of the serving cell where the PDSCH is located and the Symbol type corresponding to the PDSCH, and the target CORESET is the CORESET with the smallest controlResourceSetId that is associated with the search space to be monitored among the one or more CORESETs to be monitored in the target time slot.
  • the UE may assume that the DM-RS port of the PDSCH associated with a certain coresetPoolIndex value (i.e., the CORESET where the PDCCH that schedules the PDSCH is received is associated with the coresetPoolIndex value) is the same as the target CO in the target timeslot.
  • a certain coresetPoolIndex value i.e., the CORESET where the PDCCH that schedules the PDSCH is received is associated with the coresetPoolIndex value
  • RESET is used for the QCL parameters indicated by PDCCH QCL involving/corresponding to RS quasi-co-location, where the target time slot is the latest time slot in which the UE needs to monitor one or more CORESETs associated with the coresetPoolIndex value within the activated BWP of the serving cell where the PDSCH is located, and the target CORESET is one or more CORESETs that need to be monitored within the target time slot and are associated with the coresetPoolIndex value, and is associated with the search space that needs to be monitored and has the smallest controlResourceSetId.
  • the following describes the relevant implementation methods of receiving 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.
  • the first downlink reception includes a CSI-RS corresponding to a first NZP CSI-RS resource
  • the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located corresponds to the same time domain type, or the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located can correspond to multiple time domain types or all time domain types.
  • the method further includes:
  • the terminal receives fourth information from the network-side device, where the fourth information is used to indicate at least one of the following:
  • the receiving moments corresponding to each time domain type have their own corresponding transmission parameters, and S is an integer greater than or equal to 1.
  • the terminal determining, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception includes:
  • the terminal determines the default transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.
  • the embodiments of the present application provide an illustrative example of the TCI state configuration and determination method corresponding to NZP CSI-RS reception.
  • NZP CSI-RS is typically configured and used at the granularity of NZP CSI-RS resources.
  • NZP CSI-RS resources can be further categorized as periodic, semi-persistent, and aperiodic. In many application scenarios, NZP CSI-RS resources are further organized into NZP CSI-RS resource sets (including trigger transmission and reference).
  • CSI-RS Occasion Configuration Mode 1 For a Periodic or Semi-persistent NZP CSI-RS resource, multiple Occasions (or at least one Occasion) can be mapped to it in the time domain. Accordingly, for the configuration of the time-frequency position of a Periodic/Semi-persistent NZP CSI-RS resource, either CSI-RS Occasion Configuration Mode 1 or CSI-RS Occasion Configuration Mode 2 can be used:
  • the Occasion corresponding to the NZP CSI-RS resource can only be located in the Symbol corresponding to a single Symbol type.
  • a single Symbol type (given Symbol type) can be determined using any of (g) to (j):
  • the NZP-CSI-RS-ResourceId of the NZP CSI-RS resource must be within the NZP-CSI-RS-ResourceId value range corresponding to the Symbol type.
  • the symbol type is specified by the protocol or configured by higher-layer parameters.
  • the protocol specifies that the Occasion corresponding to the NZP CSI-RS resource can only be located within a non-SBFD symbol.
  • the network side can either ensure that all Occasions corresponding to the NZP CSI-RS resource are only located in the Symbol corresponding to the given Symbol type during configuration/activation, or the network side can not ensure that any Occasion corresponding to the NZP CSI-RS resource appears only in the Symbol corresponding to the given Symbol type during configuration, but the UE only considers it to be in the Symbol corresponding to the given Symbol type (completely in the Symbol corresponding to the given Symbol type, or in the Symbol type).
  • Occasions that are not within the Symbol corresponding to the given Symbol type are valid.
  • Occasions that are not within the Symbol corresponding to the given Symbol type are invalid.
  • the Occasion corresponding to the NZP CSI-RS resource can be located in the Symbol corresponding to each (or more than one) Symbol type.
  • the network side does not need to worry about or guarantee which symbol types the occurrences corresponding to the NZP CSI-RS resource fall within during configuration.
  • the occurrences corresponding to the NZP CSI-RS resource may all fall within SBFD symbols, or all fall within non-SBFD symbols, or some may fall within SBFD symbols and some within non-SBFD symbols.
  • the Symbol type corresponding to the Symbol where the Occasion is located is used as the Symbol type corresponding to the Occasion.
  • the TCI state is configured independently for each NZP CSI-RS resource.
  • the TCI state is indicated for each Semi-persistent NZP CSI-RS resource in this set.
  • CSI-RS TCI state determination method 1 when configuring/indicating the TCI state for a Periodic/Semi-persistent NZP CSI-RS resource (which can be understood as configuring the TCI state for this Periodic NZP CSI-RS resource through higher-layer signaling, or indicating the TCI state for this Semi-persistent NZP CSI-RS resource through MAC CE), either CSI-RS TCI state determination method 1 or CSI-RS TCI state determination method 2 can be used:
  • CSI-RS TCI state determination method 1 Regardless of the Symbol type, configure/indicate the TCI state used uniformly by all Occasions of the NZP CSI-RS resource/shared across Symbol types.
  • CSI-RS TCI state determination method 1 corresponds to general TCI state configuration method 1, and can be applied to both CSI-RS Occasion configuration method 1 and CSI-RS Occasion configuration method 2.
  • CSI-RS TCI state determination method 1 for Periodic NZP CSI-RS resource, it can be configured as NZP-CSI-RS-Resource->qcl-InfoPeriodicCSI-RS ("->" is used here to represent a 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 explanation here); for Semi-persistent NZP CSI-RS resource, the indication field in MAC CE can be used, such as TCI State IDi.
  • the single TCI state configured for this Periodic NZP CSI-RS resource based on the existing configuration parameters, or indicated for this Semi-persistent NZP CSI-RS resource based on the MAC CE indication field, can be applied to the Occasion corresponding to the NZP CSI-RS resource and any Symbol type. In other words, there is no restriction on the Symbol type corresponding to the Occasion of the TCI state configured for the NZP CSI-RS resource.
  • CSI-RS TCI state determination method 2 Configure/indicate the respective TCI states for the NZP CSI-RS resource and the Occasion corresponding to different Symbol types.
  • CSI-RS TCI state determination mode 2 corresponds to general TCI state configuration mode 2.
  • CSI-RS TCI state determination mode 2 can also correspond to general TCI state configuration mode 1.
  • CSI-RS TCI state determination mode 2 is mainly applied to CSI-RS Occasion configuration mode 2, and can also be applied to CSI-RS Occasion configuration mode 1.
  • the network side needs to ensure that the TCI state configured/indicated for a certain Symbol type is located in the configured TCI state set corresponding to the Symbol type.
  • the TCI state is independently configured for each Aperiodic NZP CSI-RS resource used for Channel measurement in the configuration information for each trigger state (e.g., the corresponding configuration parameter CSI-AperiodicTriggerState).
  • the TCI state configuration method 1 when configuring the TCI state for an Aperiodic NZP CSI-RS resource, either CSI-RS TCI state configuration method 1 or CSI-RS TCI state configuration method 2 can be used:
  • CSI-RS TCI state configuration method 1 Regardless of the Symbol type, configure the TCI state used by the NZP CSI-RS resource.
  • CSI-RS TCI state configuration mode 1 corresponds to general TCI state configuration mode 1.
  • CSI-RS TCI state configuration method 1 you can use CSI-AssociatedReportConfigInfo->resourcesForChannel->nzp-CSI-RS->qcl-info.
  • the single TCI state configured for the Aperiodic NZP CSI-RS resource is applied to the single Occasion triggered by the NZP CSI-RS resource (which can correspond to any Symbol type).
  • CSI-RS TCI state configuration method 2 Configure separate TCI states for the NZP CSI-RS resource and the Occasion corresponding to different Symbol types.
  • CSI-RS TCI state configuration mode 2 corresponds to general TCI state configuration mode 2.
  • CSI-RS TCI state configuration mode 2 can also correspond to general TCI state configuration mode 1.
  • the corresponding TCI state is used.
  • the corresponding TCI state is configured only for the Symbol type corresponding to the Occasion in which the NZP CSI-RS resource is expected to be triggered (when multiple Symbol types are expected based on possible triggering scenarios, the corresponding TCI state is configured for each Symbol type separately).
  • the network side needs to ensure that the TCI state configured/indicated for a certain Symbol type is located in the configured TCI state set corresponding to the Symbol type.
  • the TCI state of Aperiodic NZP CSI-RS does not need to distinguish the Symbol type.
  • the operations defined in the relevant specifications can be used; when the general TCI state configuration mode 2 and CSI-RS TCI state configuration mode 2 are adopted, it is necessary to distinguish the Symbol type to determine the TCI state applicable to Aperiodic NZP CSI-RS.
  • the UE determines the default QCL assumption corresponding to the first Symbol type on the serving cell where the Aperiodic NZP CSI-RS reception is applied (the default QCL assumption corresponding to the first Symbol type on the serving cell where the Aperiodic NZP CSI-RS is received is: the QCL assumption used by the target CORESET in the target time slot; the target time slot here is the latest time slot corresponding to the first Symbol type in which the UE needs to monitor one or more CORESETs within the activated BWP of the serving cell where the Aperiodic NZP CSI-RS is received; the target CORESET here is, among the one or more CORESETs to be monitored in the target time slot, the CORESET that is associated with the search space to be monitored and has the smallest controlResourceSetId).
  • the specific operations include:
  • the scheduling offset between the last Symbol of the PDCCH that carries the DCI triggering the Aperiodic NZP CSI-RS reception and the first Symbol of the non-periodic CSI-RS resource in the NZP CSI-RS resource set i.e., NZP-CSI-RS-ResourceSet; it may be further required that the high-level parameter trs-Info is not configured for the NZP-CSI-RS-ResourceSet) corresponding to the Aperiodic NZP CSI-RS reception is less than the target threshold, the following operations are performed: If the network side device does not provide the UE with dl-OrJointTCI-StateList, and the Aperiodic NZP CSI-RS reception is not ...
  • 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 time slot.
  • the target time slot is the latest time slot in which the UE needs to monitor one or more CORESETs in the activated BWP of the serving cell where the Aperiodic NZP CSI-RS is received, and corresponds to the first Symbol type.
  • the target CORESET is the CORESET with the smallest controlResourceSetId and the associated search space to be monitored among the one or more CORESETs to be monitored in the target time slot.
  • the target thresholds mentioned above can be specified by the protocol or configured by high-level signaling.
  • the target threshold is one of the values and the network-side device does not provide the enableBeamSwitchTiming function to the UE, the target threshold is the threshold value beamSwitchTiming reported by the UE;
  • the target threshold is
  • the target threshold is the threshold value beamSwitchTiming-r16 reported by the UE.
  • the following describes relevant implementation methods corresponding to the CSI measurement by taking the first measurement including the CSI measurement as an example.
  • the first measurement comprises a CSI measurement
  • the method further comprises:
  • the terminal determines a target CSI reference resource corresponding to a target CSI report
  • the terminal performs at least one of the following operations:
  • the target CSI report is a periodic or semi-continuous CSI report, determining a start time of CPU occupation based on the latest target CSI-RS reception timing;
  • the target information includes at least one of a layer 1 reference signal received power (RSRP), a layer 1 signal-to-noise and interference ratio (SINR), and a channel quality indicator (CQI);
  • RSRP layer 1 reference signal received power
  • SINR layer 1 signal-to-noise and interference ratio
  • CQI channel quality indicator
  • the target CSI report corresponds to the second time domain type; the target CSI-RS reception timing corresponds to the second time domain type, and the target CSI-RS reception timing is no later than the target CSI reference resource.
  • the embodiments of the present application provide an illustrative description of operations related to CSI reporting corresponding to CSI measurement.
  • the UE 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 receives at least one CSI-RS transmission opportunity for channel measurement corresponding to the given Symbol type and no later than the CSI reference resource, as well as CSI-RS and/or CSI interference measurement (CSI Interference Measurement, CSI-IM) opportunity for interference measurement; otherwise, the CSI report will be discarded.
  • CSI Interference Measurement CSI Interference Measurement
  • the UE When discontinuous reception (DRX) is configured, the UE reports a CSI report corresponding to the given Symbol type only if it receives at least one CSI-RS transmission opportunity for channel measurement and CSI-RS and/or CSI-IM opportunity for interference measurement corresponding to the given Symbol type and no later than the CSI reference resource within the DRX activation time; otherwise, the CSI report is discarded.
  • DRX discontinuous reception
  • CPU occupancy starts at the first symbol of the earliest occurrence of the latest CSI-RS/CSI-IM/SSB timing of each CSI-RS/CSI-IM/SSB resource used for channel or interference measurement corresponding to the given Symbol type, and no later than the first symbol of the earliest occurrence of the latest CSI-RS/CSI-IM/SSB timing of the corresponding CSI reference resource.
  • (m) determining CSI parameters specifically, including at least one of (m1) to (m3):
  • the UE derives the channel measurement value used to calculate the L1-RSRP value reported in uplink timeslot n based on the following occasions:
  • any one or more timings (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to "notConfigured").
  • the UE derives the channel measurement value corresponding to the L1-SINR reported in uplink timeslot n based on the following occasions:
  • the UE derives the interference measurement value corresponding to the L1-SINR reported in uplink timeslot n based on the following occasions:
  • the timing corresponding to the CSI-IM associated with the CSI resource setting, or the NZP CSI-RS resource used for interference measurement, or the NZP CSI-RS resource used for both channel and interference measurement the timing corresponding to the given Symbol type and no later than the timing of the CSI reference resource:
  • any one or more timings (if timeRestrictionForInterferenceMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to 'notConfigured').
  • the UE derives the channel measurement value used to calculate the CSI value reported in uplink timeslot n based on the following occasions:
  • any one or more timings (if timeRestrictionForChannelMeasurements in the CSI-ReportConfig corresponding to the CSI report is set to "notConfigured").
  • the UE derives the interference measurement value used to calculate the CSI value reported in uplink timeslot n based on the following occasions:
  • the following takes the first measurement including the CLI measurement as an example to illustrate relevant implementation methods corresponding to the CLI measurement.
  • the first measurement comprises a CLI measurement
  • a transmission parameter corresponding to the CLI measurement resource includes at least one of the following:
  • the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET In the time domain unit corresponding to the second time domain type, the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET;
  • the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET corresponding to the second time domain type are the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET corresponding to the second time domain type.
  • the transmission parameter corresponding to the CLI measurement resource includes a QCL assumption
  • the type of the QCL assumption includes type D.
  • CLI is measured only for the SBFD symbol (for example, inter-UE inter-subband CLI can be measured within the SBFD symbol), or CLI can be measured separately for the SBFD symbol and non-SBFD symbol (for example, adjacent channel or co-channel CLI can be measured for dynamic TDD within the non-SBFD symbol, etc.).
  • the UE may assume that the CLI measurement resources (including SRS resources, CLI-RSSI resources, etc.) configured in the given Symbol are consistent with one of the following QCLs (i.e., apply the corresponding QCL assumption/TCI state):
  • the type of the QCL is Type D.
  • the above assumption is only for CLI measurement in FR2.
  • the embodiments of this application provide various feasible methods for determining the QCL hypothesis/TCI state corresponding to the downlink channel/signal or measurement channel/signal (including configuration, activation, and indication), as well as corresponding UE behaviors. This allows for adapting to different SBFD deployment scenarios and enabling flexible and efficient SBFD operation. This demonstrates that the embodiments of this application enable downlink reception or measurement by a terminal in flexible duplex scenarios.
  • FIG4 shows a flow chart of a downlink receiving and measuring method provided by an embodiment of the present application. As shown in FIG4 , the downlink receiving and measuring method includes:
  • Step 401 The network-side device determines, based on a first time domain type corresponding to a first downlink reception, a transmission parameter corresponding to the first downlink reception, and performs transmission corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or
  • the network-side device receives a measurement report corresponding to the first measurement based on the second time domain type corresponding to the first measurement;
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • the first downlink reception includes at least one of SSB, PDCCH and CSI-RS;
  • the time domain units where the first downlink reception is performed correspond to the same time domain type; or,
  • the first downlink reception includes SSB
  • the network side device determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including at least one of the following:
  • 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 parameters corresponding to the first downlink reception as the first transmission parameters;
  • 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 parameters corresponding to the first downlink reception in time domain units of different time domain types based on the mapping relationship between the time domain type and the transmission parameters.
  • the method further comprises:
  • the network side device sends first information to the terminal, where 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 network-side device determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including:
  • the network-side device determines, based on the 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.
  • the at least one set includes at least one of the following:
  • any transmission parameter in the first set can be used for any time domain type
  • the time domain type corresponding to each transmission parameter in the at least one second set is determined by configuration information of the transmission parameter
  • At least one fourth set all transmission parameters in each of the fourth sets correspond to the same time domain type, and different fourth sets correspond to different time domain types.
  • a first indication of a transmission parameter where 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.
  • the third set includes one or more subsets, and each subset of the third set satisfies at least one of the following:
  • the subsets of the third set are sorted according to a predetermined order, where the predetermined order represents the order of the time domain types;
  • 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.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the time domain units where the reception opportunities of the first CORESET are located correspond to the same time domain type; or,
  • the time domain unit where the reception opportunity of the first CORESET is located can correspond to multiple time domain types or all time domain types.
  • the time domain type corresponding to the time domain unit where the reception timing of the first CORESET is located is determined by at least one of the following:
  • the configuration information of the first CORESET includes at least one of the following:
  • an identifier of the first CORESET wherein a value of the identifier of the first CORESET is used to determine a time domain type corresponding to a time domain unit where a reception opportunity of the first CORESET is located;
  • the second indication of the first CORESET is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of the first CORESET is located is the time domain type indicated by the second indication.
  • the configuration information of each search space includes at least one of the following:
  • the identifiers of the search spaces where the values of the identifiers of the search spaces are used to respectively determine the time domain types corresponding to the time domain units where the reception opportunities of the search spaces are located;
  • the third indication of each search space is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of each search space is located is the time domain type indicated by the third indication of each search space.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the method further comprises:
  • the network-side device sends second information to the terminal, where the second information is used to indicate at least one of the following:
  • the receiving opportunities corresponding to each time domain type respectively correspond to transmission parameters, where M is an integer greater than or equal to 1.
  • the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types are indicated by the same MAC CE; or,
  • the transmission parameters corresponding to the receiving moments corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE includes at least one of the following:
  • M first indication fields the M first indication fields being used to respectively indicate transmission parameters corresponding to receiving opportunities corresponding to respective time domain types in the M time domain types;
  • the second indication field is used to jointly indicate the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types in the M time domain types.
  • the MAC CE when different MAC CEs are used to indicate transmission parameters corresponding to reception opportunities corresponding to respective time domain types in the M time domain types corresponding to the first CORESET, the MAC CE includes at least one of the following:
  • the third indication field is used to indicate the time domain type corresponding to the MAC CE
  • the fourth indication field is used to indicate the transmission parameters corresponding to the corresponding time domain type
  • the fifth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the first downlink reception includes PDSCH
  • the method further comprises:
  • the network-side device sends third information to the terminal, where the third information is used to indicate at least one of the following:
  • the time domain units corresponding to each time domain type respectively have corresponding activation transmission parameters, where N is an integer greater than or equal to 1.
  • activation transmission parameters corresponding to time domain units corresponding to respective time domain types are indicated by the same MAC CE; or,
  • the activation transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE when indicating, through the same MAC CE, activation transmission parameters corresponding to time domain units corresponding to respective time domain types in N time domain types corresponding to the first downlink reception, includes at least one of the following:
  • N sixth indication fields where the N sixth indication fields are used to respectively indicate activation transmission parameters corresponding to each of the N time domain types
  • a seventh indication field wherein the seventh indication field is used to jointly indicate the activation transmission parameters corresponding to each time domain type in the N time domain types.
  • the MAC CE when different MAC CEs are used to indicate, among the N time domain types of the first downlink reception, activation transmission parameters corresponding to time domain units corresponding to respective time domain types, the MAC CE includes at least one of the following:
  • An eighth indication field is used to indicate the time domain type corresponding to the MAC CE
  • the ninth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the network-side device determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including at least one of the following:
  • the network-side device selects, from the transmission parameters indicated by the third information, a transmission parameter having the 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;
  • 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;
  • the network side device determines the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • the network side device determines the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • the network side device selects, from the transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter having the 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;
  • the network side device determines the default transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • the network-side device determines the initial transmission parameters corresponding to the first time domain type as transmission parameters corresponding to the first downlink reception.
  • the first downlink reception includes a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource;
  • the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located corresponds to the same time domain type, or the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located can correspond to multiple time domain types or all time domain types.
  • the method further includes:
  • the network side device sends fourth information to the terminal, where the fourth information is used to indicate at least one of the following:
  • the receiving moments corresponding to each time domain type have their own corresponding transmission parameters, and S is an integer greater than or equal to 1.
  • the network-side device determines, based on the first time domain type corresponding to the first downlink reception, a transmission parameter corresponding to the first downlink reception, including:
  • the network side device determines the default transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.
  • the downlink receiving and measuring method provided in the embodiment of the present application can be executed by a downlink receiving and measuring device.
  • the downlink receiving and measuring device performing the downlink receiving and measuring method is used as an example to illustrate the downlink receiving and measuring device provided in the embodiment of the present application.
  • an embodiment of the present application further provides a downlink receiving and measuring device.
  • the downlink receiving and measuring device 500 includes:
  • the first processing unit 501 is 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 reception corresponding to the first downlink reception according to the transmission parameter corresponding to the first downlink reception; or
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • the first downlink reception includes at least one of SSB, PDCCH and CSI-RS;
  • the time domain units where the first downlink reception is performed correspond 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.
  • the first downlink reception includes SSB
  • the first processing unit is specifically configured to do at least one of the following:
  • the first downlink reception includes at least one of PDSCH, PDCCH and CSI-RS;
  • the device further comprises:
  • a first receiving unit configured to receive first information from a network-side device, where 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 first processing unit is specifically configured to:
  • a transmission parameter corresponding to the first downlink reception is determined from the at least one set.
  • the at least one set includes at least one of the following:
  • any transmission parameter in the first set can be used for any time domain type
  • the time domain type corresponding to each transmission parameter in the at least one second set is determined by configuration information of the transmission parameter
  • At least one fourth set all transmission parameters in each of the fourth sets correspond to the same time domain type, and different fourth sets correspond to different time domain types.
  • the configuration information of the transmission parameters includes at least one of the following:
  • a first indication of a transmission parameter where 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.
  • the third set includes one or more subsets, and each subset of the third set satisfies at least one of the following:
  • the subsets of the third set are sorted according to a predetermined order, where the predetermined order represents the order of the time domain types;
  • 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.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the time domain units where the reception opportunities of the first CORESET are located correspond to the same time domain type; or,
  • the time domain unit where the reception opportunity of the first CORESET is located can correspond to multiple time domain types or all time domain types.
  • the time domain type corresponding to the time domain unit where the reception timing of the first CORESET is located is determined by at least one of the following:
  • the configuration information of the first CORESET includes at least one of the following:
  • an identifier of the first CORESET wherein a value of the identifier of the first CORESET is used to determine a time domain type corresponding to a time domain unit where a reception opportunity of the first CORESET is located;
  • the second indication of the first CORESET is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of the first CORESET is located is the time domain type indicated by the second indication.
  • the configuration information of each search space includes at least one of the following:
  • the identifiers of the search spaces where the values of the identifiers of the search spaces are used to respectively determine the time domain types corresponding to the time domain units where the reception opportunities of the search spaces are located;
  • the third indication of each search space is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of each search space is located is the time domain type indicated by the third indication of each search space.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the device further comprises:
  • the second receiving unit is configured to receive second information from a network-side device, where the second information indicates at least one of the following:
  • the receiving opportunities corresponding to each time domain type respectively correspond to transmission parameters, where M is an integer greater than or equal to 1.
  • the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types are indicated by the same MAC CE; or,
  • the transmission parameters corresponding to the receiving moments corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE includes at least one of the following:
  • M first indication fields the M first indication fields being used to respectively indicate transmission parameters corresponding to receiving opportunities corresponding to respective time domain types in the M time domain types;
  • the second indication field is used to jointly indicate the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types in the M time domain types.
  • the MAC CE when different MAC CEs are used to indicate transmission parameters corresponding to reception opportunities corresponding to respective time domain types in the M time domain types corresponding to the first CORESET, the MAC CE includes at least one of the following:
  • the third indication field is used to indicate the time domain type corresponding to the MAC CE
  • the fourth indication field is used to indicate the transmission parameters corresponding to the corresponding time domain type
  • the fifth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the first downlink reception includes PDSCH
  • the device further comprises:
  • the third receiving unit is configured to receive third information from the network-side device, where the third information indicates at least one of the following:
  • the time domain units corresponding to each time domain type respectively have corresponding activation transmission parameters, where N is an integer greater than or equal to 1.
  • activation transmission parameters corresponding to time domain units corresponding to respective time domain types are indicated by the same MAC CE; or,
  • the activation transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE when indicating, through the same MAC CE, activation transmission parameters corresponding to time domain units corresponding to respective time domain types in N time domain types corresponding to the first downlink reception, includes at least one of the following:
  • N sixth indication fields where the N sixth indication fields are used to respectively indicate activation transmission parameters corresponding to each of the N time domain types
  • a seventh indication field wherein the seventh indication field is used to jointly indicate the activation transmission parameters corresponding to each time domain type in the N time domain types.
  • the MAC CE when different MAC CEs are used to indicate, among the N time domain types of the first downlink reception, activation transmission parameters corresponding to time domain units corresponding to respective time domain types, the MAC CE includes at least one of the following:
  • An eighth indication field is used to indicate the time domain type corresponding to the MAC CE
  • the ninth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the first processing unit is specifically configured to perform at least one of the following:
  • the first downlink reception needs to apply the transmission parameters indicated by the third information, selecting, from the transmission parameters indicated by the third information, a transmission parameter having the 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;
  • 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, determining the transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameters corresponding to the first downlink reception;
  • the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, determining the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • 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 include the time domain type corresponding to the first downlink reception, determining the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • 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 includes the time domain type corresponding to the first downlink reception, selecting, from the transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter having the 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;
  • the initial transmission parameters corresponding to the first time domain type are determined as transmission parameters corresponding to the first downlink reception.
  • the first downlink reception includes a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource;
  • the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located corresponds to the same time domain type, or the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located can correspond to multiple time domain types or all time domain types.
  • the first downlink reception includes a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource;
  • the device further comprises:
  • a fourth receiving unit is configured to receive fourth information from a network-side device, where the fourth information is used to indicate at least one of the following:
  • the receiving moments corresponding to each time domain type have their own corresponding transmission parameters, and S is an integer greater than or equal to 1.
  • the first processing unit is specifically configured to:
  • the default transmission parameters corresponding to the first time domain type are determined as the transmission parameters corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.
  • the first measurement includes CSI measurement
  • the device further comprises:
  • a second processing unit configured to determine a target CSI reference resource corresponding to a target CSI report when reporting of the first measurement needs to distinguish time domain types
  • the third processing unit is configured to perform at least one of the following operations:
  • the target CSI report is a periodic or semi-continuous CSI report, determining a start time of CPU occupation based on the latest target CSI-RS reception timing;
  • the target information includes at least one of L1-RSRP, L1-SINR, and CQI;
  • the target CSI report corresponds to the second time domain type; the target CSI-RS reception timing corresponds to the second time domain type, and the target CSI-RS reception timing is no later than the target CSI reference resource.
  • the first measurement includes a CLI measurement
  • a transmission parameter corresponding to the CLI measurement resource includes at least one of the following:
  • the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET In the time domain unit corresponding to the second time domain type, the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET;
  • the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET corresponding to the second time domain type are the transmission parameters corresponding to the later of the latest received PDSCH and the latest monitored CORESET corresponding to the second time domain type.
  • the downlink receiving and measuring device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal, or it can be other devices other than a terminal.
  • the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
  • the downlink receiving and measuring device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be described here.
  • an embodiment of the present application further provides a downlink receiving and measuring device.
  • the downlink receiving and measuring device 600 includes:
  • the processing unit 601 is 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
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • the first downlink reception includes at least one of SSB, PDCCH and CSI-RS;
  • the time domain units where the first downlink reception is performed correspond 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.
  • the first downlink reception includes SSB
  • the processing unit is specifically configured to do at least one of the following:
  • the first downlink reception includes at least one of PDSCH, PDCCH and CSI-RS;
  • the device further comprises:
  • a first sending unit configured to send first information to a terminal, where 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 processing unit is specifically configured to:
  • a transmission parameter corresponding to the first downlink reception is determined from the at least one set.
  • the at least one set includes at least one of the following:
  • any transmission parameter in the first set can be used for any time domain type
  • the time domain type corresponding to each transmission parameter in the at least one second set is determined by configuration information of the transmission parameter
  • At least one fourth set all transmission parameters in each of the fourth sets correspond to the same time domain type, and different fourth sets correspond to different time domain types.
  • the configuration information of the transmission parameters includes at least one of the following:
  • a first indication of a transmission parameter where 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.
  • the third set includes one or more subsets, and each subset of the third set satisfies at least one of the following:
  • the subsets of the third set are sorted according to a predetermined order, where the predetermined order represents the order of the time domain types;
  • 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.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the time domain units where the reception opportunities of the first CORESET are located correspond to the same time domain type; or,
  • the time domain unit where the reception opportunity of the first CORESET is located can correspond to multiple time domain types or all time domain types.
  • the time domain type corresponding to the time domain unit where the reception timing of the first CORESET is located is determined by at least one of the following:
  • the configuration information of the first CORESET includes at least one of the following:
  • an identifier of the first CORESET wherein a value of the identifier of the first CORESET is used to determine a time domain type corresponding to a time domain unit where a reception opportunity of the first CORESET is located;
  • the second indication of the first CORESET is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of the first CORESET is located is the time domain type indicated by the second indication.
  • the configuration information of each search space includes at least one of the following:
  • the identifiers of the search spaces where the values of the identifiers of the search spaces are used to respectively determine the time domain types corresponding to the time domain units where the reception opportunities of the search spaces are located;
  • the third indication of each search space is used to indicate a time domain type, and the time domain type corresponding to the time domain unit where the reception opportunity of each search space is located is the time domain type indicated by the third indication of each search space.
  • the first downlink reception includes a PDCCH corresponding to a first control resource set CORESET;
  • the device further comprises:
  • the second sending unit is configured to send second information to the terminal, where the second information is used to indicate at least one of the following:
  • the receiving opportunities corresponding to each time domain type respectively correspond to transmission parameters, where M is an integer greater than or equal to 1.
  • the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types are indicated by the same MAC CE; or,
  • the transmission parameters corresponding to the receiving moments corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE includes at least one of the following:
  • M first indication fields the M first indication fields being used to respectively indicate transmission parameters corresponding to receiving opportunities corresponding to respective time domain types in the M time domain types;
  • the second indication field is used to jointly indicate the transmission parameters corresponding to the receiving opportunities corresponding to the respective time domain types in the M time domain types.
  • the MAC CE when different MAC CEs are used to indicate transmission parameters corresponding to reception opportunities corresponding to respective time domain types in the M time domain types corresponding to the first CORESET, the MAC CE includes at least one of the following:
  • the third indication field is used to indicate the time domain type corresponding to the MAC CE
  • the fourth indication field is used to indicate the transmission parameters corresponding to the corresponding time domain type
  • the fifth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • the first downlink reception includes PDSCH
  • the device further comprises:
  • the third sending unit is configured to send third information to the terminal, where the third information is used to indicate at least one of the following:
  • the time domain units corresponding to each time domain type respectively have corresponding activation transmission parameters, where N is an integer greater than or equal to 1.
  • activation transmission parameters corresponding to time domain units corresponding to respective time domain types are indicated by the same MAC CE; or,
  • the activation transmission parameters corresponding to the time domain units corresponding to each time domain type are indicated by different MAC CEs.
  • the MAC CE when indicating, through the same MAC CE, activation transmission parameters corresponding to time domain units corresponding to respective time domain types in N time domain types corresponding to the first downlink reception, includes at least one of the following:
  • N sixth indication fields where the N sixth indication fields are used to respectively indicate activation transmission parameters corresponding to each of the N time domain types
  • a seventh indication field wherein the seventh indication field is used to jointly indicate the activation transmission parameters corresponding to each time domain type in the N time domain types.
  • the MAC CE when different MAC CEs are used to indicate, among the N time domain types of the first downlink reception, activation transmission parameters corresponding to time domain units corresponding to respective time domain types, the MAC CE includes at least one of the following:
  • An eighth indication field is used to indicate the time domain type corresponding to the MAC CE
  • the ninth indication field is used to indicate the activation state or deactivation state of the transmission parameter corresponding to the corresponding time domain type.
  • processing unit is specifically configured to perform at least one of the following:
  • the first downlink reception needs to apply the transmission parameters indicated by the third information, selecting, from the transmission parameters indicated by the third information, a transmission parameter having the 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;
  • 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, determining the transmission parameters corresponding to the CORESET of the PDCCH as the transmission parameters corresponding to the first downlink reception;
  • the time domain type corresponding to the first downlink reception is different from the time domain type corresponding to the CORESET of the PDCCH, determining the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • 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 include the time domain type corresponding to the first downlink reception, determining the default transmission parameters or predefined transmission parameters corresponding to the first time domain type as the transmission parameters corresponding to the first downlink reception;
  • 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 includes the time domain type corresponding to the first downlink reception, selecting, from the transmission parameters corresponding to the CORESET of the PDCCH, a transmission parameter having the 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;
  • the initial transmission parameters corresponding to the first time domain type are determined as transmission parameters corresponding to the first downlink reception.
  • the first downlink reception includes a CSI-RS corresponding to a first non-zero power NZP CSI-RS resource;
  • the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located corresponds to the same time domain type, or the time domain unit where the reception opportunity corresponding to the first NZP CSI-RS resource is located can correspond to multiple time domain types or all time domain types.
  • the device further comprises:
  • the fourth sending unit is configured to send fourth information to the terminal, where the fourth information is used to indicate at least one of the following:
  • the receiving moments corresponding to each time domain type have their own corresponding transmission parameters, and S is an integer greater than or equal to 1.
  • processing unit is specifically configured to:
  • the default transmission parameters corresponding to the first time domain type are determined as the transmission parameters corresponding to the CSI-RS corresponding to the first NZP CSI-RS resource.
  • the downlink receiving and measuring device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal, or it can be other devices other than a terminal.
  • the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
  • the downlink receiving and measuring device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be described here.
  • an embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702.
  • the memory 702 stores a program or instruction that can be run on the processor 701.
  • the program or instruction when executed by the processor 701, implements the various steps of the above-mentioned terminal-side method embodiment and can achieve the same technical effect.
  • the communication device 700 is a network-side device
  • the program or instruction when executed by the processor 701, implements the various steps of the above-mentioned network-side device-side method embodiment and can achieve the same technical effect. To avoid repetition, they are not further described here.
  • the present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 .
  • This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects.
  • FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of the processor 810.
  • the terminal 800 may also include a power supply (such as a battery) to power various components.
  • the power supply may be logically connected to the processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption.
  • the terminal structure shown in FIG8 does not limit the terminal.
  • the terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.
  • the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode.
  • the display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 807 includes a touch panel 8071 and at least one of the other input devices 8072.
  • the touch panel 8071 is also called a touch screen.
  • the touch panel 8071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 8072 may include but are not limited to a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send downlink data to the network-side device.
  • the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.
  • the memory 809 can be used to store software programs or instructions and various data.
  • the memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data.
  • the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.).
  • the memory 809 may include a volatile memory or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DRRAM).
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • DDRSDRAM double data rate synchronous DRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DRRAM direct RAM
  • the memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
  • Processor 810 may include one or more processing units.
  • processor 810 integrates an application processor and a modem processor.
  • the application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.
  • the processor 810 is configured to:
  • 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;
  • the transmission parameter includes at least one of the following: transmit power; parameters related to the SSB beam; parameters related to the SSB index;
  • the transmission parameter includes at least one of the following: quasi co-location QCL assumption; transmission configuration indication TCI state;
  • the first measurement includes at least one of channel state information (CSI) measurement and cross-link interference (CLI) measurement.
  • CSI channel state information
  • CLI cross-link interference
  • the terminal when a time domain unit corresponds to or distinguishes multiple time domain types, the terminal can determine the transmission parameters corresponding to the downlink reception based on the time domain type corresponding to the downlink reception, thereby enabling the terminal to achieve flexible and reliable downlink reception based on the determined transmission parameters.
  • the terminal can also perform at least one of measurement and reporting based on the time domain type corresponding to a certain measurement, thereby enabling the terminal to achieve flexible, accurate, and efficient measurement. It can be seen that the embodiment of the present application can enable downlink reception or measurement by the terminal in a flexible duplex scenario.
  • the present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG4 .
  • This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.
  • the network-side device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95.
  • Antenna 91 is connected to radio frequency device 92.
  • radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing.
  • baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92.
  • Radio frequency device 92 processes the received information and then sends it through antenna 91.
  • the method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.
  • the baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the network side device operations shown in the above method embodiment.
  • the network side device may also include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and executable on the processor 94.
  • the processor 94 calls the instructions or programs in the memory 95 to execute the methods of execution of each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the various processes of the above-mentioned downlink reception and measurement method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk such as a hard disk, a hard disk, or a magnetic disk.
  • optical disk such as a hard disk, a hard disk, or an optical disk.
  • the readable storage medium may be a non-transitory readable storage medium.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned downlink reception and measurement method embodiments, and can achieve the same technical effects. To avoid repetition, they are not repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • An embodiment of the present application further provides a computer program/program product, which is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the various processes of the above-mentioned downlink reception and measurement method embodiments, and can achieve the same technical effects. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the downlink reception and measurement method described above, and the network-side device can be used to execute the steps of the downlink reception and measurement method described above.
  • the computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.
  • a storage medium such as ROM, RAM, magnetic disk, optical disk, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种下行接收和测量方法、装置及通信设备，属于通信技术领域，本申请实施例的下行接收和测量方法包括：终端基于第一下行接收对应的第一时域类型，确定第一下行接收对应的传输参数，并根据第一下行接收对应的传输参数，执行第一下行接收对应的接收；或，终端基于第一测量对应的第二时域类型，执行第一测量和所述第一测量对应的上报中的至少一项；在第一下行接收包括SSB的情况下，传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；在第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，传输参数包括如下至少一项：QCL假设；TCI状态；第一测量包括CSI测量和CLI测量中的至少一项。

Description

下行接收和测量方法、装置及通信设备
相关申请的交叉引用
本申请主张在2024年4月18日提交的中国专利申请No.202410471183.9的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种下行接收和测量方法、装置及通信设备。
背景技术
为了更灵活地利用有限的频谱资源，以动态地匹配业务需求，提升资源利用效率，相关技术提出了灵活的双工方式。在灵活的双工方式下，时域单元可以对应或区分多种时域类型。相关技术中，终端只需要在一种时域类型上进行下行接收或测量，无法适用于灵活双工场景，这导致终端不知该如何进行下行接收或测量。
发明内容
本申请实施例提供一种下行接收和测量方法、装置及通信设备，能够解决灵活双工场景下终端如何进行下行接收或测量的问题。
第一方面，提供了一种下行接收和测量方法，由终端执行，该方法包括：
终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第二方面，提供了一种下行接收和测量方法，由网络侧设备执行，该方法包括：
网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
所述网络侧设备基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第三方面，提供了一种下行接收和测量装置，该装置包括：
第一处理单元，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第四方面，提供了一种下行接收和测量装置，该装置包括：
处理单元，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于：
基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于：
基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的下行接收和测量方法的步骤，或实现如第二方面所述的下行接收和测量方法的步骤。
在本申请实施例中，终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；其中，所述第一下行接收包括SSB、PDCCH、PDSCH、CSI-RS中的至少一项；在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：QCL假设；TCI状态；所述第一测量包括CSI测量和CLI测量中的至少一项。这样，在时域单元对应或区分多种时域类型时，终端能够基于下行接收对应的时域类型来确定下行接收对应的传输参数，从而终端能够根据确定的传输参数实现灵活且可靠的下行接收。终端还能够基于某个测量对应的时域类型来执行测量和上报中的至少一项，从而终端能够实现灵活且准确和有效的测量。可见，本申请实施例能够实现终端在灵活双工场景下的下行接收或测量。
附图说明
图1是本申请实施例可应用的网络结构示意图；
图2是灵活双工方式的示意图；
图3是本申请实施例提供的一种下行接收和测量方法的流程图；
图4是本申请实施例提供的另一种下行接收和测量方法的流程图；
图5是本申请实施例提供的一种下行接收和测量装置的结构图；
图6是本申请实施例提供的另一种下行接收和测量装置的结构图；
图7是本申请实施例提供的一种通信设备的结构图；
图8是本申请实施例提供的一种终端的结构图；
图9是本申请实施例提供的一种网络侧设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)、统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)、网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
在对本申请实施例进行说明之前，以下先对相关技术中的灵活双工(Flexibleduplex)进行简单介绍：
在部署传统的蜂窝网络时，基于可用的频谱，以及业务特性等，可采用频分双工(Frequency Division Duplex，FDD)或时分双工(Time Division Duplex，TDD)的双工方式。当采用FDD时，上行传输和下行传输位于不同的频点上，两者互不干扰，可同时进行。当采用TDD时，上行传输和下行传输位于同一个频点上，采用时分的方式交错进行。上述两种双工方式各有优缺点。
为了更灵活地利用有限的频谱资源，以动态地匹配业务需求，提升资源利用效率，以及数据传输的上行覆盖、时延等性能，提出了灵活的双工方式。一种基于频域非交叠子带的灵活双工方式，即非交叠子带全双工(non-overlapping sub-band full duplex，SBFD)(可简称子带全双工)如下：
1、网络侧全双工
从网络侧的角度而言，在同一时刻，上行传输和下行传输可在不同的频域子带内同时进行。为避免上下行之间的干扰，可在对应不同传输方向的频域子带(例如上行子带和下行子带)之间留出一定的保护频带(Guard Band)。
2、终端侧半双工或全双工
当终端侧支持半双工时，在同一时刻，只能作上行传输或下行传输，两者不可同时进行。可以理解的是，在这种情况下，网络侧在同一时刻的上行传输和下行传输只能针对不同的终端。
当终端侧支持全双工时，与网络侧类似，在同一时刻，上行传输和下行传输可在不同的频域子带内同时进行。
图2给出了上述灵活双工方式的示意图，网络侧在一部分下行符号内，将单个载波的频域半静态划分为三个子带，其中载波两侧为下行子带，中央为上行子带，以减少对相邻载波造成的干扰。在第三个时隙内，UE1和UE2分别作上行发送和下行接收。
在图2所示的灵活双工方式的场景下，时域单元可以对应多种时域类型，如SBFD符号(symbol)与非SBFD(non-SBFD)symbol。对于启用了SBFD的服务小区(Serving cell)或带宽部分(Bandwidth Part，BWP)，在网络侧，SBFD symbol与non-SBFD symbol对应的天线或射频(Radio Frequency，RF)等的设置可能不同，以针对SBFD操作提供自干扰抑制等能力。相应地，SBFD symbol内上行信道(Channel)或信号(Signal)对应的空间相关性(Spatial relation)或传输配置指示(Transmission Configuration Indicator，TCI)状态(state)，也可能与non-SBFD symbol不同。对于各Channel/Signal对应的Spatial relation/TCI state的确定，在研究项目(Study Item，SI)阶段初步形成了单独配置(Separate configuration)的总体思路，但缺乏操作细节和信令设计方面的研究和讨论，这导致终端不知该如何进行下行接收和测量。
鉴于此，本申请实施例提供一种下行接收和测量方法、下行接收和测量装置及通信设备，以解决灵活的双工方式下终端如何进行下行接收和测量的问题。
为了便于下文中的方案描述，先给出如下概念及说明：
基于网络侧向UE提供的TDD模式(pattern)配置信息(例如，为UE的某个Serving cell提供的tdd-UL-DL-ConfigurationCommon或tdd-UL-DL-ConfigurationDedicated)，可以区分如下Symbol type：下行符号(DL symbol)、上行符号(UL symbol)、灵活符号(Flexible symbol)。
当针对某个Serving cell未提供tdd-UL-DL-ConfigurationCommon或tdd-UL-DL-ConfigurationDedicated时，可以认为各个Symbol都为Flexible symbol，或者，遵循Flexible symbol对应的规则或操作。
基于上述TDD pattern配置信息，以及网络侧向UE提供的SBFD配置信息，可以进一步区分如下Symbol type：
1、SBFD symbol
网络侧可通过SBFD配置信息将某些Symbol配置为可以执行SBFD操作(operation)，即将这些Symbol配置为SBFD symbol。例如，将基于TDD pattern确定的单个周期内的部分或所有Symbol配置为SBFD symbol。这些配置为SBFD symbol的Symbol可以为基于TDD pattern配置信息区分的Symbol type中的部分或所有类型。
针对为UE配置或激活的某个Serving cell，该Serving cell上的SBFD symbol可以进一步区分如下Symbol type：
(1)双工模式1的SBFD符号(SBFD symbol for duplex mode 1)
对于Duplex mode 1，网络侧支持基于全双工的SBFD operation；UE侧仅支持基于半双工的SBFD operation，即在单个SBFD symbol内UE只能执行上行发送或下行接收，而无法同时执行基于FDM(Frequency Division Multiplexing，频分复用)的上行发送和下行接收。
(2)双工模式2的SBFD符号(SBFD symbol for duplex mode 2)
对于Duplex mode 2，网络侧支持基于全双工的SBFD operation；UE侧可支持基于全双工的SBFD operation，即在单个SBFD symbol内UE可同时执行基于FDM的上行发送和下行接收。一般情况下，支持基于全双工的SBFD operation(即支持Duplex mode 2，或者，支持SBFD symbol for duplex mode 2)的UE必然也支持基于半双工的SBFD operation(即支持Duplex mode 1，或者，支持SBFD symbol for duplex mode 1)。
2、non-SBFD symbol
某个没有被配置(或指示)执行SBFD operation的Symbol都可以认为是non-SBFD symbol。
在版本18(Rel-18)的Duplex研究项目中，主流的观点认为：可以针对基于SBFD配置信息区分的不同Symbol type(例如，SBFD symbol和non-SBFD symbol，或者，SBFD symbol for duplex mode 1、SBFD symbol for duplex mode 2和non-SBFD symbol)分别(或直接)配置或(基于频域偏移(Offset)、各自起始参考点等隐式)推导各Channel/Signal对应的参数，以考虑/补偿不同Symbol type对应的天线与射频配置(包括天线位置、天线数、天线与RF链(chain)之间的连接关系等)、干扰情况和限制(包括自干扰(Self Interference，SI)、跨链路干扰(Cross Link Interference，CLI)等干扰及相应的限制)等。相应地，SBFD symbol内下行或CLI测量Channel/Signal对应的QCL假设/TCI state，也可能与non-SBFD symbol不同。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的下行接收和测量方法进行详细地说明。
图3示出本申请实施例提供的一种下行接收和测量方法的流程图。如图3所示，下行接收和测量方法包括：
步骤301：终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项。
第一下行接收可以包括同步信号块(Synchronization Signal Block，SSB)、物理下行控制信道(Physical downlink control channel，PDCCH)、物理下行共享信道(Physical downlink shared channel，PDSCH)、信道状态信息参考信号(Channel State Information Reference Signal，CSI-RS)中的至少一项；在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引(index)的相关参数；在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址(Quasi co-location，QCL)假设；TCI状态。其中，SSB波束的相关参数例如可以包括SSB波束的数目、SSB波束的指向、SSB波束的宽窄等参数。
第一测量可以包括信道状态信息(Channel State Information，CSI)测量和CLI测量中的至少一项。其中，在第一测量包括CSI测量时，可以同时考虑CSI的测量和上报，在第一测量包括CLI测量时，可以主要考虑CLI的测量。
上述的第一下行接收和第一测量的方案可以组合，即，步骤301包括：终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；以及，所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项。
时域类型可以理解为时域单元的类型，时域类型例如可以包括SBFD时域单元和非SBFD时域单元这两种类型，其中，SBFD时域单元又可以包括双工模式1的SBFD时域单元和双工模式2的SBFD时域单元这两种类型。时域单元可以是时隙(Slot)、符号(Symbol)等。本申请中将时域单元以Symbol为例进行描述，此时时域类型可以称为Symbol type，Symbol type例如可以包括SBFD symbol和non-SBFD symbol这两种类型，其中，SBFD symbol又可以包括SBFD symbol for duplex mode 1和SBFD symbol for duplex mode 2这两种类型。当时域单元为Slot时，时域类型可以称为Slot type，本申请不作任何限定。本申请实施例中的第一时域类型、第二时域类型均可以参照上述时域类型的相关说明进行理解，为避免重复，对此不作赘述。
本申请实施例可应用于启用了SBFD的Serving cell/BWP。对于启用了SBFD的Serving cell/BWP，UE可以基于Symbol type，确定下行Channel/Signal或CLI测量Channel/Signal对应的QCL假设/TCI state。这里的UE可以理解为支持SBFD的UE(SBFD capable UE)或知晓SBFD的UE(SBFD aware UE)。
本申请实施例中，终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；其中，所述第一下行接收包括SSB、PDCCH、PDSCH、CSI-RS中的至少一项；在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：QCL假设；TCI状态；所述第一测量包括CSI测量和CLI测量中的至少一项。这样，在时域单元对应或区分多种时域类型时，终端能够基于下行接收对应的时域类型来确定下行接收对应的传输参数，从而终端能够根据确定的传输参数实现灵活且可靠的下行接收。终端还能够基于某个测量对应的时域类型来执行测量和上报中的至少一项，从而终端能够实现灵活且准确和有效的测量。可见，本申请实施例能够实现终端在灵活双工场景下的下行接收或测量。
在一些实施例中，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
所述第一下行接收所在时域单元对应同一个时域类型；或者，
所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
这里，“能够”可以理解为允许、支持等含义，其他相同描述可作相同理解，为避免重复，不作赘述。
以下以第一下行接收包括SSB为例，对SSB接收的相关实施方式进行说明。
在一些实施例中，所述第一下行接收包括SSB；
在所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型的情况下，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
所述终端不区分所述第一下行接收所在时域单元对应的时域类型，将所述第一下行接收对应的传输参数统一确定为第一传输参数；
所述终端区分所述第一下行接收所在时域单元对应的时域类型，基于时域类型与传输参数之间的映射关系，确定所述第一下行接收在不同时域类型的时域单元内对应的传输参数。
为了便于理解，本申请实施例对SSB的传输方式进行示例性说明。
对于SSB的传输，可采用SSB传输方式1和SSB传输方式2中的任一方式：
SSB传输方式1：SSB仅能在单个Symbol type对应的Symbol内传输。
此时，既可以由网络侧保证(此时UE期望)配置的SSB仅位于该Symbol type对应的Symbol内，也可以网络侧配置SSB时不保证其仅出现在该Symbol type对应的Symbol内，但UE仅认为位于该Symbol type对应的Symbol内的SSB生效。例如，SSB仅能在non-SBFD symbol内配置，或者，SSB仅能在non-SBFD symbol内实际传输。
SSB传输方式2：SSB可在(即能够在)各个(或大于一个)Symbol type对应的Symbol内传输。
此时，对于SSB的传输属性(即传输参数)的配置/假设，可采用SSB属性方式1和SSB属性方式2中的任一项：
SSB属性方式1：UE假设不同Symbol type对应的Symbol内传输的SSB的传输属性完全一致，或者，UE不区分不同Symbol type对应的Symbol内传输的SSB之间的传输属性差异。
SSB属性方式1可以理解为：UE认为不同Symbol type对应的Symbol内传输的SSB统一使用配置参数，相互之间可统一处理，无需考虑差异。
SSB属性方式2：UE认为不同Symbol type对应的Symbol内传输的SSB之间可能存在传输属性差异。
SSB传输属性的差异包括以下至少一项：
传输的SSB index或SSB波束的数目；例如，可以为SBFD symbol独立配置ssb-PositionsInBurst，以指示在SBFD symbol内传输的单个SSB突发(burst)集(set)内实际传输的SSB index集合；
SSB发射功率；例如，可以为SBFD symbol独立配置ss-PBCH-BlockPower，以指示在SBFD symbol内传输的SSB的发射功率；
SSB波束指向和/或宽窄；一般地，网络侧对于各个SSB波束的指向和/或宽窄设置，对于UE透明。
此时，可基于Symbol type区分不同的SSB传输属性。其中，SSB传输涉及的各个Symbol type对应的SSB传输属性可以独立配置/确定，或者，配置大于一套SSB传输属性，并配置/确定各个Symbol type与各套SSB传输属性之间的映射关系。
相应地，在基于SSB波束选择结果的相关功能中，UE需要区分Symbol type，使用匹配的Symbol type对应的SSB波束，例如，确定PDSCH的初始QCL假设，确定映射的随机接入时机(RACH Occasion，RO)等。
具体采用哪种SSB传输方式，或者，当采用SSB传输方式2时，具体是采用SSB属性方式1还是SSB属性方式2，可以由协议规定或由高层信令配置。例如，在系统信息块1(System Information Block 1，SIB1)中指示采用SSB属性方式1或SSB属性方式2。
可选地，对于SIB1 PDSCH(即承载SIB1初传/重传的PDSCH)的传输，也可以采用以上类似的方式，具体可包括如下至少一项：
SIB1 PDSCH仅能在单个Symbol type对应的Symbol内传输；
SIB1 PDSCH可在各个(或大于一个)Symbol type对应的Symbol内传输。
以下以第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项为例，对下行接收对应的通用TCI state配置的相关实施方式进行说明。
在一些实施例中，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
所述方法还包括：
所述终端接收来自网络侧设备的第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
所述终端基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
可选地，所述至少一个集合包括如下至少一项：
第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
可选地，所述传输参数的配置信息包括如下至少一项：
传输参数的标识，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的标识的取值确定；
传输参数的第一指示，所述第一指示用于指示时域类型，所述至少一个第二集合中的各个传输参数对应的时域类型为传输参数的第一指示所指示的时域类型。
可选地，所述第三集合包括一个或多个子集，所述第三集合的各个子集满足如下至少之一：
所述第三集合的各个子集按照预定顺序排序，所述预定顺序表示所述时域类型的顺序；
所述第三集合的各个子集包括的传输参数的数量按照预定义的方式分配，或者直接配置或指示。
为了便于理解，本申请实施例对下行接收对应的通用TCI state的配置方式进行示例性说明。
对于下行接收(包括PDSCH、PDCCH和NZP CSI-RS)(当采用联合模式(joint mode)时，也适用于上行发送，下面不再赘述，这里的上行发送包括PUSCH、PUCCH和SRS)对应的TCI state的配置，可以采用通用TCI state配置方式1和通用TCI state配置方式2中的任一方式：
通用TCI state配置方式1：不区分Symbol type，应用统一的配置TCI state集合(即第一集合)。
通用TCI state配置方式1可以理解为，对于任一Symbol type对应的下行接收(或者，任一Symbol type对应的Symbol内的下行接收；当采用joint mode时，可扩展为进一步包含上行发送，即该Symbol type对应的上行发送，或者，该Symbol type对应的Symbol内的上行发送)，可以根据需要应用此配置TCI state集合中的任一TCI state；或者说，不限制此配置TCI state集合中的任意TCI state应用的下行接收(当采用joint mode时，进一步包含上行发送)对应的Symbol type。这里统一的配置TCI state集合，可以基于PDSCH-Config中的tci-StatesToAddModList和tci-StatesToReleaseList确定，当采用joint mode时，可以基于PDSCH-Config中的下行-联合TCI状态添加/修改列表(如dl-OrJointTCI-StateToAddModList-r17)和下行-联合TCI状态释放列表(如dl-OrJointTCI-StateToReleaseList-r17)确定。
通用TCI state配置方式2：区分Symbol type应用各自的配置TCI state集合。
通用TCI state配置方式2中，在确定Symbol type对应的配置TCI state集合时，可以采用通用TCI state配置方式2-1至通用TCI state配置方式2-3中的任一方式：
通用TCI state配置方式2-1：在每个TCI state的配置信息中，区分此TCI state对应的Symbol type。
此时，各个Symbol type对应的TCI state仍可以放在统一的配置TCI state集合(即第二集合)中。对于某个Symbol type，可以从此配置TCI state集合中筛选出与其对应的TCI state子集，作为该Symbol type对应的配置TCI state集合。具体地，可以采用方式1至方式2中的任一方式：
方式1：基于每个TCI state的TCI-StateId所在的TCI-StateId取值范围，确定此TCI state对应的Symbol type。这里假设各个Symbol type各自对应一个独立的TCI-StateId取值范围，可以由协议规定或由高层信令配置；不同Symbol type对应的TCI-StateId取值范围相互之间不存在交集。当配置某个Symbol type对应的TCI state时，此TCI state的TCI-StateId要求位于与该Symbol type对应的TCI-StateId取值范围内；
方式2：在每个TCI state的配置信息中，引入新的参数(即第一指示)指示此TCI state对应的Symbol type。
通用TCI state配置方式2-2：基于某个TCI state在统一的配置TCI state集合中的位置，确定此TCI state对应的Symbol type。
这里，假设各个Symbol type对应的TCI state放在统一的配置TCI state集合(即第三集合)中，并且此统一的配置TCI state集合为有序集合，基于PDSCH-Config中的tci-StatesToAddModList和tci-StatesToReleaseList确定(当采用joint mode时，可以基于PDSCH-Config中的dl-OrJointTCI-StateToAddModList-r17和dl-OrJointTCI-StateToReleaseList-r17确定)。例如，将第一次配置的tci-StatesToAddModList(当采用joint mode时，可以为dl-OrJointTCI-StateToAddModList-r17)作为此统一的配置TCI state集合的初始集合；之后配置的tci-StatesToAddModList(当采用joint mode时，可以为dl-OrJointTCI-StateToAddModList-r17)中新增的TCI state按tci-StatesToAddModList中出现的先后顺序依次添加到此统一的配置TCI state集合的尾部，修改的TCI state既可以覆盖此统一的配置TCI state集合中的对应TCI state，也可以按tci-StatesToAddModList中出现的先后顺序依次添加到此统一的配置TCI state集合的尾部(此时需要删除此统一的配置TCI state集合中的对应TCI state；修改的TCI state既可以统一放在新增的TCI state之前或之后，也可以和新增的TCI state一起按tci-StatesToAddModList中出现的先后顺序依次添加到此统一的配置TCI state集合的尾部(此时在此统一的配置TCI state集合的尾部添加的新增的TCI state和修改的TCI state可能会存在夹杂或交替的情况))；基于配置的tci-StatesToReleaseList(当采用joint mode时，可以为dl-OrJointTCI-StateToReleaseList-r17)从此统一的配置TCI state集合中删除对应的TCI state。
进一步地，确定上述有序集合内，与某个Symbol type对应的TCI state的位置区域；由此位置区域的所有TCI state构成该Symbol type对应的配置TCI state集合。例如，由协议规定或由高层信令配置此有序集合的前面N1个TCI state对应Symbol type 1(例如non-SBFD symbol)，后面剩余N2个TCI state对应Symbol type 2(例如SBFD symbol)。在确定N1和N2时，假设此有序集合内包含N个TCI state，则可以采用方式3和方式4中的任一方式：
方式3：约定N1＝floor(N/2)(即下取整)或N1＝ceiling(N/2)(即上取整)，并且N2＝N-N1，即将此有序集合中的TCI state对半分或近似对半分，将得到的两部分分别对应两种Symbol type；
方式4：配置或指示N1，并且N2＝N-N1。
通用TCI state配置方式2-3：分别配置和/或维护各个Symbol type对应的配置TCI state集合(即第四集合)。
当各个Symbol type对应的配置参数基于单一/共享的PDSCH-Config提供/确定时，可以在PDSCH-Config中针对各个Symbol type分别设置对应的TCI状态添加/修改列表(如tci-StatesToAddModList)和/或TCI状态释放列表(如tci-StatesToReleaseList)。当采用joint mode时，可以在PDSCH-Config中针对各个Symbol type分别设置对应的dl-OrJointTCI-StateToAddModList-r17和/或dl-OrJointTCI-StateToReleaseList-r17)；基于某个Symbol type对应的tci-StatesToAddModList和tci-StatesToReleaseList(当采用joint mode时，可以基于某个Symbol type对应的dl-OrJointTCI-StateToAddModList-r17和dl-OrJointTCI-StateToReleaseList-r17)来维护该Symbol type对应的配置TCI state集合。例如，在PDSCH-Config中针对SBFD symbol引入新的tci-StatesToAddModList和/或tci-StatesToReleaseList(当采用joint mode时，可以在PDSCH-Config中针对SBFD symbol引入新的dl-OrJointTCI-StateToAddModList-r17和/或dl-OrJointTCI-StateToReleaseList-r17)，现有tci-StatesToAddModList和tci-StatesToReleaseList(当采用joint mode时，可以是现有dl-OrJointTCI-StateToAddModList-r17和dl-OrJointTCI-StateToReleaseList-r17)用于non-SBFD symbol对应的配置TCI state集合的维护。
当各个Symbol type对应的配置参数基于各自的PDSCH-Config分别提供/确定时，基于某个Symbol type对应的PDSCH-Config中的tci-StatesToAddModList和tci-StatesToReleaseList(当采用joint mode时，可以是PDSCH-Config中的dl-OrJointTCI-StateToAddModList-r17和dl-OrJointTCI-StateToReleaseList-r17)来维护该Symbol type对应的配置TCI state集合。
以下以第一下行接收包括与第一CORESET对应的PDCCH为例，对PDCCH接收的相关实施方式进行说明。
在一些实施例中，所述第一下行接收包括与所述第一CORESET对应的PDCCH；
所述第一CORESET的接收时机所在时域单元对应同一个时域类型；或者，
所述第一CORESET的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
也就是说，在所述第一下行接收包括与所述第一CORESET对应的PDCCH的情况下，所述第一下行接收所在时域单元对应同一个时域类型；或者，所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
可选地，在所述第一CORESET的接收时机所在时域单元对应同一个时域类型的情况下，所述第一CORESET的接收时机所在时域单元对应的时域类型由如下至少一项确定：
所述第一CORESET的配置信息；
所述第一CORESET关联的搜索空间(Search Space)中，各个搜索空间的配置信息；
协议规定；
高层参数。
在所述第一CORESET的接收时机所在时域单元对应的时域类型由所述第一CORESET的配置信息(即上述第一项)，以及所述第一CORESET关联的搜索空间中，各个搜索空间的配置信息(即上述第二项)确定的情况下，时域类型的确定操作可以理解为包含如下操作：UE基于第一CORESET关联的所有搜索空间，确定第一CORESET对应的所有接收时机所在时域单元对应的时域类型。
可选地，所述第一CORESET的配置信息，包括如下至少一项：
所述第一CORESET的标识，所述第一CORESET的标识的取值用于确定所述第一CORESET的接收时机所在时域单元对应的时域类型；
所述第一CORESET的第二指示，所述第二指示用于指示时域类型，所述第一CORESET的接收时机所在时域单元对应的时域类型为所述第二指示所指示的时域类型。
可选地，所述各个搜索空间的配置信息，包括如下至少一项：
所述各个搜索空间的标识，所述各个搜索空间的标识的取值用于分别确定所述各个搜索空间的接收时机所在时域单元对应的时域类型；
所述各个搜索空间的第三指示，所述第三指示用于指示时域类型，所述各个搜索空间的接收时机所在时域单元对应的时域类型为各个搜索空间的第三指示所指示的时域类型。
这里，搜索空间的标识可以用来指示此搜索空间关联的CORESET的接收时机(occasion)对应的Symbol type。也就是说，在此搜索空间和第一CORESET关联的情况下，就可以通过搜索空间的标识来指示第一CORESET的接收时机的Symbol type。
相应的，搜索空间的第三指示可以用来指示此搜索空间关联的CORESET的接收时机对应的Symbol type。也就是说，在此搜索空间和第一CORESET关联的情况下，就可以通过搜索空间的第三指示来指示第一CORESET的接收时机的Symbol type。
可选地，所述方法还包括：
所述终端接收来自网络侧设备的第二信息，所述第二信息用于指示如下至少一项：
所述第一CORESET的所有接收时机对应的传输参数；
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
可选地，所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过同一个MAC CE指示；或者，
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示。
这里，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示，可以理解为，使用独立的MAC CE来分别指示各个时域类型对应的接收时机各自对应的传输参数。
可选地，在通过同一个MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
M个第一指示域，所述M个第一指示域用于分别指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数；
第二指示域，所述第二指示域用于联合指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数。
可选地，在通过不同的MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
第三指示域，用于指示所述MAC CE对应的时域类型；
第四指示域，用于指示对应时域类型所对应的传输参数；
第五指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
为了便于理解，本申请实施例对CORESET Occasion配置方式进行示例性说明。
对于某个CORESET(如第一CORESET)，基于其被使用的情况(例如，其与一个或多个Search Space的关联情况，以及这些关联的Search Space的时域监听配置情况)，可以在时域对应多个Occasion(或者至少一个Occasion)。
对于某个CORESET的时频位置的配置，可以采用CORESET Occasion配置方式1和CORESET Occasion配置方式2中的任一方式：
CORESET Occasion配置方式1：该CORESET对应的Occasion仅能位于单个Symbol type对应的Symbol内。
这里的单个Symbol type(假设为给定Symbol type(即第一时域类型))可以采用以下(1)至(4)的其中一项确定：
(1)基于该CORESET的ControlResourceSetId所在的ControlResourceSetId取值范围，确定给定Symbol type。这里假设各个Symbol type各自对应一个独立的ControlResourceSetId取值范围，可以由协议规定或由高层信令配置；不同Symbol type对应的ControlResourceSetId取值范围相互之间不存在交集。当配置某个Symbol type对应的CORESET时，该CORESET的ControlResourceSetId要求位于与该Symbol type对应的ControlResourceSetId取值范围内。
(2)在每个CORESET的配置信息中，引入新的参数指示该CORESET对应的Symbol type。
(3)将与该CORESET关联的至少一个Search Space对应的Symbol type，作为给定Symbol type。这里假设或要求关联的至少一个Search Space中各个Search Space对应的Symbol type相同。在确定某个Search Space对应的Symbol type时，可以采用(3.1)至(3.3)的其中一种方式：
(3.1)基于该Search Space的SearchSpaceId所在的SearchSpaceId取值范围，确定给定Symbol type。这里，假设各个Symbol type各自对应一个独立的SearchSpaceId取值范围，可以由协议规定或由高层信令配置；不同Symbol type对应的SearchSpaceId取值范围相互之间不存在交集。当配置某个Symbol type对应的Search Space时，该Search Space的SearchSpaceId要求位于与该Symbol type对应的SearchSpaceId取值范围内。
(3.2)在每个Search Space的配置信息中，引入新的参数指示该Search Space对应的Symbol type。
(3.3)基于该CORESET和该Search Space的配置信息，确定CORESET Occasion所在的Symbol对应的Symbol type。
(4)由协议规定或由高层参数配置给定Symbol type。例如，由协议规定CORESET#0对应的Occasion仅能位于non-SBFD symbol内。
此时，既可以由网络侧在配置时保证该CORESET对应的所有Occasion仅位于给定Symbol type对应的Symbol内，也可以是网络侧在配置时不保证该CORESET对应的任意Occasion仅出现在给定Symbol type对应的Symbol内，但UE仅认为位于给定Symbol type对应的Symbol内(完整位于给定Symbol type对应的Symbol内，或者位于给定Symbol type对应的Symbol内的Symbol数目不少于M，或者位于给定Symbol type对应的Symbol内的Symbol比例不小于N)的Occasion生效，或者，认为不位于给定Symbol type对应的Symbol内(不完整位于给定Symbol type对应的Symbol内，或者位于给定Symbol type对应的Symbol内的Symbol数目少于M，或者位于给定Symbol type对应的Symbol内的Symbol比例小于N)的Occasion无效。
CORESET Occasion配置方式2：该CORESET对应的Occasion可位于各个(或大于一个)Symbol type对应的Symbol内。
CORESET Occasion配置方式2可以理解为，网络侧在配置时无需关注或保证该CORESET对应的Occasion位于哪些Symbol type对应的Symbol内。例如，该CORESET对应的Occasion可能都位于SBFD symbol内，或者都位于non-SBFD symbol内，或者部分Occasion位于SBFD symbol内，部分Occasion位于non-SBFD symbol内。
可选地，对于该CORESET的某个Occasion，将此Occasion所在Symbol对应的Symbol type，作为此Occasion对应的Symbol type。
对于某个Index不为0的CORESET，可以进一步为其配置(例如，基于ControlResourceSet中的tci-StatesPDCCH-ToAddList和tci-StatesPDCCH-ToReleaseList配置)可用TCI state集合，此可用TCI state集合中包含的各个TCI state可以从网络侧为下行接收配置的配置TCI state集合中选择。
当采用通用TCI state配置方式1时(不区分是采用CORESET Occasion配置方式1还是CORESET Occasion配置方式2)，可以从统一的配置TCI state集合中选择TCI state，作为该CORESET的可用TCI state集合即可。
当采用通用TCI state配置方式2时，可以分为如下两种情况：
当采用CORESET Occasion配置方式1时，可以从给定Symbol type对应的配置TCI state集合中选择TCI state，作为该CORESET的可用TCI state集合。
当采用CORESET Occasion配置方式2时，可以为各个(或者该CORESET对应的Occasion所在Symbol对应的任一)Symbol type，从该Symbol type对应的配置TCI state集合中选择TCI state，作为该CORESET针对该Symbol type的可用TCI state集合。可以理解的是，对于该CORESET，针对每个涉及的Symbol type，都存在一个对应的可用TCI state集合。相应地，可以在ControlResourceSet中引入对应的配置参数。例如，ControlResourceSet中的tci-StatesPDCCH-ToAddList和tci-StatesPDCCH-ToReleaseList用于配置non-SBFD symbol对应的可用TCI state集合，并引入新的参数用于配置SBFD symbol对应的可用TCI state集合。
为了便于理解，本申请实施例对CORESET Occasion的PDCCH TCI state指示方式进行示例性说明。
对于CORESET Occasion内的PDCCH检测对应的TCI state的指示，可以采用PDCCH TCI state指示方式1和PDCCH TCI state指示方式2中的任一方式：
PDCCH TCI state指示方式1：不区分Symbol type，指示该CORESET的所有Occasion统一使用/跨Symbol type共享使用的TCI state。
PDCCH TCI state指示方式1与通用TCI state配置方式1对应(两种方式相互对应，可以理解为两种方式搭配使用；下文中都沿用相同的理解)，并且可同时应用于CORESET Occasion配置方式1和CORESET Occasion配置方式2。
当该CORESET的Index为0(即为CORESET#0)时，可以使用与Symbol type无关(或不考虑Symbol type的影响)的媒体接入控制(Medium Access Control，MAC)控制单元(Control Element，CE)来指示统一的配置TCI state集合中的某个TCI state，作为该CORESET的所有Occasion统一使用/跨Symbol type共享使用的TCI state；当该CORESET的Index不为0时，可以使用与Symbol type无关(或不考虑Symbol type的影响)的MAC CE来指示为该CORESET配置的可用TCI state集合中的某个TCI state，作为该CORESET的所有Occasion统一使用/跨Symbol type共享使用的TCI state。
这里的MAC CE可以理解为UE专用PDCCH的TCI状态指示的MAC CE(TCI State Indication for UE-specific PDCCH MAC CE)，或者与其功能相同或类似的MAC CE。
对于PDCCH TCI state指示方式1，可以沿用TCI State Indication for UE-specific PDCCH MAC CE的现有格式定义。基于该MAC CE为该CORESET指示的单个TCI state，可以应用于该CORESET与任意Symbol type对应的Occasion内的PDCCH检测，或者说，不限制该CORESET应用指示的TCI state作PDCCH检测的Occasion对应的Symbol type。
PDCCH TCI state指示方式2：为该CORESET与不同Symbol type对应的Occasion分别指示各自的TCI state。
一般地，PDCCH TCI state指示方式2与通用TCI state配置方式2对应。可选地，PDCCH TCI state指示方式2也可以与通用TCI state配置方式1对应。PDCCH TCI state指示方式2主要应用于CORESET Occasion配置方式2，也可以应用于CORESET Occasion配置方式1。
在使用MAC CE指示各个Symbol type对应的TCI state，以指示该CORESET与各个Symbol type对应的Occasion内的PDCCH检测分别应用的TCI state时，可以采用PDCCH TCI state指示方式2-1和PDCCH TCI state指示方式2-2中的任一方式：
PDCCH TCI state指示方式2-1：使用相同的MAC CE来指示各个(或至少一个)Symbol type对应的TCI state。
PDCCH TCI state指示方式2-1可以理解为，单个MAC CE可以用于指示超过一个Symbol type对应的TCI state。
具体地，一种可能的实现方式为(假设为实现方式1)：调整TCI State Indication for UE-specific PDCCH MAC CE的现有格式定义，或者引入一种新的MAC CE，在MAC CE中区分Symbol type分别设置各个Symbol type对应的TCI state指示域(即第一指示域)。其中，某个Symbol type对应的TCI state指示域基于(5)和(6)中的任一项，指示该Symbol type对应的TCI state：
(5)TCI-StateId。当采用通用TCI state配置方式2时，当该CORESET的Index为0(即为CORESET#0)时，需要由网络侧保证该TCI-StateId对应的TCI state位于该Symbol type对应的配置TCI state集合中；当该CORESET的Index不为0时，需要由网络侧保证该TCI-StateId对应的TCI state位于该Symbol type对应的可用TCI state集合中。
(6)配置/可用TCI state集合中的位置。这里，“配置/可用TCI state集合中的位置”，可以理解为指示的TCI state在统一的配置TCI state集合(当应用于通用TCI state配置方式1且该CORESET的Index为0时)中的序号或下标，或者，为该CORESET配置的可用TCI state集合(当应用于通用TCI state配置方式1且该CORESET的Index不为0时)中的序号或下标，或者，该Symbol type对应的配置/可用TCI state集合(当应用于通用TCI state配置方式2时)中的序号或下标(要求这些情况下的TCI state集合以有序集合的方式维护)。当该CORESET的Index为0(即为CORESET#0)时，使用配置TCI state集合；当该CORESET的Index不为0时，使用可用TCI state集合。
各Symbol type对应的TCI state指示域可以基于Symbol type的顺序在MAC CE中依次排列。Symbol type的顺序可以由协议规定或由高层信令配置。例如，由协议规定在某个MAC CE中先出现non-SBFD symbol对应的TCI state指示域，然后在其后再出现SBFD symbol对应的TCI state指示域。
当采用实现方式1时，PDCCH TCI state指示方式2-1可以应用于通用TCI state配置方式1、通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3。
另一种可能的实现方式为(假设为实现方式2)：沿用TCI State Indication for UE-specific PDCCH MAC CE的现有格式定义，或者采用与其类似的格式定义，在MAC CE中仅设置单个TCI state指示域，用于指示单个TCI-StateId或配置/可用TCI state集合中的单个位置。可选地，基于此指示的单个ID或单个位置，以及预定义规则，确定N个ID或N个位置(假设需要指示对应的TCI state的Symbol type数目为N)。例如，在MAC CE中指示第一个ID/位置，则确定的N个ID/位置为：第一个ID/位置+i，i＝0,…,N–1；或者，在MAC CE中指示最后一个ID/位置，则确定的N个ID/位置为：最后一个ID/位置-i，i＝0,…,N–1。可选地，可以进一步引入取模操作以避免ID/位置溢出。例如，将上述确定的N个ID/位置中的各个ID/位置进一步针对(最大ID+1)/位置总数进行取模，得到最终的N个ID/位置(假设各个ID/位置从0开始编号)。
当采用实现方式2时，PDCCH TCI state指示方式2-1可以应用于通用TCI state配置方式1、通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3。
当应用于通用TCI state配置方式1时，可以引入预定义规则，确定与采用实现方式2确定的N个ID/位置对应的N个TCI state各自对应的Symbol type。预定义规则可以为：N个TCI state基于TCI-StateId或配置/可用TCI state集合中的位置进行升序或降序，与N个Symbol type基于Symbol type的顺序(参见前文中的相应描述)逐一对应。例如，2个TCI state中，TCI-StateId较小的TCI state对应non-SBFD symbol，TCI-StateId较大的TCI state对应SBFD symbol。
当应用于通用TCI state配置方式2-1时，基于采用实现方式2确定的N个ID/位置对应的N个TCI state中各个TCI state的配置信息，便可得知每个TCI state对应的Symbol type。
当应用于通用TCI state配置方式2-2时，基于采用实现方式2确定的N个ID/位置对应的N个TCI state中各个TCI state在统一的配置/可用TCI state集合中的位置，便可得知每个TCI state对应的Symbol type。
当应用于通用TCI state配置方式2-3时：
当实现方式2仅指示单个ID时，仅适用于不同Symbol type对应的TCI state的ID空间允许重叠的情况(即：各个Symbol type对应的配置TCI state集合中的TCI state的ID仅要求在同一个Symbol type对应的配置TCI state集合中不能重复出现(即在单个Symbol type内要求ID唯一)，在不同Symbol type对应的配置TCI state集合中允许重复(即不同Symbol type对应的ID空间允许重叠))，此时基于指示的单个ID在各个Symbol type各自对应的配置TCI state集合中，分别确定出与此单个ID对应的单个TCI state，作为各个Symbol type各自对应的TCI state。
当实现方式2仅指示单个位置时，基于指示的单个位置在各个Symbol type各自对应的配置TCI state集合中，分别确定出与此单个位置对应的单个TCI state，作为各个Symbol type各自对应的TCI state。
当实现方式2确定N个ID/位置时，可将N个ID/位置基于升序或降序，与N个Symbol type基于Symbol type的顺序(参见前文中的相应描述)逐一对应，然后基于各个Symbol type各自对应的ID/位置，分别在各个Symbol type各自对应的配置TCI state集合中，确定出与ID/位置对应的单个TCI state，作为各个Symbol type各自对应的TCI state。
PDCCH TCI state指示方式2-2：使用独立的MAC CE来指示每个(或某个)Symbol type对应的TCI state。
PDCCH TCI state指示方式2-2可以理解为，单个MAC CE仅用于指示单个Symbol type对应的TCI state，在MAC CE中包含用于指示Symbol type的信息/字段。
当某个MAC CE用于指示某个Symbol type对应的TCI state时，该MAC CE中的TCI state指示域(即第四指示域或第五指示域)基于(7)和(8)中的任一项，指示该Symbol type对应的TCI state：
(7)TCI-StateId。当采用通用TCI state配置方式2时，当该CORESET的Index为0(即为CORESET#0)时，需要由网络侧保证该TCI-StateId对应的TCI state位于该Symbol type对应的配置TCI state集合中；当该CORESET的Index不为0时，需要由网络侧保证该TCI-StateId对应的TCI state位于该Symbol type对应的可用TCI state集合中。
(8)配置/可用TCI state集合中的位置。这里，“配置/可用TCI state集合中的位置”，可以理解为指示的TCI state在统一的配置TCI state集合(当应用于通用TCI state配置方式1且该CORESET的Index为0时)、为该CORESET配置的可用TCI state集合(当应用于通用TCI state配置方式1且该CORESET的Index不为0时)、或者该Symbol type对应的配置/可用TCI state集合(当应用于通用TCI state配置方式2时)中的序号或下标(要求这些情况下的TCI state集合以有序集合的方式维护)。当该CORESET的Index为0(即为CORESET#0)时，使用配置TCI state集合；当该CORESET的Index不为0时，使用可用TCI state集合。
PDCCH TCI state指示方式2-1可以应用于通用TCI state配置方式1、通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3。
对于CORESET#0的某个Occasion(假设其对应的Symbol type为给定的Symbol type)对应的PDCCH接收/检测(或者，此Occasion内的PDCCH接收/检测)，在确定其对应的QCL假设/TCI state时，考虑如下两种情况(Case)：
Case1：如果UE收到为CORESET#0指示应用的TCI状态的MAC CE激活命令，则在执行所述PDCCH接收/检测时，使用此MAC CE激活命令指示的TCI状态；
Case2：如果在最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)之后，UE没有收到为CORESET#0指示应用的TCI状态的MAC CE激活命令，则使用此最近的随机接入过程中UE识别的SSB对应的QCL假设。
当基于Case 1确定此Occasion对应的PDCCH接收/检测对应的TCI state时，对于“为CORESET#0指示应用的TCI状态的MAC CE激活命令”的判断，描述如下：
当采用PDCCH TCI state指示方式1时，只要UE收到任意一个或多个为CORESET#0指示应用的TCI状态的MAC CE激活命令，便认为满足Case 1。
当采用PDCCH TCI state指示方式2时，仅当UE收到至少一个为CORESET#0指示应用的TCI状态，且针对给定的Symbol type的MAC CE激活命令时(例如，当采用PDCCH TCI state指示方式2-1，并且收到一个MAC CE，且该MAC CE中指示了给定的Symbol type对应的TCI state时，或者，当采用PDCCH TCI state指示方式2-2，并且收到一个针对给定的Symbol type的MAC CE时)，才认为满足Case 1。
当基于Case 2确定此Occasion对应的PDCCH接收/检测对应的QCL假设时，对于“为CORESET#0指示应用的TCI状态的MAC CE激活命令”的判断，可以沿用上述描述，对于“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断，描述如下：
当采用SSB传输方式1时，可以采用以下(I)和(II)中的任一方式：
(I)忽略Symbol type的影响，总是认为需要考虑针对“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断；
(II)仅当给定的Symbol type与SSB传输对应的单个Symbol type相同时，才需要考虑针对“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断，否则不需要考虑此判断；
当不需要考虑针对“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断时，可以理解为：如果UE没有收到为CORESET#0指示应用的TCI状态的MAC CE激活命令，则认为满足Case 2的判断条件，此时在确定此Occasion对应的PDCCH接收/检测对应的QCL假设/TCI state时，UE可以使用最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)中识别的SSB对应的QCL假设，或者，UE在初始接入过程中识别的SSB对应的QCL假设，或者，预定义的QCL假设/TCI state(可以由协议规定或由高层信令配置)；
当需要考虑针对“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断时，沿用上述Case2中的操作即可(此时必然只有一套SSB到RO的映射，随机接入过程无需再区分Symbol type)。
当采用SSB传输方式2时，如果采用SSB属性方式1，则可以沿用采用SSB传输方式1时的操作；如果采用SSB属性方式2，可以采用以下(III)和(IV)中的任一方式：
(III)任意随机接入过程(可进一步要求随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)都满足“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断(即匹配此判断中的“随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”)；
(IV)与给定的Symbol type对应的随机接入过程(可进一步要求随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)才满足“最近的一次随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”的判断(即匹配此判断中的“随机接入过程(可进一步要求此随机接入过程不由用于触发无竞争随机接入过程的PDCCH命令发起)”)。
这里“与给定的Symbol type对应的随机接入过程”可以理解为基于给定的Symbol type对应的SSB传输属性的SSB选择，和/或，给定的Symbol type对应的RO资源(一般地，给定的Symbol type存在对应的SSB到RO的映射)发起的随机接入过程。
对于某个Index不为0的CORESET(假设其对应的Symbol type为给定的Symbol type)对应的PDCCH接收/检测(或者，该CORESET内的PDCCH接收/检测)，在确定其对应的QCL假设/TCI state时，当采用SSB属性方式2时，包括以下(V)和(VI)中的至少一项：
(V)如果网络侧设备没有通过tci-StatesPDCCH-ToAddList和tci-StatesPDCCH-ToReleaseList为UE针对该CORESET提供TCI状态的配置，或者，网络侧设备已经通过tci-StatesPDCCH-ToAddList和tci-StatesPDCCH-ToReleaseList为UE针对该CORESET提供了包含一个以上的TCI状态的初始配置，但是UE没有收到为该CORESET激活其中一个TCI状态的MAC CE激活命令，则UE假设与PDCCH接收关联的专用解调参考信号(Dedicated demodulation reference signals，DM-RS)天线端口，与UE在初始接入过程中识别的并与给定Symbol type对应的SSB准共址；
(VI)如果网络侧设备已经通过tci-StatesPDCCH-ToAddList和tci-StatesPDCCH-ToReleaseList为UE针对该CORESET提供了包含一个以上的TCI状态的配置，作为涉及同步的重配过程(Reconfiguration with sync procedure)，但是UE没有收到为该CORESET激活其中一个TCI状态的MAC CE激活命令，则UE假设与PDCCH接收关联的DM-RS天线端口，与UE在由此涉及同步的重配过程发起的随机接入过程中识别的并与给定Symbol type对应的SSB或CSI-RS资源准共址。
以下以第一下行接收包括PDSCH为例，对PDSCH接收的相关实施方式进行说明。
在一些实施例中，所述第一下行接收包括PDSCH；
所述方法还包括：
所述终端接收来自网络侧设备的第三信息，所述第三信息用于指示如下至少一项：
所述第一下行接收对应的所有时域单元对应的激活传输参数；
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
可选地，所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过同一个MAC CE指示；或者，
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示。
这里，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示，可以理解为，使用独立的MAC CE来分别指示各个时域类型对应的时域单元各自对应的激活传输参数。
可选地，在通过同一个MAC CE指示所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
N个第六指示域，所述N个第六指示域用于分别指示所述N个时域类型中的各个时域类型对应的激活传输参数；
第七指示域，所述第七指示域用于联合指示所述N个时域类型中的各个时域类型对应的激活传输参数。
可选地，在通过不同的MAC CE指示所述第一下行接收的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
第八指示域，用于指示所述MAC CE对应的时域类型；
第九指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
在所述第一下行接收需要应用所述第三信息指示的传输参数的情况下，所述终端从所述第三信息指示的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数的情况下，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型相同的情况下，所述终端将所述PDCCH的CORESET对应的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型不同的情况下，所述终端将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型不包含所述第一下行接收对应的时域类型的情况下，所述终端将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型包含所述第一下行接收对应的时域类型的情况下，所述终端从所述PDCCH的CORESET对应的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用缺省传输参数的情况下，所述终端将所述第一时域类型对应的缺省传输参数确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用初始传输参数的情况下，所述终端将所述第一时域类型对应的初始传输参数确定为所述第一下行接收对应的传输参数。
为了便于理解，本申请实施例对PDSCH接收对应的TCI state激活(Activation)/去激活(Deactivation)方式进行示例性说明。
对于PDSCH接收对应的TCI state的激活/去激活，可以采用PDSCH TCI state激活方式1和PDSCH TCI state激活方式2中的任一方式：
PDSCH TCI state激活方式1：不区分Symbol type，确定统一使用/跨Symbol type共享使用的激活(Activated)TCI states(Activated TCI states可以理解为一个或多个激活TCI state，或者，至少一个激活TCI state；下面都沿用这里的理解，不再赘述)。
PDSCH TCI state激活方式1可以与通用TCI state配置方式1对应。
可以使用与Symbol type无关(或不考虑Symbol type的影响)的MAC CE来激活/去激活统一的配置TCI state集合中的各个TCI state，以确定统一使用/跨Symbol type共享使用的Activated TCI states。这里的MAC CE可以理解为特定UE的PDSCH的TCI状态的激活/去激活的MAC CE(TCI States Activation/Deactivation for UE-specific PDSCH MAC CE)，或者与其功能相同或类似的MAC CE。
对于PDSCH TCI state激活方式1，可以沿用特定UE的PDSCH的TCI状态的激活/去激活的MAC CE的现有格式定义。基于该MAC CE确定的Activated TCI states中的某个TCI state可以应用于任意Symbol type对应的PDSCH接收，或者说，不限制Activated TCI states中任意TCI state应用的PDSCH接收对应的Symbol type。
PDSCH TCI state激活方式2：为不同Symbol type分别确定各自的Activated TCI states。
一般地，PDSCH TCI state激活方式2与通用TCI state配置方式2对应。可选地，PDSCH TCI state激活方式2也可以与通用TCI state配置方式1对应。
在使用MAC CE激活/去激活各个Symbol type对应的TCI state，以确定各个Symbol type各自对应的Activated TCI states时，可以采用PDSCH TCI state激活方式2-1和PDSCH TCI state激活方式2-2中的任一方式：
PDSCH TCI state激活方式2-1：使用相同的MAC CE来激活/去激活各个(或至少一个)Symbol type对应的TCI state。
PDSCH TCI state激活方式2-1可以理解为，单个MAC CE可以用于激活/去激活超过一个Symbol type对应的TCI state。具体地，可以采用PDSCH TCI state激活方式2-1-1至PDSCH TCI state激活方式2-1-3中的任一方式：
PDSCH TCI state激活方式2-1-1：在不同Symbol type对应的TCI state的TCI-StateId取值相互不冲突的情况下，沿用TCI States Activation/Deactivation for UE-specific PDSCH MAC CE的现有格式定义，MAC CE中的每个TCI state激活/去激活状态指示比特基于TCI-StateId与某个配置的TCI state对应。
PDSCH TCI state激活方式2-1-1可以应用于通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3。
PDSCH TCI state激活方式2-1-2：调整TCI States Activation/Deactivation for UE-specific PDSCH MAC CE的现有格式定义，或者引入一种新的MAC CE，MAC CE中的TCI state激活/去激活状态指示比特不显式区分Symbol type分别设置，每个TCI state激活/去激活状态指示比特基于统一的配置TCI state集合中的位置与某个配置的TCI state对应。
这里，统一的配置TCI state集合中的位置，可以理解为统一的配置TCI state集合中的各个TCI state在该集合(要求以有序集合的方式维护)中的序号或下标。
PDSCH TCI state激活方式2-1-2可以应用于通用TCI state配置方式2-1、通用TCI state配置方式2-2。
PDSCH TCI state激活方式2-1-3：调整TCI States Activation/Deactivation for UE-specific PDSCH MAC CE的现有格式定义，或者引入一种新的MAC CE，在MAC CE中区分Symbol type分别设置各个Symbol type对应的TCI state激活/去激活状态指示比特。
对于某个Symbol type对应的TCI state激活/去激活状态指示比特，每个比特可以基于(9)和(10)中的任一项，与该Symbol type适用的某个TCI state对应：
(9)TCI-StateId；
(10)配置TCI state集合中的位置。
各Symbol type对应的TCI state激活/去激活状态指示比特，可以基于Symbol type的顺序在MAC CE中依次排列。Symbol type的顺序可以由协议规定或由高层信令配置。例如，由协议规定在某个MAC CE中，先出现non-SBFD symbol对应的TCI state激活/去激活状态指示比特，然后在其后再出现SBFD symbol对应的TCI state激活/去激活状态指示比特。
PDSCH TCI state激活方式2-1-3可以应用于通用TCI state配置方式1、通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3，相关操作描述如下：
其一，基于TCI-StateId的对应。
当基于TCI-StateId对应时，对于某个Symbol type，其对应的TCI state激活/去激活状态指示比特(可称其为第一比特序列)中的第一个比特可以与取值为0的TCI-StateId对应，第一比特序列中的剩余比特与其它取值的TCI-StateId依次对应(即第一比特序列中的第二个比特对应取值为1的TCI-StateId，以此类推)。第一比特序列的长度由高层信令配置，或者基于为该Symbol type配置的TCI-StateId最大值确定(例如长度＝TCI-StateId最大值+1)，或者基于协议规定的TCI-StateId最大值确定。
可选地，如果在通用TCI state配置方式2-1中，各个Symbol type分别对应不同的TCI-StateId取值范围，则第一比特序列中的第一个比特可以与该Symbol type对应的TCI-StateId取值范围(可称其为第一ID范围)中的最小TCI-StateId对应，第一比特序列中的剩余比特与第一ID范围中的剩余TCI-StateId逐一对应(相应的，第一比特序列的长度为第一ID范围内包含的TCI-StateId数目)；如果在通用TCI state配置方式2-1中基于TCI state的新参数区分Symbol type，则对于某个Symbol type，该Symbol type对应的配置TCI state集合(可称其为第一TCI state集合)中的最小TCI-StateId可以与第一比特序列中的第一个比特对应，第一TCI state集合中的剩余TCI state可以基于TCI-StateId从小到大的顺序与第一比特序列中的剩余比特逐一对应。
其二，基于配置TCI state集合中位置的对应。
当基于配置TCI state集合中的位置对应时，对于某个Symbol type，其对应的TCI state激活/去激活状态指示比特(可称其为第二比特序列)中的第一个比特可以与统一的配置TCI state集合(当应用于通用TCI state配置方式1时)中的第一个TCI state对应，或者，与该Symbol type对应的配置TCI state集合(当应用于通用TCI state配置方式2时)中的第一个TCI state对应，第二比特序列中的剩余比特与该集合中的其它TCI state依次对应(即第二比特序列中的第二个比特对应该集合中的下一个TCI state，以此类推；这里假设统一的配置TCI state集合或者各个Symbol type对应的配置TCI state集合为有序集合)。第二比特序列的长度由高层信令配置，或者基于允许为单个Symbol type配置的TCI state最大数目确定。
PDSCH TCI state激活方式2-2：使用独立的MAC CE来激活/去激活每个(或某个)Symbol type对应的TCI state。
PDSCH TCI state激活方式2-2可以理解为，单个MAC CE仅用于激活/去激活单个Symbol type对应的TCI state，在MAC CE中包含用于指示Symbol type的信息/字段。
当某个MAC CE用于激活/去激活某个Symbol type对应的TCI state时，该MAC CE中的每个TCI state激活/去激活状态指示比特可以基于(11)和(12)中的任一项，与某个TCI state对应：
(11)TCI-StateId；
(12)配置TCI state集合中的位置。
PDSCH TCI state激活方式2-2可以应用于通用TCI state配置方式1、通用TCI state配置方式2-1、通用TCI state配置方式2-2和通用TCI state配置方式2-3，相关操作描述如下：
其一，基于TCI-StateId的对应。
当基于TCI-StateId对应时，MAC CE中的TCI state激活/去激活状态指示比特(可称其为第三比特序列)中的第一个比特可以与取值为0的TCI-StateId对应，第三比特序列中的剩余比特与其它取值的TCI-StateId依次对应(即第三比特序列中的第二个比特对应取值为1的TCI-StateId，以此类推)。第三比特序列的长度由高层信令配置，或者基于为该Symbol type配置的TCI-StateId最大值确定(例如长度＝TCI-StateId最大值+1)，或者基于协议规定的TCI-StateId最大值确定。
可选地，如果在通用TCI state配置方式2-1中各个Symbol type分别对应不同的TCI-StateId取值范围，则第三比特序列中的第一个比特可以与该Symbol type对应的TCI-StateId取值范围(可称其为第二ID范围)中的最小TCI-StateId对应，第三比特序列中的剩余比特与第二ID范围中的剩余TCI-StateId逐一对应(相应的，第三比特序列的长度为第二ID范围内包含的TCI-StateId数目)；如果在通用TCI state配置方式2-1中基于TCI state的新参数区分Symbol type，则该Symbol type对应的配置TCI state集合(可称其为第二TCI state集合)中的最小TCI-StateId可以与第三比特序列中的第一个比特对应，第二TCI state集合中的剩余TCI state可以基于TCI-StateId从小到大的顺序与第三比特序列中的剩余比特逐一对应。
其二，基于配置TCI state集合中位置的对应。
当基于配置TCI state集合中的位置对应时，MAC CE中的TCI state激活/去激活状态指示比特(可称其为第四比特序列)中的第一个比特可以与统一的配置TCI state集合(当应用于通用TCI state配置方式1时)或者该Symbol type对应的配置TCI state集合(当应用于通用TCI state配置方式2时)中的第一个TCI state对应，第四比特序列中的剩余比特与该集合中的其它TCI state依次对应(即第四比特序列中的第二个比特对应该集合中的下一个TCI state，以此类推；这里假设统一的配置TCI state集合或者各个Symbol type对应的配置TCI state集合为有序集合)。第四比特序列的长度由高层信令配置，或者基于允许为单个Symbol type配置的TCI state最大数目确定。
对于某个PDSCH接收应用的QCL假设/TCI state，包括(a)至(d)中的至少一项：
(a)对于应用指示的TCI state的情况。
“应用指示的TCI state的情况”可以包括在下行调度DCI(包括DCI format 1_1/1_2等)中存在TCI指示域，并且下行调度DCI与被调度的PDSCH之间的时间偏移大于或等于预定义门限(例如由参数timeDurationForQCL指示)的情况。
当采用通用TCI state配置方式1，以及PDSCH TCI state激活方式1时，任意Symbol type对应的PDSCH接收都共用统一的配置TCI state集合，以及同一套Activated TCI states。此时对于应用调度DCI中指示的TCI state的情况(例如，应用调度DCI中指示的TCI state的典型情况包括：某个PDSCH由存在TCI指示域的DCI调度，并且该DCI的接收和该PDSCH之间的时间偏移等于或大于预定义门限timeDurationForQCL；此预定义门限基于报告的UE能力确定)，无论PDSCH接收对应哪个Symbol type(或位于哪个Symbol type对应的Symbol内)，调度DCI中的相关指示域(例如，TCI指示域)总是从此套Activated TCI states中指示此PDSCH接收应用的TCI state(s)。
当采用通用TCI state配置方式2，以及PDSCH TCI state激活方式2时，每个Symbol type可对应各自的配置TCI state集合，以及各自的Activated TCI states。此时对于应用调度DCI中指示的TCI state的情况，调度DCI中的相关指示域从PDSCH接收对应的Symbol type(或者PDSCH接收所在Symbol(s)对应的Symbol type)对应的Activated TCI states中指示此PDSCH接收应用的TCI state(s)。
(b)对于应用PDCCH的QCL假设/TCI state的情况。
“应用PDCCH的QCL假设/TCI state的情况”可以包括在下行调度DCI(包括DCI format 1_0/1_1/1_2等)中不存在TCI指示域，并且下行调度DCI与被调度的PDSCH之间的时间偏移大于或等于预定义门限(例如由参数timeDurationForQCL指示)的情况。
当采用通用TCI state配置方式1，以及PDCCH TCI state指示方式1时，CORESET的TCI state不用区分Symbol type，此时沿用相关规范中定义的操作(即下文中的操作0)即可。
当采用通用TCI state配置方式2，以及PDCCH TCI state指示方式2时，需要区分Symbol type确定CORESET适用的TCI state。此时可以采用(b1)和(b2)中的任一项：
(b1)UE期望PDSCH接收与对应的PDCCH各自对应的Symbol type相同；
此时由网络侧保证PDSCH接收与对应的PDCCH各自对应的Symbol type相同。相应地，UE可沿用相关规范中定义的操作(即下文中的操作0)。
(b2)允许PDSCH接收与对应的PDCCH各自对应的Symbol type不同；
当PDSCH接收与对应的PDCCH各自对应的Symbol type相同时，沿用上述操作(即下文中的操作0)。
当PDSCH接收与对应的PDCCH各自对应的Symbol type不同时，可以采用(b21)至(b23)的其中一项：
(b21)执行操作1；
(b22)当PDCCH的CORESET基于Occasion对应的至少一个Symbol type中不包含PDSCH接收对应的Symbol type时，执行操作1；
(b23)当PDCCH的CORESET基于Occasion对应的至少一个Symbol type中包含PDSCH接收对应的Symbol type时，执行操作2。
上述操作0/1/2描述如下(假设PDSCH接收对应的Symbol type为第一Symbol type)：
操作0：PDSCH接收应用对应的PDCCH的QCL假设/TCI state；
操作0可以理解为：UE假设PDSCH的TCI状态或QCL假设与应用于对应的PDCCH接收的CORESET的TCI状态或QCL假设相同。
可进一步要求上面提及的应用于对应的PDCCH接收的CORESET的TCI状态或QCL假设，是该CORESET在与该PDSCH对应的PDCCH接收所在Symbol内应用的QCL假设/TCI state。
操作1：PDSCH接收应用第一Symbol type对应的缺省QCL假设，或者应用预定义的TCI state。
缺省QCL假设参见下文中的相关描述。
预定义的TCI state可以由协议规定或由高层信令配置；可以区分Symbol type分别确定，或者不区分Symbol type统一确定。
操作2：PDSCH接收应用对应的PDCCH对应的CORESET与第一Symbol type对应的TCI state。
操作2可以理解为：如果某个PDSCH由不存在TCI指示域的DCI调度，并且该DCI的接收和该PDSCH之间的时间偏移等于或大于预定义门限timeDurationForQCL(此预定义门限基于报告的UE能力确定)，在确定该PDSCH的天线端口的准共址时，UE假设该PDSCH的QCL假设/TCI状态与目标QCL假设/TCI状态相同；这里的目标QCL假设/TCI状态为用于承载该DCI的PDCCH接收的CORESET应用的QCL假设/TCI状态中，与第一Symbol type对应的QCL假设/TCI状态。
可进一步要求上面提及的目标QCL假设/TCI状态，是该CORESET在该PDSCH接收所在Symbol内与第一Symbol type对应的QCL假设/TCI state。
(c)对于应用初始QCL假设的情况。
“应用初始QCL假设的情况”可以包括下行调度DCI(包括DCI format 1_0/1_1/1_2等)与被调度的PDSCH之间的时间偏移小于预定义门限(例如由参数timeDurationForQCL指示)的情况。
当采用SSB传输方式1，或者，采用SSB传输方式2且采用SSB属性方式1时，可沿用相关规范中定义的操作(即被调度的PDSCH与UE在初始接入过程中确定的SSB准共址)。
当采用SSB传输方式2且采用SSB属性方式2时，如果对于调度PDSCH的CORESET(即UE在此CORESET内检测到承载下述调度PDSCH的DCI的PDCCH)，tci-PresentInDCI被设置为“使能”('enabled')，或者配置了tci-PresentDCI-1-2参数，并且DCI接收和对应PDSCH之间的时间偏移等于或大于timeDurationForQCL，在UE接收到针对TCI状态的初始高层配置并在接收激活命令之前，UE可以假设该PDSCH的DM-RS端口与在初始接入过程中确定并与给定Symbol type对应的SSB准共址，准共址类型(QCL Type，可对应参数qcl-Type)为类型A('typeA')，并且在可用的情况下，准共址类型也为类型D('typeD')。
(d)对于应用缺省QCL假设的情况。
当采用通用TCI state配置方式1，以及PDCCH TCI state指示方式1时，CORESET的TCI state不用区分Symbol type，此时沿用相关规范中定义的操作即可。
当采用通用TCI state配置方式2，以及PDCCH TCI state指示方式2时，需要区分Symbol type确定CORESET适用的TCI state。此时假设PDSCH接收对应的Symbol type为第一Symbol type，则UE确定该PDSCH接收应用所在服务小区上第一Symbol type对应的缺省QCL假设(该PDSCH接收所在服务小区上第一Symbol type对应的缺省QCL假设为：与目标时隙内的目标CORESET用于PDCCH QCL指示的QCL参数涉及/对应的RS准共址；这里的目标时隙为UE需要在该PDSCH接收所在服务小区的激活BWP内监听一个或多个CORESET，并且与第一Symbol type对应的最晚时隙；这里的目标CORESET为，目标时隙内的一个或多个需要监听的CORESET中，关联了需要监听的搜索空间，且controlResourceSetId最小的CORESET)。具体的操作包括：
在RRC连接模式下，无论tci-PresentInDCI和tci-PresentDCI-1-2怎样配置(或者说，独立于tci-PresentInDCI和tci-PresentDCI-1-2的配置)，如果网络侧设备未向UE提供dl-OrJointTCI-StateList-r17，并且DCI的接收与对应PDSCH之间的时间偏移小于预定义门限timeDurationForQCL，并且网络侧设备为被调度的PDSCH所在服务小区配置了至少一个将qcl-Type设置为'typeD'的TCI状态，则UE执行以下(e)和(f)中的至少一项：
(e)UE可以假设PDSCH的DM-RS端口与目标时隙内的目标CORESET用于PDCCH QCL指示的QCL参数涉及/对应的RS准共址，其中，目标时隙为UE需要在该PDSCH所在服务小区的激活BWP内监听一个或多个CORESET，并且与该PDSCH对应的Symbol type对应的最晚时隙，目标CORESET为目标时隙内的一个或多个需要监听的CORESET中，关联了需要监听的搜索空间，且controlResourceSetId最小的CORESET。
(f)如果网络侧设备为UE配置了enableDefaultTCI-StatePerCoresetPoolIndex，并且为UE配置的高层参数PDCCH-Config中，在不同的ControlResourceSet中涉及/包含两个不同的coresetPoolIndex值，则UE可以假设关联了某个coresetPoolIndex值的PDSCH(即调度该PDSCH的PDCCH接收所在CORESET关联了该coresetPoolIndex值)的DM-RS端口与目标时隙内的目标CORESET用于PDCCH QCL指示的QCL参数涉及/对应的RS准共址，其中，目标时隙为UE需要在该PDSCH所在服务小区的激活BWP内监听一个或多个关联了该coresetPoolIndex值的CORESET，并且与该PDSCH对应的Symbol type对应的最晚时隙，目标CORESET为目标时隙内的一个或多个需要监听且关联了该coresetPoolIndex值的CORESET中，关联了需要监听的搜索空间，且controlResourceSetId最小的CORESET。
以下以第一下行接收包括与第一NZP CSI-RS资源对应的CSI-RS为例，对第一NZP CSI-RS资源对应的CSI-RS接收的相关实施方式进行说明。
在一些实施例中，所述第一下行接收包括与第一NZP CSI-RS资源对应的CSI-RS；
在所述第一NZP CSI-RS资源为周期性或半持续资源的情况下，所述第一NZP CSI-RS资源对应的接收时机所在时域单元对应同一个时域类型，或者，所述第一NZP CSI-RS资源对应的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，所述方法还包括：
所述终端接收来自网络侧设备的第四信息，所述第四信息用于指示如下至少一项：
所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
可选地，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
在所述第一NZP CSI-RS资源为非周期性资源，并且与所述第一NZP CSI-RS资源对应的CSI-RS需要应用缺省传输参数的情况下，所述终端将所述第一时域类型对应的缺省传输参数确定为与所述第一NZP CSI-RS资源对应的CSI-RS对应的传输参数。
为了便于理解，本申请实施例对NZP CSI-RS接收对应的TCI state配置、确定方式进行示例性说明。
NZP CSI-RS一般以NZP CSI-RS资源(resource)的粒度进行配置和使用，NZP CSI-RS resource可进一步区分周期性(Periodic)、半持续(Semi-persistent)和非周期性(Aperiodic)三种资源类型。在较多应用场景中，一般将NZP CSI-RS resource进一步组织成NZP CSI-RS资源集(resource set)的形式使用(包括触发传输、引用等)。
对于资源类型为Periodic或Semi-persistent的NZP CSI-RS resource，可以在时域对应多个Occasion(或者至少一个Occasion)。相应地，对于某个Periodic/Semi-persistent NZP CSI-RS resource的时频位置的配置，可以采用CSI-RS Occasion配置方式1和CSI-RS Occasion配置方式2中的任一方式：
CSI-RS Occasion配置方式1：该NZP CSI-RS resource对应的Occasion仅能位于单个Symbol type对应的Symbol内。
这里的单个Symbol type(给定Symbol type)可以采用(g)至(j)中的任一项确定：
(g)基于该NZP CSI-RS resource的NZP-CSI-RS-ResourceId所在的NZP-CSI-RS-ResourceId取值范围，确定给定Symbol type。这里假设各个Symbol type各自对应一个独立的NZP-CSI-RS-ResourceId取值范围，可以由协议规定或由高层信令配置；不同Symbol type对应的NZP-CSI-RS-ResourceId取值范围相互之间不存在交集。当配置某个Symbol type对应的NZP CSI-RS resource时，该NZP CSI-RS resource的NZP-CSI-RS-ResourceId要求位于与该Symbol type对应的NZP-CSI-RS-ResourceId取值范围内。
(h)在每个NZP CSI-RS resource的配置信息中，引入新的参数指示该NZP CSI-RS resource对应的Symbol type。
(i)基于该NZP CSI-RS resource的配置/激活信息，确定NZP CSI-RS resource Occasion所在的Symbol对应的Symbol type。
(j)由协议规定或由高层参数配置给定Symbol type。例如，由协议规定NZP CSI-RS resource对应的Occasion仅能位于non-SBFD symbol内。
此时，既可以由网络侧在配置/激活时保证该NZP CSI-RS resource对应的所有Occasion仅位于给定Symbol type对应的Symbol内，也可以网络侧在配置时不保证该NZP CSI-RS resource对应的任意Occasion仅出现在给定Symbol type对应的Symbol内，但UE仅认为位于给定Symbol type对应的Symbol内(完整位于给定Symbol type对应的Symbol内，或者位于给定Symbol type对应的Symbol内的Symbol数目不少于M，或者位于给定Symbol type对应的Symbol内的Symbol比例不小于N)的Occasion生效，或者，认为不位于给定Symbol type对应的Symbol内(不完整位于给定Symbol type对应的Symbol内，或者位于给定Symbol type对应的Symbol内的Symbol数目少于M，或者位于给定Symbol type对应的Symbol内的Symbol比例小于N)的Occasion无效。
CSI-RS Occasion配置方式2：该NZP CSI-RS resource对应的Occasion可位于各个(或大于一个)Symbol type对应的Symbol内。
CSI-RS Occasion配置方式2可以理解为，网络侧在配置时无需关注或保证该NZP CSI-RS resource对应的Occasion位于哪些Symbol type对应的Symbol内。例如，该NZP CSI-RS resource对应的Occasion可能都位于SBFD symbol内，或者都位于non-SBFD symbol内，或者部分Occasion位于SBFD symbol内，部分Occasion位于non-SBFD symbol内。
可选地，对于该NZP CSI-RS resource的某个Occasion，将此Occasion所在Symbol对应的Symbol type，作为此Occasion对应的Symbol type。
对于Periodic NZP CSI-RS，针对每个NZP CSI-RS resource独立配置TCI state；对于Semi-persistent NZP CSI-RS，在使用SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE激活某个Semi-persistent NZP CSI-RS resource set时会针对此Set中的每个Semi-persistent NZP CSI-RS resource分别指示其对应的TCI State。对于启用了SBFD的Serving cell/BWP，在为某个Periodic/Semi-persistent NZP CSI-RS resource配置/指示TCI state(可以理解为为此Periodic NZP CSI-RS resource通过高层信令配置TCI state，或者，为此Semi-persistent NZP CSI-RS resource通过MAC CE指示TCI state)时，可以采用CSI-RS TCI state确定方式1和CSI-RS TCI state确定方式2中的任一方式：
CSI-RS TCI state确定方式1：不区分Symbol type，配置/指示该NZP CSI-RS resource的所有Occasion统一使用/跨Symbol type共享使用的TCI state。
CSI-RS TCI state确定方式1与通用TCI state配置方式1对应，并且可同时应用于CSI-RS Occasion配置方式1和CSI-RS Occasion配置方式2。
对于CSI-RS TCI state确定方式1，对于Periodic NZP CSI-RS resource，可以配置为NZP-CSI-RS-Resource->qcl-InfoPeriodicCSI-RS(这里使用“->”表示前一个消息或字段中的某个字段，例如参数NZP-CSI-RS-Resource->qcl-InfoPeriodicCSI-RS表示NZP-CSI-RS-Resource字段中的qcl-InfoPeriodicCSI-RS参数，全文中的类似表述都沿用这里的解释)；对于Semi-persistent NZP CSI-RS resource，可以沿用MAC CE中的指示域，例如TCI State IDi。基于现有配置参数为此Periodic NZP CSI-RS resource配置，或者，基于MAC CE指示域为此Semi-persistent NZP CSI-RS resource指示的单个TCI state可以应用于该NZP CSI-RS resource与任意Symbol type对应的Occasion，或者说，不限制该NZP CSI-RS resource应用配置的TCI state的Occasion对应的Symbol type。
CSI-RS TCI state确定方式2：为该NZP CSI-RS resource与不同Symbol type对应的Occasion分别配置/指示各自的TCI state。
一般地，CSI-RS TCI state确定方式2与通用TCI state配置方式2对应。可选地，CSI-RS TCI state确定方式2也可以与通用TCI state配置方式1对应。CSI-RS TCI state确定方式2主要应用于CSI-RS Occasion配置方式2，也可以应用于CSI-RS Occasion配置方式1。
当采用通用TCI state配置方式2时，需要由网络侧保证为某个Symbol type配置/指示的TCI state位于该Symbol type对应的配置TCI state集合中。
对于Aperiodic NZP CSI-RS，在每个触发状态的配置信息(例如，对应配置参数CSI-AperiodicTriggerState)中为用于Channel measurement的每个Aperiodic NZP CSI-RS resource独立配置TCI state。对于启用了SBFD的Serving cell/BWP，在为某个Aperiodic NZP CSI-RS resource配置TCI state时，可以采用CSI-RS TCI state配置方式1和CSI-RS TCI state配置方式2中的任一方式：
CSI-RS TCI state配置方式1：不区分Symbol type，配置该NZP CSI-RS resource使用的TCI state。
CSI-RS TCI state配置方式1与通用TCI state配置方式1对应。
对于CSI-RS TCI state配置方式1，可以采用CSI-AssociatedReportConfigInfo->resourcesForChannel->nzp-CSI-RS->qcl-info，为此Aperiodic NZP CSI-RS resource配置的单个TCI state应用于该NZP CSI-RS resource被触发的单个Occasion(可以与任意Symbol type对应)。
CSI-RS TCI state配置方式2：为该NZP CSI-RS resource与不同Symbol type对应的Occasion分别配置各自的TCI state。
一般地，CSI-RS TCI state配置方式2与通用TCI state配置方式2对应。可选地，CSI-RS TCI state配置方式2也可以与通用TCI state配置方式1对应。
基于该NZP CSI-RS resource被触发的单个Occasion对应的Symbol type，使用与其对应的TCI state。可选地，仅为该NZP CSI-RS resource预期被触发的Occasion对应的Symbol type配置对应的TCI state(当基于可能的触发情况预期存在多个Symbol type时，分别为每个Symbol type配置对应的TCI state)。
当采用通用TCI state配置方式2时，需要由网络侧保证为某个Symbol type配置/指示的TCI state位于该Symbol type对应的配置TCI state集合中。
此外，对于Aperiodic NZP CSI-RS应用缺省QCL假设的情况：当采用通用TCI state配置方式1，以及CSI-RS TCI state配置方式1时，Aperiodic NZP CSI-RS的TCI state不用区分Symbol type，此时沿用相关规范中定义的操作即可；当采用通用TCI state配置方式2，以及CSI-RS TCI state配置方式2时，需要区分Symbol type确定Aperiodic NZP CSI-RS适用的TCI state。此时假设Aperiodic NZP CSI-RS接收对应的Symbol type为第一Symbol type，则UE确定Aperiodic NZP CSI-RS接收应用所在服务小区上第一Symbol type对应的缺省QCL假设(该Aperiodic NZP CSI-RS接收所在服务小区上第一Symbol type对应的缺省QCL假设为：目标时隙内的目标CORESET使用的QCL假设；这里的目标时隙为UE需要在该Aperiodic NZP CSI-RS接收所在服务小区的激活BWP内监听一个或多个CORESET，并且与第一Symbol type对应的最晚时隙；这里的目标CORESET为，目标时隙内的一个或多个需要监听的CORESET中，关联了需要监听的搜索空间，且controlResourceSetId最小的CORESET)。具体的操作包括：
如果承载Aperiodic NZP CSI-RS接收对应的触发DCI的PDCCH的最后一个Symbol与该Aperiodic NZP CSI-RS接收对应的NZP CSI-RS资源集合(即NZP-CSI-RS-ResourceSet；可进一步要求没有为该NZP-CSI-RS-ResourceSet配置高层参数trs-Info)中的非周期CSI-RS资源的第一个Symbol之间的调度偏移小于目标门限，则执行如下操作：如果网络侧设备未向UE提供dl-OrJointTCI-StateList，并且该Aperiodic NZP CSI-RS接收所在BWP配置了至少一个CORESET，在接收该Aperiodic NZP CSI-RS时，UE应用目标时隙内的目标CORESET使用的QCL假设，目标时隙为UE需要在该Aperiodic NZP CSI-RS接收所在服务小区的激活BWP内监听一个或多个CORESET，并且与第一Symbol type对应的最晚时隙，目标CORESET为目标时隙内的一个或多个需要监听的CORESET中，关联了需要监听的搜索空间，且controlResourceSetId最小的CORESET。
上述目标门限可以由协议规定或由高层信令配置。例如，
当UE上报的门限值beamSwitchTiming为的其中一个值，且网络侧设备未向UE提供enableBeamSwitchTiming时，目标门限为UE上报的门限值beamSwitchTiming；
当UE上报了beamSwitchTiming-r16，且网络侧设备向UE提供了enableBeamSwitchTiming，且为该NZP-CSI-RS-ResourceSet配置了高层参数重复(repetition)并设置为'off'，或未为该NZP-CSI-RS-ResourceSet配置高层参数repetition时，目标门限为
当网络侧设备向UE提供了enableBeamSwitchTiming，且为该NZP-CSI-RS-ResourceSet配置了高层参数repetition并设置为'on'时，目标门限为UE上报的门限值beamSwitchTiming-r16。
以下以第一测量包括CSI测量为例，对CSI测量对应的相关实施方式进行说明。
在一些实施例中，所述第一测量包括CSI测量；
所述方法还包括：
在所述第一测量的上报需要区分时域类型的情况下，所述终端确定目标CSI报告(report)对应的目标CSI参考资源；
所述终端执行如下操作中的至少一项：
基于是否接收到至少一个目标CSI-RS接收时机，确定是否上报目标CSI报告；
在所述目标CSI报告为周期性或半持续CSI报告的情况下，基于最晚的所述目标CSI-RS接收时机，确定CPU占用的起始时刻；
使用至少一个所述目标CSI-RS接收时机，确定所述第一测量包含的目标信息；所述目标信息包括层一L1参考信号接收功率(reference signal received power，RSRP)、L1信号与干扰加噪声比(signal-to-noise and interference ratio，SINR)、信道质量指示(Channel quality indicator，CQI)中的至少一项；
其中，所述目标CSI报告与第二时域类型对应；所述目标CSI-RS接收时机与所述第二时域类型对应，且所述目标CSI-RS接收时机不晚于所述目标CSI参考资源。
为了便于理解，本申请实施例对CSI测量对应的CSI上报的相关操作进行示例性说明。
当区分Symbol type作CSI上报时，在确定与给定Symbol type对应的某个CSI report对应的CSI reference resource之后，包括(k)操作至(m)操作中的至少一项：
(k)判断是否忽略CSI上报；
在CSI报告配置或重配置、服务小区激活、BWP变更、或SP-CSI激活之后，UE仅当收到与给定Symbol type对应，且不晚于CSI参考资源的至少一个用于信道测量的CSI-RS传输时机，以及用于干扰测量的CSI-RS和/或CSI干扰测量(CSI Intereference Measurement，CSI-IM)时机，才会上报与给定Symbol type对应的CSI报告；否则将丢弃该CSI报告。
当配置了非连续接收(Discontinuous Reception，DRX)时，UE仅当在DRX激活时间内收到与给定Symbol type对应，且不晚于CSI参考资源的至少一个用于信道测量的CSI-RS传输时机，以及用于干扰测量的CSI-RS和/或CSI-IM时机，才会上报与给定Symbol type对应的CSI报告；否则将丢弃该CSI报告。
(l)确定CSI处理单元(CSI processing unit，CPU)占用情况；
当CSI报告为周期性或半持续时，CPU占用的起始时刻为：各个用于信道测量或干扰测量的CSI-RS/CSI-IM/SSB资源与给定Symbol type对应，且不晚于对应CSI参考资源的最晚CSI-RS/CSI-IM/SSB时机中，最早出现的时机的第一个符号。
(m)确定CSI参数；具体地，包括(m1)至(m3)中的至少一项：
(m1)确定L1-RSRP；
UE基于以下时机推导用于计算在上行时隙n中上报的L1-RSRP值对应的信道测量值：
CSI资源设置关联的SSB或NZP CSI-RS资源对应的时机中，与给定Symbol type对应，且不晚于CSI参考资源的：
最近的单个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为"Configured")；或者，
任意一到多个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为"notConfigured")。
(m2)确定L1-SINR；
UE基于以下时机推导用于计算在上行时隙n中上报的L1-SINR对应的信道测量值：
CSI资源设置关联的SSB或NZP CSI-RS资源对应的时机中，与给定Symbol type对应，且不晚于CSI参考资源的：
最近的单个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为'configured')；或者，
任意一到多个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为'notConfigured')。
UE基于以下时机推导用于计算在上行时隙n中上报的L1-SINR对应的干扰测量值：
CSI资源设置关联的CSI-IM或用于干扰测量的NZP CSI-RS资源或同时用于信道和干扰测量的NZP CSI-RS资源对应的时机中，与给定Symbol type对应，且不晚于CSI参考资源的：
最近的单个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForInterferenceMeasurements设置为'configured')；或者，
任意一到多个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForInterferenceMeasurements设置为'notConfigured')。
(m3)确定CQI；
UE基于以下时机推导用于计算在上行时隙n中上报的CSI值对应的信道测量值：
CSI资源设置关联的NZP CSI-RS资源对应的时机中，与给定Symbol type对应，且不晚于CSI参考资源的：
最近的单个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为"Configured")；或者，
任意一到多个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForChannelMeasurements设置为"notConfigured")。
UE基于以下时机推导用于计算在上行时隙n中上报的CSI值对应的干扰测量值：
CSI资源设置关联的CSI-IM和/或用于干扰测量的NZP CSI-RS资源对应的时机中，与给定Symbol type对应，且不晚于CSI参考资源的：
最近的单个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForInterferenceMeasurements设置为"Configured")；或者，
任意一到多个时机(如果CSI报告对应的CSI-ReportConfig中的timeRestrictionForInterferenceMeasurements设置为"notConfigured")。
以下以第一测量包括CLI测量为例，对CLI测量对应的相关实施方式进行说明。
在一些实施例中，所述第一测量包括CLI测量；
在基于所述第二时域类型对应的时域单元内的CLI测量资源执行所述第一测量的情况下，所述CLI测量资源对应的传输参数，包括如下至少一项：
在所述第二时域类型对应的时域单元内，最晚接收的PDSCH对应的传输参数；
与所述第二时域类型对应，且最晚接收的PDSCH对应的传输参数；
在所述第二时域类型对应的时域单元内，最晚监测的CORESET对应的传输参数；
与所述第二时域类型对应，且最晚监测的CORESET对应的传输参数；
在所述第二时域类型对应的时域单元内，最晚接收的PDSCH和最晚监测的CORESET中的较晚者对应的传输参数；
与所述第二时域类型对应的最晚接收的PDSCH和最晚监测的CORESET中，较晚者对应的传输参数。
可选地，所述CLI测量资源对应的传输参数包括QCL假设，所述QCL假设的类型包括类型D。
为了便于理解，本申请实施例对CLI测量进行示例性说明。
一般地，可假设仅针对SBFD symbol测量CLI(例如，在SBFD symbol内可测量inter-UE inter-subband CLI)，或者，可针对SBFD symbol和non-SBFD symbol分别测量CLI(例如，在non-SBFD symbol内可针对动态(Dynamic)TDD测量相邻(Adjacent)channel或共频信道(Co-channel)CLI等)。
当针对给定Symbol(假设其对应的Symbol type为给定Symbol type，对应上述的第二时域类型)测量CLI时，UE可以假设给定Symbol内配置的CLI测量资源(包括SRS资源，CLI-RSSI资源等)与以下其中一项QCL(即应用其对应的QCL假设/TCI state)：
在给定Symbol type对应的Symbol内最晚接收的PDSCH；
与给定Symbol type对应且最晚接收的PDSCH；
在给定Symbol type对应的Symbol内最晚监测的CORESET；
与给定Symbol type对应且最晚监测的CORESET；
在给定Symbol type对应的Symbol内最晚接收的PDSCH和最晚监测的CORESET中的较晚者；
与给定Symbol type对应的最晚接收PDSCH和最晚监测CORESET中的较晚者。
可选地，上述QCL的类型为TypeD。
可选地，上述假设仅针对FR2的CLI测量。
综上，对于启用了SBFD的Serving cell/BWP，下行Channel/Signal或测量Channel/Signal对应的QCL假设/TCI state的确定(包括配置、激活、指示等)，本申请实施例给出了各种可行的确定方式，以及相应的UE行为，从而可以匹配不同的SBFD部署场景，以灵活高效地实现SBFD operation。可见，本申请实施例能够实现终端在灵活双工场景下的下行接收或测量。
图4示出本申请实施例提供的一种下行接收和测量方法的流程图。如图4所示，下行接收和测量方法包括：
步骤401：网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
所述网络侧设备基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
可选地，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
所述第一下行接收所在时域单元对应同一个时域类型；或者，
所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
可选地所述第一下行接收包括SSB；
在所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型的情况下，所述网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
所述网络侧设备不区分所述第一下行接收所在时域单元对应的时域类型，将所述第一下行接收对应的传输参数统一确定为第一传输参数；
所述网络侧设备区分所述第一下行接收所在时域单元对应的时域类型，基于时域类型与传输参数之间的映射关系，确定所述第一下行接收在不同时域类型的时域单元内对应的传输参数。
可选地，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
所述方法还包括：
所述网络侧设备向终端发送第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
所述网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
所述网络侧设备基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
可选地，所述至少一个集合包括如下至少一项：
第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
可选地，所述传输参数的配置信息包括如下至少一项：
传输参数的标识，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的标识的取值确定；
传输参数的第一指示，所述第一指示用于指示时域类型，所述至少一个第二集合中的各个传输参数对应的时域类型为传输参数的第一指示所指示的时域类型。
可选地，所述第三集合包括一个或多个子集，所述第三集合的各个子集满足如下至少之一：
所述第三集合的各个子集按照预定顺序排序，所述预定顺序表示所述时域类型的顺序；
所述第三集合的各个子集包括的传输参数的数量按照预定义的方式分配，或者直接配置或指示。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述第一CORESET的接收时机所在时域单元对应同一个时域类型；或者，
所述第一CORESET的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，在所述第一CORESET的接收时机所在时域单元对应同一个时域类型的情况下，所述第一CORESET的接收时机所在时域单元对应的时域类型由如下至少一项确定：
所述第一CORESET的配置信息；
所述第一CORESET关联的搜索空间中，各个搜索空间的配置信息；
协议规定；
高层参数。
可选地，所述第一CORESET的配置信息，包括如下至少一项：
所述第一CORESET的标识，所述第一CORESET的标识的取值用于确定所述第一CORESET的接收时机所在时域单元对应的时域类型；
所述第一CORESET的第二指示，所述第二指示用于指示时域类型，所述第一CORESET的接收时机所在时域单元对应的时域类型为所述第二指示所指示的时域类型。
可选地，所述各个搜索空间的配置信息，包括如下至少一项：
所述各个搜索空间的标识，所述各个搜索空间的标识的取值用于分别确定所述各个搜索空间的接收时机所在时域单元对应的时域类型；
所述各个搜索空间的第三指示，所述第三指示用于指示时域类型，所述各个搜索空间的接收时机所在时域单元对应的时域类型为各个搜索空间的第三指示所指示的时域类型。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述方法还包括：
所述网络侧设备向终端发送第二信息，所述第二信息用于指示如下至少一项：
所述第一CORESET的所有接收时机对应的传输参数；
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
可选地，所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过同一个MAC CE指示；或者，
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
M个第一指示域，所述M个第一指示域用于分别指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数；
第二指示域，所述第二指示域用于联合指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数。
可选地，在通过不同的MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
第三指示域，用于指示所述MAC CE对应的时域类型；
第四指示域，用于指示对应时域类型所对应的传输参数；
第五指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述第一下行接收包括PDSCH；
所述方法还包括：
所述网络侧设备向终端发送第三信息，所述第三信息用于指示如下至少一项：
所述第一下行接收对应的所有时域单元对应的激活传输参数；
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
可选地，所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过同一个MAC CE指示；或者，
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
N个第六指示域，所述N个第六指示域用于分别指示所述N个时域类型中的各个时域类型对应的激活传输参数；
第七指示域，所述第七指示域用于联合指示所述N个时域类型中的各个时域类型对应的激活传输参数。
可选地，在通过不同的MAC CE指示所述第一下行接收的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
第八指示域，用于指示所述MAC CE对应的时域类型；
第九指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
在所述第一下行接收需要应用所述第三信息指示的传输参数的情况下，所述网络侧设备从所述第三信息指示的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型相同的情况下，所述网络侧设备将所述PDCCH的CORESET对应的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型不同的情况下，所述网络侧设备将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型不包含所述第一下行接收对应的时域类型的情况下，所述网络侧设备将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型包含所述第一下行接收对应的时域类型的情况下，所述网络侧设备从所述PDCCH的CORESET对应的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用缺省传输参数的情况下，所述网络侧设备将所述第一时域类型对应的缺省传输参数确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用初始传输参数的情况下，所述网络侧设备将所述第一时域类型对应的初始传输参数确定为所述第一下行接收对应的传输参数。
可选地，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
在所述第一NZP CSI-RS资源为周期性或半持续资源的情况下，所述第一NZP CSI-RS资源对应的接收时机所在时域单元对应同一个时域类型，或者，所述第一NZP CSI-RS资源对应的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，所述方法还包括：
所述网络侧设备向终端发送第四信息，所述第四信息用于指示如下至少一项：
所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
可选地，所述网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
在所述第一NZP CSI-RS资源为非周期性资源，并且与所述第一NZP CSI-RS资源对应的CSI-RS需要应用缺省传输参数的情况下，所述网络侧设备将所述第一时域类型对应的缺省传输参数确定为与所述第一NZP CSI-RS资源对应的CSI-RS对应的传输参数。
本申请实施例的相关说明可参见图3方法实施例的相关说明，并能够达到相同的技术效果，为避免重复，对此不作赘述。
本申请实施例提供的下行接收和测量方法，执行主体可以为下行接收和测量装置。本申请实施例中以下行接收和测量装置执行下行接收和测量方法为例，说明本申请实施例提供的下行接收和测量装置。
参照图5，本申请实施例还提供了一种下行接收和测量装置。如图5所示，该下行接收和测量装置500包括：
第一处理单元501，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
可选地，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
所述第一下行接收所在时域单元对应同一个时域类型；或者，
所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
可选地，所述第一下行接收包括SSB；
在所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型的情况下，所述第一处理单元具体用于如下至少一项：
不区分所述第一下行接收所在时域单元对应的时域类型，将所述第一下行接收对应的传输参数统一确定为第一传输参数；
区分所述第一下行接收所在时域单元对应的时域类型，基于时域类型与传输参数之间的映射关系，确定所述第一下行接收在不同时域类型的时域单元内对应的传输参数。
可选地，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
所述装置还包括：
第一接收单元，用于接收来自网络侧设备的第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
所述第一处理单元具体用于：
基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
可选地，所述至少一个集合包括如下至少一项：
第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
可选地，所述传输参数的配置信息包括如下至少一项：
传输参数的标识，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的标识的取值确定；
传输参数的第一指示，所述第一指示用于指示时域类型，所述至少一个第二集合中的各个传输参数对应的时域类型为传输参数的第一指示所指示的时域类型。
可选地，所述第三集合包括一个或多个子集，所述第三集合的各个子集满足如下至少之一：
所述第三集合的各个子集按照预定顺序排序，所述预定顺序表示所述时域类型的顺序；
所述第三集合的各个子集包括的传输参数的数量按照预定义的方式分配，或者直接配置或指示。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述第一CORESET的接收时机所在时域单元对应同一个时域类型；或者，
所述第一CORESET的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，在所述第一CORESET的接收时机所在时域单元对应同一个时域类型的情况下，所述第一CORESET的接收时机所在时域单元对应的时域类型由如下至少一项确定：
所述第一CORESET的配置信息；
所述第一CORESET关联的搜索空间中，各个搜索空间的配置信息；
协议规定；
高层参数。
可选地，所述第一CORESET的配置信息，包括如下至少一项：
所述第一CORESET的标识，所述第一CORESET的标识的取值用于确定所述第一CORESET的接收时机所在时域单元对应的时域类型；
所述第一CORESET的第二指示，所述第二指示用于指示时域类型，所述第一CORESET的接收时机所在时域单元对应的时域类型为所述第二指示所指示的时域类型。
可选地，所述各个搜索空间的配置信息，包括如下至少一项：
所述各个搜索空间的标识，所述各个搜索空间的标识的取值用于分别确定所述各个搜索空间的接收时机所在时域单元对应的时域类型；
所述各个搜索空间的第三指示，所述第三指示用于指示时域类型，所述各个搜索空间的接收时机所在时域单元对应的时域类型为各个搜索空间的第三指示所指示的时域类型。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述装置还包括：
第二接收单元，用于接收来自网络侧设备的第二信息，所述第二信息用于指示如下至少一项：
所述第一CORESET的所有接收时机对应的传输参数；
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
可选地，所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过同一个MAC CE指示；或者，
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
M个第一指示域，所述M个第一指示域用于分别指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数；
第二指示域，所述第二指示域用于联合指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数。
可选地，在通过不同的MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
第三指示域，用于指示所述MAC CE对应的时域类型；
第四指示域，用于指示对应时域类型所对应的传输参数；
第五指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述第一下行接收包括PDSCH；
所述装置还包括：
第三接收单元，用于接收来自网络侧设备的第三信息，所述第三信息用于指示如下至少一项：
所述第一下行接收对应的所有时域单元对应的激活传输参数；
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
可选地，所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过同一个MAC CE指示；或者，
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
N个第六指示域，所述N个第六指示域用于分别指示所述N个时域类型中的各个时域类型对应的激活传输参数；
第七指示域，所述第七指示域用于联合指示所述N个时域类型中的各个时域类型对应的激活传输参数。
可选地，在通过不同的MAC CE指示所述第一下行接收的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
第八指示域，用于指示所述MAC CE对应的时域类型；
第九指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述第一处理单元具体用于如下至少一项：
在所述第一下行接收需要应用所述第三信息指示的传输参数的情况下，从所述第三信息指示的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型相同的情况下，将所述PDCCH的CORESET对应的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型不同的情况下，将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型不包含所述第一下行接收对应的时域类型的情况下，将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型包含所述第一下行接收对应的时域类型的情况下，从所述PDCCH的CORESET对应的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用缺省传输参数的情况下，将所述第一时域类型对应的缺省传输参数确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用初始传输参数的情况下，将所述第一时域类型对应的初始传输参数确定为所述第一下行接收对应的传输参数。
可选地，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
在所述第一NZP CSI-RS资源为周期性或半持续资源的情况下，所述第一NZP CSI-RS资源对应的接收时机所在时域单元对应同一个时域类型，或者，所述第一NZP CSI-RS资源对应的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
所述装置还包括：
第四接收单元，用于接收来自网络侧设备的第四信息，所述第四信息用于指示如下至少一项：
所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
可选地，所述第一处理单元具体用于：
在所述第一NZP CSI-RS资源为非周期性资源，并且与所述第一NZP CSI-RS资源对应的CSI-RS需要应用缺省传输参数的情况下，将所述第一时域类型对应的缺省传输参数确定为与所述第一NZP CSI-RS资源对应的CSI-RS对应的传输参数。
可选地，所述第一测量包括CSI测量；
所述装置还包括：
第二处理单元，用于在所述第一测量的上报需要区分时域类型的情况下，确定目标CSI报告对应的目标CSI参考资源；
第三处理单元，用于执行如下操作中的至少一项：
基于是否接收到至少一个目标CSI-RS接收时机，确定是否上报目标CSI报告；
在所述目标CSI报告为周期性或半持续CSI报告的情况下，基于最晚的所述目标CSI-RS接收时机，确定CPU占用的起始时刻；
使用至少一个所述目标CSI-RS接收时机，确定所述第一测量包含的目标信息；所述目标信息包括L1-RSRP、L1-SINR、CQI中的至少一项；
其中，所述目标CSI报告与第二时域类型对应；所述目标CSI-RS接收时机与所述第二时域类型对应，且所述目标CSI-RS接收时机不晚于所述目标CSI参考资源。
可选地，所述第一测量包括CLI测量；
在基于所述第二时域类型对应的时域单元内的CLI测量资源执行所述第一测量的情况下，所述CLI测量资源对应的传输参数，包括如下至少一项：
在所述第二时域类型对应的时域单元内，最晚接收的PDSCH对应的传输参数；
与所述第二时域类型对应，且最晚接收的PDSCH对应的传输参数；
在所述第二时域类型对应的时域单元内，最晚监测的CORESET对应的传输参数；
与所述第二时域类型对应，且最晚监测的CORESET对应的传输参数；
在所述第二时域类型对应的时域单元内，最晚接收的PDSCH和最晚监测的CORESET中的较晚者对应的传输参数；
与所述第二时域类型对应的最晚接收的PDSCH和最晚监测的CORESET中，较晚者对应的传输参数。
本申请实施例中的下行接收和测量装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的下行接收和测量装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
参照图6，本申请实施例还提供了一种下行接收和测量装置。如图6所示，该下行接收和测量装置600包括：
处理单元601，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
可选地，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
所述第一下行接收所在时域单元对应同一个时域类型；或者，
所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
可选地所述第一下行接收包括SSB；
在所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型的情况下，所述处理单元具体用于如下至少一项：
不区分所述第一下行接收所在时域单元对应的时域类型，将所述第一下行接收对应的传输参数统一确定为第一传输参数；
区分所述第一下行接收所在时域单元对应的时域类型，基于时域类型与传输参数之间的映射关系，确定所述第一下行接收在不同时域类型的时域单元内对应的传输参数。
可选地，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
所述装置还包括：
第一发送单元，用于向终端发送第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
所述处理单元具体用于：
基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
可选地，所述至少一个集合包括如下至少一项：
第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
可选地，所述传输参数的配置信息包括如下至少一项：
传输参数的标识，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的标识的取值确定；
传输参数的第一指示，所述第一指示用于指示时域类型，所述至少一个第二集合中的各个传输参数对应的时域类型为传输参数的第一指示所指示的时域类型。
可选地，所述第三集合包括一个或多个子集，所述第三集合的各个子集满足如下至少之一：
所述第三集合的各个子集按照预定顺序排序，所述预定顺序表示所述时域类型的顺序；
所述第三集合的各个子集包括的传输参数的数量按照预定义的方式分配，或者直接配置或指示。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述第一CORESET的接收时机所在时域单元对应同一个时域类型；或者，
所述第一CORESET的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，在所述第一CORESET的接收时机所在时域单元对应同一个时域类型的情况下，所述第一CORESET的接收时机所在时域单元对应的时域类型由如下至少一项确定：
所述第一CORESET的配置信息；
所述第一CORESET关联的搜索空间中，各个搜索空间的配置信息；
协议规定；
高层参数。
可选地，所述第一CORESET的配置信息，包括如下至少一项：
所述第一CORESET的标识，所述第一CORESET的标识的取值用于确定所述第一CORESET的接收时机所在时域单元对应的时域类型；
所述第一CORESET的第二指示，所述第二指示用于指示时域类型，所述第一CORESET的接收时机所在时域单元对应的时域类型为所述第二指示所指示的时域类型。
可选地，所述各个搜索空间的配置信息，包括如下至少一项：
所述各个搜索空间的标识，所述各个搜索空间的标识的取值用于分别确定所述各个搜索空间的接收时机所在时域单元对应的时域类型；
所述各个搜索空间的第三指示，所述第三指示用于指示时域类型，所述各个搜索空间的接收时机所在时域单元对应的时域类型为各个搜索空间的第三指示所指示的时域类型。
可选地，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
所述装置还包括：
第二发送单元，用于向终端发送第二信息，所述第二信息用于指示如下至少一项：
所述第一CORESET的所有接收时机对应的传输参数；
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
可选地，所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过同一个MAC CE指示；或者，
所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
M个第一指示域，所述M个第一指示域用于分别指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数；
第二指示域，所述第二指示域用于联合指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数。
可选地，在通过不同的MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
第三指示域，用于指示所述MAC CE对应的时域类型；
第四指示域，用于指示对应时域类型所对应的传输参数；
第五指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述第一下行接收包括PDSCH；
所述装置还包括：
第三发送单元，用于向终端发送第三信息，所述第三信息用于指示如下至少一项：
所述第一下行接收对应的所有时域单元对应的激活传输参数；
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
可选地，所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过同一个MAC CE指示；或者，
所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示。
可选地，在通过同一个MAC CE指示所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
N个第六指示域，所述N个第六指示域用于分别指示所述N个时域类型中的各个时域类型对应的激活传输参数；
第七指示域，所述第七指示域用于联合指示所述N个时域类型中的各个时域类型对应的激活传输参数。
可选地，在通过不同的MAC CE指示所述第一下行接收的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
第八指示域，用于指示所述MAC CE对应的时域类型；
第九指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
可选地，所述处理单元具体用于如下至少一项：
在所述第一下行接收需要应用所述第三信息指示的传输参数的情况下，从所述第三信息指示的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型相同的情况下，将所述PDCCH的CORESET对应的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型不同的情况下，将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型不包含所述第一下行接收对应的时域类型的情况下，将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型包含所述第一下行接收对应的时域类型的情况下，从所述PDCCH的CORESET对应的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用缺省传输参数的情况下，将所述第一时域类型对应的缺省传输参数确定为所述第一下行接收对应的传输参数；
在所述第一下行接收需要应用初始传输参数的情况下，将所述第一时域类型对应的初始传输参数确定为所述第一下行接收对应的传输参数。
可选地，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
在所述第一NZP CSI-RS资源为周期性或半持续资源的情况下，所述第一NZP CSI-RS资源对应的接收时机所在时域单元对应同一个时域类型，或者，所述第一NZP CSI-RS资源对应的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
可选地，所述装置还包括：
第四发送单元，用于向终端发送第四信息，所述第四信息用于指示如下至少一项：
所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
可选地，所述处理单元具体用于：
在所述第一NZP CSI-RS资源为非周期性资源，并且与所述第一NZP CSI-RS资源对应的CSI-RS需要应用缺省传输参数的情况下，将所述第一时域类型对应的缺省传输参数确定为与所述第一NZP CSI-RS资源对应的CSI-RS对应的传输参数。
本申请实施例中的下行接收和测量装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的下行接收和测量装置能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图7所示，本申请实施例还提供一种通信设备700，包括处理器701和存储器702，存储器702上存储有可在所述处理器701上运行的程序或指令，例如，该通信设备700为终端时，该程序或指令被处理器701执行时实现上述终端侧方法实施例的各个步骤，且能达到相同的技术效果。该通信设备700为网络侧设备时，该程序或指令被处理器701执行时实现上述网络侧设备侧方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图3所示方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图8为实现本申请实施例的一种终端的硬件结构示意图。
该终端800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809以及处理器810等中的至少部分部件。
本领域技术人员可以理解，终端800还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元804可以包括图形处理器(Graphics Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元806可包括显示面板8061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板8061。用户输入单元807包括触控面板8071以及其他输入设备8072中的至少一种。触控面板8071，也称为触摸屏。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元801接收来自网络侧设备的下行数据后，可以传输给处理器810进行处理；另外，射频单元801可以向网络侧设备发送下行数据。通常，射频单元801包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器809可用于存储软件程序或指令以及各种数据。存储器809可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器809可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器809包括但不限于这些和任意其它适合类型的存储器。
处理器810可包括一个或多个处理单元；可选的，处理器810集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，处理器810用于：
基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
本申请实施例中，在时域单元对应或区分多种时域类型时，终端能够基于下行接收对应的时域类型来确定下行接收对应的传输参数，从而终端能够根据确定的传输参数实现灵活且可靠的下行接收。终端还能够基于某个测量对应的时域类型来执行测量和上报中的至少一项，从而终端能够实现灵活且准确和有效的测量。可见，本申请实施例能够实现终端在灵活双工场景下的下行接收或测量。
可以理解，本实施例中提及的各实现方式的实现过程可以参照下行接收和测量方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图4所示的方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图9所示，该网络侧设备900包括：天线91、射频装置92、基带装置93、处理器94和存储器95。天线91与射频装置92连接。在下行方向上，射频装置92通过天线91接收信息，将接收的信息发送给基带装置93进行处理。在下行方向上，基带装置93对要发送的信息进行处理，并发送给射频装置92，射频装置92对收到的信息进行处理后经过天线91发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置93中实现，该基带装置93包括基带处理器。
基带装置93例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为基带处理器，通过总线接口与存储器95连接，以调用存储器95中的程序，执行以上方法实施例中所示的网络侧设备操作。
该网络侧设备还可以包括网络接口96，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备900还包括：存储在存储器95上并可在处理器94上运行的指令或程序，处理器94调用存储器95中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述下行接收和测量方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述下行接收和测量方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述下行接收和测量方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的下行接收和测量方法的步骤，所述网络侧设备可用于执行如上所述的下行接收和测量方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (42)

  1. 一种下行接收和测量方法，包括：
    终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；
    或，
    所述终端基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
    其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
    在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
    在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
    所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
  2. 根据权利要求1中任一项所述的方法，其中，所述第一测量包括CSI测量；
    所述方法还包括：
    在所述第一测量的上报需要区分时域类型的情况下，所述终端确定目标CSI报告对应的目标CSI参考资源；
    所述终端执行如下操作中的至少一项：
    基于是否接收到至少一个目标CSI-RS接收时机，确定是否上报目标CSI报告；
    在所述目标CSI报告为周期性或半持续CSI报告的情况下，基于最晚的所述目标CSI-RS接收时机，确定CPU占用的起始时刻；
    使用至少一个所述目标CSI-RS接收时机，确定所述第一测量包含的目标信息；所述目标信息包括L1-RSRP、L1-SINR、CQI中的至少一项；
    其中，所述目标CSI报告与第二时域类型对应；所述目标CSI-RS接收时机与所述第二时域类型对应，且所述目标CSI-RS接收时机不晚于所述目标CSI参考资源。
  3. 根据权利要求1所述的方法，其中，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
    所述第一下行接收所在时域单元对应同一个时域类型；或者，
    所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
  4. 根据权利要求3所述的方法，其中，所述第一下行接收包括SSB；
    在所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型的情况下，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
    所述终端不区分所述第一下行接收所在时域单元对应的时域类型，将所述第一下行接收对应的传输参数统一确定为第一传输参数；
    所述终端区分所述第一下行接收所在时域单元对应的时域类型，基于时域类型与传输参数之间的映射关系，确定所述第一下行接收在不同时域类型的时域单元内对应的传输参数。
  5. 根据权利要求1所述的方法，其中，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
    所述方法还包括：
    所述终端接收来自网络侧设备的第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
    所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
    所述终端基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
  6. 根据权利要求5所述的方法，其中，所述至少一个集合包括如下至少一项：
    第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
    至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
    第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
    至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
  7. 根据权利要求6所述的方法，其中，所述传输参数的配置信息包括如下至少一项：
    传输参数的标识，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的标识的取值确定；
    传输参数的第一指示，所述第一指示用于指示时域类型，所述至少一个第二集合中的各个传输参数对应的时域类型为传输参数的第一指示所指示的时域类型。
  8. 根据权利要求7所述的方法，其中，所述第三集合包括一个或多个子集，所述第三集合的各个子集满足如下至少之一：
    所述第三集合的各个子集按照预定顺序排序，所述预定顺序表示所述时域类型的顺序；
    所述第三集合的各个子集包括的传输参数的数量按照预定义的方式分配，或者直接配置或指示。
  9. 根据权利要求3、5至8中任一项所述的方法，其中，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
    所述第一CORESET的接收时机所在时域单元对应同一个时域类型；或者，
    所述第一CORESET的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
  10. 根据权利要求9所述的方法，其中，在所述第一CORESET的接收时机所在时域单元对应同一个时域类型的情况下，所述第一CORESET的接收时机所在时域单元对应的时域类型由如下至少一项确定：
    所述第一CORESET的配置信息；
    所述第一CORESET关联的搜索空间中，各个搜索空间的配置信息；
    协议规定；
    高层参数。
  11. 根据权利要求10所述的方法，其中，所述第一CORESET的配置信息，包括如下至少一项：
    所述第一CORESET的标识，所述第一CORESET的标识的取值用于确定所述第一CORESET的接收时机所在时域单元对应的时域类型；
    所述第一CORESET的第二指示，所述第二指示用于指示时域类型，所述第一CORESET的接收时机所在时域单元对应的时域类型为所述第二指示所指示的时域类型；
    或者，
    所述各个搜索空间的配置信息，包括如下至少一项：
    所述各个搜索空间的标识，所述各个搜索空间的标识的取值用于分别确定所述各个搜索空间的接收时机所在时域单元对应的时域类型；
    所述各个搜索空间的第三指示，所述第三指示用于指示时域类型，所述各个搜索空间的接收时机所在时域单元对应的时域类型为各个搜索空间的第三指示所指示的时域类型。
  12. 根据权利要求3、5至11中的至少一项所述的方法，还包括：
    所述终端接收来自网络侧设备的第二信息，所述第二信息用于指示如下至少一项：
    所述第一CORESET的所有接收时机对应的传输参数；
    所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
  13. 根据权利要求12所述的方法，其中，所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过同一个MAC CE指示；或者，
    所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数通过不同的MAC CE指示。
  14. 根据权利要求13所述的方法，其中，在通过同一个MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
    M个第一指示域，所述M个第一指示域用于分别指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数；
    第二指示域，所述第二指示域用于联合指示所述M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数。
  15. 根据权利要求14所述的方法，其中，在通过不同的MAC CE指示所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数的情况下，所述MAC CE包括如下至少一项：
    第三指示域，用于指示所述MAC CE对应的时域类型；
    第四指示域，用于指示对应时域类型所对应的传输参数；
    第五指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
  16. 根据权利要求5至15中任一项所述的方法，其中，所述第一下行接收包括PDSCH；
    所述方法还包括：
    所述终端接收来自网络侧设备的第三信息，所述第三信息用于指示如下至少一项：
    所述第一下行接收对应的所有时域单元对应的激活传输参数；
    所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
  17. 根据权利要求16所述的方法，其中，所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过同一个MAC CE指示；或者，
    所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数通过不同的MAC CE指示。
  18. 根据权利要求17所述的方法，其中，在通过同一个MAC CE指示所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
    N个第六指示域，所述N个第六指示域用于分别指示所述N个时域类型中的各个时域类型对应的激活传输参数；
    第七指示域，所述第七指示域用于联合指示所述N个时域类型中的各个时域类型对应的激活传输参数。
  19. 根据权利要求17所述的方法，其中，在通过不同的MAC CE指示所述第一下行接收的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数的情况下，所述MAC CE包括如下至少一项：
    第八指示域，用于指示所述MAC CE对应的时域类型；
    第九指示域，用于指示对应时域类型所对应的传输参数的激活状态或去激活状态。
  20. 根据权利要求16至19中任一项所述的方法，其中，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括如下至少一项：
    在所述第一下行接收需要应用所述第三信息指示的传输参数的情况下，所述终端从所述第三信息指示的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型相同的情况下，所述终端将所述PDCCH的CORESET对应的传输参数，确定为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用PDCCH的传输参数，且所述第一下行接收对应的时域类型与所述PDCCH的CORESET对应的时域类型不同的情况下，所述终端将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型不包含所述第一下行接收对应的时域类型的情况下，所述终端将所述第一时域类型对应的缺省传输参数或预定义的传输参数，确定为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用PDCCH的传输参数，且所述PDCCH的CORESET对应的至少一个时域类型包含所述第一下行接收对应的时域类型的情况下，所述终端从所述PDCCH的CORESET对应的传输参数中，选择时域类型与所述第一下行接收对应的时域类型相同的传输参数作为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用缺省传输参数的情况下，所述终端将所述第一时域类型对应的缺省传输参数确定为所述第一下行接收对应的传输参数；
    在所述第一下行接收需要应用初始传输参数的情况下，所述终端将所述第一时域类型对应的初始传输参数确定为所述第一下行接收对应的传输参数。
  21. 根据权利要求3、5至8中任一项所述的方法，其中，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
    在所述第一NZP CSI-RS资源为周期性或半持续资源的情况下，所述第一NZP CSI-RS资源对应的接收时机所在时域单元对应同一个时域类型，或者，所述第一NZP CSI-RS资源对应的接收时机所在时域单元能够对应多个时域类型或所有时域类型。
  22. 根据权利要求3或21所述的方法，还包括：
    所述终端接收来自网络侧设备的第四信息，所述第四信息用于指示如下至少一项：
    所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
    所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
  23. 根据权利要求3或21所述的方法，其中，所述终端基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
    在所述第一NZP CSI-RS资源为非周期性资源，并且与所述第一NZP CSI-RS资源对应的CSI-RS需要应用缺省传输参数的情况下，所述终端将所述第一时域类型对应的缺省传输参数，确定为与所述第一NZP CSI-RS资源对应的CSI-RS对应的传输参数。
  24. 根据权利要求1所述的方法，其中，所述第一测量包括CLI测量；
    在基于所述第二时域类型对应的时域单元内的CLI测量资源执行所述第一测量的情况下，所述CLI测量资源对应的传输参数，包括如下至少一项：
    在所述第二时域类型对应的时域单元内，最晚接收的PDSCH对应的传输参数；
    与所述第二时域类型对应，且最晚接收的PDSCH对应的传输参数；
    在所述第二时域类型对应的时域单元内，最晚监测的CORESET对应的传输参数；
    与所述第二时域类型对应，且最晚监测的CORESET对应的传输参数；
    在所述第二时域类型对应的时域单元内，最晚接收的PDSCH和最晚监测的CORESET中的较晚者对应的传输参数；
    与所述第二时域类型对应的最晚接收的PDSCH和最晚监测的CORESET中，较晚者对应的传输参数。
  25. 根据权利要求24所述的方法，其中，所述CLI测量资源对应的传输参数包括QCL假设，所述QCL假设的类型包括类型D。
  26. 一种下行接收和测量方法，包括：
    网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；
    或，
    所述网络侧设备基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
    其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
    在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
    在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
    所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
  27. 根据权利要求26所述的方法，其中，所述第一下行接收包括SSB、PDCCH和CSI-RS中的至少一项；
    所述第一下行接收所在时域单元对应同一个时域类型；或者，
    所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
  28. 根据权利要求26所述的方法，其中，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
    所述方法还包括：
    所述网络侧设备向终端发送第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
    所述网络侧设备基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，包括：
    所述网络侧设备基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
  29. 根据权利要求28所述的方法，其中，所述至少一个集合包括如下至少一项：
    第一集合，所述第一集合中的任意一个传输参数可用于任意的时域类型；
    至少一个第二集合，所述至少一个第二集合中的各个传输参数对应的时域类型由传输参数的配置信息确定；
    第三集合，所述第三集合中的各个传输参数对应的时域类型由传输参数在所述第三集合中的位置确定；
    至少一个第四集合，每个所述第四集合中的全部传输参数对应同一个时域类型，不同的所述第四集合对应不同的时域类型。
  30. 根据权利要求28或29所述的方法，其中，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
    所述方法还包括：
    所述网络侧设备向终端发送第二信息，所述第二信息用于指示如下至少一项：
    所述第一CORESET的所有接收时机对应的传输参数；
    所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
  31. 根据权利要求28至30中任一项所述的方法，其中，所述第一下行接收包括PDSCH；
    所述方法还包括：
    所述网络侧设备向终端发送第三信息，所述第三信息用于指示如下至少一项：
    所述第一下行接收对应的所有时域单元对应的激活传输参数；
    所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
  32. 根据权利要求26至29中任一项所述的方法，其中，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
    所述方法还包括：
    所述网络侧设备向终端发送第四信息，所述第四信息用于指示如下至少一项：
    所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
    所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
  33. 一种下行接收和测量装置，所述装置包括：
    第一处理单元，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的接收；或，
    基于第一测量对应的第二时域类型，执行所述第一测量和所述第一测量对应的上报中的至少一项；
    其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
    在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
    在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
    所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
  34. 根据权利要求33所述的装置，其中，所述第一下行接收包括SSB、PDCCH、和CSI-RS中的至少一项；
    所述第一下行接收所在时域单元对应同一个时域类型；或者，
    所述第一下行接收所在时域单元能够对应多个时域类型或所有时域类型。
  35. 根据权利要求33所述的装置，其中，所述第一下行接收包括PDSCH、PDCCH和CSI-RS中的至少一项；
    所述装置还包括：
    第一接收单元，用于接收来自网络侧设备的第一信息，所述第一信息用于配置至少一个集合，所述至少一个集合中的各个集合包括至少一个传输参数；
    所述第一处理单元具体用于：
    基于第一下行接收对应的第一时域类型，从所述至少一个集合中确定所述第一下行接收对应的传输参数。
  36. 根据权利要求34或35所述的装置，其中，所述第一下行接收包括与第一控制资源集CORESET对应的PDCCH；
    所述装置还包括：
    第二接收单元，用于接收来自网络侧设备的第二信息，所述第二信息用于指示如下至少一项：
    所述第一CORESET的所有接收时机对应的传输参数；
    所述第一CORESET对应的M个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，M为大于或等于1的整数。
  37. 根据权利要求35所述的装置，其中，所述第一下行接收包括PDSCH；
    所述装置还包括：
    第三接收单元，用于接收来自网络侧设备的第三信息，所述第三信息用于指示如下至少一项：
    所述第一下行接收对应的所有时域单元对应的激活传输参数；
    所述第一下行接收对应的N个时域类型中，各个时域类型对应的时域单元各自对应的激活传输参数，N为大于或等于1的整数。
  38. 根据权利要求34或35所述的装置，其中，所述第一下行接收包括与第一非零功率NZP CSI-RS资源对应的CSI-RS；
    所述装置还包括：
    第四接收单元，用于接收来自网络侧设备的第四信息，所述第四信息用于指示如下至少一项：
    所述第一NZP CSI-RS资源对应的所有接收时机对应的传输参数；
    所述第一NZP CSI-RS资源对应的S个时域类型中，各个时域类型对应的接收时机各自对应的传输参数，S为大于或等于1的整数。
  39. 一种下行接收和测量装置，所述装置包括：
    处理单元，用于：基于第一下行接收对应的第一时域类型，确定所述第一下行接收对应的传输参数，并根据所述第一下行接收对应的传输参数，执行所述第一下行接收对应的发送；或，
    基于第一测量对应的第二时域类型，执行所述第一测量对应的测量报告的接收；
    其中，所述第一下行接收包括同步信号块SSB、物理下行控制信道PDCCH、物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS中的至少一项；
    在所述第一下行接收包括SSB的情况下，所述传输参数包括如下至少一项：发射功率；SSB波束的相关参数；SSB索引的相关参数；
    在所述第一下行接收包括PDCCH、PDSCH和CSI-RS中的至少一项的情况下，所述传输参数包括如下至少一项：准共址QCL假设；传输配置指示TCI状态；
    所述第一测量包括信道状态信息CSI测量和跨链路干扰CLI测量中的至少一项。
  40. 一种通信设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至25中任一项所述的下行接收和测量方法的步骤，或者实现如权利要求26至32中任一项所述的下行接收和测量方法的步骤。
  41. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至25中任一项所述的下行接收和测量方法的步骤，或者实现如权利要求26至32中任一项所述的下行接收和测量方法的步骤。
  42. 一种计算机程序产品，包括计算机指令，该计算机指令被处理器执行时实现如权利要求1至25中任一项所述的下行接收和测量方法的步骤，或者实现如权利要求26至32中任一项所述的下行接收和测量方法的步骤。
PCT/CN2025/088420 2024-04-18 2025-04-11 下行接收和测量方法、装置及通信设备 Pending WO2025218586A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410471183.9 2024-04-18
CN202410471183.9A CN120835410A (zh) 2024-04-18 2024-04-18 下行接收和测量方法、装置及通信设备

Publications (1)

Publication Number Publication Date
WO2025218586A1 true WO2025218586A1 (zh) 2025-10-23

Family

ID=97395885

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/088420 Pending WO2025218586A1 (zh) 2024-04-18 2025-04-11 下行接收和测量方法、装置及通信设备

Country Status (2)

Country Link
CN (1) CN120835410A (zh)
WO (1) WO2025218586A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021247224A1 (en) * 2020-06-04 2021-12-09 Qualcomm Incorporated Sounding reference signal configurations for subband full duplex operation in new radio
CN116567688A (zh) * 2022-01-27 2023-08-08 维沃移动通信有限公司 同步信号块接收方法、同步信号块发送方法及相关设备
CN116648878A (zh) * 2023-03-31 2023-08-25 北京小米移动软件有限公司 信道传输方法及装置、存储介质
CN117528779A (zh) * 2022-07-25 2024-02-06 维沃移动通信有限公司 信息配置方法、装置、终端、网络侧设备及可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021247224A1 (en) * 2020-06-04 2021-12-09 Qualcomm Incorporated Sounding reference signal configurations for subband full duplex operation in new radio
CN116567688A (zh) * 2022-01-27 2023-08-08 维沃移动通信有限公司 同步信号块接收方法、同步信号块发送方法及相关设备
CN117528779A (zh) * 2022-07-25 2024-02-06 维沃移动通信有限公司 信息配置方法、装置、终端、网络侧设备及可读存储介质
CN116648878A (zh) * 2023-03-31 2023-08-25 北京小米移动软件有限公司 信道传输方法及装置、存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HYUNSOO KO, LG ELECTRONICS: "Discussion on SBFD TX/RX/measurement procedures", 3GPP DRAFT; R1-2401249; TYPE DISCUSSION; NR_DUPLEX_EVO-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, GR; 20240226 - 20240301, 19 February 2024 (2024-02-19), France, XP052569018 *

Also Published As

Publication number Publication date
CN120835410A (zh) 2025-10-24

Similar Documents

Publication Publication Date Title
WO2024061261A1 (zh) 资源配置方法及装置、终端及网络侧设备
WO2024067571A1 (zh) 灵活双工sbfd信息指示方法、终端及网络侧设备
US20250039901A1 (en) Information receiving method, information transmitting method, and device
US20240365297A1 (en) Transmission Determining Method and Apparatus, Device, and Medium
WO2024022160A1 (zh) 信息配置方法、装置、终端、网络侧设备及可读存储介质
WO2023198146A1 (zh) 资源配置方法、装置、设备及介质
CN114765798A (zh) 信道信息发送方法、信道信息接收方法及相关设备
WO2024114515A2 (zh) 上行传输的发射功率确定方法、装置、终端及网络侧设备
WO2024114491A1 (zh) 上行参考信号资源传输方法、装置、终端及网络侧设备
WO2024022159A1 (zh) 信息配置方法、装置、终端、网络侧设备及可读存储介质
CN120880575A (zh) Cli的测量和上报方法、装置、终端、网络侧设备及介质
WO2024022162A1 (zh) 信息配置方法、装置、终端、网络侧设备及可读存储介质
WO2025218586A1 (zh) 下行接收和测量方法、装置及通信设备
RU2794203C2 (ru) Пользовательское оборудование, задействованное в энергосбережении
WO2025077607A1 (zh) 动态sbfd指示方法、装置、设备及存储介质
WO2024114490A1 (zh) 上行信道传输方法、装置、终端及网络侧设备
WO2025067046A1 (zh) 自干扰测量方法、装置、终端及网络侧设备
WO2026032175A1 (zh) 参数配置方法、装置、终端及网络侧设备
WO2025082378A1 (zh) 功率调整方法、装置、终端及网络侧设备
WO2025157130A1 (zh) 频域资源的确定方法、装置、设备及存储介质
CN117134868A (zh) Harq-ack反馈方法、终端及网络侧设备
WO2025167791A1 (zh) 信息处理方法、装置及相关设备
WO2025067138A1 (zh) 干扰测量方法、测量结果接收方法、装置及设备
CN120034957A (zh) 信道重复传输方法、装置、ue、网络侧设备及存储介质
WO2024235067A1 (zh) 灵活双工的实现方法、装置、终端、网络侧设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25789830

Country of ref document: EP

Kind code of ref document: A1