Set HARQ timing for PDSCH with pending PDSCH-TO-HARQ-TIMING-INDICATOR

Abstract

Methods and systems are provided for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) having a pending PDSCH-to-HARQ-timing-indicator (PHTI). In one aspect, a method performed by a wireless device includes: receiving first downlink control information (DCI) associated with a first DL data transmission, the first DCI including a non-digital PHTI; receiving the first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PHTI indicating a location of the HARQ feedback associated with the second DL data transmission; setting the location of the HARQ feedback associated with the first DL data transmission to be the same as the location of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set location.

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application serial number 62 / 836,228, filed on April 19, 2019, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present application relates to physical downlink shared channel (PDSCH) to hybrid automatic repeat request (HARQ) timing, and in particular to setting the HARQ timing for PDSCH by means of a pending PDSCH-to-HARQ-timing-indicator. Background Art

[0004] New Radio (NR) provides flexibility in Hybrid Automatic Repeat Request (HARQ) feedback timing to take into account dynamic Time Division Duplex (TDD), and also potentially combine several HARQ feedbacks to achieve lower overhead and higher reliability.

[0005] Figure 1 Hybrid automatic repeat request (HARQ) feedback according to a conventional NR system is shown. The timing (referred to as K1) between a downlink (DL) data transmission (e.g., 100A, 100B, etc.) on a physical downlink shared channel (PDSCH) and its corresponding HARQ acknowledgement (ACK) or negative acknowledgement (NACK) (e.g., 102A, 102B, etc.) on a physical uplink control channel (PUCCH) is determined based on a 3-bit field in the downlink control information (DCI) for the corresponding DL data transmission within the physical downlink control channel (PDCCH). The radio resource control (RRC) message configures the user equipment (UE) with a set of 8 values ​​to be indexed by the 3-bit field in the DCI to generate a value of K1 to be used by the UE for the timing of the corresponding HARQ (the possible value range is {0,1,...,15}). As shown Figure 1 As shown in FIG. 1 , HARQ 102A occurs in the same time slot (half subframe) as its corresponding DL data transmission 100A, and HARQ 102B occurs in the next time slot after the time slot containing its corresponding DL data transmission 100B.

[0006] With the help of semi-static codebook and / or dynamic codebook, NR provides the flexibility to include aggregate feedback corresponding to multiple HARQ processes in one PUCCH / uplink control information (UCI) transmission. Figure 1 As shown in FIG. 1 , HARQ for DL ​​data transmissions 100C and 100D occurs in a combined HARQ 102C.

[0007] Semi-static HARQ codebook

[0008] For the semi-static HARQ codebook, the codebook size in time (DL association group) is determined based on a set of configured HARQ-ACK timing K1, PDCCH monitoring opportunities, and a semi-statically configured TDD mode. For each time slot, the UE needs to report a fixed-size HARQ feedback bitmap according to its carrier aggregation (CA) and transport block (TB) / code block group (CBG) configuration. In this example, the bitmap size is 7 bits. For unreceived TB / CBG, the corresponding bit in the HARQ feedback bitmap is set to indicate NACK.

[0009] Dynamic HARQ codebook

[0010] The dynamic HARQ codebook provides the possibility to dynamically determine a set of HARQ processes for which HARQ feedback should be reported. DCI includes:

[0011] - Downlink Allocation Indicator (DAI), which indicates the number of HARQ processes that should be reported; and

[0012] - PDSCH to HARQ-ACK timing (ΔT), which specifies the time resource in which the eNB expects feedback, for example, as a time offset.

[0013] DAI calculation for dynamic HARQ codebook

[0014] The UE calculates the dynamic HARQ codebook size with reference to the DAI value. The DAI value in the DCI is incremented for each PDSCH transmission. The DAI in the DL scheduling DCI should be incremented by 1 compared to the immediately preceding DL scheduling DCI. If this is not the case, it indicates that the PDSCH transmission has been lost. The difference between the two DAI values ​​received at the UE in the current and earlier DCI indicates how many PDSCH transmissions have been lost.

[0015] Figure 2 An example of combined HARQ feedback according to a conventional NR system is shown. Figure 2 In , each time slot contains a PDCCH whose DCI value includes the DAI value and the ΔT value, followed by a PDSCH containing DL data transmission. Figure 2In the example shown in , the values ​​of DAI and ΔT are shown below the corresponding PDCCH blocks, which are arbitrarily numbered from 1 to 7. From left to right, the DAI value for PDCCH 1 is 1, indicating to the UE that the PDSCH just following the first PDCCH, PDSCH 1, will require HARQ. The ΔT value is equal to 6, indicating that the UE is expected to provide HARQ feedback after 6 time slots. The DAI value for PDCCH 2 is 2, indicating to the UE that two PDSCHs, PDSCH 1 and PDSCH 2, will require HARQ. The ΔT value is equal to 5, indicating to the UE that it should provide HARQ feedback after 5 time slots. The DAI value for PDCCH 3 is 3, indicating to the UE that each of the three PDSCHs, PDSCH 1, PDSCH 2, and PDSCH3, requires HARQ.

[0016] This sequence continues, with ΔT decreasing as the time comes for the UE to provide HARQ feedback to the NR base station (gNB), while DAI increases as the number of HARQ processes that should be reported increases. However, the DAI value in NR release 15 (rel-15) is only two bits (representing four possible values ​​0, 1, 2, 3); after reaching the highest DAI value (i.e., 3), the DAI value rolls over and starts again from the minimum value. This is in Figure 2 , where PDCCH 4 includes a DAI value of 0. PDSCH 7 is too close to PDCCH to be included in the combined HARQ feedback, so the PDCCH will include HARQ feedback for PDSCH 1 to PDSCH 6.

[0017] Figure 3 Another example of combined HARQ feedback according to a conventional NR system is shown. Figure 3 In the example shown in , PUCCH 1 includes HARQ feedback for PDSCH 1 and PDSCH 2. PDSCH 3 is too close to PUCCH 1, so PUCCH 2 includes HARQ feedback for PDSCH 3, PDSCH 4, and PDSCH 5. Figure 3 In the example, PDSCH 6 is too close to PUCCH 2, so the HARQ feedback for PDSCH 6 will need to be sent in a later PUCCH (in Figure 3 is reported in (not shown).

[0018] General system problems

[0019] Figure 4A problem encountered by conventional NR systems is shown. NR supports small processing delays, but not small enough to allow HARQ feedback to be provided in the same timeslot as the corresponding DL data transmission. For example, when the subcarrier spacing (SPS) is 15 kilohertz (kHz), the layer 1 (L1) processing delay from the end of PDSCH to the start of PUCCH is a minimum of 8 orthogonal frequency division multiplexing (OFDM) symbols, assuming a UE capability of 1. Therefore, there will be eight OFDM symbol gaps between PDSCH reception and corresponding feedback via PUCCH. For an SCS of 30kHz, HARQ feedback for PDSCH in timeslot n cannot be included in the PUCCH in timeslot n, while for an SCS of 60kHz, PDSCH feedback cannot be included in both timeslots n and n-1. Therefore, HARQ feedback for those PDSCHs will have to occur in a later PUCCH.

[0020] However, the later time may fall outside the gNB's Channel Occupancy Time (COT). In this case, the UE may have to sense the channel according to Category 4 Listen Before Talk (LBT) before sending feedback, which increases the chance that the UE will not be able to provide feedback at the indicated timing.

[0021] To this end, the 3rd Generation Partnership Project (3GPP) NR in Unlicensed Spectrum (NR-U) Working Group decided to support the possibility to defer HARQ feedback in order to give the UE a chance to send feedback at a later time, possibly within a COT initiated by another gNB, where the UE can send feedback with fast LBT or even without LBT, depending on the situation:

[0022] protocol:

[0023] A non-numeric value is added to the possible range of PDSCH-to-HARQ-timing-indicator values ​​defined in Rel-15 and is used to indicate to the UE that HARQ-ACK feedback for the corresponding PDSCH is deferred until the timing and resources for HARQ-ACK feedback are provided by the gNB.

[0024] However, it is unclear what the UE behavior is upon receiving this indication, and no mechanism is specified to trigger pending feedback.

[0025] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges.The present disclosure specifies UE behavior when a non-numeric K1 value is received indicating that HARQ feedback is deferred.

[0026] Various embodiments are proposed herein to solve one or more of the problems disclosed herein. Certain embodiments may provide one or more of the following technical advantages. The UE behavior when receiving a non-numeric value K1 value is undefined, and the present disclosure provides different alternatives on how to solve this problem. Summary of the invention

[0027] Methods and systems are provided for setting HARQ timing for a physical downlink shared channel (PDSCH) having a pending PDSCH-to-HARQ-timing-indicator.

[0028] According to one aspect of the present disclosure, a method performed by a wireless device for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator includes: receiving first downlink control information (DCI) associated with a first downlink (DL) data transmission, the first DCI including a non-digital PDSCH-to-HARQ-timing-indicator; receiving the first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of the HARQ feedback associated with the second DL data transmission; setting the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set time position.

[0029] In some embodiments, receiving the second DCI includes: receiving information indicating the number of HARQ processes that should be reported, which number includes all pending PDSCHs and all PDSCHs since the last PDSCH with a DCI including a digital PDSCH-to-HARQ-timing-indicator having a DCI including a non-digital PDSCH-to-HARQ-timing-indicator.

[0030] In some embodiments, receiving information indicating the number of HARQ processes that should be reported includes receiving a downlink allocation indicator (DAI).

[0031] In some embodiments, only when it is determined that the second DL data transmission belongs to the same PDSCH group as the first DL data transmission, the following operations are performed: the time position of the HARQ feedback associated with the first DL data transmission is set to be the same as the time position of the HARQ feedback associated with the second DL data transmission, and the HARQ feedback associated with the first DL data transmission is sent at the set time position.

[0032] In some embodiments, receiving a second DCI associated with a second DL data transmission comprises receiving a user equipment (UE) specific DCI sent on a physical downlink control channel (PDCCH), the UE specific DCI comprising a PDSCH-to-HARQ-timing-indicator.

[0033] In some embodiments, the UE-specific DCI also includes a HARQ process identifier (ID).

[0034] In some embodiments, the UE-specific DCI also includes a new data indicator (NDI) value corresponding to the HARQ process ID.

[0035] In some embodiments, the UE-specific DCI also includes a PDSCH group ID and a corresponding downlink allocation indicator (DAI).

[0036] In some embodiments, the UE-specific DCI also includes a triggering bit indicating that the PDSCH-to-HARQ-timing-indicator is applicable to all PDSCHs with pending or non-digital PDSCH-to-HARQ-timing-indicator.

[0037] In some embodiments, the trigger bit comprises a portion of the DCI that is scheduling the PDSCH.

[0038] In some embodiments, the trigger bit comprises a portion of the DCI that is not scheduling the PDSCH.

[0039] According to one aspect of the present disclosure, a method for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator, performed by a wireless device, includes: receiving first downlink control information (DCI) associated with a first downlink (DL) data transmission of a first PDSCH group, the first DCI including a digital PDSCH-to-HARQ-timing-indicator; determining that a time position of HARQ feedback associated with the first DL data transmission indicated by the digital PDSCH-to-HARQ-timing-indicator is too close to the first DL data transmission; and in response to the determination, not sending HARQ feedback associated with the first DL data transmission at the indicated HARQ transmission time.

[0040] In some embodiments, the method further comprises providing an indication on a physical uplink control channel (PUCCH) at the indicated HARQ transmission time, the indication notifying the new radio base station gNB that the HARQ feedback is deferred.

[0041] In some embodiments, the method further includes: receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of HARQ feedback associated with the second DL data transmission; setting the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set time position.

[0042] According to one aspect of the present disclosure, a method performed by a wireless device for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator includes: receiving first downlink control information (DCI) associated with a first downlink (DL) data transmission of a first PDSCH group, the first DCI including a digital PDSCH-to-HARQ-timing-indicator; determining that the digital PDSCH-to-HARQ-timing-indicator is a predefined value indicating that a corresponding HARQ transmission on a physical uplink control channel (PUCCH) should be postponed due to a later request for another HARQ transmission corresponding to another PDSCH on the PUCCH.

[0043] In some embodiments, the method further includes: receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of HARQ feedback associated with the second DL data transmission; setting the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set time position.

[0044] According to one aspect of the present disclosure, a method for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator, performed by a wireless device, includes: receiving first downlink control information DCI associated with a first downlink (DL) data transmission of a first PDSCH group, the first DCI including a digital PDSCH-to-HARQ-timing-indicator; determining that the digital PDSCH-to-HARQ-timing-indicator is a predefined value indicating that a corresponding uplink (UL) HARQ transmission on a physical uplink control channel (PUCCH) should be sent in a time slot or symbol group that can be dynamically selected for UL or DL; determining that the time slot or symbol group has been set for DL ​​transmission and is therefore unavailable for corresponding UL HARQ transmission; and in response to the determination, postponing the corresponding HARQ transmission.

[0045] In some embodiments, the method further includes: receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of HARQ feedback associated with the second DL data transmission; setting the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set time position.

[0046] According to one aspect of the present disclosure, a method performed by a wireless device for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) having a pending PDSCH-to-HARQ-timing-indicator includes: receiving first downlink control information (DCI) associated with a first downlink (DL) data transmission, the first DCI including a digital PDSCH-to-HARQ-timing-indicator having a predefined value, the predefined value indicating that the HARQ transmission should be delayed until the wireless device has received a digital PDSCH-to-HARQ-timing-indicator having a value different from the predefined value. The invention relates to a method for transmitting a HARQ feedback associated with the first DL data transmission, wherein the HARQ feedback is transmitted to the first DL data transmission via a digital PDSCH-to-HARQ-timing-indicator; receiving a first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of the HARQ feedback associated with the second DL data transmission; setting the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set time position.

