Effective PDSCH or PUSCH scheduling with multiple PDSCH or PUSCH

Abstract

Various embodiments herein provide techniques for determining enabled and disabled physical downlink shared channels (PDSCHs) and / or physical uplink shared channels (PUSCHs) with multi-PDSCH and / or PUSCH scheduling. Embodiments further relate to determining a transmission configuration indicator (TCI) state and / or quasi-co-location (QCL) for multi-PDSCH and / or PUSCH scheduling. Other embodiments may be described and claimed.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 301,888, filed January 21, 2022, and U.S. Provisional Patent Application No. 63 / 307,520, filed February 7, 2022.

[0002] Technical Field For example, some embodiments may relate to determining an effective Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) using multiple PDSCH or PUSCH scheduling. [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communications platforms. The next generation wireless communication system, 5G or new radio (NR), provides access to information and sharing of data by various users and applications anywhere, anytime. NR is expected to be a unified network / system that targets to meet very different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by various services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simpler and seamless wireless connectivity solutions. NR will enable everything to be connected by radio, providing high speed and rich content and services. [Brief description of the drawings]

[0004] BRIEF DESCRIPTION OF THE DRAWINGS The embodiments will be readily understood by the following detailed description taken in conjunction with the accompanying drawings, in which: To facilitate this description, like reference numerals indicate like structural elements, and in which: FIG.

[0005] [Figure 1] FIG. 1 illustrates an example of multi-transmission time interval (TTI) scheduling for physical downlink shared channels (PDSCHs) in accordance with various embodiments.

[0006] [Diagram 2] FIG. 1 illustrates an example of a physical uplink shared channel (PUSCH) preparation time for a first valid PUSCH#1 in accordance with various embodiments.

[0007] [Diagram 3] 1 illustrates an example of a minimum scheduling delay for a first valid PDSCH#1 according to various embodiments.

[0008] [Figure 4] FIG. 1 illustrates an example of a transmission configuration indicator (TCI) state determination according to a first valid PDSCH#1, according to various embodiments.

[0009] [Diagram 5] FIG. 1 illustrates an example of TCI state determination according to a first valid PDSCH#0 in accordance with various embodiments.

[0010] [Figure 6] 1 is a schematic diagram of a wireless network according to various embodiments;

[0011] [Figure 7] 1 is a diagram illustrating components of a wireless network according to various embodiments.

[0012] [Figure 8]FIG. 1 is a block diagram illustrating components according to some example embodiments that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0013] [Figure 9] FIG. 1 illustrates an exemplary procedure for carrying out various embodiments herein. [Figure 10] FIG. 1 illustrates an exemplary procedure for carrying out various embodiments herein. [Figure 11] FIG. 1 illustrates an exemplary procedure for carrying out various embodiments herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be implemented in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrases "A or B" and "A / B" mean (A), (B) or (A and B).

[0015] Various embodiments herein provide techniques for determining enabled and disabled physical downlink shared channels (PDSCHs) and / or physical uplink shared channels (PUSCHs) using multi-PDSCH and / or PUSCH scheduling. Embodiments further relate to determining transmission configuration indicator (TCI) state and / or quasi co-location (QCL) for multi-PDSCH and / or PUSCH scheduling.

[0016] For systems operating at carrier frequencies above 52.6 GHz, the subcarrier spacing (SCS) is increased and the slot duration is reduced. Downlink control information (DCI) may schedule multiple PDSCH or PUSCH transmissions. Different PDSCHs or PUSCHs may carry different transport blocks (TBs). Figure 1 shows an example of multi-PDSCH scheduling. In this example, four PDSCHs (PDSCH#0-3) with different TBs are scheduled by a single DCI.

[0017] Among multiple PDSCHs or PUSCHs scheduled by DCI, one or more PDSCHs or PUSCHs may be dropped. For example, for multiple PDSCHs scheduled by DCI, if the PDSCH overlaps with an uplink symbol indicated by a semi-static TDD UL-DL configuration, the PDSCH is not valid. On the other hand, for multiple PUSCHs scheduled by DCI, if the PUSCH overlaps with a downlink symbol indicated by a semi-static TDD UL-DL configuration or a symbol configured for synchronization signal (SS) / physical broadcast channel (PBCH) transmission, the PUSCH is not valid. Various embodiments herein provide solutions for handling valid PDSCH or PUSCH transmissions with multi-PDSCH or multi-PUSCH scheduling.

[0018] In an embodiment, the DCI for multi-PDSCH or multi-PUSCH scheduling may indicate a row of a time domain resource allocation (TDRA) field with one or more configured start and length indicator values ​​(SLIVs). Each of the multiple SLIVs is associated with a PDSCH or PUSCH. The number of scheduled PDSCHs or PUSCHs for a row may be equal to the number of configured SLIVs for that row. For a row of the TDRA table, each SLIV may be configured in a different slot. Alternatively, one or more SLIVs may be configured in the same slot.

[0019] PUSCH Preparation Time for Multi-PUSCH Scheduling In one embodiment, in case of multi-PUSCH scheduling, the delay between the end symbol of a PDCCH and the start symbol of a valid PUSCH among multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the PUSCH preparation time after considering the effect of timing advance. In some embodiments, a valid PUSCH indicates that the PUSCH does not overlap with a downlink (DL) symbol indicated by a common time domain duplexed (TDD) uplink (UL)-downlink (DL) configuration (tdd-UL-DL-ConfigurationCommon) or a dedicated TDD UL-DL configuration (tdd-UL-DL-ConfigurationDedicated) (if provided), or a symbol of an SS / PBCH block having an index provided by ssb-PositionsInBurst.

[0020] In one option, the PUSCH preparation time is checked after determining a valid PUSCH among multiple PUSCHs scheduled by DCI. A PUSCH is valid if it does not overlap with downlink symbols indicated by the semi-static TDD UL-DL configuration or symbols configured for SS / PBCH transmission. In some embodiments, when a UE is scheduled with multiple PUSCHs by DCI, the delay between the PDCCH and a valid PUSCH should satisfy the following condition: ● Slot offset K2 and K offsetIf the first uplink symbol in a valid PUSCH assignment for a transport block, including a DM-RS, is not earlier than symbol L2, as defined by the start S and length L of the PUSCH assignment, including the effect of timing advance, as indicated by the "Time domain resource assignment" of the scheduling DCI (if configured), then the UE shall transmit the transport block, where L2 is the symbol T after the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH. proc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ T c +T ext +T switch ,d 2,2 ) When the PDCCH candidates are associated with a search space set configured in searchSpaceLinking, for the purpose of determining the last symbol of the PDCCH carrying DCI scheduling the PUSCH, the PDCCH candidate that ends later in time of the two configured PDCCH candidates is used.

[0021] FIG. 2 shows an example of PUSCH preparation times for valid PUSCHs scheduled by DCI. It is assumed that DCI schedules a row of TDRA consisting of four SLIVs. The first SLIV, e.g. PUSCH#0, overlaps with a DL symbol according to the semi-static TDD UL-DL configuration, and therefore PUSCH#0 is invalid. Meanwhile, the other three SLIVs are valid, since they overlap with flexible or uplink symbols in the semi-static TDD UL-DL configuration. The UE can expect the delay T2 between the end symbol of PDCCH and the first symbol of the first valid PUSCH, e.g. PUSCH#1, to be equal to or greater than the required PUSCH preparation time. Meanwhile, there is no requirement on the delay T1 between the end symbol of PDCCH and the first symbol of the invalid PUSCH#0. That is, T1 can be smaller than the required PUSCH preparation time.

[0022] In one embodiment, in case of multi-PUSCH scheduling, the delay between the end symbol of the PDCCH and the start symbol of the first valid PUSCH among the multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the PUSCH preparation time after considering the effect of timing advance. In some embodiments, a valid PUSCH indicates that it does not overlap with DL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or symbols of an SS / PBCH block with index provided by ssb-PositionsInBurst.

[0023] In one embodiment, in case of multi-PUSCH scheduling, the delay between the end symbol of a PDCCH and the start symbol of each of the multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the PUSCH preparation time after considering the effect of timing advance. In particular, the above restriction on the PUSCH preparation time also applies to PUSCHs that overlap with DL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or symbols of an SS / PBCH block with index provided by ssb-PositionsInBurst.

