Uplink control information transmission and hybrid automatic repeat request processing identification

Abstract

Apparatus, methods, and systems for New Radio (NR) User Equipment (UE). The apparatus includes baseband circuitry including a radio frequency (RF) interface and one or more processors coupled to the RF interface and configured to execute instructions for: encoding a plurality of transport blocks (TBs); encoding a first uplink transmission using these TBs and destined for an NR Evolved Node B (gNodeB) in unlicensed mode; decoding downlink control information (DCI) from the gNodeB; encoding a second uplink transmission using the TBs and destined for the gNodeB based on the DCI, wherein the DCI includes information relating to an identifier (ID) (HARQ Processing ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ Processing ID being based on a resource configuration index corresponding to the second uplink transmission; and transmitting the TBs, the encoded first uplink transmission, and the encoded second uplink transmission to the RF interface.

Description

[0001] This application is a divisional application of the invention patent application filed on June 27, 2018, with application number 201880042788.9 and invention title "Uplink Control Information (UCI) Transmission and Hybrid Automatic Repeat Request (HARQ) Processing Identifier for Unlicensed Physical Uplink Shared Channel (PUSCH)".

[0002] Cross-reference to related applications

[0003] This application claims the benefit and priority of U.S. Provisional Patent Application No. 62 / 525,417, filed June 27, 2017, entitled "Uplink Control Information (UCI) Transmission And Hybrid Automatic Repeat Request (HARQ) Process Identification For Grant-free Physical Uplink Shared Channel (PUSCH)", and also claims the benefit and priority of U.S. Provisional Patent Application No. 62 / 525,417, filed October 2, 2017, entitled "Uplink Control Information (UCI) Transmission And Hybrid Automatic Repeat Request (HARQ) Process Identification For Grant-free Physical Uplink Shared Channel (PUSCH)". The rights and priorities of U.S. Provisional Patent Application No. 62 / 567,030, entitled to Channel (PUSCH), the entire disclosure of which is incorporated herein by reference. Technical Field

[0004] This disclosure generally relates to the use of new radio HARQ processing identifiers, and to the use of unlicensed and licensed transmissions in NR networks. Background Technology

[0005] Wireless mobile communication technologies use various standards and protocols to transmit data between nodes (e.g., transmission stations) and wireless devices (e.g., mobile devices). Some wireless devices use Orthogonal Frequency Division Multiple Access (OFDMA) for downlink (DL) transmission and Single Carrier Frequency Division Multiple Access (SC-FDMA) for uplink (UL) transmission. Standards and protocols that use Orthogonal Frequency Division Multiplexing (OFDM) for signal transmission include: 3GPP Long Term Evolution (LTE) and New Radio (NR); IEEE 802.16 standards (e.g., 802.16e, 802.16m), commonly referred to in the industry as WiMAX (Microwave Access Global Interoperability); and IEEE 802.11 standards, commonly referred to in the industry as Wi-Fi.

[0006] In 3GPP Radio Access Network (RAN) Long Term Evolution (LTE) and NR systems, a node can be a combination of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an Evolved Node B, Enhanced Node B, eNodeB, or eNB) and a Radio Network Controller (RNC), which communicates with radio equipment called User Equipment (UE). Downlink (DL) transmissions can be communication from a node (e.g., eNodeB) to a radio equipment (e.g., UE), and uplink (UL) transmissions can be communication from a radio equipment to a node.

[0007] In LTE and NR, data can be transmitted from the base station to the UE via the Physical Downlink Shared Channel (PDSCH). The Physical Downlink Control Channel (PDCCH) can be used to provide control information about the downlink PDSCH. The Physical Uplink Control Channel (PUCCH) can be used to acknowledge received data. Downlink and uplink channels or transmissions can use Time Division Duplex (TDD) or Frequency Division Duplex (FDD). Time Division Duplex (TDD) is an application of Time Division Multiplexing (TDM) used to separate downlink and uplink signals. In TDD, downlink and uplink signals can be carried on the same carrier frequency (i.e., a shared carrier frequency), where the downlink signal uses a different time interval than the uplink signal, so the downlink and uplink signals do not interfere with each other. Frequency Division Multiplexing (FDM) is a type of digital multiplexing where two or more bit streams or signals (e.g., downlink or uplink) are ostensibly transmitted simultaneously as a sub-channel in a communication channel, but physically transmitted on different resources. In Frequency Division Duplex (FDD), uplink and downlink transmissions can operate using different frequency carriers (i.e., separate carrier frequencies for each transmission direction). Because downlink signals use different frequency carriers than uplink signals, interference can be avoided in FDD. Attached Figure Description

[0008] Figure 1 The diagram illustrates a signaling conflict where resources configured for unlicensed uplink transmissions conflict with resources configured for PUCCH transmissions carrying UCI reports.

[0009] Figure 2 The diagram illustrates the signaling process, where one or more processors of the UE have applied a priority rule that causes the PUCCH used for UCI reporting to be discarded, thereby facilitating the transmission of URLLC in the PUSCH.

[0010] Figure 3 The illustration shows that one or more processors of the UE have applied priority rules such that while a short PUCCH UCI is being sent, the unlicensed PUSCH for URLLC is delayed until the next available configuration resource.

[0011] Figure 4 The diagram illustrates a signaling scheme with priority rules, in which one or more processors of the UE simultaneously cause the transmission of an unlicensed PUSCH for URLLC transmission while punching a long PUCCH in the overlapping resources of the time slot.

[0012] Figure 5 The diagram illustrates the signaling process, where the HARQ processing ID is determined based on the resource configuration index of the resource used for retransmission.

[0013] Figure 6 The diagram illustrates a signaling configuration with multiple resource configurations, each with its own HARQ processing number.

[0014] Figure 7 The architecture of a network system 700 is illustrated according to some embodiments;

[0015] Figure 8 Example components of device 800 are illustrated according to some embodiments;

[0016] Figure 9 An example interface of the baseband circuit is illustrated according to some embodiments;

[0017] Figure 10 The control plane protocol stack is illustrated according to some embodiments;

[0018] Figure 11 The user plane protocol stack is illustrated according to some embodiments; and

[0019] Figure 12 The diagram illustrates a block diagram of components that, according to some example embodiments, are capable of reading instructions from a machine-readable or computer-readable medium and performing any one or more methods of the embodiments discussed herein. Detailed Implementation

[0020] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of explanation and not limitation, to provide a thorough understanding of various aspects of the various embodiments. However, it will be readily understood by those skilled in the art that benefit from this disclosure that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and processes have been omitted to avoid unnecessary detail that would obscure the description of the various embodiments. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0021] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of explanation and not limitation, to provide a thorough understanding of various aspects of the various embodiments. However, it will be readily understood by those skilled in the art that benefit from this disclosure that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted to avoid unnecessary detail that would obscure the description of the various embodiments. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0022] Mobile communications have evolved dramatically from early voice systems to today's highly sophisticated integrated communication platforms. Next-generation wireless communication systems, 5G, or NR, will provide access to information and data sharing by a wide variety of users and applications, anytime, anywhere. NR is envisioned as a unified network / system designed to meet highly diverse and sometimes conflicting performance dimensions and services. This diverse, multi-dimensional requirement is driven by different services and applications. Generally, NR will evolve based on 3GPP LTE Advanced and additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simpler, and more seamless wireless connectivity solutions. NR will enable wireless connectivity for anything and deliver fast, rich content and services.

[0023] Some use case families in NR involve enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC). These use case families have very different requirements for each other in terms of user plane (U-plane) latency and required coverage levels. The key requirements for URLLC are related to user plane latency and reliability.

[0024] For URLLC: (1) The target for user plane delay should be 0.5 ms for uplink (UL) communication and 0.5 ms for downlink (DL) communication; (2) The reliability target should be 1-10 within 1 millisecond. -5 .

[0025] For NR, the uplink control information (UCI) in the Physical Uplink Control Channel (PUCCH) may include scheduling requests (SR), hybrid automatic repeat request-acknowledge (HARQ-ACK) feedback, channel state information (CSI) reports (e.g., channel quality indicator (CQI), precoding matrix indicator (PMI), and rank indicator (RI)), and beam-related information. Furthermore, in NR, beam-related information may include: (1) beam state information (BSI), which may further include beam index and beam reference signal received power (L1-RSRP); and / or (2) beam refinement information (BRI), which may include L1-RSRP and beam index measured from the beam refinement reference signal (BRRS).

[0026] Furthermore, for NR, an agreement has been reached that data transmission can have a minimum duration of one symbol and can begin at any OFDM symbol. Additionally, for NR, the UE can be configured to perform "DL control channel monitoring" on a per-symbol basis relative to the DL control channel's parameter set (numerology). It should be noted that for URLLC, unlicensed uplink transmission (i.e., without explicit DCI with UL authorization) is supported for NR. Therefore, NR-compliant devices can be configured to support unlicensed uplink transmission for URLLC. Specifically, for NR, semi-static resources can be configured for a UE for unlicensed uplink transmission. Resources can include time and frequency resources, modulation and coding schemes (MCS), reference signals, etc. Furthermore, to achieve high reliability for URLLC, for NR, K repetitions of transport block (TB) transmissions can be configured for the UE in unlicensed transmission mode.

[0027] Typically, when URLLC data arrives, the UE may need to transmit it immediately to meet the strict delay requirements of URLLC. However, resources configured for unlicensed uplink transmissions on one hand and PUCCH transmissions carrying UCI reports on the other may conflict in time.

[0028] Now for reference Figure 1 The diagram illustrates signaling diagram 100, which shows a 14-symbol NR time slot used to provide resources for both unlicensed URLLC transmissions 102 (short transmissions, in the illustrated embodiment, the duration of one symbol per time slot) and UCI transmissions 104 in PUCCH (long transmissions, in the illustrated embodiment, the duration of multiple symbols per time slot). In fact, Figure 1An example is shown where resources configured for unlicensed uplink transmissions conflict in time with resources configured for PUCCH transmissions carrying UCI reports. In this case, the UE can, for example, piggyback UCI transmission 104 into one or more unlicensed uplink transmissions 102. However, this mechanism may require blind decoding of the unlicensed uplink transmissions on the NR Node B (gNodeB) side to handle potential false detections of DCI on the UE side, which may be undesirable in terms of the resulting processing latency. To address the above issues, embodiments define certain functions for one or more processors on the UE side to encode only one of the unlicensed Physical Uplink Shared Channel (PUSCH) carrying URLLC data and the PUCCH carrying UCI reports for transmission from the UE.

[0029] Some embodiments in this document relate to the simultaneous transmission of PUCCH carrying a UCI and unlicensed PUSCH transmissions for URLLC. Note that some embodiments discussed herein can also be applied to licensed PUSCH transmissions for URLLC.

[0030] Furthermore, some embodiments provide mechanisms for identification and signaling for HARQ processing in the case of possible configurations taking into account multiple processes of unlicensed UL transmissions and simultaneous operation of unlicensed and licensed UL transmissions.

[0031] Simultaneous transmission of UCI and unlicensed PUSCH transfers

[0032] As described above, when resources configured for unlicensed PUSCH transmission and PUCCH transmission carrying UCI reports conflict in time, if the UE intends to transmit URLLC data immediately on the configured resources, according to one embodiment, the UE can send only one of the unlicensed PUSCH and the PUCCH carrying UCI reports. This can help avoid potential misalignment issues between the gNodeB and the UE for proper decoding.

[0033] The following describes in more detail an embodiment of simultaneous transmission of UCI and unlicensed PUSCH.

[0034] According to one embodiment, an apparatus for a New Radio (NR) User Equipment (UE) is provided, the apparatus including baseband circuitry including an RF interface and one or more processors, the one or more processors being configured to: determine a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH); encode a first signal to be transmitted on the PUCCH, the first signal including uplink control information (UCI); encode a second signal to be transmitted on the PUSCH in unlicensed mode; and transmit at least one of the first signal and the second signal in a time slot according to a priority rule between the first signal and the second signal.

[0035] In one embodiment, a priority rule may instruct one or more processors of the UE to encode only one of the unlicensed PUSCH and the PUCCH carrying UCI transmitted in the same time slot, instead of encoding both. The drop rule or priority rule can be defined based on the set of parameters used for transmitting the PUCCH and unlicensed PUSCH, or based on the content of the UCI report (using the UCI type), or based on whether the PUCCH carrying the UCI report is a short or long PUCCH, or a combination of the above.

[0036] Alternatively, priority rules can be predefined in any NR specification, or configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or Radio Resource Control (RRC) signaling.

[0037] According to one embodiment, unlicensed uplink transmissions for URLLC have higher priority than all UCI types. In other words, if a PUCCH carrying a UCI conflicts with an unlicensed URLLC transmission in time, the UE can discard the PUCCH carrying the UCI. Figure 2 An example is shown where the UE discards the PUCCH carrying the UCI and only sends the unlicensed PUSCH for URLLC.

[0038] Now for reference Figure 2 The diagram is similar to Figure 1 The diagram illustrates signaling diagram 200, showing a 14-symbol NR time slot used to provide resources for both unlicensed URLLC transmissions 202 (short transmissions, each occupying one symbol duration within the time slot in the illustrated embodiment) and UCI transmissions 204 in PUCCH (long transmissions, each occupying multiple symbol durations in the illustrated embodiment). In fact, Figure 2An example is shown where priority rules have been applied by one or more processors of the UE to such that discarding PUCCHs used for UCI reporting (as shown by each cross) favors transmissions of URLLCs in PUSCHs, thereby avoiding conflicts within the time slot.

