Enhanced Scheduling Request for 5G Networks

Abstract

An apparatus of a user equipment (UE) includes processing circuitry coupled to a memory. In order to configure the UE for transmitting data in a New Radio - Unlicensed (NR - U) spectrum, the processing circuitry decodes Radio Resource Control (RRC) signaling from a base station. The RRC signaling includes configuration information to configure a Listen - Before - Talk (LBT) timer and a Scheduling Request (SR) prohibition timer. When the LBT timer is activated, an LBT procedure is performed. Based on detecting unoccupied transmission resources within the NR - U spectrum during the LBT procedure, an SR is encoded for transmission to the base station. The SR transmission activates the SR prohibition timer. In response to the SR, an uplink grant from the base station is decoded, which is received when the SR prohibition timer is activated. Based on the uplink grant, a Buffer Status Report (BSR) is encoded for transmission to the base station.

Description

[0001] Priority Claim

[0002] This application claims the benefit of priority of U.S. Provisional Patent Application Serial No. 62 / 753,830, filed on Oct. 31, 2018, entitled “SCHEDULING REQUEST ENHANCEMENT FOR NR UNLICENSED”, the entire disclosure of which is incorporated herein by reference. Field of the Invention

[0003] Aspects relate to wireless communication. Some aspects relate to wireless networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth generation (5G) networks including 5G New Radio (NR) (or 5G-NR) networks, 5G-LTE networks, and 5G NR Unlicensed Spectrum (NR-U) networks. Other aspects relate to systems and methods for scheduling request (SR) enhancement for 5G networks, including NR-U networks. Background of the Invention

[0004] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platforms. With the increase in the number of different types of devices communicating with various network devices, the use of 3GPP LTE systems has increased. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for multiple networked devices in many different environments. The fifth generation (5G) wireless systems are upcoming and are expected to enable higher speeds, connectivity, and availability. The next generation 5G networks (or NR networks) are expected to improve throughput, coverage, and robustness, and reduce latency as well as operational and capital expenditures. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced and additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions, thereby providing fast and rich content and services. Since current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies can benefit from their high bandwidth.

[0005] Potential LTE operations in unlicensed spectrum include (and are not limited to) LTE operations in unlicensed spectrum via dual connectivity (DC) or DC-based LAA and stand-alone LTE systems, according to which LTE-based technologies operate only in unlicensed spectrum without an “anchor” in licensed spectrum, and this method is called MulteFire. MulteFire combines the performance advantages of LTE technologies with the simplicity of Wi-Fi-like deployments.

[0006] In future releases and 5G systems, it is expected that the LTE system will be further enhanced in operation in both licensed and unlicensed spectra. Such enhancements can include techniques for SR enhancements for 5G networks, including NR-U networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals with different letter suffixes may represent different instances of similar components. The drawings generally illustrate, by way of example and not limitation, the various aspects described in this document.

[0008] Figure 1A An architecture of a network according to some aspects is shown.

[0009] Figure 1B and Figure 1C A non-roaming 5G system architecture according to some aspects is shown.

[0010] Figure 2 A swimlane diagram of a communication exchange between a user equipment and a base station using scheduling request enhancement techniques according to some aspects is shown.

[0011] Figure 3 A block diagram of a communication device according to some aspects is shown, such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE). DETAILED DESCRIPTION

[0012] The following description and the drawings fully disclose aspects such that those skilled in the art can practice these aspects. Other aspects may incorporate structural changes, logical changes, electrical changes, process changes, and other changes. Parts and features of some aspects may be included in parts and features of other aspects or may replace parts and features of other aspects. The aspects set forth in the claims cover all available equivalents of these claims.

[0013] Figure 1Aillustrates the architecture of a network in accordance with some aspects. Network 140A is shown as including user equipment (UE) 101 and UE 102. UE 101 and UE 102 are shown as smart phones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless telephone, drone, or any other computing device including wired and / or wireless communication interfaces. UE 101 and UE 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0014] Any radio link described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard.