[0047] In some embodiments, the predefined value includes an existing PDSCH-to-HARQ-timing-indicator value that has been remapped from indicating a delay value to indicating that the HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH-to-HARQ-timing-indicator having a value different from the predefined value.

[0048] In some embodiments, prior to receiving the first DCI, the wireless device receives an instruction to remap an existing PDSCH-to-HARQ-timing-indicator value from indicating a delay value to indicating that HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH-to-HARQ-timing-indicator having a value different from a predefined value.

[0049] In some embodiments, the predefined value comprises additional bits that have been added to an existing PDSCH-to-HARQ-timing-indicator value bit field in the DCI.

[0050] According to one aspect of the present disclosure, a method performed by a base station for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator includes:

[0051] Determining PDSCH-to-HARQ-timing for an upcoming downlink (DL) data transmission to a user equipment (UE); determining that HARQ feedback for the upcoming DL data transmission should be delayed by the UE until further notification from a base station; and sending first downlink control information (DCI) associated with the upcoming DL data transmission to the UE, the first DCI including a predefined PDSCH-to-HARQ-timing-indicator value for indicating to the UE that HARQ feedback for the upcoming DL data transmission should be delayed until further notification from the base station.

[0052] In some embodiments, determining that HARQ feedback for an upcoming DL data transmission should be delayed by the UE until further notification from the base station comprises determining that a processing delay from an end of the upcoming DL data transmission to a start of the HARQ feedback opportunity is less than a minimum threshold delay.

[0053] In some embodiments, the predefined PDSCH-to-HARQ-timing-indicator value comprises a non-numeric value.

[0054] In some embodiments, the predefined PDSCH-to-HARQ-timing-indicator value includes an existing PDSCH-to-HARQ-timing-indicator value that has been remapped from indicating a delay value to indicating that the HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH-to-HARQ-timing-indicator having a value different from the predefined value.

[0055] In some embodiments, prior to sending the first DCI, the base station sends an instruction to the UE to remap an existing PDSCH-to-HARQ-timing-indicator value from indicating a delay value to indicating that HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH-to-HARQ-timing-indicator having a value different from a predefined value.

[0056] In some embodiments, the predefined value comprises additional bits that have been added to an existing PDSCH-to-HARQ-timing-indicator value bit field in the DCI.

[0057] In some embodiments, the method further includes: sending a further notification to the UE.

[0058] In some embodiments, sending the further notification to the UE comprises sending a second DCI associated with a second DL data transmission, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator.

[0059] In some embodiments, sending the second DCI further comprises sending at least one of: a HARQ process identifier (ID); a new data indicator (NDI) value; a PDSCH group ID; a downlink allocation indicator (DAI); or a trigger bit.

[0060] According to one aspect of the present disclosure, a wireless device for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator, the wireless device including a processing circuit configured to: receive first downlink control information (DCI) associated with a first downlink (DL) data transmission, the first DCI including a non-digital PDSCH-to-HARQ-timing-indicator; receive the first DL data transmission; determine HARQ feedback for the first DL data transmission; receive a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of the HARQ feedback associated with the second DL data transmission; set the time position of the HARQ feedback associated with the first DL data transmission to be the same as the time position of the HARQ feedback associated with the second DL data transmission; and send the HARQ feedback associated with the first DL data transmission at the set time position.

[0061] In some embodiments, the processing circuit is further configured to perform the steps of any of the wireless device methods disclosed herein.

[0062] In some embodiments, the processing circuit includes one or more processors and a memory storing instructions, the instructions being executable by the one or more processors, whereby the wireless device is operable to perform the steps.

[0063] According to one aspect of the present disclosure, a base station is used to set hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator, the base station including a processing circuit configured to: determine the PDSCH-to-HARQ-timing for an upcoming downlink (DL) data transmission to a user equipment (UE); determine that HARQ feedback for the upcoming DL data transmission should be delayed by the UE until further notification from the base station; and send first downlink control information (DCI) associated with the upcoming DL data transmission to the UE, the first DCI including a predefined PDSCH-to-HARQ-timing-indicator value for indicating to the UE that HARQ feedback for the upcoming DL data transmission should be delayed until further notification from the base station.

[0064] In some embodiments, the processing circuit is further configured to perform the steps of any one of the base station methods disclosed herein.

[0065] In some embodiments, the processing circuit further comprises one or more processors and a memory storing instructions, the instructions being executable by the one or more processors, whereby the wireless device is operable to perform the steps. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0067] Figure 1 shows HARQ feedback according to a conventional NR system;

[0068] Figure 2 An example of combined HARQ feedback according to a conventional NR system is shown;

[0069] Figure 3 Another example of combined HARQ feedback according to a conventional NR system is shown;

[0070] Figure 4 A problem encountered by conventional NR systems is shown;

[0071] Figure 5 shows setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure;

[0072] Figure 6is a flow chart illustrating steps of an exemplary method of setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure;

[0073] Figure 7 is a flow chart illustrating steps of an exemplary method of setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure;

[0074] Figure 8 illustrates a flow chart showing steps of an exemplary method of setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure;

[0075] Fig. 9 illustrates a flow chart showing steps of an exemplary method of setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure;

[0076] Fig.10 An example of a cellular communication system is shown in which embodiments of the present disclosure may be implemented;

[0077] Fig.11 A wireless communication system is shown represented as a 5G network architecture consisting of core network functions (NFs), wherein the interaction between any two NFs is represented by point-to-point reference points / interfaces;

[0078] Fig.12 Shows the use of service-based interfaces between NFs in the control plane instead of using Fig.11 5G network architecture of point-to-point reference points / interfaces used in the 5G network architecture;

[0079] Fig.13 An embodiment of a UE according to various aspects described herein is shown;

[0080] Fig.14 is a schematic block diagram illustrating a virtualization environment 1400 in which functionality implemented by some embodiments may be virtualized;

[0081] Fig.15 A communication system according to some embodiments of the present disclosure is shown;

[0082] Fig.16 A communication system according to some embodiments of the present disclosure is shown;

[0083] Fig.17 is a flow chart illustrating a method implemented in a communication system according to some embodiments of the present disclosure;

[0084] Fig.18 is a flow chart illustrating a method implemented in a communication system according to some embodiments of the present disclosure;

[0085] Fig.19 is a flow chart illustrating a method implemented in a communication system according to some embodiments of the present disclosure;

[0086] Fig. 20 is a flow chart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0087] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and illustrate the best mode for practicing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts that are not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0088] Set the PDSCH-to-HARQ-Timing-Indicator for pending feedback with non-digital PDSCH-to-HARQ-Timing-Indicator:

[0089] Example 1 - Using the Next Valid Timing Indicator

[0090] Figure 5 Setting the hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) with a pending PDSCH-to-HARQ-timing-indicator according to some embodiments of the present disclosure is shown. Figure 5 In the embodiment shown in , the timing and / or resources for pending HARQ acknowledgement (ACK) feedback are set to be the same as the first subsequently transmitted HARQ process with a valid (digital) PDSCH-to-HARQ-timing-indicator. Figure 5, the HARQ timing for PDSCH 3 is set to the same position in the time domain as pointed to by the PDSCH-to-HARQ-timing-indicator of PDSCH4 (variously referred to herein as "position", "time position", "time resource", "time", "opportunity", "transmission opportunity", etc.), that is, the position of the physical uplink control channel (PUCCH) 2. In other words, the HARQ feedback for PDSCH 3 and the HARQ feedback for PDSCH 4 are jointly transmitted in the HARQ feedback opportunity indicated by the digital PDSCH-to-HARQ-timing-indicator for the HARQ feedback of PDSCH 4.

