System and method for overriding authorization for CSI-feedback

Abstract

A system and method for controlling the behavior of a grant for overriding channel state information (CSI) feedback is provided. A user equipment (UE) may control an overriding of a first grant of a first radio resource by a second grant of a second radio resource. The UE determines that the second radio resource overlaps at least partially with the first radio resource. The UE also determines a physical layer priority of the first grant of the first radio resource and the second grant of the second radio resource. The physical layer priority is configured based on at least one of the first grant of the first radio resource and the second grant of the second radio resource for transmitting CSI feedback to a base station via a physical uplink shared channel (PUSCH). The UE then generates a transmission according to the physical layer priority.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including physical layer prioritization of semi-persistent (SP) channel state information (CSI) on a physical uplink shared channel (PUSCH). Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency range 1 (FR1) may include frequency bands operating at frequencies below 6 GHz, some of which may be used by previous standards and may potentially be expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 Exemplary override limitations in a UE according to certain wireless communication systems are shown.

[0007] Figure 2 Additional exemplary override restrictions related to HARQ process IDs in accordance with certain wireless communication systems are shown.

[0008] Figure 3 A table showing exemplary combinations of high priority and low priority channels and data type combinations according to one embodiment.

[0009] Figure 4 A method for a UE according to one embodiment is shown.

[0010] Figure 5 A method for a base station according to one embodiment is shown.

[0011] Figure 6 A system according to one embodiment is shown.

[0012] Figure 7 Infrastructure equipment according to one embodiment is shown.

[0013] Figure 8 A platform according to one embodiment is shown.

[0014] Fig. 9 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0015] In wireless communication systems, there is a need to clarify the override behavior between dynamic grants (DG) and configuration grants (CG) for radio resources (i.e., time and frequency resources) that at least partially overlap each other. Some combinations of channels and / or data types do not clearly define the override behavior. It has been proposed to support physical layer priority of semi-persistent (SP) channel state information (CSI) on a physical uplink control channel (PUCCH). For some wireless communication systems, a physical layer priority of SP CSI on a physical uplink shared channel (PUSCH) may also be introduced.

[0016] However, for SP-CSI carried on PUSCH, since there is no medium access control (MAC) protocol data unit (PDU) associated with PUSCH, the applicability of the DG / CG behavior derived for certain cases needs to be determined. In addition, for aperiodic (AP)-only CSI transmissions on PUSCH, since there is no MAC PDU associated with PUSCH, the applicability of the DG / CG behavior derived for certain other cases also needs to be determined.

[0017] In certain wireless communication systems (e.g., see 3GPP Technical Specification (TS) 38.214, Rel.-15), it is not expected that a UE is scheduled by a PDCCH ending with symbol i to transmit a PUSCH on a given serving cell that overlaps in time with a transmission opportunity, wherein the UE is allowed to transmit a PUSCH with a configured grant (e.g., in accordance with 3GPP TS 38.321) starting from symbol j of the same serving cell if the end of symbol i is not at least N2 symbols before the beginning of symbol j. The value N2 in the symbol is determined according to the UE processing capability (e.g., as defined in clause 6.4 of 3GPP TS 38.214), and N2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with the configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH.

[0018] For example, Figure 1 Three cases of DG override restrictions based on CG in UE of certain wireless communication systems are shown. Figure 1 , time "C" corresponds to the start of the CG transmission opportunity 102, and time "D" corresponds to the decision point of the CG (e.g., the point at which the UE decides whether to override the CG transmission opportunity 102 with the DG PUSCH). Time C and time D are separated by the N2 symbols discussed above.

[0019] In the first illustrated case (DG before CG transmission), a first PDCCH 104 for a DG PUSCH transmission (Tx) is received by the UE to schedule a first PUSCH 106 (PUSCH-1) at least N2 symbols after receiving the first PDCCH 104, which in this example is before the start of the CG transmission opportunity 102 at time C. Since the first PDCCH 104 is received before the decision point at time D, the UE is allowed to transmit the first PUSCH 106 and the CG transmission opportunity 102 is discarded (or delayed or punctured).

[0020] In the second illustrated case (DG starts no earlier than CG transmission), a second PDCCH 108 for DG PUSCH Tx is received by the UE to schedule a second PUSCH 108 (PUSCH-2) at least N2 symbols after receiving the second PDCCH 110, which in this example is after the start of the CG transmission opportunity 102. Since the second PDCCH 108 is received before the decision point at time D, the UE is allowed to transmit the second PUSCH 110 and the CG transmission opportunity 102 is discarded (or delayed or punctured).

[0021] In the third illustrated case, a third PDCCH 112 for DG PUSCH Tx is received by the UE to schedule a third PUSCH 114 (PUSCH-3) at least N2 symbols after receiving the third PDCCH 112, which in this example is less than N2 symbols before the start of the CG transmission opportunity 102 at time C. Therefore, since the third PDCCH 112 is received by the UE after the decision point at time D, the transmission of the third PUSCH 114 is not allowed, and the UE transmits the CG transmission opportunity 102 instead.

[0022] In addition to the above Figure 1In addition to the described example, in certain wireless communication systems (e.g., see 3GPP Technical Specification (TS) 38.214, Rel.-15), if there is a transmission opportunity that allows the UE to transmit a PUSCH with a configured grant starting from symbol j to symbol i on the same serving cell with the same HARQ process (e.g., according to 3GPP TS 38.321), and if the gap between the end of the PDCCH and the beginning of symbol j is less than N2 symbols, then it is not expected that the UE is scheduled by the PDCCH ending with symbol i to transmit a PUSCH for a given hybrid automatic repeat request (HARQ) process on a given serving cell. The value N2 in the symbol is determined according to the UE processing capability (e.g., as defined in clause 6.4 of 3GPP TS 38.214), and N2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with the configured grant and the subcarrier spacing of the PDCCH that schedules the PUSCH.

[0023] For configuring uplink grants, the HARQ process identifier (ID) associated with the first symbol of the UL transmission (e.g., see 3GPP TS 38.321, Rel.-15) is derived from the equation HARQ process ID = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes, where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in a frame × numberOfSymbolsPerSlot + number of symbols in a slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively (e.g., as specified in 3GPP TS 38.211). CURRENT_symbol refers to the symbol index of the first transmission opportunity of the repetition bundle that occurs. If the configured uplink grant is activated and the associated HARQ process ID is less than nrofHARQ-Processes, the HARQ process is configured for the configured uplink grant. If the MAC entity receives both a grant in the random access response and an overlapping grant for its cell-specific radio network temporary identifier (C-RNTI) or configured scheduling radio network temporary identifier (CS-RNTI), requiring concurrent transmission on the SpCell, the MAC entity may choose to continue with the grant for its RA-RNTI or the grant for its C-RNTI or CS-RNTI.

[0024] For example, something like Figure 1 The situation discussed in Figure 2 Two additional cases of CG to DG override restrictions involving HARQ process IDs according to certain wireless communication systems are shown. Figure 2 , time C corresponds to the start of the CG transmission opportunity 202, and time D corresponds to the decision point of the CG (e.g., the point at which the UE decides whether to override the CG transmission opportunity 202 with the DG PUSCH). Time C and time D are separated by the N2 symbols discussed above. The CG transmission opportunity 202 corresponds to HARQ process IDs J and K. For example, in a given time slot, the first CG configuration (e.g., the first "0" in the first Tx or

[0303] ) may be associated with HARQ process J, and the second CG configuration (e.g., the second "0" in the third Tx or

[0303] ) may be associated with HARQ process K. Therefore, the fourth PUSCH 206 (actually two transmission opportunities that happen to occupy the same orthogonal frequency division multiplexing (OFDM) symbol) may be associated with HARQ processes {J, K}.

