Systems and methods for conflict handling and physical downlink shared channel release

Abstract

A method of releasing semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs), the method comprising: receiving, by a PDSCH manager of a user equipment, a SPS release physical downlink control channel (PDCCH) in a scheduled cell, the SPS release PDCCH identifying N SPS PDSCH configuration indexes to release; identifying a slot of a scheduled cell, wherein the slot of the scheduled cell overlaps with an end of the ending symbol of the SPS release PDCCH; identifying, from the N SPS PDSCH configuration indexes scheduled in the slot, M SPS PDSCH configuration indexes that include all configuration indexes; and releasing L SPS PDSCH configuration indexes of the M SPS PDSCH configuration indexes based on a determination that the ending symbol of the SPS release PDCCH is before a corresponding ending symbol associated with each of the L SPS PDSCH configuration indexes of the slot.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 057087, filed July 27, 2020, with the United States Patent and Trademark Office, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to systems and methods for processing semi-persistent or dynamically scheduled channels in cellular communication protocols. Background Technology

[0004] In cellular communication protocols, such as the 5G-NR specification of the 3GPP Release 15, downlink traffic from a base station to a user equipment (e.g., a smartphone) is wirelessly transmitted over a signal that includes a Physical Downlink Shared Channel (PDSCH), which can be dynamically scheduled (dynamically licensed or DG) or semi-persistently scheduled (SPS). Summary of the Invention

[0005] Various aspects of this disclosure relate to a cellular communication protocol, including systems and methods implemented in a user equipment (UE) for processing semi-persistent scheduling (SPS) or dynamic scheduling (or dynamic granting or DG) channels issued by a base station (g Node B or gNB).

[0006] According to one embodiment of this disclosure, a method is provided for jointly releasing multiple semi-persistently scheduled (SPS) physical downlink shared channels (PDSCHs), the method comprising: receiving SPS release physical downlink control channels (PDCCHs) in a scheduled cell through a PDSCH manager of a user equipment including a processor and a memory, wherein the SPS release PDCCHs identify N SPS PDSCH configuration indices i1,...,i N The PDSCH manager identifies the time slot of the scheduled cell, wherein the time slot of the scheduled cell overlaps with the end of the SPS release PDCCH end symbol; the PDSCH manager identifies M SPS PDSCH configuration indices j1,...,j from N SPSPDSCH configuration indices configured in the time slot. Mwhere M < N, the M SPS PDSCH configuration indexes are associated with corresponding ending symbols; comparing, by the PDSCH manager, a timing of an end of the ending symbol of the SPS release PDCCH to a timing of a corresponding ending symbol of the M SPS PDSCH configuration indexes of the slot; releasing, by the PDSCH manager, L of the M SPS PDSCH configuration indexes based on determining that the end of the ending symbol of the SPS release PDCCH is before the corresponding ending symbol associated with each of the L SPS PDSCH configuration indexes of the slot.

[0007] An acknowledgement / negative acknowledgement (ACK / NACK) bit of the SPS release PDCCH and ACK / NACK of L of a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indexes can be mapped to a same physical uplink control channel (PUCCH).

[0008] The scheduling cell can have a first subcarrier spacing and the scheduled cell can have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell can be lower than the second subcarrier spacing of the scheduled cell. The first subcarrier spacing of the scheduling cell can be higher than the second subcarrier spacing of the scheduled cell.

[0009] According to one embodiment of the disclosure, a method for identifying a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs) to be released jointly is provided, the method comprising: identifying, by a PDSCH manager of a base station comprising a processor and a memory, a slot of a scheduled cell that will overlap with an end of an ending symbol of an SPS release physical downlink control channel (PDCCH) that identifies N SPS PDSCH configuration indexes to be released jointly; identifying, by the PDSCH manager, M SPS PDSCH configuration indexes j1,.., jMfrom the N SPS PDSCH configuration indexes configured in the slot that include all configuration indexes; and releasing, by the PDSCH manager, L of the M SPS PDSCH configuration indexes based on determining that the end of the ending symbol of the SPS release PDCCH is before a corresponding ending symbol associated with each of the L SPS PDSCH configuration indexes of the slot. Mwhere M < N, the M SPS PDSCH configuration indexes are associated with corresponding ending symbols; comparing, by the PDSCH manager, a timing of an end symbol of a SPS release PDCCH with the corresponding ending symbols of the M SPS PDSCH configuration indexes of the slot; identifying, by the PDSCH manager, L release SPS PDSCH configuration indexes from the M SPS PDSCH configuration indexes based on determining that an end of the SPS release PDCCH is before the corresponding ending symbol associated with each of the L release SPS PDSCH configuration indexes of the slot.

[0010] An acknowledgement / negative acknowledgement (ACK / NACK) bit of a SPS release PDCCH and ACK / NACK of L SPS PDSCH occasions from a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indexes can be mapped to a same physical uplink control channel (PUCCH).

[0011] The scheduling cell can have a first subcarrier spacing and the scheduled cell can have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell can be lower than the second subcarrier spacing of the scheduled cell. The first subcarrier spacing of the scheduling cell can be higher than the second subcarrier spacing of the scheduled cell.

[0012] According to one embodiment of the disclosure, a method for releasing a semi-persistently scheduled (SPS) physical downlink shared channel (PDSCH) with an aggregation factor is provided, the method comprising: receiving, by a PDSCH manager of a user equipment comprising a processor and a memory, a SPS release physical downlink control channel (PDCCH) in a scheduling cell, the SPS release PDCCH identifying a SPS PDSCH configuration index, the SPS PDSCH configuration index being associated with a SPS PDSCH configured with an aggregation factor in a scheduled cell; identifying, by the PDSCH manager, a timing of an ending symbol of a last repetition segment of the SPS PDSCH configured with the aggregation factor; comparing, by the PDSCH manager, a timing of an ending symbol of the SPS release PDCCH with a timing of a last symbol of the last repetition segment of the SPS PDSCH configured with the aggregation factor; releasing, by the PDSCH manager, the SPS PDSCH configuration index based on determining that an end of the SPS release PDCCH is before the last symbol of the last repetition segment of the SPS PDSCH configured with the aggregation factor.

[0013] An acknowledgement / negative acknowledgement bit (ACK / NACK) of the SPS release PDCCH and an ACK / NACK of the SPS PDSCH configured with an aggregation factor can be mapped to a same physical uplink control channel (PUCCH).

[0014] The scheduling cell can have a first subcarrier spacing and the scheduled cell can have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell can be lower than the second subcarrier spacing of the scheduled cell.

[0015] The SPS release PDCCH can identify a plurality of SPS PDSCH configuration indexes to be released.

[0016] According to one embodiment of the disclosure, a method for identifying a released semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) with an aggregation factor (AF) is provided, the method comprising: identifying, by a PDSCH manager of a base station comprising a processor and a memory, a timing of an ending symbol of a last repetition of the SPS PDSCH with the AF in a scheduled cell; identifying, by the PDSCH manager, a timing of an ending symbol of a SPS release physical downlink control channel (PDCCH) in a scheduling cell; comparing, by the PDSCH manager, the timing of the end of the ending symbol of the SPS release PDCCH with the timing of the end of the ending symbol of the last repetition of the SPS PDSCH with the AF; and identifying, by the PDSCH manager, that the SPS PDSCH with the AF has been released when the end of the ending symbol of the SPS release PDCCH is before the end of the ending symbol of the last repetition of the SPS PDSCH with the AF.

[0017] An acknowledgement / negative acknowledgement bit (ACK / NACK) of the SPS release PDCCH and an ACK / NACK of the SPS PDSCH configured with an aggregation factor can be mapped to a same physical uplink control channel (PUCCH).

[0018] The scheduling cell can have a first subcarrier spacing and the scheduled cell can have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell can be lower than the second subcarrier spacing of the scheduled cell.

[0019] The SPS release PDCCH can identify a plurality of SPS PDSCH configuration indexes to be released. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, together with the specification, illustrate exemplary embodiments of the present application and, along with the description, serve to explain the principles of the present application.

[0021] Figure 1 is a schematic block diagram of a wireless communication system in which a base station (or g Node B or gNB) communicates with a mobile station (or user equipment or UE).

[0022] Figure 2 is a block diagram illustrating a physical downlink shared channel (PDSCH) manager according to one embodiment of the present disclosure.

[0023] Figure 3 is a schematic diagram illustrating an arrangement of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) occasions on multiple slots of a serving cell.

[0024] Figure 4 is a schematic diagram illustrating a set of overlapping SPS PDSCH occasions and a corresponding Type-1 hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook sub-group of PDSCH occasions.

[0025] Figure 5 is a schematic diagram illustrating a slot with two overlapping SPS PDSCH occasions and a release downlink control information (DCI) for one of the SPS PDSCH configurations.

[0026] Figure 6 is a schematic diagram illustrating a slot with three SPS PDSCH occasions and a joint release DCI identifying all three SPS PDSCH configurations.

[0027] Figure 7 is a schematic diagram of four consecutive slots in which SPS PDSCH is scheduled with an aggregation factor of 4 and a SPS release DCI for the PDSCH is received during one of the slots.

[0028] Figure 8 illustrates an example of a release of SPS PDSCH scheduled with an aggregation factor, where the release physical downlink control channel (PDCCH) is transmitted on a different cell than the PDSCH cell in an X-CC scheduling scenario.

[0029] Figure 9 is a flow diagram illustrating a method for handling collisions between PDSCHs and handling release of SPS PDSCH according to one embodiment of the present disclosure.

[0030] Figure 10 is a flow diagram illustrating a method for handling release of SPS PDSCH and handling collisions between PDSCHs according to one embodiment of the present disclosure.

[0031] Figure 11 is a diagram illustrating a common release of multiple active SPS PDSCH configurations in a scheduled cell by a release DCI in a scheduling cell according to one embodiment of the disclosure.

[0032] Figure 12A is a flowchart of a method for releasing multiple SPS PDSCH configurations according to one embodiment of the disclosure.

[0033] Figure 12B is a flowchart of a method for determining which SPS PDSCH occasions a UE will receive when processing a SPS release PDCCH for a common release of multiple SPS PDSCH configurations according to one embodiment of the disclosure.

[0034] Figure 13 is an example of a release DCI PDCCH indicating a release of an SPS PDSCH configuration according to one embodiment of the disclosure.

[0035] Figure 14 is a diagram illustrating a common release of multiple active SPS PDSCH configurations with an aggregation factor in a scheduled cell by a release DCI in a scheduling cell according to one embodiment of the disclosure.

[0036] Figure 15A is a flowchart of a method for releasing SPS PDSCH configurations with an aggregation factor according to one embodiment of the disclosure.

[0037] Figure 15B is a flowchart of a method for determining whether a UE will receive SPS PDSCH with an aggregation factor when processing a SPS release PDCCH according to one embodiment of the disclosure.

