US20180035470A1 - Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system - Google Patents

Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system Download PDF

Info

Publication number
US20180035470A1
US20180035470A1 US15/663,674 US201715663674A US2018035470A1 US 20180035470 A1 US20180035470 A1 US 20180035470A1 US 201715663674 A US201715663674 A US 201715663674A US 2018035470 A1 US2018035470 A1 US 2018035470A1
Authority
US
United States
Prior art keywords
msg3
preamble
tti information
message
tti
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.)
Abandoned
Application number
US15/663,674
Other languages
English (en)
Inventor
Wei-Yu Chen
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.)
Asustek Computer Inc
Original Assignee
Asustek Computer Inc
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 Asustek Computer Inc filed Critical Asustek Computer Inc
Priority to US15/663,674 priority Critical patent/US20180035470A1/en
Assigned to ASUSTEK COMPUTER INC. reassignment ASUSTEK COMPUTER INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, WEI-YU, TSENG, LI-CHIH
Publication of US20180035470A1 publication Critical patent/US20180035470A1/en
Priority to US16/052,505 priority patent/US11291052B2/en
Priority to US17/673,985 priority patent/US20220174747A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H04W72/1284—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0875—Non-scheduled access, e.g. ALOHA using a dedicated channel for access with assigned priorities based access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal

Definitions

  • This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus for improving Msg3 transmission of random access procedure in a wireless communication system.
  • IP Internet Protocol
  • An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
  • 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.
  • a new radio technology for the next generation e.g., 5G
  • 5G next generation
  • changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.
  • the method includes the UE receiving a message from a network.
  • the message includes a TTI (Transmission Time Interval) information of Msg3.
  • the method includes the UE transmitting a preamble to the network.
  • the method also includes the UE receiving a Msg2 from the network for responding the preamble.
  • the method further includes the UE performing a Msg3 transmission to the network according to the TTI information of Msg3.
  • 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 Figure 10.1.5.1-1 of 3GPP TS 36.300 v13.2.0.
  • FIG. 6 is a reproduction of Figure 10.1.5.2-1 of 3GPP TS 36.300 v13.2.0.
  • FIG. 7 is a diagram according to one exemplary embodiment.
  • FIG. 8 is a diagram according to one exemplary embodiment.
  • FIG. 9 is a diagram according to one exemplary embodiment.
  • FIG. 10 is a diagram according to one exemplary embodiment.
  • FIG. 11 is a diagram according to one exemplary embodiment.
  • FIG. 12 is a flow chart 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.
  • FIG. 15 is a flow chart according to one exemplary embodiment.
  • FIG. 16 is a flow chart according to one exemplary embodiment.
  • FIG. 17 is a flow chart according to one exemplary embodiment.
  • FIG. 18 is a flow chart according to one exemplary embodiment.
  • FIG. 19 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: TR 38.913 v0.3.0, “Study on Scenarios and Requirements for Next Generation Access Technologies”; TS 36.300 v13.2.0, “Overall Description; Stage 2”; TS 36.913, v13.0.0, “Requirements for further advancements for Evolved Universal Terrestrial Radio Access (E-UTRA)”; TS 36.331 v13.2.0, “Radio Resource Control (RRC); Protocol specification”; TS 36.321 v13.1.0, “Medium Access Control (MAC) protocol specification”; and R2-163445, “Scheduling Framework and Requirements”, Nokia and Alcatel-Lucent Shanghai Bell.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • R2-163445 “Scheduling Framework and Requirements”, Nokia and Alcatel
  • 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 or the base station (or AN) 100 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 .
  • CPU central processing unit
  • 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.
  • the communication device 300 in a wireless communication system can also be utilized for realizing the AN 100 in FIG. 1 .
  • 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 1 portion 406 generally performs physical connections.
  • One of the general objectives of the present application is to study the frame structure used in New RAT (NR) for 5G, to accommodate various type of requirement (discussed in 3GPP TR 38.913) for time and frequency resource, e.g., from ultra-low latency ( ⁇ 0.5 ms) to expected longer TTI (Transmission Time Interval) for MTC (Machine Type Communication), from high peak rate for eMBB (enhanced Mobile Broadband) to very low data rate for MTC.
  • TTI Transmission Time Interval
  • MTC Machine Type Communication
  • eMBB enhanced Mobile Broadband
  • An important focus is low latency aspect, while other aspect of mixing/adapting different TTIs can also be considered in the study.
  • forward compatibility is an important consideration in initial NR frame structure design as not all features of NR would be included in the beginning phase/release.
  • 3GPP TS 36.300 includes the following random access (RA) procedure related description:
  • Control plane latency refers to the time to move from a battery efficient state (e.g., IDLE) to start of continuous data transfer (e.g., ACTIVE).
  • the target for control plane latency should be 10 ms.”
  • the control plane latency requirement is set to 50 ms (as discussed in 3GPP TS 36.913).
  • the contention random access procedure consists of 4 steps, including: Msg1, Msg2, Msg3, and Msg4.
  • FIG. 5 is an exemplary embodiment for the contention random access.
  • the Msg1 and Msg3 are transmitted from a UE to a network.
  • the resource for performing Msg1 transmission and Msg3 transmission are contention resource. If the network can successfully receive a Msg3, the network could identify the UE based on contents in Msg3, and transmit a Msg4 to the UE for finishing the contention.
  • a dynamic TTI adjusting concept is discussed in 3GPP R2-163445, which proposes to set the TTI size per scheduling grant for optimizing TCP (Transmission Control Protocol) transmission case.
  • TCP Transmission Control Protocol
  • short TTI can be used to accelerate TCP slow start process
  • long TTI can be used in steady transmission rate state for reduce control signaling overhead.
  • the present application further discusses whether it can also be used to accelerate random access procedure and how to achieve dynamic TTI change in random access.
  • the following discussion mainly focuses on the Msg3 transmission step in a random access procedure.
  • the discussion below does not include UE's RF/Baseband capability differentiation (e.g., differentiation between normal cell phone in LTE and NB-IoT devices in LTE) case.
  • the first configuration is generally for normal UEs with enough RF/Baseband capability to monitor whole system bandwidth (e.g., cell phones, high end MTC devices).
  • the second configuration is generally for low-end MTC devices and normal UEs with enough RF/Baseband capability but worked in power limited condition.
  • the third configuration is generally for NB-IoT (Narrow Band-Internet of Thing) UEs which pool RF/Baseband capability and can only perform transmission/reception on a narrow band (e.g., 1.4 MHz).
  • the last configuration is generally defined as a new RAT (Radio Access Technology).
  • low-end MTC devices will only worked on the second configuration, and NB-IoT devices will work only on the third configuration.
  • the UE will only change RA configuration when it enters the power limited state (e.g., cell edge or even far away).
  • the average random access latency could be reduced due to early start to monitor Msg4.
  • FIG. 7 A possible case for such benefit is shown in FIG. 7 .
  • the processing delay is a fixed period
  • the UE could start to receive Msg4 earlier owing to early Msg3 transmission.
  • two possibilities for monitoring Msg4 are shown in FIG. 7 .
  • the UE may expect either TTI format if the TTI length information is not be carried in scheduling control signal. Otherwise, the UE may expect multiple possibilities of TTI length.
  • the network can more flexibly adjust resource allocation.
  • the TTI length for Msg3 is fixed.
  • LTE system could only schedule radio resource in PRB level, while NR may be able to schedule in symbol level.
  • a UE needs to derive TTI information (e.g., TTI length, numerology) for transmitting Msg3 on air interface.
  • TTI information e.g., TTI length, numerology
  • possible candidates for the UE are proposed to obtain such information.
  • One or multiple solutions can be applied in a NR system.
  • Msg3 transmission is scheduled by UL grant field in RAR.
  • a RAR is a response for a preamble transmitted at a Msg1 transmission opportunity from UE(s).
  • the format of RAR in LTE is shown in FIG. 8 .
  • the Msg3 transmission is scheduled according to UL (Uplink) grant field in the RAR.
  • additional TTI information is added into RAR for scheduling Msg3.
  • the new TTI information can be a new field in RAR or a new field in Msg2 for a specific preamble or added into UL grant field.
  • FIG. 9 A possible exemplary embodiment is shown in FIG. 9 .
  • the TTI information is also carried in Msg2 similar to Solution 1.
  • the Msg2 may include multiple RARs. And sub-header of a RAR will indicate the RAR is for which preamble.
  • the TTI length has limited choices, there may be no need to repeatedly include the redundant information.
  • a possible example is shown in FIG. 10 .
  • the TTI information 1 could be provided to preamble set 1 (e.g., rapid 0 ⁇ 20), and the TTI information 2 could be provided to preamble set 2 (e.g., rapid 21 ⁇ 40).
  • the TTI information carried in a common field will be applied to UEs performed different Msg1 transmission (e.g., different preamble).
  • the different Msg1 transmissions are differentiable by receiving side in Code domain and/or Time domain and/or Frequency domain.
  • the common field(s) may be carried as control element.
  • the common field(s) may be carried as part of MAC (sub-)header, as data (e.g., RRC configuration), or in control signal (e.g., PDCCH signal) for scheduling Msg2.
  • a UE could select one of them to apply to Msg3 transmission.
  • the UE could select common field based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.).
  • the UE could also select common field based on service types (e.g., URLLC, eMBB, delay sensitive, . . . ). For example, if the UE triggers RA for transmitting a specific service type data (e.g., URLLC service type), then the UE could select common field for the specific service type.
  • a specific service type data e.g., URLLC service type
  • the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data.
  • the service type indication may be used in multiplexing procedure. For instance, the UE may not multiplex data with different service type indications into a TB for transmission.
  • the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field), or based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC).
  • header field of the data e.g., RLC header field, PDCP field
  • user plane protocol type/category e.g., category 1 maps to URLLC.
  • the UE could select common field for URLLC service type.
  • higher layer e.g., NAS layer, application layer, RRC layer
  • lower layer e.g., MAC, PHY
  • the UE could select common field based on the service type indicated by the service indication.
  • the UE selects common field based on random access purpose (e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.). And the random access purpose may be indicated by higher layer (e.g. NAS, RRC, application layer) in the UE.
  • random access purpose e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • higher layer e.g. NAS, RRC, application layer
  • the UE selects common field based on potential Msg3 size. For example, if the pending available data in a UE larger than a threshold when a UE is performing RA, the UE selects common field for potential message size larger than the threshold.
  • the UE selects common field based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information), based on UE priority (e.g., access class, etc.) provided from network or UE subscription, or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . . . ).
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information
  • UE priority e.
  • Msg3 could include data from a specific (set of) LC or RB (e.g. URLLC type RB, CCCH, . . . ), the UE could select common field related to the LC or RB based on the UE's configuration (e.g., association between LC/RB and random access configuration, association between LC/RB and service configuration, association between LC/RB and transport channel configuration, etc).
  • Msg3 could include a special control element/special message
  • the UE could select common field related to the special control element/message.
  • the UE will select another common field if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects common field based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select common field based on whether priority 2 is over a threshold or not.
  • the UE selects common field based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive TTI length for Msg3 transmission through a broadcast message (e.g., system information(s), MIB, etc.) from a network (e.g., gNB, base station, TRP, etc.). If multiple TTI information for Msg3 transmission are included in the broadcast message, a UE could select one of them to apply to Msg3 transmission.
  • a broadcast message e.g., system information(s), MIB, etc.
  • a network e.g., gNB, base station, TRP, etc.
  • the UE selects TTI information in the broadcast message based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.). For example, if the UE triggers RA for transmitting a specific service type data (e.g., URLLC service type), then the UE could select TTI information in the broadcast message for the specific service type. Moreover, the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data.
  • Msg1 transmission e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.
  • a specific service type data e.g., URLLC service type
  • the UE
  • the service type indication may be used in multiplexing procedure. For instance, the UE may not multiplex data with different service type indications into a TB for transmission. Alternatively, the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field). The UE may also understand the data belonging to which service type based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC). As another example, if the UE triggers RA when the UE has registered/authorized for URLLC service type, the UE could select TTI information in the broadcast message for URLLC service type.
  • higher layer e.g., NAS layer, application layer, RRC layer
  • lower layer e.g., MAC, PHY
  • the UE could select TTI information in the broadcast message based on the service type indicated by the service indication.
  • the UE selects TTI information in the broadcast message based on random access purpose (e.g., request broadcast message, paging, positioning, location update, control plane establishment, beam recovery, etc.).
  • random access purpose e.g., request broadcast message, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • the random access purpose may be indicated by higher layer (e.g., NAS, RRC, application layer) in the UE.
  • the UE selects TTI information in the broadcast message based on potential Msg3 size. For example, if the pending available data in the UE larger than a threshold when the UE is performing RA, the UE selects TTI information in the broadcast message for potential message size larger than the threshold.
  • the UE selects TTI information in the broadcast message based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information), based on UE priority provided from network or UE subscription (e.g., access class, etc.), or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . . . ).
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information
  • Msg3 could include data from a specific or a set of LC or RB (e.g., URLLC type RB, CCCH, . . . ), the UE could select TTI information in the broadcast message related to the LC or RB based on the UE's configuration.
  • Msg3 could include a special control element/special message
  • the UE could select TTI information in the broadcast message related to the special control element/message.
  • the UE will select another TTI information if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects TTI information in the broadcast message based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select TTI information in the broadcast message based on whether priority 2 is over a threshold or not.
  • the UE selects TTI information in the broadcast message based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive TTI length for Msg3 transmission through a dedicated message (e.g., RRC reconfiguration message, paging message, PDCCH for initiating RA, . . . ) from a network. If multiple TTI information for Msg3 transmission are (implicitly or explicitly) included in the dedicated message, a UE could select one of them to apply to Msg3 transmission.
  • a dedicated message e.g., RRC reconfiguration message, paging message, PDCCH for initiating RA, . . .
  • the UE selects TTI information in dedicated message based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.). For example, if the UE triggers RA for transmitting a specific service type data (e.g., URLLC service type), then the UE could select TTI information in dedicated message for the specific service type. Moreover, the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data. The service type indication may be used in multiplexing procedure.
  • Msg1 transmission e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.
  • a specific service type data e.g
  • the UE may not multiplex data with different service type indications into a TB for transmission.
  • the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field)), or based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC).
  • header field of the data e.g., RLC header field, PDCP field
  • user plane protocol type/category e.g., category 1 maps to URLLC
  • the UE could select TTI information in the dedicated message for URLLC service type.
  • higher layer e.g., NAS layer, application layer, RRC layer
  • lower layer e.g., MAC, PHY
  • the UE selects TTI information in the dedicated message based on random access purpose (e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.).
  • random access purpose e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • the random access purpose may be indicated by higher layer (e.g., NAS, RRC, application layer) in the UE.
  • the UE selects TTI information in the dedicated message based on potential Msg3 size. For example, if the pending available data in the UE larger than a threshold when the UE is performing RA, the UE selects TTI information in the dedicated message for potential message size larger than the threshold.
  • the UE selects TTI information in the dedicated message based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information), based on UE priority provided from network or UE subscription (e.g., access class, etc.), or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . . . ).
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and TTI information
  • Msg3 could include data from a specific (set of) LC or RB (e.g. URLLC type RB, CCCH, . . . ), the UE could select TTI information in dedicated message related to the LC or RB based on the UE's configuration.
  • Msg3 could include a special control element/special message
  • the UE could select TTI information in the dedicated message related to the special control element/message.
  • the UE will select another TTI information if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects TTI information in the dedicated message based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select TTI information in dedicated message based on whether priority 2 is over a threshold or not.
  • the UE selects TTI information in the dedicated message based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive TTI length for Msg3 transmission based on implicit information of Msg2.
  • a UE derives TTI length based on TTI length used by Msg2.
  • the TTI duration of Msg3 transmission may be N times of TTI duration of Msg2.
  • N value can be integer or decimal.
  • the N value may be obtained by the UE based on one or multiple solutions mentioned above. For example, the UE may obtain the N value through the broadcast message from a network. And the UE could overwrite the N value provided in the broadcast message, if the UE receives another N value in a dedicated message.
  • a UE derives TTI length based on frequency carrier used by Msg2.
  • Each frequency carrier may have corresponding different TTI lengths.
  • the corresponding TTI information may be predefined and/or provided through system information and/or dedicated RRC message.
  • the fixed gap period is designed for covering UE's Msg2/3 processing time (e.g., decode, (de-)multiplexing transport block).
  • some possible methods can bring benefits to reduce such fixed gap period. For example, if short TTI is applied to both Msg2/Msg3 transmissions as FIG. 11 , the minimum of the fixed gap between Msg2 and Msg3 can be set to short TTI. Otherwise, the minimum gap could only be set to normal sub-frame length like without short TTI case.
  • Msg3 transmission is scheduled by UL grant field in RAR.
  • a RAR is a response for a preamble transmitted at a Msg1 transmission opportunity from UE(s).
  • the format of RAR in LTE is shown in FIG. 8 .
  • the Msg3 transmission is scheduled according to UL (Uplink) grant field in the RAR.
  • additional information is added into RAR for adjusting Msg3 start timing offset.
  • the additional information can be a new field in RAR or a new field in Msg2 for a specific preamble or added into UL grant field.
  • the Msg3 start timing offset is also carried in Msg2 similar to Solution 1.
  • the Msg2 may include multiple RARs.
  • MAC sub-header of a RAR will indicate the RAR is for which preamble.
  • TTI length since the TTI length has limited choices, there may be no need to repeatedly include the redundant information.
  • the Msg3 start timing offset carried in a common field will be applied to UEs performed different Msg1 transmission (e.g., different preamble).
  • the different Msg1 transmissions are differentiable by receiving side in Code domain and/or Time domain and/or Frequency domain.
  • the common field(s) may be carried as control element.
  • the common field(s) may be carried as part of MAC (sub-)header, as data (e.g., RRC configuration), or in control signal (e.g., PDCCH signal) for scheduling Msg2.
  • a UE could select one of them to apply to Msg3 transmission.
  • the UE could select common field based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.).
  • the UE could also select common field based on service types (e.g., URLLC, eMBB, delay sensitive, . . . ). For example, if the UE triggers RA for transmitting a specific service type data (e.g., URLLC service type), then the UE could select common field for the specific service type.
  • a specific service type data e.g., URLLC service type
  • the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data.
  • the service type indication may be used in multiplexing procedure. For instance, the UE may not multiplex data with different service type indications into a TB for transmission.
  • the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field), or based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC).
  • header field of the data e.g., RLC header field, PDCP field
  • user plane protocol type/category e.g., category 1 maps to URLLC.
  • higher layer e.g., NAS layer, application layer, RRC layer
  • lower layer e.g., MAC, PHY
  • the UE could select common field based on the service type indicated by the service indication.
  • the UE selects common field based on random access purpose (e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.). And the random access purpose may be indicated by higher layer (e.g., NAS, RRC, application layer) in the UE.
  • random access purpose e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • higher layer e.g., NAS, RRC, application layer
  • the UE selects common field based on potential Msg3 size. For example, if the pending available data in a UE larger than a threshold when a UE is performing RA, the UE selects common field for potential message size larger than the threshold.
  • the UE selects common field based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg3 start timing offset), based on UE priority (e.g., access class, etc.) provided from network or UE subscription, or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . . . ).
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg3 start timing offset
  • Msg3 could include data from a specific (set of) LC or RB (e.g. URLLC type RB, CCCH, . . . ), the UE could select common field related to the LC or RB based on the UE's configuration (e.g., association between LC/RB and random access configuration, association between LC/RB and service configuration, association between LC/RB and transport channel configuration, etc.).
  • Msg3 could include a special control element/special message
  • the UE could select common field related to the special control element/message.
  • the UE will select another common field if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects common field based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select common field based on whether priority 2 is over a threshold or not.
  • the UE selects common field based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive Msg3 start timing offset for Msg3 transmission through a broadcast message (e.g., system information(s), MIB, etc.) from a network (e.g., gNB, base station, TRP, etc.). If multiple Msg3 start timing offsets for Msg3 transmission are included in the broadcast message, a UE could select one of them to apply to Msg3 transmission.
  • a broadcast message e.g., system information(s), MIB, etc.
  • a network e.g., gNB, base station, TRP, etc.
  • the UE selects Msg3 start timing offsets in the broadcast message based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc.), or based on service types (e.g., URLLC, eMBB, delay sensitive, . . . ).
  • service types e.g., URLLC, eMBB, delay sensitive, . . .
  • the UE could select Msg3 start timing offset in the broadcast message for the specific service type.
  • the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data.
  • the service type indication may be used in multiplexing procedure. For instance, the UE may not multiplex data with different service type indications into a TB for transmission. Alternatively, the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field). The UE may also understand the data belonging to which service type based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC). As another example, if the UE triggers RA when the UE has registered/authorized for URLLC service type, the UE could select Msg3 start timing offset in the broadcast message for URLLC service type.
  • a higher layer e.g., NAS layer, application layer, RRC layer
  • a service indication e.g., MAC, PHY
  • the UE could select Msg3 start timing offset in the broadcast message based on the service type indicated by the service indication.
  • the UE selects Msg3 start timing offset in the broadcast message based on random access purpose (e.g., request broadcast message, paging, positioning, location update, control plane establishment, beam recovery, etc.).
  • random access purpose e.g., request broadcast message, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • the random access purpose may be indicated by higher layer (e.g., NAS, RRC, application layer) in the UE.
  • the UE selects Msg3 start timing offset in the broadcast message based on potential Msg3 size. For example, if the pending available data in the UE larger than a threshold when the UE is performing RA, the UE selects Msg3 start timing offset in the broadcast message for potential message size larger than the threshold.
  • the UE selects Msg3 start timing offset in the broadcast message based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg3 start timing offset), based on UE priority provided from network or UE subscription (e.g., access class, etc.), or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . .
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg
  • Msg3 could include data from a specific or a set of LC or RB (e.g., URLLC type RB, CCCH, . . . ), the UE could select Msg3 start timing offset in the broadcast message related to the LC or RB based on the UE's configuration.
  • Msg3 could include a special control element/special message
  • the UE could select Msg3 start timing offset in the broadcast message related to the special control element/message.
  • the UE will select another Msg3 start timing offset if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects Msg3 start timing offset in the broadcast message based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select Msg3 start timing offset in the broadcast message based on whether priority 2 is over a threshold or not.
  • the UE selects Msg3 start timing offset in the broadcast message based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive Msg3 start timing offset for Msg3 transmission through a dedicated message (e.g., RRC reconfiguration message, paging message, PDCCH for initiating RA, . . . ) from a network. If multiple Msg3 start timing offsets for Msg3 transmission are (implicitly or explicitly) included in the dedicated message, a UE could select one of them to apply to Msg3 transmission.
  • a dedicated message e.g., RRC reconfiguration message, paging message, PDCCH for initiating RA, . . .
  • the UE selects Msg3 start timing offset in dedicated message based on its Msg1 transmission (e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc), or based on service types (e.g., URLLC, eMBB, delay sensitive, . . . ).
  • Msg1 transmission e.g., preamble group set in RA configuration used by Msg1, PRACH resource set in RA configuration used by Msg1, Msg1 length or format, RA configuration used by Msg1, etc
  • service types e.g., URLLC, eMBB, delay sensitive, . . .
  • the UE may understand the data belonging to which service type based on a service type indication (similar to logical channel priority) in configuration of logical channel/RB having available data.
  • the service type indication may be used in multiplexing procedure. For instance, the UE may not multiplex data with different service type indications into a TB for transmission.
  • the UE may understand the data belonging to which service type based on header field of the data (e.g., RLC header field, PDCP field)), or based on delivering user plane protocol type/category (e.g., category 1 maps to URLLC).
  • the UE could select Msg3 start timing offset in the dedicated message for URLLC service type.
  • higher layer e.g., NAS layer, application layer, RRC layer
  • lower layer e.g., MAC, PHY
  • the UE selects Msg3 start timing offset in the dedicated message based on random access purpose (e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.).
  • random access purpose e.g., request system information, paging, positioning, location update, control plane establishment, beam recovery, etc.
  • the random access purpose may be indicated by higher layer (e.g., NAS, RRC, application layer) in the UE.
  • the UE selects Msg3 start timing offset in the dedicated message based on potential Msg3 size. For example, if the pending available data in the UE larger than a threshold when the UE is performing RA, the UE selects Msg3 start timing offset in the dedicated message for potential message size larger than the threshold.
  • the UE selects Msg3 start timing offset in the dedicated message based on its DL measurement, based on connection establishment cause (e.g., emergency call, mo-data, mt-data, . . . ), based on its current power ramping result (e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg3 start timing offset), based on UE priority provided from network or UE subscription (e.g., access class, etc), or based on Msg3 contents (e.g., which type control element could be included, BSR reporting for which LCG or which RB/LC, data from which user plane protocol stock, data from which radio bearer, data from which logical channel, . .
  • connection establishment cause e.g., emergency call, mo-data, mt-data, . . .
  • current power ramping result e.g., ramping over threshold times or threshold power, changing based on mapping table between ramping steps and Msg3
  • Msg3 could include data from a specific (set of) LC or RB (e.g., URLLC type RB, CCCH, . . . ), the UE could select Msg3 start timing offset in dedicated message related to the LC or RB based on the UE's configuration.
  • Msg3 could include a special control element/special message
  • the UE could select Msg3 start timing offset in the dedicated message related to the special control element/message.
  • the UE will select another Msg3 start timing offset if the Msg3 doesn't include the special control element and/or the special message (e.g., RRC message).
  • the UE selects Msg3 start timing offset in the dedicated message based on highest priority of radio bearers having available data. For example, the UE has available data belonging to radio bearer with priority 2 and priority 8 when the UE is performing RA. The UE could select Msg3 start timing offset in dedicated message based on whether priority 2 is over a threshold or not.
  • the UE selects Msg3 start timing offset in the dedicated message based on highest priority of logical channels having available data, or based on which user plane protocol stock (e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . . ) performing the random access.
  • user plane protocol stock e.g., URLLC or eMBB type user plane protocol, protocol stock category/index 1 or 2, . . .
  • a UE could derive Msg3 start timing offset for Msg3 transmission based on implicit information of Msg2.
  • a UE derives Msg3 start timing offset based on start timing offset used by Msg2.
  • the Msg3 start timing offset of Msg3 transmission may be N times of start timing offset of Msg2.
  • N value can be integer or decimal.
  • the N value may be obtained by the UE based on one or multiple solutions mentioned above. For example, the UE may obtain the N value through the broadcast message from a network. And the UE could overwrite the N value provided in the broadcast message, if the UE receives another N value in a dedicated message.
  • a UE derives Msg3 start timing offset based on frequency carrier used by Msg2.
  • Each frequency carrier may have corresponding different Msg3 start timing offsets.
  • the corresponding Msg3 start timing offset may be predefined and/or provided through system information and/or dedicated RRC message.
  • the Msg3 start timing offset can be derived through the solution 1 to 5 mentioned above or combination of those solutions, while Msg3 start timing offset and TTI information of Msg3 can apply the same or different solutions.
  • the Msg3 start timing offset can be indicated in TTI duration, numerology, symbol, slot, microsecond, millisecond or N times of periodicity of periodic behavior. N can be an integer or a decimal number.
  • FIG. 12 is a flow chart 1200 according to one exemplary embodiment from the perspective of a UE.
  • the UE receives a dedicated message from a network to set a TTI duration of Msg3 transmission and/or a start timing offset for Msg3 transmission.
  • the UE transmits a Msg1 to the network.
  • the UE receives a Msg2 from the network in response to the Msg1.
  • the UE transmits a Msg3 to the network according to the TTI duration and/or the start timing offset.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to receive a dedicated message from a network to set a TTI duration of Msg3 transmission and/or a start timing offset for Msg3 transmission, (ii) to transmit a Msg1 to the network, (iii) to receive a Msg2 from the network in response to the Msg1, and (iv) to transmit a Msg3 to the network according to the TTI duration and/or the start timing offset.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 13 is a flow chart 1300 according to one exemplary embodiment from the perspective of a UE.
  • the UE receives a broadcast message from a network to set TTI duration of Msg3.
  • the UE transmits a Msg1 to the network.
  • the UE receives a Msg2 from the network in response to the Msg1.
  • the UE transmits a Msg3 to the network according to the TTI duration of Msg3.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to receive a broadcast message from a network to set TTI duration of Msg3, (ii) to transmit a Msg1 to the network, (iii) to receive a Msg2 from the network in response to the Msg1, and (iv) to transmit a Msg3 to the network according to the TTI duration of Msg3.
  • the CPU 308 can 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 according to one exemplary embodiment from the perspective of a UE.
  • the UE transmits a preamble to a network.
  • the UE receives a Msg2 from the network in response to the Msg1, wherein the Msg2 contains a TTI information of Msg3 transmission and/or a start timing offset of Msg3 transmission.
  • the TTI information of Msg3 transmission is indicated in a common field for multiple RARs in the Msg2.
  • the TTI information of Msg3 is indicated in a RAR in response to the Msg1 transmission.
  • the start timing offset of Msg3 is indicated in a common field for multiple RARs in the Msg2. In another embodiment, the start timing offset of Msg3 is indicated in a RAR in response to the Msg1 transmission.
  • the UE transmits a Msg3 to the network according to the TTI information of Msg3 and/or the start timing offset of Msg3.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to transmit a preamble to a network, (ii) to receive a Msg2 from the network in response to the preamble, wherein the Msg2 contains a TTI duration of Msg3 transmission and/or a start timing offset of Msg3 transmission, and (iii) to perform a Msg3 transmission to the network according to the TTI information of Msg3 and/or the start timing offset of Msg3.
  • the CPU 308 can 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 according to one exemplary embodiment from the perspective of a UE.
  • the UE transmits a Msg1 to a network.
  • the UE receives a Msg2 from the network in response to the Msg1.
  • the UE transmits a Msg3 to the network according to a TTI duration of the Msg3, wherein the TTI duration of the Msg3 is decided based on a TTI duration of Msg2.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to transmit a Msg1 to a network, (ii) to receive a Msg2 from the network in response to the Msg1, and (iii) to transmit a Msg3 to the network according to a TTI duration of the Msg3, wherein the TTI duration of the Msg3 is decided based on a TTI duration of Msg2.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 16 is a flow chart 1600 according to one exemplary embodiment from the perspective of a UE.
  • the UE receives a dedicated message from a network to set a start timing offset for Msg3 transmission.
  • the UE transmits a Msg1 to the network.
  • the UE receives a Msg2 from the network in response to the Msg1.
  • the UE transmits a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to receive a dedicated message from a network to set a start timing offset for Msg3 transmission, (ii) to transmit a Msg1 to the network, (iii) to receive a Msg2 from the network in response to the Msg1, and (iv) to transmit a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 17 is a flow chart 1700 according to one exemplary embodiment from the perspective of a UE.
  • the UE receives a broadcast message from a network to set a start timing offset for Msg3 transmission.
  • the UE transmits a Msg1 to the network.
  • the UE receives a Msg2 from the network in response to the Msg1.
  • the UE transmits a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to receive a broadcast message from a network to set a start timing offset for Msg3 transmission, (ii) to transmit a Msg1 to the network, (iii) to receive a Msg2 from the network in response to the Msg1, and (iv) to transmit a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 18 is a flow chart 1800 according to one exemplary embodiment from the perspective of a UE.
  • the UE transmits a Msg1 to the network.
  • the UE receives a Msg2 from the network in response to the Msg1, wherein the Msg2 contains a start timing offset for Msg3 transmission.
  • the UE transmits a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to transmit a Msg1 to the network, (iii) to receive a Msg2 from the network in response to the Msg1, (ii) to receive a Msg2 from the network in response to the Msg1, wherein the Msg2 contains a start timing offset for Msg3 transmission, and (iii) to transmit a Msg3 to the network after the start timing offset passes from when the UE received the Msg2.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • FIG. 19 is a flow chart 1900 according to one exemplary embodiment from the perspective of a UE.
  • the UE receives a message from a network, wherein the message includes a TTI information of Msg3.
  • the UE transmits a preamble to a network.
  • the UE receives a Msg2 from the network in response to the preamble.
  • the TTI information of Msg3 is indicated in a common field for multiple RARs in the Msg2.
  • the TTI information of Msg3 is indicated in a RAR in response to the Msg1 transmission.
  • the UE performs a Msg3 transmission to the network according to the TTI information of Msg3.
  • the device 300 includes a program code 312 stored in the memory 310 .
  • the CPU 308 could execute program code 312 to enable the UE (i) to receive a message from a network, wherein the message includes a TTI information of Msg3, (ii) to transmit a preamble to a network, (ii) to receive a Msg2 from the network in response to the preamble, and (iii) to perform a Msg3 transmission to the network according to the TTI information of Msg3.
  • the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.
  • the UE selects a TTI information of Msg3 if there are multiple TTI information of Msg3 in the dedicated message, the broadcast message, or the Msg2. Furthermore, the TTI information of Msg3 could be included in a RAR in response to Msg1 or in a common field for multiple RARs in a Msg2.
  • the UE selects a TTI information of Msg3 if there are multiple start timing offsets for Msg3 transmission in the dedicated message, the broadcast message, or the Msg2. Furthermore, the start timing offset of Msg3 could be included in a RAR in response to Msg1 or in a common field for multiple RARs in a Msg2.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
US15/663,674 2016-07-28 2017-07-28 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system Abandoned US20180035470A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/663,674 US20180035470A1 (en) 2016-07-28 2017-07-28 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system
US16/052,505 US11291052B2 (en) 2016-07-28 2018-08-01 Method and apparatus for improving Msg3 transmission of random access procedure in a wireless communication system
US17/673,985 US20220174747A1 (en) 2016-07-28 2022-02-17 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662367875P 2016-07-28 2016-07-28
US15/663,674 US20180035470A1 (en) 2016-07-28 2017-07-28 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/052,505 Division US11291052B2 (en) 2016-07-28 2018-08-01 Method and apparatus for improving Msg3 transmission of random access procedure in a wireless communication system

Publications (1)

Publication Number Publication Date
US20180035470A1 true US20180035470A1 (en) 2018-02-01

Family

ID=59485287

Family Applications (3)

Application Number Title Priority Date Filing Date
US15/663,674 Abandoned US20180035470A1 (en) 2016-07-28 2017-07-28 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system
US16/052,505 Active US11291052B2 (en) 2016-07-28 2018-08-01 Method and apparatus for improving Msg3 transmission of random access procedure in a wireless communication system
US17/673,985 Abandoned US20220174747A1 (en) 2016-07-28 2022-02-17 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system

Family Applications After (2)

Application Number Title Priority Date Filing Date
US16/052,505 Active US11291052B2 (en) 2016-07-28 2018-08-01 Method and apparatus for improving Msg3 transmission of random access procedure in a wireless communication system
US17/673,985 Abandoned US20220174747A1 (en) 2016-07-28 2022-02-17 Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system

Country Status (7)

Country Link
US (3) US20180035470A1 (zh)
EP (1) EP3277042B1 (zh)
JP (2) JP2018019403A (zh)
KR (1) KR101967540B1 (zh)
CN (1) CN107666722A (zh)
ES (1) ES2923517T3 (zh)
TW (1) TWI675599B (zh)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10051500B2 (en) * 2014-07-23 2018-08-14 Samsung Electronics Co., Ltd. Method and apparatus for generating and transmitting power headroom report in mobile communication system
US20180242354A1 (en) * 2015-08-21 2018-08-23 Ntt Docomo, Inc. User terminal, radio base station, and wireless communication method
US20180343682A1 (en) * 2016-02-02 2018-11-29 Huawei Technologies Co., Ltd. Tti configuration method, device, and system
US20190059108A1 (en) * 2017-01-24 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Control plane latency reduction in a wireless communications network
US20190110234A1 (en) * 2016-11-04 2019-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Identifying a beam for accessing a target cell of a wireless hanover
US20190141515A1 (en) * 2017-04-28 2019-05-09 Lg Electronics Inc. Method for transmitting data according to edt
US20190261422A1 (en) * 2018-02-16 2019-08-22 Qualcomm Incorporated Random access timeline and timing adjustment techniques
US10419259B1 (en) * 2018-04-16 2019-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Time-domain table for PUSCH and Msg3
CN110351879A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 一种通信方法及装置
KR20200003927A (ko) * 2018-04-16 2020-01-10 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Pusch 및 msg3을 위한 시간-도메인 표
WO2020024863A1 (zh) * 2018-07-31 2020-02-06 华为技术有限公司 一种连接建立方法及装置
WO2020056639A1 (en) * 2018-09-19 2020-03-26 Nokia Shanghai Bell Co., Ltd. Methods, devices and computer readable medium for resource information for early data transmission
CN111264087A (zh) * 2018-10-01 2020-06-09 联发科技（新加坡）私人有限公司 移动通信中用于两步骤RACH之MsgB的多工、寻址以及HARQ
US10863484B2 (en) 2017-01-09 2020-12-08 Qualcomm Incorporated Indication of random-access channel MSG3 resource duration via random-access channel MSG2
CN112997574A (zh) * 2019-05-06 2021-06-18 Oppo广东移动通信有限公司 随机接入的方法、终端设备和网络设备
CN113016221A (zh) * 2018-11-14 2021-06-22 中兴通讯股份有限公司 生成带有承载信息的随机接入信号
US11140707B2 (en) 2018-02-16 2021-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Time resource assignment signaling mechanism for MSG3 transmission
US11252644B2 (en) * 2017-12-11 2022-02-15 Beijing Xiaomi Mobile Software Co., Ltd. Method, device, user equipment and base station for use in shortening access delay
US11265840B2 (en) 2018-02-09 2022-03-01 Zte Corporation Data transmission and management for positioning mobile devices
US11297627B2 (en) * 2017-12-20 2022-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for low-latency transmission using shared SR-less resources
US11382049B2 (en) * 2017-09-20 2022-07-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
US11424810B2 (en) * 2017-08-18 2022-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for random access for beam failure recovery
US11470670B2 (en) 2018-02-12 2022-10-11 Datang Mobile Communications Equipment Co., Ltd. Beam failure recovery method and user equipment
WO2023185491A1 (zh) * 2022-03-30 2023-10-05 华为技术有限公司 随机接入方法及装置

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5454123B2 (ja) * 2009-12-16 2014-03-26 ソニー株式会社 ハンドオーバのための方法、端末装置及び無線通信システム
US10893550B2 (en) * 2017-03-11 2021-01-12 Qualcomm Incorporated Numerology dependent random access timing
WO2019157706A1 (en) * 2018-02-14 2019-08-22 Nokia Shanghai Bell Co., Ltd. Methods and apparatuses for prioritized random access during handover
US20200383137A1 (en) * 2018-02-23 2020-12-03 Lg Electronics Inc. Method for performing initial access in wireless communication system and apparatus therefor
GB2572336B (en) * 2018-03-26 2022-02-02 Samsung Electronics Co Ltd Improvements in and relating to random access in a telecommunication network
WO2019242382A1 (zh) * 2018-06-19 2019-12-26 Oppo广东移动通信有限公司 一种指示信道接入类型的方法、终端设备及网络设备
EP3815456A1 (en) * 2018-06-29 2021-05-05 Lenovo (Singapore) Pte. Ltd. Efficient rach behavior
CN110719647B (zh) * 2018-07-13 2021-08-20 维沃移动通信有限公司 一种随机接入方法、终端及网络设备
US20210352689A1 (en) * 2018-09-21 2021-11-11 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
EP4195853A1 (en) * 2018-09-27 2023-06-14 ZTE Corporation Methods, apparatus and systems for performing a random access procedure in a wireless communication
US11374677B2 (en) * 2019-04-12 2022-06-28 Qualcomm Incorporated Signaling of higher modulation order baseband capability
KR102422525B1 (ko) * 2019-06-03 2022-07-20 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 모바일-종료 조기 데이터 전송(mt-edt) 및 사전 구성된 업링크 리소스(pur)를 위한 방법 및 장치
KR20210007645A (ko) 2019-07-12 2021-01-20 엘지전자 주식회사 냉장고

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070268812A1 (en) * 2006-05-19 2007-11-22 Lg Electronics Inc. Method of configuring wireless resource for effective and efficient transmission in a wireless communication system
US20160366705A1 (en) * 2015-06-10 2016-12-15 Apple Inc. Random Access Procedures for Link Budget Constrained Wireless Devices
US20170111933A1 (en) * 2015-10-16 2017-04-20 Htc Corporation Device and Method of Handling Random Access Procedure

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1972079A4 (en) 2005-12-23 2015-07-08 Lg Electronics Inc METHOD AND PROCEDURES FOR UNSYNCHRONIZED, SYNCHRONIZED AND SYNCHRONIZED STAND-BY COMMUNICATIONS IN E-UTRA SYSTEMS
CN101321368B (zh) * 2007-06-08 2012-05-09 中兴通讯股份有限公司 一种多媒体广播组播业务中时分复用机制的实现方法
CN101426274B (zh) * 2007-10-29 2010-07-21 大唐移动通信设备有限公司 一种随机接入过程中资源分配位置的指示方法、***及装置
US8446859B2 (en) * 2008-02-01 2013-05-21 Lg Electronics Inc. Method for controlling uplink load in cell— FACH state
EP2263341B1 (en) * 2008-04-14 2018-09-19 Amazon Technologies, Inc. Method and apparatus for performing random access procedures
KR101618172B1 (ko) * 2009-04-30 2016-05-04 삼성전자주식회사 이동통신시스템의 ｒａｃｈ 채널 정보 전송 방법
EP2265077B1 (en) * 2009-06-18 2012-03-21 Panasonic Corporation Enhanced random access procedure for mobile communications
CN102740468A (zh) * 2011-04-02 2012-10-17 华为技术有限公司 分配信道资源的方法、基站设备、终端设备和通信***
CN102740407B (zh) * 2011-04-11 2017-08-29 中兴通讯股份有限公司 上行调度方法及***、终端及基站
US10123353B2 (en) * 2011-12-20 2018-11-06 Lg Electronics Inc. Method and apparatus for performing random access process in wireless communication system
US9590878B2 (en) * 2013-01-16 2017-03-07 Qualcomm Incorporated Channel state information and adaptive modulation and coding design for long-term evolution machine type communications
US10305626B2 (en) * 2013-04-05 2019-05-28 Qualcomm Incorporated Enhanced transmission time interval bundling design for machine type communications
US10051665B2 (en) * 2013-07-16 2018-08-14 Lg Electronics Inc. Method and apparatus for performing random access procedure in wireless communication system
US20170290008A1 (en) * 2014-09-08 2017-10-05 Interdigital Patent Holdings, Inc. Systems and Methods of Operating with Different Transmission Time Interval (TTI) Durations
JP2016072843A (ja) * 2014-09-30 2016-05-09 Kddi株式会社 基地局装置、通信方法、および通信システム
US9913263B2 (en) 2014-12-23 2018-03-06 Intel Corporation Association request for narrowband communications in a telecommunication environment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070268812A1 (en) * 2006-05-19 2007-11-22 Lg Electronics Inc. Method of configuring wireless resource for effective and efficient transmission in a wireless communication system
US20160366705A1 (en) * 2015-06-10 2016-12-15 Apple Inc. Random Access Procedures for Link Budget Constrained Wireless Devices
US20170111933A1 (en) * 2015-10-16 2017-04-20 Htc Corporation Device and Method of Handling Random Access Procedure

Cited By (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10952085B2 (en) 2014-07-23 2021-03-16 Samsung Electronics Co., Ltd. Method and apparatus for generating and transmitting power headroom report in mobile communication system
US11722914B2 (en) 2014-07-23 2023-08-08 Samsung Electronics Co., Ltd. Method and apparatus for generating and transmitting power headroom report in mobile communication system
US10051500B2 (en) * 2014-07-23 2018-08-14 Samsung Electronics Co., Ltd. Method and apparatus for generating and transmitting power headroom report in mobile communication system
US11405949B2 (en) * 2015-08-21 2022-08-02 Ntt Docomo, Inc. Terminal and radio communication method for performing a random access procedure
US20180242354A1 (en) * 2015-08-21 2018-08-23 Ntt Docomo, Inc. User terminal, radio base station, and wireless communication method
US20180343682A1 (en) * 2016-02-02 2018-11-29 Huawei Technologies Co., Ltd. Tti configuration method, device, and system
US11856466B2 (en) 2016-11-04 2023-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Wireless handover
US10484915B2 (en) * 2016-11-04 2019-11-19 Telefonaktiebolaget Lm Ericsson (Publ) Identifying a beam for accessing a target cell of a wireless handover
US11178587B2 (en) 2016-11-04 2021-11-16 Telefonaktiebolaget Lm Ericsson (Publ) Wireless hanover
US20190110234A1 (en) * 2016-11-04 2019-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Identifying a beam for accessing a target cell of a wireless hanover
US10863484B2 (en) 2017-01-09 2020-12-08 Qualcomm Incorporated Indication of random-access channel MSG3 resource duration via random-access channel MSG2
US10667299B2 (en) * 2017-01-24 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Control plane latency reduction in a wireless communications network
US20190059108A1 (en) * 2017-01-24 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Control plane latency reduction in a wireless communications network
US20190141515A1 (en) * 2017-04-28 2019-05-09 Lg Electronics Inc. Method for transmitting data according to edt
US10932121B2 (en) * 2017-04-28 2021-02-23 Lg Electronics Inc. Method for transmitting data according to EDT
US11812502B2 (en) 2017-04-28 2023-11-07 Lg Electronics Inc. Method for transmitting data according to EDT
US11424810B2 (en) * 2017-08-18 2022-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for random access for beam failure recovery
US11664875B2 (en) 2017-08-18 2023-05-30 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for random access for beam failure recovery
US11923947B2 (en) 2017-08-18 2024-03-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for random access for beam failure recovery
US11382049B2 (en) * 2017-09-20 2022-07-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
US11252644B2 (en) * 2017-12-11 2022-02-15 Beijing Xiaomi Mobile Software Co., Ltd. Method, device, user equipment and base station for use in shortening access delay
US11297627B2 (en) * 2017-12-20 2022-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for low-latency transmission using shared SR-less resources
AU2022201231B2 (en) * 2018-02-09 2023-08-10 Zte Corporation Data transmission and management for positioning mobile devices
US11265840B2 (en) 2018-02-09 2022-03-01 Zte Corporation Data transmission and management for positioning mobile devices
US11470670B2 (en) 2018-02-12 2022-10-11 Datang Mobile Communications Equipment Co., Ltd. Beam failure recovery method and user equipment
US11140707B2 (en) 2018-02-16 2021-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Time resource assignment signaling mechanism for MSG3 transmission
US10959268B2 (en) * 2018-02-16 2021-03-23 Qualcomm Incorporated Random access timeline and timing adjustment techniques
US20190261422A1 (en) * 2018-02-16 2019-08-22 Qualcomm Incorporated Random access timeline and timing adjustment techniques
EP3768028A4 (en) * 2018-04-04 2021-05-05 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
US20210022175A1 (en) * 2018-04-04 2021-01-21 Huawei Technologies Co., Ltd. Communications method and apparatus
CN110351879A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 一种通信方法及装置
EP4329217A3 (en) * 2018-04-04 2024-05-22 Huawei Technologies Co., Ltd. Communications method and apparatus
KR20200003927A (ko) * 2018-04-16 2020-01-10 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Pusch 및 msg3을 위한 시간-도메인 표
US10979269B2 (en) * 2018-04-16 2021-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Time-domain table for PUSCH and Msg3
KR102139239B1 (ko) 2018-04-16 2020-07-29 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Pusch 및 msg3을 위한 시간-도메인 표
US20190394075A1 (en) * 2018-04-16 2019-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Time-domain table for pusch and msg3
US10419259B1 (en) * 2018-04-16 2019-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Time-domain table for PUSCH and Msg3
WO2020024863A1 (zh) * 2018-07-31 2020-02-06 华为技术有限公司 一种连接建立方法及装置
WO2020056639A1 (en) * 2018-09-19 2020-03-26 Nokia Shanghai Bell Co., Ltd. Methods, devices and computer readable medium for resource information for early data transmission
CN111264087A (zh) * 2018-10-01 2020-06-09 联发科技（新加坡）私人有限公司 移动通信中用于两步骤RACH之MsgB的多工、寻址以及HARQ
CN113016221A (zh) * 2018-11-14 2021-06-22 中兴通讯股份有限公司 生成带有承载信息的随机接入信号
US11825524B2 (en) 2018-11-14 2023-11-21 Zte Corporation Generating random access signals with bearer information
CN112997574A (zh) * 2019-05-06 2021-06-18 Oppo广东移动通信有限公司 随机接入的方法、终端设备和网络设备
WO2023185491A1 (zh) * 2022-03-30 2023-10-05 华为技术有限公司 随机接入方法及装置

Also Published As

Publication number Publication date
EP3277042A1 (en) 2018-01-31
KR20180013808A (ko) 2018-02-07
US20220174747A1 (en) 2022-06-02
CN107666722A (zh) 2018-02-06
JP2020022205A (ja) 2020-02-06
US11291052B2 (en) 2022-03-29
JP6960443B2 (ja) 2021-11-05
TW201804855A (zh) 2018-02-01
TWI675599B (zh) 2019-10-21
KR101967540B1 (ko) 2019-04-09
US20180359785A1 (en) 2018-12-13
JP2018019403A (ja) 2018-02-01
ES2923517T3 (es) 2022-09-28
EP3277042B1 (en) 2022-05-25

Similar Documents

Publication Publication Date Title
US20220174747A1 (en) Method and apparatus for improving msg3 transmission of random access procedure in a wireless communication system
US10433343B2 (en) Method and apparatus for improving random access procedure in a wireless communication system
CN111511036B (zh) 针对***信息请求的随机接入程序的方法和设备
US11317446B2 (en) Method and apparatus of handling BWP inactivity timer during random access procedure in a wireless communication system
US10701734B2 (en) Method and apparatus of selecting bandwidth part for random access (RA) procedure in a wireless communication system
US10701702B2 (en) Method and apparatus for transmission using Preconfigured Uplink Resources while in RRC idle or RRC inactive in a wireless communication system
US20210227566A1 (en) Method and apparatus of preventing bandwidth part misalignment in a wireless communication system
US10455531B2 (en) Method and apparatus for identifying uplink timing advance in a wireless communication system
US10506632B2 (en) Method and apparatus for monitoring physical downlink control channel (PDCCH) in a wireless communication system
EP3607801B1 (en) Apparatus and method for performing a random access procedure
US20150043489A1 (en) Method and apparatus for small cell enhancement in a wireless communication system

Legal Events

Date Code Title Description
AS Assignment

Owner name: ASUSTEK COMPUTER INC., TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHEN, WEI-YU;TSENG, LI-CHIH;REEL/FRAME:043136/0656

Effective date: 20170727

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: FINAL REJECTION MAILED

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

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

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

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION