Scheduling request transmission

Abstract

When timing information (TI) of a scheduling request (SR) and / or a buffer status report (BSR) is provided to a base station, latency of scheduling request (SR) communications, including uplink (UL) dynamic scheduling, may be improved. The TI may be transmitted to a base station along with or separately from the SR and / or the BSR. The TI indicates when the SR and / or BSR are effective, when the UE needs to transmit uplink (UL) data, or when UL traffic arrives. A base station may transmit a UL scheduling signal to a UE even before UL data is to be transmitted.

Description

Scheduling request transmission Technical Field

[0001] This document generally relates to wireless communications. More specifically, it addresses how to improve latency in scheduling request (SR) communications, including uplink (UL) dynamic scheduling. Background Technology

[0002] Wireless communication technology is propelling the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and radio access network nodes (including but not limited to radio base stations). Next-generation networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the needs of various industries and users. User mobile stations or user equipment (UE) are becoming increasingly complex, and the amount of data being communicated continues to increase. The transmission rate, latency, throughput, reliability, and other performance metrics of wireless communication systems have been improved through the use of high-frequency bands, large bandwidths, multiple antennas, and other technologies. Extended Reality (XR) and cloud gaming are media applications that require improved performance. XR includes representative forms such as Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR). These services require high reliability, high throughput, and low latency, while simultaneously needing to improve battery life to enhance the UE experience. Battery life will also impact the UE experience. Communication improvements are necessary to enhance communication, reduce UE power consumption while increasing reliability, meet the reliability requirements of vertical industries, and support next-generation network services. Summary of the Invention

[0003] This document relates to methods, systems, and apparatus for improving latency in scheduling request (SR) communications, including uplink (UL) dynamic scheduling. Timing information (TI) for scheduling requests (SR) and / or buffer state reporting (BSR) is provided to the base station. This TI may be transmitted to the base station together with or separately from the SR and / or BSR. The TI indicates when the SR and / or BSR take effect, when the UE needs to transmit uplink (UL) data, or when UL services arrive. Even before UL data is to be transmitted, the base station may send UL scheduling signals to the UE.

[0004] In one embodiment, a method for wireless communication includes: sending a scheduling request or a buffer status report (BSR); and providing timing information, wherein the timing information is either provided together with the scheduling request or the timing information itself can imply the scheduling request.

[0005] In one embodiment, a method for wireless communication includes sending an uplink scheduling signal to a user equipment (UE) in the absence of uplink data to be transmitted.

[0006] In one embodiment, a method for wireless communication includes receiving an uplink scheduling signal at a user equipment (UE) in the absence of uplink data to be transmitted.

[0007] In one embodiment, a method for wireless communication includes: receiving a user equipment (UE) capability indicating timing information; and determining timing information for a scheduling request from the UE capability.

[0008] In one embodiment, a method for wireless communication includes: transmitting timing information that can imply a scheduling request.

[0009] In one embodiment, a method for wireless communication includes: receiving a scheduling request or a buffer status report (BSR); and receiving timing information.

[0010] In one embodiment, a method for wireless communication includes: receiving timing information; and implying a scheduling request based on the timing information.

[0011] In one embodiment, a method for wireless communication includes transmitting a user equipment (UE) capability, wherein timing information is determined from the UE capability in response to a scheduling request.

[0012] In one embodiment, a computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the embodiments discussed above.

[0013] In some embodiments, a wireless communication device includes a processor and a memory, wherein the processor is configured to read code from the memory and implement any of the methods described in any embodiment. In some embodiments, a computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the methods described in any embodiment. The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0014] Figure 1 shows an example base station.

[0015] Figure 2 illustrates an example random access (RA) messaging environment.

[0016] Figure 3 illustrates an embodiment of a wireless network system architecture.

[0017] Figure 4 illustrates an example of scheduling request (SR) communication.

[0018] Figure 5 illustrates an example of scheduling request (SR) timing.

[0019] Figure 6 illustrates another embodiment of scheduling request (SR) timing.

[0020] Figure 7 illustrates an example of communication combining a scheduling request (SR) timing with timing information (TI).

[0021] Figure 8 illustrates an example of communication between a scheduling request (SR) timing, timing information (TI), and a buffer status report (BSR).

[0022] Figure 9 illustrates another embodiment of communication combining timing information (TI) and buffer status report (BSR) for scheduling requests (SR) using different frequency domain resources. Detailed Implementation