[0038] Figure 16 is a diagram illustrating a cross-carrier SPS PDSCH release.

[0039] Figure 17 is a diagram illustrating a cross-carrier SPS PDSCH release according to one embodiment of the disclosure. DETAILED DESCRIPTION

[0040] In the following detailed description, certain exemplary embodiments of the application are shown and described, by way of illustration. As those skilled in the art would recognize, the application can be embodied in many different forms and should not be limited to the embodiments set forth herein.

[0041] In cellular communications, such as Release 15 (Rel-15) mobile network Third Generation Partnership Project (3GPP) New Radio (NR) technology (e.g., Fifth Generation New Radio or 5G-NR), downlink traffic from a base station or g Node B (gNB) to a mobile station or user equipment (e.g., a smartphone) is transmitted in a physical downlink shared channel (PDSCH), which can be dynamically scheduled (dynamic grant or DG) or semi-persistently scheduled (SPS).

[0042] A DG PDSCH is scheduled by a scheduling physical downlink control channel (PDCCH) that is used to convey downlink control information (DCI) to a user equipment (UE), such as a smartphone, tablet, Wi-Fi hotspot, etc. The DCI includes, among other information, time and frequency resources in which the UE can receive the DG PDSCH. According to the Rel-15 5G-NR standard, each DG PDSCH can only be received by first receiving the scheduling DCI.

[0043] Semi-persistent scheduling (SPS) PDSCH is also defined in the Rel-15 5G-NR standard, which enables a UE to receive a PDSCH without a corresponding scheduling DCI. In the Rel-15 standard, SPS PDSCH is supported to provide continuous downlink transmission without scheduling each individual PDSCH by a separate DCI.

[0044] For example, in SPS PDSCH, a base station (or g Node B or gNB) configures one or more SPS configurations for a UE through radio resource control (RRC) messages. An SPS configuration information element (IE) per serving cell per bandwidth part (BWP) includes periodicity, physical uplink control channel (PUCCH) resource information, and other information needed for SPS operation (see, e.g., 3GPP Technical Specification 38.331, clause 6). For example, the SPS configuration information element can specify a periodicity of SPS PDSCH occasions, e.g., a frequency of receiving SPS PDSCH. For example, in some cases, the minimum periodicity is 10 ms (10 slots when the subcarrier spacing is 15 KHz).

[0045] Rel-15 5G-NR supports up to one active SPS PDSCH configuration per serving cell per bandwidth part (BWP). In addition, up to one serving cell in each cell group can be configured with an SPS PDSCH configuration. To provide greater flexibility, including lower latency, to uRLLC UEs, aspects of the present disclosure are directed to supporting multiple active SPS configurations per BWP per serving cell. In addition, aspects of the present disclosure allow for configurations that enable multiple cells within each cell group to have SPS configurations.

[0046] Figure 1 is a schematic block diagram of a wireless communication system in which a base station (or g Node B or gNB) communicates with a mobile station (or user equipment or UE). As shown in Figure 1 , the mobile station 10 can include an antenna 11 configured to receive downlink electromagnetic signals 30 (e.g., transmitted by the base station 20). The downlink electromagnetic signals 30 transmitted by the base station 20 include one or more downlink channels, such as a PDSCH. As shown in Figure 1 , the mobile station 10 can also transmit uplink electromagnetic signals 40 to be received by the base station 20, where the uplink electromagnetic signals 40 include one or more uplink channels, such as a PUCCH.

[0047] The received downlink analog signals 30 can be provided to an air interface 12, which can apply various signal processing operations to the received analog signals to generate digital signals that can be further processed by a baseband processor 14. In some cases, the air interface 12 and baseband processor 14 can be integrated as a single unit. The baseband processor 14 generates digital information 50 decoded from the received signals 30 and can provide the decoded information, as well as other information regarding the status of the communication, to an application processor (AP) 18. The digital information or data 50 can include a digital bitstream that is to be provided for consumption by an application running on the application processor 18 of the mobile station 10. The application processor 18 can execute an operating system (e.g., Android®, iOS®, Tizen TM , , etc.), and the applications (or apps) can include, for example, a voice call application, a video conference application, an email application, a Web browser, etc. The application processor 18 can also control aspects of the communication with the base station 20 via the baseband processor 14 and air interface 12.

[0048] Figure 2 ​is a block diagram illustrating a physical downlink shared channel (PDSCH) manager 200 according to one embodiment of the present disclosure. According to various embodiments of the present disclosure, the application processor 18 and / or the baseband processor 14 can implement the PDSCH manager. Referring to Figure 2 The PDSCH manager includes a sub-group determiner 210 configured to group PDSCHs of a current slot k into one or more sub-groups, a PDSCH selector 250 configured to select one or more PDSCHs to receive, and a hybrid automatic repeat request acknowledgement (HARQ-ACK) generator 270 configured to generate HARQ-ACK bits to acknowledge (or in some cases, to negatively acknowledge) reception of the selected PDSCHs (e.g., where the HARQ-ACK can be transmitted from the mobile station 10 to the base station 20 on the uplink electromagnetic signals 40 in the PUCCH).

[0049] In various embodiments of the present disclosure, the components of the PDSCH manager 200, such as the sub-group determiner 210, the PDSCH selector 250, and the HARQ-ACK generator 270, can be implemented in one or more processing circuits of a digital air interface (e.g., an air interface baseband processor (BP or BBP), a central processing unit (CPU) or application processor (AP), a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC)), where portions of the various blocks can be implemented in the same circuit (e.g., on the same die or in the same package) or in different circuits (e.g., on different dies or in different packages, connected by a communication bus).

[0050] Figure 3 is a schematic diagram illustrating an arrangement of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) occasions on multiple slots of a serving cell. The SPS configuration is activated by an activation DCI 302, which can generally be any DCI format that schedules a DG PDSCH and performs some additional validation mechanisms (see, e.g., 3GPP Technical Specification 38.213, Section 10.2). In contrast to DCI that schedules a DG PDSCH, the 3GPP 5G-NR specification indicates that the SPS activation DCI is scrambled by a configured scheduling air interface network temporary identifier (CS-RNTI), and certain specific DCI fields are dedicated to identifying SPS activation, including a new data indicator (NDI), a hybrid automatic repeat request (HARQ) process number (HPN), and a redundancy version (RV). The SPS activation DCI schedules the first SPS PDSCH occasion 310 in slot m in a similar manner as a DG PDSCH.

[0051] like Figure 3 As shown, an SPS activation DCI 302 is received in time slot m, and the SPS activation DCI indicates / schedules the first SPS PDSCH timing 310 in time slot m. The next SPS PDSCH timing is determined based on the periodicity set by the SPS activation DCI 302 and the time and frequency domain resources indicated by the SPS activation DCI 302, where in this example, the periodicity is the period of one time slot. For example, within the SPS time slot, the time and frequency resources are consistent with the time and frequency resources of the first SPS timing (e.g., having the same offset from the start of their respective time slots). As another example, if the periodicity is set to two time slots, the first SPS PDSCH timing will be scheduled in time slot m, no SPS PDSCH timing will be scheduled in time slot m+1, the second SPS PDSCH timing will be scheduled in time slot m+2, and so on. Figure 3 As shown, in time slot m+1 or time slot m+2, no corresponding SPS activation DCI is required to receive the corresponding SPS PDSCH timing 311 or SPS PDSCH timing 312.

[0052] like Figure 3 As shown, Release DCI 304 (where n>m) in time slot n releases the active SPS configuration. Although Release DCI 304 does not technically schedule resources, in some embodiments, Release DCI 304 is associated with the last PDSCH timing 318. In some embodiments, the last PDSCH timing 318 is used only for the construction of a semi-static HARQ-ACK codebook, in which case the user equipment can assume that there will be no SPS PDSCH reception during this last PDSCH timing 318. According to the Rel-15 3GPP 5G-NR standard, there can be at most one active SPS configuration per bandwidth portion (BWP) of the serving cell.

[0053] Various aspects of embodiments of this disclosure relate to providing greater flexibility to base stations (or g node B or gNB) to schedule ultra-reliable low-latency communication (uRLLC) and meet latency requirements by allowing multiple active SPS configurations per BWP for each serving cell. By allowing multiple active SPS configurations in each BWP of the serving cell, the timing of multiple active SPSs may overlap in a time slot in both time and / or frequency.

[0054] Figure 4 An example of time slot k for serving cell C is shown, in which six SPS PDSCH times 400 are scheduled to occur, some of which overlap. Figure 4The horizontal axis indicates time domain or time (t) and the vertical axis generally represents diversity in different domains, such as frequency domain and / or code division domain. The six SPS PDSCH occasions are labeled as SPS config#0 410, SPS config#1 411, SPS config#2 412, SPS config#3 413, SPS config#4 414, and SPS config#5 415, respectively. In embodiments described herein, the SPS PDSCH occasions are indexed in an order such that each SPS PDSCH occasion is scheduled by its corresponding activation DCI (e.g., the mobile station receives the activation DCI scheduling SPS config#0 410, and then receives any activation DCI scheduling SPS config#1, SPS config#1 411, SPS config#2 412, SPS config#3 413, SPS config#4 414, and SPS config#5 415, in that order). In other embodiments of the disclosure, the SPS PDSCH occasions are indexed according to different rules (e.g., a combination of priority and scheduled order).

[0055] Figure 4 The SPS PDSCH occasions 400 shown are scheduled for slot k, other slots can have different SPS PDSCH occasions scheduled depending on the periodicity of the SPS PDSCH. For example, one SPS configuration can schedule SPS PDSCH with a periodicity of 2, while another SPS configuration can schedule SPS PDSCH with a periodicity of 3. As such, these two configurations cause the corresponding SPS PDSCH occasions to occur in the same slot once every six slots (6 is the least common multiple of 2 and 3). As such, slot k-1 and slot k+1 can have SPS occasions different from the example slot k shown. Figure 4

[0056] To handle these multiple active SPS configurations, various aspects of embodiments of the disclosure relate to systems and methods for determining which active SPS configuration to handle in the event that active SPS occasions overlap in time and / or frequency in a slot, as shown in Figure 4

[0057] Handling of physical downlink shared channel with semi-persistent scheduling in release 16

[0058] Figure 4 ​​is a diagram showing a set of overlapping SPS occasions and corresponding Type-1 hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook subgroups. Figure 4 Each SPS PDSCH occasion 400 in the drawn boxes is a PDSCH candidate such that the base station 20 can transmit a PDSCH. In some cases, these candidates can be empty, e.g., the base station 20 needs to transmit a PDSCH for the UE in every scheduled SPS occasion. Each subgroup of overlapping PDSCHs can be defined according to a Type-1 codebook subgroup. In particular, the PDSCH occasion with the earliest last symbol is selected, and every other PDSCH overlapping this PDSCH is grouped into the first subgroup in the slot. Except for the PDSCHs in the first subgroup, the PDSCH with the earliest last symbol is selected, and every other PDSCH overlapping this PDSCH is grouped into the second subgroup in the slot, and so on (see, e.g., 3GPP Technical Specification 38.213, clause 9.1.2).