[0024] In some embodiments, when a UE is scheduled with multiple PUSCHs by the DCI, the delay between the PDCCH and the scheduled PUSCH indicated by the TDRA information field should satisfy the following condition: ● Slot offset K2 and K offset If the first uplink symbol in a valid PUSCH allocation for a transport block indicated by the TDRA information field, including the DM-RS, is not earlier than symbol L2, as defined by the start S and length L of the PUSCH allocation indicated by the "time domain resource allocation" of the scheduling DCI (if configured), including the effect of timing advance, then the UE shall transmit the transport block, where L2 is the symbol T after the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH. proc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ T c +T ext +T switch ,d 2,2), when the PDCCH candidates are associated with a search space set configured in searchSpaceLinking, for the purpose of determining the last symbol of the PDCCH carrying DCI scheduling the PUSCH, the PDCCH candidate that ends later in time of the two configured PDCCH candidates is used.

[0025] UE PDSCH reception preparation time for multi-PDSCH scheduling In one embodiment, in case of multi-PDSCH scheduling, for cross-carrier scheduling with different SCS, the delay between the end symbol of a PDCCH and the start symbol of a valid PDSCH among multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the minimum scheduling delay. The PDCCH carrying the scheduling DCI is spaced apart from one OFDM subcarrier interval (μ PDCCH ), and the PDSCH scheduled to be received by the DCI is received on one carrier with a different OFDM subcarrier spacing (μ PDSCH ) on another carrier.

[0026] In some embodiments, a valid PDSCH is a PDSCH that does not overlap with a UL symbol indicated by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided).

[0027] In one option, the minimum scheduling delay is checked after determining valid PDSCHs among multiple PDSCHs scheduled by DCI. A PDSCH is valid if it does not overlap with uplink symbols indicated by the semi-static TDD UL-DL configuration. In some embodiments, when a UE is scheduled with multiple PDSCHs by DCI, the delay between the PDCCH and the valid PDSCH needs to satisfy one or more of the following conditions: μ PDCCH <μ PDSCH In this case, the first symbol in the PDSCH allocation, including the DM-RS, occurs at least N after the end of the PDCCH that schedules the PDSCH, as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI. pdsch If PDSCH reception starts at this PDCCH symbol no earlier than the first symbol of the slot, the UE is expected to receive a valid scheduled PDSCH without considering the effect of the reception timing difference between the scheduling cell and the scheduled cell. μ PDCCH >μ PDSCH In this case, the first symbol in the PDSCH allocation, including the DM-RS, occurs N after the end of the PDCCH that schedules the PDSCH, as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI. pdsch 1 PDCCH symbols earlier, without considering the effect of the reception timing difference between the scheduling cell and the scheduled cell, the UE Valid It is expected to receive the scheduled PDSCH. In some embodiments, N pdsch The value of is the subcarrier spacing of the PDCCH (μ PDCCH ) may be determined based on Table 5.5-1. Table 5.5-1 shows an example. In some embodiments, when the PDCCH candidates are associated with a search space set consisting of searchSpaceLinking, N pdsch For the purpose of determining, the PDCCH candidate that ends later in time of the two configured PDCCH candidates is used.

[0028] [Table 1]

[0029] Figure 3 shows an example of minimum PDCCH to PDSCH scheduling delay for valid PDSCHs scheduled by DCI. Assume that DCI schedules a row of TDRA consisting of four SLIVs. The first SLIV, e.g. PDSCH#0, overlaps with an UL symbol according to the semi-static TDD UL-DL configuration, and therefore PDSCH#0 is invalid. Meanwhile, the other three SLIVs are valid since they overlap with flexible or downlink symbols in the semi-static TDD UL-DL configuration. The UE can expect the delay T2 between the end symbol of PDCCH and the first symbol of the first valid PDSCH, e.g. PDSCH#1, to be equal to or greater than the required minimum scheduling delay. Meanwhile, there is no requirement on the delay T1 between the end symbol of PDCCH and the first symbol of the invalid PDSCH#0. That is, T1 can be smaller than the required minimum scheduling delay.

[0030] In one embodiment, in case of multi-PDSCH scheduling, for cross-carrier scheduling with different SCS, the delay between the end symbol of a PDCCH and the start symbol of the first valid PDSCH among multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the minimum scheduling delay. The PDCCH carrying the scheduling DCI is spaced apart from one OFDM subcarrier interval (μ PDCCH ), and the PDSCH scheduled to be received by the DCI is received on one carrier with a different OFDM subcarrier spacing (μ PDSCH ) on a different carrier.

[0031] In one embodiment, in case of multi-PDSCH scheduling, for cross-carrier scheduling with different SCS, the delay between the end symbol of a PDCCH and the start symbol of a PDSCH among multiple PUSCHs scheduled by the PDCCH should be equal to or greater than the minimum scheduling delay. In particular, the above restriction on the minimum scheduling delay also applies to PDSCHs that overlap with UL symbols indicated by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided).

[0032] When a UE is scheduled with multiple PDSCHs by the DCI, the delay between the PDCCH and the scheduled PDSCH indicated by the TDRA information field should satisfy one or more of the following conditions: μ PDCCH <μ PDSCH In this case, the first symbol in the PDSCH allocation, including the DM-RS, occurs at least N after the end of the PDCCH that schedules the PDSCH, as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI. pdsch If the PDSCH reception starts at this PDCCH symbol no earlier than the first symbol of the slot, the UE is expected to receive the scheduled PDSCH, as indicated by the TDRA information field, without taking into account the effect of the reception timing difference between the scheduling cell and the scheduled cell. μ PDCCH >μ PDSCH In this case, the first symbol in the PDSCH allocation, including the DM-RS, occurs N after the end of the PDCCH that schedules the PDSCH, as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI. pdschIf the UE does not start earlier than 1 PDCCH symbols, the UE is expected to receive the scheduled PDSCH without considering the effect of the receive timing difference between the scheduling cell and the scheduled cell. When the PDCCH candidates are associated with a search space set consisting of searchSpaceLinking, N pdsch For the purpose of determining, the PDCCH candidate that ends later in time of the two configured PDCCH candidates is used.

[0033] TCI State / QCL Decision for Multi-PDSCH Scheduling In one embodiment, when the UE is configured with multi-PDSCH transmission, the indicated TCI state may be based on the activated TCI state in the first slot with a valid PDSCH, and the UE shall expect the activated TCI state to be the same across slots with scheduled PDSCHs. In this scheme, the activated TCI state is determined after determining the valid PDSCHs among the multiple PDSCHs scheduled by the DCI. In some embodiments, a PDSCH is valid if it does not overlap with the uplink symbols indicated by the semi-static TDD UL-DL configuration.

[0034] When the UE is configured with a multi-slot PDSCH, the indicated TCI state may be based on the activated TCI state in the first slot with a scheduled PDSCH, and the UE may expect the activated TCI state to be the same across slots with scheduled PDSCH. When the UE is configured with the higher layer parameter PDSCH time domain allocation list for multi-PDSCH (pdsch-TimeDomainAllocationListForMultiPDSCH-r17) and is not configured with a multi-slot PDSCH, the indicated TCI state should be based on the activated TCI state in the slot corresponding to the first valid PDSCH.

[0035] In one option, if tci-PresentInDCI is set to "enabled" or tci-PresentDCI-1-2 is configured for the control resource set (CORESET) that schedules the PDSCH, and the time offset between the reception of the DL DCI and the corresponding first valid PDSCH is equal to or greater than timeDurationForQCL (if applicable), after the UE receives the initial higher layer configuration of the TCI state and before the reception of the activation command, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the SS / PBCH block determined in the initial access procedure for qcl-Type set to "typeA" and also for qcl-Type set to "typeD" (when applicable).