[0025] So, continue Figure 1 An exemplary case of Figure 2 A fourth illustrated case is included, in which a fourth PDCCH 204 for DG PUSCHTx is received by the UE to schedule a fourth PUSCH 206 (PUSCH-4) at least N2 symbols after receiving the fourth PDCCH 204. Since the fourth PDCCH 204 is received less than N2 symbols before the start of the CG transmission opportunity 202, and since both the fourth PUSCH 206 and the CG transmission opportunity 202 share the same HARQ process K, the fourth PUSCH 206 is not allowed.

[0026] In the fifth illustrated case, a fifth PDCCH 208 for DG PUSCH Tx is received by the UE to schedule a fifth PUSCH 208 (PUSCH-5) at least N2 symbols after receiving the fifth PDCCH 210. In this example, the fifth PUSCH 210 is for HARQ process ID W, which is not equal to HARQ process ID J or K. Therefore, even if the fifth PDCCH 208 is received after the decision point at time D, the fifth PUSCH 210 is allowed.

[0027] Many combinations of channels and / or data types may be considered for transmissions of different priorities. Figure 3A table of exemplary combinations of high priority (HP) and low priority (LP) channels and data type combinations according to certain embodiments is shown. The table includes HP / LP combinations of DG PUSCH with uplink shared channel (UL-SCH), CG PUSCH, aperiodic CSI (A-CSI or AP-CSI) only on PUSCH, SP-CSI on PUSCH, PUCCH with scheduling request (SR), PUCCH with beam failure recovery (BFR) information, PUCCH with HARQ acknowledgement (HARQ-ACK) for DG PDSCH, PUCCH with HARQ-ACK for semi-persistent scheduling (SPS) PDSCH, and scheduling and / or SP (S / SP) CSI on PUCCH. In some wireless communication systems, DG / CG override behavior may be defined or agreed upon for combinations shown in various shading or patterns. However, for combinations not shown highlighted or shaded, override behavior is not defined. As discussed in detail below, embodiments disclosed herein define override behaviors for combination 302 , combination 304 , combination 306 , combination 308 , combination 310 , combination 312 , combination 314 , combination 316 , and combination 318 .

[0028] In one embodiment, only AP CSI on PUSCH is considered as PUSCH with UL-SCH for DG / CG prioritization.

[0029] In another embodiment, for SP-CSI on PUSCH, the first transmission is considered to be DG PUSCH and the rest of the transmissions are considered to be CG PUSCH transmissions (such as in CG PUSCH transmissions after CG activation).

[0030] In another embodiment, the SP CSI on the PUSCH is associated with a priority level and DG / CG prioritization is used. In certain such embodiments, the UE may send a UE capability message to the base station to indicate support for SP CSI on the PUSCH with priority. Additionally, or in other embodiments, if the UE does not support the cancel and replace capability (e.g., in 3GPP Rel.-17), the UE behavior for DG / CG override is followed (e.g., for 3GPP Rel-16). On the other hand, if the UE supports the cancel and replace capability, the UE behavior with respect to the cancel and replace of two PUSCHs with UL-SCH is as described in one or more embodiments described herein.

[0031] like Figure 3As shown, combination 302 corresponds to a high priority DG PUSCH with UL-SCH and a low priority SP-CSI on PUSCH. In one embodiment of combination 302, the HP DG PUSCH overrides the SP-CSI on PUSCH because the HP DGPUSCH overrides the LP CG-PUSCH, but without reference to the HARQ process ID because there is no data transmission (and therefore no HARQ process) for the SP-CSI. In another embodiment of combination 302, if the semi-persistent CSI report to be carried on the PUSCH overlaps in time with the DG PUSCH with high priority UL-SCH in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels does not start earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling the PUSCH, where d2,1 is the maximum value of d2,1 associated with a PUSCH carrying a semi-persistent CSI report and a PUSCH with data transmission, then the UE does not transmit the CSI report. Otherwise, if the timeline requirement is not met, this is an error condition.

[0032] The combination 304 corresponds to a high priority CG PUSCH and a low priority SP-CSI on the PUSCH. In one embodiment of 304, the HP CG PUSCH overrides the SP-CSI on the PUSCH because the HP CG PUSCH overrides the LP CG-PUSCH, but without reference to the HARQ process ID. In another embodiment, if the semi-persistent CSI report to be carried on the PUSCH overlaps in time with the PUSCH data transmission in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling the PUSCH, where d2,1 is the maximum value of d2,1 associated with a PUSCH carrying a semi-persistent CSI report and a PUSCH with data transmission, then the UE does not transmit the CSI report. Otherwise, if the timeline requirement is not met, this is an error condition. In yet another embodiment, if the UE is to transmit a first PUSCH including a semi-persistent CSI report and a second PUSCH as a configuration grant, and the first PUSCH transmission is to overlap in time with the second PUSCH transmission, then if the physical layer priority level of the first PUSCH is not higher than the physical layer priority level of the second PUSCH, the UE does not transmit the first PUSCH but transmits the second PUSCH. The UE expects that the first PUSCH transmission and the second PUSCH transmission meet the above timing conditions for PUSCH transmissions overlapping in time when at least one of the first PUSCH transmission or the second PUSCH transmission is responsive to DCI format detection by the UE.

[0033] Combination 306 corresponds to high priority A-CSI on PUSCH only and low priority SP-CSI on PUSCH. In one embodiment of combination 306, the HP AP CSI on PUSCH overrides the SP-CSI on PUSCH because the HP DG PUSCH overrides the LP CG-PUSCH without reference to the HARQ process ID. In another embodiment, if the semi-persistent CSI report to be carried on the PUSCH overlaps in time with the HP PUSCH with AP-only CSI scheduled by the PDCCH in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling the PUSCH, where d2,1 is the maximum value of d2,1 associated with a PUSCH carrying a semi-persistent CSI report and a PUSCH with data transmission, then the UE does not transmit the CSI report. Otherwise, if the timeline requirement is not met, this is an error case.

[0034] Combination 308 corresponds to a high priority SP-CSI on the PUSCH and a low priority SP-CSI on the PUSCH. In one embodiment of combination 308, the HP SP CSI on the PUSCH overrides the LP (or no priority) SP-CSI on the PUSCH because the HP CG PUSCH overrides the LP CG-PUSCH without reference to the HARQ process ID. In another embodiment, if the UE is to transmit a first PUSCH including a semi-persistent CSI report and a second PUSCH including a semi-persistent CSI report, and the first PUSCH transmission is to overlap in time with the second PUSCH transmission, then if the physical layer priority of the first PUSCH is higher than the physical layer priority of the second PUSCH, and neither the first PUSCH nor the second PUSCH is the first PUSCH transmission when the SP-CSI on the PUSCH is activated, the UE does not transmit the second PUSCH but transmits the first PUSCH. If PUSCH A is the first PUSCH or the second PUSCH and is the first PUSCH transmission when SP-CSI is activated on PUSCH, PUSCH A may be transmitted and the other PUSCH (PUSCH B) may be discarded. If PUSCH B, which is not the first PUSCH transmission when SP-CSI is activated on PUSCH, overlaps in time with PUSCH A in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling PUSCH, where d2,1 is the maximum of d2,1 associated with PUSCH A and PUSCH B, then the UE does not transmit PUSCH B. Otherwise, if the timeline requirement is not met, this is an error condition.