[0059] In Figure 4 In the particular example shown, SPS config#0 410 has the earliest last symbol (e.g., the right edge of box 410 is earliest in time among all SPS PDSCH occasions 400). Every other PDSCH occasion overlapping SPS config#0 410 in time is considered to belong to the same subgroup as SPS config#0 410. Referring to Figure 4 Two PDSCH occasions overlap if a vertical line can be drawn through both boxes representing the PDSCH occasions. In Figure 4 In the example shown, SPS config#1 411, SPS config#2 412, and SPS config#3 413 all overlap SPS config#0 in time, and are therefore part of a subgroup. Among the remaining PDSCH occasions, SPS config#4 414 has the earliest last symbol (e.g., the right edge of SPS config#4 414 is earlier in time than the right edge of SPS config#5 415). SPS config#5 415 overlaps SPS config#4 414 in time, and therefore belongs to the same subgroup as SPS config#4 414, and there are no remaining subgroups.

[0060] Thus, based on the 5G-NR Release 15 (Rel-15) standard, in Type 1 HARQ-ACK codebook, SPS occasions with configuration 0 to 3 (SPS config#0 410, SPS config#1 411, SPS config#2 412, and SPS config#3 413) are sub-grouped in sub-group #0 430, while SPS occasions with configuration 4 and 5 (SPS config#4 414 and SPS config#5 415) are sub-grouped in sub-group #1 431, forming two sub-groups.

[0061] Problem A: PDSCH collision and release handling

[0062] Generally, in 5G-NR Release 16 (Rel-16) 3GPP specifications, in the case of multiple active SPS PDSCH configurations on a serving cell's bandwidth part (BWP), a user equipment (UE) only receives certain SPS PDSCHs that do not overlap, where the SPS PDSCHs to be received are determined by their SPS configuration index. See Figure 4 In Rel-16, the UE handles collision among one or more PDSCHs without a corresponding physical downlink control channel (PDCCH) transmission as follows:

[0063] - Step 0: Set j = 0, where j is the number of PDSCHs selected for decoding. Q is the set of activated PDSCHs within a slot that do not have a corresponding PDCCH transmission

[0064] - Step 1: The UE receives one PDSCH configured with the lowest configuration index within Q, set j = j + 1. The received PDSCH is designated as a survivor PDSCH.

[0065] - Step 2: Exclude or remove from Q the survivor PDSCH in Step 1 and any other PDSCHs that overlap (even partially) with the survivor PDSCH in Step 1.

[0066] - Step 3: Repeat Steps 1 and 2 until Q is empty or j is equal to the number of unicast PDSCHs in a slot that the UE supports.

[0067] In this example, as shown in FIG. 2A, and assuming the UE supports processing up to two unicast PDSCHs in a slot, in Step 0, the PDSCH manager 200 initially identifies PDSCHs 210, 220, 230, and 240 as candidates for decoding. Figure 4 Figure 5 ​All six SPS configurations shown in the middle are added to the set Q, and j is set to 0. In step 1, the PDSCH manager 200 receives one PDSCH with the lowest configured index, SPSconfig#0 410, designates it as the survivor PDSCH, and j is incremented to 1. In step 2, the PDSCH manager 200 removes all PDSCHs that overlap with the survivor PDSCH SPSconfig#0 410. Since SPSconfig#1 411, SPSconfig#2 412, and SPSconfig#3 413 all overlap with SPSconfig#0 410, these three SPS configurations are removed from Q, leaving only SPSconfig#4 414 and SPSconfig#5 415 in Q. In step 3, since Q is not yet empty and since j is still less than the maximum number of PDSCHs supported (assumed to be 2), the process continues with step 1. In step 1, the PDSCH manager 200 receives the PDSCH with the lowest configuration in Q. In this case, this PDSCH will be SPSconfig#4 414, which is designated as the survivor PDSCH, and j is incremented to 2. In step 2, the PDSCH manager 200 removes SPSconfig#5 415 from Q since it overlaps with the survivor PDSCH SPSconfig#4 414. In step 3, the PDSCH manager 200 determines that the collision handling process is complete since Q is now empty and since j is equal to the maximum number of PDSCHs supported by the UE in a slot (either condition is sufficient to end the collision handling process in this example).

[0068] As described above, a slot SPS release DCI can be transmitted by a PDCCH to release an active SPS configuration, where after the UE has received the corresponding release PDCCH for this active SPS configuration, the UE is expected to no longer receive the previously scheduled SPS PDSCH. In Rel-16, this behavior involves supporting the following: if a slot SPS release PDCCH is received before the end of the SPS PDSCH reception for the same SPS configuration corresponding to the SPS release PDCCH, a 1-bit HARQ-ACK is generated for the SPS release, and if the HARQ-ACKs for the SPS release and the SPS reception would map to the same physical uplink control channel (PUCCH), the UE is expected to not receive the SPS PDSCH. Additionally, in Rel-16, if the HARQ-ACKs for the SPS release and the SPS reception would map to the same PUCCH, it is not supported to receive the SPS release PDCCH in a slot after the end of the SPS PDSCH reception in a slot for the same SPS configuration corresponding to the SPS release PDCCH.

[0069] Further, in Rel-16, if a UE is configured to receive SPS PDSCH in a slot for an SPS configuration, and if the UE receives a PDCCH indicating a release of SPS PDSCH corresponding to the SPS configuration in the slot, and if the last symbol or end symbol of the PDCCH reception is not after the end of the last symbol of the SPS PDSCH reception, the UE is not expected to receive the SPS PDSCH, not generate HARQ-ACK information for the SPS PDSCH reception, and generate HARQ-ACK information bits for the SPS PDSCH release (see, e.g., 3GPP Technical Specification 38.213, clause 9.1).

[0070] However, the Rel-16 3GPP 5G-NR standard does not specify the order in which the above specifications apply, which can lead to different results depending on how these specifications are interpreted by implementing cellular devices, such as UEs and gNBs. Different interpretations of the protocol by UEs and gNBs communicating with each other can lead to data loss and / or inefficient communication, as the UEs and gNBs differ in their decisions of which active SPS configurations to receive and which active SPS configurations not to receive.

[0071] Figure 5 is a schematic diagram showing a slot with two overlapping SPS PDSCH occasions and a release DCI for one of the SPS PDSCH configurations. In Figure 5 In the particular example slot shown, SPS config#0 510 overlaps with SPS config#1 511. Additionally, release DCI#0 520 overlaps with SPS config#0 510 and SPS config#1 511. The first symbol of SPS config#1 511 is earlier than the start of both SPS config#0 510 and release DCI#0 520, while the last symbol of SPS config#1 511 is earlier than the end of SPS config#0 510 and release DCI#0 520. The first symbol of release DCI#0 520 and SPS config#0 510 is aligned (e.g., simultaneous), and the last symbol of release DCI#0 520 is before the last symbol of SPS config#0 510.

[0072] If the UE first resolves the collision between the SPS PDSCHs, SPS config#0 510 is identified as the SPS PDSCH configuration with the lowest index and the other overlapping PDSCH, and SPS config#1 511 is deleted. Next, the rule regarding the release DCI is applied, because the last symbol of release DCI#0 520 is before the end of the corresponding SPS PDSCH occasion (SPS config#0 510), and thus SPS config#0 510 is released, and thus the corresponding occasion is not received. In addition, an acknowledgement / negative acknowledgement (ACK / NACK) can be transmitted. For a “Type-1” (Type-1) HARQ-ACK codebook (CB), assuming that two containers are available, (NACK#1, ACK#0) is transmitted (according to Technical Specification 38.213, the TDRAs for SPS#1 and SPS#0 are divided into two different subgroups for Type-1 HARQ-ACK CB). For a “Type-2” (Type-2) HARQ-ACK CB, ACK#0 is transmitted.

[0073] On the other hand, if the UE first addresses the release DCI, SPS config#0 510 is released and deleted. After the PDSCH occasion corresponding to SPS config#0 510 is deleted, the UE applies the collision resolution rule. In this particular example, only SPS config#1 511 remains and does not overlap with any other PDSCH occasion in this slot, and thus SPS config#1 511 is received. In this case, for a Type-1 HARQ-ACK CB, assuming that two containers are available, (ACK#1, ACK#0) is transmitted (according to TS 38.213, the TDRAs for SPS#1 and SPS#0 belong to two different subgroups of Type-1 CB). For a Type-2 HARQ-ACK CB, (ACK#0, ACK#1) is transmitted by appending the ACK / NACK for SPS PDSCH config#1 511 to the end of the dynamic part of the Type-2 CB, which in this context is assumed to include only the release DCI for SPS config#0 510 (release DCI#0 520).

[0074] Accordingly, Figure 6 An example case is shown in which the order in which the UE applies the rules results in different behavior, i.e., reception or non-reception of SPS config#1 511.

[0075] Problem B: Joint SPS PDSCH release handling

[0076] The 3GPP 5G-NR Release 16 specifies that a release DCI can be used to jointly release multiple SPS PDSCH configurations, as identified based on their indices. Figure 6 is a schematic diagram showing a slot with three SPS PDSCH occasions and a joint release DCI identifying all three SPS PDSCH configurations. In Figure 7 In the arrangement shown, SPS config#0 610 has the earliest first symbol, while its last symbol is before the start of SPS config#1 611. SPS config#2 612 starts during SPS config#0 610 and ends during SPS config#1 611, thus overlapping both. Release DCI #0#1#2 620 identifies all three shown SPS PDSCH configurations SPS config#0 610, SPS config#1 611, and SPS config#2 612. The first symbol of release DCI #0#1#2 620 occurs after the first symbol of SPS config#2 612 and before the end of SPS config#1 611. The UE can send a response (ACK / NACK message) about the four communications in PUCCH 630 in a subsequent slot (slot n).

[0077] According to one interpretation of the standard, release DCI #0#1#2 620 is not supported (e.g., not allowed according to the standard) because the end of SPS config#0 610 is before the end of release DCI #0#1#2 620. On the other hand, release DCI #0#1#2 620 is supported under another interpretation because the end of SPS config#1 611 is after the end of the release PDCCH. This situation can also occur in cross-carrier scheduling with different numerologies when the subcarrier spacing (SCS) of the release DCI is smaller than the subcarrier spacing (SCS) of the SPS PDSCH slot. In this case, the release PDCCH typically overlaps with multiple SPS PDSCH slots.

[0078] Problem C: SPS PDSCH release with aggregation factor

[0079] In some cases, the SPS release DCI PDCCH overlaps with a single occasion of SPS PDSCH with aggregation factor (e.g., where SPS PDSCH is scheduled for multiple consecutive slots). In this case, the end of some SPS PDSCH occasions will be before the end of the SPS release DCI PDCCH, while the end of some other SPS PDSCH can be after the end of the release PDCCH. However, Rel-16 does not allow this arrangement because if the ACK / NACK for PDSCH and release PDCCH are mapped to the same PUCCH, one ACK / NACK will be generated for the entire SPS PDSCH reception. If this scenario is not supported, it will greatly reduce the network flexibility in terms of SPS PDSCH with aggregation factor. A similar case is when the cross-carrier (X-CC) SPS release PDCCH releases SPS PDSCH configuration on a cell with larger numerology.

[0080] Figure 7 is an illustration of four consecutive slots where SPS PDSCH is scheduled and the SPS release DCI for PDSCH is received in slot 1. In particular, SPS PDSCH is scheduled with aggregation factor 4, so SPS PDSCH occasions 710, 711, 712, and 713 occur in consecutive slots (labeled nD=0, nD=l, nD=2, and nD=3). Release DCI PDCCH 720 is sent during slot nD=l to release SPS PDSCH occasions. This arrangement is not allowed by the standard because the end of the release DCI PDCCH 720 is after the end of SPS PDSCH occasion 711 in the same slot. Figure 8

[0081] Figure 8 is an illustration of an example of release of SPS PDSCH scheduled with aggregation factor, where in X-CC scheduling scenario, release PDCCH is sent on a different cell than the PDSCH cell. In this case, if the numerology of the scheduling cell is less than the numerology of the scheduled cell, and the SPS PDSCH periodicity is small, e.g., periodicity is one slot, it is possible that the end of one SPS PDSCH is before the end of the release PDCCH, while the end of the next SPS PDSCH is after the end of the PDCCH. In this case, the ACK / NACK for PDSCH and release PDCCH are mapped to the same PUCCH, one ACK / NACK will be generated for the entire SPS PDSCH reception. Figure 9 ​In the particular example shown, scheduled cell 801 has a subcarrier spacing (SCS) of 120 KHz, which has corresponding SPS PDSCH occasions 810, 811, 812, 813, 814, 815, 816, and 817, and scheduling cell 802 has a SCS of 15 KHz, which has release DCI PDCCH 820. Although release DCI PDCCH 820 starts at the beginning of scheduling cell 802, first SPS PDSCH occasion 810 still ends before the end of release DCI PDCCH 820, in part due to the difference in numerology between scheduling cell 802 and scheduled cell 801.

[0082] Assuming all ACK / NACK for all SPS PDSCH and all ACK / NACK for release PDCCH are mapped to the same PUCCH, if “slot” (same as the term used in 3GPP standards in Release 16) refers to PDCCH slots of scheduled cell 801 (rather than slots of scheduling cell 802), then according to current standards, this scenario would not be supported, and this scenario can be a typical use case for X-CC scheduling with different numerologies. Similar situation holds when the numerology of the scheduling cell is larger than the numerology of the scheduled cell.

[0083] Accordingly, aspects of the present disclosure are directed to systems and methods for at least addressing the above raised issues: Issue A: PDSCH collision and release handling; Issue B: SPS PDSCH joint release handling; and Issue C: SPS PDSCH release with aggregation factor.

[0084] Systems and methods for PDSCH collision and release handling

[0085] As noted above, Issue A relates to how the order of performing physical downlink shared channel (PDSCH) collision resolution rules and PDSCH release rules can result in different behaviors in silent cases.

[0086] Accordingly, some aspects of the present disclosure are directed to systems and methods for determining which PDSCH or PDSCHs are to be received in a slot according to an order in which a collision between PDSCHs is processed and a command to release a PDSCH is processed, rather than determining alone or simultaneously (e.g., in parallel) or without a defined order. For example, if the operations are performed concurrently with a shared data structure (e.g., a shared set Q of SPS PDSCHs in a slot), a race condition can occur in which different PDSCHs are selected to be received based on different times at which the determinations are made. As another example, different implementations can cause the determinations to be made in different orders, resulting in determinations made by different devices to be inconsistent or incompatible, thereby reducing communication efficiency between the devices.

[0087] According to one embodiment of the present disclosure, a SPS PDSCH collision is processed before a SPS PDSCH release is processed. Figure 9 FIG. 9 is a flowchart illustrating a method 900 for processing a collision between PDSCHs and processing a release of a SPS PDSCH according to one embodiment of the present disclosure. As Figure 10As shown, in operation 910, the PDSCH manager 200 selects SPS PDSCHs received in the current slot (e.g., slot k) based on resolving conflicts among the SPS PDSCHs. For example, as described above, in some embodiments, the UE receives the SPS PDSCH with the lowest configuration index within the SPS PDSCH set Q for the current slot, where the received SPS PDSCH is designated as the residual PDSCH, then all SPS PDSCHs overlapping with the residual PDSCH are removed from Q, and the process is repeated until Q is empty or the maximum number of PDSCHs to be received (set by hardware constraints of the UE) is selected. In operation 930, the PDSCH manager 200 then processes any release DCI PDCCHs for releasing any SPS PDSCHs (e.g., if the end of the last symbol of the PDCCH is not after the end of the last symbol of the SPS PDSCH reception, and the ACK / NACK of the release PDCCH and the SPS PDSCH map to the same PUCCH, then the SPS PDSCH is not expected to be received). If any selected PDSCHs in operation 910 are released, the released SPS PDSCHs are removed from the selected PDSCHs, and the PDSCH manager 200 returns to determine a set of selected and unreleased SPS PDSCHs to be received. Because the PDSCH manager 200 of the UE has information about all semi-static SPS PDSCH configurations via radio resource control (RRC), the SPS conflicts are simply resolved in operation 910, and then any DCI that will affect SPS PDSCH reception is received, as shown by the processing in operation 930.

[0088] According to one embodiment of the disclosure, SPS PDSCH releases are processed prior to processing SPS PDSCH conflicts. Figure 10 FIG. 10 is a flowchart illustrating a method 1000 for processing releases of SPS PDSCHs and processing conflicts among PDSCHs, according to one embodiment of the disclosure. As shown, in operation 1002, the PDSCH manager 200 receives a release DCI PDCCH for releasing an SPS PDSCH. In operation 1004, the PDSCH manager 200 then processes the release DCI PDCCH for releasing the SPS PDSCH (e.g., if the end of the last symbol of the PDCCH is not after the end of the last symbol of the SPS PDSCH reception, and the ACK / NACK of the release PDCCH and the SPS PDSCH map to the same PUCCH, then the SPS PDSCH is not expected to be received). If the SPS PDSCH is released, the released SPS PDSCH is removed from the set of SPS PDSCHs to be received, and the PDSCH manager 200 returns to determine a set of selected and unreleased SPS PDSCHs to be received. Because the PDSCH manager 200 of the UE has information about all semi-static SPS PDSCH configurations via radio resource control (RRC), the SPS release is simply processed in operation 1004, and then any DCI that will affect SPS PDSCH reception is received, as shown by the processing in operation 1006. Figure 9As shown, in operation 1010, the PDSCH manager 200 processes any release DCI PDCCHs for releasing any SPS PDSCHs of the current slot k (e.g., if the end of the last symbol of the PDCCH is not after the end of the last symbol of the SPS PDSCH reception, and the ACK / NACK of the release PDCCH and the SPS PDSCH map to the same PUCCH, then no SPS PDSCH is expected to be received). Any such released SPS PDSCHs are then removed from the PDSCH set Q of the current slot k, leaving a set of unreleased PDSCHs. In operation 1030, the PDSCH manager 200 applies the collision resolution procedure as described above to select one or more PDSCHs to be received from the unreleased PDSCHs based on resolution of the collisions (e.g., select the SPS PDSCH with the lowest configuration index, designate the SPS PDSCH as a surviving PDSCH, and remove all PDSCHs overlapping the surviving PDSCH, then repeat the procedure until Q is empty). Thus, in some embodiments of the disclosure, the PDSCH manager 200 determines a set of selected and unreleased SPS PDSCHs to be received by first resolving any release of SPS PDSCHs before resolving collisions among the unreleased SPS PDSCHs.

[0089] Although some aspects of embodiments of the disclosure are discussed above with reference to the PDSCH manager 200 of the UE 10, embodiments of the disclosure are not limited thereto, and also include embodiments in which the PDSCH manager of the base station or gNB 20 performs corresponding analysis of SPS collisions and SPS releases for a given UE 10 connected to the gNB 20 to determine which SPS PDSCHs are to be received by the given UE 10. This enables the gNB 20 to transmit data to the connected UE 10, for example, only in SPS PDSCHs to be received by the UE 10, when the SPS PDSCHs are selected and released in accordance with embodiments of the disclosure as shown in Figure 10 and Figure 9 Figure 10 Figure 10

[0090] Figure 5 ​​​​The ACK / NACK for the released PDCCH is in the same position as the ACK / NACK for the unreleased SPS PDSCH when the embodiment shown is receiving a PDSCH in a slot and when a Type-1 HARQ-ACK codebook is used according to Rel-16. As such, the unreleased SPS PDSCH is expected to be received, but its ACK / NACK cannot be reported in the same position as the released DCCH. As one specific example, referring back to Figure 10 When following the PDSCH selection procedure shown Figure 10 SPS config#0 is released and the UE is expected to not receive this configuration when following the PDSCH selection procedure shown. One ACK / NACK bit is generated in the ACK / NACK position for SPS PDSCH#0 for the release DCI#0. SPS PDSCH#1 is expected to be received, but since SPS config#0 510 and SPS config#1 511 are in the same Type-1 codebook sub-group (due to the overlap of SPS configurations), only one ACK / NACK bit is available in the two PDSCH codebooks.

[0091] Accordingly, some aspects of embodiments of the present disclosure are directed to systems and methods for ACK / NACK determination according to Figure 5

[0092] In some embodiments, the following is an error case: a) configured with a Type-1 HARQ-ACK codebook, and b) the ACK / NACK position for the released PDCCH is the same as the ACK / NACK position for the unreleased SPS PDSCH whose ACK / NACK is mapped to the same PUCCH as the released PDCCH.

