Wireless communication device and method

Abstract

A wireless communication apparatus and method are provided, the method by a user device (UE) including performing a first operation and / or a second operation for a pending scheduling request (SR). The first operation includes, when resources for an SR transmission opportunity overlap with data, the UE performing a first priority sorting based on at least one of a configured / predefined priority between an SCell BFR SR and data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than a priority of the data, and prioritizing the SCell BFR SR when Low Latency and Ultra Reliable Communication (URLLC) or high priority data is not or cannot be multiplexed into a grant. The second operation includes, when resources for an SR transmission opportunity overlap with data, performing a second priority sorting by the UE selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured for the SR.

Description

[Technical field]

[0001] The present disclosure relates to the field of communication systems, and more particularly, to a wireless communication device and method capable of providing good communication performance and / or high reliability. [Background technology]

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and the like. These wireless communication systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, power). Examples of such multiple-access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE) systems, and fifth-generation (5G) systems, also referred to as New Radio (NR) systems. A wireless multiple-access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication for multiple communication devices. These communication devices may be referred to as user devices (UEs).

[0003] A wireless communication network may include a base station capable of supporting communication for a UE. The UE may communicate with the base station via a downlink and an uplink. The downlink refers to a communication link from the base station to the UE, and the uplink refers to a communication link from the UE to the base station. In a wireless communication system operating in a high frequency band, the transmission and reception of paging will increase the signaling overhead and the power consumption of the UE. 3GPP TSG-RAN WG2 Meeting #108, R2-1915331 is prior art related to this field. More specifically, R2-1915331 discloses an option 2 in which a Secondary Cell (SCell) Beam Failure Recovery (BFR) Medium Access Control (MAC) Control Element (CE) should have a higher priority than at least a "single-entry Physical (PHR) MAC CE or a multiple-entry PHR MAC CE" and a "Buffer Status Report (BSR) (except for BSR for padding) MAC CE". Furthermore, a higher priority is under study (Further For Study, FFS) in the proposal that SCell BFR MAC CE has a higher priority than at least “data from any logical channel (except data from the Uplink Common Control Channel (UL-CCCH))”. Therefore, it is an open question how the UE performs priority sorting of Scheduling Requests (SRs) that overlap with Uplink Shared Channel (UL-SCH) resources. Furthermore, it is unclear which layer in the UE is responsible for priority sorting.

[0004] Therefore, there is a need for a wireless communication apparatus (e.g., a user device (UE) and / or a base station) and method that can solve the problems of the prior art, provide priority sorting for scheduling requests (SRs), and provide good communication performance and / or high reliability. Summary of the Invention

[0005] An object of the present disclosure is to provide a wireless communication apparatus (e.g., a user device (UE) and / or a base station) and method that can solve the problems of the prior art, provide priority sorting for scheduling requests (SRs), and provide good communication performance and / or high reliability.

[0006] In a first aspect of the disclosure, a method for wireless communication by a user device (UE) includes performing, by the UE, one or more of a first operation and a second operation for a pending scheduling request (SR), where the first operation includes the UE performing a first priority sorting based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a Low Latency and Ultra Reliable Communication (URLLC) or high priority data is not or cannot be multiplexed into a grant, and the second operation includes the UE performing a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured in the SR.

[0007] In a second aspect of the present disclosure, a method for wireless communication by a base station includes the base station determining a pending scheduling request (SR) from a user device (UE), the pending SR being associated with one or more of a first operation and a second operation, the first operation including, if resources for an SR transmission opportunity overlap with data, a first priority sorting performed by the UE is based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR if a Low Latency and Ultra Reliable Communication (URLLC) or high priority data is not or cannot be multiplexed into a grant, and the second operation includes, the UE performing a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured in the SR.

[0008] In a third aspect of the disclosure, a user device (UE) comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor configured to perform one or more of a first operation and a second operation for a pending scheduling request (SR), the first operation includes the processor performing a first priority sorting based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant, and the second operation includes the processor performing a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured in the SR.

[0009] In a fourth aspect of the present disclosure, a base station includes a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor is configured to determine a pending scheduling request (SR) from a user device (UE), the pending SR being associated with one or more of a first operation and a second operation, the first operation includes: if a resource for a SR transmission opportunity overlaps with data, a first priority sorting performed by the UE is based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant, and the second operation includes: the UE performs a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, the priority set in the SR configuration, and the resource configured in the SR.

[0010] In a fifth aspect of the present disclosure, a non-transitory machine-readable storage medium stores instructions that, when executed by a computer, cause the computer to perform the method set forth above.

[0011] In a sixth aspect of the present disclosure, the chip includes a processor that calls and executes a computer program stored in a memory, thereby causing a device in which the chip is installed to perform the above method.

[0012] In a seventh aspect of the present disclosure, a computer-readable storage medium having a computer program stored thereon causes a computer to perform the above method.

[0013] In an eighth aspect of the present disclosure, a computer program product includes a computer program, the computer program causing a computer to perform the above method.

[0014] In a ninth aspect of the present disclosure, a computer program causes a computer to carry out the above method. [Brief description of the drawings]

[0015] In order to more clearly explain the embodiments of the present disclosure or related art, the following figures are briefly introduced in the examples. It is obvious that the drawings are merely some embodiments of the present disclosure, and those skilled in the art can obtain other figures according to these figures without any effort. [Figure 1] FIG. 1 is a block diagram of one or more user devices (UEs) and a base station for wireless communication in a communication network system according to an embodiment of the present disclosure. [Diagram 2] 1 is a flowchart illustrating a wireless communication method performed by a user device (UE) according to an embodiment of the present disclosure. [Diagram 3] 1 is a flowchart illustrating a wireless communication method performed by a base station according to an embodiment of the present disclosure. [Figure 4] FIG. 1 is a block diagram of a wireless communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The embodiments of the present disclosure will be described in detail with reference to the following accompanying drawings together with technical matters, structural features, objectives to be achieved, and effects. Specifically, the terms in the embodiments of the present disclosure are merely for describing the objectives of specific embodiments, and are not intended to limit the present disclosure.

[0017] Intra-User Device (UE) Priority Sorting and Multiplexing: Resource contention between dynamic grants (DG) and configured grants (CG) for the Physical Uplink Shared Channel (PUSCH), and contention for multiple CGs.

[0018] In the current discussion, the issue of how the Medium Access Control (MAC) layer performs priority sorting of Scheduling Requests (SRs) that overlap with the Physical Uplink Shared Channel (PUSCH) is discussed. The Associated Logical Channel (LCH) is used as the principle in case of collision. The details are as follows:

[0019] In case of CGCG and CGDG contention, the priority value of the uplink grant (Uplink Shared Channel (UL-SCH) resources) is the highest priority of the LCH that is or can be multiplexed in the MAC Protocol Data Unit (PDU), taking into account LCH limitations and data availability.

[0020] If the Physical Uplink Control Channel (PUCCH) resources of an SR transmission opportunity overlap with UL-SCH resources, then SR transmission is allowed (SR transmission has priority) if the priority of the LCH that triggered the SR is higher based on a comparison between the priority of the LCH that triggered the SR and the priority value of the UL-SCH resource (this priority value is determined according to the current protocol).

[0021] In case of CG-CG conflicts with equal priority, priority sorting is up to the UE implementation.

[0022] In case of SR-Data contention with equal priority, UL-SCH (ie, data) takes precedence.

[0023] Problem 1 The current discussion focuses only on the case where SR is triggered by a Beam Failure Recovery (BFR) MAC Control Element (CE). Since the BFR MAC CE is triggered by the LCH, it is easy to say that SR is related to a specific LCH.

[0024] However, in Release 16 (Rel-16), SR can be triggered by other MAC CEs, such as BFR MAC CE. BFR MAC CE is triggered due to beam failure, which is not related to LCH but to downlink (DL) channel quality issues. Also, SR triggered by BFR MAC CE can collide with PUSCH. Therefore, it is clear that such cases cannot be handled by current Radio Layer 2 (RAN2) protocols and need to be discussed further.

[0025] Furthermore, there is a collision problem between the secondary cell (SCell) BFR SR and other SR PUCCH resources, so if the SCell BFR SR overlaps with the SR PUCCH resource, the SCell BFR SR has priority.

[0026] The protocol is as follows: The parameters beamFailureDetectionTimer and beamFailureInstanceMaxCount are configured cell-specifically for each configured DL BWP.

[0027] Upon reconfiguration of beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any of the reference signals used for beam failure detection by higher layers, BFI_COUNTER is set to 0 for a given serving cell.

[0028] If SCell BFR SR resources are not configured and SCell BFR MAC CE transmission triggers SCell BFR SR, a random access procedure on the SpCell is triggered to request UL resources to transmit the SCell BFR MAC CE (similar to Rel-15 behavior with SR).

[0029] If a SCell BFR SR is triggered and the UE has a SR PUCCH resource that overlaps with an SCell BFR SR PUCCH resource, the UE shall select the SCell BFR SR PUCCH resource for transmission.

[0030] If a MAC PDU is transmitted and this PDU contains a SCell BFR MAC CE, any pending SR for SCell beam failure recovery triggered before MAC PDU assembly must be canceled.

[0031] The SCell BFR MAC CE can carry information of multiple failed SCells, that is, multiple entry formats of the SCell BFR MAC CE are defined.

[0032] For each SCell, the SCell BFR MAC CE indicates information about the failed SCell index, an indication of whether a new candidate beam RS was detected, and / or the new candidate beam RS index (if available).

[0033] The SCell BFR MAC CE has a higher priority than at least “data from any logical channel (except data from the Uplink Common Control Channel (UL-CCCH))” and the LBT MAC CE, with higher priority being under study (FFS).

[0034] Problem 2 It is unclear which layer in the UE is responsible for priority sorting.

[0035] Regarding Scheduling Requests (SR), As long as at least one SR is pending, the MAC entity shall, for each pending SR: 1> If the MAC entity does not have a valid PUCCH resource configured for a pending SR, 2> Start the random access procedure on the SpCell and cancel the pending SR.

[0036] 1> Otherwise, for the SR configuration corresponding to the pending SR, 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource configured for SR, and 2> When the sr-ProhibitTimer is not running for the SR transmission opportunity, and 2> When the PUCCH resource for the SR transmission opportunity does not overlap with the measurement gap, and 2> When the PUCCH resource for the SR transmission opportunity does not overlap with the UL-SCH resource, 3> If SR_COUNTER < sr-TransMax, 4> Increment SR_COUNTER by 1, 4> Instruct the physical layer to transmit a signal for the SR on one valid PUCCH resource for SR, 4> Start the sr-ProhibitTimer.

[0037] 3> Otherwise, In the current discussion above, there are unresolved issues regarding how the UE performs priority sorting of scheduling requests (SRs) that overlap with uplink shared channel (UL-SCH) resources. Furthermore, it is unclear which layer of the UE is responsible for priority sorting. Therefore, some embodiments of the present disclosure propose a wireless communication device (e.g., a user device (UE) and / or a base station) and a method that can solve the problems of the prior art, provide priority sorting for scheduling requests (SRs), and provide good communication performance and / or high reliability.

[0038] FIG. 1 illustrates that in some embodiments, one or more user devices (UEs) 10 and base stations (e.g., gNBs or eNBs) 20 are provided for wireless communication in a communication network system 30 according to an embodiment of the present disclosure. The communication network system 30 includes one or more UEs 10 and base stations 20. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or the processor 21 may be configured to implement proposed functions, procedures, and / or methods described in the present disclosure. Multiple layers of an air interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled to the processor 11 or 21 and stores various information for operating the processor 11 or 21. The transceiver 13 or 23 is operatively coupled to the processor 11 or 21, the transceiver 13 or 23 transmitting and / or receiving wireless signals.

[0039] The processor 11 or 21 may include an application specific integrated circuit (ASIC), other chipset, logic circuit, and / or data processing device. The memory 12 or 22 may include a read only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage device. The transceiver 13 or 23 may include a baseband circuit for processing radio frequency signals. When an embodiment is implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 may be implemented within the processor 11 or 21 or external to the processor 11 or 21, in which case they may be communicatively coupled to the processor 11 or 21 via various means known in the art.

[0040] In some embodiments, the processor 11 is configured to perform one or more of a first operation and a second operation on a pending scheduling request (SR), where the first operation includes the processor 11 performing a first priority sort based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than the priority of the data, prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant, and the processor 11 performing a second priority sort by selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured in the SR. This can solve the problems of the prior art and can provide priority sorting for the scheduling request (SR) and provide good communication performance and / or high reliability.

[0041] In some embodiments, the processor 21 is configured to determine a pending scheduling request (SR) from a user device (UE) 10, the pending SR being associated with one or more of a first operation and a second operation, where the first operation includes: if resources of the SR transmission opportunity overlap with data, a first priority sorting performed by the UE 10 is based on at least one of: a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than the priority of the data, prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into the grant, where the second operation includes the UE 10 performing a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in the SR configuration, and a resource configured in the SR. This can solve the problems of the prior art, provide priority sorting for scheduling requests (SR), and provide good communication performance and / or high reliability.