[0091] As another aspect of this embodiment, the downlink allocation indicator (DAI) value for the first PDSCH with a valid PDSCH-to-HARQ-timing-indicator (e.g., PDSCH 4) should also count the previous PDSCH with a non-numeric PDSCH-to-HARQ-timing-indicator (e.g., PDSCH 3) since the last PDSCH with a valid PDSCH-to-HARQ-timing-indicator (e.g., PDSCH 2). Figure 5 In the example, the value of ΔT in the physical downlink control channel (PDCCH) 4 should be 2 (indicating both PDSCH 3 and PDSCH 4) instead of 1 (indicating only PDCCH 4).

[0092] Figure 6 1 is a flowchart showing steps of an exemplary method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, performed at a user equipment (UE) according to embodiment 1 of the present invention. Figure 6 In the embodiment shown in , the process includes the following steps:

[0093] Step 600: Receive first downlink control information (DCI) associated with a first downlink (DL) data transmission, the first DCI including a non-digital PDSCH-to-HARQ-timing-indicator;

[0094] Step 602: Receive a first DL data transmission;

[0095] Step 604: Determine HARQ feedback for the first DL data transmission;

[0096] Step 606: Receive a second DCI associated with a second DL data transmission, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator indicating a location of a HARQ feedback associated with the second DL data transmission;

[0097] Step 608: Setting the position of the HARQ feedback associated with the first DL data transmission to be the same as the position of the HARQ feedback associated with the second DL data transmission; and

[0098] Step 610: Send HARQ feedback associated with the first DL data transmission at the location set in step 608.

[0099] Example 2—Also considering PDSCH group

[0100] In some embodiments of the present disclosure, if the DCI scheduling the PDSCH supports PDSCH group indication, the timing and / or resources for pending HARQ-ACK feedback will be set to the same as the first subsequently transmitted HARQ process belonging to the same group and with a valid (digital) PDSCH-to-HARQ-timing-indicator.

[0101] As another aspect of this embodiment, the DAI value for the first PDSCH with a valid PDSCH-to-HARQ-timing-indicator also counts the previous PDSCHs with non-numeric PDSCH-to-HARQ-timing-indicators belonging to the same group since the last one with a valid PDSCH-to-HARQ-timing-indicator.

[0102] Figure 7 1 is a flowchart showing steps of an exemplary method performed at a UE for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to Embodiment 2 of the present disclosure. Figure 7 In the embodiment shown in , the process includes the following steps:

[0103] Step 700: Receive a first DCI associated with a first DL data transmission of a first PDSCH group, the first DCI comprising a non-digital PDSCH-to-HARQ-timing-indicator;

[0104] Step 702: Receive a first DL data transmission;

[0105] Step 704: Determine HARQ feedback for the first DL data transmission;

[0106] Step 706: Receive a second DCI associated with a second DL data transmission, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator indicating a location of a HARQ feedback associated with the second DL data transmission;

[0107] Step 708: Determine whether the second DL data transmission belongs to the same PDSCH group as the first DL data transmission. If not, end the process. If yes, proceed to step 710.

[0108] Step 710: Setting the position of the HARQ feedback associated with the first DL data transmission to be the same as the position of the HARQ feedback associated with the second DL data transmission; and

[0109] Step 712: Send HARQ feedback associated with the first DL data transmission at the location set in step 710.

[0110] Example 3 - Explicit DCI signaling

[0111] In some embodiments of the present disclosure, new signaling is defined to indicate the timing and resources (with non-digital timing indication) for pending HARQ-ACK feedback. For example, in some embodiments, new UE-specific DCI is sent on the PDCCH. Examples include, but are not limited to, the following:

[0112] o The DCI indicates at least a HARQ process identifier (ID) and a PDSCH-to-HARQ-timing-indicator. It may also include a new data indicator (NDI) value corresponding to the HARQ process ID.

[0113] οThe DCI indicates at least a PDSCH group ID, a corresponding DAI, and a PDSCH-to-HARQ-timing-indicator.

[0114] o The DCI includes a trigger bit and a PDSCH-to-HARQ-timing-indicator applicable to all PDSCHs with pending or unset PDSCH-to-HARQ-timing-indicator.

[0115] ■ In some embodiments, the trigger may be part of the DCI that is scheduling another PDSCH. In some embodiments, the PDSCH-to-HARQ-timing-indicator applies to both pending and new PDSCHs.

[0116] ■ In some embodiments, the trigger may be part of a separate DCI that does not schedule PDSCH.

[0117] Figure 8 A flowchart showing steps of an exemplary method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator performed at a new radio (NR) base station (gNB) according to embodiment 3 of the present disclosure is shown. Figure 8 In the embodiment shown in , the process includes the following steps:

[0118] Step 800: Sending a first DCI associated with a first DL data transmission to a first UE, the first DCI including a non-digital PDSCH-to-HARQ-timing-indicator;

[0119] Step 802: Send a second DCI associated with a second DL data transmission to the first UE, the second DCI including a digital PDSCH-to-HARQ-timing-indicator and at least one of the following: at least one HARQ process ID; an NDI value; at least one PDSCH group ID; a corresponding DAI; and / or a trigger bit.

[0120] Example 4 - Delayed HARQ despite digital timing indicators

[0121] In some embodiments of the present disclosure, according to predefined rules (e.g., radio resource control (RRC) configuration), the UE is not expected to send feedback according to the indicated digital Kl value, but the UE is expected to defer sending feedback until new timing and resources for HARQ-ACK feedback are provided by the gNB. Example conditions include, but are not limited to, the following:

[0122] Condition 1: PDSCH scheduled with a digital K1 value that results in a HARQ-ACK transmission too close to the PUCCH to be sent on the PUCCH, for example, because the required processing time between the end of the PDSCH and the PUCCH cannot be met.

[0123] In some embodiments, the gNB detects this condition based on the absence of HARQ feedback in the indicated PUCCH resources; this may trigger the gNB to signal new HARQ feedback timing, for example according to one of the alternatives of embodiment 3, or in a subsequent DCI according to embodiment 2. Yet another alternative is to use embodiment 1, in which case the gNB does not have to take any explicit signaling action to resolve the situation, but will have to prepare to receive HARQ feedback according to embodiment 1.

[0124] In some embodiments, as an alternative to using lack of HARQ feedback as a sign of delayed HARQ feedback, when the processing time is too short to provide "real" HARQ feedback, the UE instead provides an indication (on the PUCCH indicated by the number K1) that informs the gNB that the UE has deferred HARQ feedback (e.g. due to lack of processing time). This will be a new type of indication to be standardized.

[0125] Condition 2: A PDSCH scheduled with a digital K1 value should postpone the corresponding HARQ-ACK transmission on the PUCCH due to a later request for another HARQ-ACK transmission corresponding to other PDSCH on the PUCCH.

[0126] Condition 3: PDSCH is scheduled with a digital Kl value indicating that HARQ feedback should be sent in a dynamic time slot or dynamic symbol group (i.e., symbols dynamically selected by the gNB that can be used for uplink (UL) or DL ​​transmission), and the gNB then allocates these symbols (or this time slot) for DL ​​transmission. In this case, the deferred HARQ feedback can be processed according to embodiments 3, 2, or 1 in the same manner as described above for condition 1.

[0127] Fig. 9 The figure illustrates a flowchart showing the steps of an exemplary method performed at a UE for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator according to embodiment 4, condition 1 of the present invention. Fig. 9 In the embodiment shown in , the process includes the following steps:

[0128] Step 900: Receive a first DCI associated with a first DL data transmission of a first PDSCH group, the first DCI comprising a digital PDSCH-to-HARQ-timing-indicator;

[0129] Step 902: Determine that the position of the HARQ associated with the first DL data transmission indicated by the digital PDSCH-to-HARQ-timing-indicator is too close to the first DL data transmission; and

[0130] Step 904: In response to the determination, not sending a HARQ associated with the first DL data transmission at the indicated HARQ transmission time;

[0131] Step 906: Optionally, provide an indication on the PUCCH at the indicated HARQ transmission time, which notifies the gNB that the HARQ feedback is deferred.

[0132] Embodiment 5 - Modified or extended PDSCH-to-HARQ-Timing-Indicator field

[0133] In some embodiments of the present disclosure, the existing PDSCH-to-HARQ-timing-indicator field in NR Release (Rel-) 15 is modified or extended. Example embodiments include but are not limited to the following:

[0134] In one embodiment, in DCI format 1_0 in NR Rel-15, the PDSCH-to-HARQ-timing-indicator field is 3 bits with values ​​mapped to the number of time slots {1,2,3,4,5,6,7,8}, but for the NR-U use case, the field is extended by 1 bit to provide 16 possible HARQ feedback timing offset values. One of the 16 values ​​(e.g., 0b1111) can be used as a non-numeric value to indicate pending HARQ feedback transmission until further notice, and the remaining 15 values ​​can be used to provide further HARQ feedback scheduling flexibility.

[0135] In an alternative embodiment, the PDSCH-to-HARQ-timing-indicator remains at 3 bits, but one of the current values ​​(e.g., 0b111) is redefined as a non-numeric value for use in NR-U to indicate pending HARQ feedback transmission until further notice.

[0136] In any of the above embodiments, the modification or extension of the PDSCH-to-HARQ-timing-indicator field and / or the reinterpretation of one of the values ​​as a non-numeric value may be higher layer configurable.

[0137] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Fig.10 The exemplary wireless network shown in FIG. 1 is described in detail.

[0138] Fig.10 An example of a cellular communication system 1000 in which embodiments of the present disclosure may be implemented is shown. For simplicity, Fig.10The wireless network of only depicts network 1006, network nodes 1060 and 1060B, and wireless devices (WD) 1010, 1010B and 1010C. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (such as a landline phone, a service provider, or any other network node or terminal device). In the components shown, network node 1060 and WD 1010 are depicted with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access of wireless devices and / or the use of services provided by or via the wireless network.

[0139] A wireless network may include or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, a specific embodiment of a wireless network may implement a communication standard such as a global system for mobile communications (GSM), a universal mobile telecommunications system (UMTS), a long term evolution (LTE), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standard; a wireless local area network (WLAN) standard such as the IEEE 802.11 standard; and / or any other suitable wireless communication standard such as the Worldwide Interoperability for Microwave Access (Wi Max), Bluetooth, Z-Wave, and / or ZigBee standard.

[0140] The network 1006 may include one or more backhaul networks, core networks, Internet Protocol (IP) networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0141] The network node 1060 and WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and signals via a wired or wireless connection.