[0093] In some embodiments, the PDSCH manager 200 generates one bit ACK / NACK as a logical AND of the ACK / NACK for the released PDCCH and the ACK / NACK for the unreleased SPS PDSCH whose ACK / NACK is mapped to the same PUCCH as the released PDCCH in the following cases: a) configured with a Type-1 HARQ-ACK CB; and b) the ACK / NACK position for the released PDCCH is the same as the ACK / NACK position for the unreleased SPS PDSCH whose ACK / NACK is mapped to the same PUCCH as the released PDCCH. Figure 5 In the specific example shown, one ACK / NACK bit is generated as a logical AND of the ACK / NACK for the SPS release DCI#0 520 and the ACK / NACK for SPS config#1 511.

[0094] ​In some embodiments, in the case where: a) configured with Type-1 HARQ-ACK CB; and b) the ACK / NACK location of the PDCCH is released and its ACK / NACK is mapped to the same PUCCH as the ACK / NACK location of the unreleased SPS PDSCH whose ACK / NACK is mapped to the same PUCCH as the released PDCCH, the PDSCH manager 200 performs SPS collision handling (as described above) to resolve the collision between the SPS PDSCH and the released SPS PDSCH as if the released SPS PDSCH was not actually released. In Figure 11 In the specific example shown, the PDSCH collision resolution is applied as if SPS config#0 510 was not actually released. In this case, SPS config#0 510 has the lowest configuration index, and thus, SPS config#1 511 is dropped and is not expected to be received. In this way, one ACK / NACK is generated for SPS release DCI#0 PDCCH 520.

[0095] System and method for SPS PDSCH common release handling

[0096] As described above, Problem B involves the common release of multiple SPS PDSCH occasions in the case where the end of one of the SPS PDSCH occasions to be released is before the end of the release PDCCH.

[0097] Accordingly, some aspects of embodiments of the present disclosure relate to systems and methods for handling the common release of multiple SPS PDSCH configurations.

[0098] Multiple embodiments will be described based on a reference slot used to determine UE behavior. The reference slot can be the slot with the smallest SCS among the PDCCH slot, the PDSCH slot, or both. The PDCCH slot is defined as the slot on the scheduled cell in which the release PDCCH is transmitted. The PDSCH slot is defined as the slot on the scheduled cell in which the end symbol of the release PDCCH ends (e.g., the slot overlapping the end of the end symbol, which can be different from the slot overlapping the beginning of the PDCCH). The slot configured based on the smallest SCS can be the PDCCH slot or the PDSCH slot, depending on which has the smallest SCS (or they can be the same size).

[0099] In some embodiments of the present disclosure, the base station or gNB ensures that the SPS release PDCCH ends before at least one of the SPS PDSCHs indicated for release.

[0100] One embodiment of this disclosure relates to a situation where the end of the released PDCCH precedes the end of at least one SPS PDSCH in the corresponding PDSCH time slot, wherein μ PDCCH ≤μ PDSCH (where μ is the subcarrier spacing of the cell, for example μ) PDCCH It is the SCS of PDCCH, and μ PDSCH (This refers to the SCS of PDSCH). In this embodiment, the SPS release PDCCH instruction in the PDCCH slot releases the index i1, i2, ..., i on the PDSCH cell. N The SPS PDSCH configuration makes: 1) M SPS PDSCH configuration indices j1, j2, ..., j M (where M≤N and ) is configured to be in the PDCCH time slot 1) Receive in one PDSCH slot; 2) Release PDCCH and the ACK / NACK (where L≤M) of L SPS PDSCHs in M ​​PSDCHs are mapped to the same PUCCH; 3) After at least one SPS PDSCH in the L SPS PDSCH reception is completed, receive and release PDCCH.

[0101] One embodiment of this disclosure involves the following situation: the release of the PDCCH ends before the end of at least one of the SPS PDSCHs in the corresponding PDSCH time slot, wherein μ PDCCH ≥μ PDSCH In this embodiment, the SPS release PDCCH instruction in the PDCCH time slot indicates the release of SPS PDSCH configuration indexes i1, i2, ..., i on the PDSCH cell. N , such that: 1) M SPS PDSCH configuration indices j1,j2,…,j M (where M≤N and 1) It is configured to receive in a PDSCH slot containing a PDCCH slot; 2) Release the PDCCH and map the ACK / NACK (where L≤M) of L SPS PDSCHs out of M PSDCHs to the same PUCCH; 3) After at least one SPS PDSCH in the L SPS PDSCH reception has ended, receive the released PDCCH.

[0102] According to some embodiments of this disclosure, the network (e.g., a base station gNB) sends an SPS release PDCCH before all SPS PDSCHs in the largest slot of the PDCCH and PDSCH slots. These embodiments are suitable for simple UE implementations for processing SPS PDSCHs and reporting ACK / NACKs.

[0103] One embodiment of this disclosure relates to the following situation: the end of the PDCCH is released before the ends of all SPS PDSCHs, and where μ PDCCH ≤μ PDSCH And the minimum SCS time slot is used as the reference time slot (in this case, due to μ) PDCCH ≤μ PDSCH (The PDCCH time slot is used as a reference time slot). In this embodiment, SPS release in the PDCCH time slot is not supported. The PDCCH instruction releases SPS on the PDSCH cell. PDSCH configuration index i1, i2, ..., i N , such that 1) M ≤ N SPS PDSCH configuration indices j1, j2, ..., j M (in ) is configured to, within the PDCCH time slot, 1) Receive in one PDSCH slot; 2) Release PDCCH and map the ACK / NACK of L ≤ M SPS PDSCHs in the M PDSCHs to the same PUCCH; and 3) After any of the L SPS PDSCHs is received, receive and release PDCCH. In other words, this embodiment supports the following case: when 1) M ≤ N SPS PDSCHs are configured with indices j1, j2, ..., j M (in ) is configured to, within the PDCCH time slot, 1) Receive in a PDSCH slot; and 2) Release PDCCH and when the ACK / NACK of L≤M SPS PDSCHs in M ​​PDSCHs are mapped to the same PUCCH, then 3) the release PDCCH must be received before all L SPS PDSCHs are received.

[0104] One embodiment of this disclosure involves the following situation: the end of the PDCCH is released before the end of all SPS PDSCHs, wherein the smallest SCS slot is used as the reference slot μ. PDCCH ≥μ PDSCH (In this case, due to μ) PDCCH >μ PDSCH (The PDSCH time slot is used as a reference time slot). In this embodiment, SPS release in the PDCCH time slot is not supported. The PDCCH instruction releases SPS on the PDSCH cell. PDSCH configuration index i1, i2, ..., i N 1) M ≤ N SPS PDSCH configuration indices j1, j2, ..., j M (in ) configured to be received in a PDSCH slot containing the PDCCH slot; and 2) ACK / NACK for the release PDCCH and L≤M SPS PDSCHs out of M PDSCHs are mapped to the same PUCCH, then 3) the release PDCCH must be received after the end of all L SPS PDSCH receptions. M (wherein ) configured to be received in a PDSCH slot containing the PDCCH slot; and 2) ACK / NACK for the release PDCCH and L≤M SPS PDSCHs out of M PDSCHs are mapped to the same PUCCH, then 3) the release PDCCH must be received after the end of all L SPS PDSCH receptions.

[0105] One embodiment of the present disclosure relates to the case where the end of the release PDCCH is before the end of all SPS PDSCHs, with the PDSCH slot being used as the reference slot. In this embodiment, SPS release PDCCH indication in the PDCCH slot releasing SPS PDSCH configuration index i1, i2, …, i N , such that: 1) M SPS PDSCH configuration index j1, j2, …, j M (wherein M≤N and ) configured to be received in a PDSCH slot containing or overlapping the end symbol of the PDCCH; 2) ACK / NACK for the release PDCCH and L SPS PDSCHs out of M PDSCHs (wherein L≤M) are mapped to the same PUCCH; 3) the release PDCCH is received after the end of any one of the L SPS PDSCH receptions. In the case where 1) and 2) are true but 3) is not true, for example, in the case where the PDCCH is received before the end of all L SPS PDSCHs, all L SPS PDSCHs in the PDSCH slot are considered to have been released, and all indicated SPS PDSCHs in the previous PDSCH slots overlap with the PDCCH slot. In other words, this embodiment supports the following case: 1) when M SPS PDSCH configuration index j1, j2, …, j M (wherein M≤N and ) configured to receive in the last PDSCH slot containing or overlapping the end symbol of the PDCCH; 2) ACK / NACK for release PDCCH and L of M SPS PDSCHs (where L < M) are mapped to the same PUCCH, then 3) the release PDCCH must be received before the end of all L SPS PDSCH receptions.

[0106] Figure 11 is a diagram illustrating a common release of multiple active SPS PDSCH configurations in a scheduled cell by a release DCI in the scheduling cell. In Figure 12AIn the illustrated example, four consecutive slots (labeled nD=0, nD=1, nD=2, and nD=3) of the scheduled cell 1140 include four different SPS PDSCH configured occasions, labeled SPS config#0, SPS config#1, SPS config#2, and SPS config#3. SPS config#0 has PDSCH occasions 1100, 1101, 1102, and 1103 in slots nD=0, nD=1, nD=2, and nD=3, respectively. SPS config#1 has SPS PDSCH occasions 1110 and 1112 in slots nD=0 and nD=2, respectively. SPS config#2 has SPS PDSCH occasions 1121 and 1123 in slots nD=1 and nD=3, respectively. SPS config#3 has SPS PDSCH occasions 1130 and 1132 in slots nD=0 and nD=2, respectively. The release DCI 1170 occurs in a scheduling cell 1180, where one slot of the scheduling cell is longer in length than the slots in the scheduled cell (in other words, the scheduling cell has a subcarrier spacing that is smaller than the subcarrier spacing of the scheduled cell, e.g., the scheduling cell can have a subcarrier spacing of 15 kHz while the scheduled cell has a subcarrier spacing of 120 kHz). The PDCCH of the release DCI 1170 starts during slot nD=1 of the scheduled cell 1140 and ends during slot nD=2 of the scheduled cell 1140 (e.g., the last symbol of the release DCI 1170 ends) (to be precise, during the SPS config#1 occasion 1112). In this example, it is assumed that the release PDCCH or release DCI 1170 indicates a release of N=3 SPS PDSCH configurations with configuration indices {0, 1, 2}. In this example, it is assumed that the ACK / NACK for the indicated SPS PDSCHs are mapped to the same PUCCH as the release PDCCH and the SPS PDSCHs are released according to the embodiments described above. To be precise, SPS PDSCH 1100, 1110, 1130 in slot nD=0, and SPS PDSCHs 1101 and 1121 in slot nD=1 are all considered not released. One ACK / NACK bit is generated for each of these SPS PDSCHs. In slot nD=2, only the SPS PDSCH with configuration index #1 (SPS PDSCH 1112) is considered released (SPS PDSCH 1132 of SPS config#3 is not released since the release DCI 1170 is assumed to identify only configuration indices 0, 1, and 2), and in slot nD=3, the SPS PDSCHs with configuration indices 0 and 2 (SPS PDSCHs 1103 and 1123) are considered released.The UE is expected not to receive SPS PDSCHs that are considered to be released, and will generate a 1-bit ACK / NACK for the set of released SPS PDSCHs and the released PDCCH.

[0107] Figure 12A This is a flowchart of a method 1200 for jointly releasing multiple SPS PDSCH configurations according to an embodiment of this disclosure. (Refer to...) Figure 12B The PDSCH manager 200 can receive information about SPS release PDCCH in the scheduling cell, where the SPS release PDCCH identifier is an N SPS PDSCH configuration index i1,...,i N In operation 1210, the PDSCH manager 200 identifies the time slot of the scheduled cell, wherein the time slot of the scheduled cell overlaps with the end of the SPS release PDCCH end symbol. In operation 1230, the PDSCH manager 200 identifies M SPS PDSCH configuration indices j1,...,j from the N SPS PDSCH configuration indices configured in the time slot, including all configuration indices. M Where M ≤ N. Each of the M SPS PDSCH configuration indices is associated with a corresponding end symbol, which has specific timing (e.g., timing of the start and end symbols) for the start and end of its corresponding PDSCH timing within a time slot. In operation 1250, the PDSCH manager 200 compares the timing of the end of the end symbol of the SPS releasing the PDCCH with the timing of the end of the end symbol of the PDSCH timing associated with the M SPS PDSCH configuration indices. In operation 1270, when the PDSCH manager 200 determines that the end of the end symbol of the SPS releasing the PDCCH precedes the end of the end symbol of each PDSCH timing associated with the M SPS PDSCH configuration indices, the PDSCH manager 200 determines that releasing all M SPS PDSCH configurations is appropriate.

[0108] Figure 12Bis a flowchart of a method 1205 for determining which SPS PDSCH occasions a UE will receive when processing a SPS release PDCCH for jointly releasing multiple SPS PDSCH configurations according to one embodiment of the present disclosure. In more detail, in some embodiments of the present disclosure, a gNB 20 generates a SPS release PDCCH for N SPS PDSCH configurations and transmits the generated SPS release PDCCH to control the behavior of a UE 10, such as by causing the UE 10 to release specific SPS PDSCHs identified in the SPS release PDCCH and controlling the UE 10’s reception of SPS PDSCHs. The gNB 20 can also transmit data to the UE 10 via one or more SPS PDSCHs, where the gNB 20 uses the determination of which SPS PDSCHs will be received to determine which SPS PDSCHs to use to transmit the data. Referring to Figure 13 In the gNB 20, an approximate timing for the SPS release PDCCH can be initially determined, such as determining which slot or slots of the scheduled cell 1140 will overlap with the end of the ending symbol of the SPS release PDCCH 1170 in operation 1215. In operation 1235, the gNB 20 identifies M SPS PDSCH configuration indices of SPS PDSCHs configured to occur in the identified slot(s). In operation 1255, the gNB 20 determines the timing of the end of the ending symbol of the M SPS PDSCH configuration indices of the slot. In operation 1275, the gNB 20 generates the SPS release PDCCH with N SPS PDSCH configuration indices, where the N SPS PDSCH configuration indices and the timing of the SPS release PDCCH are set based on ensuring that the last symbol of the SPS release PDCCH occurs before the end of the ending symbol of each of the N SPS PDSCHs corresponding to the N SPS PDSCH configuration indices listed in the SPS release PDCCH.

[0109] One embodiment of the present disclosure relates to the case where the end of the release PDCCH is before the end of all SPS PDSCHs. In this embodiment, SPS release PDCCH in PDCCH slot indicating release of SPS PDSCH configuration indices i1, i2, …, i N such that 1) the M SPS PDSCH configuration indices j1, j2, …, j M (where M < N and ) configured to receive in any PDSCH slot overlapping with the PDCCH slot; 2) ACK / NACK for the release PDCCH and L≥1 SPS PDSCHs out of M PDSCHs (where L≤M) are mapped to the same PUCCH, and 3) the release PDCCH is received after the end of any one of the L SPS PDSCH receptions. In other words, some embodiments are directed to the case where a SPS release PDCCH in a PDCCH slot indicates release of SPS PDSCH configuration indices i1, i2, …, i N , such that 1) M SPS PDSCH configuration indices j1, j2, …, j M (where M≤N and ) configured to receive in any PDSCH slot overlapping with the PDCCH slot; 2) ACK / NACK for the release PDCCH and L≥1 SPS PDSCHs out of M PDSCHs (where L≤M) are mapped to the same PUCCH, and 3) the release PDCCH is received after the end of all L SPS PDSCH receptions.

[0110] Some aspects of embodiments of the present disclosure are directed to less restrictive methods of handling the joint release of SPS PDSCH configurations, such as by determining which indicated SPS PDSCHs are actually released and which SPS PDSCHs the UE is expected to receive, despite being indicated as released.

[0111] One embodiment of the present disclosure is directed to the case where only SPS PDSCHs whose end is after the end of the release PDCCH are released, where μ PDCCH ≤μ PDSCH ; and the smallest SCS slot is considered as the reference slot (in this case, because μ PDCCH ≤μ PDSCH , the PDCCH slot is considered as the reference slot). In this embodiment, a SPS release PDCCH indicating release of SPS PDSCH configuration indices i1, i2, …, i N (N≥1) on a SPS PDSCH cell is received in a PDCCH slot, such that: 1) the SCS parameter set of the release PDCCH is smaller than or equal to the SCS parameter set of the SPS PDSCH cell; 2) M SPS PDSCH configuration indices j1, j2, …, j M (where M≤N and ) configured to receive in any PDSCH slot overlapping with the PDCCH slot; 2) ACK / NACK for the release PDCCH and L≥1 SPS PDSCHs out of M PDSCHs (where L≤M) are mapped to the same PUCCH, and 3) the release PDCCH is received after the end of any one of the L SPS PDSCH receptions. In other words, some embodiments are directed to the case where a SPS release PDCCH in a PDCCH slot indicates release of SPS PDSCH configuration indices i1, i2, …, i 3) Releasing the PDCCH and mapping the ACK / NACK of L SPS PDSCHs to the same PUCCH (where L≤M). In this case, SPS release of PDCCH only applies to R SPS PDSCHs (where R≤L) whose end symbol of the PDSCH is not before the end symbol of the released PDCCH. These SPS PDSCHs are considered released, and it is expected that the UE will not receive these SPS PDSCHs in the PDCCH slot. Generate 1 bit ACK / NACK for SPS release of PDCCH and R released SPS PDSCHs.

[0112] One embodiment of this disclosure involves the following situation: only SPSPDSCH whose ends are released after the ends of PDCCH are released, where μ PDCCH ≥μ PDSCH ; and the minimum SCS time slot is considered the reference time slot (in this case, because μ PDCCH ≥μ PDSCH (The PDSCH time slot is considered as a reference time slot). In this embodiment, it is supported to configure SPSPDSCH indexes i1, i2, ..., i on the SPS PDSCH-indicating cell. N In the PDCCH time slots where (N≥1) are released, an SPS-released PDCCH is received, such that: 1) the SCS parameter set of the released PDCCH is greater than or equal to the SCS parameter set of the SPS PDSCH cell; 2) M SPS PDSCH configuration indices j1, j2, ..., j M (where M≤N and 1) It is configured to receive in the SPSPDSCH slot containing the PDCCH slot; 2) Release the PDCCH and map the ACK / NACK of L≤M SPS PDSCHs to the same PUCCH. In this case, SPS release of PDCCH only applies to R SPS PDSCHs (where R≤L) whose end symbol of the PDSCH is not before the end symbol of the released PDCCH. These SPS PDSCHs are considered released, and it is expected that the UE will not receive these SPS PDSCHs in the PDCCH slot. Generate one ACK / NACK for the SPS release of PDCCH and R released SPS PDSCHs.

[0113] Figure 13 This is an example of instructing the release of the DCIPDCCH configuration in the SPS PDSCH configuration. Figure 13 In the example shown, the release of PDCCH 1370 in scheduling cell 1380 indicates the release of SPS configuration indices 0 and 1 (shown as PDSCH timings 1300 and 1310) in scheduling cell 1340.Figure 14 In the illustrated example, the scheduling cell 1380 has shorter slots than the scheduled cell 1340 (in other words, the scheduling cell has a larger subcarrier spacing than the scheduled cell, e.g., the scheduling cell can have a subcarrier spacing of 60 kHz and the scheduled cell can have a subcarrier spacing of 15 kHz). Assuming the ACK / NACK for the release PDCCH 1370 and the indicated PUCCH resources for the SPS PDSCHs 1300 and 1310 are the same, only SPS PDSCH#1 1310 is considered to be released (because the last symbol of the release PDCCH 1370 is not before the end of SPS PDSCH#0 1300) and the UE is expected to not receive this SPS PDSCH (e.g., in some embodiments, the gNB 20 generates no or never includes SPS PDSCHs in their end before the last symbol of the release PDSCH in the case that the PDCCH and the A / N for the released PDSCH map to the same PUCCH slot). A one-bit ACK / NACK is generated for the released SPS PDSCH#1 1310 and the set of release PDCCH 1370. The release PDCCH does not change the ACK / NACK for the remaining SPS PDSCHs.

[0114] One embodiment of the present disclosure relates to the case where a SPS PDSCH is released based on the reference PDSCH slot only if its end is after the end of the release PDCCH. In this embodiment, the indication of SPS PDSCH configuration indices i1, i2, …, i N The SPS release PDCCH is received in the release PDCCH slot of (N > 1) such that 1) M SPS PDSCH configuration indices j1, j2, …, j M (where M < N and ) is configured to be received in the PDSCH slot containing or overlapping the end symbol of the PDCCH, and 2) the ACK / NACK for the release PDCCH and L SPS PDSCHs map to the same PUCCH (where L < M). In this case, the SPS release PDCCH only applies to R SPS PDSCHs whose end symbol is not before the end symbol of the release PDCCH (where R < L). These SPS PDSCHs are considered to be released and the UE is expected to not receive these SPS PDSCHs in the PDSCH slot (e.g., the gNB 20 does not transmit data on the SPS PDSCHs considered to be released). A one-bit ACK / NACK is generated for the SPS release PDCCH and the R released SPS PDSCHs. The UE is expected to receive the SPS PDSCH whose end symbol is before the end of the release PDCCH.

[0115] One embodiment of the disclosure relates to the case where only SPS PDSCHs whose end is after the end of the releasing PDCCH are released, and the PDCCH slot is considered as a reference slot. In this embodiment, SPS PDSCH configuration indices i1, i2, …, i N (N≥1) are received in the released PDCCH slot, such that 1) M SPS PDSCH configuration indices j1, j2, …, j M (where M≤N and ) are configured to be received in all PDSCH slots overlapping with the PDCCH slot, and 2) the ACK / NACK for the releasing PDCCH and L SPS PDSCHs are mapped to the same PUCCH (where L≤M). In this case, the SPS releasing PDCCH only applies to R SPS PDSCHs whose end symbol end is not before the end symbol end of the releasing PDCCH (where R≤L). These SPS PDSCHs are considered as released, and the UE is expected not to receive these SPS PDSCHs within the PDSCH slots (e.g., gNB 20 does not transmit data on the SPS PDSCHs considered as released). One bit ACK / NACK is generated for the SPS releasing PDCCH and R released SPS PDSCHs. The UE is expected to receive SPS PDSCHs whose end symbol end is before the end symbol end of the releasing PDCCH.