[0035] Combination 310 corresponds to high priority CG PUSCH and low priority A-CSI on PUSCH only. In one embodiment of combination 310, the HP SP CSI on PUSCH overrides the LP (or no priority) AP-CSI on PUSCH because the HP CGPUSCH overrides the LP DG-PUSCH without reference to the HARQ process ID. In an alternative embodiment, the LP DGPUSCH with AP-CSI can override the HP CG PUSCH as long as the Rel-15 timeline conditions are met; and the HARQ process ID of the CG PUSCH is not used to check the HARQ process ID with the LP DG PUSCH to determine whether the LP DG PUSCH can be transmitted. In yet another embodiment, the LP DG PUSCH with AP-CSI may override the HP CG PUSCH as long as the Rel-15 timeline conditions are met; if there is a transmission opportunity that allows the UE to transmit PUSCH with a configured grant on the same serving cell with the same HARQ process starting from symbol j to symbol i according to 3GPP TS 38.321, and if the gap between the end of the PDCCH and the beginning of symbol j is less than N2 symbols, then the UE is not expected to be scheduled by the PDCCH ending with symbol i to transmit PUSCH with AP-CSI on a given serving cell with a given HARQ process. The value N2 in the symbol is determined according to the UE processing capabilities defined in clause 6.4 of TS 38.214, and N2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with the configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH, even in this case, the HARQ process ID indicated in the DCI scheduling the LP DGP U SCH is not relevant to the PUSCH transmission itself because the UL-SCH is not included.

[0036] Combination 312 corresponds to high priority A-CSI and low priority CG PUSCH on PUSCH only. In one embodiment of combination 312, the HP AP CSI on PUSCH overrides the LP (or no priority) SP-CSI on PUSCH because the HP DGPUSCH overrides the LP CG-PUSCH without reference to the HARQ process ID. In an alternative embodiment, the HP DGPUSCH with AP-CSI can override the LP CG PUSCH as long as the Rel-15 timeline conditions are met; and the HARQ process ID of the CG PUSCH is not used to check the HARQ process ID with the HP DG PUSCH to determine whether the LP DG PUSCH can be transmitted. In yet another embodiment, the HP DG PUSCH with AP-CSI may override the LP CG PUSCH as long as the Rel-15 timeline conditions are met; and if there is a transmission opportunity that allows the UE to transmit PUSCH with a configured grant on the same serving cell with the same HARQ process starting from symbol j to symbol i according to TS38.321, and if the gap between the end of the PDCCH and the beginning of symbol j is less than N2 symbols, then the UE is not expected to be scheduled by the PDCCH ending with symbol i to transmit PUSCH with AP-CSI on a given serving cell with a given HARQ process. The value N2 in the symbol is determined according to the UE processing capabilities defined in clause 6.4 of TS 38.214, and N2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with the configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH, even in this case, the HARQ process ID indicated in the DCI scheduling the LP DGPUSCH is not relevant to the PUSCH transmission itself because the UL-SCH is not included.

[0037] Combination 314 corresponds to high priority SP-CSI on PUSCH and low priority DG PUSCH with UL-SCH. In one embodiment, combination 314 is not supported (e.g., for legacy systems that do not support high priority SP CSI on PUSCH). In another embodiment of combination 314, the HP SP CSI on PUSCH overrides the LP (or no priority) DG PUSCH because the HP CG PUSCH overrides the LP DG-PUSCH without reference to the HARQ process ID. In another embodiment, if the semi-persistent CSI report to be carried on the PUSCH overlaps in time with the PUSCH data transmission in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling the PUSCH, where d2,1 is the maximum value of d2,1 associated with a PUSCH carrying a semi-persistent CSI report and a PUSCH with data transmission, then the UE does not transmit the CSI report. Otherwise, if the timeline requirement is not met, this is an error condition.

[0038] Combination 316 corresponds to high priority SP-CSI and low priority CG PUSCH on PUSCH. In one embodiment, combination 316 is not supported (e.g., for legacy systems that do not support high priority SP CSI on PUSCH). In another embodiment of combination 316, the HP SP CSI on PUSCH overrides the LP (or no priority) CG PUSCH because the HP CG PUSCH overrides the LP CG-PUSCH without reference to the HARQ process ID. In an alternative embodiment, if the UE is to transmit a first PUSCH including a semi-persistent CSI report and a second PUSCH including a UL-SCH (configuration grant) and the first PUSCH transmission is to overlap in time with the second PUSCH transmission, then if 1) the physical layer priority of the first PUSCH is higher than the physical layer priority of the second PUSCH, and 2) the first PUSCH is not the first PUSCH transmission when SP-CSI on PUSCH is activated, and the second PUSCH is not the first PUSCH transmission when CG PUSCH is activated, then the UE does not transmit the second PUSCH but transmits the first PUSCH. For combination 316 and combination 304, if PUSCH A, which is SP-CSI or CG PUSCH on PUSCH, is the first PUSCH transmission upon activation of SP-CSI on PUSCH or CG PUSCH, then PUSCH A may be transmitted and PUSCH B, which is CG PUSCH or SP-CSI on PUSCH, may be discarded. If PUSCH B, which is not the first PUSCH transmission upon activation of CG PUSCH or SP-CSI on PUSCH, overlaps in time with PUSCH A in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling PUSCH, where d2,1 is the maximum of d2,1 associated with PUSCH A and PUSCH B, then the UE shall not transmit PUSCH B. Otherwise, if the timeline requirement is not met, this is an error condition.

[0039] Combination 318 corresponds to high priority SP-CSI on PUSCH and low priority A-CSI on PUSCH only. In one embodiment, combination 318 is not supported (e.g., for legacy systems that do not support high priority SP CSI on PUSCH). In another embodiment of combination 318, the HP SP CSI on PUSCH overrides the LP (no priority) AP-CSI on PUSCH because the HP CG PUSCH overrides the LP DG-PUSCH without reference to the HARQ process ID. In an alternative embodiment, if the semi-persistent CSI report to be carried on PUSCH overlaps in time with an LP PUSCH with APCSI only scheduled by PDCCH in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N2+d2,1 symbols after the last symbol of the DCI scheduling the PUSCH, where d2,1 is the maximum value of d2,1 associated with a PUSCH carrying a semi-persistent CSI report and a PUSCH with data transmission, then the UE does not transmit a CSI report. Otherwise, if the timeline requirement is not met, this is an error condition.

[0040] Figure 4 4 is a flow chart of a method 400 for a UE to control an override of a first grant of a first radio resource by a second grant of a second radio resource. In block 402, the method 400 includes determining that the second radio resource at least partially overlaps with the first radio resource. In block 404, the method 400 determines a physical layer priority of the first grant of the first radio resource and the second grant of the second radio resource, the physical layer priority being configured for transmitting channel state information (CSI) feedback to a base station via a physical uplink shared channel (PUSCH) based on at least one of the first grant of the first radio resource and the second grant of the second radio resource. In block 406, the method 400 includes generating a transmission according to the physical layer priority.

[0041] In certain embodiments of the method 400, the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on a PUSCH, and the second grant includes a dynamic grant (DG) for a PUSCH with an uplink shared channel (UL-SCH). The SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level. Determining the physical layer priority includes determining, in response to determining that the second priority level is higher than the first priority level, that the DG for the PUSCH with the UL-SCH overrides the SP CSI on the PUSCH.