[0039] According to another embodiment, a priority rule can indicate that the priority of unlicensed uplink transmissions for URLLC is higher than that of Channel State Information (CSI) reports and / or beam-related reports in the UCI, but lower than the priority of HARQ-ACK feedback in the UCI. Under the latter priority rule, when an unlicensed uplink transmission for URLLC conflicts with a PUCCH carrying CSI reports and / or beam-related reports, the UE can discard the PUCCH carrying CSI and / or beam-related reports and only transmit the unlicensed uplink transmission for URLLC. However, when an unlicensed uplink transmission for URLLC conflicts with a PUCCH carrying HARQ-ACK feedback, the UE can only transmit the PUCCH carrying HARQ-ACK feedback and discard the unlicensed transmission for URLLC.

[0040] Note that, according to one embodiment of the priority rule, if HARQ-ACK and CSI and / or beam-related reports conflict in the same time slot, and further conflict with unlicensed uplink transmissions for URLLC, the UE may discard the PUCCH carrying all UCI types and only transmit the unlicensed PUSCH for URLLC. Alternatively, the UE may only transmit the PUCCH carrying HARQ-ACK feedback, while discarding the unlicensed PUSCH carrying URLLC and the PUCCH carrying CSI and / or beam-related reports.

[0041] HARQ-ACK feedback can be carried by the PUCCH in either a short or long duration. According to one embodiment, a priority rule for the UE to send a PUCCH carrying HARQ-ACK feedback while discarding an unlicensed PUSCH carrying URLLC and a PUCCH carrying CSI and / or beam-related reports can be applied to cases where only long PUCCHs are used to carry HARQ-ACK feedback and / or CSI and / or beam-related reports. As acknowledged in the NR, a short PUCCH can span one or two symbols, while a long PUCCH can span any number of symbols in a time slot, ranging from 4 to 14. If resources are configured in the same time slot for an unlicensed PUSCH for URLLC and for a short PUCCH carrying HARQ-ACK feedback, the UE can, according to the priority rules described in this paragraph, still send the short PUCCH carrying HARQ-ACK feedback while deferring the unlicensed PUSCH for URLLC to the next available configuration resource, such as... Figure 3 One example is shown. The latter priority rule may apply to situations where a short PUCCH carries CSI and / or beam-related reports.

[0042] Now for reference Figure 3 , Figure 3 The diagram illustrates signaling diagram 300, which shows a 14-symbol NR time slot used to provide resources for both unlicensed URLLC transmission 302 (short transmission, in the illustrated embodiment, the duration of one symbol within each occupied time slot) and UCI transmission 304 in short PUCCH. Figure 3 An example is shown in which a priority rule has been applied by one or more processors of the UE such that, while transmitting the short PUCCH UCI 304, the unlicensed PUSCH 302a for URLLC is delayed until the next available configuration resource. Alternatively, one or more processors of the UE may apply a priority rule to discard the PUCCH carrying CSI and / or beam-related reports, while causing the unlicensed PUSCH for URLLC (not shown) to be transmitted immediately.

[0043] According to another embodiment, if an unlicensed PUSCH for URLLC conflicts with a PUCCH carrying a UCI report in the time domain, the UE can stop transmitting the PUCCH and only transmit the unlicensed PUSCH for URLLC. Subsequently, when the UE completes the transmission of the unlicensed PUSCH, the UE may or may not continue the transmission of the PUCCH.

[0044] Now for reference Figure 4The diagram illustrates signaling diagram 400, which shows a 14-symbol NR time slot used to provide resources for both unlicensed URLLC transmission 402 (short transmission, in the illustrated embodiment, the duration of one symbol within each occupied time slot) and UCI transmissions 404a and 404b in long PUCCH, as shown in the figure. Figure 4 An example of a priority rule is illustrated, in which one or more processors of the UE cause the transmission of an unlicensed URLLC transmission 402 while simultaneously puncturing a long PUCCH 402a in the overlapping resources of a time slot. In this example, one or more processors will only cause the transmission of PUCCH 402a to continue only after the transmission of the unlicensed URLLC transmission 402 is completed. The latter embodiment can be applied to situations where the UE is configured to transmit a time-slot unlicensed PUSCH, such as... Figure 4 As suggested in the article, this may not result in a substantial performance degradation due to the perforation of the long PUCCH.

[0045] In another embodiment, in the event that the PUCCH carrying the UCI and the unlicensed PUSCH for URLLC are transmitted in time rather than frequency, a priority rule may be implemented by one or more processors of the UE to enable the simultaneous transmission of both the PUCCH carrying the UCI and the unlicensed PUSCH for URLLC, if the UE is capable of doing so.

[0046] According to another embodiment, the UE can implement a power sharing mechanism or power control equation based on the priority of PUCCH transmissions carrying UCI or unlicensed PUSCH transmissions used for URLLC. Specifically, according to one embodiment, the UE can allocate power in descending order of priority. For example, power is first allocated to the transmission with the highest priority (e.g., for unlicensed PUSCH transmissions) according to priority rules, and if there is a power margin to satisfy the power control equation, the UE can allocate power to transmissions with lower priority. If no power margin is available, the UE can discard lower priority transmissions.

[0047] HARQ processing identifiers and signaling for unlicensed UL transmissions

[0048] Typically, a UE can be configured with multiple HARQ processes for unlicensed UL transmissions, or it can maintain HARQ processes for both unlicensed and licensed UL transmissions simultaneously. Without the assistance of HARQ identification processing, the gNodeB typically cannot combine an unlicensed initial transmission with a subsequent licensed retransmission. The following description describes various embodiments involving multiple HARQ processes that simultaneously address HARQ identification. Depending on service characteristics and use cases, and different UE types with different service combinations, combinations of the embodiments disclosed herein can be applied to specific scenarios.

[0049] Multiple HARQ processes for unlicensed transmission

[0050] The following describes various embodiments involving multiple HARQ processes for unlicensed transmission. Scenario 1. Do not switch to base Retransmission under authorized PUSCH conditions

[0051] In cases where retransmissions occur without switching to license-based PUSCH, the gNodeB can detect such retransmissions but may not decode the retransmitted packets. UE retransmissions are triggered by a negative acknowledgment (NACK) message from the gNodeB, or by the absence of any ACK within a predetermined time period following a previous transmission (i.e., initial transmission or retransmission) in unlicensed mode. According to this embodiment, the NACK message can be sent in the downlink control information (DCI) of the physical downlink control channel (PDCCH) in the common search space or group common search space, wherein the DCI addressed to the UE (or multiple UEs) is transmitted on the specific physical resource where the retransmission is to occur, but it is not necessary to switch to license-based transmission.

[0052] In the latter case, although explicit DCI-based UL authorization is not required, the resources used for retransmission can be deterministically linked to the original resources by the gNodeB in a certain way, thereby avoiding consistency conflicts when multiple UEs use the same physical resources. Specifically, if multiple UEs transmit on the same physical resources using demodulation reference signals (DM-RS) or preamble sequences or with different scrambling seeds, the gNodeB can determine the appropriate retransmission resources based on the original transmission resources and the specific index / selection of the DM-RS, preamble, and / or scrambling used in the initial transmission. Therefore, the gNodeB can perform blind decoding at possible locations to detect unauthorized retransmissions, thus completing HARQ processing at the gNodeB end.

[0053] To support retransmission mechanisms such as those described above, explicit identification of HARQ processing may not be necessary. However, this approach may not be suitable for certain applications (such as URLLC applications or applications with low latency requirements), and switching the UE to licensed UL transmission may be advantageous for achieving stringent latency and / or reliability goals.

[0054] Scenario 2. Switch to authorization-based retransmission

[0055] Some embodiments include switching the UE to a license-based mode to transmit packets that were initially attempted to be transmitted via unlicensed UL transmission.

[0056] For unlicensed transmissions, the UE can be configured via semi-static signaling (e.g., semi-static UE-specific signaling or UE group-specific signaling) and / or RRC signaling, utilizing a set of physical time-frequency resources. This set of physical time-frequency resources includes a reference signal (DM-RS), preamble, and / or scrambling sequence (explicit or implicit) for unlicensed transmissions. These physical resources may also be associated with certain MCS selections, which may result in a mapping to certain transport block sizes (TBS) depending on the physical resource size of each individual transmission and / or on consideration of a certain number (K) of configurations with redundant version (RV) cycles.

[0057] Based on the above, a UE can therefore be configured with one or more resource configurations, each providing transmission opportunities that can be interleaved in time. For a single / given resource configuration, there may also be one or more HARQ processes corresponding to one or more transmission instances of different transport blocks (TBs). If a single HARQ process is associated with a single resource configuration, and furthermore, if the UE can only be configured with a single resource configuration, then only one HARQ process identifier may be required after switching from unlicensed transmission to licensed transmission.

[0058] However, multiple resource configurations can be configured for the UE for unlicensed transport, each with one or more HARQ processes. In this case, the gNodeB must be able to distinguish between such HARQ processes and between these processes and any other licensed HARQ processes.

[0059] First, the UE can be configured with multiple HARQ processes corresponding to unlicensed transmission. Therefore, multiple HARQ process numbers (HPNs) may be required to initiate unlicensed transmission. In one embodiment, where the UE is configured with multiple resource configurations for unlicensed transmission via semi-static signaling, different HPNs can be determined based on the index of the resource configuration. Option 1 will be further explained below.

[0060] Option 1: HARQ processing IDs are functions for resource configuration indexes that handle unauthorized transfers.

[0061] According to the embodiment of option 1, such as by Figure 5 As illustrated in the example, the HARQ processing ID can be determined based on the resource configuration index of the resources used for retransmission. In the latter case, each resource configuration can be associated with a HARQ processing ID, which is either explicitly configured or implicitly derived from the resource configuration index. Since the gNodeB has complete control over the resources of each configuration, the UE and gNodeB can always derive the HARQ processing ID without question based on the resource configuration index. In Equation 1 below, "number of HARQ processes" corresponds to the total number of HARQ processes configured for one or more resource configurations corresponding to the UE, and "offset" can correspond to the time offset of the transmission / retransmission from the UE relative to the start boundary of the time-domain (e.g., timeslot) of the time-frequency resources configured for the UE.

[0062] HARQ Processor ID = [Resource Configuration Index + Offset] modulo [Number of HARQ Processors] (Equation 1)

[0063] For details, please refer to the following: Figure 5 The diagram 500 illustrates signaling diagram 500, which depicts uplink transmissions 502a, 502b, and 502c in three different corresponding scenarios 503a, 503b, and 503c, as shown in the figure. Scenario 503a involves an uplink transmission with a single HARQ process numbered 0, scenario 503b involves an uplink transmission with two HARQ processes numbered 0 and 1, and scenario 503c involves an uplink transmission with three HARQ processes numbered 0, 1, and 2. Figure 5 This is an example of deriving the HARQ processing ID based on a configuration index, where each resource configuration index has a HARQ processing ID. Transmissions 503a / b / c may include licensed or unlicensed uplink retransmissions, and the gNodeB will need the corresponding HARQ processing ID for the retransmission to reconstruct the packet at the gNodeB end. When the UE subsequently performs a retransmission (where at least the initial transmission was in unlicensed mode), HARQ processing numbers 0, 1, and 2 can be used as the basis for the HARQ processing ID that the gNodeB transmits to the UE.

[0064] like Figure 5 As shown, the horizontal axis is in the time domain and illustrates the offset of each transmission group relative to the time slot 0 boundary, which is represented by a system frame number (SFN) equal to zero. The UE needs to know the SFN to determine when to receive DL and / or to transmit on the uplink. Figure 5The period for each set of repetitions for semi-persistent scheduling (SPS) is further described. To support more allocations without increasing the size of the PDCCH, SPS can be used, according to which the base station can pre-configure the UE using the SPS-RNTI (allocation ID) and the period. Once pre-configured, if the UE receives an allocation for DL ​​or UL using the SPS radio network temporary identifier SPS-RNTI (instead of the typical cell RNTI (C-RNTI)), the allocation is repeated according to the pre-configured period. Figure 5 The repetitions for each scenario 503a, 503b, and 503c are shown as two repetitions (two 0s, two 1s, and two 2s within each cycle are shown as repetitions), but more repetitions are possible.

[0065] Option 2: HARQ handles IDs as functions of resource (time / frequency) indexes.

[0066] If a single resource configuration also includes multiple time-interleaved transmission opportunities for different TBs for the UE, in one embodiment, the corresponding HPN can be determined based on the physical resource index, or based on transmission parameters associated with the first repetition (out of K repetitions) of each transmission opportunity (e.g., DM-RS, preamble, pre-synchronization preamble in PUSCH, and / or scrambling seed), or based on the interleaving of transmission opportunities within a specific resource configuration, such as through... Figure 6 As illustrated in the example above. Therefore, for a UE with N transmission opportunities and M resource configurations within a single resource configuration, the UE can support up to M*N HPNs for unlicensed transmissions. For a resource configuration index m and a transmission opportunity n, the HPN is given by HPN(m, n) = m*N + n, where m = 0, 1, ..., M-1, and n = 0, 1, ..., N-1. Typically, N can be limited to a small number, for example, N = 1 or 2. The above embodiments are described in detail for option 2.