[0015] LTE and LTE-Advanced are wireless communication standards for high-speed data for UEs such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique according to which multiple carrier signals operating at different frequencies may be used to carry communications for a single UE, thereby increasing the bandwidth available for a single device. In some aspects, carrier aggregation may be used when one or more component carriers operate at unlicensed frequencies.

[0016] Aspects described herein may be used in the context of any spectrum management scheme, including for example dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as licensed shared access (LSA) at 2.3 GHz - 2.4 GHz, 3.4 GHz - 3.6 GHz, 3.6 GHz - 3.8 GHz, and other frequencies, and spectrum access systems (SAS) at 3.55 GHz - 3.7 GHz and other frequencies).

[0017] Aspects described herein may also be applied to different single-carrier or OFDM families (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) by assigning OFDM carrier data bit vectors to corresponding symbol resources, and specifically to 3GPP NR (New Radio).

[0018] In some aspects, either UE 101 or UE 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some aspects, either UE 101 or UE 102 may include a NarrowBand (NB) IoT UE (e.g., such as an Enhanced NB-IoT (eNB-IoT) UE and a Further Enhanced (FeNB-IoT) UE). IoT UEs may utilize technologies such as Machine-to-Machine (M2M) or Machine-Type Communication (MTC) to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity-Based Services (ProSe), or Device-to-Device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be machine-initiated data exchange. The IoT network includes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) that utilize short-lived connections. IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connections to the IoT network.

[0019] In some aspects, either UE 101 or UE 102 may include an Enhanced MTC (eMTC) UE or a Further Enhanced MTC (FeMTC) UE.

[0020] UE 101 and UE 102 may be configured to connect (e.g., communicatively couple) to a Radio Access Network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NGRAN), or some other type of RAN. UE 101 and UE 102 respectively utilize connections 103 and 104, where each connection includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces to enable communicative coupling and may be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long-Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, etc.

[0021] In one aspect, UE 101 and UE 102 may also directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface including one or more logical channels, the one or more logical channels including but not limited to Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0022] UE 102 is shown as being configured to access an access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as (for example) a connection compliant with any IEEE 802.11 protocol, according to which AP 106 may include a Wireless Fidelity (WiFi ® ) router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0023] RAN 110 may include one or more access nodes enabling connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may include terrestrial sites (e.g., terrestrial access points) or satellite sites covering a certain geographical area (e.g., a cell). In some aspects, communication nodes 111 and 112 may be transmission / reception points (TRPs). In the case where communication node 111 and communication node 112 are Node Bs (e.g., eNB or gNB), one or more TRPs may function within the communication cell of the Node B. RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells, and one or more RAN nodes (e.g., low-power (LP) RAN node 112) for providing femtocells or picocells (e.g., cells having a smaller coverage area, smaller user capacity, or higher bandwidth compared to macro cells).

[0024] Either of RAN node 111 and RAN node 112 may terminate the air interface protocol and may be the first point of contact for UE 101 and UE 102. In some aspects, either of RAN node 111 and RAN node 112 may perform various logical functions of RAN 110, 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. In one example, either of node 111 and / or node 112 may be a new generation Node-B (gNB), evolved Node-B (eNB), or another type of RAN node.

[0025] RAN 110 is shown as communicatively coupled to a core network (CN) 120 via an SI interface 113. In some aspects, CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (e.g., as referenced Figure 1B - Figure 1C shown). In this aspect, the SI interface 113 is divided into two parts: an S1-U interface 114, which bears traffic data between RAN nodes 111 and 112 and a serving gateway (S-GW) 122; and an SI-mobility management entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and an MME 121.

[0026] In this aspect, CN 120 includes an MME 121, an S-GW 122, a packet data network (PDN) gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MME 121 may functionally be similar to the control plane of a traditional serving general packet radio service (GPRS) support node (SGSN). The MME 121 may manage mobility aspects in access, such as gateway selection and tracking area list management. The HSS 124 may include a database for network users, which includes subscription-related information for supporting network entities to process communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN120 may include one or several HSSs 124. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, etc.