[0036] In another option, if the PDSCH is scheduled with a DCI format in which the TCI field is absent and the time offset between the reception of the DL DCI and the corresponding first valid PDSCH of the serving cell is greater than or equal to a threshold timeDurationForQCL (if applicable), where the threshold is based on the reported UE capabilities (e.g. as described in 3GPP Technical Standard (TS) 38.306), then to determine the PDSCH antenna port quasi-co-location, the UE shall assume that the TCI state or QCL assumption of the PDSCH is identical to the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0037] In another option, when the UE is configured with both sfnSchemePdcch and sfnSchemePdsch scheduled by DCI format 1_0 or DCI format 1_1 / 1_2, if the time offset between reception of DL DCI and the corresponding first valid PDSCH of the serving cell is greater than or equal to a threshold timeDurationForQCL (if applicable): If the UE supports DCI scheduling without a TCI field, the UE shall assume that the TCI state or QCL assumption of the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for receiving DL DCI in the active BWP of the serving cell, regardless of the number of active TCI states in the CORESET. If the UE does not support dynamic switching between SFN PDSCH and non-SFN PDSCH, the UE shall be activated with a CORESET with two TCI states. - Otherwise, if the UE does not support DCI scheduling without the TCI field, the UE shall expect the TCI field to be present when scheduled by DCI format 1_1 / 1_2.

[0038] In another option, for PDSCH scheduled by DCI formats 1_0, 1_1, 1_2, when the UE is configured with sfnSchemePdcch set to "sfnSchemeA", when sfnSchemePdsch is not configured and there is no TCI codepoint with two TCI states in the activation command, if the time offset between the reception of the DL DCI and the corresponding first valid PDSCH is greater than or equal to the threshold timeDurationForQCL (if applicable) and the CORESET scheduling the PDSCH is indicated with two TCI states, the UE shall assume that the TCI state or QCL assumption of the PDSCH is identical to the first TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the serving cell's active BWP.

[0039] In another option, if the time offset between the reception of the DL DCI and the corresponding first valid PDSCH is greater than or equal to a threshold timeDurationForQCL, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS of the TCI state with respect to the QCL type parameter given by the indicated TCI state, where the threshold is based on the reported UE capabilities (as described in TS 38.306). When the UE is configured with a single-slot PDSCH, the indicated TCI state should be based on the activated TCI state in the slot with a scheduled PDSCH.

[0040] In another option, if the UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with enableDefaultBeamForCCS, the UE expects tci-PresentInDCI to be set as "enabled" or tci-PresentDCI-1-2 to be configured for CORESET, and if one or more of the TCI states configured for the serving cells scheduled by the search space set include qcl-Type set to "typeD", the UE expects the time offset between reception of a detected PDCCH in the search space set and the corresponding first valid PDSCH to be greater than or equal to a threshold timeDurationForQCL.

[0041] In one option, independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding first valid PDSCH is less than a threshold timeDurationForQCL and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to "typeD"; The UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-colocated with the RS for the PDCCH quasi-colocation indication of the CORESET associated with the monitoring search space with the lowest controlResourceSetId in the latest slot where one or more CORESETs in the active BWP of the serving cell are monitored by the UE. In this case, if the qcl-Type is set to "typeD" for the PDSCH DM-RS, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET if it differs from that of the PDCCH DM-RS with which they overlap in at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers). -If the UE is configured with enableDefaultTCI-StatePerCoresetPoolIndex and the UE is configured by a higher layer parameter PDCCH-Config that includes two different values ​​of coresetPoolIndex in different ControlResourceSets; The UE may assume that the DM-RS port of the PDSCH associated with the value of coresetPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameters used for the indication of PDCCH quasi-colocation of the CORESET associated with the monitoring search space with the lowest controlResourceSetId among the CORESETs configured with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH in the latest slot where one or more CORESETs associated with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH in the active BWP of the serving cell are monitored by the UE. In this case, if the "QCL-TypeD" of the PDSCH DM-RS is different from that of the overlapping PDCCH DM-RS in at least one symbol and they are associated with the same value of coresetPoolIndex, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers). - If the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the PDSCH transmission opportunity of the DM-RS port or serving cell of the PDSCH is quasi-co-located with the RS for the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. When the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or configured with the higher layer parameter repetitionNumber and the offset between the reception of the DL DCI and the first PDSCH transmission opportunity is less than the threshold timeDurationForQCL, the mapping of the TCI state to the PDSCH transmission opportunity is determined according to clause 5.1.2.1 by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states based on the activated TCI state in the slot with the first PDSCH transmission opportunity. In this case, the UE is expected to prioritize reception of the PDCCH associated to that CORESET if the "QCL-TypeD" in both TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states differs from that of the PDCCH DM-RS with which they overlap in at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers).

[0042] Another option is if a PDCCH carrying a scheduling DCI is received on one component carrier and the PDSCH scheduled by that DCI is on another component carrier: -timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCH Additional timing delay if

number

[0043] In another option, when a PDCCH candidate is associated with a search space set configured in searchSpaceLinking for a configuration of tci-PresentInDCI or tci-PresentDCI-1-2, the UE expects the same configuration in the first and second CORESETs associated with the configured PDCCH candidate, and if the PDSCH is scheduled by a DCI format that does not have a TCI field and if the scheduling offset between the DCI and the corresponding first valid PDSCH is equal to or greater than timeDurationForQCL (if applicable), the assumption of the PDSCH QCL is based on the CORESET with the lower ID among the first and second CORESETs associated with the configured PDCCH candidate.

[0044] FIG. 4 shows an example of TCI state determination for valid PDSCHs scheduled by DCI. It is assumed that DCI schedules a row of TDRA consisting of four SLIVs. The first SLIV, e.g. PDSCH#0, overlaps with an UL symbol according to the semi-static TDD UL-DL configuration, therefore PDSCH#0 is invalid. Meanwhile, the other three SLIVs are valid since they overlap with flexible or downlink symbols in the semi-static TDD UL-DL configuration. In FIG. 4, the delay T2 between the end symbol of PDCCH and the first symbol of the first valid PDSCH, e.g. PDSCH#1, is greater than timeDurationForQCL. Therefore, the UE receives valid PDSCH 1 / 2 / 3 according to the TCI state indicated by DCI. There is no requirement on the delay T1 between the end symbol of PDCCH and the first symbol of invalid PDSCH#0. That is, even when T1 is less than timeDurationForQCL, the UE still uses the TCI state indicated by the DCI for PDSCH reception.

[0045] Figure 5 shows another example of TCI state determination for valid PDSCHs scheduled by DCI. It is assumed that DCI schedules a row of TDRA consisting of four SLIVs. It assumes that according to the semi-static TDD UL-DL configuration, all symbols are DL symbols, and therefore all four PDSCHs are invalid. In Figure 5, the delay T1 between the end symbol of PDCCH and the first symbol of the first valid PDSCH, e.g. PDSCH#0, is less than timeDurationForQCL. Thus, for the indication of PDCCH quasi-co-location of CORESET associated with the monitoring search space with the lowest controlResourceSetId in the latest slot where one or more CORESETs in the active BWP of the serving cell are monitored by the UE, the UE receives four valid PDSCHs, assuming that the DM-RS port of the PDSCH is quasi-co-located with the RS.

[0046] In one embodiment, when the UE is configured with multi-PDSCH transmission, the indicated TCI state should be based on the activated TCI state in the first slot with a scheduled PDSCH indicated by the TDRA information field, and the UE shall expect the activated TCI state to be the same across slots with scheduled PDSCHs, i.e., the scheduled PDSCH of said first slot may overlap with the UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided). In this scheme, the activated TCI state is determined by the scheduled PDSCH associated by DCI to the first SLIV configured in the indicated row of the TDRA field.

[0047] When the UE is configured with a multi-slot PDSCH, the indicated TCI state shall be based on the activated TCI state in the first slot with a scheduled PDSCH and the UE shall expect the activated TCI state to be the same across slots with scheduled PDSCH. When the UE is configured with higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH-r17 and is not configured with a multi-slot PDSCH, the indicated TCI state shall be based on the activated TCI state in the slot corresponding to the first scheduled PDSCH indicated by the TDRA information field.

[0048] In one option, if tci-PresentInDCI is set to "enabled" or tci-PresentDCI-1-2 is configured for the CORESET scheduling PDSCH and the time offset between the reception of DL DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field is equal to or greater than timeDurationForQCL (if applicable), after the UE receives the initial higher layer configuration of the TCI state and before the reception of the activation command, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the SS / PBCH block determined in the initial access procedure for qcl-Type set to "typeA" and, when applicable, for qcl-Type set to "typeD".