[0067] One example is the LTE equation used to determine HARQ processing based on the current transmission time interval (TTI). Depending on the number of HARQ processes configured for semi-persistent scheduling (SPS), this equation, namely Equation 2, will generate a different HARQ process ID for each consecutive transmission moment.

[0068] HARQ process ID=[floor(CURRENT_TTI / semiPersistSchedIntervalUL)]modulo[numberOfConfUlSPS-Processes] (Equation 2)

[0069] As reflected in Equation 2, since the baseline assumption is to configure a single resource within a TTI, it may not be necessary to rely on any frequency resources within a resource configuration to determine the HARQ process ID based on the current TTI. Here, "numberOfConfUlSPS-Processes" corresponds to the number of HARQ processes configured for that resource configuration, and the UE should use the authorization provided in the SPS activation DCI from the base station once per semiPersistSchedIntervalUL.

[0070] In the case of multiple resource configurations, each resource configuration can have its own HARQ processing numbering scheme. Therefore, some offset or semi-static partitioning of HARQ processing across different resource configurations may be required, as will be explained in further detail below.

[0071] Now for specific reference Figure 6 The diagram illustrates signaling diagram 600, which depicts uplink transmissions 602a, 602b, and 602c in three different corresponding scenarios 603a, 603b, and 603c, as shown. Scenario 603a involves an uplink transmission with a single HARQ process numbered 0, scenario 603b involves an uplink transmission with two HARQ processes numbered 0 and 1, and scenario 603c involves an uplink transmission with three HARQ processes numbered 0, 1, and 2. A single resource is shown in each current TTI. Transmissions 603a / b / c may include licensed or unlicensed uplink retransmissions, and the gNodeB will require the corresponding HARQ process ID for the retransmission to reconstruct the packet at the gNodeB end. When the UE subsequently performs a retransmission (where at least the initial transmission was in unlicensed mode), HARQ process numbers 0, 1, and 2 can be used as the basis for the HARQ process ID transmitted by the gNodeB to the UE.

[0072] like Figure 6 As shown, the horizontal axis is in the time domain and illustrates the offset of each transmission group relative to the time slot 0 boundary, which is represented by a system frame number (SFN) equal to zero. The UE needs to know the SFN to determine when to receive DL and / or to transmit on the uplink. Figure 6 The period for each set of repetitions used in semi-persistent scheduling (SPS) is further described. Figure 6 The repetitions for each scenario 603a, 603b, and 603c are shown as two repetitions (two 0s, two 1s, and two 2s within each cycle are shown as repetitions), but more repetitions are possible.

[0073] The numbering method for HPNs suggested by, for example, Equation 2 is limited to the set of HPNs corresponding to unlicensed transmissions. That is, the aforementioned HPN / HARQ processing ID can be indicated to the UE as part of a DCI carrying UL authorization, which is used to switch the UE from unlicensed transmissions to licensed transmissions for a specific TB.

[0074] When HARQ processing for unlicensed and licensed transports is to be shared from a common pool of available HARQ processes, the corresponding HPN / HARQ process IDs need to be appropriately mapped to the entire set of HARQ processes. Some relevant embodiments are further described in the section below entitled “Multiple HARQ Processes for Unlicensed and Licensed Transports”.

[0075] The following describes a unified framework that can support combinations of options 1 and 2.

[0076] In one embodiment, the “CURRENT_TTI” component in the equation of option 2 can be generalized such that it corresponds to a transmission opportunity consisting of individual resources or a transmission opportunity consisting of a set of resources identified by the initial transmission of TB, followed by its repetition (the initial and K repetitions are referred to as a single transmission opportunity). The hierarchical relationship can then be defined as follows: First, a set of one or more HARQ process IDs (HPNs) defined by the starting HARQ process index can be identified for a given resource configuration according to option 1. Second, when multiple processes are configured for each resource configuration, the HARQ process ID of each transmission opportunity in one or more transmission opportunities within the resource configuration can be identified according to option 2. For the above two-stage HARQ process ID determination method, HARQ processes can be semi-statically partitioned between different resource configurations, and the equation of option 1 can be further generalized to adapt to resource configurations with different numbers of HARQ processes. An example of such a generalized method can be provided by the following equation (Equation 3):

[0077] HARQ processing ID={[floor(CURRENT_TTI / semiPersistSchedIntervalUL(i))]modulonumberofConfUlSPS-Processes(i)+harqProcessOffset(i)}modulototalNumberOfConfUlSps-Processes;

[0078] Where i represents the index of the resource configuration, and multiple parameters can be configured based on each resource configuration, such as semiPersistSchedIntervalUL(i), numberOfConfUlSPS-Processes(i), and harqProcessOffset(i).

[0079] Multiple HARQ processes for unlicensed and licensed transmissions.

[0080] In this section, embodiments can be described in a context that distinguishes between HARQ processing corresponding to an unlicensed initial transmission and HARQ processing corresponding to subsequent licensed transmissions / retransmissions.

[0081] Unlicensed UL transmissions can be based on one of two scenarios: (i) semi-static resource configuration without any additional Layer 1 activation / signaling, or (ii) semi-static resource configuration followed by Layer 1 activation and subject to further Layer 1 modification or deactivation. In this context, it is desirable to implement any Layer 1 signaling via a DCI that has a Cyclic Redundancy Check (CRC) scrambled with an appropriate UE-ID (e.g., C-RNTI). Furthermore, a switch from unlicensed retransmission to licensed retransmission for TB can also be implemented via Layer 1 signaling using a DCI with a CRC scrambled with an appropriate UE-ID (e.g., C-RNTI).

[0082] In one embodiment of the scheme requiring Layer 1 signaling described above, a DCI for activating / deactivating / modifying resource configurations for unlicensed transmissions can be sent, with its CRC scrambled using SPS-C-RNTI (Semi-Persistent Scheduling C-RNTI) or Unlicensed C-RNTI (GF-C-RNTI). However, on the other hand, a DCI indicating a switch to licensed retransmissions can be sent, with its CRC scrambled using a regular C-RNTI in the case of previous unlicensed transmissions requiring no Layer 1 signaling; and its CRC scrambled using either SPS-C-RNTI or GF-C-RNTI in the case of previous unlicensed transmissions subject to Layer 1 activation / deactivation / modification. Here, GF-C-RNTI can be used, for example, only to scramble the CRC for DCIs indicating licensed retransmissions, with the aim of distinguishing it from regular retransmission licenses for licensed operations. Therefore, in another embodiment, the use of GF-C-RNTI can be applied to DCIs indicating a switch from unlicensed to licensed retransmissions for both types of unlicensed operations (without Layer 1 signaling or with Layer 1 signaling). Alternatively, in all cases corresponding to the unlicensed transmission type, the transmission indication can be switched to licensed retransmission DCI, with its CRC scrambled using regular C-RNTI.

[0083] In cases where the RNTI differs from the C-RNTI, in one embodiment, the HPN indicated by the HARQ Processor ID field in the DCI indicating a switch to licensed retransmission can indicate an HPN within the processing set used for unlicensed transmissions. When a shared HARQ processing pool is used for both unlicensed and licensed operations, further mapping of the indicated HPN can be achieved using a specified HPN mapping rule relative to the global HARQ processing pool. One such rule can be based on a higher-layer configuration, thereby partitioning the HARQ processing pool between unlicensed and licensed initial transmissions. Alternatively, a higher-layer configuration-based partitioning approach can be used to directly indicate the HPN (within the global HARQ processing pool) via the HARQ Processor ID field in the switching DCI, if the DCI is sent and its CRC is scrambled with the C-RNTI.

[0084] According to one embodiment, for two CRC scrambling options (i.e., scrambling with C-RNTI or scrambling with an RNTI different from C-RNTI), although the range of the HPN indicated in the corresponding cases may be different, the bit width of the HARQ processing ID field can be the same. The above is to enable the use of a common DCI format (thereby not increasing the number of blind decoding attempts by the UE) for retransmission indications for unlicensed to licensed switching and for regular licensed operations, respectively.

[0085] In cases where an RNTI different from the C-RNTI is used to scramble the CRC in a DCI indicating a switch from unlicensed retransmission to licensed retransmission, according to one embodiment, the multiplexing between HARQ processing for licensed UL transmission and unlicensed UL transmission does not necessarily have to be based on a HARQ processing pool partitioned by a higher layer, but can be dynamically determined. This is possible because using SPS-C-RNTI or GF-C-RNTI to scramble the CRC in the corresponding DCI indicates to the UE that the HPN indicated in the HARQ processing ID field actually corresponds to the HARQ processing used for unlicensed initial transmission.

[0086] However, the sum of HARQ processing for both unlicensed and regular licensed transmissions may exceed the maximum number of total UL HARQ processing for the UE. To manage this possibility, embodiments consider reservations for minimum and maximum numbers of HARQ processing for each type of UL transmission. Therefore, in one embodiment, the number of HARQ processing for a UE configured with unlicensed transmissions can be configured to be in the range of X_GFmin to X_GFmax for unlicensed initial transmissions, and from X_GBmin to X_GBmax for regular licensed transmissions, where X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured. X_GFmin (X_GFmax) and X_GBmin (X_GBmax) are the minimum (maximum) numbers of HARQ processing reserved for unlicensed initial transmissions and regular licensed transmissions, respectively.

[0087] As an example, both X_GFmin and X_GBmin can consist only of non-zero small integers (e.g., 1 or 2), or X_GFmin can be 0, but X_GBmin may consist only of non-zero integers. Therefore, in some examples, X_GBmax = X_max – X_GFmin and X_GFmax = X_max – X_GBmin, or X_GFmax can be configured to a value smaller than X_max – X_GBmin. Here, X_max is the maximum number of UL HARQ processes for the UE.

[0088] According to some illustrative embodiments, an apparatus, system, and method for a New Radio (NR) user equipment is provided. The apparatus includes baseband circuitry including an RF interface and one or more processors coupled to the RF interface. The one or more processors are configured to: encode a plurality of transport blocks (TBs); encode a first uplink transmission using the TBs and destined for an NR evolved Node B (gNodeB) in an unlicensed mode; decode downlink control information (DCI) from the gNodeB; and, based on the DCI, encode a second uplink transmission using the TBs and destined for the gNodeB, wherein the second uplink transmission is in either an unlicensed mode or a licensed mode, and wherein the DCI includes information relating to an identifier (ID) (HARQ process ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ process ID being based on a resource configuration index corresponding to the second uplink transmission.

[0089] According to some illustrative embodiments, an apparatus, system, and method are provided for a new radio (NR) user equipment. The apparatus includes a memory with a buffer and one or more processors coupled to the memory, the buffer corresponding to Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) processing. The one or more processors are configured to: decode a first uplink transmission from an NR user equipment (UE) in an unlicensed mode; encode downlink control information (DCI) for transmission to the NR UE; and decode a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ processing ID) of the HARQ processing corresponding to the second uplink transmission; and decoding the second uplink transmission includes implementing the HARQ processing.

[0090] According to some illustrative embodiments, an apparatus, system, and method are provided for a new radio (NR) user equipment. The apparatus includes a memory and one or more processors coupled to the memory. The processors are configured to: decode a first uplink transmission from an NR user equipment (UE) in an unlicensed mode; encode downlink control information (DCI) for transmission to the NR UE; and decode a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ processing ID) of a HARQ process corresponding to the second uplink transmission; and decoding the second uplink transmission includes implementing HARQ processing.

[0091] Example networks and architectures that can be used to implement some illustrative embodiments will be referred to below. Figures 7-12 To describe and illustrate.

[0092] Figure 7 The architecture of a network system 700 is illustrated according to some embodiments. System 700 is shown as including user equipment (UE) 701 and UE 702. UE 701 and 702 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless phone, or any computing device including a wireless communication interface.

[0093] In some embodiments, either UE 701 or 702 may include an Internet of Things (IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may use technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based service (ProSe), device-to-device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated. The IoT network description utilizes short-lived connections to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messaging, state updates, etc.) to facilitate connectivity within the IoT network.

[0094] UEs 701 and 702 can be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 710—RAN 710 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. UEs 701 and 702 utilize connections 703 and 704 respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 703 and 704 are shown as air interfaces to enable communication coupling and can conform to cellular communication protocols such as Global System for Mobile Communications (GSM), code-division multiple access (CDMA) network protocols, push-to-talk (PTT) protocols, PTT over Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, fifth generation (5G) protocols, New Radio (NR) protocols, and so on.

[0095] In this embodiment, UEs 701 and 702 can also directly exchange communication data via the ProSe interface 705. The ProSe interface 705 may also be referred to as a sideline interface including one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0096] UE 702 is shown configured to access access point (AP) 706 via connection 707. Connection 707 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, where AP 706 will include Wireless Fibre Channel. Router. In this example, AP 706 is shown connected to the Internet, but not to the core network of the wireless system (described in more detail below).

[0097] RAN 710 may include one or more access nodes that enable connectivity between 703 and 704. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNodeBs), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). RAN 710 may include one or more RAN nodes for providing macrocell coverage, such as macro RAN node 711, and one or more RAN nodes for providing femtocells or picocells (e.g., cells with smaller coverage area, smaller user capacity, or higher bandwidth compared to macrocells), such as low-power (LP) RAN node 712.