[0027] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0028] The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the EPC network 120 and an external network such as a network including an application server 184 (alternatively referred to as an Application Function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 may also deliver data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IMS) network, and other networks. Generally, the application server 184 may be an element that provides an application that uses IP bearer resources together with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this regard, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Internet Protocol Voice (VoIP) session, Push-to-Talk (PTT) session, group communication session, social network service, etc.) for the UEs 101 and 102 via the CN 120.

[0029] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF associated with the Internet Protocol Connectivity Access Network (IP-CAN) session of a UE in a Home Public Land Mobile Network (HPLMN). In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of a UE: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0030] In some aspects, the communication network 140A may be an IoT network or a 5G network, including a 5G New Radio network that uses both licensed (5G NR) spectrum and unlicensed (5G NR-U) spectrum for communication. One of the current enablers of IoT is Narrowband IoT (NB-IoT).

[0031] The NG system architecture may include a Radio Access Network (RAN) 110 and a 5G Network Core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., 5G core network or 5GC) may include an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The AMF and UPF may be communicatively coupled to the gNBs and NG-eNBs via the NG interface. More specifically, in some aspects, the gNBs and NG-eNBs may be connected to the AMF via the NG-C interface and to the UPF via the NG-U interface. The gNBs and NG-eNBs may be coupled to each other via the Xn interface.

[0032] In some aspects, the NG system architecture may use reference points between the various nodes as provided in 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, December 2018). In some aspects, each of the gNBs and NG-eNBs may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some aspects, in the 5G architecture, the gNB may be the Master Node (MN) and the NG-eNB may be the Secondary Node (SN).

[0033] Figure 1B A non-roaming 5G system architecture according to some aspects is shown. Refer to Figure 1B , which shows the 5G system architecture 140B in a reference point representation. More specifically, the User Equipment (UE) 102 may communicate with the RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes multiple Network Functions (NFs), such as an Access and Mobility Management Function (AMF) 132, a Session Management Function (SMF) 136, a Policy Control Function (PCF) 148, an Application Function (AF) 150, a User Plane Function (UPF) 134, a Network Slice Selection Function (NSSF) 142, an Authentication Server Function (AUSF) 144, and a Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 may provide a connection to a Data Network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. The AMF 132 may be used to manage access control and mobility and may also include a network slice selection function. The SMF 136 may be configured to set up and manage various sessions according to network policies. The UPF 134 may be deployed according to one or more configurations based on the desired service type. The PCF 148 may be configured to provide a policy framework using network slices, mobility management, and roaming (similar to the PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to the HSS in a 4G communication system).

[0034] In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and multiple IP Multimedia Core Network Subsystem entities, such as Call Session Control Function (CSCF). More specifically, IMS 168B includes a CSCF, which can act as a Proxy CSCF (P-CSCF) 162BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) ( Figure 1B not shown in Figure 1B ) or an Interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured as the first point of contact for the UE 102 within the IP Multimedia Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session state in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B can be configured to act as a point of contact within the carrier network for all IMS connections to subscribers of that network operator or roaming subscribers currently located within the service area of that network operator. In some aspects, the I-CSCF 166B can be connected to another IP Multimedia Network 170E, such as an IMS operated by a different network operator.

