US10568114B2 - Method and apparatus for requesting resources in a wireless communication system - Google Patents

Method and apparatus for requesting resources in a wireless communication system Download PDF

Info

Publication number
US10568114B2
US10568114B2 US14/856,942 US201514856942A US10568114B2 US 10568114 B2 US10568114 B2 US 10568114B2 US 201514856942 A US201514856942 A US 201514856942A US 10568114 B2 US10568114 B2 US 10568114B2
Authority
US
United States
Prior art keywords
data
bsr
timing
new
period
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US14/856,942
Other languages
English (en)
Other versions
US20160081108A1 (en
Inventor
Li-Chih Tseng
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Innovative Sonic Corp
Original Assignee
Innovative Sonic Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Innovative Sonic Corp filed Critical Innovative Sonic Corp
Priority to US14/856,942 priority Critical patent/US10568114B2/en
Assigned to INNOVATIVE SONIC CORPORATION reassignment INNOVATIVE SONIC CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TSENG, LI-CHIH
Publication of US20160081108A1 publication Critical patent/US20160081108A1/en
Application granted granted Critical
Publication of US10568114B2 publication Critical patent/US10568114B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H04W72/1242—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W72/0493—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies

Definitions

  • This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus for requesting resources in a wireless communication system.
  • IP Internet Protocol
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the E-UTRAN system can provide high data throughput in order to realize the above-noted voice over IP and multimedia services.
  • the E-UTRAN system's standardization work is currently being performed by the 3GPP standards organization. Accordingly, changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.
  • a method and apparatus are disclosed for requesting resources in a wireless communication system.
  • the method includes sending a first scheduling assignment (SA) in a first SA period at a first timing.
  • the method also includes considering a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing.
  • the method further includes skipping a resource associated with the first SA for sending the data at a third timing, wherein the third timing is later than the second timing and earlier than a second SA period which is later than the first SA period.
  • the method includes sending a second SA in the second SA period.
  • the method includes sending the data on a resource associated with the SA.
  • FIG. 1 shows a diagram of a wireless communication system according to one exemplary embodiment.
  • FIG. 2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment.
  • a transmitter system also known as access network
  • a receiver system also known as user equipment or UE
  • FIG. 3 is a functional block diagram of a communication system according to one exemplary embodiment.
  • FIG. 4 is a functional block diagram of the program code of FIG. 3 according to one exemplary embodiment.
  • FIG. 5 is a reproduction of FIG. 2 of 3GPP R2-141256.
  • FIG. 6 is a reproduction of FIG. 6.1.2-1 of 3GPP TS 36.321 v11.2.0.
  • FIG. 7 is a reproduction of FIG. 6.1.2-2 of 3GPP TS 36.321 v11.2.0.
  • FIG. 8 is a reproduction of FIG. 6.1.2-3 of 3GPP TS 36.321 v11.2.0.
  • FIG. 9 is a reproduction of FIG. 6.1.3-1 of 3GPP TS 36.321 v11.2.0.
  • FIG. 10 is a reproduction of FIG. 6.1.3-2 of 3GPP TS 36.321 v11.2.0.
  • FIG. 11 is a diagram according to one exemplary embodiment.
  • FIG. 12 is a diagram according to one exemplary embodiment.
  • FIG. 13 is a flow chart according to one exemplary embodiment.
  • FIG. 14 is a flow chart according to one exemplary embodiment.
  • Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, or some other modulation techniques.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • 3GPP LTE Long Term Evolution
  • 3GPP LTE-A or LTE-Advanced Long Term Evolution Advanced
  • 3GPP2 UMB Ultra Mobile Broadband
  • WiMax Worldwide Interoperability for Mobile communications
  • the exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including SP-110638, “WID on Proposal for a study on Proximity-based Services”; R2-141256, “Layer 2 procedures for D2D Communication”, Ericsson; R2-140625, “Resource allocation for D2D transmitters in coverage”, Ericsson; TS 36.321 V11.2.0, “Medium Access Control (MAC) protocol specification”; R1-143590, “Chairman's Notes of Agenda Item 7.2.3 LTE Device to Device Proximity Services”, Session Chairman (Alcatel-Lucent).
  • 3GPP 3rd Generation Partnership Project
  • FIG. 1 shows a multiple access wireless communication system according to one embodiment of the invention.
  • An access network 100 includes multiple antenna groups, one including 104 and 106 , another including 108 and 110 , and an additional including 112 and 114 . In FIG. 1 , only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group.
  • Access terminal 116 is in communication with antennas 112 and 114 , where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118 .
  • Access terminal (AT) 122 is in communication with antennas 106 and 108 , where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124 .
  • communication links 118 , 120 , 124 and 126 may use different frequency for communication.
  • forward link 120 may use a different frequency then that used by reverse link 118 .
  • antenna groups each are designed to communicate to access terminals in a sector of the areas covered by access network 100 .
  • the transmitting antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 122 . Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.
  • An access network may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an evolved Node B (eNB), or some other terminology.
  • An access terminal may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.
  • FIG. 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200 .
  • a transmitter system 210 also known as the access network
  • a receiver system 250 also known as access terminal (AT) or user equipment (UE)
  • traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214 .
  • TX transmit
  • each data stream is transmitted over a respective transmit antenna.
  • TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
  • the coded data for each data stream may be multiplexed with pilot data using OFDM techniques.
  • the pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response.
  • the multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols.
  • the data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230 .
  • TX MIMO processor 220 The modulation symbols for all data streams are then provided to a TX MIMO processor 220 , which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 220 then provides N T modulation symbol streams to N T transmitters (TMTR) 222 a through 222 t . In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
  • Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel.
  • N T modulated signals from transmitters 222 a through 222 t are then transmitted from N T antennas 224 a through 224 t , respectively.
  • the transmitted modulated signals are received by N R antennas 252 a through 252 r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254 a through 254 r .
  • Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.
  • An RX data processor 260 then receives and processes the N R received symbol streams from N R receivers 254 based on a particular receiver processing technique to provide N T “detected” symbol streams.
  • the RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream.
  • the processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210 .
  • a processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.
  • the reverse link message may comprise various types of information regarding the communication link and/or the received data stream.
  • the reverse link message is then processed by a TX data processor 238 , which also receives traffic data for a number of data streams from a data source 236 , modulated by a modulator 280 , conditioned by transmitters 254 a through 254 r , and transmitted back to transmitter system 210 .
  • the modulated signals from receiver system 250 are received by antennas 224 , conditioned by receivers 222 , demodulated by a demodulator 240 , and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250 .
  • Processor 230 determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.
  • FIG. 3 shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention.
  • the communication device 300 in a wireless communication system can be utilized for realizing the UEs (or ATs) 116 and 122 in FIG. 1 , and the wireless communications system is preferably the LTE system.
  • the communication device 300 may include an input device 302 , an output device 304 , a control circuit 306 , a central processing unit (CPU) 308 , a memory 310 , a program code 312 , and a transceiver 314 .
  • the control circuit 306 executes the program code 312 in the memory 310 through the CPU 308 , thereby controlling an operation of the communications device 300 .
  • the communications device 300 can receive signals input by a user through the input device 302 , such as a keyboard or keypad, and can output images and sounds through the output device 304 , such as a monitor or speakers.
  • the transceiver 314 is used to receive and transmit wireless signals, delivering received signals to the control circuit 306 , and outputting signals generated by the control circuit 306 wirelessly.
  • FIG. 4 is a simplified block diagram of the program code 312 shown in FIG. 3 in accordance with one embodiment of the invention.
  • the program code 312 includes an application layer 400 , a Layer 3 portion 402 , and a Layer 2 portion 404 , and is coupled to a Layer 1 portion 406 .
  • the Layer 3 portion 402 generally performs radio resource control.
  • the Layer 2 portion 404 generally performs link control.
  • the Layer 1portion 406 generally performs physical connections.
  • 3GPP SP-110638 proposes a new study item on proximity-based services (ProSe), i.e., D2D (Device to Device) services.
  • ProSe proximity-based services
  • D2D Device to Device
  • Proximity-based applications and services represent a recent and enormous socio-technological trend.
  • the principle of these applications is to discover instances of the applications running in devices that are within proximity of each other, and ultimately also exchange application-related data.
  • proximity-based discovery and communications in the public safety community.
  • 3GPP technology has the opportunity to become the platform of choice to enable proximity-based discovery and communication between devices, and promote a vast array of future and more advanced proximity-based applications.
  • the objective is to study use cases and identify potential requirements for an operator network controlled discovery and communications between devices that are in proximity, under continuous network control, and are under a 3GPP network coverage, for:
  • study item will study use cases and identify potential requirements for
  • RA Random Access
  • 3GPP R2-141256 introduces a D2D resource request/grant procedure using random access (RA) procedure and a new MAC (Medium Access Control) control element, called D2D BSR (Buffer Status Report), as follows:
  • This procedure applies only to communication mode 1.
  • the UE has been configured with a logical channel for D2D Communication. It is also assumed that the UE is in RRC_CONNECTED. The purpose of this procedure is for the UE to get a grant from the eNB to transmit on the ProSe physical channel. There are two cases, whether the UE has a PUCCH resource to send the Scheduling Request on or not.
  • the UE does not have a PUCCH Resource
  • FIG. 1 shows how the random access procedure is used to support D2D Communication requests and grants.
  • FIG. 2 of 3GPP R2-141256 has been reproduced as FIG. 5 ]
  • the D2D-BSR should be transmitted on the PUSCH similar to legacy BSR.
  • the purpose of the D2D-BSR is for the UE to inform the eNB about the amount of data the UE has on logical channels related to D2D.
  • the eNB configures the UE with a logical channel ID to be used for D2D communication. Although this makes it possible to reuse the existing BSR, it would require at least one logical channel group for D2D communication. If the UE is also configured with legacy LTE bearers and D2D discovery, the four existing logical channel groups may become a restriction.
  • ProSe BSR MAC CE
  • 3GPP R2-140625 proposes a mechanism, which is similar with legacy mechanism, for transmitting D2D BSR as follows:
  • the UE Upon completion of this procedure the UE will have a D2D resource to transmit the data on.
  • 3GPP TS 36.321 v11.2.0 introduces and describes how a BSR triggers a SR (Schedule Request)/D-SR (Dynamic Schedule Request) procedure or a Random Access procedure for transmission and legacy BSR format as follows:
  • the random-access procedure shall be performed as follows:
  • the UE shall monitor the PDCCH of the PCell for Random Access Response(s) identified by the RA-RNTI defined below, in the RA Response window which starts at the subframe that contains the end of the preamble transmission [ 7 ] plus three subframes and has length ra-ResponseWindowSize subframes.
  • t_id is the index of the first subframe of the specified PRACH (0 ⁇ t_id ⁇ 10)
  • f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0 ⁇ f_id ⁇ 6).
  • the UE may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted Random Access Preamble.
  • Random Access Response reception is considered not successful and the UE shall:
  • Contention Resolution is based on either C-RNTI on PDCCH of the PCell or UE Contention Resolution Identity on DL-SCH.
  • the UE shall:
  • the Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.
  • the UE shall set the SR_COUNTER to 0.
  • the UE shall for each TTI:
  • the Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers of the UE.
  • RRC controls BSR reporting by configuring the two timers periodicBSR-Timer and retxBSR-Timer and by, for each logical channel, optionally signalling logicalChannelGroup which allocates the logical channel to an LCG [8].
  • the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.
  • a Buffer Status Report shall be triggered if any of the following events occur:
  • a MAC PDU shall contain at most one MAC BSR control element, even when multiple events trigger a BSR by the time a BSR can be transmitted in which case the Regular BSR and the Periodic BSR shall have precedence over the padding BSR.
  • the UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.
  • the UE shall transmit at most one Regular/Periodic BSR in a TTI. If the UE is requested to transmit multiple MAC PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR.
  • All BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI.
  • Each LCG shall report at the most one buffer status value per TTI and this value shall be reported in all BSRs reporting buffer status for this LCG.
  • a MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC control elements, and optionally padding; as described in FIG. 6.1.2-3.
  • MAC SDU MAC Service Data Units
  • Both the MAC header and the MAC SDUs are of variable sizes.
  • a MAC PDU header consists of one or more MAC PDU subheaders; each subheader corresponds to either a MAC SDU, a MAC control element or padding.
  • a MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU and for fixed sized MAC control elements.
  • the last subheader in the MAC PDU and subheaders for fixed sized MAC control elements consist solely of the four header fields R/R/E/LCID.
  • a MAC PDU subheader corresponding to padding consists of the four header fields R/R/E/LCID.
  • FIG. 6.1.2-1 of 3GPP TS 36.321 v11.2.0 has been reproduced as FIG. 6 .
  • FIG. 6.1.2-2 of 3GPP TS 36.321 v11.2.0 has been reproduced as FIG. 7 .
  • MAC PDU subheaders have the same order as the corresponding MAC SDUs, MAC control elements and padding.
  • MAC control elements are always placed before any MAC SDU.
  • Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed.
  • one or two MAC PDU subheaders corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader.
  • a maximum of one MAC PDU can be transmitted per TB per UE.
  • a maximum of one MCH MAC PDU can be transmitted per TTI.
  • FIG. 6.1.2-3 of 3GPP TS 36.321 v11.2.0 has been Reproduced as FIG. 8 .
  • BSR Buffer Status Report
  • the BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2.
  • the MAC header and subheaders are octet aligned.
  • 3GPP R1-143590 states:
  • the only possible value of the number of transmissions of a given D2D communication MAC PDU is 4.
  • Each transmission takes place in one subframe.
  • the UE may need to consider (if possible) (i) how to use the transmission opportunities, or (ii) whether to send a Scheduling Assignment in the subsequent SA period and then be able to send the D2D data and/or the ProSe BSR through the resources associated with the subsequent SA period.
  • the latency of transmitting the D2D data and transmission robustness between transmitter and receiver might need to be studied, especially for some services like urgent data or VoIP.
  • the general concept of the invention is that UE needs to determine whether to send BSR and/or SR based on the available resources which have been allocated before the determination. More specifically, if D2D data arrives or ProSe BSR is triggered, UE would check if there are any available (whether sufficient or not) transmission opportunities/D2D grants in the current or the subsequent SA/Data Cycle), and would determine whether to trigger ProSe BSR or to cancel (or not send) the triggered ProSe BSR, or whether to send a scheduling request for D2D grant.
  • the UE may not send the ProSe BSR to the base station if the data can be sent through D3 and/or D4, or even D5 ⁇ D7. If the D2D grant has been allocated previously by the base station and not yet used by the UE then UE may not trigger Scheduling Request for the new D2D data.
  • Mode 1 means the UE needs to by itself select SA (randomly or following some specific rule) and derives the D2D resource associated with the SA.
  • SA randomly or following some specific rule
  • Mode 2 means the UE should send a request to base station, and the base station can then schedule D2D resource for the UE.
  • the UE could skip D3/D4 of SA/Data Cycle 1 and could send a SA in the next SA period to send the data in the SA/Data Cycle 2.
  • ProSe BSR or information of amount of D2D data could be sent by a first UE to the network or to a second UE (i.e., buffer status could be also sent between two different UEs except for between UE and network) since it might be also beneficial for the second UE to know how much data will be transmitted roughly in advance by the first UE.
  • FIG. 13 is a flow chart 1300 in accordance with one exemplary embodiment from the perspective of a UE.
  • the UE sends a first scheduling assignment (SA) in a first SA period at a first timing.
  • the UE considers a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing.
  • the UE skips a resource associated with the first SA for sending the data at a third timing, wherein the third timing is later than the second timing and earlier than a second SA period which is later than the first SA period.
  • the first SA and the second SA are associated with a plurality of resources in a SA/Data Cycle.
  • the plurality of resources could be associated with a T-RPT (Time Resource Pattern for Transmission).
  • the UE sends a second SA in the second SA period.
  • the UE transmits or sends the data on a resource associated with the second SA.
  • the data could include control information (such as a BSR) and/or data information (such as upper layer data on the UE side).
  • the UE determines whether to send a scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with the SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to a base station (BS) the scheduling request (SR) associated with the triggered BSR.
  • BS base station
  • SR scheduling request
  • the final UE behavior does not send a SR since the remaining resources are sufficient to carry all remaining buffered data. Since a triggered BSR could trigger a SR, it is then foreseen not to send the triggered SR to request an UL grant for sending the triggered BSR. Normally, when a BSR is triggered due to higher priority data arrival or data available from empty to non-empty or some other specific case, the UE would need to send the SR, which is triggered by the BSR, to request an UL grant, and UE would use the UL grant for sending the BSR. However, in this special case, nothing will happen.
  • the device 300 includes a program code 312 stored in memory 310 of a UE.
  • the CPU 308 could execute program code 312 to enable the UE to (i) send a first SA in a first SA period at a first timing, (ii) consider a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing, (iii) skip a resource associated with the first SA for sending the data at a third timing, wherein the third timing is later than the second timing and earlier than a second SA period which is later than the first SA period, (iv) send a second SA in the second SA period, and (v) transmit or send the data on a resource associated with the second SA.
  • the CPU could further execute program code 312 to enable the UE to determine whether to send a scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with a SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to a base station the scheduling request (SR) associated with the triggered BSR.
  • SR scheduling request
  • CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 14 is a flow chart 1400 in accordance with one exemplary embodiment from the perspective of a UE.
  • the UE establishes a connection with a BS.
  • the UE sends a first scheduling request to the BS.
  • the UE receives a control signal from the BS.
  • the UE sends a SA associated with the control signal at a first timing.
  • the UE considers a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing.
  • the UE determines whether there is an available resource associated with the SA for transmitting the data.
  • the SA is associated with a plurality of resources in a SA/Data Cycle. Furthermore, the plurality of resources could be associated with a T-RPT.
  • the UE transmits or sends the data on the available resource at a third timing, wherein the third timing is later than the second timing.
  • the data could include control information (such as a BSR) and/or data information (such as upper layer data in the UE side).
  • the UE determines whether to send a second scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with the SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to the base station the second SR associated with the triggered BSR since the amount of remaining resources associated with the SA can accommodate the data to result in BSR cancellation.
  • the final UE behavior does not send a SR since the remaining resources are sufficient to carry all remaining buffered data. Since a triggered BSR could trigger a SR, it is foreseen not to send the triggered SR to request an UL grant for sending the triggered BSR. Normally, when a BSR is triggered due to higher priority data arrival or data available from empty to non-empty or some other specific case, UE would need to send the SR, which is triggered by the BSR, to request an UL grant, and UE would use the UL grant for sending the BSR. However, in this special case, nothing will happen.
  • the device 300 includes a program code 312 stored in memory 310 of a UE.
  • the CPU 308 could execute program code 312 to enable the UE to (i) establish a connection with a BS, (ii) send a first scheduling request to the BS, (iii) receive a control signal from the BS, (iv) sending a SA associated with the control signal at a first timing, (v) consider a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing, (vi) determine whether there is an available resource associated with the SA for transmitting the data, and (vii) transmit or send the data on the available resource at a third timing, wherein the third timing is later than the second timing.
  • the CPU could further execute program code 312 to enable the UE to determine whether to send a second scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with the SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to a base station the second scheduling request (SR) associated with the triggered BSR since the amount of remaining resources associated with the SA can accommodate the data to result in BSR cancellation.
  • SR second scheduling request
  • CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 15 is a flow chart 1500 in accordance with one exemplary embodiment from the perspective of a UE.
  • the UE establishes a connection with a base station.
  • the UE sends a first scheduling request to the BS.
  • the UE receives a control signal from the BS.
  • the UE sends a SA associated with the control signal in a SA period at a first timing.
  • the SA is associated with a plurality of resources in a SA/Data Cycle.
  • the plurality of resources could be associated with a T-RPT.
  • the UE considers a data available in the UE at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing.
  • the data could include control information (such as a BSR) and/or data information (such as upper layer data in the UE side).
  • step 1530 the UE triggers a BSR associated with the data.
  • step 1535 the UE cancels the BSR since the amount of remaining resources associated with the SA can accommodate the data.
  • step 1540 the UE transmits the data on the remaining resources at a third timing, wherein the third timing is later than the second timing.
  • the final UE behavior does not send a SR since the remaining resources are sufficient to carry all remaining buffered data. Since a triggered BSR could trigger SR, it is foreseen to cancel the BSR that has just been triggered. Then no SR would be triggered. As shown in steps 1530 and 1535 , a BSR is triggered and then intentionally cancelled so that the UE would not send any SR for requesting an UL grant for sending any BSR. Normally, when a BSR is triggered due to higher priority data arrival or data available from empty to non-empty or some other specific case, the UE would need to send SR, which is triggered by the BSR, to request an UL grant, and UE would use the UL grant for sending the BSR. However, in this special case, nothing will happen.
  • the UE determines whether to send a second scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with the SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to the base station the second SR associated with the triggered BSR since the amount of remaining resources associated with the SA can accommodate the data to result in BSR cancellation.
  • the final UE behavior does not send a SR since the remaining resources are sufficient to carry all remaining buffered data. Since a triggered BSR could trigger SR, it is foreseen not to send the triggered SR to request an UL grant for sending the triggered BSR. Normally, when a BSR is triggered due to higher priority data arrival or data available from empty to non-empty or some other specific case, the UE would need to send a SR, which is triggered by the BSR, to request an UL grant, and UE would use the UL grant for sending the BSR. However, in this special case, nothing will happen.
  • the device 300 includes a program code 312 stored in memory 310 of a UE.
  • the CPU 308 could execute program code 312 to enable the UE to (i) establish a connection with a BS, (ii) send a first scheduling request to the BS, (iii) receive a control signal from the BS, (iv) sending a SA associated with the control signal in a SA period at a first timing, (v) consider a data available at a second timing, wherein the data needs to be transmitted and the second timing is later than the first timing, (vi) triggers a BSR associated with the data, (vii) cancel the BSR since the amount of remaining resources associated with the SA can accommodate the data, and (viii) transmit or send the data on the remaining resources at a third timing, wherein the third timing is later than the second timing.
  • the CPU could further execute program code 312 to enable the UE to determine whether to send a second scheduling request or to trigger a BSR associated with the data based on the amount of existing or remaining resources associated with the SA which the UE could use. In one embodiment, the UE does not trigger the BSR associated with the data. Alternatively, the UE triggers the BSR associated with the data. However, the UE does not send to a base station the second scheduling request (SR) associated with the triggered BSR since the amount of remaining resources associated with the SA can accommodate the data to result in BSR cancellation.
  • SR second scheduling request
  • CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • the control signal from the BS could be a D2D grant received on PDCCH in the physical layer.
  • the D2D grant informs the UE which time and frequency resource the UE should send the SA (scheduling assignment) and D2D data in a specific SA/Data cycle.
  • the control information could be a BSR (Buffer Status Report) Control Element in the MAC layer.
  • concurrent channels may be established based on pulse repetition frequencies.
  • concurrent channels may be established based on pulse position or offsets.
  • concurrent channels may be established based on time hopping sequences.
  • concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.
  • the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point.
  • the IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both.
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module e.g., including executable instructions and related data
  • other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art.
  • a sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium.
  • a sample storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in user equipment.
  • the processor and the storage medium may reside as discrete components in user equipment.
  • any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure.
  • a computer program product may comprise packaging materials.