[0042] In certain embodiments of the method 400, the first grant includes a first configuration grant (CG) for a semi-persistent (SP) CSI on a PUSCH, and the second grant includes a second CG for the PUSCH. The SP CSI on the PUSCH is associated with a first priority level and the second CG for the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the second CG for the PUSCH overrides the SPCSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0043] In certain embodiments of the method 400, the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on the PUSCH, and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH. The SP CSI on the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the APCSI on the PUSCH overrides the SP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0044] In certain embodiments of the method 400, the first grant includes a first configuration grant (CG) for a first semi-persistent (SP) CSI on a PUSCH, and the second grant includes a second CG for a second SP CSI on the PUSCH. The first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the second SP CSI on the PUSCH overrides the first SP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0045] In certain embodiments of the method 400, the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on a PUSCH, and the second grant includes a configuration grant (CG) for the PUSCH. The AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the CG for the PUSCH overrides the AP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level. The CG for the PUSCH may be used to transmit semi-persistent (SP) CSI on the PUSCH.

[0046] In certain embodiments of the method 400, the first grant includes a configuration grant (CG) for a PUSCH, and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH. The CG for the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the AP CSI on the PUSCH overrides the CG for the PUSCH in response to determining that the second priority level is higher than the first priority level. The CG for the PUSCH may be used to transmit semi-persistent (SP) CSI on the PUSCH.

[0047] In certain embodiments of the method 400, the first grant includes a dynamic grant (DG) for a PUSCH with an uplink shared channel (UL-SCH), and the second grant includes a configured grant for a semi-persistent (SP) CSI on the PUSCH. The DG for the PUSCH with the UL-SCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the SP CSI on the PUSCH overrides the DG for the PUSCH with the UL-SCH in response to determining that the second priority level is higher than the first priority level.

[0048] In certain embodiments of the method 400, the first grant includes a first configuration grant (CG) for a PUSCH, and the second grant includes a second CG for a semi-persistent (SP) CSI on the PUSCH. The first CG for the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the SP CSI on the PUSCH overrides the first CG for the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0049] In certain embodiments of the method 400, the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, and the second grant includes a configuration grant (CG) for semi-persistent (SP) CSI on the PUSCH. The AP CSI on the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level. Determining the physical layer priority includes determining that the SP CSI on the PUSCH overrides the AP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0050] In certain embodiments of the method 400, determining the physical layer priority is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

[0051] In certain embodiments of method 400, the CSI feedback includes aperiodic (AP) CSI on PUSCH, and determining the physical layer priority includes treating the AP CSI on the PUSCH as a PUSCH with an uplink shared channel (UL-SCH) for dynamic grant (DG) and configuration grant (CG) prioritization.

[0052] In certain embodiments of the method 400, the CSI feedback includes semi-persistent (SP) CSI on a PUSCH, and determining the physical layer priority includes treating a first transmission of the SP CSI on the PUSCH as a dynamic grant (DG) PUSCH transmission and treating one or more second transmissions of the SP CSI on the PUSCH as a configured grant (CG) PUSCH transmission, wherein the one or more second transmissions are performed after the first transmission.

[0053] Figure 5 The present invention is a method 500 for controlling an override of a first grant of a first radio resource in a base station. In block 502, the method 500 includes transmitting a second grant of a second radio resource to a user equipment (UE), the second radio resource at least partially overlapping the first radio resource. In block 504, the method 500 includes determining whether the second grant overrides the first grant based on at least one of the first grant of the first radio resource and the second grant of the second radio resource being configured for transmitting channel state information (CSI) feedback from the UE to the base station via a physical uplink shared channel (PUSCH).

[0054] In certain embodiments of the method 500, the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on a PUSCH, and the second grant includes a dynamic grant (DG) for a PUSCH with an uplink shared channel (UL-SCH). The SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the DG for the PUSCH with the UL-SCH overrides the SP CSI on the PUSCH.

[0055] In certain embodiments of the method 500, the first grant includes a first configuration grant (CG) for semi-persistent (SP) CSI on a PUSCH, and the second grant includes a second CG for the PUSCH. The SP CSI on the PUSCH is associated with a first priority level and the second CG for the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the second CG for the PUSCH overrides the SP CSI on the PUSCH.

[0056] In certain embodiments of the method 500, the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on PUSCH, and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on PUSCH. The SP CSI on PUSCH is associated with a first priority level and the AP CSI on PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the AP CSI on PUSCH overrides the SP CSI on PUSCH.

[0057] In certain embodiments of the method 500, the first grant includes a first configuration grant (CG) for a first semi-persistent (SP) CSI on a PUSCH, and the second grant includes a second CG for a second SP CSI on the PUSCH. The first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the second SP CSI on the PUSCH overrides the first SP CSI on the PUSCH.

[0058] In certain embodiments of the method 500, the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on a PUSCH, and the second grant includes a configuration grant (CG) for the PUSCH. The AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the CG for the PUSCH overrides the AP CSI on the PUSCH.

[0059] In certain embodiments of the method 500, the first grant includes a configuration grant (CG) for a PUSCH and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH. The CG for the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the AP CSI on the PUSCH overrides the CG for the PUSCH.

[0060] In certain embodiments of the method 500, the first grant includes a dynamic grant (DG) for a PUSCH with an uplink shared channel (UL-SCH), and the second grant includes a configured grant for a semi-persistent (SP) CSI on the PUSCH. The DG for the PUSCH with the UL-SCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the SP CSI on the PUSCH overrides the DG for the PUSCH with the UL-SCH.

[0061] In certain embodiments of the method 500, the first grant includes a first configuration grant (CG) for a PUSCH, and the second grant includes a second CG for a semi-persistent (SP) CSI on the PUSCH. The first CG for the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the SP CSI on the PUSCH overrides the first CG for the PUSCH.

[0062] In certain embodiments of the method 500, the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on PUSCH, and the second grant includes a configured grant (CG) for semi-persistent (SP) CSI on PUSCH. The AP CSI on PUSCH is associated with a first priority level and the SP CSI on PUSCH is associated with a second priority level. Determining whether the second grant overrides the first grant includes determining that the SP CSI on PUSCH overrides the AP CSI on PUSCH.

[0063] In certain embodiments of method 500, determining whether the second grant overrides the first grant is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

[0064] Figure 6 An exemplary architecture of a network system 600 according to various embodiments is shown. The following description is provided for an example system 600 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0065] like Figure 6As shown, system 600 includes UE 622 and UE 620. In this example, UE 622 and UE 620 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0066] In some embodiments, UE 622 and / or UE 620 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0067] UE 622 and UE 620 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R) AN 608). In an embodiment, (R) AN 608 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R) AN 608 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R) AN 608 operating in an LTE or 4G system. UE 622 and UE 620 utilize connections (or channels) (shown as connection 604 and connection 602, respectively), each connection comprising a physical communication interface or layer (discussed in further detail below).

[0068] In this example, connection 604 and connection 602 are air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 622 and UE 620 may also directly exchange communication data via a ProSe interface 610. The ProSe interface 610 may alternatively be referred to as a side link (SL) interface 110, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0069] UE 620 is shown as being configured to access AP 612 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 624. Connection 624 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 612 would include Wireless Fidelity. router. In this example, AP 612 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 620, (R) AN 608, and AP 612 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 620 in RRC_CONNECTED being configured by RAN node 614 or RAN node 616 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 620 using WLAN radio resources (e.g., connection 624) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 624. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0070] (R)AN 608 may include one or more AN nodes, such as RAN node 614 and RAN node 616, that implement connection 604 and connection 602. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 600. According to various embodiments, the RAN node 614 or the RAN node 616 may be implemented as one or more of dedicated physical devices such as macrocell base stations and / or low power (LP) base stations for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macrocells.

