Aspects of embodiments of the present disclosure relate to systems and methods for processing semi-persistently scheduled or dynamically scheduled channels in cellular communications protocols.
In cellular communications protocols, such as Release 15 of the 3rd Generation Partnership Project (3GPP) Fifth Generation New Radio (5G-NR) specifications for mobile networks, downlink traffic from a base station to user equipment (e.g., a smartphone) is wirelessly transmitted in signals that include a physical downlink shared channel (PDSCH) which can be either dynamically scheduled (dynamic grant or DG) or semi-persistently scheduled (SPS).
Aspects of embodiments of the present disclosure relate to cellular communication protocols, including systems and methods implemented in user equipment (UE) for processing semi-persistently scheduled (SPS) or dynamically scheduled (or dynamic grant or DG) channels transmitted by a base station (or g node B or gNB).
According to one embodiment of the present disclosure, a method for jointly releasing multiple semi-persistently scheduled (SPS) physical downlink shared channels (PDSCHs) includes: receiving, by a PDSCH manager of a user equipment including a processor and memory, 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; identifying, by the PDSCH manager, a slot of a scheduled cell, where the slot of the scheduled cell overlaps with the end of an ending symbol of the SPS release PDCCH; identifying, by the PDSCH manager, M SPS PDSCH configuration indices j1, . . . , jM including all configuration indices from among the N SPS PDSCH configuration indices that are configured in the slot, where M≤N, the M SPS PDSCH configuration indices being associated with corresponding ending symbols; comparing, by the PDSCH manager, timings of the end of the ending symbol of the SPS release PDCCH and the corresponding ending symbols of the M SPS PDSCH configuration indices of the slot; and releasing, by the PDSCH manager, L SPS PDSCH configuration indices among the M SPS PDSCH configuration indices 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 indices of the slot.
An acknowledgement/negative-acknowledge bit (ACK/NACK) of the SPS release PDCCH and an ACK/NACK of L SPS PDSCH occasions from among a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indices may be mapped to a same physical uplink control channel (PUCCH).
The scheduling cell may have a first subcarrier spacing and the scheduled cell may have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell may be lower than the second subcarrier spacing of the scheduled cell. The first subcarrier spacing of the scheduling cell may be higher than the second subcarrier spacing of the scheduled cell.
According to one embodiment of the present disclosure, a method for identifying jointly released multiple semi-persistently scheduled (SPS) physical downlink shared channels (PDSCHs) includes: identifying, by a PDSCH manager of a base station including a processor and memory, a slot of a scheduled cell that will overlap with the end of an ending symbol of a SPS release physical downlink control channel (PDCCH) identifying N SPS PDSCH configuration indices to be jointly released; identifying, by the PDSCH manager, M SPS PDSCH configuration indices j1, . . . , jM including all configuration indices from among the N SPS PDSCH configuration indices that are configured in the slot, where M≤N, the M SPS PDSCH configuration indices being associated with corresponding ending symbols; comparing, by the PDSCH manager, timings of the end of the ending symbol of the SPS release PDCCH and the corresponding ending symbols of the M SPS PDSCH configuration indices of the slot; and identifying, by the PDSCH manager, L released SPS PDSCH configuration indices among the M SPS PDSCH configuration indices 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 released SPS PDSCH configuration indices of the slot.
An acknowledgement/negative-acknowledge bit (ACK/NACK) of the SPS release PDCCH and an ACK/NACK of L SPS PDSCH occasions from among a plurality of SPS PDSCH occasions identified by the M SPS PDSCH configuration indices may be mapped to a same physical uplink control channel (PUCCH).
The scheduling cell may have a first subcarrier spacing and the scheduled cell may have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell may be lower than the second subcarrier spacing of the scheduled cell. The first subcarrier spacing of the scheduling cell may be higher than the second subcarrier spacing of the scheduled cell.
According to one embodiment of the present disclosure, a method for releasing a semi-persistently scheduled (SPS) physical downlink shared channel (PDSCH) with an aggregation factor includes: receiving, by a PDSCH manager of a user equipment including a processor and 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 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 the timing of the 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 end of 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.
An acknowledgement/negative-acknowledge bit (ACK/NACK) of the SPS release PDCCH and an ACK/NACK of the SPS PDSCH configured with the aggregation factor may be mapped to a same physical uplink control channel (PUCCH).
The scheduling cell may have a first subcarrier spacing and the scheduled cell may have a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell may be lower than the second subcarrier spacing of the scheduled cell.
The SPS release PDCCH may identify a plurality of SPS PDSCH configuration indices to be released.
According to one embodiment of the present disclosure, a method for identifying a released semi-persistently scheduled (SPS) physical downlink shared channel (PDSCH) with aggregation factor (AF) includes: identifying, by a PDSCH manager of a base station including a processor and memory, a timing of an ending symbol of a last repetition of the SPS PDSCH with AF in a scheduled cell; identifying, by the PDSCH manager, a timing of an ending symbol of a 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 and the timing of the end of the ending symbol of the last repetition of the SPS PDSCH with AF; and identifying, by the PDSCH manager, that the SPS PDSCH with AF is 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 AF.
An acknowledgement/negative-acknowledge bit (ACK/NACK) of the SPS release PDCCH and an ACK/NACK of the SPS PDSCH configured with the aggregation factor may be mapped to a same physical uplink control channel (PUCCH).
The scheduling cell may have a first subcarrier spacing and the scheduled cell has a second subcarrier spacing different from the first subcarrier spacing. The first subcarrier spacing of the scheduling cell may be lower than the second subcarrier spacing of the scheduled cell.
The SPS release PDCCH may identify a plurality of SPS PDSCH configuration indices to be released.
The accompanying drawings, together with the specification, illustrate exemplary embodiments of the present invention, and, together with the description, serve to explain the principles of the present invention.
In the following detailed description, only certain exemplary embodiments of the present invention are shown and described, by way of illustration. As those skilled in the art would recognize, the invention may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein.
In cellular communications, such as Release 15 (Rel-15) of the 3rd Generation Partnership Project (3GPP) new radio (NR) technology (e.g., fifth generation new radio or 5G-NR) for mobile networks, 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 physical downlink shared channels (PDSCHs) which can be either dynamically scheduled (dynamic grant or DG) or semi-persistently scheduled (SPS).
A DG PDSCH is scheduled by a scheduling physical downlink control channel (PDCCH) which is used to convey the downlink control information (DCI) to the user equipment (UE) such as a smartphone, a tablet computer, a Wi-Fi hotspot, and the like. The DCI includes, among other information, the time and frequency resources in which UE can receive the DG PDSCH. According to Rel-15 of the 5G-NR standards, every DG PDSCH can only be received by first receiving the scheduling DCI.
Release-15 of the 5G-NR standards also define a semi-persistently scheduled (SPS) PDSCH, which makes it possible for the UE to receive PDSCHs without a corresponding scheduling DCI. In Release-15, SPS PDSCH is supported to provide contiguous downlink transmission without the need to schedule every individual PDSCH via a separate DCI.
For example, in SPS PDSCH, a base station (or g Node B or gNB) configures the UE with one or more SPS configurations via radio resource control (RRC) messages. A SPS configuration information element (IE) per serving cell per bandwidth part (BWP) includes periodicity, physical uplink control channel (PUCCH) resource information and other information required for SPS operation (see, e.g., 3GPP Technical Specification 38.331 Clause 6). For example, a SPS configuration information element may specify a periodicity for the SPS PDSCH occasions, e.g., how frequently the SPS PDSCH can be received. For example, under some circumstances, the minimum periodicity is 10 ms (10 slots for subcarrier spacing of 15 KHz).
Rel-15 of the 5G-NR supports at most one active SPS PDSCH configuration per bandwidth part (BWP) per serving cell. Furthermore, there can be at most one serving cell within each cell group that can be configured with a SPS PDSCH configuration. To provide more flexibility to the uRLLC UE, including lower latency, aspects of embodiments of the present disclosure relate to supporting multiple active SPS configurations per BWP per serving cell. Moreover, aspects of embodiments of the present disclosure allow the configuration of more than one cell with SPS configurations within each cell group.
The received downlink analog signal 30 may be supplied to a radio 12, which may apply various signal processing operations to the received analog signal to generate a digital signal, which may be further processed by baseband processor 14. In some circumstances, the radio 12 and the baseband processor may be integrated as a single unit. The baseband processor 14 generates digital information 50 decoded from the received signal 30 and may supply the decoded information, along with other information about the state of the communication, to an application processor (AP) 18. The digital information or data 50 may include a digital bitstream, to be supplied for consumption by applications running on the application processor 18 of the mobile station 10. The application processor 18 may execute an operating system (e.g., Google® Android®, Tizen™, Apple® iOS®, or the like) and the applications (or apps) may include, for example, a voice calling application, a video conferencing application, an email application, a web browser, or the like. The application processor 18 may also control aspects of the communication with the base station 20 via the baseband processor 14 and the radio 12.
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, may be implemented in one or more processing circuits (e.g., a radio 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)) of a digital radio, where various portions of various blocks may be implemented in the same circuit (e.g., on the same die or in a same package) or in different circuits (e.g., on different dies or in different packages, connected over a communication bus).
As shown in
As shown in
Aspects of embodiments of the present disclosure relate to providing more flexibility to the base station (or g node B or gNB) to schedule Ultra Reliable Low Latency Communications (uRLLC) and to satisfy the latency requirements, by allowing multiple active SPS configurations per serving cell per BWP. By allowing multiple active SPS configurations per BWP of a serving cell, it is possible that multiple active SPS occasions overlap in time and/or frequency in one slot.
While
In order to handle these multiple active SPS configurations, various aspects of embodiments of the present disclosure relate to systems and methods for determining which of the active SPS configurations are to be handled under circumstances where these SPS occasions overlap in time and/or frequency in one slot, as shown in
Handling Semi-Persistently Scheduled Physical Downlink Shared Channels in Release 16
In the particular example shown in
Accordingly, based on Release 15 of the 5G-NR standards, in the type-1 HARQ-ACK codebook, SPS occasions for configurations 0 through 3 (SPS config #0 410, SPS config #1 411, SPS config #2 412, and SPS config #3 413) are sub-grouped together in sub-group #0 430 and SPS occasions for configurations 4 and 5 (SPS config #4 414 and SPS config #5 415) are sub grouped together in sub-group #1 431, thereby forming two sub-groups.
Problem A: PDSCH Collision and Release Handling
Generally, in Release 16 (Rel-16) of the 3rd Generation Partnership Project (3GPP) Fifth Generation New Radio (5G-NR) specifications for mobile networks, in the case of multiple active Semi-Persistently Scheduled (SPS) Physical Downlink Shared Channel (PDSCH) configurations on a bandwidth part (BWP) of a serving cell, the user equipment (UE) only receives certain SPS PDSCHs which are not overlapping, where the SPS PDSCHs to be received are determined by their SPS configuration indices. Referring to
In the example, shown in
As noted above, a slot SPS release DCI may be transmitted via a PDCCH to release an active SPS configuration, where a UE is no longer expected to receive a previously-scheduled SPS PDSCH after it has received a corresponding release PDCCH for that active SPS configuration. In Release 16, this behavior involves supporting a case that 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, then a 1 bit HARQ-ACK is generated for SPS release and a UE does not expect to receive the SPS PDSCH if HARQ-ACKs for the SPS release and the SPS reception would map to the same physical uplink control channel (PUCCH). In addition, in Release 16, it is not supported that a SPS release PDCCH in a slot is received after the end of the SPS PDSCH reception in the slot for the same SPS configuration corresponding to the SPS release PDCCH if HARQ-ACKs for the SPS release and the SPS reception would map to the same PUCCH.
Furthermore, in Release 16, if a UE is configured to receive a SPS PDSCH in a slot for a SPS configuration, and if the UE receives a PDCCH indicating a SPS PDSCH release corresponding to the SPS configuration in the slot where the end of a last symbol or ending symbol of the PDCCH reception (as opposed to the beginning of the ending symbol of the PDCCH reception) is not after the end of a last symbol of the SPS PDSCH reception, and if HARQ-ACK information for the SPS PDSCH release and the SPS PDSCH reception would be multiplexed in a same PUCCH, the UE does not expect to receive the SPS PDSCH, does not generate HARQ-ACK information for the SPS PDSCH reception, and generates a HARQ-ACK information bit for the SPS PDSCH release (see, e.g., 3GPP Technical Specification 38.213 clause 9.1).
However, Release 16 of the 3GPP 5G-NR standard does not specify the order in which the above specifications of are applied, which can result in different outcomes, depending on how the specifications are interpreted by implementing cellular equipment such as the UE and the gNB. Different interpretations of the agreements by a UE and a gNB that are communicating with each other can cause data loss and/or communication inefficiencies due to different decisions about which of the active SPS configurations will be received and which will not be received.
If the UE resolves the collision among the SPS PDSCHs first, then SPS config #0 510 is identified as the SPS PDSCH configuration with lowest index and the other overlapping PDSCH, SPS config #1 511 is removed and therefore SPS config #1 511 is removed. Next applying the rule regarding the release DCI, because the last symbol of the release DCI #0 520 is before the end of the corresponding SPS PDSCH occasion (SPS config #0 510), then SPS config #0 510 is released and therefore the corresponding occasion is not received. In addition, the acknowledgement/negative-acknowledgement (ACK/NACK) may be transmitted. For a “Type-1” HARQ-ACK codebook (CB), (NACK #1,ACK #0) is transmitted assuming two containers are available, (TDRA of SPS #1 and SPS #0 fall into two different subgroups for a Type-1 HARQ-ACK CB according to Technical Specification 38.213). For a “Type-2” HARQ-ACK CB, ACK #0 is transmitted.
On the other hand, if the UE addresses the release DCI first, then SPS config #0 510 is released and removed. After removing the PDSCH occasion corresponding to SPS config #0 510, the UE applies the collision resolution rule. In this particular example, only SPS config #1 511 remains and it does not overlap with any other PDSCH occasions in this slot and therefore SPS config #1 511 is received. In this case, for a Type-1 HARQ-ACK CB, (ACK #1,ACK #0) is transmitted assuming two containers are available (TDRA of SPS #1 and SPS #0 fall into two different subgroup for Type-1 CB according to TS 38.213). For a Type-2 HARQ-ACK CB, (ACK #0,ACK #1) is transmitted by appending ACK/NACK of SPS PDSCH config #1 511 to the end of the dynamic portion of the Type-2 CB which here is assumed to only include the release DCI for SPS config #0 510 (Release DCI #0 520).
Accordingly,
Problem B: Joint SPS PDSCH Release Handling
Release 16 of the 3GPP 5G-NR specifies that a release DCI can be used to jointly release multiple SPS PDSCH configurations, as identified based on their indices.
Under one interpretation of the standards, the Release DCI #0 #1 #2 620 is not supported (e.g., not permitted under the standard) because the SPS config #0 610 ends before the end of the Release DCI #0 #1 #2 620. On the other hand, under another interpretation, the Release DCI #0 #1 #2 620 is supported because the SPS config #1 611 ends after the end of the release PDCCH. This situation may also take place in cross carrier scheduling with different numerologies when the sub-carrier spacing (SCS) of the release DCI is smaller than that of SPS PDSCH slot. In this case, the release PDCCH typically overlaps with multiple SPS PDSCH slots.
Problem C: SPS PDSCH Release with Aggregation Factor
In some circumstances, a SPS release DCI PDCCH overlaps with a single occasion of a SPS PDSCH with aggregation factor (e.g., where a SPS PDSCH is scheduled for multiple consecutive slots). In that case, some of the SPS PDSCH occasions will end before the end of the SPS release DCI PDCCH, while some other SPS PDSCH may end after the end of the release PDCCH. However, Rel-16 disallows this arrangement because one ACK/NACK is generated for the entire SPS PDSCH reception, if the ACK/NACK for PDSCH and release PDCCH are mapped to the same PUCCH. Not supporting this scenario will significantly reduce the network flexibility to release the SPS PDSCH with aggregation factor. A similar scenario is when the cross carrier (X-CC) SPS release PDCCH releases a SPS PDSCH configuration on a cell with larger numerology.
Assuming that all the ACK/NACK of all of the SPS PDSCH and that of the release PDCCH is mapped to the same PUCCH, the scenario will not be supported according to the current standard if the “slot” (as the term is used in Release 16 of the 3GPP standard) refers to the PDCCH slot of the scheduled cell 801 (rather than a slot of the scheduling cell 802), while it may be a typical use case of X-CC scheduling with different numerologies. Similar scenario holds when the numerology of scheduling cell is larger than that of scheduled cell.
Accordingly, aspects of embodiments of the present disclosure relate to systems and methods for addressing at least the problems identified above: Problem A: PDSCH collision and release handling; Problem B: joint SPS PDSCH release handling; and Problem C: SPS PDSCH release with aggregation factor.
Systems and Methods for PDSCH Collision and Release Handling
As described above, Problem A relates to how the order in which physical downlink shared channel (PDSCH) collision resolution rules and PDSCH release rules are performed can sometimes cause different behavior.
Accordingly, some aspects of embodiments of the present disclosure relate to systems and methods for determining which PDSCH or PDSCHs are to be received in a slot in accordance with sequentially handling collisions between PDSCHs and handling commands to release PDSCHs, rather than making the determinations separately or concurrently (e.g., in parallel) or in circumstances where the order is undefined. For example, if the operations were performed concurrently with shared data structures (e.g., a shared set of Q SPS PDSCHs in a slot), a race condition may occur in which different PDSCHs may be selected to be received based on the timing by which the determinations were made. As another example, different implementations may cause these determinations to be made in different orders, thereby causing inconsistency or incompatibility in the determinations made by different devices, and thereby reducing the efficiency of communication between the devices.
According to one embodiment of the present disclosure, SPS PDSCH collisions are handled before handling SPS PDSCH releases.
According to one embodiment of the present disclosure, SPS PDSCH releases are handled before handling SPS PDSCH collisions.
While some aspects of embodiments of the present disclosure are discussed above in reference to
When determining PDSCHs to be received in a slot in accordance with the embodiments of
Accordingly, some aspects of embodiments of the present disclosure relate to systems and methods for ACK/NACK determination in accordance with the embodiment of
In some embodiments, it is an error case when: a) Type-1 HARQ-ACK codebook is configured and b) the ACK/NACK location of the release PDCCH and that of an unreleased SPS PDSCH whose ACK/NACK is mapped to the same PUCCH as the release PDCCH, are the same.
In some embodiments, in a case where: a) Type-1 HARQ-ACK CB is configured; and b) the ACK/NACK location of the release PDCCH and that of an unreleased SPS PDSCH whose ACK/NACK is mapped to the same PUCCH as the release PDCCH, are the same, then the PDSCH manager 200 generates a one bit ACK/NACK as the logical AND of the ACK/NACK of the release PDCCH and that of the unreleased PDSCH. In the specific example of
In some embodiments, in a case where: a) Type-1 HARQ-ACK CB is configured; and b) the ACK/NACK location of the release PDCCH and that of an unreleased SPS PDSCH whose ACK/NACK is mapped to the same PUCCH as the release PDCCH, are the same, then PDSCH manager 200 performs SPS collision handling (as described above) to resolve the collision among the SPS PDSCHs and the released SPS PDSCH as if the released SPS PDSCH was not actually released. In the specific example of
Systems and Methods for Joint SPS PDSCH Release Handling
As discussed above, Problem B relates to joint release of multiple SPS PDSCH occasions in circumstances where one of the SPS PDSCH occasions to be released ends before the end of the release PDCCH.
Accordingly, some aspects of embodiments of the present disclosure relate to systems and methods for handling joint release of multiple SPS PDSCH configurations.
Various embodiments will be described based on a reference slot to determine the UE behavior. The reference slot may be the PDCCH slot, PDSCH slot, or the slot with smallest SCS among the two. The PDCCH slot is defined as the slot on the scheduling cell in which the release PDCCH is transmitted. The PDSCH slot is defined as the slot on the scheduled cell in which the ending symbol of the release PDCCH ends (e.g., the slot overlapping with the end of the ending symbol, which may not be the same as the slot overlapping with the beginning of the ending symbol). The slot based on the smallest SCS configuration may be either the PDCCH slot or the PDSCH slot, depending on which has the smallest SCS (or they may be the same size).
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 that are indicated for release.
One embodiment of the present disclosure relates to a case where the release PDCCH ends before the end of at least one of the SPS PDSCHs in a corresponding PDSCH slot, where μPDCCH≤μPDSCH (where μ is the subcarrier spacing of the cells, e.g., μPDCCH is the SCS of the PDCCH and μPDSCH is the SCS of the PDSCH). In this embodiment, a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations having indices i1, i2, . . . , iN, on the PDSCH cell such that: 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the 2μ
One embodiment of the present disclosure relates to a case where the release PDCCH ends before the end of at least one of the SPS PDSCHs in a corresponding PDSCH slot, where μPDCCH≥μPDSCH. In this embodiment, a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN, on the PDSCH cell such that: 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the SPS PDSCH slot which contains the PDCCH slot; 2) ACK/NACK of the release PDCCH and L SPS PDSCHs among the M PDSCHs (where L≤M) are mapped to the same PUCCH; and 3) the release PDCCH is received after the end of at least one of the SPS PDSCHs among the L SPS PDSCH receptions,
According to some embodiments of the present disclosure, the network (e.g., a base station gNB) sends the SPS release PDCCH ahead of all the SPS PDSCHs in the largest slot among the PDCCH slot and the PDSCH slot. These embodiments is amenable to a simple UE implementation for processing of SPS PDSCHs and the ACK/NACK reporting.
One embodiment of the present disclosure relate to a case where the release PDCCH ends before the end of all SPS PDSCHs and where μPDCCH≤μPDSCH and where a smallest SCS slot is taken as a reference slot (in this case, because μPDCCH≤μPDSCH, a PDCCH slot is taken as the reference slot). In this embodiment, it is not supported that a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN, on the PDSCH cell such that 1) M≤N SPS PDSCH configuration indices j1, j2, . . . , jM where {j1, j2, . . . , jM}⊆{j1, j2, . . . , iN} are configured to be received in the 2μ
One embodiment of the present disclosure relates to a case where a release PDCCH ends before the end of all SPS PDSCHs where the smallest SCS slot is taken as the reference slot μPDCCH≥μPDSCH (in this case, because μPDCCH>μPDSCH, a PDSCH slot is taken as the reference slot). In this embodiment, it is not supported that a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN on the PDSCH cell, such that 1) M≤N SPS PDSCH configuration indices j1, j2, . . . , jM where {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN} are configured to be received in the PDSCH slot containing the PDCCH slot and 2) ACK/NACK of the release PDCCH and L≤M SPS PDSCHs among the M PDSCHs are mapped to the same PUCCH and 3) the release PDCCH is received after the end of any of the L SPS PDSCH receptions. In other words, this embodiment supports a case where, when 1) M≤N SPS PDSCH configuration indices j1, j2, . . . , jM where {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN} are configured to be received in the PDSCH slot containing the PDCCH slot and 2) ACK/NACK of the release PDCCH and L≤M SPS PDSCHs among the M PDSCHs are mapped to the same PUCCH, then 3) the release PDCCH must be received before the end of all L SPS PDSCH receptions.
One embodiment of the present disclosure relates to a case where a release PDCCH ends before the end of all SPS PDSCHs, where a PDSCH slot is taken as the reference slot. In this embodiment, it is not supported that a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN on the PDSCH cell, such that: 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the last PDSCH slot containing or overlapping with the end of the ending symbol of the PDCCH; 2) ACK/NACK of the release PDCCH and L SPS PDSCHs among the M PDSCHs (where L≤M) are mapped to the same PUCCH; and 3) the PDCCH is received after the end of any of the L SPS PDSCH receptions. In case where 1) and 2) hold but 3) does not, such as where the PDCCH is received before the end of all the L SPS PDSCHs, all the L SPS PDSCHs in the PDSCH slots are considered as released and all the indicated SPS PDSCHs in the previous PDSCH slots overlapping with the PDCCH slots are received. In other words, this embodiment supports a case where, when 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the last PDSCH slot containing or overlapping with the end of the ending symbol of the PDCCH; 2) ACK/NACK of the release PDCCH and L SPS PDSCHs among the M PDSCHs (where L≤M) are mapped to the same PUCCH, then 3) the release PDCCH must be received before the end of all of the L SPS PDSCH receptions.
One embodiment of the present disclosure relates to a case where the release PDCCH ends before the end of all SPS PDSCHs; PDCCH slot). In this embodiment, it is not supported that a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN on the PDSCH cell, such that 1) MSPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in any of the PDSCH slots which overlap with the PDCCH slot; 2) ACK/NACK of the release PDCCH and L≥1 SPS PDSCHs among the M PDSCHs (where L≤M) are mapped to the same PUCCH; and 3) the PDCCH is received after the end of any of the L SPS PDSCH receptions. In other words, some embodiments relate to a case where it is supported that a SPS release PDCCH in a PDCCH slot indicates the release of SPS PDSCH configurations indices i1, i2, . . . , iN on the PDSCH cell, such that 1) MSPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , iM}⊆{i1, i2, . . . , iN}) are configured to be received in any of the PDSCH slots which overlap with the PDCCH slot; 2) ACK/NACK of the release PDCCH and L≥1 SPS PDSCHs among the M PDSCHs (where L≤M) are mapped to the same PUCCH; and 3) the PDCCH is received before the end of all of the L SPS PDSCH receptions.
Some aspects of embodiments of the present disclosure relate to less restrictive approaches to handling joint releases of SPS PDSCH configurations, such as by determining which indicated SPS PDSCHs are actually released and which ones are expected to be received by UE in spite of being indicted as released.
One embodiment of the present disclosure relates to a case where only SPS PDSCHs which end after the end of the release PDCCH are released, where μPDCCH≤μPDSCH; and a smallest SCS slot is taken as the reference slot (in this case, because μPDCCH≤μPDSCH, a PDCCH slot is taken as the reference slot). In this embodiment, it is supported to receive a SPS release PDCCH in a PDCCH slot indicating the release of SPS PDSCH configurations indices i1, i2, . . . , iN (N≥1) on the SPS PDSCH cell such that: 1) the SCS numerology of the release PDCCH is smaller than or equal to that of the SPS PDSCH cell; 2) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the 2μ
One embodiment of the present disclosure relates to a case where only SPS PDSCHs which end after the end of the release PDCCH are released μPDCCH≥μPDSCH; and a smallest SCS slot is taken as the reference slot (in this case, because μPDCCH≥μPDSCH, a PDSCH slot is taken as the reference slot). In this embodiment, it is supported to receive a SPS release PDCCH in a PDCCH slot indicating the release of SPS PDSCH configurations indices i1, i2, . . . , iN (N≥1) on the SPS PDSCH cell such that: 1) the SCS numerology of the release PDCCH is greater than or equal to that of the SPS PDSCH cell; 2) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the SPS PDSCH slots which contains the PDCCH slot; and 3) ACK/NACK of the release PDCCH and L≤M SPS PDSCHs are mapped to the same PUCCH. In this case, the SPS release PDCCH is only applicable to R SPS PDSCHs (where R≤L) for which the end of the ending symbol of the PDSCH is not before the end of the ending symbol of release PDCCH. These SPS PDSCHs are considered as released and the UE is not expected to receive them within the PDCCH slot. One bit ACK/NACK is generated for the SPS release PDCCH and the R released SPS PDSCHs.
One embodiment of the present disclosure relates to a case where only SPS PDSCHs which end after the end of the release PDCCH are released, based on a reference PDSCH slot. In this embodiment, it is supported to receive a SPS release PDCCH in a PDCCH slot indicating the release of SPS PDSCH configurations indices i1, i2, . . . , iN (N≥1) on the SPS PDSCH cell such that 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in the PDSCH slot where the PDSCH slot is the PDSCH slot which contains or overlaps with the end of the ending symbol of the PDCCH and 2) ACK/NACK of the release PDCCH and L SPS PDSCHs are mapped to the same PUCCH (where L≤M). In this case, the SPS release PDCCH is only applicable to R SPS PDSCHs for which the end of the ending symbol of the PDSCH is not before the end of the ending symbol of release PDCCH (where R≤L). These SPS PDSCHs are considered as released and UE is not expected to receive them within the PDSCH slot (e.g., the gNB 20 does not transmit data on the SPS PDSCHs that are considered to be released). A 1 bit ACK/NACK is generated for the SPS release PDCCH and the R released SPS PDSCHs. The UE is expected to receive the SPS PDSCHs whose ending symbol ends before the ending symbol of the release PDCCH.
One embodiment of the present disclosure relates to a case where Only SPS PDSCHs which end after the end of the release PDCCH are released, and a PDCCH slot is taken as the reference slot. In this embodiment, it is supported to receive a SPS release PDCCH in a PDCCH slot indicating the release of SPS PDSCH configurations indices i1, i2, . . . , iN (N≥1) on the SPS PDSCH cell such that 1) M SPS PDSCH configuration indices j1, j2, . . . , jM (where M≤N and {j1, j2, . . . , jM}⊆{i1, i2, . . . , iN}) are configured to be received in all of the PDSCH slots which overlap with the PDCCH slot and 2) ACK/NACK of the release PDCCH and the L SPS PDSCHs are mapped to the same PUCCH (where L≤M). In this case, the SPS release PDCCH is only applicable to R SPS PDSCHs for which the end of the ending symbol of the PDSCH is not before the end of the ending symbol of release PDCCH (where R≤L). These SPS PDSCHs are considered as released and UE is not expected to receive them within the PDSCH slots (e.g., the gNB 20 does not transmit data on the SPS PDSCHs that are considered to be released). A 1 bit ACK/NACK is generated for the SPS release PDCCH and the R released SPS PDSCHs. The UE is expected to receive the SPS PDSCHs whose ending symbol ends before the end of the ending symbol of the release PDCCH.
In the above embodiments, the PDSCH manager 200 of the UE determines which indicated SPS PDSCHs are actually released and which ones are expected to be received by UE in spite of being indicted as released. Some aspects of embodiments of the present disclosure relate to providing a location for reporting ACK/NACK of SPS PDSCHs in these circumstances where a SPS PDSCH is received even though they were released.
One embodiment of the present disclosure relates to an error case indicating that an ACK/NACK location is unavailable. In more detail, when a Type-1 HARQ-ACK codebook is configured, in the above embodiments, 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 (the R SPS PDSCHs) and there are ACK/NACK bit locations available for each of the remaining received SPS PDSCHs. If this is not the case, embodiments of the present disclosure relate to providing an error case indicating this condition.
One embodiment of the present disclosure relates to modifying ACK/NACK behavior to ignore SPS PDSCH configuration indices in the PDCCH that are not actually released. When Type-1 HARQ-ACK codebook is configured, for the purpose of determination of ACK/NACK bits for the release PDCCH, the PDSCH manager 200 of the UE assumes that only SPS configuration indices of the actually released SPS PDSCHs (the R SPS PDSCHs) are present in the release PDCCH. The location of ACK/NACK of the release PDCCH and the R released PDSCHs is determined from the start and length indicator value (SLIV) of the SPS PDSCH with the lowest configuration index among the R SPS PDSCHs. The ACK/NACK locations for the remaining SPS PDSCHs are determined assuming they are received. Any of the remaining SPS PDSCH whose SLIV is in the same Type-1 CB subgroup as that of the release PDCCH is determined by the PDSCH manager 200 as not received by the UE, and no ACK/NACK bit is generated for such SPS PDSCHs.
Systems and Methods for SPS PDSCH Release with Aggregation Factor
As discussed above, Problem C relates to handling release of SPS PDSCHs that are configured with an aggregation factor. Some aspects of embodiments of the present disclosure relate to supporting a case where the release PDCCH ends after the end of a SPS PDSCH occasion within the repetition of the SPS PDSCH in accordance with its aggregation factor. In some embodiments, the end of the ending symbol of the release PDCCH may be after the end of the ending symbol of the SPS PDSCH in the same slot and still release the SPS PDSCH, so long as the SPS PDSCH occasion is not the last repetition due to the aggregation factor.
One embodiment of the present disclosure relates to a case where the last SPS PDSCH occasion among the SPS PDSCH with repetition is considered to determine whether the release PDCCH can release the SPS PDSCHs). In more detail, if the SPS PDSCH configurations indicated by the release PDCCH are configured with an aggregation factor (AF) greater than or equal to 1, for the purposes of determining release behavior, a SPS PDSCH configuration with AF≥1 is only considered as configured to be received in the last slot among the j≤AF slots. In other words, the SPS PDSCH with configuration AF≥1 can by released by a PDCCH that ends at any time before the last symbol of the last slot of the SPS PDSCH configuration with AF≥1. In case of semi-static time division duplex uplink/downlink (TDD UL/DL) configuration, J slots are determined as the slots among the AF slots in which the SPS PDSCH occasion does not overlap with any uplink (UL) symbol. Embodiments of the present disclosure relating to addressing Problem B can also be applied to the X-CC scenario as well as to single release in accordance with the case of N=1 (e.g., only one SPS PDSCH configuration identified in the release PDCCH).
Some aspects of embodiments of the present disclosure relate to the particular case of a single SPS release and a SPS PDSCH with aggregation factor. In one embodiment, it is supported that a release PDCCH is received in a PDCCH slot indicating the release of a SPS PDSCH configured with an aggregation factor AF≥1 on the PDSCH cell such that: 1) at least for one occasion among J≤AF occasions of the SPS PDSCH, the end of a last symbol of the PDCCH reception is not after the end of a last symbol of the SPS PDSCH occasion reception where the J occasions are determined after resolving conflict with TDD UL/DL configuration and 2) the ACK/NACK of the SPS PDCCH release and the ACK/NACK of the SPS PDSCH would be mapped to the same PUCCH. In this case, the SPS PDSCH is considered as released, and a 1 bit A/N is generated for the SPS release PDCCH and the SPS PDSCHs.
According to another embodiment of the present disclosure, it is not supported that a release PDCCH is received in a PDCCH slot indicating the release of a SPS PDSCH configured with an aggregation factor AF≥1 on the PDSCH cell such that: 1) at least for one occasion among the AF occasions of the SPS PDSCH, the end of a last symbol of the PDCCH reception is not after the end of a last symbol of the SPS PDSCH occasion reception and 2) the ACK/NACK of the SPS PDCCH release and ACK/NACK of the SPS PDSCH would be mapped to the same PUCCH.
In addition, the UE 10 may have finished the SPS PDSCH decoding process before it has finished the PDCCH decoding process and therefore prepared an ACK/NACK value for the SPS PDSCH 1600. In the example shown in
According to one embodiment of the present disclosure, a UE 10 is not expected to receive a SPS release PDCCH 1770 in a slot of scheduling cell indicating the release of a SPS PDSCH 1700 in a slot of scheduled cell 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 (in the numerology of SPS PDSCH) after the end of the ending symbol of the SPS release PDCCH 1770. In other words, the UE 10 supports a SPS release PDCCH 1770 in a slot of scheduling cell indicating the release of a SPS PDSCH 1700 in a slot of the scheduled cell if a) the ACK/NACK of SPS PDSCH 1700 and the ACK/NACK of 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. In some embodiments, d corresponds to the length of the gap (labeled A in
In some embodiments, the UE 10 is not expected to receive a SPS release PDCCH 1770 in a slot of scheduling cell indicating the release of a SPS PDSCH 1700 in a slot of scheduled cell if a) the ACK/NACK of the SPS PDSCH 1700 and the ACK/NACK of 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 (in the numerology of SPS PDSCH) after the end of the ending symbol of the SPS release PDCCH 1770. In other words, the UE 10 supports a SPS release PDCCH 1770 in a slot of scheduling cell indicating the release of a SPS PDSCH 1700 in a slot of scheduled cell if a) the ACK/NACK of the SPS PDSCH 1700 and the ACK/NACK of 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 (in the numerology of SPS PDSCH) after the end of the ending symbol of the SPS release PDCCH 1770. As such, some embodiments of the present disclosure relate to a system and method for cross-carrier release of SPS PDSCHs, 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.
Accordingly, various aspects of embodiments of the present disclosure relate to systems and methods for handling the release of SPS PDSCH, including circumstances involving collision handling between PDSCHs, joint release of PDSCHs, and PDSCHs configured with aggregation factors.
While the present invention has been described in connection with certain exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims, and equivalents thereof.
This application is a continuation of U.S. patent application Ser. No. 17/148,443, filed Jan. 13, 2021, which claims priority to and the benefit of U.S. Provisional Patent Application No. 63/057,087, filed in the United States Patent and Trademark Office on Jul. 27, 2020, the entire disclosure of each of which is incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
10924225 | Tsai et al. | Feb 2021 | B2 |
20130301582 | Jiang et al. | Nov 2013 | A1 |
20150043458 | Seo | Feb 2015 | A1 |
20180014284 | Yi et al. | Jan 2018 | A1 |
20180331792 | Yang et al. | Nov 2018 | A1 |
20190090266 | Zhao | Mar 2019 | A1 |
20190253206 | Kusashima et al. | Aug 2019 | A1 |
20190306841 | Huang | Oct 2019 | A1 |
20200205141 | Khoshnevisan et al. | Jun 2020 | A1 |
Number | Date | Country |
---|---|---|
202008811 | Feb 2020 | TW |
WO 2020022523 | Jan 2020 | WO |
Entry |
---|
Taiwanese Notice of Allowance dated Aug. 6, 2024, issued in corresponding Taiwanese Patent Application No. 110111231, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20230337246 A1 | Oct 2023 | US |
Number | Date | Country | |
---|---|---|---|
63057087 | Jul 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17148443 | Jan 2021 | US |
Child | 18207574 | US |