[0116] In the above embodiments, the PDSCH manager 200 of the UE determines which of the indicated SPS PDSCHs are actually released, and which SPS PDSCHs are expected to be received by the UE, despite being indicated as released. Some aspects of the embodiments of the disclosure relate to providing a location for reporting ACK / NACK for SPS PDSCHs in the case where the SPS PDSCHs are received even though they are released.

[0117] One embodiment of the disclosure relates to an error case indicating that the ACK / NACK location is not available. In more detail, in the above embodiments, when configured with Type-1 HARQ-ACK codebook, the PDSCH manager 200 expects that there is one ACK / NACK bit location available for the SPS PDCCH release and the actually released SPS PDSCHs (R SPS PDSCHs), and there is an ACK / NACK bit location available for each of the remaining SPS PDSCHs that are received. If this is not the case, the embodiments of the disclosure relate to providing an error case indicating this situation.

[0118] One embodiment of the present disclosure relates to modifying ACK / NACK behavior to ignore SPS PDSCH configuration indices that are not actually released in the release PDCCH. When configured with Type-1 HARQ-ACK codebook, the PDSCH manager 200 of the UE assumes that only the SPS configuration indices of the SPS PDSCHs that are actually released (R SPS PDSCHs) are present in the release PDCCH for the purpose of determining the ACK / NACK bits for the release PDCCH. The starting and length indicator value (SLIV) of the SPS PDSCH with the lowest configuration index from the R SPS PDSCHs determines the location of the ACK / NACK for the release PDCCH and the R released PDSCHs. The ACK / NACK locations for the remaining SPS PDSCHs are determined under the assumption that they have been received. Any of the remaining SPS PDSCHs whose SLIVs are in the same Type-1 CB subgroup as the release PDCCH are determined by the PDSCH manager 200 to not have been received by the UE, and no ACK / NACK bits are generated for those SPS PDSCHs.

[0119] System and method for SPS PDSCH release with aggregation factor

[0120] As mentioned above, problem C relates to handling the release of SPS PDSCHs configured with an aggregation factor. Some aspects of embodiments of the present disclosure relate to supporting the case where, according to its aggregation factor, the end of the release PDCCH is after the end of the SPS PDSCH occasion within the repetition of the SPS PDSCH. In some embodiments, the end of the release PDCCH can be after the end of the end of the SPS PDSCH in the same slot and still release the SPS PDSCH as long as the SPS PDSCH occasion is not the last repetition due to the aggregation factor.

[0121] One embodiment of the present disclosure relates to the case where the last SPS PDSCH occasion in a SPS PDSCH with repetition is considered to determine whether a release PDCCH can release the SPS PDSCH. In more detail, if the SPS PDSCH configuration indicated by the release PDCCH is configured with an aggregation factor (AF) greater than or equal to 1, only the SPS PDSCH configuration with AF > 1 is considered to be configured to be received in the last slot of J < AF slots for the purpose of determining the release behavior. In other words, an SPS PDSCH configured with AF > 1 can be released by a PDCCH at any time up to the end of the last symbol of the last slot of the SPS PDSCH configuration with AF > 1. In the case of a semi-static time division duplex uplink / downlink (TDD UL / DL) configuration, the J slots are determined as the slots of the AF slots where the SPS PDSCH occasion does not overlap with any uplink (UL) symbols. The embodiments of the present disclosure related to Problem B can also be applied to the X-CC scenario and single release according to the case of N = 1 (e.g., only one SPS PDSCH configuration is identified in the release PDCCH).

[0122] Some aspects of the embodiments of the present disclosure relate to the specific case of single SPS release and SPS PDSCH with aggregation factor. In one embodiment, receiving a release PDCCH in the slot of the PDCCH indicating release of an SPS PDSCH configured with an aggregation factor AF > 1 on a PDSCH cell is supported such that: 1) at least for one of J < AF SPS PDSCH occasions, the end of the last symbol of the PDCCH reception is not after the end of the last symbol of the SPS PDSCH occasion reception, where the J occasions are determined after resolving the conflict with the TDD UL / DL configuration, and 2) the ACK / NACK of the SPS PDSCH release and the ACK / NACK of the SPS PDSCH will be mapped to the same PUCCH. In this case, the SPS PDSCH is considered to be released and a 1-bit A / N is generated for the SPS release PDCCH and the SPS PDSCH.

[0123] Figure 14 is a diagram illustrating a co-release of multiple active SPS PDSCH configurations with aggregation factor in a scheduled cell by a release DCI in a scheduling cell. In Figure 14 In the example shown, the release PDCCH 1470 (in the scheduling cell 1480) indicates release of SPS PDSCH configuration indices #0, #1, and #3. In this example, it is assumed that the SPS configurations with indices 0, 1, and 3 are configured with aggregation factors 4, 3, and 2, respectively. In particular, Figure 15AThe last three repetitions of SPS config#0 1400, 1401, and 1402 are shown in slots nD=0, nD=1, and nD=2, respectively (the first repetition of SPS config#0 is not shown). The three repetitions of SPS config#1 1411, 1412, and 1413 are illustrated in slots nD=1, nD=2, and nD=3, respectively. The two repetitions of SPS config#3 are illustrated in slots nD=2 and nD=3, respectively. According to the above method, because the last symbol of the release PDCCH 1470 falls in slot nD=2, it is before the last repetition of both SPS config#1 and SPS config#3 (e.g., repetitions 1413 and 1433, respectively), and thus, these configurations will be released. However, the last symbol falls after the last repetition of SPS config#0 (repetition 1402), and thus, SPS config#0 will not be released.

[0124] Figure 15A is a flowchart of a method 1500 for releasing SPS PDSCH configurations with aggregation according to one embodiment of the disclosure. As shown, a PDSCH manager 200 receives a release PDCCH that identifies an SPS PDSCH configured with aggregation. In operation 1510, the PDSCH manager 200 identifies a timing of an end symbol of a last repetition of the SPS PDSCH with aggregation. In operation 1530, the PDSCH manager 200 identifies a timing of an end symbol of the release PDCCH. In operation 1550, the PDSCH manager 200 compares the timing of the end of the end symbol of the release PDCCH to the timing of the end of the end symbol of the last repetition of the SPS PDSCH with aggregation, and in operation 1570, the PDSCH manager 200 releases the SPS PDSCH configured with aggregation if the end of the end symbol of the release PDCCH is before the end of the end symbol of the last repetition of the SPS PDSCH with aggregation. Figure 15B

[0125] Figure 15A is a flowchart of a method 1505 for determining whether a UE will receive an SPS PDSCH with aggregation when processing an SPS release PDCCH according to one embodiment of the disclosure. In more detail, in some embodiments of the disclosure, a gNB determines whether a UE will receive an SPS PDSCH with aggregation when processing an SPS release PDCCH according to the above method. In operation 1515, the gNB identifies a timing of an end symbol of a last repetition of the SPS PDSCH with aggregation. In operation 1535, the gNB identifies a timing of an end symbol of the release PDCCH. In operation 1555, the gNB compares the timing of the end of the end symbol of the release PDCCH to the timing of the end of the end symbol of the last repetition of the SPS PDSCH with aggregation, and in operation 1575, the gNB determines whether the UE will receive the SPS PDSCH with aggregation if the end of the end symbol of the release PDCCH is before the end of the end symbol of the last repetition of the SPS PDSCH with aggregation. Figure 15B ​The described embodiments generate an SPS release PDCCH to release an SPS PDSCH configuration with an aggregation factor and transmit the generated SPS release PDCCH to control the behavior of the UE 10, such as by causing the UE 10 to release the SPS PDSCH with the aggregation factor identified in the SPS release PDCCH and controlling the UE 10 reception of the SPS PDSCH. See Figure 16 In operation 1515, the gNB 20 identifies the timing of the end symbol of the last repetition of the SPS PDSCH with the aggregation factor to be released. In operation 1535, the gNB 20 identifies the timing of the end of the end symbol of the SPS release PDCCH. In operation 1555, the gNB 20 compares the timing of the end of the end symbol of the release PDCCH to the timing of the end of the end symbol of the last repetition of the SPS PDSCH with the aggregation factor. In operation 1575, the gNB 20 determines that the SPS PDSCH with the AF is released if the end of the end symbol of the SPS release PDCCH is before the end of the end symbol of the last repetition of the SPS PDSCH with the AF. The gNB 20 can then use this determination to transmit the release PDCCH according to the specified timing (e.g., generate a release PDCCH specifying the configuration index of the SPS PDSCH with the aggregation factor to be released) to control the UE 10 to release the identified SPS PDSCH with the aggregation factor. In some embodiments, the gNB 20 uses this determination to control whether to transmit data in the SPS PDSCH with the AF (e.g., whether to release the SPS PDSCH with the AF).

[0126] According to another embodiment of the disclosure, receiving a release PDCCH in a PDCCH slot indicating release of an SPS PDSCH configured with an aggregation factor AF > 1 on a PDSCH cell is not supported such that: 1) the end of the last symbol of the PDCCH reception is not after the end of the last symbol of the SPS PDSCH occasion reception at least for one of the AF SPS PDSCH occasions; and 2) the ACK / NACK of the SPS PDCCH and the ACK / NACK of the SPS PDSCH are to be mapped to the same PUCCH.

[0127] Figure 16 is a diagram illustrating cross-carrier SPS PDSCH release. Generally, decoding of downlink control information (DCI) takes longer on a cell with a lower SCS compared to a cell with a higher SCS. Figure 16One example is shown of SPS PDSCH 1600 on a cell 1640 with higher SCS = 120 KHz being released by a release PDCCH 1670 on a cell 1680 with lower SCS = 15 KHz. In the worst case, the UE 10 can unnecessarily decode the SPS PDSCH 1600, as the DCI can take too long to decode due to being received on a cell 1680 with a lower SCS than the cell 1640 on which the SPS PDSCH 1600 is received.

[0128] Additionally, the UE 10 can have completed the SPS PDSCH decoding process before it has completed the PDCCH decoding process, and thus has an ACK / NACK value prepared for the SPS PDSCH 1600. In Figure 17 In the example shown, the UE 10 takes a shorter time 1602 to decode the SPS PDSCH 1600, and the UE 10 takes a longer time 1672 to decode the release PDCCH 1670, such that the SPS PDSCH 1600 is decoded at time 1604 (as shown by the dashed line), which is before the time 1674 at which the release PDCCH 1670 is decoded. However, once the UE 10 decodes the release PDCCH 1670, the UE 10 can need to update the value of the ACK / NACK, such as by replacing the ACK / NACK of the SPS PDSCH 1600 with the ACK / NACK of the release DCI of the PDCCH 1670. This can interrupt the operation of the UE 10, depending on how the ACK / NACK preparation is implemented in hardware. In particular, for the UE 10, the values of the ACK / NACK bits in the payload can be updated after it has generated the full payload, or it feeds the values into the buffer in order as they are known. In the latter case, according to some embodiments of the present disclosure, a time offset can be introduced from the end of the PDCCH to the start of the SPS PDSCH to provide sufficient time to update the ACK / NACK bits of the payload accordingly.