[0035] In some aspects, the UDM / HSS 146 can be coupled to an Application Server 160E, which can include a Telephony Application Server (TAS) or another Application Server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0036] Reference points indicate that interactions can exist between the corresponding NF services. For example, Figure 1BThe following reference points are shown: N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SAIF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (if in a non-roaming scenario, between PCF 148 and AMF 132; if in a roaming scenario, between PCF 148 and the visited network and AMF 132, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference points not shown in Figure 1B may also be represented using

[0037] Figure 1C A 5G system architecture 140C and a service-based representation are shown. In addition to Figure 1B the network entities shown in

[0038] In some aspects, such as Figure 1CAs shown, service-based representations can be used to represent network functions within a control plane that enables other authorized network functions to access its services. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (service-based interface exposed by AMF 132), Nsmf 158I (service-based interface exposed by SMF 136), Nnef 158B (service-based interface exposed by NEF 154), Npcf 158D (service-based interface exposed by PCF 148), Nudm 158E (service-based interface exposed by UDM 146), Naf158F (service-based interface exposed by AF 150), Nnrf 158C (service-based interface exposed by NRF 156), Nnssf 158 A (service-based interface exposed by NSSF 142), Nausf 158G (service-based interface exposed by AUSF 144). Other service-based interfaces not shown in Figure 1C (e.g., Nudr, N5g-eir, and Nudsf) may also be used.

[0039] The techniques discussed herein may be performed by a UE or a base station (e.g., in conjunction with Figure 1A to Figure 1C either of the UEs or base stations shown).

[0040] The Rel-15 NR system is designed to operate on licensed spectrum. NR-U is a technology that enables the NR system to operate on unlicensed spectrum.

[0041] A UE requires a scheduling request (SR) in the connected mode or in the NR-U standalone mode and in an LTE-NR-U deployment scenario. Transmitting an SR on the PUCCH may be subject to certain listen-before-talk (LBT) requirements in the unlicensed spectrum. The techniques discussed herein can be used to mitigate the impact of LBT.

[0042] SR counters and timers.

[0043] In some aspects, RRC signaling can be used to configure the SR timer, SR counters, and the threshold of the SR counter (e.g., the sr-TransMax threshold). In addition, the RRC signaling can also configure a separate LBT timer (or LBT success timer) and an LBT failure counter (and the associated LBT failure counter threshold). The LBT timer can be started after the LBT process is initiated. If the UE does not detect an available spectrum / channel before the LBT timer expires, the LBT failure counter is incremented. If the LBT failure counter threshold is reached, a connection reconstruction or another reconfiguration process can be initiated. Otherwise, a new LBT timer can be started after a new LBT process is initiated.

[0044] When a usable NR-U spectrum is successfully detected, the SR timer can be started when the SR is transmitted to the base station. If a response (e.g., the first uplink grant) is not received before the SR timer expires, the SR counter is incremented. If the SR counter threshold is reached, the UE can perform connection reconstruction or another reconfiguration procedure. If the UE receives the first uplink grant before the SR timer expires, the UE can transmit a buffer status report (BSR) to the base station and receive a second uplink grant in response to the BSR. Then, the UE can use the second uplink grant to transmit the data reflected in the BSR to the base station.

[0045] In some aspects, when no separate LBT timer and separate LBT counter are configured, the UE can increase the timer duration of the SR timer and the SR counter threshold to account for possible SR transmission delays due to LBT failures.

[0046] In some aspects, SR transmission is subject to LBT (e.g., in an NR-U communication network). In this case, if the SR transmission is not performed due to LBT during the SR transmission occasion configured for the pending SR, starting the SR timer (e.g., sr-ProhibitTimer) can prevent the MAC entity of the UE from signaling the physical layer to perform an SR transmission. Thus, in some aspects, the physical layer can indicate LBT success during the SR transmission occasion to initiate the start of the prohibit timer.

[0047] In aspects where the previous SR transmission was unsuccessful due to LBT (i.e., there was no physical layer indication on the previous SR transmission occasion), the UE can determine whether to increment the SR_COUNTER for subsequent SR transmission occasions configured for the SR.

[0048] The purpose of the SR counter (e.g., SR_COUNTER) is to give the maximum number of attempts that the UE can make for SR transmission to avoid the UE getting stuck in the request state due to poor RF conditions. An LBT failure can be considered as another factor of poor RF conditions (i.e., when the channel load is very high). In this regard, the SR_COUNTER can be incremented. To account for LBT failures, the sr-TransMax counter threshold can be appropriately configured to provide a time-domain solution to overcome LBT via RRC signaling / default configuration or to dynamically set LBT based on the channel load (e.g., RSSI or channel occupancy, presence of DL transmission, etc.). For RSSI or channel occupancy, if such values are higher than a certain fixed or configurable threshold at the start of the SR process, the sr-TransMax threshold can be used for that RSSI or channel occupancy. In this regard, there are sr-TransMax for different RSSI or channel occupancies.

[0049] In terms of the aspect when the counter is not incremented, if the channel remains busy during the SR transmission occasion, the MAC entity may stay in this state for an extremely long time. This process can be acceptable when the load on the channel is light.

[0050] In some aspects, separate LBT success timers and LBT counters (for each SR configuration) can be used to count the number of SR transmission failures caused by LBT. In this case, the existing SR_COUNTER can continue to be associated with SR transmission failures due to RF conditions other than LBT failures, while the new separate LBT failure counter counts the number of LBT failures associated with SR transmission. Once the separate LBT failure counter reaches a fixed or configurable maximum value, it can report it to the network via an RRC or MAC signaling message (for DC or CA cases) or perform RRC connection reconstruction.

[0051] Figure 2 A swimlane diagram of a communication exchange 200 between a user equipment (UE) 202 and a base station 204 using scheduling request enhancement techniques is shown. See Figure 2, and in the initial configuration phase, UE 202 can start the LBT success timer at operation 206. While this timer is running, at operation 208, UE 202 can perform the LBT process and can detect available NR-U spectrum before the LBT success timer expires. When available spectrum is detected, UE 202 can start the SR prohibition timer at operation 210. While the SR prohibition timer is running, UE 202 transmits the SR to base station 204 at operation 212. In response, at operation 214, base station 204 transmits a first uplink grant for communication of the BSR. At operation 216, the SR prohibition timer expires.

[0052] Optionally, after the SR prohibition timer expires, the first uplink grant can be received via operation 218, and the SR can be retransmitted at operation 222.

[0053] At operation 224, UE 202 transmits the BSR based on the first uplink grant received from base station 204. At operation 226, in response to the BSR, base station 204 transmits a second uplink grant. At operation 228, UE 202 transmits data on the PUSCH based on the second uplink grant.

[0054] Increase the SR transmission opportunity.

[0055] In some aspects, the SR configuration can include a set of PUCCH resources for SR across different bandwidth parts (BWPs) and / or cells. The PUCCH resources associated with the SR configuration can overlap in time across different BWPs and serving cells.

[0056] In some aspects, to increase the SR transmission opportunity, the MAC can pass to the physical layer across different serving cells associated with the SR configuration on multiple SR PUCCH resources, thereby allowing the physical layer to attempt SR transmission on the first PUCCH resource that passes the LBT (across different serving cells). If multiple active BWPs may be used for NR-U communication, the PUCCH resources across different active BWPs can also be used to increase the SR transmission opportunity. Thus, the UE MAC entity can provide PUCCH resources to the physical layer across different serving cells of the SR configuration. If multiple active BWPs may be used for NR-U communication, it may also be beneficial for the UE MAC entity to provide the PUCCH resources across different active BWPs of the SR configuration to the physical layer.

[0057] Scheduling request and configured grant.

[0058] In some aspects, a configured grant may be configured for and active for a UE, and a BSR may be transmitted via the configured grant without first transmitting an SR. In such a case, it is necessary to ensure that a BSR triggered only by a logical channel of an unlicensed serving cell configured to use a grant with enhanced configuration for an unlicensed carrier will not trigger an SR (this is to reduce possible conflicts between the configured grant and the scheduled grant). If all logical channels triggering the BSR have a logical channel restriction that restricts the use of a grant with enhanced configuration for an unlicensed carrier for an unlicensed serving cell, the SR may not be triggered.

[0059] In some aspects, when transmissions are subject to LBT, the techniques disclosed herein may be used to manage counters and timers in scheduling requests. In some aspects, scheduling request transmission opportunities may be increased based on LBT. In some aspects, a scheduling request may be bypassed when a configured grant is available. The start of the sr - ProhibitTimer may be subject to an indication of successful completion of LBT. Regardless of the result of LBT, the counter SR_COUNTER may be incremented. In some aspects, the SR_COUNTER threshold may be configured based on network load or RF conditions. In some aspects, a separate counter is used to count the number of LBT failures. In some aspects, the separate LBT counter may be configured via signaling from the base station. In some aspects, when the LBT counter reaches a configurable threshold, the counter value is reported to the gNB. In some aspects, when the LBT counter reaches a configurable threshold, the UE undergoes RRC connection reconstruction. In some aspects, when LBT passes, the counter SR_COUNTER is incremented. In some aspects, multiple PUCCH resources may be configured for each SR. In some aspects, the PUCCH resources may be in different frequency domains. In some aspects, different frequency domains may include different BWPs, sub - bands, or serving cells. In some aspects, a scheduling request may be skipped if the logical channel configuration allows. In some aspects, a configuration field (e.g., in control signaling) may be used to indicate a skipped SR.

[0060] Figure 3 A block diagram of a communication device for performing one or more of the techniques disclosed herein is shown, such as an evolved Node - B (eNB), a next - generation Node - B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE). In an alternative aspect, the communication device 300 may operate as a stand - alone device or may be connected (e.g., networked) to other communication devices.