[0071] In some embodiments, all or part of RAN node 614 or RAN node 616 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 614 or RAN node 616); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 614 or RAN node 616); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of the RAN node 614 or RAN node 616 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 6In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 608 or by a server pool in a manner similar to the CRAN / vBBUP. Additionally or alternatively, the RAN node 614 or one or more of the RAN nodes 616 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 622 and the UE 620 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, one or more of the RAN node 614 or the RAN node 616 may be an RSU or act as an RSU.

[0072] The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz direct short range communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0073] The RAN node 614 and / or the RAN node 616 may terminate the air interface protocol and may be the first point of contact for the UE 622 and the UE 620. In some embodiments, the RAN node 614 and / or the RAN node 616 may perform various logical functions of the (R)AN 608, 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.

[0074] In an embodiment, UE 622 and UE 620 may be configured to communicate with each other or with RAN node 614 and / or RAN node 616 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0075] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 614 and / or RAN node 616 to UE 622 and UE 620, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each 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 includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0076] According to various embodiments, UE 622 and UE 620 and RAN node 614 and / or RAN node 616 communicate (e.g., transmit and receive) data through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0077] To operate in the unlicensed spectrum, UE 622 and UE 620 and RAN node 614 or RAN node 616 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 622 and UE 620 and RAN node 614 or RAN node 616 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0078] LBT is a mechanism for equipment (e.g., UE 622 and UE 620, RAN node 614 or RAN node 616, etc.) to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0079] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 622, AP 612, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0080] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0081] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require the UE 622 to undergo a switch. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0082] The PDSCH carries user data and higher layer signaling to UE 622 and UE 620. The PDCCH carries, among other information, information about transport formats and resource allocations related to the PDSCH channel. It may also inform UE 622 and UE 620 about transport formats, resource allocations, and HARQ information related to uplink shared channels. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 620 within a cell) may be performed at either RAN node 614 or RAN node 616 based on channel quality information fed back from either UE 622 and UE 620. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 622 and UE 620.

[0083] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0084] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0085] The RAN node 614 or the RAN node 616 may be configured to communicate with each other via the interface 630. In an embodiment where the system 600 is an LTE system (e.g., when the CN 606 is an EPC), the interface 630 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 622 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 622; information about the current minimum expected buffer size at the Se NB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0086] In an embodiment where the system 600 is a SG or NR system (e.g., when the CN 606 is an SGC), the interface 630 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to the SGC, between a RAN node 614 (e.g., a gNB) and an eNB connected to the SGC, and / or between two eNBs connected to a 5GC (e.g., CN 606). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 622 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 614 or RAN nodes 616. Mobility support may include context transfer from the old (source) service RAN node 614 to the new (target) service RAN node 616; and control of the user plane tunnel between the old (source) service RAN node 614 and the new (target) service RAN node 616. The protocol stack of Xn-U may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0087] (R)AN 608 is shown as being communicatively coupled to the core network - in this embodiment, communicatively coupled to CN 606. CN 606 may include one or more network elements 632, which are configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 622 and UE 620) connected to CN 606 via (R)AN 608. The components of CN 606 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 606 may be referred to as a network slice, and a logical instance of a portion of CN 606 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0088] In general, the application server 618 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 618 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for UE 622 and UE 620 via the EPC. The application server 618 may communicate with the CN 606 via the IP communication interface 636.

[0089] In an embodiment, CN 606 may be an SGC, and (R)AN 116 may be connected to CN 634 via NG interface 606. In an embodiment, NG interface 634 may be divided into two parts: NG user plane (NG-U) interface 626, which carries traffic data between RAN node 614 or RAN node 616 and UPF; and S1 control plane (NG-C) interface 628, which is a signaling interface between RAN node 614 or RAN node 616 and AMF.

[0090] In an embodiment, CN 606 may be an SG CN, while in other embodiments, CN 606 may be an EPC. In the case where CN 606 is an EPC, (R)AN 116 may be connected to CN 606 via an S1 interface 634. In an embodiment, S1 interface 634 may be divided into two parts: an S1 user plane (S1-U) interface 626, which carries traffic data between RAN node 614 or RAN node 616 and S-GW; and an S1-MME interface 628, which is a signaling interface between RAN node 614 or RAN node 616 and MME.

[0091] Figure 7 An example of infrastructure equipment 700 according to various embodiments is shown. The infrastructure equipment 700 can be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device discussed herein. In other examples, the infrastructure equipment 700 can be implemented in or by a UE.

[0092] The infrastructure equipment 700 includes application circuits 702, baseband circuits 704, one or more radio front end modules 706 (RFEM), memory circuits 708, power management integrated circuits (shown as PMIC 710), power tee circuits 712, network controller circuits 714, network interface connectors 720, satellite positioning circuits 716, and user interface circuits 718. In some embodiments, the infrastructure equipment 700 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuits may be included separately in more than one device for CRAN, vBBU, or other similar implementations. The application circuits 702 include, for example, but not limited to, one or more processors (or processor cores), cache memory, and one or more low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, l 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of the application circuit 702 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure equipment 700. In some specific implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0093] The processor of the application circuit 702 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 702 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 702 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPSWarrior P-class processor; etc. In some embodiments, the infrastructure equipment 700 may not utilize the application circuit 702, and instead may include a dedicated processor / controller to process IP data received, for example, from the EPC or 5GC.

[0094] In some implementations, the application circuit 702 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such implementations, the circuits of the application circuit 702 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 702 may include a memory unit (e.g., an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a static memory (e.g., a static random access memory (SRAM), an anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), etc. The baseband circuit 704 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0095] The user interface circuitry 718 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 700 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 700. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0096] The radio front end module 706 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 706 that combines both millimeter wave antennas and sub-millimeter waves.

[0097] The memory circuit 708 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM); and a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as “flash memory”), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 708 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0098] The PMIC 710 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 712 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 700 using a single cable.

[0099] The network controller circuit 714 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 700 via a network interface connector 720, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 714 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 714 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0100] The positioning circuit 716 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 716 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 716 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 716 may also be part of or interact with the baseband circuit 704 and / or the radio front end module 706 to communicate with nodes and components of the positioning network. The positioning circuit 716 may also provide location data and / or time data to the application circuit 702, which may use the data to synchronize operations with various infrastructures, etc. Figure 7 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCix), PCI express (PCie), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0101] Figure 8 An example of a platform 800 according to various embodiments is shown. In an embodiment, the computer platform 800 may be suitable for use as a UE, an application server, and / or any other element / device discussed herein. The platform 800 may include any combination of components shown in the example. The components of the platform 800 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 800, or implemented as components otherwise incorporated within the chassis of a larger system. Figure 8 The block diagram is intended to show a high-level view of the components of computer platform 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0102] Application circuit 802 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 C or general programmable serial interface module, RTC, timer (including interval timer and watchdog timer), general IO, memory card controller (such as SD MMC or similar controller), USB interface, MIPI interface and JTAG test access port. The processor (or core) of the application circuit 802 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the platform 800. In some specific implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0103] The processor of the application circuit 802 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 802 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0104] As an example, the processor of the application circuit 802 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU-class processors, or can be purchased from The processor of application circuit 802 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s AS-A9 processor, Snapdragon by Technologies, Inc.TM Processor, Texas Instruments, OpenMultimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 802 can be part of a system on a chip (SoC), in which the application circuit 802 and other components are formed as a single integrated circuit or a single package, such as available from Edison Corporation TM or Galileo TM SoC board.