[0142] As used herein, a network node refers to a device that is capable of, configured to, set to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio APs), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and new radio (NR) base stations (gNBs)). They can be classified based on the amount of coverage provided by the base stations (or in other words, their transmit power levels), and they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU), sometimes also referred to as a remote radio head (RRH). Such an RRU may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet another example of a network node includes an MSR device such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., a mobile switching center (MSC), a mobility management entity (MME)), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT). As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable and / or provide a wireless device with access to a wireless network or to provide some services to a wireless device that has accessed a wireless network.

[0143] exist Fig.10 In the embodiment, the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig.10The network node 1060 shown in the exemplary wireless network of can represent a device including a combination of the hardware components shown, but some embodiments may include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 1060 are depicted as a single box within a larger box or nested within multiple boxes, in practice, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium 1080 may include multiple separate hard drives and multiple random access memory (RAM) modules).

[0144] Similarly, the network node 1060 can be composed of multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which can have its own corresponding components. In certain scenarios where the network node 1060 includes multiple separate components (e.g., a BTS and a BSC component), one or more separate components can be shared between several network nodes. For example, a single RNC can control multiple node Bs. In this scenario, each unique node B and RNC pair can be regarded as a separate network node in some instances. In some embodiments, the network node 1060 can be configured to support multiple radio access technologies (RATs). In this embodiment, some components can be copied (e.g., separate device-readable media 1080 for different RATs) and some components can be reused (e.g., the same antenna 1062 can be shared by RATs). The network node 1060 can also include multiple groups of various components shown for different wireless technologies (such as GSM, wideband code division multiple access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technology) integrated into the network node 1060. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .

[0145] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 1070 may include, for example, processing the information obtained by the processing circuit 1070 by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing.

[0146] The processing circuit 1070 may include a microprocessor, a controller, a microcontroller, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide the functionality of the network node 1060 alone or in conjunction with other network node 1060 components such as the device readable medium 1080. For example, the processing circuit 1070 may execute instructions stored in the device readable medium 1080 or in a memory within the processing circuit 1070. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC).

[0147] In some embodiments, processing circuitry 1070 may include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074. In some embodiments, RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on separate chips (or chipsets), boards, or units such as a radio unit and a digital unit. In alternative embodiments, part or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on the same chip or chipset, board, or unit.

[0148] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit 1070 executing instructions stored on device-readable medium 1080 or memory within processing circuit 1070. In alternative embodiments, some or all of the functions may be provided by processing circuit 1070 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of those embodiments, processing circuit 1070 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited solely to processing circuit 1070 or other components of network node 1060, but are enjoyed by network node 1060 as a whole, and / or generally by end users and wireless networks.

[0149] The device-readable medium 1080 may include any form of volatile or non-volatile computer-readable memory that stores information, data, and / or instructions that can be used by the processing circuit 1070, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device. The device-readable medium 1080 may store any suitable instructions, data or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 1070 and used by the network node 1060. The device-readable medium 1080 may be used to store any calculations performed by the processing circuit 1070 and / or any data received via the interface 1090. In some embodiments, the processing circuit 1070 and the device-readable medium 1080 may be considered integrated.

[0150] Interface 1090 is used in wired or wireless communication of signaling and / or data between network node 1060, network 1006 and / or WD 1010. As shown, interface 1090 includes port / terminal 1094 to send and receive data, such as sending data to network 1006 and receiving data from network 1006 via wired connection. Interface 1090 also includes radio front-end circuit 1092 that can be coupled to antenna 1062, or in some embodiments, coupled to a part of antenna 1062. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 can be connected to antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can be configured to adjust the signal transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can receive digital data that will be sent outward to other network nodes or WDs via wireless connection. The radio front end circuit 1092 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1098 and / or amplifiers 1096. The radio signal may then be transmitted via the antenna 1062. Similarly, when receiving data, the antenna 1062 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 1092. The digital data may be transmitted to the processing circuit 1070. In some embodiments, the interface may include different components and / or different combinations of components.

[0151] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, but rather the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without a separate radio front end circuit 1092. Similarly, in some embodiments, all or some of the RF transceiver circuit 1072 may be considered part of the interface 1090. In still other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074 as part of a digital unit (not shown).

[0152] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuit 1090 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional sector or flat panel antennas operable to send / receive radio signals, for example, between 2 gigahertz (GHz) and 66GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some instances, using more than one antenna may be referred to as multiple input multiple output (MIMO). In some embodiments, antenna 1062 may be separated from network node 1060 and may be connected to network node 1060 via an interface or port.

[0153] Antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a WD, another network node and / or any other network device. Similarly, antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0154] The power circuit 1087 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 1060 for performing the functions described herein. The power circuit 1087 may receive power from the power supply 1086. The power supply 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the corresponding components (e.g., at the voltage and current levels required by each corresponding component). The power supply 1086 may be included in the power circuit 1087 and / or the network node 1060, or outside the power circuit 1087 and / or the network node 1060. For example, the network node 1060 may be connected to an external power source (e.g., a power outlet) via an input circuit or an interface such as a cable, whereby the external power source provides power to the power circuit 1087. As another example, the power supply 1086 may include a power source in the form of a battery or a battery pack, which is connected to or integrated into the power circuit 1087. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.

[0155] Alternative embodiments of network node 1060 may include Fig.10 , which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1060 may include a user interface device to allow information to be input into the network node 1060 and to allow information to be output from the network node 1060. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 1060.

[0156] As used herein, WD refers to a device that can, is configured to, is set to, and / or is operable to wirelessly communicate with a network node and / or other WD. Unless otherwise specified, the term WD can be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, WD may be configured to send and / or receive information without direct human interaction. For example, WD may be designed to send information to the network on a predetermined schedule when triggered by an internal or external event, or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing the 3G Partnership Project (3GPP) standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in the Internet of Things (loT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband loT (NB-loT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, household or personal appliances (e.g., refrigerators, televisions, etc.), or personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0157] like Fig.10As shown in , WD 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036 and power supply circuit 1037. WD 1010 may include multiple groups of one or more of the various components shown for different wireless technologies supported by WD 1010 (such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technology, to name a few). These wireless technologies can be integrated into the same or different chips or chipsets and other components within WD 1010.

[0158] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 1014. In some alternative embodiments, antenna 1011 can be separated from WD 1010 and can be connected to WD 1010 through an interface or port. Antenna 1011, interface 1014, and / or processing circuit 1020 can be configured to perform any receiving or sending operation described herein as being performed by WD. Any information, data, and / or signal can be received from a network node and / or another WD. In some embodiments, radio front-end circuit and / or antenna 1011 can be considered as an interface.

[0159] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020, and is configured to adjust the signal transmitted between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or a portion of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered as part of the interface 1014. The radio front-end circuit 1012 may receive digital data to be sent out to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via the antenna. Similarly, when receiving data, the antenna 1011 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 1012. The digital data may be transmitted to the processing circuit 1020. In some embodiments, the interface 1014 may include different components and / or different combinations of components.

[0160] The processing circuit 1020 may include a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide the functionality of the WD 1010 alone or in combination with other WD 1010 components such as device readable medium 1030. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 1020 may execute instructions stored in the device readable medium 1030 or in a memory within the processing circuit 1020 to provide the functionality disclosed herein.

[0161] As shown, the processing circuit 1020 includes one or more of the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026. In some embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of the WD 1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into one chip or chipset, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026 can be combined into the same chip or chipset. In some embodiments, the RF transceiver circuit 1022 can be part of the interface 1014. The RF transceiver circuit 1022 can condition the RF signal for the processing circuit 1020.

[0162] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by the processing circuit 1020 executing instructions stored on the device-readable medium 1030, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of those specific embodiments, the processing circuit 1020 may be configured to perform the described functions, regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited solely to the processing circuit 1020 or other components of the WD 1010, but are enjoyed by the WD 1010 as a whole, and / or generally by end users and wireless networks.

[0163] Processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being performed by WD. Such operations performed by processing circuit 1020 may include, for example, processing information obtained by processing circuit 1020 by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 1010, and / or performing one or more operations based on the obtained information or the converted information, and making determinations as a result of the processing.

[0164] Device readable medium 1030 may be operable to store a computer program; software; an application including one or more of logic, rules, codes, tables, etc.; and / or other instructions executable by processing circuit 1020. Device readable medium 1030 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by processing circuit 1120. In some embodiments, processing circuit 1020 and device readable medium 1030 may be considered integrated.

[0165] The user interface device 1032 can provide a component that allows a human user to interact with the WD 1110. This interaction can have multiple forms, such as visual, auditory, tactile, etc. The user interface device 1032 can be operable to generate output to the user and allow the user to provide input to the WD 1010. The type of interaction can vary according to the type of user interface device 1032 installed in the WD 1010. For example, if the WD 1010 is a smart phone, the interaction can be via a touch screen; if the WD 1010 is a smart meter, the interaction can be through a screen that provides use (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1032 can include an input interface, device, and circuit, as well as an output interface, device, and circuit. The user interface device 1032 is configured to allow information to be input into the WD 1010, and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. User interface device 1032 can for example include microphone, proximity sensor or other sensor, key / button, touch display, one or more cameras, universal serial bus (USB) port or other input circuit.User interface device 1132 is also configured to allow information to be output from WD 1110, and allows processing circuit 1020 to output information from WD 1010.User interface device 1032 can for example include loud speaker, display, vibration circuit, USB port, headphone jack or other output circuit.Using one or more input and output interfaces, equipment and circuit of user interface device 1032, WD 1010 can communicate with terminal user and / or wireless network, and allow them to benefit from the functions described herein.

[0166] Auxiliary device 1034 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional communication types such as wired communications, etc. The inclusion and types of components of auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0167] In some embodiments, the power supply 1036 may be in the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. The WD 1010 may also include a power circuit 1037 for delivering power from the power supply 1036 to various parts of the WD 1310 that require power from the power supply 1036 to perform any function described or indicated herein. In some embodiments, the power circuit 1037 may include a power management circuit. Additionally or alternatively, the power circuit 1037 may be operable to receive power from an external power source; in this case, the WD 1010 may be connected to an external power source (such as a power outlet) via an input circuit or an interface such as a power cord. In some embodiments, the power circuit 1037 may also be operable to deliver power from an external power source to the power supply 1036. This may be used, for example, for charging the power supply 1036. The power circuit 1037 may perform any formatting, conversion, or other modification of the power from the power supply 1036 to make the power suitable for each corresponding component of the WD 1010 being powered.

[0168] Fig.11 A wireless communication system is shown represented as a 5G network architecture consisting of core network functions (NFs), where the interaction between any two NFs is represented by point-to-point reference points / interfaces. Fig.11 can be considered as Fig.10 A specific implementation of system 1000.

[0169] From the access side, Fig.11 The 5G network architecture shown in the figure includes multiple user equipment (UE) connected to the radio access network (RAN) or access network (AN) and access and mobility management function (AMF). Typically, R (AN) includes base stations, such as evolved Node B (eNB) or NR base station (gNB). From the core network side, Fig.11 The 5G core NF shown in the figure includes a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM), an AMF, a session management function (SMF), a policy control function (PCF), and an application function (AF).