[0061] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of device 300, the tangible entity including hardware (e.g., simple circuits, gates, logic components, etc.). Circuit component relationships can vary flexibly over time. The circuit includes components that can perform specified operations (individually or in combination) during operation. In one example, the hardware of the circuit can be invariantly designed to perform a specific operation (e.g., hardwired). In one example, the hardware of the circuit can include physically modifiable (e.g., magnetically, electrically, removably placed immobile particles, etc.) machine-readable media of physically variable-connected components (e.g., execution units, transistors, simple circuits, etc.) to encode instructions for a specific operation.

[0062] When connecting physical components, the basic electrical properties of the hardware components change, e.g., from insulator to conductor and vice versa. The instruction enables the embedded hardware (e.g., execution unit or loading mechanism) to create circuit components in the hardware via variable connections to perform parts of a specific operation during operation. Thus, in one example, the machine-readable media element is part of the circuit or communicatively coupled to other components of the circuit when the device is operating. For example, any one of these physical components can be used in more than one component of more than one circuit. For example, under operation, an execution unit can be used for a first circuit in a first circuit system at one point in time and reused by a second circuit in the first circuit system or by a third circuit in a second circuit system at different times. The following are additional examples of these components with respect to device 300.

[0063] In some aspects, device 300 can operate as a stand-alone device or be connected (e.g., networked) to other devices. In a networked deployment, communication device 300 can operate as a server communication device, a client communication device, or both in a server-client network environment. In one example, communication device 300 can act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. Communication device 300 can be a UE, eNB, PC, tablet, STB, PDA, mobile phone, smart phone, web device, network router, switch, or bridge, or any communication device capable of (sequentially or otherwise) executing instructions that specify actions to be taken by the communication device. Additionally, although only one communication device is shown, the term "communication device" should also be considered to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein (such as cloud computing software as a service (SaaS)) and other computer cluster configurations.