[0049] In another option, if a PDSCH is scheduled by a DCI format without a TCI field and the reception of DL DCI and the time offset of the first scheduled PDSCH indicated by the TDRA information field of the corresponding serving cell is greater than or equal to a threshold timeDurationForQCL (if applicable), where the threshold is based on the reported UE capabilities (as described in TS 38.306), then in order to determine the PDSCH antenna port quasi-co-location, the UE shall assume that the TCI state or QCL assumption of the PDSCH is identical to the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0050] In another option, when the UE is configured with both sfnSchemePdcch and sfnSchemePdsch scheduled by DCI format 1_0 or by DCI format 1_1 / 1_2, if the time offset between the reception of the DL DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field of the serving cell is greater than or equal to a threshold timeDurationForQCL (if applicable): If the UE supports DCI scheduling without a TCI field, the UE shall assume that the TCI state or QCL assumption of the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for receiving DL DCI in the active BWP of the serving cell, regardless of the number of active TCI states in the CORESET. If the UE does not support dynamic switching between SFN PDSCH and non-SFN PDSCH, the UE shall be activated with a CORESET with two TCI states. - Otherwise, if the UE does not support DCI scheduling without the TCI field, the UE expects the TCI field to be present when scheduled by DCI format 1_1 / 1_2.

[0051] In another option, for PDSCH scheduled by DCI formats 1_0, 1_1, 1_2, when the UE is configured with sfnSchemePdcch set to "sfnSchemeA", when sfnSchemePdsch is not configured and there is no TCI codepoint with two TCI states in the activation command, if the time offset between the reception of the DL DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field is greater than or equal to the threshold timeDurationForQCL (if applicable) and the CORESET scheduling the PDSCH is indicated with two TCI states, the UE shall assume that the TCI state or QCL assumption of the PDSCH is identical to the first TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the serving cell's active BWP.

[0052] In another option, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS of the TCI state with respect to the QCL type parameter given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field is greater than or equal to a threshold timeDurationForQCL (where the threshold is based on the reported UE capabilities [TS 38.306]). When the UE is configured with a single-slot PDSCH, the indicated TCI state should be based on the activated TCI state in the slot with the scheduled PDSCH.

[0053] In another option, when the UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with enableDefaultBeamForCCS, the UE expects tci-PresentInDCI to be set as "enabled" or tci-PresentDCI-1-2 to be configured for the CORESET, and if one or more of the TCI states configured for the serving cells scheduled by the search space set include qcl-Type set to "typeD", the UE expects the time offset between reception of a detected PDCCH in the search space set and the corresponding first scheduled PDSCH indicated by the TDRA information field to be greater than or equal to a threshold timeDurationForQCL.

[0054] In one option, independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the offset between reception of DL DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field is less than a threshold timeDurationForQCL and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to "typeD"; The UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS with respect to the QCL parameter used for the indication of PDCCH quasi-co-location of the CORESET associated with the monitoring search space with the lowest controlResourceSetId in the latest slot where one or more CORESETs in the active BWP of the serving cell are monitored by the UE. In this case, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET if the qcl-Type is set to "typeD" for the PDSCH DM-RS and differs from that of the PDCCH DM-RS with which they overlap in at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers). -If the UE is configured with enableDefaultTCI-StatePerCoresetPoolIndex and the UE is configured by a higher layer parameter PDCCH-Config that includes two different values ​​of coresetPoolIndex in different ControlResourceSets; The UE may assume that the DM-RS port of the PDSCH associated with the value of coresetPoolIndex of the serving cell is quasi-colocated with the RS with respect to the QCL parameters used for the PDCCH quasi-colocation indication of the CORESET associated with the monitoring search space with the lowest controlResourceSetId among the CORESETs configured with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH in the latest slot where one or more CORESETs associated with the same coresetPoolIndex as the PDCCH scheduling the PDSCH in the active BWP of the serving cell are monitored by the UE. In this case, if the "QCL-TypeD" of the PDSCH DM-RS is different from that of the overlapping PDCCH DM-RS in at least one symbol and they are associated with the same value of coresetPoolIndex, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers). - If the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the PDSCH transmission opportunity of the DM-RS port or serving cell of the PDSCH is quasi-co-located with the RS for the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. When the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or configured with the higher layer parameter repetitionNumber and the offset between the reception of the DL DCI and the first PDSCH transmission opportunity is less than the threshold timeDurationForQCL, the mapping of the TCI state to the PDSCH transmission opportunity is determined according to clause 5.1.2.1 by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states based on the activated TCI state in the slot with the first PDSCH transmission opportunity. In this case, the UE is expected to prioritize reception of the PDCCH associated to that CORESET if the "QCL-TypeD" in both TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states differs from that of the PDCCH DM-RS with which they overlap in at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers).

[0055] Another option is if a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by that DCI is on another component carrier: -timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCH Additional timing delay if

number

[0056] In another option, when a PDCCH candidate is associated to a search space set configured in searchSpaceLinking for a configuration of tci-PresentInDCI or tci-PresentDCI-1-2, the UE expects the same configuration in the first and second CORESETs associated to the configured PDCCH candidate, and if the PDSCH is scheduled by a DCI format in which the TCI field is not present, the PDSCH QCL assumption is based on the CORESET with the lower ID in the first and second CORESETs associated to the configured PDCCH candidate if the scheduling offset between the DCI and the corresponding first scheduled PDSCH indicated by the TDRA information field is equal to or greater than timeDurationForQCL (if applicable).

[0057] System and Implementation 6-8 illustrate various systems, devices and components in which aspects of the disclosed embodiments may be implemented.

[0058] 6 illustrates a network 600 in accordance with various embodiments. Network 600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited in this respect and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems, etc.

[0059] The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with the RAN 604 via an over-the-air connection. The UE 602 may be communicatively coupled to the RAN 604 by a Uu interface. The UE 602 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0060] In some embodiments, the network 600 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0061] In some embodiments, the UE 602 may further communicate with the AP 606 via a terrestrial connection. The AP 606 may manage the WLAN connection, which may be responsible for offloading some / all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may conform to any IEEE 802.11 protocol, where the AP 606 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 602, the RAN 604, and the AP 606 may use cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may include the UE 602 being configured by the RAN 604 to use both cellular radio resources and WLAN resources.

[0062] The RAN 604 may include one or more access nodes, such as the AN 608. The AN 608 may terminate air interface protocols for the UE 602 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 608 may enable data / voice connectivity between the CN 620 and the UE 602. In some embodiments, the AN 608 may be implemented in a separate device or as one or more software entities running on a server computer as part of a virtual network, which may also be referred to as a CRAN or virtual baseband unit pool. The AN 608 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, Node B, RSU, TRxP, TRP, etc. The AN 608 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0063] In embodiments where the RAN 604 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments and may allow the ANs to communicate information regarding handover, data / context transfer, mobility, load management, interference coordination, etc.

[0064] Each of the ANs of the RAN 604 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 602 with an air interface for network access. The UE 602 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 604. For example, the UE 602 and the RAN 604 may use carrier aggregation to enable the UE 602 to connect with multiple component carriers, each of which corresponds to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first AN / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0065] The RAN 604 may provide an air interface over a licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques with the PCell / Scell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example based on a listen-before-talk (LBT) protocol.

[0066] In a V2X scenario, the UE 602 or AN 608 may be or operate as an RSU, which may refer to any transportation infrastructure entity used for V2X communication. The RSU may be implemented in or by an appropriate AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; in the case of an eNB, it may be referred to as an "eNB-type RSU"; in the case of a gNB, it may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuitry that stores intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communication necessary for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a traffic signal controller or a network interface controller to provide a wired connection (e.g., Ethernet) to a backhaul network.

[0067] In some embodiments, the RAN 604 may be an LTE RAN 610 having an eNB, e.g., eNB 612. The LTE RAN 610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in bands below 6 GHz.

[0068] In some embodiments, the RAN 604 may be an NG-RAN 614 having a gNB, e.g., gNB 616, or an ng-eNB, e.g., ng-eNB 618. The gNB 616 may connect with a 5G-capable UE using a 5G NR interface. The gNB 616 may connect with a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 may also connect with a 5G core via an NG interface, but may connect with a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 may connect with each other via an Xn interface.