[0098] Either RAN node 711 or 712 may terminate the air interface protocol and may be the first contact point for UEs 701 and 702. In some embodiments, either RAN node 711 or 712 may perform various logical functions for RAN 710, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0099] According to some embodiments, UEs 701 and 702 may be configured to communicate with each other or with either RAN nodes 711 and 712 via a multi-carrier communication channel using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals, according to various communication technologies, such as, but not limited to, Orthogonal Frequency-Division Multiple Access (OFDMA) communication technology (e.g., for downlink communication) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technology (e.g., for uplink and ProSe or side-by-side communication), although the scope of the embodiments is not limited thereto. OFDM signals may include multiple orthogonal subcarriers.

[0100] In some embodiments, the downlink resource grid can be used for downlink transmissions from either RAN nodes 711 and 712 to UEs 701 and 702, while uplink transmissions can utilize similar techniques. This grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is standard practice in OFDM systems, making it intuitive for radio resource allocation. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises several resource blocks, which describe the mapping from a specific physical channel to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this represents the minimum amount of currently allocable resources. Several different physical downlink channels are transported using such resource blocks.

[0101] The physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to UEs 701 and 702. The physical downlink control channel (PDCCH) carries information about the transmission format and resource allocation associated with the PDSCH channel, etc. It also informs UEs 701 and 702 about the transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UE 702 within the cell) can be performed at either RAN nodes 711 or 712 based on channel quality information fed back from either UE 701 or 702. Downlink resource assignment information can be transmitted on the PDCCH used (e.g., assigned to) each of UEs 701 and 702.

[0102] PDCCH can use control channel elements (CCEs) to transport control information. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quadruplets, which are then transposed using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE corresponds to one of nine sets of physical resource elements called a resource element group (REG), each set comprising four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped for each REG. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, four or more different PDCCH formats can be defined with different numbers of CCEs (e.g., aggregation levels L = 1, 2, 4, or 8).

[0103] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the concepts described above. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of physical resource elements called enhanced resource element groups (EREGs), each set comprising four physical resource elements. In some cases, an ECCE may have an additional number of EREGs.

[0104] RAN 710 is shown communicatively coupled to core network (CN) 720 via S1 interface 713. In embodiments, CN 720 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 713 is divided into two parts: S1-U interface 714, which carries traffic data between RAN nodes 711 and 712 and the serving gateway (S-GW) 722; and S1 mobility management entity (MME) interface 715, which is the signaling interface between RAN nodes 711 and 712 and MME 721.

[0105] In this embodiment, CN 720 includes MME 721, S-GW 722, Packet Data Network (PDN) Gateway (P-GW) 723, and Home Subscriber Server (HSS) 724. MME 721 is functionally similar to the control plane of a conventional Serving GPRS Support Node (SGSN). MME 721 manages mobility aspects of access, such as gateway selection and tracking area list management. HSS 724 may include a database for network users, including subscription-related information, to support network entities in processing communication sessions. CN 720 may include one or more HSS 724s, depending on the number of mobile subscribers, device capacity, network organization, etc. For example, HSS 724 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location compliance, etc.

[0106] The S-GW 722 can terminate the S1 interface 713 facing the RAN 710 and route data packets between the RAN 710 and CN 720. Furthermore, the S-GW 722 can serve as a local mobility anchor point for handovers between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0107] The P-GW 723 can terminate an SGi interface toward the PDN. The P-GW 723 can route data packets between the EPC network and an external network via an Internet Protocol (IP) interface 725, such as a network including an application server 730 (or application function (AF)). Generally, the application server 730 can be an element providing IP-bearing resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 723 is shown communicatively coupled to the application server 730 via the IP communication interface 725. The application server 730 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 701 and 702 via a CN 720.

[0108] The P-GW 723 can also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 726 is the policy and charging control element of the CN720. In non-roaming scenarios, a single PCRF can exist in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic routing, two PCRFs can be associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMMN and the Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 726 can be communicatively coupled to the application server 730 via the P-GW 723. Application server 730 can signal PCRF 726 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 726 can configure this rule into the Policy and Charge Enforcement Function (PCRF) (not shown) using an appropriate traffic flow template (TFT) and QoS class identifier (QCI), which initiates the QoS and charging specified by application server 730.

[0109] Figure 8Example components of device 800 are illustrated according to some embodiments. In some embodiments, device 800 may include at least, as shown, application processing circuitry 802, baseband circuitry 804, radio frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 coupled together. The components of the illustrated device 800 may be included in a UE or RAN node. In some embodiments, device 800 may include fewer components (e.g., the RAN node may not utilize application processing circuitry 802, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 800 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interface components. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

[0110] Application processing circuitry 802 may include one or more application processors. For example, application processing circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 800. In some embodiments, the processor of application processing circuitry 802 may process IP data packets received from the EPC.

[0111] The baseband circuit 804 may include, for example, but not limited to, one or more single-core or multi-core processors. The baseband circuit 804 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuit 806 and to generate baseband signals for the transmit signal path of the RF circuit 806. The baseband circuit 804 may interface with the application processing circuit 802 to generate and process baseband signals and control the operation of the RF circuit 806. For example, in some embodiments, the baseband circuit 804 may include one or more processors, including a third-generation (3G) baseband processing circuit 804A, a fourth-generation (4G) baseband processing circuit 804B, a fifth-generation (5G) baseband processing circuit 804C, or other (one or more) baseband processing circuits 804D for other existing generations, generations under development, or future generations to be developed (e.g., second-generation (2G), sixth-generation (6G), etc.). Baseband circuitry 804 (e.g., one or more of baseband processing circuitry 804A-D) can handle various radio control functions that enable communication with one or more radio networks via RF circuitry 806. In other embodiments, some or all of the functions of baseband processing circuitry 804A-D may be included in a module stored in memory 804G and executed via central processing unit (CPU) 804E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF offset, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 804 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. The FFT may be provided via one or more memories coupled to the modulation / demodulation circuitry of the baseband circuitry, such as one or more random access memories to allow butterfly operations. In some embodiments, the encoding / decoding circuitry of baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other appropriate functions may be included in other embodiments.

[0112] In some embodiments, the baseband circuitry 804 may include one or more audio digital signal processors (DSPs) 804F. The audio DSP(s) 804F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. Components of the baseband circuitry may be suitably combined in a single chip, a single chip assembly, or, in some embodiments, arranged on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 804 and the application processing circuitry 802 may be implemented together on, for example, a system on a chip (SOC).

[0113] In some embodiments, baseband circuitry 804 can provide communication compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 804 may support communication with an evolved universal terrestrial radio access network (E-UTRAN) or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), or wireless personal area networks (WPAN). Embodiments in which baseband circuitry 804 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuitry.

[0114] RF circuit 806 can enable communication with a wireless network using modulated electromagnetic radiation via a non-solid-state medium. In various embodiments, RF circuit 806 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 806 may include a receive signal path, which may include circuitry to down-convert RF signals received from FEM circuit 808 and provide baseband signals to baseband circuit 804. RF circuit 806 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by baseband circuit 804 and provide RF output signals to FEM circuit 808 for transmission.

[0115] In some embodiments, the receive signal path of RF circuit 806 may include mixer circuit 806a, amplifier circuit 806b, and filter circuit 806c. In some embodiments, the transmit signal path of RF circuit 806 may include filter circuit 806c and mixer circuit 806a. RF circuit 806 may also include synthesizer circuit 806d for synthesizing frequencies for use by mixer circuit 806a in both the receive and transmit signal paths. In some embodiments, mixer circuit 806a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 808 based on the synthesized frequency provided by synthesizer circuit 806d. Amplifier circuit 806b may be configured to amplify the down-converted signal, and filter circuit 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 804 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, although this is not a necessary requirement. In some embodiments, the mixer circuit 806a of the received signal path may include a passive mixer, although the scope of the embodiments is not limited thereto.

[0116] In some embodiments, the mixer circuit 806a of the transmit signal path may be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuit 806d to generate an RF output signal for the FEM circuit 808. The baseband signal may be provided by the baseband circuit 804 and may be filtered by the filter circuit 806c.

[0117] In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may be configured for superheterodyne operation.

[0118] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 804 may include a digital baseband interface for communicating with RF circuitry 806.

[0119] In some dual-mode embodiments, separate radio IC circuitry may be provided to process signals for each spectrum, although the scope of the embodiments is not limited thereto.

[0120] In some embodiments, synthesizer circuit 806d may be a fractional N-type synthesizer or a fractional N / N+1-type synthesizer, although the scope of the embodiments is not limited thereto, as other types of frequency synthesizers may be appropriate. For example, synthesizer circuit 806d may be an incremental sum synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0121] The synthesizer circuit 806d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 806a of the RF circuit 806. In some embodiments, the synthesizer circuit 806d can be a fractional N / N+1 type synthesizer.

[0122] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. Depending on the desired output frequency, the divider control input may be provided by baseband circuitry 804 or application processing circuitry 802. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application processing circuitry 802.

[0123] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0124] In some embodiments, synthesizer circuitry 806d may be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases from each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 806 may include an IQ / polar coordinate converter.

[0125] FEM circuit 808 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals, and provide an amplified version of the received signals to RF circuit 806 for further processing. FEM circuit 808 may also include a transmit signal path, which may include circuitry configured to amplify a transmit signal provided by RF circuit 806 for transmission by one or more of the one or more antennas 810. In various embodiments, amplification via the transmit or receive path may be performed only in RF circuit 806, only in FEM 808, or in both RF circuit 806 and FEM 808.

[0126] In some embodiments, FEM circuit 808 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 806). The transmit signal path of FEM circuit 808 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 806) and include one or more filters to generate an RF signal for subsequent transmission (e.g., transmitted by one or more of one or more antennas 810).

[0127] In some embodiments, the PMC 812 manages the power supplied to the baseband circuitry 804. Specifically, the PMC 812 controls power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 812 is often included when the device 800 can be battery powered, such as when the device is included in a UE. The PMC 812 increases power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0128] although Figure 8 A PMC 812 is shown coupled only to the baseband circuit 804. However, in other embodiments, the PMC 812 may additionally or alternatively couple to other components and perform similar power management operations for other components, such as, but not limited to, the application processing circuit 802, the RF circuit 806, or the FEM 808.

[0129] In some embodiments, the PMC 812 may control various power-saving mechanisms of the device 800 or otherwise be part of such power-saving mechanisms. For example, if the device 800 is in an RRC_Connected state that remains connected to the RAN node because it expects to receive traffic soon, it may enter a state called Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 800 may interrupt power at short intervals to save power.

[0130] If there is no data traffic activity for an extended period, device 800 can transition to the RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 800 enters a very low-power state and performs paging, during which it periodically wakes up again to listen to the network, and then powers off again. Device 800 may not receive data in this state; to receive data, it must transition back to the RRC_Connected state.

[0131] Additional power-saving modes allow devices to be unavailable to the network for periods longer than the paging interval (ranging from seconds to hours). During this time, the device is completely unreachable from the network and can be completely powered off. Any data transmitted during this time suffers a significant delay, which is assumed to be acceptable.

[0132] The processor of application processing circuitry 802 and the processor of baseband circuitry 804 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuitry 804 can be used individually or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application processing circuitry 802 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). For the purposes of this document, layer 3 may include the radio resource control (RRC) layer, which is described in more detail below. For the purposes of this document, layer 2 may include the medium access control (MAC) layer, the radio link control (RLC) layer, and the packet data convergence protocol (PDCP) layer, which is described in more detail below. For the purposes of this document, layer 1 may include the physical (PHY) layer of the UE / RAN node, which is described in more detail below.

[0133] Figure 9 Example interfaces of the baseband circuit are illustrated according to some embodiments. As described above, Figure 8 The baseband circuit 804 may include processors 804A-804E and memory 804G utilized by the processors. Each of the processors 804A-804E may include memory interfaces 904A-904E for sending / receiving data to / from memory 804G.

[0134] The baseband circuit 804 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 912 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 804) and an application circuit interface 914 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 804). Figure 8 Application processing circuit 802 (interface for transmitting / receiving data), RF circuit interface 916 (e.g., for sending / receiving data to / from...) Figure 8RF circuit 806 (interface for transmitting / receiving data), wireless hardware connectivity interface 918 (e.g., for transmitting / receiving data to / from Near Field Communication (NFC) components), Components (e.g., low energy consumption) ), Interfaces for sending / receiving data to / from components and other communication components) and power management interface 920 (e.g., an interface for sending / receiving power or control signals to / from PMC 812).

[0135] Figure 10 This is a diagram of a control plane protocol stack according to some embodiments. In this embodiment, control plane 1000 is shown as a communication protocol stack between UE 701 (or UE 702), RAN node 711 (or RAN node 712) and MME 721.

[0136] PHY layer 1001 can transmit or receive information used by MAC layer 1002 through one or more air interfaces. PHY layer 1001 can also perform link adaptive or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., RRC layer 1005). PHY layer 1001 can also perform error detection on the transport channel, forward error correction (FEC) encoding / decoding on the transport channel, modulation / demodulation of the physical channel, interleaving, rate matching, mapping to the physical channel, and multiple input multiple output (MIMO) antenna processing.