[0170] The reference point representation of the 5G network architecture is used to develop detailed call flows in specification standardization. The N1 reference point is defined as carrying signaling between the UE and the AMF. The reference points for connecting between the AN and the AMF and between the AN and the UPF are defined as N2 and N3, respectively. There is a reference point N11 between the AMF and the SMF, which means that the SMF is at least partially controlled by the AMF. N4 is used by the SMF and the UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its status to the SMF. Respectively, N9 is a reference point for connection between different UPFs 316, and N14 is a reference point for connection between different AMFs. Since the PCF applies policies to the AMF and SMP, respectively, N15 and N7 are defined. The AMF requires N12 to perform authentication of the UE. Since the AMF and the SMF require subscription data of the UE, N8 and N10 are defined.

[0171] The 5G core network is designed to separate the user plane and the control plane. The user plane carries user traffic, while the control plane carries signaling in the network. Fig.11 In the NF, UPF is in the user plane, while all other NFs (i.e., AMF, SMF, PCF, AF, AUSF, and UDM) are in the control plane. Separating the user plane and the control plane ensures that the resources of each plane are scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. In this architecture, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network for some applications that require low latency.

[0172] The core 5G network architecture consists of modular functions. For example, AMF and SMF are independent functions in the control plane. Separating AMF and SMF allows for separate evolution and expansion. Other control plane functions (such as PCF and AUSF) can be Fig.11 The modular functional design enables the 5G core network to flexibly support various services.

[0173] Each NF interacts directly with another NF. An intermediate function can be used to route messages from one NF to another. In the control plane, a set of interactions between two NFs is defined as a service, so its reuse is possible. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0174] Fig.12 Shows the use of service-based interfaces between NFs in the control plane instead of using Fig.11 The 5G network architecture uses point-to-point reference points / interfaces in the 5G network architecture. Fig.11 The NF described corresponds to Fig.12The services provided by NF to other authorized NFs can be opened to authorized NFs through service-based interfaces. Fig.12 In the NF, the service-based interface is represented by the letter "N" followed by the name of the NF, for example, Namf is used for the service-based interface of AMF, Nsmf is used for the service-based interface of SMF, etc. Fig.12 The Network Open Function (NEF) and Network Repository Function (NRF) in Fig.11 However, it should be clear that although Fig.11 It is not explicitly stated, but Fig.11 All NFs depicted in the Fig.12 The NEF and NRF interact.

[0175] exist Fig.11 and 12 Some characteristics of the NF shown in can be described in the following way. AMF provides UE-based authentication, authorization, mobility management, etc. Even UEs using multiple access technologies are basically connected to a single AMF because the AMF is independent of the access technology. SMF is responsible for session management and assigns an Internet Protocol (IP) address to the UE. It also selects and controls the UPF for data transmission. If the UE has multiple sessions, a different SMF can be assigned to each session to manage them separately, and different functions can be provided per session. AF provides information about packet flows to the PCF responsible for policy control in order to support quality of service (QoS). Based on this information, the PCF determines policies on mobility and session management to enable the AMF and SMF to operate correctly. AUSF supports authentication functions for UEs, etc., and therefore stores data for authenticating UEs, etc., while UDM stores subscription data for UEs. The data network (DN) is not part of the 5G core network, which provides Internet access or operator services, etc.

[0176] NFs may be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on a suitable platform (e.g., cloud infrastructure).

[0177] Fig.13An embodiment of a UE according to the various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in terms of a human user who owns and / or operates the associated equipment. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user but may not be associated with a specific human user or was not originally associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with the benefit of a user or may be operated for the benefit of a user (e.g., a smart meter). UE 1300 may be any UE identified by 3GPP, including NB-loT UE, MTC UE, and / or enhanced MTC (eMTC) UE. As Fig.13 As shown in , UE 1300 is an example of a WD configured to communicate according to one or more communication standards promulgated by 3GPP, such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE can be used interchangeably. Therefore, although Fig.13 The reference is to UE, but the components discussed in this article are also applicable to WD and vice versa.

[0178] exist Fig.13 In the embodiment, UE 1300 includes a processing circuit 1301, which is operably coupled to an input / output interface 1305, an RF interface 1309, a network connection interface 1311, a memory 1315 including a RAM 1317, a ROM 1319, and a storage medium 1321, a communication subsystem 1331, a power supply 1333, and / or any other components or any combination thereof. The storage medium 1321 includes an operating system 1323, an application 1325, and data 1327. In some embodiments, the storage medium 1321 may include other similar types of information. Some UEs may use Fig.13 All components shown in the UE may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. Further, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0179] exist Fig.13In the embodiment of the present invention, the processing circuit 1301 can be configured to process computer instructions and data. The processing circuit 1301 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., using discrete logic, FPGA, ASIC, etc.); programmable logic and suitable firmware; one or more stored programs, general-purpose processors such as microprocessors or DSPs and suitable software; or any combination of the above. For example, the processing circuit 1301 may include two CPUs. The data may be information in a form suitable for use by a computer.

[0180] In the described embodiment, the input / output interface 1305 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1300 may be configured to use an output device via the input / output interface 1305. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1300 and output from the UE 1300. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1300 may be configured to use an input device via the input / output interface 1305 to allow a user to capture information into the UE 1300. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0181] exist Fig.13In the embodiment of the present invention, the RF interface 1309 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface 1311 can be configured to provide a communication interface to the network 1343A. The network 1343A can include a wired and / or wireless network, such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1343A can include a WiFi network. The network connection interface 1311 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols such as Ethernet, transmission control protocol (TCP) / IP, synchronous optical network (SONET), asynchronous transfer mode (ATM), etc. The network connection interface 1311 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately.

[0182] RAM 1317 can be configured to interface with processing circuit 1301 via bus 1302 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 1319 can be configured to provide computer instructions or data to processing circuit 1401. For example, ROM 1319 can be configured to store constant low-level system code or data for basic system functions such as basic input and output (I / O) stored in non-volatile memory, startup, or receiving keystrokes from a keyboard. Storage medium 1321 can be configured to include a memory such as RAM, ROM, programmable ROM (PROM), erasable PROM (EPROM), electric EPROM (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 1421 can be configured to include operating system 1323, application 1325 such as a web browser application, a control or gadget engine or another application, and data file 1327. The storage medium 1321 may store any one of various operating systems or a combination of operating systems for use by the UE 1300 .

[0183] The storage medium 1321 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro DIMM SDRAM, a smart card memory such as a subscriber identity module (SIM) or a removable user identity (RUIM) module, other memory, or any combination thereof. The storage medium 1321 may allow the UE 1300 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 1321, which may include a device-readable medium.

[0184] exist Fig.13 In the embodiment, the processing circuit 1301 can be configured to communicate with the network 1343B using the communication subsystem 1331. The network 1343A and the network 1343B can be the same network or different networks. The communication subsystem 1331 can be configured to include one or more transceivers for communicating with the network 1343B. For example, the communication subsystem 1331 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication such as another WD, UE or base station of a radio access network (RAN) according to one or more communication protocols such as IEEE 802.13, code division multiple access (CDMA), WCDMA, GSM, LTE, universal terrestrial radio access network (UTRAN), WiMax, etc. Each transceiver can include a transmitter 1333 and / or a receiver 1335 to respectively implement the functions of a transmitter or a receiver suitable for a RAN link (e.g., frequency allocation, etc.). Further, the transmitter 1333 and receiver 1335 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0185] In the illustrated embodiment, the communication functions of the communication subsystem 1331 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 1331 may include cellular communication, WiFi communication, Bluetooth communication, and GPS communication. The network 1343B may cover wired and / or wireless networks, such as LAN, WAN, computer network, wireless network, telecommunication network, another similar network, or any combination thereof. For example, the network 1343B may be a cellular network, a WiFi network, and / or a near-field network. The power supply 1313 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1300.

[0186] The features, benefits and / or functions described herein may be implemented in one of the components of UE 1300, or may be divided between multiple components of UE 1300. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1331 may be configured to include any component described herein. Further, the processing circuit 1301 may be configured to communicate with any such component via bus 1302. In another example, any such component may be represented by program instructions stored in a memory that perform corresponding functions described herein when executed by the processing circuit 1301. In another example, the functions of any such component may be divided between the processing circuit 1301 and the communication subsystem 1331. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0187] Fig.14 1400 is a schematic block diagram showing a virtualized environment 1400 in which functions implemented by some embodiments may be virtualized. In the current context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a WD, or any other type of communication device) or a component thereof, and involves an implementation in which at least a portion of a function is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0188] In some embodiments, some or all of the functionality described herein may be implemented as virtual components performed by one or more virtual machines implemented in one or more virtual environments 1400 hosted by one or more hardware nodes 1430. Further, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0189] Functionality may be implemented by one or more applications 1420 (alternatively referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some functionality, features, and / or benefits of some embodiments disclosed herein. Applications 1420 run in a virtualized environment 1500 that provides hardware 1430 including processing circuitry 1460 and memory 1490. Memory 1490 contains instructions 1495 executable by processing circuitry 1460, whereby applications 1420 are operable to provide one or more features, benefits, and / or functionality disclosed herein.

[0190] The virtualized environment 1400 includes general-purpose or special-purpose network hardware devices 1430, which include a set of one or more processors or processing circuits 1460, which can be commercial off-the-shelf (COTS) processors, special-purpose ASICs, or any other type of processing circuits, including digital or analog hardware components or special-purpose processors. Each hardware device may include a memory 1490-1, which may be a non-permanent memory for temporarily storing instructions 1495 or software executed by the processing circuit 1460. Each hardware device may include one or more network interface controllers (NICs) 1470, also known as network interface cards, which include a physical network interface 1480. Each hardware device may also include a non-transitory, permanent, machine-readable storage medium 1490-2 in which software 1495 and / or instructions executable by the processing circuit 1460 are stored. The software 1495 may include any type of software, including software for instantiating one or more virtualization layers 1450 (also referred to as a hypervisor), software for executing virtual machines 1440, and software that enables them to perform functions, features and / or benefits related to some of the embodiments described herein.

[0191] The virtual machine 1440 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 1450 or hypervisor. Different embodiments of instances of the virtual device 1420 can be implemented on one or more virtual machines 1440 and can be implemented in different ways.

[0192] During operation, processing circuit 1460 executes software 1495 to instantiate a hypervisor or virtualization layer 1450 , which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1450 may present a virtual operating platform that appears to networked hardware to virtual machine 1440 .

[0193] like Fig.14 As shown in , hardware 1430 can be an independent network node with common or specific components. Hardware 1430 can include antenna 14225, and some functions can be implemented via virtualization. Alternatively, hardware 1430 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), where multiple hardware nodes work together and are managed via management and orchestration (MANO) 14100 (which oversees the lifecycle management of application 1420 with other programs).