[0069] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., the N3 interface), which carries traffic data between nodes of the NG-RAN 614 and the UPF 648, and an NG Control Plane (NG-C) interface (e.g., the N2 interface), which is the signaling interface between nodes of the NG-RAN 614 and the AMF 644.

[0070] The NG-RAN 614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operate in the FR1 band, which includes bands below 6 GHz, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0071] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For example, a UE 602 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWPs relates to power saving. In particular, multiple BWPs can be configured for a UE 602 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP with a smaller number of PRBs can be used for data transmission with low traffic load while enabling power saving in the UE 602 and possibly the gNB 616. A BWP with a larger number of PRBs can be used for higher traffic load scenarios.

[0072] The RAN 604 is communicatively coupled to the CN 620, which includes network elements that provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UEs 602). The components of the CN 620 may be implemented within one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize some or all of the functions provided by the network elements of the CN 620 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.

[0073] In some embodiments, the CN 620 may be an LTE CN 622, which may also be referred to as an EPC. The LTE CN 622 may include an MME 624, an SGW 626, an SGSN 628, an HSS 630, a PGW 632, and a PCRF 634 coupled together via interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 622 may be briefly introduced as follows.

[0074] The MME 624 may implement mobility management functions that track the current location of the UE 602 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0075] The SGW 626 may terminate the S1 interface to the RAN and route data packets between the RAN and the LTE CN 622. The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0076] The SGSN 628 may track the location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 624; MME selection for handover, etc. The S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0077] The HSS 630 may include a database for network users containing subscription-related information to support processing of communication sessions by network entities. The HSS 630 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 620.

[0078] The PGW 632 may terminate an SGI interface to a data network (DN) 636, which may include an application / content server 638. The PGW 632 may route data packets between the LTE CN 622 and the data network 636. The PGW 632 may be coupled to the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node for policy enforcement and charging data collection (e.g., PCEF). In addition, the SGi reference point between the PGW 632 and the data network 636 may be an operator external public, private PDN, or intra-operator packet data network, e.g., for the provision of IMS services. The PGW 632 may be coupled to the PCRF 634 via a Gx reference point.

[0079] The PCRF 634 is the policy and charging control element of the LTE CN 622. The PCRF 634 is communicatively coupled to an application / content server 638 and may determine appropriate QoS and charging parameters for a service flow. The PCRF 632 may provision the relevant rules to the PCEF (via the Gx reference point) with the appropriate TFT and QCI.

[0080] In some embodiments, the CN 620 may be a 5GC 640. The 5GC 640 may include an AUSF 642, an AMF 644, an SMF 646, a UPF 648, an NSSF 650, an NEF 652, an NRF 654, a PCF 656, a UDM 658, and an AF 660 coupled together via interfaces (or "reference points") as shown. The function of each component of the 5GC 640 may be briefly introduced as follows.

[0081] The AUSF 642 may store data for authentication of the UE 602 and process authentication related functionality. The AUSF 642 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the GC 640 via the reference points shown, the AUSF 642 may present a Nausf service-based interface.

[0082] The AMF 644 may enable other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and subscribe to notifications regarding mobility events related to the UE 602. The AMF 644 may be involved in registration management (e.g., to register the UE 602), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646 and act as a transparent proxy for routing SM messages. The AMF 644 may also provide transport for SMS messages between the UE 602 and the SMSF. The AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Additionally, the AMF 644 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 604 and the AMF 644, and the AMF 644 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 644 may also support NAS signaling with the UE 602 over the N3 IWF interface.

[0083] The SMF 646 may be involved in SM (e.g., session establishment, tunnel management between the UPF 648 and the AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering in the UPF 648 to route traffic to the appropriate destination; termination of the interface towards the policy control function; control of policy enforcement, charging and part of the QoS; lawful intercept (for SM events and interface to the LI system); termination of the SM part of NAS messages; downlink data notification; initiating AN-specific SM information to be sent over N2 to the AN 608 via the AMF 644; and determining the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.

[0084] The UPF 648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 636, and a branching point for supporting multi-homed PDU sessions. The UPF 648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering, and downlink data notification triggering. The UPF 648 may include an uplink classifier that supports routing traffic flows to the data network.

[0085] The NSSF 650 may select a set of network slice instances to serve the UE 602. The NSSF 650 may also determine the allowed NSSAIs and mapping to subscribed S-NSSAIs, if necessary. The NSSF 650 may also determine the AMF set used to serve the UE 602 or may determine a list of candidate AMFs based on an appropriate configuration and possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 to which the UE 602 is registered by interacting with the NSSF 650, which may result in a change of AMF. The NSSF 650 may interact with the AMF 644 via the N22 reference point and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 650 may present an Nnssf service-based interface.

[0086] The NEF 652 may securely expose services and capabilities offered by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AFs 660), edge computing or fog computing systems, etc. In such an embodiment, the NEF 652 may authenticate, authorize or throttle the AFs. The NEF 652 may also translate information exchanged with the AFs 660 and with internal network functions. For example, the NEF 652 may translate between AF service identifiers and internal 5GC information. The NEF 652 may also receive information from other NFs based on the exposed capabilities of the other NFs. This information may be stored in the NEF 652 as structured data or in a data storage NF using a standardized interface. The stored information may then be re-exposed by the NEF 652 to other NFs and AFs or used for other purposes such as analytics. In addition, the NEF 652 may present an Nnef service-based interface.

[0087] The NRF 654 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to the NF instances. The NRF 654 also maintains information of available NF instances and their supported services. As used herein, terms such as "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 654 may present an Nnrf service-based interface.

[0088] The PCF 656 may provide policy rules to the control plane functions to enforce them and may also support a unified policy framework for managing network behavior. The PCF 656 may also implement a front end to access subscription information related to policy decisions in the UDRs of the UDM 658. In addition to communicating with functions through reference points as shown, the PCF 656 presents an Npcf service-based interface.

[0089] The UDM 658 may process subscription related information to support processing of communication sessions by network entities and may store subscription data of the UE 602. For example, the subscription data may be communicated via the N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts: an application front end and a UDR. The UDR may store structured data for subscription and policy data for the UDM 658 and the PCF 656, and / or public and application data for the NEF 652 (including PFD for application discovery, application requirement information for multiple UEs 602). A Nudr service-based interface may be exposed by the UDR 221 to enable the UDM 658, the PCF 656, and the NEF 652 to access a particular set of stored data, read, update (e.g., add, modify), delete, subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends may service the same user with different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 658 may present a Nudm service-based interface.

[0090] The AF 660 may provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0091] In some embodiments, the 5GC 640 may enable edge computing by selecting an operator / third party service to be geographically close to the point where the UE 602 is attached to the network. This may reduce network latency and load. To provide edge computing implementation, the 5GC 640 may select a UPF 648 close to the UE 602 and perform traffic steering from the UPF 648 to the data network 636 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing. Based on the operator's deployment, when the AF 660 is considered to be a trusted entity, the network operator may allow the AF 660 to directly interact with the associated NFs. In addition, the AF 660 may present a Naf service-based interface.

[0092] Data network 636 may represent various network operator services, Internet access, or third party services, which may be provided by one or more servers, including, for example, application / content server 638 .

[0093] 7 illustrates a schematic of a wireless network 700 in accordance with various embodiments. The wireless network 700 may include a UE 702 in wireless communication with an AN 704. The UE 702 and the AN 704 may be similar to similarly named components described elsewhere herein and may be substantially interchangeable.

[0094] The UE 702 may be communicatively coupled to the AN 704 via a connection 706. The connection 706 is shown as an air interface for enabling the communicative coupling and may correspond to a cellular communication protocol such as mmWave or an LTE protocol or a 5G NR protocol operating at frequencies below 6 GHz.