[0137] The MAC layer 1002 can perform mapping between logical channels and transport channels, multiplexing MAC service data units (SDUs) from one or more logical channels onto transport blocks (TBs) for delivery to the PHY via the transport channels, demultiplexing MAC SDUs from transport blocks (TBs) delivered from the PHY via the transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel priority differentiation.

[0138] RLC layer 1003 can operate in multiple modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC layer 1003 can perform the transmission of upper-layer protocol data units (PDUs), error correction via automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC layer 1003 can also perform RLC data PDU resegmentation for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0139] PDCP layer 1004 can perform IP data header compression and decompression, maintain PDCP sequence numbers (SN), perform in-order delivery of upper-layer PDUs during lower-layer re-establishment, eliminate duplication of lower-layer SDUs during lower-layer re-establishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of control plane data, discard control data based on timers, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0140] The main services and functions of RRC layer 1005 may include broadcasting system information (e.g., included in the Master Information Block (MIB) or System Information Block (SIB) related to the non-access stratum (NAS), broadcasting system information related to the access stratum (AS), paging, establishment, maintenance, and release of RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more information elements (IEs), each of which may include an individual data field or data structure.

[0141] UE 701 and RAN node 711 can use the Uu interface (e.g., LTE-Uu interface) to exchange control plane data via a protocol stack including PHY layer 1001, MAC layer 1002, RLC layer 1003, PDCP layer 1004 and RRC layer 1005.

[0142] The Non-Access Plane (NAS) protocol 1006 forms the highest level of the control plane between UE 701 and MME 721. NAS protocol 1006 supports the mobility and session management processes of UE 701 to establish and maintain IP connectivity between UE 701 and P-GW 723.

[0143] The S1 Application Protocol (S1-AP) layer 1015 supports the functions of the S1 interface and includes an Elementary Procedure (EP). The EP is the unit of interaction between RAN node 711 and CN 720. S1-AP layer services can include two groups: UE-associated services and non-UE-associated services. These services perform functions, including but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transfer.

[0144] The Stream Control Transmission Protocol (SCTP) layer (or SCTP / IP layer) 1014 can, in part, rely on the IP protocol supported by IP layer 1013 to ensure reliable delivery of signaling messages between RAN node 711 and MME 721. L2 layer 1012 and L1 layer 1011 can refer to the communication links (e.g., wired or wireless) used by the RAN node and MME to exchange information.

[0145] RAN node 711 and MME 721 can use the S1-MME interface to exchange control plane data via a protocol stack including L1 layer 1011, L2 layer 1012, IP layer 1013, SCTP layer 1014 and S1-AP layer 1015.

[0146] Figure 11This is an illustration of a user plane protocol stack according to some embodiments. In this embodiment, user plane 1100 is shown as a communication protocol stack between UE 701 (or UE 702), RAN node 711 (or RAN node 712), S-GW 722, and P-GW 723. User plane 1100 may utilize at least some of the same protocol layers as control plane 1000. For example, UE 701 and RAN node 711 may use a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including PHY layer 1001, MAC layer 1002, RLC layer 1003, and PDCP layer 1004.

[0147] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1104 can be used to carry user data within the GPRS core network and between the radio access network and the core network. The transmitted user data can be packets in formats such as IPv4, IPv6, or PPP. The UDP and IP Security (UDP / IP) layer 1103 provides checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on selected data streams. RAN node 711 and S-GW 722 can utilize the S1-U interface to exchange user plane data via a protocol stack including L1 layer 1011, L2 layer 1012, UDP / IP layer 1103, and GTP-U layer 1104. The S-GW 722 and P-GW 723 can utilize the S5 / S8a interface to exchange user plane data via a protocol stack including L1 layer 1011, L2 layer 1012, UDP / IP layer 1103, and GTP-U layer 1104. (As mentioned above...) Figure 10 The NAS protocol supports the mobility and session management process of UE 701 to establish and maintain IP connectivity between UE 701 and P-GW 723.

[0148] Figure 12 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 12A schematic representation of hardware resource 1200 is shown, which includes one or more processors (or processor cores) 1210, one or more memory / storage devices 1220, and one or more communication resources 1230, each of which can be communicatively coupled via bus 1240. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1202 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1200.

[0149] Processor 1210 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (e.g., baseband processing circuitry), an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1212 and processor 1214.

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

[0151] Communication resource 1230 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1204 or one or more databases 1206 via network 1208. For example, communication resource 1230 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, etc. Components (e.g., low energy consumption) ), Components and other communication components.

[0152] Instructions 1250 may include software, programs, applications, applets, or other executable code for causing at least any one of the processors 1210 to perform any one or more of the methods discussed herein. Instructions 1250 may reside wholly or partially within at least one of the processors 1210 (e.g., within the processor's cache memory), within memory / storage device 1220, or any suitable combination thereof. Furthermore, any portion of instructions 1250 may be transferred to hardware resource 1200 from any combination of peripheral device 1204 or database 1206. Therefore, the memory of processor 1210, memory / storage device 1220, peripheral device 1204, and database 1206 are examples of computer-readable and machine-readable media.

[0153] In some embodiments, any of the electronic devices, networks, systems, chips, or components shown and described herein, or portions thereof, in any of the accompanying drawings may be configured to perform one or more of the processes, techniques, or methods described herein, or a portion thereof.

[0154] In some embodiments, Figures 7-12 Or one or more electronic devices, networks, systems, chips, or components, or portions thereof, shown in other figures herein, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein in connection with the embodiments.

[0155] Example

[0156] Example 1 includes an apparatus for a new radio (NR) user equipment, the apparatus including baseband circuitry including: a radio frequency (RF) interface; and one or more processors for: encoding a plurality of transport blocks (TBs); encoding a first uplink transmission using the TBs in an unlicensed mode to an NR evolved Node B (gNodeB); decoding downlink control information (DCI) from the gNodeB; encoding a second uplink transmission using the TBs to the gNodeB based on the DCI, wherein the second uplink transmission is in either an unlicensed mode or a licensed mode, and wherein the DCI includes information relating to an identifier (ID) (HARQ processing ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ processing ID being based on a resource configuration index corresponding to the second uplink transmission; and transmitting the TBs, the encoded first uplink transmission, and the encoded second uplink transmission to the RF interface.

[0157] Example 2 includes the subject of Example 1, and optionally, wherein the HARQ processing ID includes a plurality of HARQ processing IDs, and the HARQ processing includes a plurality of HARQ processing corresponding to a corresponding HARQ processing ID in the HARQ processing ID and corresponding to a corresponding TB in the TB.

[0158] Example 3 includes the subject of Example 2, and optionally, wherein the one or more processors are used to: encode the TB based on a single resource configuration.

[0159] Example 4 includes the subject of Example 1, and optionally, the one or more processors are configured to: encode the TB based on a single resource configuration, and wherein the HARQ process is a single HARQ process corresponding to the single resource configuration.

[0160] Example 5 includes the subject of Example 2, and optionally, wherein the one or more processors are used to encode the TB based on a plurality of resource configurations, and wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0161] Example 6 includes the subject of Example 5, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0162] Example 7 includes the subject of Example 6, and optionally, wherein the one or more processors are further configured to: decode semi-static signaling from the gNodeB, the semi-static signaling including information about the HPN.

[0163] Example 8 includes the subject of Example 6, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0164] Example 9 includes the subject of Example 6, and optionally, wherein the one or more processors are further configured to: encode a subset of TBs within a corresponding resource configuration in the resource configuration for transmission, such that each corresponding resource configuration in the resource configuration includes a plurality of transmission opportunities that are staggered in time, and wherein each HPN is based on a transmission parameter of a first repetition of K repetitions of a corresponding transmission opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0165] Example 10 includes the subject of Example 9, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0166] Example 11 includes the subject of Example 6, and optionally, the second uplink transmission is in unlicensed mode, and the HPN consists of an HPN for unlicensed transmission.

[0167] Example 12 includes the subject of Example 2, and optionally, wherein the DCI further includes a Layer 1 indication for the one or more processors, the Layer 1 indication indicating a switch from the unlicensed mode to the licensed mode for a given TB, the one or more processors being further configured to: monitor and decode the Layer 1 indication to switch from the unlicensed mode for the first uplink transmission to the licensed mode for the second uplink transmission.

[0168] Example 13 includes the subject of Example 12, and optionally, wherein: the unlicensed mode is based on semi-static resource configuration; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and wherein the DCI includes Cyclic Redundancy Check (CRC), which is scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an unlicensed C-RNTI (GF-C-RNTI).

[0169] Example 14 includes the subject of Example 12, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0170] Example 15 includes the subject of Example 13, and optionally, the second uplink transmission is an uplink retransmission based on the grant mode.

[0171] Example 16 includes the subject of Example 12, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0172] Example 17 includes the subject of Example 13, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes Cyclic Redundancy Check (CRC) scrambled with a regular Cell Radio Network Temporary Identifier (C-RNTI).

[0173] Example 18 includes the subject matter of any one of Examples 13 and 16, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the first uplink transmission.

[0174] Example 19 includes the subject matter of Example 1, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the one or more processors are configured to: determine HPN mapping rules based on signaling from the gNodeB regarding the mapping from HPN to the global HARQ processing pool; and encode the second uplink transmission using the HPN mapping rules, based on the global HARQ processing pool.

[0175] Example 20 includes the subject of Example 19, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0176] Example 21 includes the subject of Example 19, and optionally, the signaling includes Radio Resource Control (RRC) signaling.

[0177] Example 22 includes the subject matter of Example 20, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); and a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the one or more processors being configured to implement the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0178] Example 23 includes the subject matter of Example 20, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the one or more processors are configured to implement mapping rules based on the CRC to dynamically partition the global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0179] Example 24 includes the subject matter of Example 20, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0180] Example 25 includes the subject of Example 9, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0181] Example 26 includes the subject of Example 1, and optionally also includes a front-end module coupled to the one or more processors.

[0182] Example 27 includes the subject of Example 26, and optionally includes at least one antenna coupled to the front-end module.

[0183] Example 28 includes a method to be executed at one or more processors in the baseband circuitry of a new radio (NR) user equipment, the method comprising: encoding a plurality of transport blocks (TBs); encoding a first uplink transmission using the TBs and traveling to an NR evolved Node B (gNodeB) in an unlicensed mode; decoding downlink control information (DCI) from the gNodeB; encoding a second uplink transmission using the TBs and traveling to the gNodeB based on the DCI, wherein the second uplink transmission is in either an unlicensed mode or a licensed mode, and wherein the DCI includes information relating to an identifier (ID) (HARQ processing ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ processing ID being based on a resource configuration index corresponding to the second uplink transmission; and transmitting the TBs, the encoded first uplink transmission, and the encoded second uplink transmission to the RF interface.

[0184] Example 29 includes the subject of Example 28, and optionally, wherein the HARQ processing ID includes a plurality of HARQ processing IDs, and the HARQ processing includes a plurality of HARQ processing corresponding to a corresponding HARQ processing ID in the HARQ processing IDs and corresponding to a corresponding TB in the TB.

[0185] Example 30 includes the subject of Example 29, and optionally also includes: encoding the TB based on a single resource configuration.

[0186] Example 31 includes the subject of Example 28, and optionally further includes: encoding the TB based on a single resource configuration, wherein the HARQ process is a single HARQ process corresponding to the single resource configuration.

[0187] Example 32 includes the subject of Example 29, and optionally further includes encoding the TB based on a plurality of resource configurations, wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0188] Example 33 includes the subject of Example 32, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0189] Example 34 includes the subject of Example 33, and optionally further includes: decoding semi-static signaling from the gNodeB, the semi-static signaling including information about the HPN.

[0190] Example 35 includes the subject of Example 33, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0191] Example 36 includes the subject of Example 33 and optionally further includes: encoding a subset of TBs within a corresponding resource configuration in the resource configuration for transmission, such that each corresponding resource configuration in the resource configuration includes multiple transmission opportunities that are staggered in time, and wherein each HPN is based on a transmission parameter of a first repetition of K repetitions of a corresponding transmission opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0192] Example 37 includes the subject matter of Example 36, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0193] Example 38 includes the subject of Example 33, and optionally, wherein the second uplink transmission is in unlicensed mode, and wherein the HPN consists of an HPN for unlicensed transmission.

[0194] Example 39 includes the subject of Example 29, and optionally, wherein the DCI further includes a Layer 1 indication for the one or more processors, the Layer 1 indication indicating a switch from the unlicensed mode to the licensed mode for a given TB, the one or more processors being further configured to: monitor and decode the Layer 1 indication to switch from the unlicensed mode for the first uplink transmission to the licensed mode for the second uplink transmission.

[0195] Example 40 includes the subject matter of Example 39, and optionally, wherein: the unlicensed mode is based on semi-static resource configuration; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and the DCI includes Cyclic Redundancy Check (CRC) scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an unlicensed C-RNTI (GF-C-RNTI).

[0196] Example 41 includes the subject of Example 39, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0197] Example 42 includes the subject of Example 40, and optionally, the second uplink transmission is an uplink retransmission based on the grant mode.

[0198] Example 43 includes the subject of Example 39, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0199] Example 44 includes the subject of Example 40, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes Cyclic Redundancy Check (CRC) scrambled with a regular Cell Radio Network Temporary Identifier (C-RNTI).

[0200] Example 45 includes the subject of Example 40, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the second uplink transmission.