[0194] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate multiple network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices that can be located in data centers and CPEs.

[0195] In the context of NFV, a virtual machine 1440 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtual machine. Each virtual machine 1440 and the portion of the hardware 1430 that executes the virtual machine 1440, i.e., the hardware dedicated to the virtual machine 1440 and / or the hardware shared by the virtual machine 1440 with other virtual machines 1440, form a separate virtual network element (VNE).

[0196] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 1440 on top of the hardware networking infrastructure 1430 and corresponds to Fig.14 Application 1420.

[0197] In some embodiments, one or more radio units 14200, each including one or more transmitters 14220 and one or more receivers 14210, may be coupled to one or more antennas 14225. The radio unit 14200 may communicate directly with the hardware node 1430 via one or more suitable networks, and may be used in conjunction with virtual components to provide radio functionality to a virtual node such as a radio access node or base station.

[0198] In some embodiments, some signaling may be implemented using control system 14230 , which may alternatively be used for communication between hardware node 1430 and radio unit 14200 .

[0199] Fig.15 A communication system according to some embodiments of the present disclosure is shown. Fig.15 According to an embodiment, the communication system includes a telecommunication network 1510 such as a 3GPP type cellular network, which includes an access network 1511 such as a RAN and a core network 1414. The access network 1511 includes a plurality of base stations 1512A, 1512B, 1512C, such as NB, eNB, gNB or other types of wireless APs, each of which defines a corresponding coverage area 1513A, 1513B, 1513C. Each base station 1512A, 1512B, 1512C may be connected to the core network 1514 via a wired or wireless connection 1515. A first UE 1591 located in the coverage area 1513C is configured to be wirelessly connected to the corresponding base station 1512C or to be paged by the corresponding base station 1512C. A second UE 1592 located in the coverage area 1513A may be wirelessly connected to the corresponding base station 1512A. Although multiple UEs 1591 , 1592 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connecting to the corresponding base station 1512 .

[0200] The telecommunications network 1510 itself is connected to a host computer 1530, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1530 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 1521 and 1522 between the telecommunications network 1510 and the host computer 1530 may extend directly from the core network 1514 to the host computer 1530, or may be connected via an optional intermediate network 1520. The intermediate network 1520 may be one or a combination of more than one of a public, private, or managed network; the intermediate network 1520 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1520 may include two or more sub-networks (not shown).

[0201] Fig.15The communication system as a whole implements a connection between the connected UEs 1591, 1592 and the host computer 1530. The connection can be described as an over-the-top (OTT) connection 1550. The host computer 1530 and the connected UEs 1591, 1592 are configured to use the access network 1511, the core network 1514, any intermediate networks 1520, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 1550. The OTT connection 1550 can be transparent in the sense that the participating communication devices through which the OTT connection 1550 passes are unaware of the routes of the uplink and downlink communications. For example, the base station 1512 may not or need not be informed of the past routes of incoming downlink communications, wherein the incoming downlink communications have data that originates from the host computer 1530 to be forwarded (e.g., handed over) to the connected UE 1591. Similarly, base station 1512 need not be aware of future routes of outgoing uplink communications originating from UE 1591 to host computer 1530 .

[0202] Fig.16 A communication system according to some embodiments of the present disclosure is shown. Fig.16 To describe the exemplary implementation of the UE, base station and host computer discussed in the previous paragraphs according to the embodiment. In the communication system 1600, the host computer 1610 includes hardware 1615, which includes a communication interface 1616 configured to establish and maintain a wired or wireless connection with different communication devices in the communication system 1600. The host computer 1610 also includes a processing circuit 1618, which may have storage and / or processing capabilities. In particular, the processing circuit 1618 may include one or more programmable processors, ASICs, FPGAs, or a combination of these components (not shown) suitable for executing instructions. The host computer 1610 also includes software 1611, which is stored in or accessible to the host computer 1610 and can be executed by the processing circuit 1618. Software 1611 includes a host application 1612. The host application 1612 may be operable to provide services to a remote user, such as a UE 1630 connected via an OTT connection 1650 terminating at the UE 1630 and the host computer 1610. In providing services to the remote user, the host application 1612 may provide user data sent using the OTT connection 1650.

[0203] The communication system 1600 also includes a base station 1620, which is provided in the telecommunication system and includes hardware 1625 that enables it to communicate with the host computer 1610 and the UE 1630. The hardware 1625 may include a communication interface 1626 for establishing and maintaining a wired or wireless connection with different communication devices in the communication system 1600, and a communication interface 1626 for establishing and maintaining a connection with at least a network located in a coverage area (not in a coverage area) served by the base station 1620. Fig.16 16). The communication interface 1626 may be configured to facilitate a connection 1660 to the host computer 1610. The connection 1660 may be direct, or it may pass through a core network (not shown in FIG. 16) in the telecommunications system. Fig.16 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1625 of the base station 1620 also includes a processing circuit 1628, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these components (not shown) suitable for executing instructions. The base station 1620 also has software 1621 that is stored internally or accessible via an external connection.

[0204] The communication system 1600 also includes the UE 1630 already mentioned. Its hardware 1635 may include a radio interface 1637, which is configured to establish and maintain a wireless connection 1670 with a base station serving the coverage area where the UE 1630 is currently located. The hardware 1635 of the UE 1630 also includes a processing circuit 1638, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these components (not shown) suitable for executing instructions. The UE 1630 also includes software 1631, which is stored in the UE 1630 or can be accessed by it and can be executed by the processing circuit 1638. The software 1631 includes a client application 1632. The client application 1632 can be operated with the support of the host computer 1610 to provide services to human or non-human users via the UE 1630. In the host computer 1610, the executing host application 1612 can communicate with the executing client application 1632 via the OTT connection 1650 that terminates at the UE 1630 and the host computer 1610. When providing services to users, the client application 1632 can receive request data from the host application 1612 and provide user data in response to the request data. The OTT connection 1650 can transmit both the request data and the user data. The client application 1632 can interact with the user to generate the user data it provides.

[0205] Notice, Fig.16The host computer 1610, base station 1620 and UE 1630 shown in FIG. 1 can be respectively connected to Fig.15 The host computer 1530, one of the base stations 1512A, 1512B, 1512C, and one of the UEs 1591, 1592 may be similar or identical. That is, the internal workings of these entities may be similar to Fig.16 As shown in , and independently, the surrounding network topology can be Fig.15 Those in .

[0206] exist Fig.16 In the figure, the OTT connection 1650 has been abstractly drawn to illustrate the communication between the host computer 1610 and the UE 1630 via the base station 1620, without explicitly mentioning any intermediate devices and the precise message routing via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 1630 or the service provider operating the host computer 1610, or both. When the OTT connection 1650 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0207] The wireless connection 1670 between the UE 1630 and the base station 1620 is in accordance with the teachings of the embodiments described in the present disclosure. One or more of the various embodiments may improve the performance of OTT services provided to the UE 1630 using the OTT connection 1650, where the wireless connection 1670 constitutes the last segment. More precisely, the teachings of these embodiments may improve the flexibility of PDSCH-to-HARQ-timing compared to conventional NR networks.

[0208] For the purpose of monitoring data rate, delay, and other factors that one or more embodiments improve, a measurement process may be provided. There may also be an optional network function for reconfiguring the OTT connection 1650 between the host computer 1610 and the UE 1630 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 1650 may be implemented in the software 1611 and hardware 1615 of the host computer 1610 or the software 1631 and hardware 1635 of the UE 1630, or both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1650 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above, or providing the value of other physical quantities (the software 1611, 1631 may calculate or estimate the monitoring quantity based on the other physical quantities). The reconfiguration of the OTT connection 1650 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 1620, and it may be unknown or imperceptible to the base station 1620. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 1610 measurements of throughput, propagation time, latency, etc. These measurements may be implemented while software 1611 and 1631 monitor propagation time, errors, etc., causing messages (particularly empty messages or "dummy" messages) to be sent using OTT connection 1650.

[0209] Fig.17 is a flow chart showing a method implemented in a communication system according to some embodiments of the present disclosure. The communication system includes a host computer, a base station and a UE, which can be reference Fig.15 and Fig.16 For the sake of simplicity of this disclosure, only the Fig.17 . In step 1710, the host computer provides user data. In sub-step 1711 of step 1710 (which may be optional), the host computer provides the user data by executing a host application. In step 1720, the host computer initiates a transmission to the UE carrying the user data. In step 1730 (which may be optional), in accordance with the teachings of the embodiments described in the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0210] Fig.18is a flow chart showing a method implemented in a communication system according to some embodiments of the present disclosure. The communication system includes a host computer, a base station and a UE, which can be reference Fig.15 and Fig.16 For the sake of simplicity of this disclosure, only the Fig.18 . In step 1810 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1820, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described in the present disclosure, the transmission may pass through a base station. In step 1830 (which may be optional), the UE receives the user data carried in the transmission.

[0211] Fig.19 is a flow chart showing a method implemented in a communication system according to some embodiments of the present disclosure. The communication system includes a host computer, a base station and a UE, which can be reference Fig.15 and Fig.16 For the sake of simplicity of this disclosure, only the Fig.19 . In step 1910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1920, the UE provides user data. In sub-step 1921 of step 1920 (which may be optional), the UE provides the user data by executing a client application. In sub-step 1911 of step 1910 (which may be optional), the UE executes a client application, which provides the user data in response to the received input data provided by the host computer. When providing the user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing the user data, in sub-step 1930 (which may be optional), the UE initiates the transmission of the user data to the host computer. In step 1940 of the method, according to the teachings of the embodiments described in the present disclosure, the host computer receives the user data sent from the UE.

[0212] Fig. 20 is a flow chart showing a method implemented in a communication system according to some embodiments of the present disclosure. The communication system includes a host computer, a base station and a UE, which can be reference Fig.15 and Fig.16 For the sake of simplicity of this disclosure, only the Fig. 20In step 2010 (which may be optional), in accordance with the teachings of the embodiments described in the present disclosure, the base station receives user data from the UE. In step 2020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0213] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuits and other digital hardware, wherein the processing circuits may include one or more microprocessors or microcontrollers, and other digital hardware may include DSPs, dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, and the memory may include one or more types of memory, such as ROM, RAM, buffer memory, flash memory device, optical memory, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function.