[0105] Additionally or alternatively, the application circuit 802 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 802 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 802 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in a lookup table (LUT), etc.

[0106] Baseband circuitry 804 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0107] The radio front end module 806 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 806 that combines both millimeter wave antennas and sub-millimeter waves.

[0108] The memory circuit 808 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 808 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SD RAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 808 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 808 may be implemented as one or more of the following: solder-in package integrated circuit, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socket memory module, dual in-line memory module (DIMM) (including micro DIMM or mini DIMM, and / or soldered to the motherboard via ball grid array (BGA)). In a low-power implementation, the memory circuit 808 may be an on-chip memory or register associated with the application circuit 802. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 808 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 800 may be combined with a memory device obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0109] Removable memory circuitry 826 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 800. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0110] Platform 800 may also include interface circuitry (not shown) for connecting external devices to platform 800. External devices connected to platform 800 via the interface circuitry include sensors 822 and electromechanical components (shown as EMC 824), as well as removable memory devices coupled to removable memory 826.

[0111] Sensors 822 include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0112] EMC 824 includes devices, modules or subsystems for the purpose of enabling platform 800 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 824 may be configured to generate messages / signaling and send messages / signaling to other components of platform 800 to indicate the current state of EMC 824. Examples of EMC 824 include one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 800 is configured to operate one or more EMC 824 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients. In some specific implementations, an interface circuit may connect platform 800 to positioning circuit 816. The positioning circuit 816 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 816 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 816 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 816 may also be part of or interact with the baseband circuit 804 and / or the radio front-end module 806 to communicate with nodes and components of the positioning network. Positioning circuitry 816 may also provide position data and / or time data to application circuitry 802 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0113] In some implementations, the interface circuit may connect the platform 800 to a near field communication circuit (shown as NFC circuit 812). The NFC circuit 812 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 812 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 800. The NFC circuit 812 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 812 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 812, or initiate data transfer between the NFC circuit 812 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) proximate to the platform 800.

[0114] The driver circuit 818 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 800. The driver circuit 818 may include various drivers to allow other components of the platform 800 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 800. For example, the driver circuit 818 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 800, a sensor driver for obtaining sensor readings of a sensor 822 and controlling and allowing access to the sensor 822, an EMC driver for obtaining actuator positions of an EMC 824 and / or controlling and allowing access to the EMC 824, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0115] A power management integrated circuit (shown as PMIC 810) (also referred to as a "power management circuit") can manage the power provided to various components of the platform 800. In particular, the PMIC 810 can control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 804. The PMIC 810 can typically be included when the platform 800 is capable of being powered by a battery 814, for example, when the device is included in a UE.

[0116] In some embodiments, the PMIC 810 may control or otherwise be part of various power saving mechanisms of the platform 800. For example, if the platform 800 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 800 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 800 may transition to the RRC_Idle state, in which the platform is disconnected from the network and no operations such as channel quality feedback, handovers, etc. are performed. The platform 800 enters an extremely low power state and performs paging, in which the platform periodically wakes up to listen to the network and then powers off again. The platform 800 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0117] The battery 814 can provide power to the platform 800, but in some examples, the platform 800 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 814 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 814 can be a typical lead-acid car battery.

[0118] In some implementations, the battery 814 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 800 to track the state of charge (SoCh) of the battery 814. The BMS may be used to monitor other parameters of the battery 814, such as the state of health (SoH) and state of function (SoF) of the battery 814 to provide fault prediction. The BMS may transmit information about the battery 814 to the application circuit 802 or other components of the platform 800. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 802 to directly monitor the voltage of the battery 814 or the current from the battery 814. The battery parameters may be used to determine actions that the platform 800 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0119] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 814. In some examples, the power block can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 800. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 814 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0120] The user interface circuit 820 includes various input / output (I / O) devices present in or connected to the platform 800, and includes one or more user interfaces designed to implement user interaction with the platform 800 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 800. The user interface circuit 820 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators such as binary status indicators (e.g., light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 800. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor 822 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuits (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuit including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0121] Although not shown, the components of platform 800 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0122] Fig. 9 is a block diagram illustrating a component 900 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 902 is shown, which includes one or more processors 906 (or processor cores), one or more memory / storage devices 914, and one or more communication resources 924, each of which may be communicatively coupled via a bus 916. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 922 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 902.

[0123] Processor 906 (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) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 908 and processor 910.

[0124] The memory / storage device 914 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 914 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, etc.

[0125] The communication resources 924 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 920 via the network 918. For example, the communication resources 924 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.

[0126] The instructions 912 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 906 to perform any one or more of the methods discussed herein. The instructions 912 may reside completely or partially in at least one of the processors 906 (e.g., in a cache memory of the processor), the memory / storage device 914, or any suitable combination thereof. In addition, any portion of the instructions 912 may be transmitted to the hardware resources 902 from any combination of the peripheral device 904 or the database 920. Therefore, the memory of the processor 906, the memory / storage device 914, the peripheral device 904, and the database 920 are examples of computer-readable and machine-readable media.

[0127] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the examples section below.

[0128] Examples

[0129] The following examples relate to additional embodiments.

[0130] Embodiment 1 is a method for a user equipment (UE) to control the override of a first grant of a first radio resource by a second grant of a second radio resource. The method includes: determining that the second radio resource overlaps at least partially with the first radio resource; determining a physical layer priority of the first grant of the first radio resource and the second grant of the second radio resource, the physical layer priority being configured based on at least one of the first grant of the first radio resource and the second grant of the second radio resource for transmitting channel state information (CSI) feedback to a base station via a physical uplink shared channel (PUSCH); and generating a transmission according to the physical layer priority.

[0131] Embodiment 2 includes a method according to embodiment 1, wherein the first grant includes a configuration grant (CG) for a semi-persistent (SP) CSI on the PUSCH, and the second grant includes a dynamic grant (DG) for the PUSCH with an uplink shared channel (UL-SCH), wherein the SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level, and wherein determining the physical layer priority includes determining, in response to determining that the second priority level is higher than the first priority level, that the DG for the PUSCH with the UL-SCH overrides the SP CSI on the PUSCH.

[0132] Embodiment 3 includes a method according to embodiment 1, wherein the first grant includes a first configuration grant (CG) for a semi-persistent (SP) CSI on the PUSCH, and the second grant includes a second CG for the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the second CG for the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the second CG for the PUSCH overrides the SP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0133] Embodiment 4 includes a method according to embodiment 1, wherein the first grant includes a configuration grant (CG) for a semi-persistent (SP) CSI on the PUSCH, and the second grant includes a dynamic grant (DG) for an aperiodic (AP) CSI on the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the APCSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the AP CSI on the PUSCH overrides the SP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0134] Embodiment 5 includes a method according to embodiment 1, wherein the first grant includes a first configuration grant (CG) for a first semi-persistent (SP) CSI on the PUSCH, and the second grant includes a second CG for a second SP CSI on the PUSCH, wherein the first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the second SP CSI on the PUSCH overrides the first SP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0135] Embodiment 6 includes a method according to embodiment 1, wherein the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, and the second grant includes a configuration grant (CG) for the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the CG for the PUSCH overrides the AP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0136] Embodiment 7 includes the method according to embodiment 1, wherein the first grant includes a configuration grant (CG) for the PUSCH, and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, wherein the CG for the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the AP CSI on the PUSCH overrides the CG for the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0137] Embodiment 8 includes a method according to embodiment 1, wherein the first grant includes a dynamic grant (DG) for a PUSCH with an uplink shared channel (UL-SCH), and the second grant includes a configuration grant for a semi-persistent (SP) CSI on the PUSCH, wherein the DG for the PUSCH with the UL-SCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the SP CSI on the PUSCH overrides the DG for the PUSCH with the UL-SCH.