[0201] Example 46 includes the subject of Example 28, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the method further includes: determining HPN mapping rules based on signaling from the gNodeB regarding the mapping from HPN to the global HARQ processing pool; and encoding the second uplink transmission using the HPN mapping rules, based on the global HARQ processing pool.

[0202] Example 47 includes the subject of Example 46, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0203] Example 48 includes the subject of Example 46, and optionally, the signaling includes Radio Resource Control (RRC) signaling.

[0204] Example 49 includes the subject matter of Example 47, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from an unlicensed mode to a licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from an unlicensed mode for the first uplink transmission to a licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); and a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the method further includes implementing the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0205] Example 50 includes the subject matter of Example 47, and optionally, wherein: DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the method further includes implementing mapping rules based on the CRC to dynamically partition a global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0206] Example 51 includes the subject matter of Example 47, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0207] Example 52 includes the subject of Example 36, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0208] Example 53 includes a product comprising one or more computer-readable storage media (which may be tangible and non-transitory), the one or more computer-readable storage media including computer-executable instructions operable to cause the one or more processors to perform operations at the UE when executed by one or more processors of the baseband circuitry of a New Radio (NR) User Equipment (UE), the operations including: encoding a plurality of transport blocks (TBs) and encoding a first uplink transmission using the TBs and in unlicensed mode to an NR Evolved Node B (gNodeB); and encoding downlink control information from the gNodeB. (DCI) is decoded; based on the DCI, a second uplink transmission using the TB and destined for the gNodeB is encoded, wherein the second uplink transmission is in either an unlicensed mode or a licensed mode, and wherein the DCI includes information related to an identifier (ID) (HARQ Processor ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ Processor ID being based on a resource configuration index corresponding to the second uplink transmission; and the TB, the encoded first uplink transmission, and the encoded second uplink transmission are sent to the RF interface.

[0209] Example 54 includes the subject of Example 53, and optionally, wherein the HARQ processing ID includes a plurality of HARQ processing IDs, and the HARQ processing includes a plurality of HARQ processing corresponding to a corresponding HARQ processing ID in the HARQ processing IDs and corresponding to a corresponding TB in the TB.

[0210] Example 55 includes the subject of Example 54, and optionally also includes: encoding the TB based on a single resource configuration.

[0211] Example 56 includes the subject of Example 53, and optionally further includes: encoding the TB based on a single resource configuration, wherein the HARQ process is a single HARQ process corresponding to the single resource configuration.

[0212] Example 57 includes the subject of Example 54, and optionally further includes encoding the TB based on a plurality of resource configurations, wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0213] Example 58 includes the subject of Example 57, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0214] Example 59 includes the subject of Example 58, and optionally further includes: decoding semi-static signaling from the gNodeB, the semi-static signaling including information about the HPN.

[0215] Example 60 includes the subject of Example 58, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0216] Example 61 includes the subject of Example 58 and optionally further includes: encoding a subset of TBs within a corresponding resource configuration in the resource configuration for transmission, such that each corresponding resource configuration in the resource configuration includes multiple transmission opportunities that are staggered in time, and wherein each HPN is based on a transmission parameter of a first repetition of K repetitions of a corresponding transmission opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0217] Example 62 includes the subject matter of Example 61, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0218] Example 63 includes the subject of Example 58, and optionally, wherein the second uplink transmission is in unlicensed mode, and wherein the HPN consists of an HPN for unlicensed transmission.

[0219] Example 64 includes the subject of Example 54, and optionally, wherein the DCI further includes a Layer 1 indication for the one or more processors, the Layer 1 indication indicating a switch from the unlicensed mode to the licensed mode for a given TB, the one or more processors being further configured to: monitor and decode the Layer 1 indication to switch from the unlicensed mode for the first uplink transmission to the licensed mode for the second uplink transmission.

[0220] Example 65 includes the subject matter of Example 64, and optionally, wherein: the unlicensed mode is based on semi-static resource configuration; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and the DCI includes Cyclic Redundancy Check (CRC) scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an unlicensed C-RNTI (GF-C-RNTI).

[0221] Example 66 includes the subject of Example 64, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0222] Example 67 includes the subject of Example 65, and optionally, the second uplink transmission is an uplink retransmission based on the grant mode.

[0223] Example 68 includes the subject matter of Example 64, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0224] Example 69 includes the subject matter of Example 65, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes Cyclic Redundancy Check (CRC) scrambled with a regular Cell Radio Network Temporary Identifier (C-RNTI).

[0225] Example 70 includes the subject matter of any one of Examples 65 and 68, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the second uplink transmission.

[0226] Example 71 includes the subject matter of Example 53, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the operation further includes: determining HPN mapping rules based on signaling from the gNodeB regarding the mapping from HPN to the global HARQ processing pool; and encoding the second uplink transmission using the HPN mapping rules, based on the global HARQ processing pool.

[0227] Example 72 includes the subject of Example 71, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0228] Example 73 includes the subject matter of Example 71, and optionally, the signaling includes Radio Resource Control (RRC) signaling.

[0229] Example 74 includes the subject matter of Example 72, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from an unlicensed mode to a licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from an unlicensed mode for the first uplink transmission to a licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); and a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the operation further includes implementing the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0230] Example 75 includes the subject matter of Example 72, and optionally, wherein: DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the operation further includes implementing mapping rules based on the CRC to dynamically partition a global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0231] Example 76 includes the subject matter of Example 72, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0232] Example 77 includes the subject of Example 61, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0233] Example 78 includes an apparatus for a novel radio (NR) user equipment, the apparatus comprising: means for encoding a plurality of transport blocks (TBs); means for encoding a first uplink transmission using the TBs and destined for an NR evolved Node B (gNodeB) in an unlicensed mode; means for decoding downlink control information (DCI) from the gNodeB; means for encoding a second uplink transmission using the TBs and destined for the gNodeB based on the DCI, wherein the second uplink transmission is in either an unlicensed mode or a licensed mode, and wherein the DCI includes information relating to an identifier (ID) (HARQ processing ID) of a Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) process corresponding to the second uplink transmission, the HARQ processing ID being based on a resource configuration index corresponding to the second uplink transmission; and means for transmitting the TBs, the encoded first uplink transmission, and the encoded second uplink transmission to an RF interface.

[0234] Example 79 includes the subject of Example 78, and optionally, wherein the HARQ processing ID includes a plurality of HARQ processing IDs, and the HARQ processing includes a plurality of HARQ processing corresponding to a corresponding HARQ processing ID in the HARQ processing IDs and corresponding to a corresponding TB in the TB.

[0235] Example 80 includes the subject of Example 78, and optionally further includes: means for encoding the TB based on a single resource configuration, wherein the HARQ process is a single HARQ process corresponding to the single resource configuration.

[0236] Example 81 includes an apparatus for a New Radio (NR) Evolutionary Node B (gNodeB), the apparatus comprising: a memory having a buffer corresponding to Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) processing; and one or more processors coupled to the memory, the one or more processors being configured to: decode a first uplink transmission from an NR User Equipment (UE) in an unlicensed mode; encode downlink control information (DCI) and cause the DCI to be transmitted to the NR UE; and decode a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ processing ID) of the HARQ processing corresponding to the second uplink transmission; and decoding the second uplink transmission includes implementing the HARQ processing.

[0237] Example 82 includes the subject of Example 81, and optionally, the buffer includes a plurality of buffers, the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to a corresponding HARQ process ID in the HARQ process IDs and corresponding to a corresponding buffer in the buffer.

[0238] Example 83 includes the subject of Example 82, and optionally, the first uplink transport and the second uplink transport are based on a single resource configuration.

[0239] Example 84 includes the subject of Example 83, and optionally, wherein the HARQ processing is a single HARQ processing corresponding to the single resource configuration.

[0240] Example 85 includes the subject of Example 82, and optionally, wherein the first transmission and the second transmission are each based on a plurality of resource configurations, and wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0241] Example 86 includes the subject of Example 85, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0242] Example 87 includes the subject of Example 86, and optionally, wherein the one or more processors are further configured to: encode semi-static signaling, the semi-static signaling including information about the HPN, the semi-static signaling being transmitted to the NR UE.

[0243] Example 88 includes the subject of Example 86, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0244] Example 89 includes the subject of Example 86, and optionally, each corresponding resource configuration in the resource configuration includes multiple time-staggered transport opportunities and multiple transport blocks, and each HPN in the HPN is based on the transport parameters of the first repetition of K repetitions of a corresponding transport opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0245] Example 90 includes the subject matter of Example 89, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0246] Example 91 includes the subject of Example 86, and optionally, the second uplink transmission is in unlicensed mode, and the HPN consists of an HPN for unlicensed transmission.

[0247] Example 92 includes the subject of Example 82, and optionally, the DCI further includes a Layer 1 indication for the NR UE for switching from an unlicensed mode of the first uplink transmission to a licensed mode of the second uplink transmission.

[0248] Example 93 includes the subject matter of Example 92, and optionally, wherein: the one or more processors are configured to implement semi-static resource configuration of the NR UE in unlicensed mode; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and the DCI includes a Cyclic Redundancy Check (CRC) scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an Unlicensed C-RNTI (GF-C-RNTI).

[0249] Example 94 includes the subject of Example 92, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0250] Example 95 includes the subject of Example 93, and optionally, wherein the second uplink transmission is an uplink retransmission based on the grant mode.

[0251] Example 96 includes the subject matter of Example 92, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0252] Example 97 includes the subject matter of Example 93, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes Cyclic Redundancy Check (CRC) scrambled with a regular Cell Radio Network Temporary Identifier (C-RNTI).

[0253] Example 98 includes the subject matter of Examples 93 and 96, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the second uplink transmission.

[0254] Example 99 includes the subject matter of Example 81, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the one or more processors are configured to: encode signaling regarding the mapping from the HPN to the global HARQ processing pool based on mapping rules, the signaling being transmitted to the NR UE; and encode the second uplink transmission based on the HPN mapping rules and based on the global HARQ processing pool.

[0255] Example 100 includes the subject of Example 99, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0256] Example 101 includes the subject of Example 99, and optionally, the signaling said therein includes Radio Resource Control (RRC) signaling.

[0257] Example 102 includes the subject matter of Example 100, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from an unlicensed mode to a licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from an unlicensed mode for the first uplink transmission to a licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); and a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the one or more processors are configured to implement the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0258] Example 103 includes the subject matter of Example 100, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the one or more processors are configured to implement mapping rules based on the CRC to dynamically partition a global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0259] Example 104 includes the subject matter of Example 100, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0260] Example 105 includes the subject of Example 89, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0261] Example 106 includes the subject of Example 81, and optionally also includes a front-end module coupled to the one or more processors.

[0262] Example 107 includes the subject of Example 106, and optionally includes at least one antenna coupled to the front-end module.

[0263] Example 108 includes a method to be executed at one or more processors in a New Radio (NR) Evolution Node B (gNodeB), the NR gNodeB including a memory having a buffer corresponding to Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) processing, the one or more processors being coupled to the memory, the method comprising: decoding a first uplink transmission from an NR User Equipment (UE) in an unlicensed mode; encoding downlink control information (DCI) for transmission to the NR UE; and decoding a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ processing ID) of the HARQ processing corresponding to the second uplink transmission; and decoding the second uplink transmission includes implementing the HARQ processing.

[0264] Example 109 includes the subject of Example 108, and optionally, the buffer includes a plurality of buffers, the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to a corresponding HARQ process ID in the HARQ process IDs and corresponding to a corresponding buffer in the buffer.

[0265] Example 110 includes the subject of Example 109, and optionally, the first uplink transport and the second uplink transport are based on a single resource configuration.

[0266] Example 111 includes the subject of Example 110, and optionally, the HARQ processing is a single HARQ processing corresponding to the single resource configuration.

[0267] Example 112 includes the subject of Example 109, and optionally, wherein the first transmission and the second transmission are each based on a plurality of resource configurations, and wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0268] Example 113 includes the subject of Example 112, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0269] Example 114 includes the subject of Example 113, and optionally further includes: encoding semi-static signaling for transmission to the NR UE, the semi-static signaling including information about the HPN.

[0270] Example 115 includes the subject of Example 113, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0271] Example 116 includes the subject of Example 113, and optionally, each corresponding resource configuration in the resource configuration includes multiple time-staggered transport opportunities and multiple transport blocks, and each HPN in the HPN is based on the transport parameters of the first repetition of K repetitions of a corresponding transport opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0272] Example 117 includes the subject matter of Example 116, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0273] Example 118 includes the subject of Example 113, and optionally, wherein the second uplink transmission is in unlicensed mode, and wherein the HPN consists of an HPN for unlicensed transmission.

[0274] Example 119 includes the subject of Example 109, and optionally, the DCI further includes a Layer 1 indication for the NR UE for switching from an unlicensed mode of the first uplink transmission to a licensed mode of the second uplink transmission.

[0275] Example 120 includes the subject matter of Example 119, and optionally, wherein: the method includes implementing a semi-static resource configuration for an NR UE in unlicensed mode; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and the DCI includes a Cyclic Redundancy Check (CRC) scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an Unlicensed C-RNTI (GF-C-RNTI).

[0276] Example 121 includes the subject of Example 119, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0277] Example 122 includes the subject of Example 120, and optionally, the second uplink transmission is an uplink retransmission based on the grant mode.