[0064] Examples as described herein may include a logic component or components, modules, or mechanisms, or may operate on a logic component or components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing specified operations and configured or arranged in some manner. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or relative to external entities such as other circuits). In one example, all or part of one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) to operate as a module that performs specified operations. For example, software may reside on a communication device-readable medium. In one example, when executed by the underlying hardware of a module, the software causes the hardware to perform the specified operations.

[0065] Accordingly, the term “module” should be understood to encompass a tangible entity, i.e., a physical construction, a specific configuration (e.g., hardwired), or a temporarily (e.g., transiently) configured entity (e.g., programmed) that operates or performs part or all of any of the operations described herein in a specified manner. Considering an example where a module is temporarily configured, each module need not be instantiated at any given moment. For example, if a module includes a general hardware processor configured with software, the general hardware processor may be configured as a respective different module at different times. The software may configure the hardware processor accordingly, e.g., to constitute a particular module at one instance of time and a different module at a different instance of time.

[0066] A communication device (e.g., UE) 300 may include a hardware processor 302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 304, a static memory 306, and a mass storage device 307 (e.g., a hard disk drive, a tape drive, a flash storage device, other block or storage devices), some or all of which may communicate with each other via an interconnect link (e.g., a bus) 308.

[0067] The communication device 300 may further include a display device 310, an alphanumeric input device 312 (e.g., a keyboard), and a user interface (UI) navigation device 314 (e.g., a mouse). In one example, the display device 310, the input device 312, and the UI navigation device 314 may be a touch screen display. The communication device 300 may additionally include a signal generation device 318 (e.g., a speaker), a network interface device 320, and one or more sensors 321, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 300 may include an output controller 328, such as a serial (e.g., universal serial bus (USB)) connection, a parallel connection, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0068] The storage device 307 may include a communication device-readable medium 322 on which is stored one or more sets of data structures or instructions 324 (e.g., software) embodied or utilized by any of the techniques or functions described herein. In some aspects, the registers of the processor 302, the main memory 304, the static memory 306, and / or the mass storage device 307 may (wholly or at least partially) be or include a device-readable medium 322 on which is stored one or more sets of data structures or instructions 324 embodied or utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of the hardware processor 302, the main memory 304, the static memory 306, or the mass storage device 316 constitutes the device-readable medium 322.