[0138] Embodiment 9 includes a method according to embodiment 1, wherein the first grant includes a first configuration grant (CG) for the PUSCH, and the second grant includes a second CG for a semi-persistent (SP) CSI on the PUSCH, wherein the first CG for the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the SP CSI on the PUSCH overrides the first CG for the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0139] Embodiment 10 includes a method according to embodiment 1, wherein the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, and the second grant includes a configured grant (CG) for semi-persistent (SP) CSI on the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the SPCSI on the PUSCH is associated with a second priority level, and wherein determining the physical layer priority includes determining that the SP CSI on the PUSCH overrides the AP CSI on the PUSCH in response to determining that the second priority level is higher than the first priority level.

[0140] Embodiment 11 includes the method of any one of embodiments 2 to 10, wherein determining the physical layer priority is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

[0141] Embodiment 12 includes a method according to any one of Embodiment 6 or Embodiment 7, wherein the CG for the PUSCH is used to transmit semi-persistent (SP) CSI on the PUSCH.

[0142] Embodiment 13 includes a method according to embodiment 1, wherein the CSI feedback includes aperiodic (AP) CSI on the PUSCH, and wherein determining the physical layer priority includes treating the AP CSI on the PUSCH as a PUSCH with an uplink shared channel (UL-SCH) for dynamic grant (DG) and configuration grant (CG) prioritization processing.

[0143] Embodiment 14 includes a method according to embodiment 1, wherein the CSI feedback includes semi-persistent (SP) CSI on the PUSCH, and wherein determining the physical layer priority includes considering a first transmission of the SP CSI on the PUSCH as a dynamic grant (DG) PUSCH transmission and considering one or more second transmissions of the SP CSI on the PUSCH as a configuration grant (CG) PUSCH transmission, wherein the one or more second transmissions are performed after the first transmission.

[0144] Embodiment 15 is a method in a base station for controlling an override of a first grant of a first radio resource. The method includes: transmitting a second grant of a second radio resource to a user equipment (UE), the second radio resource at least partially overlapping with the first radio resource; and determining whether the second grant overrides the first grant based on at least one of the first grant of the first radio resource and the second grant of the second radio resource being configured for transmitting channel state information (CSI) feedback from the UE to the base station via a physical uplink shared channel (PUSCH).

[0145] Embodiment 16 includes a method according to embodiment 15, wherein the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on the PUSCH, and the second grant includes a dynamic grant (DG) for the PUSCH with an uplink shared channel (UL-SCH), wherein the SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the DG for the PUSCH with the UL-SCH overrides the SPCSI on the PUSCH.

[0146] Embodiment 17 includes a method according to embodiment 15, wherein the first grant includes a first configuration grant (CG) for a semi-persistent (SP) CSI on the PUSCH, and the second grant includes a second CG for the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the second CG for the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the second CG for the PUSCH overrides the SP CSI on the PUSCH.

[0147] Embodiment 18 includes a method according to embodiment 15, wherein the first grant includes a configuration grant (CG) for semi-persistent (SP) CSI on the PUSCH, and the second grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the AP CSI on the PUSCH overrides the SP CSI on the PUSCH.

[0148] Embodiment 19 includes a method according to embodiment 15, wherein the first grant includes a first configuration grant (CG) for a first semi-persistent (SP) CSI on the PUSCH, and the second grant includes a second CG for a second SP CSI on the PUSCH, wherein the first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the second SP CSI on the PUSCH overrides the first SP CSI on the PUSCH.

[0149] Embodiment 20 includes a method according to embodiment 15, wherein the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, and the second grant includes a configuration grant (CG) for the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the CG for the PUSCH overrides the AP CSI on the PUSCH.

[0150] Embodiment 21 comprises the method according to embodiment 15, wherein the first grant comprises a configuration grant (CG) for the PUSCH, and the second grant comprises a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, wherein the CG for the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant comprises determining that the APCSI on the PUSCH overrides the CG for the PUSCH.

[0151] Embodiment 22 includes a method according to embodiment 15, wherein the first grant includes a dynamic grant (DG) for the PUSCH with an uplink shared channel (UL-SCH), and the second grant includes a configured grant for a semi-persistent (SP) CSI on the PUSCH, wherein the DG for the PUSCH with the UL-SCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the SP CSI on the PUSCH overrides the DG for the UL-PUSCH with the UL-SCH.

[0152] Embodiment 23 includes a method according to embodiment 15, wherein the first grant includes a first configuration grant (CG) for the PUSCH, and the second grant includes a second CG for a semi-persistent (SP) CSI on the PUSCH, wherein the first CG for the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the SPCSI on the PUSCH overrides the first CG for the PUSCH.

[0153] Embodiment 24 includes a method according to embodiment 15, wherein the first grant includes a dynamic grant (DG) for aperiodic (AP) CSI on the PUSCH, and the second grant includes a configured grant (CG) for semi-persistent (SP) CSI on the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and wherein determining whether the second grant overrides the first grant includes determining that the SP CSI on the PUSCH overrides the AP CSI on the PUSCH.

[0154] Embodiment 25 includes a method according to any one of Embodiments 16 to 24, wherein determining whether the second grant overrides the first grant is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

[0155] Embodiment 26 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0156] Embodiment 27 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0157] Embodiment 28 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

[0158] Embodiment 29 may include a method, technique or process, or a portion or component thereof, as described in or related to any of the above embodiments.

[0159] Embodiment 30 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any of the above embodiments.

[0160] Embodiment 31 may include signals or parts or components thereof as described in or related to any one of the above embodiments.

[0161] Embodiment 32 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0162] Embodiment 33 may include a signal encoded with data or a portion or component thereof as described in or related to any of the above embodiments, or content described in other ways in this disclosure.

[0163] Embodiment 34 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0164] Embodiment 35 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of these computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

[0165] Embodiment 36 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any one of the above embodiments.

[0166] Embodiment 37 may include signals in a wireless network as shown and described herein.

[0167] Embodiment 38 may include a method of communicating in a wireless network as shown and described herein.

[0168] Embodiment 39 may include a system for providing wireless communications as shown and described herein.

[0169] Embodiment 40 may include an apparatus for providing wireless communications as shown and described herein.

[0170] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0171] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0172] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0173] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0174] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment UE to control overriding of a first grant of a first radio resource by a second grant of a second radio resource, the method comprising: determining that the second radio resource at least partially overlaps with the first radio resource; determining a physical layer priority of the first grant of the first radio resource and the second grant of the second radio resource, the physical layer priority being configured based on at least one of the first grant of the first radio resource and the second grant of the second radio resource for transmitting channel state information (CSI) feedback to a base station through a physical uplink shared channel (PUSCH), wherein the CSI feedback comprises semi-persistent CSI (SP CSI) on the PUSCH, and wherein determining the physical layer priority comprises: treating a first transmission of the SP CSI on the PUSCH as a dynamically granted PUSCH transmission (DG PUSCH transmission), and treating one or more second transmissions of the SP CSI on the PUSCH as configured granted PUSCH transmissions (CG PUSCH transmissions), wherein the one or more second transmissions are after the first transmission; and Transmissions are generated according to the physical layer priorities.