[0042] 2 illustrates a method 200 of wireless communication by a user device (UE) 10 according to an embodiment of the present disclosure. In some embodiments, the method 200 includes block 202 of performing, by the UE 10, one or more of a first operation and a second operation for a pending scheduling request (SR), where the first operation includes the UE 10 performing a first priority sorting based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than the priority of the data, prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into the grant, and the second operation includes the UE 10 performing a second priority sorting by selecting a prioritized resource based on at least one of the SCell BFR SR resource, the priority set in the SR configuration, and the resource configured in the SR. This can solve the problems of the prior art, provide priority sorting for scheduling requests (SR), and provide good communication performance and / or high reliability.

[0043] 3 illustrates a method 300 of wireless communication by a base station 20 according to one embodiment of the present disclosure. In some embodiments, the method 300 includes block 302 in which the base station 20 determines a pending scheduling request (SR) from a user device (UE) 10, the pending SR being associated with one or more of a first operation and a second operation, where the first operation includes a first priority sorting performed by the UE 10 based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR with a higher priority than the priority of the data, prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant. Here, the second operation includes the UE 10 selecting a prioritized resource based on at least one of the SCell BFR SR resource, the priority set in the SR configuration, and the resource configured in the SR to perform a second priority sorting, which can solve the problems of the prior art, provide priority sorting for the scheduling request (SR), and provide good communication performance and / or high reliability.

[0044] In some embodiments, one or more of the first operation and / or the second operation may include one or more of the first operation and the second operation. Or, one or more of the first operation or the second operation. One or more of the first operation and the second operation may include a first operation, a second operation, or a first operation and a second operation, etc. One or more of the first operation or the second operation may include a first operation, a second operation, a plurality of first operations, or a plurality of second operations, etc. In some embodiments, the data includes an uplink shared channel (UL-SCH) resource. In some embodiments, the first priority sorting may be performed at one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE 10. In some embodiments, when the first priority sorting may be performed at the PHY layer, both the SR and the data are delivered to the PHY layer. In some embodiments, when one conflicting resource of the SR and the data is delivered to the PHY layer, the latter resource of the SR and the data is not delivered to the PHY layer. In some embodiments, if the first priority sorting can be performed at the MAC layer and the PHY layer, and the first priority sorting is performed before both SR and data are delivered to the PHY layer, then only one resource of SR and data is delivered. In some embodiments, if one conflicting resource of SR and data is delivered to the PHY layer, then the latter resource of SR and data is delivered to the PHY layer if the latter resource of SCell BFR SR and data has a higher priority or is prioritized. In some embodiments, if resources for SR transmission opportunities overlap with data, then at least one of the following is satisfied:That is, at least one of the following is satisfied: a priority sorting parameter is configured in the UE 10 and SR has a higher priority than data or SR is prioritized; a priority sorting parameter is configured in the UE 10 and it is an SCell BFR SR; a priority sorting parameter is configured in the UE 10 and it is an SCell BFR SR with a higher priority than data priority; a priority sorting parameter is configured in the UE 10 and it is an SCell BFR SR and URLLC / higher priority data is not or cannot be multiplexed into a grant; SR has a higher priority than data and SR is prioritized; it is an SCell BFR SR; it is an SCell BFR SR with a higher priority than data priority; it is an SCell BFR SR and URLLC / higher priority data is not or cannot be multiplexed into a grant.

[0045] In some embodiments, the prioritized resources include prioritized physical uplink control channel (PUCCH) resources. In some embodiments, the second priority sorting may be performed at one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE 10. In some embodiments, if the second priority sorting may be performed at the PHY layer, both the first SR and the second SR are delivered to the PHY layer. In some embodiments, if the second priority sorting may be performed at the MAC layer, one of the first SR and the second SR is delivered to the PHY layer. In some embodiments, if the first SR is delivered to the PHY layer, the latter second SR is not delivered to the PHY layer. In some embodiments, if the second priority sorting may be performed at the MAC layer and the PHY layer, and the second priority sorting is performed before the first SR and the second SR are delivered to the PHY layer, only one of the first SR and the second SR is delivered. In some embodiments, if one conflicting resource of the first SR and the second SR is delivered to the PHY layer, the latter resource of the first SR and the second SR is delivered to the PHY layer if the latter resource of the first SR and the second SR has a higher priority or if the latter resource of the first SR and the second SR is prioritized.

[0046] In some embodiments, at least one of the following is satisfied: the UE 10 is configured with priority sorting parameters and a first SR has a higher priority than a second SR triggered by a logical channel (LCH) or the first SR is prioritized, the UE 10 is configured with priority sorting parameters and it is an SCell BFR SR, the UE 10 is configured with priority sorting parameters and resources for SR transmission opportunities do not overlap with resources for SCell BFR SRs, the UE 10 is configured with priority sorting parameters and resources for SR transmission opportunities do not overlap with resources for SRs with higher priority, the first SR has a higher priority than a second SR triggered by an LCH or the first SR is prioritized and it is an SCell BFR SR, resources for SR transmission opportunities do not overlap with resources for SCell BFR SRs, resources for SR transmission opportunities do not overlap with resources for SRs with higher priority. In some embodiments, if the UE 10 is configured with priority sorting parameters and resources for an SR transmission opportunity overlap with data, then SR is prioritized. In some embodiments, the SCell BFR SR is not triggered by the LCH. In some embodiments, the SCell BFR SR is not associated with the LCH. In some embodiments, the SCell BFR SR is triggered due to beam failure.

[0047] MAC Entity Figure 1 shows that in some embodiments, the MAC entity of the UE 10 processes the following transport channels: Broadcast Channel (BCH), Downlink Shared Channel(s) (DL-SCH), Paging Channel (PCH), Uplink Shared Channel(s) (UL-SCH), and Random Access Channel(s) (RACH). In addition, the MAC entity of the UE 10 processes the following sidelink transport channels: Sidelink Shared Channel (SL-SCH) and Sidelink Broadcast Channel (SL-BCH). If the UE 10 is configured with an SCG, two MAC entities are configured in the UE: one for the Master Cell Group (MCG) and one for the Secondary Cell Group (SCG). If a MAC entity is configured with one or more SCells, there are multiple DL-SCHs per MAC entity, and there may be multiple UL-SCHs and multiple RACHs, and there is one DL-SCH, one UL-SCH, and one RACH in a special cell (SpCell), and there is one DL-SCH, zero or one UL-SCH, and zero or one RACH per SCell. In some embodiments, in case of dual connectivity operation, the term SpCell refers to the Primary Cell (PCell) of the MCG or the Primary SCell (pSCell) of the SCG, depending on whether the MAC entity is associated with the MCG or SCG, respectively. Otherwise, the term SpCell refers to the PCell. The SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access, and is always activated.