[0023] This disclosure will now be described in detail with reference to the accompanying drawings, which form a part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be implemented in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0024] Throughout the specification and claims, terms may have suggestive or implied meanings in the context, in addition to their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, exemplary embodiments or combinations of embodiments.

[0025] Generally, terms can be understood at least in part from their use in context. For example, terms used herein, such as “and,” “or,” or “and / or,” can include a variety of meanings, which can depend at least in part on the context in which these terms are used. Typically, “or,” when used in an associative list, such as A, B, or C, means A, B, and C in an inclusive sense, and A, B, or C in an exclusive sense. Furthermore, the terms “one or more” or “at least one,” as used herein, can be used, at least in part on context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can also be understood to convey either a singular or a plural usage, at least in part on context. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather to allow for the existence of additional factors that are not necessarily explicitly described, which, too, depends at least in part on the context.

[0026] The wireless communication described herein can be performed via radio access including new radio (NR) access. Radio resource control (RRC) is a protocol layer at the IP level (network layer) between the user equipment (UE) and the network (e.g., a base station or gNB). Various RRC states can exist, such as RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE. As mentioned above, the UE can transmit data via a Random Access Channel (RACH) protocol scheme or a Configuration Grant (CG) scheme or grant scheme. Figures 1 and 2 illustrate an example radio access network (RAN) node (e.g., a base station) and the user equipment and messaging environment.

[0027] If the User Equipment (UE) has uplink (UL) data to be transmitted, the UE will transmit a Scheduling Request (SR) or Buffer Status Report (BSR) to the base station, and the base station can send an uplink (UL) grant to the UE by allocating Physical Uplink Shared Channel (PUSCH) resources. The SR indication can indicate whether the UE has UL data to be transmitted. In one embodiment, '1' indicates that there is data to be transmitted. If the UE does not have available PUSCH resources, it can use the Physical Uplink Control Channel (PUCCH) to send the SR.

[0028] The Information Element (IE) `SchedulingRequestResourceConfig` determines the physical layer resources on the PUCCH, and the UE can send a dedicated scheduling request (D-SR). The `SchedulingRequestResourceConfig` IE includes `schedulingRequestResourceId` (i.e., the ID of the SR resource), `schedulingRequestID` (i.e., the ID of the associated SR), and `periodicityAndOffset` (i.e., the period and offset of the SR resource that determine the timing of transmission). An SR configuration has dedicated SR resources. A BSR can indicate the buffer size of UL data. SRs can be transmitted on the PUCCH, while BSRs can be transmitted on the Physical Uplink Shared Channel (PUSCH). The Configured Grant (CG) configuration includes resources for the PUSCH. If the UE has UL data to be transmitted, the UE can send an SR during the SR transmission timing to indicate the presence of UL data to be transmitted. If there are available uplink scheduling (UL-SCH) resources to indicate the buffer size of UL data, the UE can send a BSR.

[0029] Figure 1 illustrates an example base station 102. This base station may also be referred to as a network device or a wireless network node. Base station 102 may also be identified as a nodeB (NB, e.g., eNB or gNB) in a mobile telecommunications context. The example base station may include a wireless Tx / Rx circuit 113 for receiving and transmitting with a user equipment (UE) 104. The base station may also include a network interface circuit 116 that couples the base station to the core network 110, such as an optical interconnect or wired interconnect, Ethernet, and / or other data transmission media / protocols.

[0030] The base station may also include system circuitry 122. System circuitry 122 may include one or more processors 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130. Operations 128 may include instructions for execution on one or more processors in processor 124 to support base station operation. For example, operations may process random access transmission requests from multiple UEs. Control parameters 130 may include parameters or may support the execution of operations 128. For example, control parameters may include network protocol settings, random access messaging format rules, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0031] For at least some specifications (e.g., 5G New Radio (NR)), data and control signals are transmitted and / or carried on physical channels. Typically, a physical channel corresponds to a set of time-frequency resources used for signal transmission. Different types of physical channels can be used to transmit different types of signals. For example, a physical data channel (or simply data channel), also referred to herein as a traffic channel, is used to transmit data signals; while a physical control channel (or simply control channel) is used to transmit control signals. Example types of traffic channels (or physical data channels) include, but are not limited to: a physical downlink shared channel (PDSCH) for transmitting downlink data signals, a physical uplink shared channel (PUSCH) for transmitting uplink data signals, and a physical sidelink shared channel (PSSCH) for transmitting sidelink data signals. Furthermore, example types of physical control channels include, but are not limited to, physical downlink control channels (PDCCH) for transmitting downlink control signals, physical uplink control channels (PUCCH) for transmitting uplink control signals, and physical sidelink control channels (PSCCH) for transmitting sidelink control signals. As used herein, for simplicity, unless otherwise stated, a specific type of physical channel is also used to refer to the signals transmitted on that specific type of physical channel, and / or the transmission on that specific type of transmission. By way of example, PDSCH refers to the physical downlink shared channel itself, downlink data signals transmitted on the PDSCH, or downlink data transmission. Therefore, a communication node sending or receiving a PDSCH means that the communication node is sending or receiving signals on the PDSCH.