[0278] Example 123 includes the subject matter of Example 119, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0279] Example 124 includes the subject matter of Example 120, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes a cyclic redundancy check (CRC) scrambled with a regular cell radio network temporary identifier (C-RNTI).

[0280] Example 125 includes the subject of Example 120, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the second uplink transmission.

[0281] Example 126 includes the subject matter of Example 108, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the method further includes: encoding signaling regarding the mapping from the HPN to the global HARQ processing pool based on mapping rules for transmission to the NRUE; and encoding the second uplink transmission based on the HPN mapping rules and based on the global HARQ processing pool.

[0282] Example 127 includes the subject of Example 126, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0283] Example 128 includes the subject of Example 126, and optionally, the signaling includes Radio Resource Control (RRC) signaling.

[0284] Example 129 includes the subject matter of Example 127, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from an unlicensed mode to a licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from an unlicensed mode for the first uplink transmission to a licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); and a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the method further includes implementing the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0285] Example 130 includes the subject matter of Example 127, and optionally, wherein: DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the method further includes implementing mapping rules based on the CRC to dynamically partition a global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0286] Example 131 includes the subject matter of Example 127, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0287] Example 132 includes the subject of Example 116, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0288] Example 133 includes a product comprising one or more computer-readable storage media (which may be tangible and non-transitory), the one or more computer-readable storage media including computer-executable instructions operable to cause the one or more processors of a New Radio Evolution Node B (gNodeB) to perform operations at a UE when executed, the operations including: decoding a first uplink transmission from an NR user equipment (UE) in an unlicensed mode; encoding downlink control information (DCI) for transmission to the NR UE; and decoding a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ processing ID) of a Hybrid Automatic Repeat Request (HARQ) processing corresponding to the second uplink transmission; and decoding the second uplink transmission includes implementing the HARQ processing.

[0289] Example 134 includes the subject of Example 133, and optionally, the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to a corresponding HARQ process ID in the HARQ process IDs.

[0290] Example 135 includes the subject of Example 134, and optionally, the first uplink transport and the second uplink transport are based on a single resource configuration.

[0291] Example 136 includes the subject of Example 135, and optionally, wherein the HARQ processing is a single HARQ processing corresponding to the single resource configuration.

[0292] Example 137 includes the subject of Example 134, and optionally, wherein the first transmission and the second transmission are each based on a plurality of resource configurations, and wherein: a corresponding subset of the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations; or a corresponding HARQ process in the plurality of HARQ processes corresponds to a corresponding resource configuration in the plurality of resource configurations.

[0293] Example 138 includes the subject of Example 137, and optionally, the HARQ processing ID is associated with a corresponding HARQ processing number (HPN).

[0294] Example 139 includes the subject of Example 138 and optionally further includes: encoding semi-static signaling, the semi-static signaling including information about the HPN, the semi-static signaling being used for transmission to the NR UE.

[0295] Example 140 includes the subject of Example 138, and optionally, each HARQ processing ID in the HARQ processing IDs is based on a corresponding resource configuration index of the resource configuration corresponding to each HARQ processing ID.

[0296] Example 141 includes the subject of Example 138, and optionally, each corresponding resource configuration in the resource configuration includes multiple time-staggered transport opportunities and multiple transport blocks, and each HPN in the HPN is based on the transport parameters of the first repetition of K repetitions of a corresponding transport opportunity within a corresponding resource configuration in the resource configuration, or each HPN is based on a resource configuration index of a corresponding resource configuration in the resource configuration.

[0297] Example 142 includes the subject matter of Example 141, and optionally, the transmission parameters include at least one of the following: demodulation reference signal (DM-RS), synchronization preamble in the physical uplink shared channel (PUSCH), or scrambling seed.

[0298] Example 143 includes the subject of Example 138, and optionally, wherein the second uplink transmission is in unlicensed mode, and wherein the HPN consists of an HPN for unlicensed transmission.

[0299] Example 144 includes the subject of Example 134, and optionally, the DCI further includes a Layer 1 indication for the NR UE for switching from an unlicensed mode of the first uplink transmission to a licensed mode of the second uplink transmission.

[0300] Example 145 includes the subject matter of Example 144, and optionally, wherein: the operation includes implementing a semi-static resource configuration of the NR UE in unlicensed mode; the Layer 1 indication is also an indication for activating, deactivating, or modifying transmission parameters between the first uplink transmission and the second uplink transmission; and the DCI includes a Cyclic Redundancy Check (CRC) scrambled with a Semi-Persistent Scheduling (SPS) Cell Radio Network Temporary Identifier (C-RNTI) (SPS-C-RNTI) or an Unlicensed C-RNTI (GF-C-RNTI).

[0301] Example 146 includes the subject of Example 144, and optionally, the Layer 1 indication does not include indications for activating, deactivating, or modifying transmission parameters between the first transmission and the second transmission, and the DCI includes a Cyclic Redundancy Check (CRC) value scrambled with a Conventional Cell Radio Network Temporary Identifier (C-RNTI).

[0302] Example 147 includes the subject of Example 145, and optionally, the second uplink transmission is an uplink retransmission based on the grant mode.

[0303] Example 148 includes the subject matter of Example 144, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the licensed mode; the DCI includes a cyclic redundancy check (CRC) scrambled with an unlicensed cell radio network temporary identifier (GF-C-RNTI) configured in a UE-specific manner.

[0304] Example 149 includes the subject matter of Example 145, and optionally, wherein: the second uplink transmission is an uplink retransmission based on the grant mode; the DCI includes Cyclic Redundancy Check (CRC) scrambled with a regular Cell Radio Network Temporary Identifier (C-RNTI).

[0305] Example 150 includes the subject matter of any one of Examples 145 and 148, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); and the DCI includes a HARQ processing ID field that indicates each HPN in the HARQ processing used for the second uplink transmission.

[0306] Example 151 includes the subject matter of Example 133, and optionally, wherein: the second uplink transmission is in unlicensed mode; a HARQ processing ID is associated with a corresponding HARQ processing number (HPN); the DCI includes an indication of the HPN; HARQ processing is based on a global HARQ processing pool associated with unlicensed and licensed transmissions from the UE; the operation further includes: encoding signaling regarding the mapping from the HPN to the global HARQ processing pool based on mapping rules for transmission to the NRUE; and encoding the second uplink transmission based on the HPN mapping rules and based on the global HARQ processing pool.

[0307] Example 152 includes the subject of Example 151, and optionally, the HPN mapping rules are based on a partition of the global HARQ processing pool between unlicensed initial transports and licensed initial transports.

[0308] Example 153 includes the subject of Example 151, and optionally, the signaling includes Radio Resource Control (RRC) signaling.

[0309] Example 154 includes the subject matter of Example 152, and optionally, wherein: the DCI includes: a Layer 1 indication for the one or more processors to switch from an unlicensed mode to a licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from an unlicensed mode for the first uplink transmission to a licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI); a HARQ Processing ID field; and the mapping rule includes using the DCI to indicate the HPN in the HARQ Processing ID field; the operation further includes implementing the mapping rule by decoding the HARQ Processing ID field of the DCI.

[0310] Example 155 includes the subject matter of Example 152, and optionally, wherein: DCI includes: a Layer 1 indication for the one or more processors to switch from unlicensed mode to licensed mode for a given TB, the one or more processors also being configured to monitor and decode the Layer 1 indication to switch from unlicensed mode for the first uplink transmission to licensed mode for the second uplink transmission; a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) different from the Cell RNTI (C-RNTI); a HARQ processing ID field; and the operation further includes implementing mapping rules based on the CRC to dynamically partition a global HARQ processing pool between unlicensed initial transmissions and licensed initial transmissions.

[0311] Example 156 includes the subject matter of Example 152, and optionally, wherein: the range of the number of HARQ processes is from X_GFmin to X_GFmax for unlicensed initial transmissions and from X_GBmin to X_GBmax for regular licensed transmissions; X_GFmin, X_GBmin, X_GFmax, and X_GBmax are configured; X_GFmin and X_GBmin correspond to the minimum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively; and X_GFmax and X_GBmax correspond to the maximum number of HARQ processes reserved for unlicensed initial transmissions and licensed transmissions, respectively.

[0312] Example 157 includes the subject of Example 141, and optionally, wherein: HARQ processing is semi-statically partitioned across resource configurations; and HARQ processing IDs are defined according to a two-stage HARQ processing ID process, the first stage of which includes determining a set of one or more HARQ processing IDs for each resource configuration, and the second stage including determining the HARQ processing ID corresponding to one or more HARQ processings associated with each resource configuration based on the resource index of each transport opportunity within the resource configuration.

[0313] Example 158 includes an apparatus for a New Radio (NR) Evolution Node B (gNodeB) comprising a memory and one or more processors coupled to the memory, the memory having a buffer corresponding to Hybrid Automatic Repeat Request Acknowledgment Feedback (HARQ) processing, the one or more processors including: means for decoding a first uplink transmission from an NR User Equipment (UE) in an unlicensed mode; means for encoding downlink control information (DCI) to transmit the DCI to the NR UE; and means for decoding a second uplink transmission from the NR UE, wherein: the second uplink transmission is in either an unlicensed mode or a licensed mode; the DCI includes information relating to an identifier (ID) (HARQ Processing ID) of the HARQ processing corresponding to the second uplink transmission; and the means for decoding the second uplink transmission includes means for implementing the HARQ processing.

[0314] Example 159 includes the subject of Example 158, and optionally, the buffer includes a plurality of buffers, the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to a corresponding HARQ process ID in the HARQ process IDs and corresponding to a corresponding buffer in the buffer.

[0315] Example 160 includes the subject of Example 159, and optionally, the first uplink transport and the second uplink transport are based on a single resource configuration.

[0316] Example 161 includes an apparatus for a novel radio (NR) user equipment, the apparatus including baseband processing circuitry including an RF interface and one or more processors for: determining a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH); encoding a first signal to be transmitted on the PUCCH, the first signal including uplink control information (UCI); encoding a second signal to be transmitted on the PUSCH in unlicensed mode; and such that at least one of the first signal and the second signal is transmitted in a time slot according to a priority rule between the first signal and the second signal.

[0317] Example 162 includes the subject of Example 161, and optionally, the one or more processors are configured to: implement a priority rule based on at least one of the following: a corresponding set of parameters for the transmission of the first signal and the transmission of the second signal, the content of the UCI, or whether to use a short PUCCH or a long PUCCH to carry the UCI.

[0318] Example 163 includes the subject of Example 161, and optionally, the priority rule therein conforms to one of the following: is predefined, and is configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or Radio Resource Control signaling.

[0319] Example 164 includes the subject of Example 161, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal of any UCI type, and the one or more processors are configured to: implement the priority rule by discarding the first signal and causing the second signal to be sent when the second signal corresponds to a URLLC signal.

[0320] Example 165 includes the subject matter of Example 161, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Channel State Information (CSI) report or a beam correlation report, and a priority rule assigns a lower priority to a second signal corresponding to a URLLC signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback, wherein the one or more processors are configured to: implement the priority rule by discarding the first signal and causing the second signal to be transmitted when the second signal corresponds to a URLLC signal and the first signal corresponds to a CSI report or a beam correlation report, and implement the priority rule by discarding the second signal and causing the first signal to be transmitted when the second signal corresponds to a URLLC signal and the first signal corresponds to a HARQ-ACK signal.

[0321] Example 166 includes the subject of Example 161, and optionally, wherein a priority rule assigns a lower priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback on a short PUCCH, the one or more processors being configured to: implement the priority rule by causing the transmission of the first signal and by delaying the transmission of the second signal to the next available configuration resource when the first signal corresponds to a HARQ-ACK feedback, the PUCCH is a short PUCCH, and the second signal corresponds to a URLLC signal.

[0322] Example 167 includes the subject of Example 161, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal compared to a first signal, and the one or more processors are configured to: implement the priority rule to stop sending the first signal but send the second signal when the second signal corresponds to a URLLC signal and the first signal and the second signal conflict in time.

[0323] Example 168 includes the subject of Example 161, and optionally, wherein a priority rule assigns the same priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal as to a first signal, and the one or more processors are configured to: implement the priority rule to transmit the first signal and the second signal simultaneously when the second signal corresponds to the URLLC signal, and when the first signal and the second signal conflict in time but not in frequency.

[0324] Example 169 includes a method to be performed at the baseband circuitry of a new radio (NR) user equipment, the method comprising: determining a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH); encoding a first signal to be transmitted on the PUCCH, the first signal including uplink control information (UCI); encoding a second signal to be transmitted on the PUSCH in unlicensed mode; such that at least one of the first signal and the second signal is transmitted in a time slot according to a priority rule between the first signal and the second signal.

[0325] Example 170 includes the subject of Example 169, and optionally, the method further includes implementing a priority rule based on at least one of the following: a corresponding set of parameters for the transmission of the first signal and the transmission of the second signal, the content of the UCI, or whether to use a short PUCCH or a long PUCCH to carry the UCI.

[0326] Example 171 includes the subject of Example 169, and optionally, the priority rule therein conforms to one of the following: is predefined, and is configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or Radio Resource Control signaling.

[0327] Example 172 includes the subject of Example 169, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal of any UCI type, the method comprising: implementing the priority rule by discarding the first signal and causing the second signal to be transmitted when the second signal corresponds to a URLLC signal.