[0048] Logical Channel (LCH) The MAC sublayer provides data transmission services on logical channels. Several types of logical channels are defined to accommodate different kinds of data transmission services. That is, each type of logical channel supports the transmission of a specific type of information. The type of logical channel is defined by the type of information transmitted. The MAC sublayer provides the control and traffic channels listed in Table 1 below. [Table 1]

[0049] Example Technical solution for problem 1 For the SR collision case mentioned in problem 1, the following technical solutions can be used:

[0050] 1 shows that in some embodiments, the UE 10 performs priority sorting based on one of the following options: optionally, a configured / predefined priority between SCell BFR SR and data (UL-SCH), always prioritizing SCell BFR SR or data (UL-SCH), prioritizing SCell BFR SR with higher priority than UL-SCH priority, and / or prioritizing SCell BFR SR when URLLC / high priority data is not or cannot be multiplexed into a grant. This solves the problems of the prior art and provides priority sorting for scheduling requests (SR), which can provide good communication performance and / or high reliability.

[0051] In some embodiments, priority sorting may be performed at the MAC layer and / or the PHY layer of the UE. In some embodiments, priority sorting may be performed at the PHY layer, and both SR and data are delivered to the PHY layer. In some embodiments, priority sorting may be performed at the MAC layer, and either SR or data is delivered to the PHY layer. Optionally, if one of the conflicting resources, SR and data, is delivered to the PHY layer, the other one of the SR and data should not be delivered to the PHY layer. In some embodiments, if priority sorting can be performed at the MAC layer and the PHY layer, and priority sorting is performed before both SR and data are delivered to the PHY layer, only one resource is delivered. If one conflicting resource is delivered to the PHY layer, the latter resource is delivered to the PHY layer if it has a higher priority or is prioritized.

[0052] Technical solution for problem 2 For the SR collision case mentioned in problem 2, the following technical solutions can be used.

[0053] 1 shows that in some embodiments, the UE 10 selects a prioritized PUCCH resource according to at least one of the SCell BFR SR PUCCH resource, the priority set in the SR configuration, and / or the PUCCH resource configured in the SR, which can solve the problems of the prior art, provide priority sorting for the scheduling request (SR), and provide good communication performance and / or high reliability.

[0054] In some embodiments, priority sorting may be performed at the MAC layer and / or the PHY layer of the UE. In some embodiments, priority sorting may be performed at the PHY layer, where all SRs are delivered to the PHY layer. In some embodiments, priority sorting may be performed at the MAC layer, where one of the SRs is delivered to the PHY layer. Optionally, if one SR is delivered to the PHY layer, later SRs may not be delivered to the PHY layer. In some embodiments, if priority sorting can be performed at the MAC layer and the PHY layer, and priority sorting is performed before all SRs are delivered to the PHY layer, only one SR is delivered. If one conflicting resource is delivered to the PHY layer, the later resource is delivered to the PHY layer if it has a higher priority or is prioritized.

[0055] An implementation of the procedures in the MAC specification may be as follows.

[0056] Problem 1, Option 1 Scheduling Request (SR) As long as at least one SR is pending, the MAC entity MUST do the following for each pending SR:

[0057] 1> If the MAC entity does not have a valid PUCCH resource configured for a pending SR, 2> Initiate a random access procedure on the SpCell and cancel any pending SR.

[0058] 1> Otherwise, for the SR configuration that corresponds to the pending SR, 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource configured for SR, and 2> The sr-ProhibitTimer is not running during an SR transmission opportunity, and 2> If the PUCCH resources for SR transmission opportunities do not overlap with the measurement gaps, 3> The PUCCH resources for the SR transmission opportunity do not overlap with the UL-SCH resources, or 3> If priorityBasedPrioritization is configured for the MAC entity, and the PUCCH resources for SR transmission opportunities overlap with the UL-SCH resources and SR is prioritized, or 3> If the PUCCH resources for SR transmission opportunities overlap with the UL-SCH resources and any of A is satisfied, 4> When SR_COUNTER < sr-TransMax, 5> Increment SR_COUNTER by 1, 5> Instruct the physical layer to signal SR on one valid PUCCH resource for SR, 5> Start sr-ProhibitTimer.

[0059] 4> Otherwise, 5> Notify RRC to release the PUCCH of all serving cells, 5> Notify RRC to release the SRS of all serving cells, 5> Clear all configured downlink allocations and uplink grants, 5> Clear all PUSCH resources for semi-persistent CSI reporting, 5> Start a random access procedure on the SpCell and cancel all pending SRs.

[0060] A is including that the MAC entity is configured with priorityBasedPrioritizationM and SR has a higher priority than UL-SCH / SR is prioritized, or that the MAC entity is configured with priorityBasedPrioritizationM and it is an SCell BFR SR, or that the MAC entity is configured with priorityBasedPrioritizationM and it is an SCell BFR SR with a higher priority than the UL-SCH priority, or that the MAC entity is configured with priorityBasedPrioritizationM and it is an SCell BFR SR and URLLC / higher priority data is not or cannot be multiplexed into the grant, or that SR has a higher priority than UL-SCH / SR is prioritized, or that it is an SCell BFR SR, or that it is an SCell BFR SR with a higher priority than the UL-SCH priority, or that it is an SCell BFR SR and URLLC / higher priority data is not or cannot be multiplexed into the grant.

[0061] Furthermore, one of the following is a criterion as to whether it is a preferred SR: a configured / predefined priority between SCell BFR SR and data (UL-SCH), or always prioritizing SCell BFR SR or data (UL-SCH), or prioritizing SCell BFR SR with higher priority than UL-SCH priority, or prioritizing SCell BFR SR if URLLC / higher priority data is not or cannot be multiplexed into the grant.

[0062] Problem 2, Option 2 Scheduling Request (SR) As long as at least one SR is pending, the MAC entity MUST do the following for each pending SR:

[0063] 1> If the MAC entity does not have a valid PUCCH resource configured for the pending SR, 2> Start a random access procedure on the SpCell and cancel the pending SR.