[0032] Additionally, for at least some specifications such as 5G NR and / or for at least some types of control signals, the control signals transmitted by the communication nodes may include control information that includes information necessary to enable the transmission of one or more data signals and / or the scheduling of one or more data channels (or one or more transmissions on data channels) between the communication nodes. For example, such control information may include: information necessary to correctly receive, decode, and demodulate data signals received on physical data channels during data transmission; and / or information necessary to uplink scheduling authorization, which informs the user equipment of the resources and transmission formats used for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted from base station 102 to UE 104 in the downlink direction. In other embodiments, the control information includes uplink control information (UCI) or sidelink control information (SCI), wherein the uplink control information is transmitted from UE 104 to base station 102 in the uplink direction, and the sidelink control information is sent from one UE 104 to another UE 104 in the sidelink direction.

[0033] Furthermore, in some embodiments, UE 104 can be configured to support at least one simultaneous UL transmission mode for cross-band pairs of UL transmissions. In a first simultaneous UL transmission mode (also known as switchedUL mode), UE 104 does not support simultaneous UL transmission across band pairs. Accordingly, when UE 104 transmits UL transmissions in the first simultaneous UL transmission mode, UE 104 transmits the UL transmission without performing simultaneous transmission across band pairs. Furthermore, in a second simultaneous UL transmission mode (also known as dualUL mode), UE 104 supports simultaneous UL transmission across band pairs. Accordingly, when UE 104 transmits UL transmissions in the second simultaneous UL transmission mode, UE 104 transmits the UL transmission using simultaneous transmission across band pairs.

[0034] Figure 2 illustrates an example random access messaging environment 200. In this environment, UE 104 can communicate with base station 102 via random access channel 252. In this example, UE 104 supports one or more Subscriber Identity Modules (SIMs), such as SIM1 202. An electrical and physical interface (also known as a SIM card 1 interface) 206 connects SIM1 202 to the rest of the user equipment hardware, for example, via system bus 210.