[0069] As used herein, the term "device-readable medium" may be interchangeable with "computer-readable medium" or "machine-readable medium". Although the communication device-readable medium 322 is shown as a single medium, the term "communication device-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 324. The term "communication device-readable medium" includes the term "machine-readable medium" or "computer-readable medium", and may include any medium that can store, encode, or carry instructions (e.g., instructions 324) for execution by the communication device 300, and cause the communication device 300 to perform any one or more of the techniques of the present disclosure, or any medium that can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of communication device-readable media may include solid state memories, and optical and magnetic media. Specific examples of communication device-readable media may include: non-volatile memories such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device-readable medium may include a non-transitory communication device-readable medium. In some examples, the communication device-readable medium may include a communication device-readable medium that is not a transitory propagated signal.

[0070] The instructions 324 may also be transmitted or received over a communication network 326 using a transmission medium via the network interface device 320, using any one of a plurality of transmission protocols. In one example, the network interface device 320 may include one or more physical jacks (e.g., Ethernet, coaxial cable, or phone jacks) or one or more antennas to connect to the communication network 326. In one example, the network interface device 320 may include multiple antennas to perform wireless communication using at least one of single input multiple output (SIMO) technology, MIMO technology, or multiple input single output (MISO) technology. In some examples, the network interface device 320 may perform wireless communication using multi-user MIMO technology.

[0071] The term "transmission medium" shall be considered to include any intangible medium that can store, encode, or carry instructions for execution by the communication device 300, and includes digital or analog communication signals or another intangible medium to facilitate the communication of such software. In this regard, in the context of the present disclosure, the transmission medium is a device-readable medium.

[0072] While one aspect has been described with reference to specific exemplary aspects, it will be apparent that various modifications and changes can be made to these aspects without departing from the broader scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. Thus, this detailed description is not limiting in sense, and the scope of the aspects is defined only by the full scope of the appended claims and equivalents of such claims that are entitled.

Claims

1. A device, comprising: At least one processor, wherein in order to configure a user equipment UE for transmitting data in a new radio-unlicensed (NR-U) spectrum, the at least one processor is configured to cause the UE: When a configured grant is active for the UE, in response to a scheduling request SR triggered by a buffer status report BSR, indicate that the physical layer performs an SR transmission to a base station on physical uplink control channel PUCCH resources that overlap in time across different bandwidth parts; In a case where an SR transmission is unsuccessful due to a listen-before-talk LBT failure, increment an LBT failure counter without incrementing an SR counter and without starting an SR prohibition timer; In a case where LBT for the SR transmission is successful, increment the SR counter and start the SR prohibition timer.