[0064] 1> Otherwise, for the SR configuration corresponding to the pending SR, 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource configured for SR, and 2> The sr-ProhibitTimer is not running for the SR transmission opportunity, and 2> The PUCCH resource for the SR transmission opportunity does not overlap with a measurement gap, and 3> The PUCCH resource for the SR transmission opportunity does not overlap with a UL-SCH resource, or 3> priorityBasedPrioritization is configured for the MAC entity, and the PUCCH resource for the SR transmission opportunity overlaps with a UL-SCH resource and the SR is prioritized, or 3> If any of A is satisfied, 4> If SR_COUNTER < sr-TransMax, 5> Increment SR_COUNTER by 1, 5> Instruct the physical layer to send a signal for the SR on one valid PUCCH resource for SR, 5> Start the sr-ProhibitTimer.

[0065] 4> Otherwise, 5> Notify the RRC to release the PUCCH of all serving cells, 5> Notify the RRC to release the SRS of all serving cells, 5> Clear all configured downlink allocations and uplink grants, 5> Clear all PUSCH resources for semi-persistent CSI reporting, 5> Initiate a random access procedure on the SpCell and cancel all pending SRs.

[0066] A is, or the MAC entity is configured with priorityBasedPrioritizationM and SR has higher priority / SR is prioritized over other SRs triggered by LCH, or the MAC entity is configured with priorityBasedPrioritizationM and it is an SCell BFR SR, or the MAC entity is configured with priorityBasedPrioritizationM and the PUCCH resources of the SR transmission opportunity do not overlap with the PUCCH resources of the SCell BFR SR, or the MAC entity is configured with priorityBasedPrioritizationM and the PUCCH resources of the SR transmission opportunity do not overlap with the PUCCH resources of the SR of a higher priority (i.e., SCell BFR SR), or the SR has higher priority / SR is prioritized over other SRs triggered by LCH, or it is an SCell BFR SR, or the PUCCH resources of the SR transmission opportunity do not overlap with the PUCCH resources of the SCell BFR SR, or the PUCCH resources of the SR transmission opportunity do not overlap with the PUCCH resources of the SCell BFR SR, or the PUCCH resources of the SR transmission opportunity do not overlap with the PUCCH resources of the SR of a higher priority (i.e., SCell BFR This includes not overlapping with the PUCCH resources of BFR SR).

[0067] In some embodiments, the implementation of the procedures in the MAC specification may be as follows.

[0068] Scheduling Request (SR) Scheduling Request (SR) is used to request UL-SCH resources for new transmissions. A MAC entity may be configured with zero, one or multiple SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. In case of logical channel or SCell beam failure recovery and consistent LBT failure, at most one PUCCH resource is configured per BWP for SR. Each SR configuration corresponds to one or more logical channels and / or SCell beam failure recovery and / or consistent LBT failure. Each logical channel, SCell beam failure recovery and consistent LBT failure can be mapped to zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers BSR or SCell beam failure recovery or consistent LBT failure (if such configuration exists) is considered as the SR configuration corresponding to the triggered SR. Any SR configuration can be used for SR triggered by preemptive BSR. Furthermore, each SR configuration corresponds to one or more logical channels and / or SCell beam failure recovery. This proves that BFR SR is not related to LCH. As a beneficial effect, in the prior art, BFR is higher than BSR, and BSR is higher than LCH transmission. Usually, the higher priority should be transmitted first. The priority transmission of the BSR is now. BFR has higher priority. However, BFR is not transmitted first because we consider that repair of SCell BFR itself is not a very urgent issue and there is also PCell downlink. Also, data may require LCH data with high delay, so we need to ensure priority transmission of such services. In this way, it is compatible with the original technology and has achieved the desired effect. In some embodiments, in Release 16 (Rel-16), SR can be triggered by other MAC CEs, such as BFR MAC CE. BFR MAC CE is triggered due to beam failure, which is not related to LCH, but to downlink (DL) channel quality issues. Therefore, BFR MAC CE is not triggered by LCH.BFR SR is not triggered by LCH.

[0069] RRC configures the following parameters for the Scheduling Request procedure: sr-ProhibitTimer (per SR configuration) and / or sr-TransMax (per SR configuration).

[0070] The following UE variables are used for the scheduling request procedure: SR_COUNTER (per SR configuration).

[0071] When an SR is triggered and there are no other pending SRs corresponding to the same SR configuration, the MAC entity MUST set the SR_COUNTER of the corresponding SR configuration to 0.

[0072] When an SR is triggered, it shall be considered pending until it is cancelled. If a MAC PDU is transmitted and this PDU contains a long or short BSR MAC CE (containing the buffer status up to (and including) the last event that triggered a BSR before MAC PDU assembly), all pending SRs for BSRs triggered according to the BSR procedure before MAC PDU assembly, except for SCell beam failure recovery, shall be cancelled and their corresponding sr-ProhibitTimers shall be stopped. If the (multiple) UL grants can accommodate all pending data available for transmission, all pending SRs for BSRs triggered according to the BSR procedure, except for SCell beam failure recovery, shall be cancelled and their corresponding sr-ProhibitTimers shall be stopped. When a MAC PDU containing an associated preemptive BFR MAC CE is transmitted, all pending SRs for preemptive BSRs triggered according to the preemptive BSR procedure before MAC PDU assembly, shall be cancelled and their corresponding sr-ProhibitTimers shall be stopped. If a MAC PDU is transmitted and this PDU contains a BFR MAC CE or a Truncated BFR MAC CE (containing beam failure recovery information for that SCell), any pending SR triggered due to beam failure recovery for the SCell shall be canceled and the respective corresponding sr-ProhibitTimer shall be stopped. Any pending SR triggered due to beam failure recovery for the SCell shall be canceled upon deactivation of that SCell.

[0073] The MAC entity shall do the following for each pending SR triggered by a consistent LBT failure of the serving cell:

[0074] 1> When a MAC PDU is transmitted and the MAC PDU contains an LBT failure MAC CE indicating a consistent LBT failure of the serving cell that triggered the SR, or 1> All consistent LBT failures triggered for the serving cell that triggered the SR are cancelled. 2> Cancel any pending SR and stop the corresponding sr-ProhibitTimer (if it is running).

[0075] Only PUCCH resources on the BWP that are active during a SR transmission opportunity are considered valid.

[0076] As long as at least one SR is pending, the MAC entity MUST do the following for each pending SR:

[0077] 1> If the MAC entity does not have a valid PUCCH resource configured for a pending SR, 2> Initiate a random access procedure on the SpCell and cancel any pending SR.