[0095] The UE 702 may include a host platform 708 coupled to a modem platform 710. The host platform 708 may include an application processing circuit 712, which may be coupled to a protocol processing circuit 714 of the modem platform 710. The application processing circuit 712 may execute various applications for the UE 702 that source / sink application data. The application processing circuit 712 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0096] The protocol processing circuitry 714 may implement one or more layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0097] The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include PHY operations, including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulated signal mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time coding, space-frequency coding, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0098] The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and an RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 720 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 722 may include low noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 724 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panel 726 (collectively referred to as the "transmit / receive components") may be specific to the details of a particular implementation, for example, whether the communications are TDM or FDM, mmWave or frequencies below 6 GHz, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc.

[0099] In some embodiments, the protocol processing circuit 714 may include one or more instances of control circuitry (not shown) for providing control functions to the transmit / receive components.

[0100] UE reception may be established by and through the antenna panel 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panel 726 may receive transmissions from the AN 704 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 726.

[0101] UE transmissions may be established by and through the protocol processing circuitry 714, the digital baseband circuitry 716, the transmit circuitry 718, the RF circuitry 722, the RFFE 724, and the antenna panel 726. In some embodiments, the transmit components of the UE 704 may apply spatial filters to the data to be transmitted to form transmit beams that are radiated by the antenna elements of the antenna panel 726.

[0102] Similar to the UE 702, the AN 704 may include a host platform 728 coupled to a modem platform 730. The host platform 728 may include an application processing circuit 732 coupled to a protocol processing circuit 734 of the modem platform 730. The modem platform may further include a digital baseband circuit 736, a transmit circuit 738, a receive circuit 740, an RF circuit 742, an RFFE circuit 744, and an antenna panel 746. The components of the AN 704 may be similar to, and substantially interchangeable with, the like-named components of the UE 702. In addition to performing data transmission / reception as described above, the components of the AN 704 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0103] FIG. 8 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods described herein. Specifically, FIG. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 802 may execute to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 800.

[0104] Processor 810 may include, for example, processor 812 and processor 814. Processor 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0105] The memory / storage device 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 820 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0106] Communications resources 830 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 804 or one or more databases 806 or other network elements over network 808. For example, communications resources 830 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth (or Bluetooth Low Energy) components, Wi-Fi components, and other communications components.

[0107] The instructions 850 may include software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 810 to perform any one or more of the methodologies described herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., in a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. Additionally, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral device 804 or the database 806. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable and machine-readable media.

[0108] Exemplary Procedure In some embodiments, the electronic device, network, system, chip, or component of FIG. 6-FIG. 8 or some other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. For example, FIG. 9 illustrates an example process 900 according to various embodiments. The process 900 may be performed by a UE or a portion thereof. At 902, the process 900 may include decoding downlink control information (DCI) that schedules multiple physical downlink shared channels (PDSCHs). At 904, the process 900 may further include determining a transmission configuration indicator (TCI) state for the PDSCHs based on a time domain resource allocation (TDRA) field in the DCI and one or more activated TCI states in the earliest slot in which one of the PDSCHs is scheduled. At 906, the process 900 may further include receiving the PDSCHs based on the determined TCI state.

[0109] FIG. 10 illustrates another process 1000 according to various embodiments. Process 1000 may be performed by a UE or a portion thereof. At 1002, process 1000 may include decoding downlink control information (DCI) that schedules multiple physical uplink shared channels (PUSCHs). At 1004, process 1000 may further include identifying one or more valid PUSCHs from among the multiple PUSCHs scheduled by the DCI based on the DCI, where the one or more valid PUSCHs are identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) that includes the DCI and a start symbol of a valid PUSCH among the multiple PUSCHs, where the delay is based on a PUSCH preparation time and a timing advance. At 1006, process 1000 may further include encoding the one or more valid PUSCHs for transmission.

[0110] FIG. 11 illustrates another process 1100 according to various embodiments. The process 1100 may be performed by a UE or a portion thereof. At 1102, the process 1100 may include decoding downlink control information (DCI) that schedules a plurality of physical downlink shared channels (PDSCHs) including a first PDSCH on a second carrier having a second SCS on a first carrier having a first subcarrier spacing (SCS). At 1104, the process 1100 further includes identifying one or more valid PDSCHs from among the plurality of PDSCHs scheduled by the DCI based on the DCI, where the one or more valid PUSCHs are identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) including the DCI and a start symbol of the valid PDSCH that is greater than or equal to a minimum scheduling delay. At 1106, the process 1100 may further include decoding the one or more valid PDSCHs.

[0111] For one or more embodiments, at least one of the components described in one or more of the preceding drawings may be configured to perform one or more of the operations, techniques, processes, and / or methods as described in the example section below. For example, the baseband circuitry described above in connection with one or more of the preceding drawings may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the preceding drawings may be configured to operate according to one or more of the examples described below in the example section.

[0112] Working Example Example 1 may include one or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed by one or more processors of a user equipment (UE), configure the UE to: decode downlink control information (DCI) that schedules multiple physical downlink shared channels (PDSCHs); determine a transmission configuration indicator (TCI) state for the PDSCHs based on a time domain resource allocation (TDRA) field in the DCI and one or more activated TCI states in an earliest slot in which one of the PDSCHs is scheduled; and receive the PDSCHs based on the determined TCI state.

[0113] Example 2 may include one or more NTCRMs of example 1, wherein the one or more activated TCI states are the same across slots of the PDSCHs.

[0114] Example 3 may include one or more NTCRMs of example 1, wherein the instructions, when executed, further configure the UE to receive a configuration of a PDSCH time domain allocation list for multi-PDSCH scheduling, and the TCI state is determined based on the PDSCH time domain allocation list.

[0115] Example 4 may include one or more NTCRMs of example 1, wherein the TCI state is determined based on a first SLIV of a row of a TDRA table indicated by the TDRA field.

[0116] Example 5 may include one or more NTCRMs of Example 1, wherein the earliest slot in which one of the PDSCHs is scheduled overlaps with an uplink (UL) symbol indicated by a time domain duplexed (TDD) uplink (UL)-downlink (DL) configuration.

[0117] Example 6 may include one or more NTCRMs of example 5, wherein the TDD UD-DL configuration is a common TDD UD-DL configuration or a dedicated TDD UD-DL configuration.

[0118] Example 7 may include one or more NTCRMs of Example 1, wherein the instructions, when executed, further configure the UE to identify, from among the plurality of PDSCHs, one or more valid PDSCHs and one or more invalid PDSCHs based on the DCI.

[0119] Example 8 may include one or more NTCRMs of Example 7, wherein the PDSCHs are scheduled across different carriers having different subcarrier spacings, and the one or more valid PDSCHs are determined based on a delay greater than or equal to a minimum scheduling delay between an ending symbol of a physical downlink control channel (PDCCH) that includes the DCI and a starting symbol of a first valid PDSCH of the plurality of PDSCHs.

[0120] Example 9 may include one or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed by one or more processors of a user equipment (UE), configure the UE to: decode downlink control information (DCI) that schedules multiple physical uplink shared channels (PUSCHs); identify one or more valid PUSCHs from among the multiple PUSCHs scheduled by the DCI based on the DCI, the one or more valid PUSCHs being identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) that includes the DCI and a start symbol of a valid PUSCH from among the multiple PUSCHs, the delay being based on a PUSCH preparation time and a timing advance; and encode the one or more valid PUSCHs for transmission.

[0121] Example 10 may include one or more NTCRMs of Example 9, wherein the validity of the one or more valid PUSCHs is checked after an initial determination that the one or more valid PUSCHs do not overlap with downlink symbols indicated by a time domain duplexed (TDD) uplink-downlink (UL-DL) configuration or symbols configured for transmission of a synchronization signal (SS) / physical broadcast channel (PBCH).

[0122] Example 11 may include one or more NTCRMs of example 9, wherein one or more of the valid PUSCHs overlap with downlink symbols of a time domain duplexed (TDD) uplink-downlink (UL-DL) configuration.

[0123] Example 12 may include the one or more NTCRMs of example 9, wherein the one or more valid PUSCHs are identified based on satisfying a condition that a first uplink symbol in a resource allocation for the PUSCH, including an effect of the timing advance, is not earlier than a symbol L2, where L2 is a time Tproc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ T c +T ext +T switch ,d 2,2 ) is defined as the next uplink symbol having a cyclic prefix starting at

[0124] Example 13 may include one or more NTCRMs of example 12, wherein the resource allocation includes a demodulation reference signal (DM-RS), and a first slot offset value K2, a second slot offset value K3, and a second slot offset value K4. offset , and based on the start S and length L of the resource allocation indicated by the time domain resource allocation in the DCI.

[0125] Example 14 may include one or more NTCRMs according to any one of Examples 9 to 13, wherein the PDCCH is received in PDCCH candidates associated with a search space set configured using search space linking, and the last symbol of the PDCCH corresponds to a first PDCCH candidate among the PDCCH candidates that is latest in time.

[0126] Example 15 may include one or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed by one or more processors of a user equipment (UE), configure the UE to: decode downlink control information (DCI) that schedules, on a first carrier having a first subcarrier spacing (SCS), a plurality of physical downlink shared channels (PDSCHs) including a first PDSCH on a second carrier having a second SCS; identify, based on the DCI, one or more valid PDSCHs from among the plurality of PDSCHs scheduled by the DCI, the one or more valid PDSCHs being identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) including the DCI and a start symbol of a valid PDSCH that is greater than or equal to a minimum scheduling delay; and decode the one or more valid PDSCHs.

[0127] Example 16 may include one or more NTCRMs of Example 15, wherein the validity of the one or more valid PDSCHs is checked after an initial determination that the one or more valid PDSCHs do not overlap with uplink symbols indicated by a time domain duplexed (TDD) uplink-downlink (UL-DL) configuration.

[0128] Example 17 may include one or more NTCRMs of Example 15, wherein if the first SCS is smaller than the second SCS, the minimum scheduling delay is at least N symbols after the last symbol of the PDCCH, including a demodulation reference signal (DM-RS). pdsch corresponding to a first symbol of a resource allocation for a PDSCH that starts no earlier than the first symbol of a slot starting with the N PDCCH symbols, pdsch The number of subcarriers is based on the first subcarrier spacing.

[0129] Example 18 may include one or more NTCRMs of example 15, wherein if the first SCS is greater than the second SCS, the minimum scheduling delay includes a demodulation reference signal (DM-RS) and is N symbols after the last symbol of the PDCCH. pdsch corresponding to a first symbol of a resource allocation for a PDSCH that starts no earlier than N PDCCH symbols, pdsch The number of subcarriers is based on the first subcarrier spacing.

[0130] Example 19 may include one or more NTCRMs of Examples 17 or 18, wherein the resource allocation for the PDSCH is identified based on a slot offset K0 and a start and length indicator value (SLIV) indicated by the DCI.

[0131] Example 20 may include one or more NTCRMs according to any one of Examples 15 to 19, wherein the delay is determined without taking into account a receive timing difference between a first cell associated with the first carrier and a second cell associated with the second carrier.

[0132] Example 21 may include one or more NTCRMs according to any one of Examples 15 to 20, wherein the PDCCH is received in PDCCH candidates associated with a search space set configured using search space linking, and the last symbol of the PDCCH corresponds to a first PDCCH candidate among the PDCCH candidates that is latest in time.

[0133] Example 22 may include a method of wireless communication for multiple PDSCH or PUSCH transmission, the method including: receiving, by a UE, higher layer configuration and TDD UL-DL configuration on multi-PDSCH or multi-PUSCH scheduling; determining, by the UE, DCI for scheduling the multiple PDSCHs or PUSCHs; and processing, by the UE, valid scheduled PDSCHs or PUSCHs.

[0134] Example 23 may include the method of Example 22 or any other example herein, wherein a delay between an end symbol of a PDCCH and a start symbol of a valid PUSCH among a plurality of PUSCHs scheduled by the PDCCH is equal to or greater than a PUSCH preparation time after taking into account the effect of a timing advance.

[0135] Example 24 may include the method of Example 22 or any other example herein, wherein for cross-carrier scheduling with different SCSs, a delay between an end symbol of a PDCCH and a start symbol of a first valid PDSCH among a plurality of PUSCHs scheduled by the PDCCH is greater than or equal to a minimum scheduling delay.

[0136] Example 25 may include the method of Example 22 or some other examples herein, wherein when the UE is configured with multi-PDSCH transmission, the indicated TCI state is based on an activated TCI state in the first slot having a valid scheduled PDSCH, and the UE expects the activated TCI state to be the same across slots having a scheduled PDSCH.

[0137] Example 26 may include a method for a UE, the method including: receiving configuration information for multi-PDSCH or multi-PUSCH scheduling and a TDD UL-DL configuration; decoding DCI scheduling a plurality of PDSCHs or PUSCHs; and determining, based on the DCI, one or more valid PDSCHs or PUSCHs from among the plurality of PDSCHs or PUSCHs scheduled by the DCI.

[0138] Example 27 may include the method of Example 26 or some other example herein, wherein the one or more valid PUSCHs are determined based on a delay between an end symbol of a PDCCH including a DCI and a start symbol of a valid PUSCH among the multiple PUSCHs scheduled by the PDCCH, where the delay is based on a PUSCH preparation time and a timing advance.

[0139] Example 28 may include the method of Example 26 or some other examples herein, where for cross-carrier scheduling with different SCSs, the one or more valid PDSCHs are determined based on a delay greater than or equal to a minimum scheduling delay between an ending symbol of a PDCCH including a DCI and a starting symbol of a first valid PDSCH among the multiple PDSCHs scheduled by the PDCCH.

[0140] Example 29 may include the method of Example 26 or some other examples herein, wherein the indicated TCI state for the multi-PDSCH transmission is based on one or more activated TCI states in the first slot having a valid PDSCH.

[0141] Example 30 may include the method of example 29 or any other example herein, wherein the one or more activated TCI states are the same across slots having a valid PDSCH.

[0142] Example Z01 may include an apparatus having means for performing one or more elements of the method described in or related to any of Examples 1 to 30, or any other method or process described herein.

[0143] Example Z02 may include one or more non-transitory computer-readable media comprising instructions that, upon execution by one or more processors of the electronic device, cause the electronic device to perform a method described in or related to any of Examples 1 to 30, or any other method or process described herein.

[0144] Example Z03 may include an apparatus having logic, modules, or circuits for performing one or more elements of a method described or related to any of Examples 1 to 30, or any other method or process described herein.

[0145] Example Z04 may include any method, technique, or process described or related to any of Examples 1 to 30 or any part or portion thereof.

[0146] Example Z05 may include an apparatus having one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to 30 or any portion or portion thereof.

[0147] Example Z06 may include signals described or related to any of Examples 1 to 30 or any part or portion thereof.

[0148] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1 to 30 or any part or portion thereof or otherwise described in this disclosure.

[0149] Example Z08 may include a signal encoded with data described or related to any of Examples 1 to 30 or any portion or portion thereof or otherwise described in this disclosure.

[0150] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1 to 30 or any portion or portion thereof or otherwise described in this disclosure.

[0151] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to 30 or a portion thereof.

[0152] Example Z11 may include a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples 1 to 30 or a portion thereof.

[0153] Example Z12 may include signals in a wireless network as shown and described herein.

[0154] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0155] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0156] Example Z15 may include a device for providing wireless communication as shown and described herein.

[0157] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0158] Abbreviation Unless used differently herein, the terms, definitions and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein: [Table 2] TIFF2025502906000006.tif220169TIFF2025502906000007.tif221169TIFF202 5502906000008.tif222169TIFF2025502906000009.tif222169TIFF2025502906 000010.tif220169TIFF2025502906000011.tif222169TIFF2025502906000012. tif219169TIFF2025502906000013.tif222169TIFF2025502906000014.tif90169

[0159] term For purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0160] As used herein, the term "circuitry" refers to, is a part of, or includes hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide a described functionality. In some embodiments, a circuitry may execute one or more software or firmware programs to provide at least a portion of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0161] The term "processor circuitry" as used herein refers to, is a part of, or includes a circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry".

[0162] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0163] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communications network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless equipment, reconfigurable wireless equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0164] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or may be referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0165] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. In addition, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0166] As used herein, the terms "appliance," "computer appliance," and the like refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing specific computing resources.