[0214] The term "unit" may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output, and / or display functions, etc. such as those described herein.

[0215] Exemplary Embodiments

[0216] Group A Embodiment - Wireless Device Method

[0217] 1. A method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, performed by a wireless device, the method comprising: receiving a first DCI associated with a first DL data transmission, the first DCI comprising a non-digital PDSCH-to-HARQ-timing-indicator; receiving the first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator indicating a time position of the HARQ feedback associated with the second DL data transmission; setting the position of the HARQ feedback associated with the first DL data transmission to be the same as the position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set position.

[0218] 2. A method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, performed by a wireless device, the method comprising: receiving a first DCI associated with a first DL data transmission of a first PDSCH group, the first DCI comprising a non-digital PDSCH-to-HARQ-timing-indicator; receiving the first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator indicating a location of HARQ feedback associated with the second DL data transmission; determining that the second DL data transmission belongs to the same PDSCH group as the first DL data transmission; setting the location of the HARQ feedback associated with the first DL data transmission to be the same as the location of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set location.

[0219] 3. A method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, performed by a wireless device, the method comprising: receiving a first DCI associated with a first DL data transmission of a first PDSCH group, the first DCI comprising a digital PDSCH-to-HARQ-timing-indicator; determining that a position of HARQ feedback associated with the first DL data transmission indicated by the digital PDSCH-to-HARQ-timing-indicator is too close to the first DL data transmission; and in response to the determination, not sending the HARQ associated with the first DL data transmission at the indicated HARQ transmission time.

[0220] 4. The method according to embodiment 3 also includes: providing an indication on the PUCCH at the indicated HARQ transmission time, which notifies the gNB that the HARQ feedback is postponed.

[0221] Group B Embodiment - gNB Method

[0222] 5. A method performed by a gNB for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, the method comprising: sending a first DCI associated with a first DL data transmission to a first UE, the first DCI comprising a non-digital PDSCH-to-HARQ-timing-indicator; sending a second DCI associated with a second DL data transmission to the first UE, the second DCI comprising a digital PDSCH-to-HARQ-timing-indicator and at least one of: at least one HARQ process ID; an NDI value; at least one PDSCH group ID; a corresponding DAI; and / or a trigger bit.

[0223] Group C Embodiment - Device

[0224] 6. A wireless device for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, the wireless device comprising: a processing circuit configured to perform any step of any one of Group A embodiments; and a power circuit configured to supply power to the wireless device.

[0225] 7. A base station for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, the base station comprising: a processing circuit configured to perform any step of any one of Group B embodiments; and a power supply circuit configured to supply power to the base station.

[0226] 8. A user equipment UE, for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator, the UE comprising: an antenna, which is configured to send and receive wireless signals; a radio front-end circuit, connected to the antenna and the processing circuit and configured to adjust the signal transmitted between the antenna and the processing circuit; the processing circuit, which is configured to perform any step of any one of the embodiments of Group A; an input interface, connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface, connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery, connected to the processing circuit and configured to supply power to the UE.

[0227] Group D Embodiment—System (with Host Computer)

[0228] 9. A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; a communication interface configured to forward the user data to a cellular network for transmission to a user equipment UE, wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps described in any one of the embodiments of group B.

[0229] 10. The communication system according to the previous embodiment further includes a base station.

[0230] 11. The communication system according to the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0231] 12. The communication system according to the first three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the UE includes a processing circuit configured to execute a client application associated with the host application.

[0232] 13. A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: providing user data at the host computer; and initiating transmission at the host computer to carry the user data to the UE via a cellular network including the base station, wherein the base station performs any step of any one of the embodiments of group B.

[0233] 14. The method according to the previous embodiment further includes: sending user data at the base station.

[0234] 15. The method according to the first two embodiments, wherein the user data is provided by executing a host application at a host computer, the method further comprising: executing a client application associated with the host application at a UE.

[0235] 16. A user equipment UE, configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the method described in the first three embodiments.

[0236] 17. A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; a communication interface configured to forward the user data to a cellular network for transmission to a user equipment UE, wherein the UE comprises a radio interface and a processing circuit, and the components of the UE are configured to perform any of the steps described in any one of the embodiments of group A.

[0237] 18. The communication system according to the previous embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0238] 19. The communication system according to the first two embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the processing circuit of the UE is configured to execute a client application associated with the host application.

[0239] 20. A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: providing user data at the host computer; and initiating transmission of the user data to the UE via a cellular network including the base station at the host computer, wherein the UE performs any step of any one of the embodiments of group A.

[0240] 21. The method according to the previous embodiment further includes: at the UE, receiving user data from the base station.

[0241] 22. A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment UE to a base station, wherein the UE comprises a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any step of any one of the embodiments of Group A.

[0242] 23. The communication system according to the previous embodiment further includes a UE.

[0243] 24. The communication system according to the first two embodiments, further comprising a base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0244] 25. The communication system according to the first three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0245] 26. A communication system according to the first four embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide request data; and the processing circuit of the UE is configured to execute a client application associated with the host application in response to the request data to provide user data.

[0246] 27. A method implemented in a communication system comprising a host computer, a base station and a user equipment UE, the method comprising: receiving, at the host computer, user data sent from the UE to the base station, wherein the UE performs any step of any one of Group A embodiments.

[0247] 28. The method of the preceding embodiment further comprising providing user data to the base station at the UE.

[0248] 29. The method according to the previous two embodiments further comprises: executing a client application at the UE to provide user data to be sent; and executing a host application associated with the client application at the host computer.

[0249] 30. The method according to the first three embodiments further includes: executing a client application at the UE; receiving input data for the client application at the UE, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be sent is provided by the client application in response to the input data.

[0250] 31. A communication system comprising a host computer, the host computer comprising a communication interface, which is configured to receive user data originating from a transmission from a user equipment UE to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any of the steps described in any one of Group B embodiments.

[0251] 32. According to the communication system described in the previous embodiment, it also includes a base station.

[0252] 33. The communication system according to the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0253] 34. The communication system according to the first two embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0254] 35. A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: at the host computer, receiving from the base station user data originating from a transmission that the base station has received from the UE, wherein the UE performs any step of any one of the embodiments of group A.

[0255] 36. The method according to the previous embodiment further includes: receiving user data from the UE at the base station.

[0256] 37. The communication system according to the first two embodiments further comprises: at the base station, initiating transmission of the received user data to the host computer.

[0257] According to some aspects of the present disclosure, a method for setting HARQ timing for a PDSCH with a pending PDSCH-to-HARQ-timing-indicator performed by a wireless device includes: receiving a first DCI associated with a first DL data transmission, the first DCI including a non-digital PDSCH-to-HARQ-timing-indicator; receiving the first DL data transmission; determining HARQ feedback for the first DL data transmission; receiving a second DCI associated with a second DL data transmission, the second DCI including a digital PDSCH-to-HARQ-timing-indicator indicating a time position of the HARQ feedback associated with the second DL data transmission; setting the position of the HARQ feedback associated with the first DL data transmission to be the same as the position of the HARQ feedback associated with the second DL data transmission; and sending the HARQ feedback associated with the first DL data transmission at the set position.

[0258] Abbreviations

[0259] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between these abbreviations, priority should be given to how the abbreviation is used above. If listed multiple times below, the first listing should take precedence over any subsequent listing.

[0260] 2G Second Generation

[0261] 3G Third Generation

[0262] ·3GPP Third Generation Partnership Project

[0263] 4G Fourth Generation

[0264] 5G fifth generation

[0265] AC

[0266] ACK

[0267] AF application function

[0268] AMF core access and mobility management functions

[0269] AN Access Network

[0270] AP Access Point

[0271] ASIC Application-Specific Integrated Circuit

[0272] ATM Asynchronous Transfer Mode

[0273] AUSF authentication server function

[0274] BS Base Station

[0275] BSC Base Station Controller

[0276] BTS Base Transceiver Station

[0277] CA Carrier Aggregation

[0278] CBG Code Block Group

[0279] CD

[0280] CDMA Code Division Multiple Access

[0281] COT Channel Occupancy Time

[0282] ·COTS Commercial Off-the-Shelf

[0283] CPE

[0284] CPU Central Processing Unit

[0285] D2D Device to Device

[0286] DAI Downlink Allocation Indicator

[0287] DAS Distributed Antenna System

[0288] DC Direct current

[0289] DCI Downlink Control Information

[0290] DIMM Dual In-line Memory Module

[0291] DL Downlink

[0292] DN Data Network

[0293] DSP Digital Signal Processor

[0294] DVD Digital Video Disc

[0295] EEPROM Electrically Erasable Programmable Read-Only Memory

[0296] eMTC Enhanced Machine Type Communication

[0297] eNB Evolved Node B

[0298] EPROM Erasable Programmable Read Only Memory

[0299] E-SMLC Evolved Service Mobile Location Center

[0300] FPGA Field Programmable Gate Array

[0301] GHz Gigahertz

[0302] gNB New Radio Base Station

[0303] GPS Global Positioning System

[0304] GSM Global System for Mobile Communications

[0305] HARQ Hybrid Automatic Repeat Request

[0306] ·HDDS Holographic Digital Data Storage

[0307] HD-DVD High-density digital versatile disc

[0308] I / O input and output

[0309] IoT

[0310] IP Internet Protocol

[0311] kHz Kilohertz

[0312] L1 Layer 1

[0313] LAN

[0314] LBT Listen before speaking

[0315] ·LEE Laptop Embedded Device

[0316] LME Laptop Mounted Device

[0317] LTE Long Term Evolution

[0318] M2M Machine to Machine

[0319] MANO management and orchestration

[0320] MCE Multi-cell / multicast coordination entity

[0321] MDT Minimized Drive Test

[0322] MIMO Multiple Input Multiple Output

[0323] MME Mobility Management Entity

[0324] MSC Mobile Switching Center

[0325] MSR Multi-Standard Radio

[0326] MTC Machine Type Communication

[0327] NACK Negative Acknowledgement

[0328] NB-IoT Narrowband Internet of Things

[0329] NDI New Data Indicator

[0330] NEF network open function

[0331] NFV Network Function Virtualization

[0332] NIC Network Interface Controller

[0333] NR New Radio

[0334] NRF Network Function Repository function

[0335] NR-U New Radio in unlicensed spectrum

[0336] NSSF network slice selection function

[0337] O&M Operation and Maintenance