[0078] 1> Otherwise, for the SR configuration that corresponds to the pending SR, 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource for an SR configuration, and 2> The sr-ProhibitTimer is not running during an SR transmission opportunity, and 2> If the PUCCH resources for SR transmission opportunities do not overlap with the measurement gaps, 3> The PUCCH resources for the SR transmission opportunity do not overlap with either the UL-SCH resources or the SL-SCH resources, or 3> The MAC entity is able to perform the SR transmission simultaneously with the transmission of the SL-SCH resource, or 3> If the MAC entity is configured with lch-based Prioritization and the PUCCH resources for the SR transmission opportunity do not overlap with the PUSCH period of the uplink grant or MSGA payload received in the random access response, and the PUCCH resources of the SR transmission opportunity triggered for a pending SR overlap with any other UL-SCH resources, the physical layer may signal the SR on one valid PUCCH resource of the SR, and the priority of the logical channel that triggered the SR is higher than the uplink grant priority of any UL-SCH resource (where the uplink grant priority has not yet been lowered), and the uplink grant priority is determined, or 3> Both sl-Prioritizationthres and ul-Prioritizationthres are configured, the PUCCH resources of a triggered SR transmission opportunity for a pending SR overlap with any UL-SCH resources carrying a MAC PDU, the determined priority of the triggered SR is lower than sl-Prioritizationthres, the value of the highest priority of any logical channel in the MAC PDU is equal to or greater than ul-Prioritizationthres, and the MAC PDU has not been prioritized by higher layers, or 3> An SL-SCH resource overlaps with a PUCCH resource of an SR transmission opportunity triggered for a pending SR, and the MAC entity cannot perform the SR transmission simultaneously with the transmission on the SL-SCH resource, and the transmission on the SL-SCH resource is not prioritized or the priority value of the logical channel that triggered the SR is lower than ul-Prioritizationthres (if configured), or 3> If the SL-SCH resource overlaps with the PUCCH resource of the SR transmission opportunity triggered for a pending SR, and the MAC entity cannot perform the SR transmission simultaneously with the transmission of the SL-SCH resource, and the determined priority of the triggered SR is higher than the determined priority of the MAC PDU for the SL-SCH resource; 4> Consider the SR transmission as the preferred SR transmission.

[0079] 4> Treat other overlapping uplink grants (if any) as down-prioritized uplink grants; 4> If SR_COUNTER < sr-TransMax, 5> Instruct the physical layer to transmit a signal to the SR on one available PUCCH resource for the SR; 5> If no LBT failure indication is received from the lower layer, 6> Increment SR_COUNTER by 1, 6> Start sr-ProhibitTimer.

[0080] 5> Else, if lbt-FailureRecoveryConfig is not configured, 6> Increment SR_COUNTER by 1.

[0081] 4>Otherwise, 5> Inform RRC to release the PUCCH of all serving cells; 5> Inform RRC to release SRS of all serving cells, 5> Clear all configured downlink assignments and uplink grants, 5> Clear all PUSCH resources for semi-persistent CSI reporting, 5> Initiate a random access procedure on the SpCell and cancel all pending SRs.

[0082] 3>Otherwise, 4> Treat the SR transmission as a deprioritized SR transmission.

[0083] In NOTE 1, except for SR for SCell beam failure recovery, when the MAC entity has multiple overlapping valid PUCCH resources for SR transmission opportunities, the selection of a valid PUCCH resource for SR to signal to the SR is left to the UE implementation.

[0084] In NOTE 2, if multiple individual SRs trigger instructions from the MAC entity to the PHY layer to signal an SR on the same enabled PUCCH resource, the SR_COUNTER of the associated SR configuration is incremented only once.

[0085] NOTE 3: If the MAC entity has a pending SR for SCell beam failure recovery and the MAC entity has one or more PUCCH resources that overlap with the PUCCH resources of the SCell beam failure recovery for a SR transmission opportunity, the MAC entity shall consider only the PUCCH resources for SCell beam failure recovery as valid.

[0086] For UEs operating in semi-static channel access mode, PUCCH resources that overlap with idle times of a fixed frame period are considered not valid.

[0087] For pending SRs of BSR and BFR for which no valid PUCCH resources are configured, the MAC entity may stop the ongoing random access procedure (if any), which is initiated by the MAC entity before MAC PDU assembly. For pending SRs of BSR, the ongoing random access procedure may be stopped when a MAC PDU is transmitted using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload, and the PDU contains a BSR MAC CE (including the buffer status up to and including the last event that triggered the BSR before MAC PDU assembly) or when the UL grant(s) can accommodate all pending data available for transmission. Alternatively, for pending SRs of BFR of SCell, the ongoing random access procedure may be stopped when a MAC PDU is transmitted using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload, and the PDU contains a BFR MAC CE or a truncated BFR MAC CE (including beam failure recovery information for that SCell). Deactivating a SCell with beam failure detection configured may cause an ongoing random access procedure to be stopped due to a pending SR for a BFR if all BFRs triggered for the SCell are cancelled.

[0088] Once all SCells that triggered the consistent LBT failure are deactivated or a MAC PDU is sent using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload, and this PDU contains an LBT failure MAC CE (indicating consistent LBT failures for all cells that triggered the consistent LBT failure), the MAC entity may stop the ongoing random access procedure (if any) for a pending SR of consistent LBT failure for which no valid PUCCH resources are configured.

[0089] Buffer Status Reporting (BSR) The Buffer Status Reporting (BSR) procedure is used to provide the serving gNB with information about the amount of UL data in the MAC entity.

[0090] RRC configures the following parameters to control BSR: periodicBSR-Timer, retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelSR-DelayTimer, logicalChannelSR-Mask, and logicalChannelGroup.

[0091] Each logical channel can be assigned to an LCG using logicalChannelGroup. The maximum number of LCGs is 8. The MAC entity determines the amount of UL data available for a logical channel according to the data amount calculation procedure.

[0092] A BSR must be triggered if any of the following events occur:

[0093] UL data of logical channels belonging to an LCG becomes available to the MAC entity, and this UL data belongs to a logical channel with a higher priority than the priority of any logical channel with available UL data belonging to any LCG, or none of the logical channels belonging to the LCG contain any available UL data. In this case, the BSR is hereinafter referred to as "Regular BSR". If UL resources are allocated and the number of padding bits is equal to or greater than the size of the Buffer Status Report MAC CE and its subheader, the BSR is hereinafter referred to as "Padding BSR". If the retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains UL data, the BSR is hereinafter referred to as "Regular BSR". If the periodicBSR-Timer expires, the BSR is hereinafter referred to as "Periodic BSR".