2. The method of claim 1 , wherein the first grant comprises a configuration grant CG for a semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a dynamic grant DG for the PUSCH with an uplink shared channel UL-SCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the DG for the PUSCH with the UL-SCH overrides the SP CSI on the PUSCH.

3. The method of claim 1 , wherein the first grant comprises a first configuration grant CG for a semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a second CG for the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the second CG for the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the second CG for the PUSCH overrides the SP CSI on the PUSCH.

4. The method of claim 1 , wherein the first grant comprises a configuration grant CG for a semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a dynamic grant DG for an aperiodic CSI (AP CSI) on the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the AP CSI on the PUSCH overrides the SP CSI on the PUSCH.

5. The method of claim 1 , wherein the first grant comprises a first configuration grant CG for a first semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a second CG for a second SP CSI on the PUSCH, wherein the first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the second SP CSI on the PUSCH overrides the first SP CSI on the PUSCH.

6. The method of claim 1, wherein the first grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, and the second grant comprises a configuration grant CG for the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the CG for the PUSCH overrides the AP CSI on the PUSCH.

7. The method of claim 1, wherein the first grant comprises a configuration grant CG for the PUSCH, and the second grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, wherein the CG for the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the AP CSI on the PUSCH overrides the CG for the PUSCH.

8. The method of claim 1 , wherein the first grant comprises a dynamic grant DG for the PUSCH with an uplink shared channel UL-SCH, and the second grant comprises a configured grant for a semi-persistent SPCSI on the PUSCH, wherein the DG for the PUSCH with the UL-SCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority comprises, in response to determining that the second priority level is higher than the first priority level, determining the SP CSI override on the PUSCH for the DG of the PUSCH with the UL-SCH.

9. The method of claim 1 , wherein the first grant comprises a first configuration grant CG for the PUSCH, and the second grant comprises a second CG for a semi-persistent CSI (SP CSI) on the PUSCH, wherein the first CG for the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the SP CSI on the PUSCH overrides the first CG for the PUSCH.

10. The method of claim 1, wherein the first grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, and the second grant comprises a configuration grant CG for semi-persistent CSI (SPCSI) on the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the SP CSI on the PUSCH is associated with a second priority level, and Wherein determining the physical layer priority includes, in response to determining that the second priority level is higher than the first priority level, determining that the SP CSI on the PUSCH overrides the AP CSI on the PUSCH.

11. The method according to any one of claims 2 to 10, wherein determining the physical layer priority is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

12. The method according to any one of claims 6 or 7, wherein the CG for the PUSCH is for the transmission of semi-persistent CSI (SP CSI) on the PUSCH.

13. The method of claim 1, wherein the CSI feedback comprises a non-periodic APCSI on the PUSCH, and wherein determining the physical layer priority comprises treating the AP CSI on the PUSCH as a PUSCH with an uplink shared channel UL-SCH for dynamic grant DG and configuration grant CG prioritization.

14. A method in a base station for controlling an override of a first grant of a first radio resource, the method comprising: transmitting a second grant of a second radio resource to a user equipment UE, the second radio resource at least partially overlapping the first radio resource, wherein the first grant comprises a configuration grant CG for semi-persistent channel state information SP CSI on a physical uplink shared channel PUSCH, and the second grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the AP CSI on the PUSCH is associated with a second priority level; as well as Based on at least one of the first grant of the first radio resource and the second grant of the second radio resource being configured for transmitting CSI feedback from the UE to the base station via the PUSCH, determining whether the second grant overrides the first grant, wherein determining whether the second grant overrides the first grant includes determining that the AP CSI on the PUSCH overrides the SP CSI on the PUSCH.

15. The method of claim 14, wherein the first grant comprises a configuration grant CG for a semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a dynamic grant DG for the PUSCH with an uplink shared channel UL-SCH, wherein the SP CSI on the PUSCH is associated with a first priority level and the DG for the PUSCH with the UL-SCH is associated with a second priority level, and Wherein determining whether the second grant overrides the first grant includes determining that the DG for the PUSCH with the UL-SCH overrides the SPCSI on the PUSCH.

16. The method of claim 14, wherein the first grant comprises a first configuration grant CG for a semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a second CG for the PUSCH, wherein the SP CSI on the PUSCH is associated with the first priority level and the second CG for the PUSCH is associated with the second priority level, and Determining whether the second grant overrides the first grant includes determining that the second CG for the PUSCH overrides the SP CSI on the PUSCH.

17. The method of claim 14, wherein the first grant comprises a first configuration grant CG for a first semi-persistent CSI (SP CSI) on the PUSCH, and the second grant comprises a second CG for a second SP CSI on the PUSCH, wherein the first SP CSI on the PUSCH is associated with a first priority level and the second SP CSI on the PUSCH is associated with a second priority level, and The determining whether the second grant overrides the first grant comprises determining that the second SPCSI on the PUSCH overrides the first SP CSI on the PUSCH.

18. The method of claim 14, wherein the first grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, and the second grant comprises a configuration grant CG for the PUSCH, wherein the AP CSI on the PUSCH is associated with a first priority level and the CG for the PUSCH is associated with a second priority level, and Determining whether the second grant overrides the first grant includes determining that the CG for the PUSCH overrides the AP CSI on the PUSCH.

19. The method of claim 14, wherein the first grant comprises a configuration grant CG for the PUSCH, and the second grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, wherein the CG for the PUSCH is associated with the first priority level and the AP CSI on the PUSCH is associated with the second priority level, and Determining whether the second grant overrides the first grant includes determining that the AP CSI on the PUSCH overrides the CG for the PUSCH.

20. The method of claim 14, wherein the first grant comprises a dynamic grant DG for the PUSCH with an uplink shared channel UL-SCH, and the second grant comprises a configuration grant for a semi-persistent CSI (SP CSI) on the PUSCH, wherein the DG for the PUSCH with the UL-SCH is associated with the first priority level and the SP CSI on the PUSCH is associated with the second priority level, and Wherein determining whether the second grant overrides the first grant comprises determining that the SP CSI on the PUSCH overrides the DG for the PUSCH with the UL-SCH.

21. The method of claim 14, wherein the first grant comprises a first configuration grant CG for the PUSCH, and the second grant comprises a second CG for a semi-persistent SPCSI on the PUSCH, wherein the first CG for the PUSCH is associated with the first priority level and the SP CSI on the PUSCH is associated with the second priority level, and Wherein determining whether the second grant overrides the first grant includes determining that the SP CSI on the PUSCH overrides the first CG for the PUSCH.

22. The method of claim 14, wherein the first grant comprises a dynamic grant DG for aperiodic CSI (AP CSI) on the PUSCH, and the second grant comprises a configuration grant CG for semi-persistent CSI (SPCSI) on the PUSCH, wherein the AP CSI on the PUSCH is associated with the first priority level and the SP CSI on the PUSCH is associated with the second priority level, and The determining whether the second grant overrides the first grant comprises determining that the SP CSI on the PUSCH overrides the AP CSI on the PUSCH.

23. The method of any one of claims 15 to 22, wherein determining whether the second grant overrides the first grant is performed without reference to a hybrid automatic repeat request (HARQ) process identifier (ID).

24. User equipment comprising means for processing each of the steps of any one of claims 1 to 10.

25. A base station comprising means for performing each of the steps of any one of claims 14 to 22.

Images