[0338] OFDM Orthogonal Frequency Division Multiplexing

[0339] OSS Operation Support System

[0340] OTT Over the Top

[0341] PCF policy control function

[0342] PDA Personal Digital Assistant

[0343] PDCCH Physical Downlink Control Channel

[0344] PDSCH Physical Downlink Shared Channel

[0345] PROM Programmable Read Only Memory

[0346] PSTN Public Switched Telephone Network

[0347] PUCCH Physical Uplink Control Channel

[0348] QoS Quality of Service

[0349] RAID Redundant Array of Independent Disks

[0350] RAM Random Access Memory

[0351] RAN Radio Access Network

[0352] RAT Radio Access Technology

[0353] RF

[0354] RNC Radio Network Controller

[0355] ROM Read Only Memory

[0356] RRC Radio Resource Control

[0357] RRH Remote Radio Head

[0358] RRU Remote Radio Unit

[0359] RTT Round Trip Time

[0360] RUIM removable user ID

[0361] SDRAM Synchronous Dynamic Random Access Memory

[0362] SIM Subscriber Identity Module

[0363] SMF session management function

[0364] ·SOC System on Chip

[0365] SON self-organizing network

[0366] SONET Synchronous Optical Network

[0367] SPS Semi-Persistent Scheduling

[0368] TB transmission block

[0369] TCP Transmission Control Protocol

[0370] TDD Time Division Duplex

[0371] UCI Uplink Control Information

[0372] UDM unified data management

[0373] UE User Equipment

[0374] UL Uplink

[0375] UMTS Universal Mobile Telecommunications System

[0376] USB Universal Serial Bus

[0377] UTRAN Universal Terrestrial Radio Access Network

[0378] V2I Vehicle to Infrastructure

[0379] V2V Vehicle to Vehicle

[0380] V2X Vehicle to Everything

[0381] VMM Virtual Machine Monitor

[0382] VNE Virtual Network Element

[0383] VNF Virtual Network Function

[0384] ·VoIP Voice over Internet Protocol

[0385] WAN Wide Area Network

[0386] ·WCDMA Wideband Code Division Multiple Access

[0387] WD Wireless Devices

[0388] WiMax Worldwide Interoperability for Microwave Access

[0389] WLAN Wireless Local Area Network

[0390] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to fall within the scope of the concepts disclosed herein.

Claims

1. A method for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH) performed by a wireless device, the method comprising: receiving (600, 700) first downlink control information (DCI) (508) associated with a first downlink (DL) data transmission (510), the first DCI (508) comprising a PDSCH to HARQ timing indicator having a first value, the first value indicating that HARQ feedback for the first DL data transmission will occur once the wireless device has received a DCI comprising a digital PDSCH to HARQ timing indicator having a value different from the first value; receiving (602, 702) the first DL data transmission (510); determining (604, 704) HARQ feedback for the first DL data transmission (510); receiving (606, 706) a second DCI (514) associated with a second DL data transmission (516), the second DCI (514) comprising a digital PDSCH-to-HARQ timing indicator indicating a time position of HARQ feedback associated with the second DL data transmission; Setting (608, 710) a time position of HARQ feedback associated with the first DL data transmission to be the same as a time position of HARQ feedback associated with the second DL data transmission; and At the set time position, HARQ feedback associated with the first DL data transmission (522) is sent (610, 712).

2. The method according to claim 1, wherein: Receiving (606) the second DCI (514) includes: receiving information indicating the number of HARQ processes that should be reported, the number including all pending PDSCHs and all PDSCHs having a DCI including a PDSCH to HARQ timing indicator having the first value since the last PDSCH having a DCI including a digital PDSCH to HARQ timing indicator having a value different from the first value.

3. The method according to claim 2, wherein: Receiving the information indicating the number of HARQ processes that should be reported comprises receiving a downlink allocation indicator, DAI.

4. The method according to any one of claims 1 to 3, further comprising: After receiving (606, 706) the second DCI associated with the second DL data transmission, determining (708) that the second DL data transmission belongs to the same PDSCH group as the first DL data transmission, Wherein, when it is determined that the second DL data transmission is indicated to belong to the same PDSCH group as the first DL data transmission, the following operations are performed: the time position of the HARQ feedback associated with the first DL data transmission is set (608, 710) to be the same as the time position of the HARQ feedback associated with the second DL data transmission, and the HARQ feedback associated with the first DL data transmission (522) is sent (610, 712) at the set time position.

5. The method according to any one of claims 1 to 3, wherein: Receiving (606, 706) the second DCI (514) associated with the second DL data transmission (516) includes receiving a user equipment (UE) specific DCI sent on a physical downlink control channel (PDCCH), the UE specific DCI including the PDSCH to HARQ timing indicator.

6. The method according to claim 5, wherein: The UE-specific DCI also includes a HARQ process identifier ID.

7. The method according to claim 5, wherein: The UE-specific DCI also includes a new data indicator NDI value corresponding to the HARQ process ID.

8. The method according to claim 5, wherein: The UE-specific DCI also includes a PDSCH group ID and a corresponding downlink allocation indicator DAI.

9. The method according to claim 5, wherein: The UE-specific DCI further includes a triggering bit indicating that the PDSCH to HARQ timing indicator is applicable to all PDSCHs for which the PDSCH to HARQ timing indicator has the first value.

10. The method according to claim 9, wherein: The trigger bit includes a portion of the DCI that is scheduling the PDSCH.

11. The method according to claim 9, wherein: The trigger bit includes a portion of the DCI that is not scheduling the PDSCH.

12. The method according to any one of claims 1 to 3, wherein: The PDSCH-to-HARQ timing indicator having the first value is a digital PDSCH-to-HARQ timing indicator indicating that HARQ feedback for the first DL data transmission should be delayed until the wireless device has received a DCI including a digital PDSCH-to-HARQ timing indicator having a value different from the first value.

13. The method according to claim 12, wherein: The first value comprises an existing PDSCH to HARQ timing indicator value that has been remapped from indicating a delay value to indicating that HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH to HARQ timing indicator having a value different from the first value.

14. The method according to claim 13, wherein: Prior to receiving the first DCI, the wireless device receives an instruction to remap the existing PDSCH to HARQ timing indicator value from indicating a delay value to indicating that HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH to HARQ timing indicator having a value different from the first value.

15. The method according to claim 12, wherein: The first value comprises additional bits that have been added to an existing PDSCH to HARQ timing indicator value bit field in the DCI.

16. A method for setting hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH), performed by a base station, the method comprising: determining PDSCH to HARQ timing for an upcoming downlink DL data transmission to a user equipment UE; determining that HARQ feedback for the upcoming DL data transmission should be delayed by the UE until further notification from the base station; sending first downlink control information (DCI) associated with the upcoming DL data transmission to a UE, the first DCI comprising a PDSCH-to-HARQ timing indicator having a first value for indicating to the UE that HARQ feedback for the upcoming DL data transmission should be delayed until further notification from the base station; as well as A second DCI is sent to the UE as the further notification, the second DCI being associated with a second DL data transmission and comprising a digital PDSCH to HARQ timing indicator.

17. The method according to claim 16, wherein: Determining that the HARQ feedback for the upcoming DL data transmission should be delayed by the UE until further notification from the base station includes determining that a processing delay from an end of the upcoming DL data transmission to a start of the HARQ feedback opportunity is less than a minimum threshold delay.

18. The method according to claim 16 or 17, wherein: The first value comprises an existing PDSCH to HARQ timing indicator value that has been remapped from indicating a delay value to indicating that HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH to HARQ timing indicator having a value different from the first value.

19. The method according to claim 18, wherein: Prior to sending the first DCI, the base station sends an instruction to the UE to remap the existing PDSCH to HARQ timing indicator value from indicating a delay value to indicating that the HARQ transmission should be delayed until the wireless device has received a DCI including a digital PDSCH to HARQ timing indicator having a value different from the first value.

20. The method according to claim 16 or 17, wherein: The first value comprises additional bits that have been added to an existing PDSCH to HARQ timing indicator value bit field in the DCI.

21. The method according to claim 16, wherein: Sending the second DCI also includes sending at least one of the following: a HARQ process identifier ID; a new data indicator NDI value; a PDSCH group ID; a downlink allocation indicator DAI; or a trigger bit.

22. A wireless device for setting a hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH), the wireless device comprising a processing circuit, the processing circuit being configured to: receiving (600, 700) first downlink control information (DCI) (508) associated with a first downlink (DL) data transmission (510), the first DCI (508) comprising a PDSCH to HARQ timing indicator having a first value, the first value indicating that HARQ feedback for the first DL data transmission will occur once the wireless device has received a DCI comprising a digital PDSCH to HARQ timing indicator having a value different from the first value; receiving (602, 702) the first DL data transmission (510); determining (604, 704) HARQ feedback for the first DL data transmission (510); receiving (606, 706) a second DCI (514) associated with a second DL data transmission (516), the second DCI (514) comprising a digital PDSCH-to-HARQ timing indicator indicating a time position of HARQ feedback associated with the second DL data transmission; Setting (608, 710) a time position of HARQ feedback associated with the first DL data transmission to be the same as a time position of HARQ feedback associated with the second DL data transmission; and At the set time position, HARQ feedback associated with the first DL data transmission (522) is sent (610, 712).

23. The wireless device of claim 22, wherein: The processing circuit is further configured to perform a method according to any one of claims 2-15.

24. The wireless device according to claim 22 or 23, wherein: The processing circuit comprises one or more processors and a memory storing instructions, the instructions being executable by the one or more processors, whereby the wireless device is operable to perform the method according to any one of claims 2-15.

25. A base station for setting a hybrid automatic repeat request (HARQ) timing for a physical downlink shared channel (PDSCH), the base station comprising a processing circuit, the processing circuit being configured to: determining PDSCH to HARQ timing for an upcoming downlink DL data transmission to a user equipment UE; determining that HARQ feedback for the upcoming DL data transmission should be delayed by the UE until further notification from the base station; sending first downlink control information (DCI) associated with the upcoming DL data transmission to a UE, the first DCI comprising a PDSCH-to-HARQ timing indicator having a first value for indicating to the UE that HARQ feedback for the upcoming DL data transmission should be delayed until further notification from the base station; as well as A second DCI is sent to the UE as the further notification, the second DCI being associated with a second DL data transmission and comprising a digital PDSCH to HARQ timing indicator.

26. The base station according to claim 25, wherein: The processing circuit is further configured to perform a method according to any one of claims 16-21.

27. The base station according to claim 25 or 26, wherein: The processing circuit comprises one or more processors and a memory storing instructions, wherein the instructions are executable by the one or more processors, whereby the base station is operable to perform the method according to any one of claims 16-21.

Images