[0094] In NOTE 1, if a regular BSR triggering event occurs simultaneously for multiple logical channels, each logical channel triggers one separate regular BSR.

[0095] For a normal BSR, the MAC entity must:

[0096] 1> When a BSR is triggered for a logical channel for which the logicalChannelSR-DelayTimerApplied value configured by higher layers is true, 2> Start or restart the logicalChannelSR-DelayTimer.

[0097] 1>Otherwise, 2> Stop the logicalChannelSR-DelayTimer if it is running.

[0098] For normal and periodic BSR, the MAC entity must:

[0099] 1> If multiple LCGs have data available for transmission when a MAC PDU containing a BSR is constructed, 2> Report the long BSR for all LCGs that have data available for transmission.

[0100] 1>Otherwise, 2> Report a short BSR.

[0101] For a padding BSR, the MAC entity must:

[0102] 1> If the number of padding bits is greater than or equal to the size of the short BSR and its subheaders, but less than the size of the long BSR and its subheaders, 2> When a BSR is established, if multiple LCGs have data available for transmission, 3> If the number of padding bits is equal to the size of the short BSR plus its subheader, 4> Report a short truncated BSR for the LCG with the highest priority logical channel that has data available for transmission.

[0103] 3>Otherwise, 4> In each of these LCGs, report the Long Truncated BSR of the LCG with the highest priority logical channel that has data available for transmission according to descending order of highest priority logical channels (with or without data available for transmission) or, in case of equal priority, according to ascending order of LCGID.

[0104] 2>Otherwise, 3> Report a short BSR.

[0105] 1> Otherwise, if the number of padding bits is equal to or greater than the size of the Long BSR and its subheaders, 2> Report the long BSR for all LCGs that have data available for transmission.

[0106] In the case of a BSR triggered by the expiry of the retxBSR-Timer, the MAC entity shall consider the logical channel that triggered the BSR to be the highest priority logical channel that has data available for transmission at the time the BSR was triggered.

[0107] A MAC entity must:

[0108] 1> If the Buffer Status Reporting procedure determines that at least one BSR has been triggered and not canceled, 2> If, as a result of the priority sorting of logical channels, UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the BSR MAC CE and its subheader, 3> Direct the multiplexing and assembly procedure to create (multiple) BSR MAC CEs; 3> Start or restart the periodicBSR-Timer, unless all the generated BSRs are long or short truncated BSRs; 3> Start or restart the retxBSR-Timer.

[0109] 2> If normal BSR is triggered and logicalChannelSR-DelayTime is not executed, 3> There are no UL-SCH resources available for new transmissions, or 3> A regular BSR is triggered for a logical channel for which the MAC entity has configured uplink grants and logicalChannelSR-Mask is set to false, or 3> If the UL-SCH resources available for new transmissions do not satisfy the LCP mapping restrictions configured for the logical channel that triggered the BSR, 4> Trigger a scheduling request.

[0110] In NOTE 2, a UL-SCH resource is considered available if the MAC entity has an active configuration for any type of configured uplink grant, or if the MAC entity has received a dynamic uplink grant, or if both of these conditions are met. If the MAC entity determines that a UL-SCH resource is available at a particular time, this does not imply that the UL-SCH resource is available at that time.

[0111] Even if multiple events trigger a BSR, a MAC PDU MUST contain at most one BSR MAC CE. Regular BSR and periodic BSR MUST take precedence over padding BSR.

[0112] The MAC entity shall restart retxBSR-Time upon receiving a grant for the transmission of new data on any UL-SCH.

[0113] If the UL grant(s) can accommodate all pending data available for transmission, but are not sufficient to additionally accommodate the BSR MAC CE and its subheaders, then all triggered BSRs may be cancelled. If a MAC PDU is transmitted and this PDU contains a long or short BSR MAC CE (containing the buffer status up to and including the last event that triggered a BSR before MAC PDU assembly), then all BSRs triggered before MAC PDU assembly must be cancelled.

[0114] NOTE 3: MAC PDU assembly may occur at any time between the receipt of an uplink grant and the actual transmission of the corresponding MAC PDU. BSR and SR may be triggered after assembly of a MAC PDU containing a BSR MAC CE and before transmitting this MAC PDU. Additionally, BSR and SR may be triggered during MAC PDU assembly.

[0115] Note 4: Void In NOTE 5, if a cg-RetransmissionTimer is configured for an HARQ process and a BSR is already included in a MAC PDU for transmission by this HARQ process, but has not yet been transmitted by lower layers, it is up to the UE implementation how to handle the BSR content.

[0116] Commercial benefits of some embodiments are as follows: 1. Resolves problems in the prior art. 2. Provides priority sorting for Scheduling Requests (SR). 3. Provides superior communication performance. 4. Provides high reliability. 5. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automobile manufacturers (including cars, trains, trucks, buses, bicycles, motobikes, helmets, etc.), drones (unmanned aerial vehicles), smartphone manufacturers, communication devices for public safety, and AR / VR device manufacturers (e.g., games, conferences / seminars, educational purposes). Some embodiments of the present disclosure are combinations of "techniques / processes" that can be adopted in 3GPP specifications to create end products. Some embodiments of the present disclosure can be adopted for 5G NR unlicensed band communication. Some embodiments of the present disclosure propose technical mechanisms.

[0117] FIG. 4 is a block diagram of an exemplary system 700 for wireless communication according to an embodiment of the present disclosure. The embodiments described herein may be implemented in a system using any suitably configured hardware and / or software. FIG. 4 illustrates a system 700 including at least a radio frequency (RF) circuit 710, a baseband circuit 720, an application circuit 730, a memory / storage 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, which are coupled to each other. The application circuit 730 may include, but is not limited to, one or more single-core or multi-core processor circuits. The processor may include any combination of general-purpose processors and special-purpose processors, such as graphics processors, application processors, etc. The processor may be coupled to the memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or operating systems to run on the system.

[0118] The baseband circuitry 720 may include, but is not limited to, one or more single-core or multi-core processor circuits. The processor may include a baseband processor. The baseband circuitry may process various radio control functions, which may communicate with one or more radio networks via RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communications with an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs). An embodiment in which the baseband circuitry is configured to support wireless communications of multiple radio protocols may be referred to as a multimode baseband circuit.