[0129] Figure 17 is a diagram showing cross-carrier SPS PDSCH release according to one embodiment of the present disclosure. As Figure 17 is shown, the SPS PDSCH 1700 in a scheduled cell 1740 is released by a release PDCCH 1770 in a scheduling cell 1780, where the ACK / NACK of the SPS PDSCH and the ACK / NACK of the release PDCCH 1770 are mapped to the same PUCCH 1730.

[0130] According to one embodiment of the present disclosure, if a) the ACK / NACK of the SPS PDSCH 1700 and the ACK / NACK of the SPS release PDCCH 1770 are mapped to the same PUCCH 1730, and b) the end of the ending symbol of the SPS PDSCH 1700 is less than d symbols after the end of the ending symbol of the SPS release PDCCH 1770 (in the numerology of the SPS PDSCH), then the UE 10 is not expected to receive the SPS release PDCCH 1770 in the scheduling cell's time slot that indicates the release of the SPS PDSCH 1700 in the scheduling cell's time slot. In other words, if a) the ACK / NACK of the SPS PDSCH 1700 and the ACK / NACK of the SPS release PDCCH 1770 are mapped to the same PUCCH 1730, and b) the end of the ending symbol of the SPS PDSCH 1700 is at least d symbols after the end of the ending symbol of the SPS release PDCCH 1770, then the UE 10 supports the SPS release PDCCH 1770 in the scheduling cell's time slot that indicates the release of the SPS PDSCH 1700 in the scheduling cell's time slot. In some embodiments, d corresponds to the length of the gap between the end of the ending symbol of the SPS release PDCCH 1770 to the start of the SPS PDSCH 1700 (labeled as Δ in ​ Rel-16 3GPP 5G NR specification in the case of cross-carrier scheduling with different numerologies (e.g., d is the number of SPS PDSCH symbols that can be transmitted during the gap Δ). In some embodiments, d is defined to be one of several possible values, and the UE 10 can declare or advertise support for one or more values of d as a capability of the UE 10 (e.g., based on the UE's support for different d values in hardware and / or firmware). In some embodiments, the value d can be zero, and support for cross-carrier SPS release with mixed numerologies is specified or advertised to the gNB 20 as a capability of the UE 10. As such, some embodiments of the present disclosure relate to systems and methods for cross-carrier release of SPS PDSCH, where the gNB 20 transmits the SPS release PDCCH with timing such that the end of the ending symbol of the SPS release PDCCH is at least d symbols before the end of the ending symbol of the SPS PDSCH to be released.

[0131] In some embodiments, if a) the ACK / NACK for the SPS PDSCH 1700 and the ACK / NACK for the SPS release PDCCH 1770 are mapped to the same PUCCH 1730, and b) the starting symbol of the SPS PDSCH 1700 is less than d symbols after the end of the ending symbol of the SPS release PDCCH 1770 (in the parameter set of the SPS PDSCH), then the UE 10 is not expected to receive the SPS release PDCCH 1770 in the time slot of the scheduling cell that indicates the release of the SPS PDSCH 1700 in the time slot of the scheduled cell. In other words, if a) the ACK / NACK for the SPS PDSCH 1700 and the ACK / NACK for the SPS release PDCCH 1770 are mapped to the same PUCCH 1730, and b) the starting symbol of the SPS PDSCH 1700 is at least d symbols after the end of the ending symbol of the SPS release PDCCH 1770 (in the parameter set of the SPS PDSCH), then the UE 10 supports the SPS release PDCCH 1770 in the time slot of the scheduling cell that indicates the release of the SPS PDSCH 1700 in the time slot of the scheduled cell. As such, various aspects of embodiments of the present disclosure relate to systems and methods for cross-carrier release of SPS PDSCH, where the gNB 20 transmits the SPS release PDCCH with a timing such that the end of the ending symbol of the SPS release PDCCH is at least d symbols before the starting symbol of the SPS PDSCH to be released.

[0132] Accordingly, various aspects of embodiments of the present disclosure relate to systems and methods for handling the release of SPS PDSCH, including handling of collisions between PDSCHs, common release of PDSCHs, and PDSCHs configured with an aggregation factor.

[0133] While the application has been described in connection with certain exemplary embodiments, it will be understood that the application is not limited to the embodiments disclosed, but instead, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims and their equivalents.

Claims

1. A method for jointly releasing multiple semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs), the method comprising: A PDSCH manager of a user equipment including a processor and a memory receives a SPS release physical downlink control channel, PDCCH, in a scheduling cell, the SPS release PDCCH identifying N SPS PDSCH configuration indices, i1,..,iN, to be released N ; identifying, by a PDSCH manager, a time slot of a scheduled cell that overlaps with an end of an ending symbol of an SPS release physical downlink control channel (PDCCH); configurations, the M SPS PDSCH configuration indexes j1,.., jMcomprise all of the N SPS PDSCH configuration indexes configured to be received in the slot; and M where M < N, the M SPS PDSCH configuration indexes are associated with corresponding ending symbols. comparing, by the PDSCH manager, a timing of the end of the ending symbol of the SPS release PDCCH to a timing of an end of a corresponding ending symbol of the M SPS PDSCH configuration indices of the time slot; and releasing, by the PDSCH manager, L of the M SPS PDSCH configuration indices based on determining that the ending symbol of the SPS release PDCCH is before a corresponding ending symbol associated with each of the L SPS PDSCH configuration indices of the time slot.

2. The method of claim 1, wherein an acknowledgement / negative acknowledgement (ACK / NACK) bit of the SPS release PDCCH and an ACK / NACK of L of a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indices are mapped to a same physical uplink control channel (PUCCH).

3. The method of claim 1, wherein the scheduling cell has a first subcarrier spacing and the scheduled cell has a second subcarrier spacing that is different than the first subcarrier spacing.

4. The method of claim 3, wherein the first subcarrier spacing of the scheduling cell is lower than the second subcarrier spacing of the scheduled cell.

5. The method of claim 3, wherein the first subcarrier spacing of the scheduling cell is higher than the second subcarrier spacing of the scheduled cell.

6. A method for identifying jointly released multiple semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs), the method comprising: identifying, by a PDSCH manager of a base station comprising a processor and a memory, a time slot of a scheduled cell that overlaps with an end of an ending symbol of an SPS release physical downlink control channel (PDCCH) that identifies N SPS PDSCH configuration indices to be jointly released; by the PDSCH manager, identifying, from the N SPS PDSCH configuration indices configured in the slot, M SPS PDSCH configuration indices j1,.., jM comprising all configuration indices M where M < N, the M SPS PDSCH configuration indices being associated with corresponding ending symbols; comparing, by the PDSCH manager, a timing of the ending symbol of the SPS release PDCCH to a timing of a corresponding ending symbol of the M SPS PDSCH configuration indices of the time slot; and identifying, by the PDSCH manager, L of the M SPS PDSCH configuration indices based on determining that the ending symbol of the SPS release PDCCH is before a corresponding ending symbol associated with each of the L released SPS PDSCH configuration indices of the time slot.

7. The method of claim 6, wherein an acknowledgement / negative acknowledgement bit (ACK / NACK) of the SPS release PDCCH and ACK / NACK of L SPS PDSCH occasions of a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indices are mapped to a same physical uplink control channel (PUCCH).

8. The method of claim 6, wherein the scheduling cell has a first subcarrier spacing and the scheduled cell has a second subcarrier spacing different from the first subcarrier spacing.

9. The method of claim 8, wherein the first subcarrier spacing of the scheduling cell is lower than the second subcarrier spacing of the scheduled cell.

10. The method of claim 8, wherein the first subcarrier spacing of the scheduling cell is higher than the second subcarrier spacing of the scheduled cell.

11. A method for releasing a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) with an aggregation factor, the method comprising: receiving, by a PDSCH manager of a user equipment including a processor and a memory, a SPS release physical downlink control channel (PDCCH) in a scheduling cell, the SPS release PDCCH identifying a SPS PDSCH configuration index associated with a SPS PDSCH configured with an aggregation factor in a scheduled cell; identifying, by the PDSCH manager, a timing of an ending symbol of a last repetition of the SPS PDSCH with the aggregation factor; comparing, by the PDSCH manager, a timing of an ending symbol of the SPS release PDCCH to a timing of a last symbol of the last repetition of the SPS PDSCH configured with the aggregation factor; and releasing, by the PDSCH manager, the SPS PDSCH configuration index based on determining that the ending symbol of the SPS release PDCCH is before the last symbol of the last repetition of the SPS PDSCH configured with the aggregation factor.

12. The method of claim 11, wherein an acknowledgement / negative acknowledgement bit (ACK / NACK) of the SPS release PDCCH and ACK / NACK of the SPS PDSCH configured with the aggregation factor are mapped to a same physical uplink control channel (PUCCH).

13. The method of claim 11, wherein the scheduling cell has a first subcarrier spacing and the scheduled cell has a second subcarrier spacing different from the first subcarrier spacing.

14. The method of claim 13, wherein the first subcarrier spacing of the scheduling cell is lower than the second subcarrier spacing of the scheduled cell.

15. The method of claim 11, wherein the SPS release PDCCH identifies a plurality of SPS PDSCH configuration indices to release.

16. A method for identifying a released semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) with an aggregation factor (AF), the method comprising: identifying, by a PDSCH manager of a base station comprising a processor and a memory, a timing of an ending symbol of a last repetition of a SPS PDSCH with an AF in a scheduled cell; identifying, by the PDSCH manager, a timing of an ending symbol of a SPS release physical downlink control channel (PDCCH) in a scheduling cell; comparing, by the PDSCH manager, the timing of the ending symbol of the SPS release PDCCH with the timing of the ending symbol of the last repetition of the SPS PDSCH with the AF; and identifying, by the PDSCH manager, that the SPS PDSCH with the AF has been released when the ending symbol of the SPS release PDCCH is before the ending symbol of the last repetition of the SPS PDSCH with the AF.

17. The method of claim 16, wherein an acknowledgement / negative acknowledgement (ACK / NACK) bit of the SPS release PDCCH and an ACK / NACK of the SPS PDSCH configured with the aggregation factor are mapped to a same physical uplink control channel (PUCCH).

18. The method of claim 17, wherein the scheduling cell has a first subcarrier spacing and the scheduled cell has a second subcarrier spacing different from the first subcarrier spacing.

19. The method of claim 18, wherein the first subcarrier spacing of the scheduling cell is lower than the second subcarrier spacing of the scheduled cell.

20. The method of claim 16, wherein the SPS release PDCCH identifies a plurality of SPS PDSCH configuration indexes to be released.

Images