US14/856,942 2014-09-17 2015-09-17 Method and apparatus for requesting resources in a wireless communication system Active 2036-06-06 US10568114B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/856,942 US10568114B2 (en) 2014-09-17 2015-09-17 Method and apparatus for requesting resources in a wireless communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201462051500P 2014-09-17 2014-09-17
US14/856,942 US10568114B2 (en) 2014-09-17 2015-09-17 Method and apparatus for requesting resources in a wireless communication system

Publications (2)

Publication Number Publication Date
US20160081108A1 US20160081108A1 (en) 2016-03-17
US10568114B2 true US10568114B2 (en) 2020-02-18

Family

ID=54196788

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/856,942 Active 2036-06-06 US10568114B2 (en) 2014-09-17 2015-09-17 Method and apparatus for requesting resources in a wireless communication system

Country Status (7)

Country Link
US (1) US10568114B2 (zh)
EP (1) EP2999286B1 (zh)
JP (1) JP6649728B2 (zh)
KR (1) KR101780375B1 (zh)
CN (1) CN105451273B (zh)
ES (1) ES2798312T3 (zh)
TW (1) TWI612833B (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11350453B2 (en) 2019-07-18 2022-05-31 Samsung Electronics Co., Ltd. System and method for performing transmission cancellation indication monitoring
US11357032B2 (en) * 2015-09-18 2022-06-07 Huawei Technologies Co., Ltd. Control information transmission method, transmit end, and receive end

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102289116B1 (ko) * 2014-08-08 2021-08-12 주식회사 아이티엘 단말간 통신을 지원하는 무선 통신 시스템에서 신호의 송수신 방법 및 장치
WO2016048082A1 (en) * 2014-09-25 2016-03-31 Lg Electronics Inc. Method and apparatus for canceling triggered prose bsr in wireless communication system
US10165580B2 (en) * 2014-10-30 2018-12-25 Lg Electronics Inc. Method for prohibiting from triggering scheduling request in a D2D communication system and device therefor
WO2016072590A1 (en) * 2014-11-06 2016-05-12 Lg Electronics Inc. Method for canceling scheduling requests triggered by a sidelink buffer status report in a d2d communication system and device therefor
WO2016072591A1 (en) * 2014-11-06 2016-05-12 Lg Electronics Inc. Method for canceling a sidelink buffer status report in a d2d communication system and device therefor
KR20170095958A (ko) * 2014-12-31 2017-08-23 후지쯔 가부시끼가이샤 버퍼 상태 보고를 생성하기 위한 방법 및 장치 및 통신 시스템
US10512105B2 (en) * 2015-03-09 2019-12-17 Lg Electronics Inc. Method for operating a fast random access procedure in a wireless communication system and a device therefor
US10869296B2 (en) * 2015-04-17 2020-12-15 Panasonic Intellectual Property Corporation Of America Multiple prose group communication during a sidelink control period
US20160323777A1 (en) * 2015-04-28 2016-11-03 Asustek Computer Inc. Method and apparatus for supporting ue-to-network relay based on device to device service in a wireless communication system
US10743336B2 (en) * 2015-09-23 2020-08-11 Telefonaktiebolaget Lm Ericsson (Publ) Scheduling and transmitting control information and data for direct communication
US10667286B2 (en) * 2015-10-21 2020-05-26 Lg Electronics Inc. Method for selecting prose destinations or SL grants in a D2D communication system and device therefor
WO2017077625A1 (ja) * 2015-11-05 2017-05-11 富士通株式会社 通信装置および無線通信方法
US10716130B2 (en) 2016-02-05 2020-07-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Communication method, terminal equipment, and network equipment
AU2017236677A1 (en) * 2016-03-21 2018-07-12 Telefonaktiebolaget Lm Ericsson (Publ) Uplink data indication
EP3422787B1 (en) * 2016-03-31 2020-04-29 Huawei Technologies Co., Ltd. Buffer processing method, and user equipment
WO2017170223A1 (ja) * 2016-03-31 2017-10-05 株式会社Ｎｔｔドコモ ユーザ装置
CN108605319A (zh) * 2016-04-01 2018-09-28 华为技术有限公司 一种上行信息的传输方法及设备、系统
CN112468279B (zh) * 2016-04-15 2022-10-18 Oppo广东移动通信有限公司 资源确定的方法和装置
CN109479302B (zh) 2016-07-07 2020-09-29 松下电器（美国）知识产权公司 用于v2x发送的改进的半持续资源分配行为
WO2018030710A1 (en) 2016-08-11 2018-02-15 Samsung Electronics Co., Ltd. Method and apparatus for scheduling uplink data in mobile communication system
US11191073B2 (en) 2016-08-12 2021-11-30 Telefonaktiebolaget Lm Ericsson (Publ) UL scheduling timing in TDD with 1 MS TTI and reduced processing time
WO2018084614A1 (en) * 2016-11-02 2018-05-11 Samsung Electronics Co., Ltd. Resource selection method and corresponding equipment
US10667290B2 (en) * 2016-11-30 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Method for handling users with different timing alignment requirements
EP4080980B1 (en) * 2017-01-05 2023-11-22 Motorola Mobility LLC Scheduling request indication
US11291036B2 (en) * 2017-03-24 2022-03-29 Qualcomm Incorporated Scheduling requests and buffer status reports for low latency wireless communications
KR102091925B1 (ko) * 2017-04-26 2020-03-23 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 제어 엘리먼트 전송을 위한 자원을 요청하기 위한 방법 및 장치
CN108809582B (zh) 2017-05-05 2021-07-20 华为技术有限公司 一种数据传输的方法和装置
RU2749102C1 (ru) * 2017-09-21 2021-06-04 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ передачи отчета о состоянии буфера, терминал и компьютерный носитель данных
US10645610B2 (en) * 2017-11-24 2020-05-05 Mediatek Singapore Pte. Ltd. Method and apparatus for skipping uplink transmission in mobile communications
EP3732799A1 (en) * 2017-12-27 2020-11-04 Lenovo (Singapore) Pte. Ltd. Beam recovery procedure
SG11202007570UA (en) * 2018-02-09 2020-09-29 Beijing Xiaomi Mobile Software Co Ltd Trigger hold method and trigger hold apparatus
CN110149674A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种路由更新方法及设备
WO2020113433A1 (zh) * 2018-12-04 2020-06-11 Oppo广东移动通信有限公司 一种处理调度请求的方法及装置、终端
CN112099832B (zh) * 2020-11-04 2021-04-20 中国人民解放军国防科技大学 星载设备的单粒子翻转恢复方法及系统
RU2762254C1 (ru) * 2021-05-31 2021-12-17 Бейджин Сяоми Мобайл Софтвеа Ко., Лтд. Способ сохранения возможности запуска и аппарат для сохранения возможности запуска

Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090034527A (ko) 2007-10-04 2009-04-08 한국전자통신연구원 피드백 메시지 기반의 상향 트래픽 전송 스케줄링 방법 및장치
KR20090084718A (ko) 2008-02-01 2009-08-05 엘지전자 주식회사 기할당된 무선 자원을 이용한 효율적인 Ｂｕｆｆｅｒ Ｓｔａｔｕｓ Ｒｅｐｏｒｔ(ＢＳＲ) 과정 수행 방법
US20100260152A1 (en) * 2007-10-29 2010-10-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and Arrangement in a Telecommunications System
US20100322156A1 (en) * 2009-06-17 2010-12-23 Chih-Hsiang Wu Method for transmitting data in a wireless communication system and system thereof
US20100330995A1 (en) * 2008-02-01 2010-12-30 Panasonic Corporation Communication terminal and base station
US20110255492A1 (en) 2009-01-13 2011-10-20 Zte Corporation Method and device for triggering or reporting a scheduled request in wireless networks
US20130235768A1 (en) * 2012-03-12 2013-09-12 Andrew Mark Earnshaw Handling scheduling request collisions with an ack/nack repetition signal
US20130301446A1 (en) * 2012-05-14 2013-11-14 Industrial Technology Research Institute Method of allocating resources for scheduling request and user equipment using the same and a control node using the same
US20130322413A1 (en) * 2012-05-31 2013-12-05 Interdigital Patent Holdings, Inc. Methods to enable scheduling and control of direct link communication in cellular communication systems
US20140185467A1 (en) * 2012-08-03 2014-07-03 Youn Hyoung Heo Enhanced node b, user equipment and methods for discontinuous reception in inter-enb carrier aggregation
US20140254509A1 (en) 2013-03-06 2014-09-11 Qualcomm Incorporated Methods and apparatus for multi-subframe scheduling
US9247546B2 (en) * 2014-05-13 2016-01-26 Lg Electronics Inc. Allocation of resources for device-to-device (D2D) communication and method and apparatus for transmitting and receiving signal on the basis of the resource allocation
US20160183276A1 (en) * 2013-08-07 2016-06-23 Interdigital Patent Holdings, Inc. Distributed scheduling for device-to-device communication
US20160183239A1 (en) * 2013-08-09 2016-06-23 Kt Corporation Method for transmitting buffer status report in device-to-device communication, and device thereof
US20160205714A1 (en) * 2013-08-30 2016-07-14 Kyocera Corporation Mobile communication system and user terminal
US20160381666A1 (en) * 2014-03-20 2016-12-29 Seoul National University R&Db Foundation Method for transmitting and receiving signal in wireless communication system and device therefor
US20170019812A1 (en) * 2014-03-19 2017-01-19 Lg Electronics Inc. Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
US20170041942A1 (en) * 2014-05-09 2017-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatus, and systems for determining communication priority
US20170215160A1 (en) * 2014-08-01 2017-07-27 Sun Patent Trust Transmission timing control for d2d communication
US9723618B2 (en) * 2012-05-04 2017-08-01 Sun Patent Trust Threshold-based and power-efficient scheduling request procedure

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8559365B2 (en) * 2007-10-30 2013-10-15 Coppergate Communications Ltd. After transmission return signal
PT3094148T (pt) * 2009-05-05 2020-04-22 Ericsson Telefon Ab L M Método e disposição num sistema de comunicações sem fios

Patent Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090034527A (ko) 2007-10-04 2009-04-08 한국전자통신연구원 피드백 메시지 기반의 상향 트래픽 전송 스케줄링 방법 및장치
US20100260152A1 (en) * 2007-10-29 2010-10-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and Arrangement in a Telecommunications System
KR20090084718A (ko) 2008-02-01 2009-08-05 엘지전자 주식회사 기할당된 무선 자원을 이용한 효율적인 Ｂｕｆｆｅｒ Ｓｔａｔｕｓ Ｒｅｐｏｒｔ(ＢＳＲ) 과정 수행 방법
US20100330995A1 (en) * 2008-02-01 2010-12-30 Panasonic Corporation Communication terminal and base station
US20110255492A1 (en) 2009-01-13 2011-10-20 Zte Corporation Method and device for triggering or reporting a scheduled request in wireless networks
JP2012503379A (ja) 2009-01-13 2012-02-02 中▲興▼通▲訊▼股▲ふぇん▼有限公司 無線ネットワークにおけるスケジューリングリクエストを触発或は送信する方法及び装置
US20100322156A1 (en) * 2009-06-17 2010-12-23 Chih-Hsiang Wu Method for transmitting data in a wireless communication system and system thereof
US20130235768A1 (en) * 2012-03-12 2013-09-12 Andrew Mark Earnshaw Handling scheduling request collisions with an ack/nack repetition signal
US9723618B2 (en) * 2012-05-04 2017-08-01 Sun Patent Trust Threshold-based and power-efficient scheduling request procedure
US20130301446A1 (en) * 2012-05-14 2013-11-14 Industrial Technology Research Institute Method of allocating resources for scheduling request and user equipment using the same and a control node using the same
US20130322413A1 (en) * 2012-05-31 2013-12-05 Interdigital Patent Holdings, Inc. Methods to enable scheduling and control of direct link communication in cellular communication systems
US20140185467A1 (en) * 2012-08-03 2014-07-03 Youn Hyoung Heo Enhanced node b, user equipment and methods for discontinuous reception in inter-enb carrier aggregation
US20140254509A1 (en) 2013-03-06 2014-09-11 Qualcomm Incorporated Methods and apparatus for multi-subframe scheduling
US20160183276A1 (en) * 2013-08-07 2016-06-23 Interdigital Patent Holdings, Inc. Distributed scheduling for device-to-device communication
US20160183239A1 (en) * 2013-08-09 2016-06-23 Kt Corporation Method for transmitting buffer status report in device-to-device communication, and device thereof
US20160205714A1 (en) * 2013-08-30 2016-07-14 Kyocera Corporation Mobile communication system and user terminal
US20170019812A1 (en) * 2014-03-19 2017-01-19 Lg Electronics Inc. Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
US20160381666A1 (en) * 2014-03-20 2016-12-29 Seoul National University R&Db Foundation Method for transmitting and receiving signal in wireless communication system and device therefor
US20170041942A1 (en) * 2014-05-09 2017-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatus, and systems for determining communication priority
US9247546B2 (en) * 2014-05-13 2016-01-26 Lg Electronics Inc. Allocation of resources for device-to-device (D2D) communication and method and apparatus for transmitting and receiving signal on the basis of the resource allocation
US20170215160A1 (en) * 2014-08-01 2017-07-27 Sun Patent Trust Transmission timing control for d2d communication

Non-Patent Citations (10)

* Cited by examiner, † Cited by third party
Title
3GPP TSG RAN WG1 Meeting #78, Dresden, Germany, Aug. 18-22, 2014 (R1-142930).
3GPP TSG-RAN WG1 Meeting#76bis, Shenzhenn, China, Mar. 31-Apr. 4, 2014(R1-141390).
3GPP TSG-RAN WG1 Meeting#78, Dresden, Germany, 18th-22nd 2014(R1-142898).
3GPP TSG-RAN WG1 Meeting#78, Dresden, Germany, 18th-22th 2014(R1-143367).
3GPP TSG-RAN WG2 #61, 11th-15th 2008, Sorrento, Italy (R2-081070).
3GPP TSG-RAN WG2 #85bis, Valencia, Spain, Mar. 31-Apr. 4, 2014(R2-141256).
Office Action on corresponding JP Patent Application No. 2015-184528 dated Jul. 26, 2016.
Office Action on corresponding JP Patent Application No. 2015-184528 dated Nov. 13, 2018.
Office Action on corresponding KR Patent Application No. 10-2015-0131666 dated Apr. 1, 2016.
Search Report on corresponding EP Patent Application No. 15185676.2 dated Feb. 8, 2016.

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11357032B2 (en) * 2015-09-18 2022-06-07 Huawei Technologies Co., Ltd. Control information transmission method, transmit end, and receive end
US11350453B2 (en) 2019-07-18 2022-05-31 Samsung Electronics Co., Ltd. System and method for performing transmission cancellation indication monitoring
US11956819B2 (en) 2019-07-18 2024-04-09 Samsung Electronics Co., Ltd. System and method for performing transmission cancellation indication monitoring

Also Published As

Publication number Publication date
EP2999286A1 (en) 2016-03-23
EP2999286B1 (en) 2020-04-15
CN105451273B (zh) 2020-03-31
TWI612833B (zh) 2018-01-21
TW201613399A (en) 2016-04-01
US20160081108A1 (en) 2016-03-17
JP6649728B2 (ja) 2020-02-19
ES2798312T3 (es) 2020-12-10
KR101780375B1 (ko) 2017-09-21
JP2016063545A (ja) 2016-04-25
CN105451273A (zh) 2016-03-30
KR20160033059A (ko) 2016-03-25

Similar Documents

Publication Publication Date Title
US10568114B2 (en) Method and apparatus for requesting resources in a wireless communication system
US9769699B2 (en) Method and apparatus for performing device to device (D2D) content estimation and triggering of buffer status reporting (BSR) in a wireless communication system
CN109699088B (zh) 无线通信系统中基于msg3的系统信息请求的方法和设备
US11317446B2 (en) Method and apparatus of handling BWP inactivity timer during random access procedure in a wireless communication system
US20210105126A1 (en) Feedback for Wireless Communications
US11595991B2 (en) Method for indicating the allocated resources for a HARQ message in a random access procedure for a low-complexity, narrowband terminal
EP3247054B1 (en) Control information transmission method and apparatus in wireless communication system
US10433343B2 (en) Method and apparatus for improving random access procedure in a wireless communication system
US20200275502A1 (en) Method and apparatus for improving one-to-one sidelink communication in a wireless communication system
US9888509B2 (en) Method and apparatus for performing a random access (RA) procedure for device to-device (D2D) service in a wireless communication system
US20190098655A1 (en) Method and apparatus of preventing bandwidth part misalignment in a wireless communication system
CN106576314B (zh) 用于d2d通信的传输定时控制
US11291012B2 (en) Method and apparatus for selecting beam for preconfigured uplink resources in a wireless communication system
EP3982580A1 (en) Method and apparatus for transmitting and receiving data using plurality of carriers in mobile communication system
US20150382378A1 (en) Method and apparatus for performing a random access (ra) procedure for a device-to-device (d2d) communication
JP2023536877A (ja) 制御された環境における設定済みグラントでの送信
US20240163905A1 (en) Channel Access Priority Class for Sidelink Feedback Transmission with Conflict Information

Legal Events

Date Code Title Description
AS Assignment

Owner name: INNOVATIVE SONIC CORPORATION, TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TSENG, LI-CHIH;REEL/FRAME:036590/0609

Effective date: 20150909

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4