[0167] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and application, workload unit, etc. "Hardware resources" may refer to computational, storage, and / or network resources provided by physical hardware elements. "Virtualization resources" may refer to computational, storage, and / or n-resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity for providing services and may include computational and / or network resources. A system resource may be thought of as a set of coherent functions, network data objects, or services accessible through a clearly identifiable server, where such system resources reside on a single host or multiple hosts.

[0168] As used herein, the term "channel" refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terminology indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0169] As used herein, terms like "instantiation" and "instance" refer to the creation of an instance, and an "instance" refers to a specific occurrence of an object, such as might occur during the execution of program code.

[0170] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by any communication means, including via a wire or other interconnection, via a wireless communication channel or link, and / or the like.

[0171] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents.

[0172] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0173] The term "SSB" refers to SS / PBCH block.

[0174] The term "primary cell" refers to an MCG cell operating on a primary frequency on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0175] The "primary SCG cell" refers to an SCG cell to which the UE performs random access when performing a Reconfiguration with Sync procedure for DC operation.

[0176] The term "Secondary Cell" refers to a cell that provides additional radio resources on top of a special cell for UEs configured with CA.

[0177] The term "secondary cell group" refers to a subset of serving cells that includes a PSCell and zero or more secondary cells for a UE configured with a DC.

[0178] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell that constitutes the primary cell.

[0179] The term "serving cell" or "serving cells" refers to a set of cells including the special cell for a UE in RRC_CONNECTED configured with CA / and all secondary cells.

[0180] "Special Cell" refers to a PCell for an MCG or a PSCell for an SCG for DC operation; otherwise, "Special Cell" refers to a Pcell.

Claims

1. When executed by one or more processors in a user equipment (UE), decoding downlink control information (DCI) scheduling a plurality of physical downlink shared channels (PDSCHs); determining a transmission configuration indicator (TCI) state for the PDSCHs based on a time domain resource allocation (TDRA) field in the DCI and one or more activated TCI states in an earliest slot in which one of the PDSCHs is scheduled; receiving the PDSCHs based on the determined TCI status; and and one or more non-transitory computer readable media (NTCRMs) storing instructions for configuring the UE to perform the steps of:

2. the one or more activated TCI states are the same across slots of the PDSCHs. One or more NTCRMs according to claim 1.

3. The instructions, when executed, further configure the UE to receive a configuration of a PDSCH time domain allocation list for multi-PDSCH scheduling, and the TCI state is determined based on the PDSCH time domain allocation list.

2. One or more NTCRMs according to claim 1.

4. The TCI state is determined based on the first SLIV of a row of a TDRA table indicated by the TDRA field. One or more NTCRMs according to claim 1.

5. the earliest slot in which one of the PDSCHs is scheduled overlaps with an uplink (UL) symbol indicated by a time domain duplex (TDD) uplink (UL)-downlink (DL) configuration. One or more NTCRMs according to claim 1.

6. The TDD UD-DL configuration is a common TDD UD-DL configuration or a dedicated TDD UD-DL configuration; One or more NTCRMs according to claim 5.

7. The instructions, when executed, further configure the UE to identify, from among the plurality of PDSCHs, one or more valid PDSCHs and one or more invalid PDSCHs based on the DCI. One or more NTCRMs according to any one of claims 1 to 6.

8. the PDSCHs are scheduled across different carriers having different subcarrier spacings, and the one or more valid PDSCHs are determined based on a delay between an end symbol of a physical downlink control channel (PDCCH) that includes the DCI and a start symbol of a first valid PDSCH of the plurality of PDSCHs that is greater than or equal to a minimum scheduling delay.

8. One or more NTCRMs according to claim 7.

9. When executed by one or more processors in a user equipment (UE), decoding downlink control information (DCI) scheduling a plurality of physical uplink shared channels (PUSCHs); identifying, based on the DCI, one or more valid PUSCHs from among the plurality of PUSCHs scheduled by the DCI, the one or more valid PUSCHs being identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) including the DCI and a start symbol of a valid PUSCH from the plurality of PUSCHs, the delay being based on a PUSCH preparation time and a timing advance; encoding the one or more valid PUSCHs for transmission; and and one or more non-transitory computer readable media (NTCRMs) storing instructions for configuring the UE to perform the steps of:

10. The validity of the one or more valid PUSCHs is checked after an initial determination that the one or more valid PUSCHs do not overlap with downlink symbols indicated by a Time Domain Duplexing (TDD) uplink-downlink (UL-DL) configuration or symbols configured for transmission of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH).

10. One or more NTCRMs according to claim 9.

11. one or more of the valid PUSCHs overlaps with downlink symbols of a time domain duplex (TDD) uplink-downlink (UL-DL) configuration; 10. One or more NTCRMs according to claim 9.

12. The one or more valid PUSCHs include the effect of the timing advance, and the first uplink symbol in the resource allocation for the PUSCH is symbol L ２ is identified based on satisfying the condition that it is not earlier than ２ is a time T after the end of reception of the last symbol of the PDCCH carrying the DCI. ｐｒｏｃ，２ = max ((N ２ +d ２，１ +d ２ )(2048+144)・κ2 －μ ・T ｃ +T ｅｘｔ +T ｓｗｉｔｃｈ , d ２，２ ) is defined as the next uplink symbol having a cyclic prefix starting at 10. One or more NTCRMs according to claim 9.

13. The resource allocation includes a demodulation reference signal (DM-RS) and a first slot offset value K ２ , the second slot offset value K ｏｆｆｓｅｔ and the resource allocation indicated by the time domain resource allocation in the DCI based on a start S and a length L of the resource allocation.

13. One or more NTCRMs according to claim 12.

14. The PDCCH is received on a PDCCH candidate associated with a search space set configured using search space linking, and the last symbol of the PDCCH corresponds to a first PDCCH candidate that is latest in time among the PDCCH candidates.

14. One or more NTCRMs according to any one of claims 9 to 13.

15. When executed by one or more processors in a user equipment (UE), decoding downlink control information (DCI) scheduling a plurality of physical downlink shared channels (PDSCHs) on a first carrier having a first subcarrier spacing (SCS), the PDSCH including a first PDSCH on a second carrier having a second SCS; identifying, based on the DCI, one or more valid PDSCHs from among the plurality of PDSCHs scheduled by the DCI, the one or more valid PDSCHs being identified based on a delay between a last symbol of a physical downlink control channel (PDCCH) that includes the DCI and a start symbol of a valid PDSCH that is greater than or equal to a minimum scheduling delay; decoding the one or more valid PDSCHs; and and one or more non-transitory computer readable media (NTCRMs) storing instructions for configuring the UE to perform the steps of:

16. The validity of the one or more valid PDSCHs is checked after an initial determination that the one or more valid PDSCHs do not overlap with uplink symbols indicated by a time domain duplex (TDD) uplink-downlink (UL-DL) configuration.

16. One or more NTCRMs according to claim 15.

17. If the first SCS is smaller than the second SCS, the minimum scheduling delay is at least N symbols after the last symbol of the PDCCH, including a demodulation reference signal (DM-RS). ｐｄｓｃｈ corresponds to a first symbol of a resource allocation for the PDSCH that starts no earlier than the first symbol of a slot starting with the N PDCCH symbols, ｐｄｓｃｈ is based on the first subcarrier spacing, 16. One or more NTCRMs according to claim 15.

18. If the first SCS is greater than the second SCS, the minimum scheduling delay is at least N symbols after the last symbol of the PDCCH, including a demodulation reference signal (DM-RS). ｐｄｓｃｈ corresponding to a first symbol of a resource allocation for the PDSCH that starts no earlier than N PDCCH symbols, ｐｄｓｃｈ is based on the first subcarrier spacing, 16. One or more NTCRMs according to claim 15.

19. The resource allocation for the PDSCH is ０ and a Start and Length Indicator Value (SLIV) indicated by the DCI.

18. One or more NTCRMs according to claim 17.

20. the delay is determined without taking into account a reception timing difference between a first cell associated with the first carrier and a second cell associated with the second carrier.

16. One or more NTCRMs according to claim 15.

21. The PDCCH is received on a PDCCH candidate associated with a search space set configured using search space linking, and the last symbol of the PDCCH corresponds to a first PDCCH candidate that is latest in time among the PDCCH candidates.

21. One or more NTCRMs according to any one of claims 15 to 20.

Images