[0119] In various embodiments, the baseband circuitry 720 may include circuitry for operating with signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry for operating with signals having intermediate frequencies that are between baseband frequencies and radio frequencies. The RF circuitry 710 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry for operating with signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry for operating with signals having intermediate frequencies that are between baseband frequencies and radio frequencies.

[0120] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to a user device, eNB, or gNB may be embodied in whole or in part in one or more of an RF circuitry, a baseband circuitry, and / or an application circuitry. As used herein, a "circuitry" refers to or is a portion of an application specific integrated circuit (ASIC), an electronic circuitry, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group), combinatorial logic circuitry, and / or other suitable hardware components that provide the described functionality. In some embodiments, an electronic device circuitry may be implemented in one or more software or firmware modules, or functionality associated with a circuitry may be implemented in one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / storage may be implemented together on a system on a chip (SOC). The memory / storage 740 may be used, for example, to load and store data and / or instructions used in the system. The memory / storage of one embodiment may include any combination of suitable volatile memory (eg, dynamic random access memory (DRAM)) and / or non-volatile memory (eg, flash memory).

[0121] In various embodiments, I / O interface 780 may include one or more user interfaces designed to enable user interaction with the system and / or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces include, but are not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. Peripheral component interfaces include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power interface. In various embodiments, sensors 770 may include one or more sensing devices for determining environmental conditions and / or position information associated with the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with baseband circuitry and / or RF circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0122] In various embodiments, the display 750 may include displays such as liquid crystal displays and touch screen displays. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or a different architecture. If desired, the methods described herein may be implemented as a computer program. The computer program may be stored in a storage medium, such as a non-transitory storage medium.

[0123] Those skilled in the art should understand that each of the units, algorithms, and steps described and disclosed in the embodiments of the present disclosure can be realized using electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the application conditions and design requirements of the solution. Those skilled in the art can use different methods to realize the functions for each specific application, but such realization should not be considered beyond the scope of the present disclosure. It should be understood that the work processes of the above systems, devices, and units are basically the same, so those skilled in the art can refer to the work processes of the systems, devices, and units in the above embodiments. For convenience and simplicity of description, these work processes will not be described in detail here.

[0124] In the embodiments of the present disclosure, it should be understood that the disclosed system, device, and method may be realized in other ways. For example, the above-mentioned embodiments are merely examples, and the division of the above units is merely a division according to logical functions, and may be divided in other ways when actually realized. A plurality of units or components may be combined or integrated into another system. Some features may be omitted or not implemented. Meanwhile, the couplings or direct couplings or communication connections between the shown or discussed mutually may be through some interfaces, and the indirect couplings or communication connections by the devices or units may be electrical, mechanical, or other forms.

[0125] The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, i.e., they may be located at one place or distributed over multiple network units. Depending on the purpose of the embodiment, some or all of the units may be used. Note that each functional unit according to each embodiment may be integrated into one physically independent processing unit, or may be integrated into one processing unit having two or more units.

[0126] When realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical means proposed in this disclosure can be essentially or partially embodied in the form of a software product. Alternatively, the part of the technical means that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes some instructions that cause a computer device (e.g., a personal computer, a server, or a network device) to execute all or part of the steps described in the embodiments of the present disclosure. The storage medium includes a USB memory, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or other types of media that can store program code.

[0127] While the present disclosure has been described in connection with what are considered to be the most practical and preferred embodiments, the present disclosure is not limited to the disclosed embodiments, but is intended to cover various arrangements that may be made without departing from the broadest interpretation of the appended claims.

Claims

1. 1. A method of wireless communication by a user device (UE), comprising: performing, by the UE, one or more of a first operation and / or a second operation for a pending scheduling request (SR); The first operation includes, when resources for a SR transmission opportunity overlap with data, the UE performing a first priority sorting based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant; The second operation includes the UE selecting a prioritized resource based on at least one of the SCell BFR SR resource, a priority set in an SR configuration, and a resource configured in an SR to perform a second priority sorting.

23. A wireless communication method comprising:

2. The data includes uplink shared channel (UL-SCH) resources.

2. The method of claim 1 .

3. The first priority sorting may be performed in one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE.

3. The method according to claim 1 or 2.

4. A wireless communication method by a base station, comprising: determining a pending Scheduling Request (SR) from a user device (UE), the pending SR being associated with one or more of a first action and a second action; The first operation includes, when resources for a SR transmission opportunity overlap with data, a first priority sorting performed by the UE is based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant; The second operation includes the UE selecting a prioritized resource based on at least one of an SCell BFR SR resource, a priority set in an SR configuration, and a resource configured in an SR to perform a second priority sorting.

23. A wireless communication method comprising:

5. The data includes uplink shared channel (UL-SCH) resources.

5. The method of claim 4.

6. The first priority sorting may be performed in one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE.

6. The method according to claim 4 or 5.

7. Memory, A transceiver; a processor coupled to the memory and the transceiver; the processor is configured to perform one or more of a first operation and / or a second operation for a pending scheduling request (SR); The first operation includes, when resources for a SR transmission opportunity overlap with data, the processor performing a first priority sorting based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant; The second operation includes the processor selecting a prioritized resource based on at least one of an SCell BFR SR resource, a priority set in an SR configuration, and a resource configured in an SR to perform a second priority sort. A user device comprising:

8. The data includes uplink shared channel (UL-SCH) resources.

8. A user device as claimed in claim 7.

9. The first priority sorting may be performed in one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE. A user device according to claim 7 or 8.

10. Memory, A transceiver; a processor coupled to the memory and the transceiver; The processor is configured to determine a pending scheduling request (SR) from a user device (UE), the pending SR associated with one or more of a first action and a second action; The first operation includes, when resources for a SR transmission opportunity overlap with data, a first priority sorting performed by the UE is based on at least one of a configured / predefined priority between a secondary cell (SCell) beam failure recovery (BFR) SR and the data, prioritizing the SCell BFR SR or prioritizing the data, prioritizing the SCell BFR SR having a higher priority than a priority of the data, and prioritizing the SCell BFR SR when a low latency and ultra reliable communication (URLLC) or high priority data is not or cannot be multiplexed into a grant; The second operation includes the UE selecting a prioritized resource based on at least one of an SCell BFR SR resource, a priority set in an SR configuration, and a resource configured in an SR to perform a second priority sorting. A base station comprising:

11. The data includes uplink shared channel (UL-SCH) resources. The base station according to claim 10 .

12. The first priority sorting may be performed in one or more of a medium access control (MAC) layer and a physical (PHY) layer of the UE.

12. The base station according to claim 10 or 11.

Images