2. The device according to claim 1, wherein an LBT failure is determined based on the absence of a physical layer indication.

3. The device according to claim 1, wherein the at least one processor is further configured to: Perform RRC connection reconstruction when the LBT failure counter reaches a configured threshold.

4. The device according to claim 1, wherein the at least one processor is further configured to: Report to the network via MAC or radio resource control RRC signaling when the LBT failure counter reaches a configured threshold.

5. The device according to claim 1, wherein the PUCCH resources for the SR transmission are provided by an SR configuration, and wherein the BSR is triggered at least by a logical channel that is not configured to use an unlicensed serving cell with the configured grant.

6. The device according to claim 1, wherein the at least one processor is further configured to: Increment the SR counter and start the SR prohibition timer when LBT is successful and the SR transmission fails.

7. A user equipment UE, comprising: Wireless communication circuitry; And At least one processor, the at least one processor being coupled to the wireless communication circuitry, wherein in order to configure a user equipment UE for transmitting data in a new radio-unlicensed (NR-U) spectrum, the at least one processor circuit is configured to cause the UE: When a configured grant is active for the UE, in response to a scheduling request SR triggered by a buffer status report BSR, indicate that the physical layer performs an SR transmission to a base station on physical uplink control channel PUCCH resources that overlap in time across different bandwidth parts; In a case where an SR transmission is unsuccessful due to a listen-before-talk LBT failure, increment an LBT failure counter without incrementing an SR counter and without starting an SR prohibition timer; In a case where LBT for the SR transmission is successful, increment the SR counter and start the SR prohibition timer.

8. The UE according to claim 7, wherein, Determine an LBT failure based on the absence of a physical layer indication.

9. The UE according to claim 7, wherein, The at least one processor is further configured to: Perform RRC connection reconstruction when the LBT failure counter reaches a configured threshold.

10. The UE according to claim 7, wherein, The at least one processor is further configured to: When the LBT failure counter reaches a configured threshold, report to the network via MAC or radio resource control (RRC) signaling.

11. The UE according to claim 7, wherein, The PUCCH resource for SR transmission is provided by SR configuration, and wherein the BSR is triggered at least by a logical channel of an unlicensed serving cell not configured to use the license with the configuration.

12. The UE according to claim 7, wherein, The at least one processor is further configured to: When LBT is successful and SR transmission fails, increment the SR counter and start the SR prohibition timer.

13. A method for operating a user equipment (UE), the method comprising: By the UE: When the configured license is active for the UE, in response to a scheduling request (SR) triggered by a buffer status report (BSR), instruct the physical layer to perform an SR transmission to the base station on a physical uplink control channel (PUCCH) resource that overlaps in time across different bandwidth parts; In the case where the SR transmission is unsuccessful due to a listen-before-talk (LBT) failure, increment the LBT failure counter without incrementing the SR counter and without starting the SR prohibition timer; In the case where LBT for SR transmission is successful, increment the SR counter and start the SR prohibition timer.

14. The method according to claim 13, further comprising: When the LBT failure counter reaches a configured threshold, perform RRC connection reconstruction.

15. The method according to claim 13, wherein, The PUCCH resource for SR transmission is provided by SR configuration, and wherein the BSR is triggered at least by a logical channel of an unlicensed serving cell not configured to use the license with the configuration.

16. The method according to claim 13, further comprising: When LBT is successful and SR transmission fails, increment the SR counter and start the SR prohibition timer.

17. The method according to claim 13, wherein LBT failure is determined based on the absence of a physical layer indication.

18. The method according to claim 13, further comprising: When the LBT failure counter reaches a configured threshold, report to the network via MAC or radio resource control (RRC) signaling.

19. A non-transitory computer-readable storage medium storing instructions that can be executed by a processor to cause a user equipment (UE) to implement the operations of the method according to any one of claims 13 to 18.

20. A computer program product comprising instructions that, when executed by a computer, cause the computer to perform the method according to any one of claims 13 to 18.

Images