[0035] Mobile device 200 includes a communication interface 212, system logic (also referred to as system circuitry) 214, and a user interface 218. System logic 214 may include any combination of hardware, software, firmware, or other logic. System logic 214 may be implemented, for example, using one or more systems-on-a-chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System logic 214 is part of an implementation of any desired functionality in UE 104. In this regard, system logic 214 may include logic that facilitates operations such as: decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (e.g., for internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 218. User interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of input 228 include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of input.

[0036] System logic 214 may include one or more processors 216 and memory 220. Memory 220 stores, for example, control instructions 222 executed by processor 216 to achieve the desired functions of UE 104. Control parameters 224 provide and specify operational options and configurations for the control instructions 222. Memory 220 may also store any BT, WiFi, 3G, 4G, 5G, or other data 226 that UE 104 will send or has received via communication interface 212. In various embodiments, system power may be provided by a power storage device such as battery 282.

[0037] In communication interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 230 processes the transmission and reception of signals via one or more antennas 232. Communication interface 212 may include one or more transceivers. The transceiver may be a wireless transceiver, which includes modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaper, an analog-to-digital converter (ADC), filters, waveform shapers, pre-amplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium.

[0038] Transmitted and received signals can follow any of a wide variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 212 may include transceivers supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the technologies described below, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies, are applicable to other wireless communication technologies.

[0039] Multiple RAN nodes (eNB, gNB) using the same or different radio access technologies (RATs) can be deployed on the same or different frequency carriers within a specific geographical area. These nodes can interoperate with each other via dual connectivity to provide joint communication services to the same (one or more) target UEs. A multi-RAT dual connectivity (MR-DC) architecture can have non-co-located master nodes (MNs) and secondary nodes (SNs). Access Mobility Functions (AMFs) and Session Management Functions (SMFs) can be control plane entities, while User Plane Functions (UPFs) are user plane entities in the New Radio (NR) or 5GC.

[0040] The Media Access Control (MAC) entity can be configured with zero or more Schedule Request (SR) configurations (e.g., IESchedulingRequestConfig). An SR configuration can include a set of Physical Uplink Control Channel (PUCCH) resources for SRs across bandwidth parts (BWPs) and cells. The embodiments described below include variations for timing improvements to the Schedule Request (SR). The SR can be transmitted from a User Equipment (UE) to a base station and can include Timing Information (TI) for timing UL data / signals. Figures 4 through 9 illustrate examples of SR timing communication.

[0041] Figure 3 illustrates one embodiment of a wireless network system architecture. This architecture is merely an example, and more or fewer components may be present to implement some of the embodiments described herein. Interconnections or communications between components are identified as N1, N2, N4, N6, N7, N8, N10, and N11, and these identifiers may be referenced in the specification or other figures. Figure 2 illustrates an example user equipment (UE) 104. UE 302 is a device that accesses a wireless network (e.g., 5GS) and obtains services via an NG-RAN node or base station 304. UE 302 interacts with the access and mobility control function (AMF) 306 of the core network via NAS (Non-Access Stratum) signaling. Figure 1 illustrates an example base station or NG-RAN 102. Base station 304 may also be referred to as a next-generation radio access network (NG-RAN) node and may communicate with the user equipment (UE) for timing of SR.

[0042] AMF 306 includes the following functions: registration management, connection management, reachability management, and mobility management. AMF 306 also performs access authentication and access authorization. AMF 306 is the NAS secure termination point and relays session management NAS between UE 302 and SMF 308. SMF 308 includes the following functions: session management (e.g., session establishment, modification, and release), UE IP address allocation and management (including optional authentication), uplink function selection and control, downlink data notification, etc. User plane functions (UPF) 310 include the following functions: intra-RAT / inter-RAT mobility anchoring, packet routing and forwarding, traffic usage reporting, user plane QoS (Quality of Service) processing, downlink packet buffering, and downlink data notification triggering, etc. Unified Data Management (UDM) 312 manages the UE's subscription profile. This subscription includes data for mobility management (e.g., restricted areas) and session management (e.g., QoS profiles). The subscription data also includes slice selection parameters used by AMF 306 to select the appropriate SMF 308. AMF 306 and SMF 308 obtain subscriptions from UDM 312. The subscription data can be stored in a unified data repository and works in conjunction with UDM 312, which uses this data when receiving requests from AMF 306 or SMF 308. The Policy Control Function (PCF) 314 includes the following functions: supporting a unified policy framework to manage network behavior, providing policy rules to control plane(s) to enforce those rules, and implementing a front-end to access subscription information related to policy decisions in the user data repository. The Network Exposure Function (NEF) 316 is optionally deployed for exchanging information with external third parties. In one embodiment, the Application Function (AF) 316 can store application information in the unified data repository via the NEF. UPF 310 communicates with the data network 318.

[0043] Figure 4 illustrates an embodiment of a scheduling request (SR) communication. This embodiment illustrates a simplified communication process for scheduling request (SR) communication. Future networks may have more stringent latency requirements. Uplink (UL) latency may be affected by scheduling request (SR) or buffer status report (BSR) transmissions, which are used to indicate to the base station in box 402 that the UE has UL data to be scheduled. Upon receiving the SR and / or BSR, the base station sends scheduling signaling to the UE in box 404 to allocate resources and indicates other information to the UE for the upcoming corresponding uplink transmission in box 406. This process can be referred to as dynamic licensed scheduling, which allows UL transmissions to adapt to channel conditions and have higher resource efficiency. To avoid latency caused by SR and / or BSR transmissions, unlicensed scheduling may exist, which indicates periodic resources and other information related to UL transmissions in advance. When uplink traffic arrives, the UE does not need to send SR and / or BSR to the base station and can use pre-allocated resources to transmit UL data. While unlicensed scheduling reduces latency caused by SR and / or BSR, it may reduce the adaptability of UL transmissions and worsen resource utilization efficiency because the pre-allocated resources are dedicated to the user equipment.

[0044] Artificial intelligence (AI), or machine learning, is considered an inherent capability of future networks (e.g., 6G), enabling the use of UE capabilities for service prediction or estimation. In the embodiments described herein, such service prediction or estimation can be used to reduce UL latency in dynamically scheduled applications. This may include the UE predicting when the UL will arrive. These embodiments can reduce uplink dynamic scheduling latency.

[0045] Figure 5 illustrates an embodiment of the scheduling request (SR) timing. The scheduling request (SR) and timing information (TI) are transmitted by the UE at time slot 0 using different frequency resources. Uplink data will arrive at t0. Since the granularity of the TI indication is one time slot, when n is time slot 0, the TI should be 4 (i.e., uplink data will arrive at n+4). The base station may not know the exact data arrival time within time slot 4, so it can send a scheduling grant at t1 within time slot 4 to schedule PUSCH transmission at the start of time slot 5. There may be a delay between t1 and the start of PUSCH, which is used for scheduling grant signaling processing. The UE can only send the TI to the base station, which also implies the SR. In this embodiment, the SR is sent by the UE along with the timing information. In other embodiments, the TI is sent without the SR.

[0046] Figure 6 illustrates another embodiment of the scheduling request (SR) timing. The base station can also send a scheduling authorization signaling before time slot 4 (e.g., within time slot 2 as shown in Figure 6) to schedule PUSCH transmission at the start of time slot 5. Therefore, when data arrives at t0 in time slot 4, the UE can transmit data in time slot 5 using the scheduled PUSCH. The SR can also be a buffer status report (BSR), which reports the UE's buffer status. For a BSR, simply transmitting TI may not be sufficient, as it may not have enough resources to convey the UE's complete buffer status information.

[0047] Figure 7 illustrates an embodiment of communication combining a scheduling request (SR) timing with timing information (TI). The timing information (TI) can include multiple time points. Each time point can correspond to an SR and / or a BSR. The TI can be transmitted together with an SR and / or a BSR, or the TI can be transmitted separately. As shown in Figure 7, the TI is sent by the UE at time slot 0, which includes two time points. Uplink (UL) data will arrive at t0 in time slot 4 and t1 in time slot 7. Since the granularity of the TI indication is one time slot, the indications in the TI are 4 and 7 (i.e., the two uplink data will arrive at n+4 and n+7 respectively), where n is time slot 0. The base station sends a scheduling authorization signaling 1 at t2 to schedule PUSCH1 for uplink data 1 transmission, and a scheduling authorization signaling 2 at t3 to schedule PUSCH2 for uplink data 2 transmission. In this embodiment, t2 can be in any time slot; this is merely an example.

[0048] In alternative embodiments, it may not be necessary to send a TI for SR and / or BSR. The base station can retrieve the TI, which is implied in the UE's capabilities. The UE reports its service prediction capabilities. For example, a capability of M=5 means that the UE can predict when a data packet will arrive M=5 time slots in advance. For example, the UE can predict at time slot n that a data packet will arrive at time slot n+5. If the UE is able to send an SR or BSR at time slot n, then the base station will know by default that the UE will have UL data to be transmitted in time slot n+5. In other words, the TI can be implicitly derived from the UE's capabilities in the transmission of the SR or BSR.

[0049] In another embodiment, the maximum value of the timing information depends on the UE's capability. Unlike implicit capability, the UE reports its service prediction capability. For example, a capability of M=6 means that the UE can predict whether a data packet will arrive up to M=6 time slots in advance. In other words, TI will be explicitly sent in this embodiment. The base station can configure the UE's timing information range, which in this example should not exceed the UE's capability (e.g., [1, 2, 3, 4]). If the UE indicates TI=2 at time slot n, this means that there will be uplink data at time slot n+2.

[0050] Figure 8 illustrates an example of communication combining a scheduling request (SR) timing with timing information (TI) and a buffer status report (BSR). The SR can replace the BSR. The UE keeps the UL scheduling signaling active until the deadline. The UE discards the previous UL scheduling signaling if it does not expect another UL scheduling signaling before the deadline, or if it receives another UL scheduling signaling before the deadline. If uplink data arrives before the deadline, the UE uses the UL link scheduling signaling to transmit the UL data.

[0051] As shown in Figure 8, the BSR and Timing Information (TI) are transmitted together by the UE using different frequency resources in time slot 0. UL data is predicted to arrive in time slot 4, therefore the TI should be 4 (i.e., uplink data is predicted to arrive at n+4), where n is time slot 0. The base station sends a scheduling grant at t1 within time slot 2 to schedule PUSCH transmission at the start of time slot 5. If the predicted uplink data does not arrive in time slot 4, the UE will not transmit the PUSCH scheduled by the base station. If UL data arrives at time point t2, the UE transmits the PUSCH at the start of time slot 6, which is the closest valid position to t2 before the PUSCH deadline. The PUSCH deadline is set to four time slots after the scheduled PUSCH position (i.e., time slot 9). If the actual UL data arrives after the PUSCH deadline, the scheduling grant is discarded.

[0052] Figure 9 illustrates another embodiment of communication combining timing information (TI) and buffer status report (BSR) for scheduling requests (SR) using different frequency domain resources. This embodiment illustrates how scheduling authorization signaling is utilized when predictions are inaccurate. The UE transmits SR / BSR and / or timing information (TI) using uplink (UL) scheduling signaling. One condition for this embodiment may be that no UL data arrives at t0, therefore no data is transmitted in time slot 5. In this example, the UE uses PUSCH1 to transmit SR and BSR.

[0053] As shown in Figure 9, the BSR and TI are transmitted together by the UE in time slot 0 using different frequency resources. UL data is predicted to arrive in time slot 4, therefore TI should be 4 (i.e., UL data is predicted to arrive at n+4), where n is time slot 0. The base station sends a scheduling authorization signaling 1 at t1 within time slot 2 to schedule PUSCH transmission at the start of time slot 5. However, if the predicted UL data does not arrive in time slot 4, the UE uses PUSCH1, scheduled by the base station, to transmit another BSR indicating that the UL data is predicted to arrive in time slot 7. The base station sends another scheduling authorization signaling 2 at t2 to schedule PUSCH2, which is used to transmit UL data arriving at t3 within time slot 7. If the UE predicts no UL data before or in time slot 5, this prediction can also be indicated in the BSR transmitted in PUSCH1.

[0054] In some embodiments, timing information (TI) for scheduling requests (SRs) and / or buffer status reports (BSRs) is provided to the base station. For example, this timing information may be transmitted to the base station along with the SR and / or BSR. In this example, only the TI is sent, or the SR and / or BSR are reported together with the TI. The TI may be transmitted using different frequency and / or code domain resources than the SR and / or BSR. The TI may include multiple time points. Each time point may correspond to one SR and / or BSR. In one example, the UE reports its capabilities to the base station, which indicate the TI of the SR and / or BSR. This TI may be provided explicitly as part of the UE's capabilities, or it may be implicitly derived from the UE's capabilities. The TI indicates when the SR and / or BSR are active, when the UE needs to transmit UL data, or when UL services arrive. The maximum value of the TI may depend on the UE's capabilities.

[0055] In some embodiments, when the UE receives a scheduling signaling or the PUSCH is scheduled by the scheduling signaling and there is no UL data to be transmitted, the base station sends a UL scheduling signaling to the UE. At this point in time, although there is no UL data to be transmitted, there will be UL data to be transmitted in the future. The UE can keep the uplink scheduling signaling valid until a deadline; before the deadline, if the UE does not expect another uplink scheduling signaling, it remains valid; or, if the UE receives another uplink scheduling signaling before the deadline, in this case, the UE discards the previous uplink scheduling signaling. If the UL data arrives before the deadline, the UE transmits the UL data according to the uplink scheduling signaling; otherwise, the UE discards the UL scheduling signaling, or the UE transmits SR / BSR and / or TI according to the UL scheduling signaling. As shown in Figure 9, when no UL data arrives at t0, there is no data transmission in time slot 5, so the UE uses PUSCH1 to transmit SR and BSR.

[0056] The systems and processes described above can be encoded in a signal-carrying medium, a computer-readable medium (such as memory), programmed within a device (such as one or more integrated circuits, one or more processors), or processed by a controller or computer. The data can be analyzed in a computer system and used to generate a spectrogram. If the method is executed by software, the software can reside in memory that communicates with the transmitter via a storage device, synchronizer, communication interface, or non-volatile or volatile memory, or be connected via an interface to such a storage device, synchronizer, communication interface, or non-volatile or volatile memory. A circuit or electronic device is designed to transmit data to another location. The memory may include an ordered list of executable instructions for implementing logical functions. The described logical functions or any system elements can be implemented via optical circuitry, digital circuitry, source code, analog circuitry, or analog sources (such as analog electrical, audio, or video signals or combinations thereof). The software can be implemented in any computer-readable or signal-carrying medium for use by or connection to an instruction-executable system, apparatus, or device. Such a system may include a computer-based system, a processor-integrated system, or another system that can selectively obtain instructions from an instruction-executable system, apparatus, or device that can also execute instructions.

[0057] "Computer-readable medium," "machine-readable medium," "signal propagation medium," and / or "signal-carrying medium" can include any device that includes, stores, transmits, propagates, or transmits software for use by or connection to an instruction-executable system, apparatus, or device. Machine-readable media may optionally be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, devices, or propagation media. A non-exhaustive list of examples of machine-readable media would include: an electrical connection "electronic device" having one or more wires, a portable magnetic disk or optical disk, volatile memory (such as random access memory, RAM), read-only memory, erasable programmable read-only memory (EPROM, or flash memory), or optical fiber. Because software can be electrically stored as an image or other format (e.g., by optical scanning) and then compiled, and / or interpreted or otherwise processed, machine-readable media may also include tangible media on which software is printed. The processed medium can then be stored in computer and / or machine memory.

[0058] The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of various embodiments. The illustrations are not intended to be a complete description of all elements and features of apparatuses and systems utilizing the structures or methods described herein. Many other embodiments will be apparent to those skilled in the art upon review of this disclosure. Other embodiments may be utilized and derived from this disclosure, allowing for structural and logical substitutions and changes without departing from the scope of this disclosure. Furthermore, the illustrations are representative only and may not be drawn to scale. Some scales within the illustrations may be exaggerated, while others may be minimized. Therefore, this disclosure and the accompanying drawings should be considered illustrative rather than restrictive.

[0059] One or more embodiments of this disclosure may be referred to herein, individually and / or collectively, by the term "invention," merely for convenience and not intended to voluntarily limit the scope of this application to any particular invention or inventive concept. Furthermore, although specific embodiments have been shown and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of the various embodiments. Combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art upon review of the specification.

[0060] The phrase "coupled with" is defined as indicating a direct connection or indirect connection via one or more intermediate components. Such intermediate components may include both hardware and software-based components. The arrangement and type of components may be varied without departing from the spirit or scope of the claims described herein. Additional, different, or fewer components may be provided.

[0061] The subject matter disclosed above should be considered illustrative rather than restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments falling within the true spirit and scope of the invention. Therefore, to the fullest extent permitted by law, the scope of the invention will be determined by the broadest permissible interpretation of the claims and their equivalents, and should not be limited or restricted by the foregoing detailed description. While various embodiments of the invention have been described, it will be apparent to those skilled in the art that many more embodiments and implementations are possible within the scope of the invention. Therefore, the invention should not be limited except by the appended claims and their equivalents.

Claims

1. A method for wireless communication, comprising: Send a scheduling request or a buffer status report (BSR); And provide timing information for the scheduling request.

2. The method according to claim 1, wherein, The scheduling request indicates an uplink data scheduling request.

3. The method according to claim 1, wherein, The transmission and provision are performed by the user equipment (UE) to the base station.

4. The method according to claim 3, further comprising: The UE capability is reported to the base station, wherein the UE capability indicates the timing information.

5. The method according to claim 1, wherein, The maximum value of the timing information depends on the UE capability.

6. The method according to claim 1, wherein, The timing information is provided at a different frequency and / or with different code domain resources than the scheduling request.

7. The method according to claim 1, wherein, The timing information includes multiple time points.

8. The method according to claim 7, wherein, Each of the multiple time points corresponds to a single scheduling request.

9. The method according to claim 1, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, when the uplink data arrives, or when uplink resources are requested.

10. A method for wireless communication, comprising: In the absence of uplink data to be transmitted, an uplink scheduling signal is sent to the user equipment (UE).

11. The method according to claim 10, wherein, The uplink scheduling signal is considered valid before the deadline.

12. The method according to claim 10, wherein, No other uplink scheduling signal is transmitted before the deadline.

13. The method of claim 10, further comprising: Another uplink scheduling signal is transmitted before the deadline, wherein the uplink scheduling signal is considered discarded by the UE when the UE receives the transmission.

14. The method of claim 10, further comprising: When uplink data arrives before the deadline, the uplink data is received according to the uplink scheduling signal.

15. The method of claim 10, further comprising: Receive timing information for the transmission.

16. The method according to claim 15, wherein, The uplink data to be transmitted is not available until the uplink scheduling signal is sent and the UE receives the uplink scheduling signal.

17. The method of claim 15, further comprising: The ability of the UE to receive the timing information indicated by the UE.

18. The method according to claim 15, wherein, The maximum value of the timing information depends on the UE capability.

19. The method according to claim 15, wherein, The timing information is provided at a different frequency and / or with different code domain resources than the scheduling signal.

20. The method of claim 15, wherein, The timing information includes multiple time points.

21. The method according to claim 19, wherein, Each of the multiple time points corresponds to a single scheduling request.

22. The method according to claim 15, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, or when uplink data arrives.

23. A method for wireless communication, comprising: In the absence of uplink data to be transmitted, the uplink scheduling signal is received at the user equipment (UE).

24. The method according to claim 23, wherein, The uplink data to be transmitted is not available until the uplink scheduling signal is received.

25. The method of claim 23, further comprising: Provide timing information for the transmission.

26. The method according to claim 25, wherein, The maximum value of the timing information depends on the UE capability.

27. The method according to claim 23, wherein, The uplink scheduling signal is valid until the deadline.

28. The method according to claim 23, wherein, The UE does not expect another uplink scheduling signal before the deadline.

29. The method of claim 23, further comprising: If the other uplink scheduling signal is received before the deadline, the uplink scheduling signal is discarded.

30. The method of claim 23, further comprising: When uplink data arrives before the deadline, the uplink data is transmitted according to the uplink scheduling signal.

31. The method of claim 23, further comprising: Discard the uplink scheduling signal.

32. A method for wireless communication, comprising: The ability of a user equipment (UE) to receive timing indication information; And determine the timing information for the scheduling request from the UE capabilities.

33. The method according to claim 32, wherein, The timing information is part of the UE's capabilities.

34. The method according to claim 32, wherein, The timing information is implicitly determined from the UE capability.

35. The method according to claim 32, wherein, The scheduling request includes a cache status report (BSR).

36. The method according to claim 32, wherein, The maximum value of the timing information depends on the UE capability.

37. The method according to claim 32, wherein, The timing information includes multiple time points, each time point corresponding to a single scheduling request.

38. The method according to claim 32, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, or when uplink data arrives.

39. A method for wireless communication, comprising: Send timing information that can imply a scheduling request.

40. The method according to claim 39, wherein, The scheduling request indicates an uplink data scheduling request.

41. The method according to claim 39, wherein, The transmission is performed by the user equipment (UE) to the base station.

42. The method of claim 41, further comprising: The UE capability is reported to the base station, wherein the UE capability indicates the timing information.

43. The method according to claim 39, wherein, The maximum value of the timing information depends on the UE capability.

44. The method according to claim 39, wherein, The timing information includes multiple time points.

45. The method according to claim 44, wherein, Each of the multiple time points corresponds to a single scheduling request.

46. ​​The method according to claim 39, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, when the uplink data arrives, or when uplink resources are requested.

47. A method for wireless communication, comprising: Receive scheduling requests or buffer status reports (BSRs); And receive timing information.

48. The method according to claim 47, wherein, The timing information is received together with the scheduling request or cache status report (BSR).

49. The method according to claim 47, wherein, The scheduling request indicates an uplink data scheduling request.

50. The method of claim 47, wherein, The reception is performed by the base station from the user equipment (UE).

51. The method of claim 50, further comprising: The UE's ability to receive the timing information indicated therein.

52. The method according to claim 47, wherein, The maximum value of the timing information depends on the UE capability.

53. The method according to claim 47, wherein, The timing information is provided at a different frequency and / or with different code domain resources than the scheduling request.

54. The method according to claim 47, wherein, The timing information includes multiple time points.

55. The method according to claim 54, wherein, Each of the multiple time points corresponds to a single scheduling request.

56. The method according to claim 54, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, when the uplink data arrives, or when uplink resources are requested.

57. A method for wireless communication, comprising: Receive timed information; And based on the timing information, a scheduling request is implied.

58. The method according to claim 57, wherein, The scheduling request indicates an uplink data scheduling request.

59. The method according to claim 57, wherein, The reception is performed by the base station from the user equipment (UE).

60. The method of claim 59, further comprising: Receive UE capabilities from the UE, wherein the UE capabilities indicate the timing information.

61. The method according to claim 57, wherein, The maximum value of the timing information depends on the UE capability.

62. The method according to claim 57, wherein, The timing information includes multiple time points.

63. The method according to claim 62, wherein, Each of the multiple time points corresponds to a single scheduling request.

64. The method according to claim 57, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, when the uplink data arrives, or when uplink resources are requested.

65. A method for wireless communication, comprising: Send user equipment (UE) capabilities, wherein timing information is determined from the UE capabilities in response to a scheduling request.

66. The method according to claim 65, wherein, The timing information is part of the UE's capabilities.

67. The method according to claim 65, wherein, The timing information is implicitly determined from the UE capability.

68. The method according to claim 65, wherein, The scheduling request includes a cache status report (BSR).

69. The method according to claim 65, wherein, The maximum value of the timing information depends on the UE capability.

70. The method of claim 65, wherein, The timing information includes multiple time points, each time point corresponding to a single scheduling request.

71. The method according to claim 65, wherein, The timing information includes indications of when a scheduling request occurs, when the UE needs to transmit uplink data, or when uplink data arrives.

72. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 71.

73. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 71.

Images