[0328] Example 173 includes the subject matter of Example 169, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Channel State Information (CSI) report or a beam-related report, and a priority rule assigns a lower priority to a second signal corresponding to a URLLC signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback, the method comprising: when the second signal corresponds to a URLLC signal and the first signal corresponds to a CSI report or a beam-related report, implementing the priority rule by discarding the first signal and causing the second signal to be transmitted; and when the second signal corresponds to a URLLC signal and the first signal corresponds to a HARQ-ACK signal, implementing the priority rule by discarding the second signal and causing the first signal to be transmitted.

[0329] Example 174 includes the subject of Example 169, and optionally, wherein a priority rule assigns a lower priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback on a short PUCCH, the method comprising: when the first signal corresponds to a HARQ-ACK feedback, the PUCCH is a short PUCCH, and the second signal corresponds to a URLLC signal, implementing the priority rule by causing the transmission of the first signal and by delaying the transmission of the second signal to the next available configuration resource.

[0330] Example 175 includes the subject of Example 169, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal compared to a first signal, the method comprising: implementing the priority rule to stop sending the first signal but send the second signal when the second signal corresponds to a URLLC signal and the first signal and the second signal conflict in time.

[0331] Example 176 includes the subject of Example 169, and optionally, wherein a priority rule assigns the same priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal as to a first signal, the method comprising: implementing the priority rule to transmit the first signal and the second signal simultaneously when the second signal corresponds to the URLLC signal, and when the first signal and the second signal conflict in time but not in frequency.

[0332] Example 177 includes a product comprising one or more computer-readable storage media (which may be tangible and non-transitory), the one or more computer-readable storage media including computer-executable instructions operable to cause the one or more processors of a New Radio (NR) User Equipment (UE) to perform operations at the UE when executed, the operations including: determining a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH); encoding a first signal to be transmitted on the PUCCH, the first signal including uplink control information (UCI); encoding a second signal to be transmitted on the PUSCH in unlicensed mode; and causing at least one of the first signal and the second signal to be transmitted in a time slot according to a priority rule between the first signal and the second signal.

[0333] Example 178 includes the subject of Example 177, and optionally, the operation further includes implementing a priority rule based on at least one of the following: a corresponding set of parameters for the transmission of the first signal and the transmission of the second signal, the content of the UCI, or whether to use a short PUCCH or a long PUCCH to carry the UCI.

[0334] Example 179 includes the subject of Example 177, and optionally, the priority rule therein conforms to one of the following: is predefined, and is configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or Radio Resource Control signaling.

[0335] Example 180 includes the subject of Example 177, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal of any UCI type, the operation comprising: when the second signal corresponds to a URLLC signal, implementing the priority rule by discarding the first signal and causing the second signal to be transmitted.

[0336] Example 181 includes the subject matter of Example 177, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Channel State Information (CSI) report or a beam correlation report, and a priority rule assigns a lower priority to a second signal corresponding to a URLLC signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback, the operation comprising: when the second signal corresponds to a URLLC signal and the first signal corresponds to a CSI report or a beam correlation report, implementing the priority rule by discarding the first signal and causing the second signal to be transmitted; and when the second signal corresponds to a URLLC signal and the first signal corresponds to a HARQ-ACK signal, implementing the priority rule by discarding the second signal and causing the first signal to be transmitted.

[0337] Example 182 includes the subject of Example 177, and optionally, wherein a priority rule assigns a lower priority to a second signal corresponding to an Ultra-Reliable Low-Latency Communication (URLLC) signal compared to a first signal corresponding to a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback on a short PUCCH, the operation comprising: when the first signal corresponds to a HARQ-ACK feedback, the PUCCH is a short PUCCH, and the second signal corresponds to a URLLC signal, implementing the priority rule by causing the transmission of the first signal and by delaying the transmission of the second signal to the next available configuration resource.

[0338] Example 183 includes the subject of Example 177, and optionally, wherein a priority rule assigns a higher priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal compared to a first signal, the operation including: when the second signal corresponds to a URLLC signal and the first signal and the second signal conflict in time, implementing the priority rule to stop sending the first signal but send the second signal.

[0339] Example 184 includes the subject of Example 177, and optionally, wherein a priority rule assigns the same priority to a second signal corresponding to an Ultra Reliable Low Latency Communication (URLLC) signal as to a first signal, the operation comprising: implementing the priority rule to transmit the first signal and the second signal simultaneously when the second signal corresponds to the URLLC signal, and when the first signal and the second signal conflict in time but not in frequency.

[0340] Example 185 includes an apparatus for a new radio (NR) user equipment (UE), the apparatus comprising: means for determining a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH); means for encoding a first signal to be transmitted on the PUCCH, the first signal including uplink control information (UCI); means for encoding a second signal to be transmitted on the PUSCH in unlicensed mode; and means for causing at least one of the first signal and the second signal to be transmitted in a time slot according to a priority rule between the first signal and the second signal.

[0341] Example 186 includes the subject matter of Example 185, and optionally further includes: means for implementing a priority rule based on at least one of the following: a corresponding set of parameters for the transmission of the first signal and the transmission of the second signal, the content of the UCI, or whether to use a short PUCCH or a long PUCCH to carry the UCI.

[0342] Example 187 includes the subject of Example 185, and optionally, the priority rule therein conforms to one of the following: is predefined, and is configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or Radio Resource Control signaling.

[0343] Example 188 includes a product comprising one or more computer-readable storage media (which may be tangible and non-transitory), the one or more computer-readable storage media including computer-executable instructions operable to, when executed by at least one computer processor, cause the at least one computer processor to perform the method of any one of Examples 28-52, 108-132, and 169-176.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising a baseband circuit, the baseband circuit comprising: RF circuit interface; as well as One or more processors are configured as follows: Receive one or more resource configurations for unauthorized transmission, wherein each resource configuration is identified by an associated index; Uplink transmissions are sent according to a first resource configuration in one or more resource configurations; Receive Hybrid Automatic Repeat Request (HARQ) information from the base station in the downlink channel; The HARQ process identifier ID for the HARQ information is determined based on the index of the first resource configuration and the value of the harqProcessOffset parameter used for the first resource configuration, wherein the harqProcessOffset parameter is configured on a per-resource-configuration basis; and Based on the HARQ information, subsequent uplink transmissions identified by the HARQ process ID are sent to the base station.

2. The apparatus according to claim 1, wherein the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to the corresponding HARQ process IDs in the HARQ process IDs.

3. The apparatus of claim 2, wherein the HARQ process ID is based on a value equal to {[floor(CURRENT_TTI / semiPersistSchedIntervalUL(i) modulo numberOfConfUlSPS- Processes(i) + harqProcessOffset(i)} modulo totalNumberOfConfUlSps-Processes Where i represents the index of the resource configuration, and "CURRENT_TTI" corresponds to the current transmission time interval (TTI). semiPersistSchedIntervalUL(i) "This corresponds to the scheduling time interval of the semi-persistent scheduling (SPS) for the uplink transmission UL configured for the resource with index i." numberOfConfUlSPS-Processes(i) "This corresponds to the number of HARQ procedures for the resource configuration with index i," harqProcessOffset(i) "Corresponding to the harqProcessOffset parameter configured for the resource with index i, and" totalNumberOfConfUlSps-Processes "This corresponds to the number of the plurality of HARQ procedures configured for the one or more resources." 4. The apparatus of claim 1, wherein the HARQ process ID is based on the system frame number (SFN) used for the uplink transmission.

5. The apparatus of claim 1 further includes a front-end module (FEM) coupled to the RF circuit interface.

6. The apparatus of claim 5 further includes at least one antenna coupled to the FEM.

7. A non-transient computer-readable storage medium comprising computer-executable instructions operable to, when executed by one or more processors of a user equipment (UE), enable the one or more processors to perform an operation at the UE, the operation comprising: Receive one or more resource configurations for unauthorized transmission, wherein each resource configuration is identified by an associated index; Uplink transmissions are sent according to a first resource configuration in one or more resource configurations; Receive Hybrid Automatic Repeat Request (HARQ) information from the base station in the downlink channel; The HARQ process identifier ID for the HARQ information is determined based on the index of the first resource configuration and the value of the harqProcessOffset parameter used for the first resource configuration, wherein the harqProcessOffset parameter is configured on a per-resource-configuration basis; and Based on the HARQ information, subsequent uplink transmissions identified by the HARQ process ID are sent to the base station.

8. The non-transient computer-readable storage medium of claim 7, wherein the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to the corresponding HARQ process IDs in the HARQ process IDs.

9. The non-transient computer-readable storage medium of claim 7, wherein the HARQ procedure ID is based on a value equal to {[floor(CURRENT_TTI / semiPersistSchedIntervalUL(i) modulo numberOfConfUlSPS-Processes(i) + harqProcessOffset(i)} modulo totalNumberOfConfUlSps-Processes Where i represents the index of the resource configuration, and "CURRENT_TTI" corresponds to the current transmission time interval (TTI). semiPersistSchedIntervalUL(i) "This corresponds to the scheduling time interval of the semi-persistent scheduling (SPS) for the uplink transmission UL configured for the resource with index i." numberOfConfUlSPS-Processes(i) "This corresponds to the number of HARQ procedures for the resource configuration with index i," harqProcessOffset(i) "Corresponding to the harqProcessOffset parameter configured for the resource with index i, and" totalNumberOfConfUlSps-Processes "This corresponds to the number of the plurality of HARQ procedures configured for the one or more resources." 10. The non-transient computer-readable storage medium of claim 7, wherein the HARQ procedure ID is based on the system frame number (SFN) used for the uplink transmission.

11. A method performed at a user equipment (UE), comprising: Receive one or more resource configurations for unauthorized transmission, wherein each resource configuration is identified by an associated index; Uplink transmissions are sent according to a first resource configuration in one or more resource configurations; Receive Hybrid Automatic Repeat Request (HARQ) information from the base station in the downlink channel; The HARQ process identifier ID for the HARQ information is determined based on the index of the first resource configuration and the value of the harqProcessOffset parameter used for the first resource configuration, wherein the harqProcessOffset parameter is configured on a per-resource-configuration basis; and Based on the HARQ information, subsequent uplink transmissions identified by the HARQ process ID are sent to the base station.

12. The method of claim 11, wherein the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to the corresponding HARQ process IDs in the HARQ process IDs.

13. The method of claim 11, wherein the HARQ procedure ID is based on a value equal to {[floor(CURRENT_TTI / semiPersistSchedIntervalUL]} (i) )] modulo numberOfConfUlSPS-Processes (i) + harqProcessOffset (i) } modulo totalNumberOfConfUlSps-Processes, where i represents the index of the resource configuration, "CURRENT_TTI" corresponds to the current transmission time interval TTI, and "semiPersistSchedIntervalUL (i) "Corresponding to the scheduling time interval of the semi-persistent scheduling (SPS) for the uplink transmission UL configured for the resource with index i," numberOfConfUlSPS-Processes (i) "This corresponds to the number of HARQ procedures for the resource configuration with index i," harqProcessOffset(i) "Corresponding to the harqProcessOffset parameter configured for the resource with index i, and" totalNumberOfConfUlSps-Processes "This corresponds to the number of the plurality of HARQ procedures configured for the one or more resources." 14. The method of claim 11, wherein the HARQ procedure ID is based on the system frame number (SFN) used for the uplink transmission.

15. A method performed at a base station, comprising: Send one or more resource configurations for unauthorized transmission, wherein each resource configuration is identified by an associated index and includes a configured value for the harqProcessOffset parameter, wherein the harqProcessOffset parameter is configured on a per-resource-configuration basis; Receive uplink transmissions according to a first resource configuration in one or more resource configurations; Send Hybrid Automatic Repeat Request (HARQ) information in the downlink channel; The HARQ process identifier ID for the HARQ information is determined based on the index of the first resource configuration and the value of the harqProcessOffset parameter used for the first resource configuration; and Based on the HARQ information, subsequent uplink transmissions identified by the HARQ process ID are received.

16. The method of claim 15, wherein the HARQ process ID includes a plurality of HARQ process IDs, and the HARQ process includes a plurality of HARQ processes corresponding to a corresponding HARQ process ID in the HARQ process IDs.

17. The method of claim 15, wherein the HARQ procedure ID is based on a value equal to {[floor(CURRENT_TTI / semiPersistSchedIntervalUL]} (i) )] modulo numberOfConfUlSPS-Processes (i) + harqProcessOffset (i) } modulo totalNumberOfConfUlSps-Processes, where i represents the index of the resource configuration, "CURRENT_TTI" corresponds to the current transmission time interval TTI, and "semiPersistSchedIntervalUL (i) "Corresponding to the scheduling time interval of the semi-persistent scheduling (SPS) for the uplink transmission UL configured for the resource with index i," numberOfConfUlSPS-Processes (i) "This corresponds to the number of HARQ procedures for the resource configuration with index i," harqProcessOffset(i) "Corresponding to the harqProcessOffset parameter configured for the resource with index i, and" totalNumberOfConfUlSps-Processes "This corresponds to the number of the plurality of HARQ procedures configured for the one or more resources." 18. The method of claim 15, wherein the HARQ procedure ID is based on the system frame number (SFN) used for the uplink transmission.

Images