IP Library › Granted Patent US 12,677,325
Granted Patent B2
US 12,677,325 · App. 18/353,599 · Granted Jul 7, 2026

Random access process in new radio

Inventors: Hyoungsuk Jeon (Centreville, VA); Esmael Hejazi Dinan (McLean, VA)
Assignee: Comcast Cable Communications, LLC
H04W74/0833H04W72/23H04W74/0836H04L5/001H04L5/0023H04L5/0048H04W74/0838
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,677,325
App. No.
18/353,599
Filed
Jul 17, 2023
Granted
Jul 7, 2026
Kind
B2
Examiner
DUONG, DUC T
Art Unit
2467
USPC
370/329
Abstract

Systems, apparatuses, and methods are described for wireless communications. Random access procedures may include various types of procedures, such as four-step or two-step random access procedures.

Claims (154)

1 . A method comprising:

transmitting, by a wireless device and as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

receiving, by the wireless device, a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmitting, based on the RAR type being the second RAR type, one or more transport blocks comprising the data.

2 . The method of claim 1 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the transmitting one or more transport blocks, based on the RAR type being the second RAR type, is part of the four-step random access procedure.

3 . The method of claim 1 , wherein the transmitting one or more transport blocks based on the RAR type being the second RAR type is as a third step of a four-step random access procedure.

4 . The method of claim 1 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

5 . The method of claim 1 , wherein the MAC subheader is a single byte.

6 . The method of claim 1 , wherein the MAC packet data unit further comprises an RAR, the method further comprising:

determining, based on the MAC subheader, a size of the RAR as being the second size; and

decoding, based on the second size, the RAR.

7 . A method comprising:

transmitting, by a wireless device and as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

receiving, by the wireless device, a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmitting, based on the RAR type being the first RAR type, a second one or more transport blocks comprising second data.

8 . The method of claim 7 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

9 . The method of claim 7 , wherein the MAC subheader is a single byte.

10 . The method of claim 7 , wherein the MAC packet data unit further comprises an RAR, the method further comprising:

determining, based on the MAC subheader, a size of the RAR as being the first size; and

decoding, based on the first size, the RAR.

11 . A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

transmit, as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the second RAR type, one or more transport blocks comprising the data.

12 . The wireless device of claim 11 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit the one or more transport blocks, based on the RAR type being the second RAR type, as part of the four-step random access procedure.

13 . The wireless device of claim 11 , wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit the one or more transport blocks, based on the RAR type being the second RAR type, as a third step of a four-step random access procedure.

14 . The wireless device of claim 11 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

15 . The wireless device of claim 11 , wherein the MAC subheader is a single byte.

16 . The wireless device of claim 11 , wherein the MAC packet data unit further comprises an RAR, and wherein the instructions, when executed by the one or more processors, further cause the wireless device to:

determine, based on the MAC subheader, a size of the RAR as being the second size; and

decode, based on the second size, the RAR.

17 . A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

transmit, as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the first RAR type, a second one or more transport blocks comprising second data.

18 . The wireless device of claim 17 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

19 . The wireless device of claim 17 , wherein the MAC subheader is a single byte.

20 . The wireless device of claim 17 , wherein the MAC packet data unit further comprises an RAR, and wherein the instructions, when executed by the one or more processors, further cause the wireless device to:

determine, based on the MAC subheader, a size of the RAR as being the first size; and

decode, based on the first size, the RAR.

21 . A non-transitory computer-readable medium storing instructions that, when executed, configure a wireless device to:

transmit, as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the second RAR type, one or more transport blocks comprising the data.

22 . The non-transitory computer-readable medium of claim 21 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the instructions, when executed, configure the wireless device to transmit the one or more transport blocks, based on the RAR type being the second RAR type, as part of the four-step random access procedure.

23 . The non-transitory computer-readable medium of claim 21 , wherein the instructions, when executed, configure the wireless device to transmit the one or more transport blocks, based on the RAR type being the second RAR type, as a third step of a four-step random access procedure.

24 . The non-transitory computer-readable medium of claim 21 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

25 . The non-transitory computer-readable medium of claim 21 , wherein the MAC subheader is a single byte.

26 . The non-transitory computer-readable medium of claim 21 , wherein the MAC packet data unit further comprises an RAR, and wherein the instructions, when executed, further configure the wireless device to:

determine, based on the MAC subheader, a size of the RAR as being the second size; and

decode, based on the second size, the RAR.

27 . A non-transitory computer-readable medium storing instructions that, when executed, configure a wireless device to:

transmit, as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the first RAR type, a second one or more transport blocks comprising second data.

28 . The non-transitory computer-readable medium of claim 27 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

29 . The non-transitory computer-readable medium of claim 27 , wherein the MAC subheader is a single byte.

30 . The non-transitory computer-readable medium of claim 27 , wherein the MAC packet data unit further comprises an RAR, and wherein the instructions, when executed, further configure the wireless device to:

determine, based on the MAC subheader, a size of the RAR as being the first size; and

decode, based on the first size, the RAR.

31 . A method comprising:

receiving, by a base station as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

transmitting, by the base station, a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receiving a transmission that is based on the RAR type being the second RAR type, wherein the transmission comprises one or more transport blocks comprising the data.

32 . The method of claim 31 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the received transmission is part of the four-step random access procedure.

33 . The method of claim 31 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

34 . The method of claim 31 , wherein the MAC subheader is a single byte.

35 . A method comprising:

receiving, by a base station and as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

transmitting, by the base station, a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receiving a transmission that is based on the RAR type being the first RAR type, wherein the transmission comprises a second one or more transport blocks comprising second data.

36 . The method of claim 35 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

37 . The method of claim 35 , wherein the MAC subheader is a single byte.

38 . A base station comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the base station to:

receive, as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

transmit a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receive a transmission that is based on the RAR type being the second RAR type, wherein the transmission comprises one or more transport blocks comprising the data.

39 . The base station of claim 38 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the received transmission is part of the four-step random access procedure.

40 . The base station of claim 38 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

41 . The base station of claim 38 , wherein the MAC subheader is a single byte.

42 . A base station comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the base station to:

receive, as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

transmit a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receive a transmission that is based on the RAR type being the first RAR type, wherein the transmission comprises a second one or more transport blocks comprising second data.

43 . The base station of claim 42 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

44 . The base station of claim 42 , wherein the MAC subheader is a single byte.

45 . A non-transitory computer-readable medium storing instructions that, when executed, configure a base station to:

receive, as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

transmit a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receive a transmission that is based on the RAR type being the second RAR type, wherein the transmission comprises one or more transport blocks comprising the data.

46 . The non-transitory computer-readable medium of claim 45 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the received transmission is part of the four-step random access procedure.

47 . The non-transitory computer-readable medium of claim 45 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

48 . The non-transitory computer-readable medium of claim 45 , wherein the MAC subheader is a single byte.

49 . A non-transitory computer-readable medium storing instructions that, when executed, configure a base station to:

receive, as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

transmit a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

receive a transmission that is based on the RAR type being the first RAR type, wherein the transmission comprises a second one or more transport blocks comprising second data.

50 . The non-transitory computer-readable medium of claim 49 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

51 . The non-transitory computer-readable medium of claim 49 , wherein the MAC subheader is a single byte.

52 . A system comprising:

a base station; and

a wireless device configured to:

transmit, as part of a two-step random access procedure, a preamble and one or more transport blocks comprising data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the second RAR type, one or more transport blocks comprising the data,

wherein the base station is configured to transmit the MAC packet data unit.

53 . The system of claim 52 , wherein the second RAR type is associated with falling back from the two-step random access procedure to a four-step random access procedure, and wherein the wireless device is configured to transmit the one or more transport blocks, based on the RAR type being the second RAR type, as part of the four-step random access procedure.

54 . The system of claim 52 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

55 . The system of claim 52 , wherein the MAC subheader is a single byte.

56 . A system comprising:

a base station; and

a wireless device configured to:

transmit, as part of a two-step random access procedure, a preamble and a first one or more transport blocks comprising first data;

receive a media access control (MAC) packet data unit comprising a MAC subheader indicating a random access response (RAR) type of a plurality of RAR types, wherein the plurality of RAR types comprise:

a first RAR type associated with random access procedure success and that has a first size; and

a second RAR type associated with falling back from the two-step random access procedure and that has a second size different from the first size; and

transmit, based on the RAR type being the first RAR type, a second one or more transport blocks comprising second data,

wherein the base station is configured to transmit the MAC packet data unit.

57 . The system of claim 56 , wherein the MAC subheader comprises a field that is a single bit indicating the RAR type.

58 . The system of claim 56 , wherein the MAC subheader is a single byte.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068430/0400 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068430/0709 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068431/0174 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: OFINNO TECHNOLOGIES, LLC
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068431/0187 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068431/0217 →
Continuity (6)
Continuation 17333821 · May 28, 2021
Continuation 15933295 · Mar 22, 2018
Provisional Application 62475039 · Mar 22, 2017
Provisional Application 62475045 · Mar 22, 2017
Provisional Application 62475028 · Mar 22, 2017
Related Publication 20240090038A1 · Mar 14, 2024
References Cited (204)
US 7161952B1 · Herrmann · 2007 [cited by applicant]
US 7304970B1 · Ishikawa · 2007 [cited by applicant]
US 8229439B2 · Du · 2012 [cited by applicant]
US 8229494B1 · Kela et al. · 2012 [cited by applicant]
US 8451781B2 · Jeong et al. · 2013 [cited by applicant]
US 8494572B2 · Chen et al. · 2013 [cited by applicant]
US 9008050B2 · Feuersanger et al. · 2015 [cited by applicant]
US 9609499B2 · Shukla · 2017 [cited by applicant]
US 9781687B2 · Sen et al. · 2017 [cited by applicant]
US 9930700B2 · Wang et al. · 2018 [cited by applicant]
US 9942412B1 · Oroskar et al. · 2018 [cited by applicant]
US 10142980B2 · Radulescu et al. · 2018 [cited by applicant]
US 10397958B2 · Tsai · 2019 [cited by applicant]
US 11601988B2 · Qian et al. · 2023 [cited by applicant]
US 20090041246A1 · Kitazoe · 2009 [cited by applicant]
US 20090156194A1 · Meylan · 2009 [cited by applicant]
US 20090181710A1 · Pani et al. · 2009 [cited by applicant]
US 20100062799A1 · Ishii et al. · 2010 [cited by applicant]
US 20100322096A1 · Hsu et al. · 2010 [cited by applicant]
US 20110176513A1 · Yi et al. · 2011 [cited by applicant]
US 20120069788A1 · Shen et al. · 2012 [cited by applicant]
US 20120076075A1 · Komine et al. · 2012 [cited by applicant]
US 20120149422A1 · Ye et al. · 2012 [cited by applicant]
US 20130010711A1 · Larsson et al. · 2013 [cited by applicant]
US 20130058315A1 · Feuersanger et al. · 2013 [cited by applicant]
US 20130195048A1 · Ekpenyong et al. · 2013 [cited by applicant]
US 20130242730A1 · Pelletier et al. · 2013 [cited by applicant]
US 20140204843A1 · Larsson et al. · 2014 [cited by applicant]
US 20140334448A1 · Langereis et al. · 2014 [cited by applicant]
US 20150110072A1 · Kato et al. · 2015 [cited by applicant]
US 20150181546A1 · Freda et al. · 2015 [cited by applicant]
US 20150296542A1 · Heo et al. · 2015 [cited by applicant]
US 20150304957A1 · Noh et al. · 2015 [cited by applicant]
US 20160150445A1 · Sandhu et al. · 2016 [cited by applicant]
US 20160183203A1 · Larsson et al. · 2016 [cited by applicant]
US 20160212769A1 · Huang et al. · 2016 [cited by applicant]
US 20160262109A1 · Chen et al. · 2016 [cited by applicant]
US 20160330740A1 · Uchino et al. · 2016 [cited by applicant]
US 20160381715A1 · Lee · 2016 [cited by examiner]
US 20170006640A1 · Dinan · 2017 [cited by applicant]
US 20170034853A1 · Rune et al. · 2017 [cited by applicant]
US 20170041841A1 · Pedersen et al. · 2017 [cited by applicant]
US 20170257195A1 · Maaref · 2017 [cited by applicant]
US 20170290064A1 · Liu et al. · 2017 [cited by applicant]
US 20170332372A1 · Lee et al. · 2017 [cited by applicant]
US 20180054837A1 · Islam et al. · 2018 [cited by applicant]
US 20180103465A1 · Agiwal · 2018 [cited by examiner]
US 20180110074A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180115981A1 · Kim et al. · 2018 [cited by applicant]
US 20180116000A1 · Ly · 2018 [cited by examiner]
US 20180124830A1 · Lin et al. · 2018 [cited by applicant]
US 20180176962A1 · Wu · 2018 [cited by applicant]
US 20180205516A1 · Jung et al. · 2018 [cited by applicant]
US 20180220345A1 · Moon et al. · 2018 [cited by applicant]
US 20180220450A1 · Aiba · 2018 [cited by examiner]
US 20180234839A1 · Tenny et al. · 2018 [cited by applicant]
US 20180270869A1 · Tsai · 2018 [cited by examiner]
US 20180288746A1 · Zhang et al. · 2018 [cited by applicant]
US 20180310257A1 · Papasakellariou · 2018 [cited by applicant]
US 20180343682A1 · Tang et al. · 2018 [cited by applicant]
US 20190029062A1 · Wu · 2019 [cited by applicant]
US 20190075598A1 · Li et al. · 2019 [cited by applicant]
US 20190173740A1 · Zhang et al. · 2019 [cited by applicant]
US 20190174554A1 · Deenoo et al. · 2019 [cited by applicant]
US 20190380071A1 · Liu · 2019 [cited by examiner]
US 20200045742A1 · Suzuki et al. · 2020 [cited by applicant]
US 20200068616A1 · Qian et al. · 2020 [cited by applicant]
US 20200120713A1 · Yerramalli et al. · 2020 [cited by applicant]
US 20200252974A1 · Akkarakaran et al. · 2020 [cited by applicant]
US 20200314812A1 · Xu et al. · 2020 [cited by applicant]
US 20200367284A1 · Lei et al. · 2020 [cited by applicant]
US 20210058971A1 · MolavianJazi et al. · 2021 [cited by applicant]
US 20210227587A1 · Tsai et al. · 2021 [cited by applicant]
US 20210314979A1 · Agiwal et al. · 2021 [cited by applicant]
US 20210337597A1 · Yoshimura et al. · 2021 [cited by applicant]
US 20210352733A1 · Ma · 2021 [cited by applicant]
US 20210360660A1 · Cozzo et al. · 2021 [cited by applicant]
JP 5023150B2 · 2012 [cited by applicant]
3GPP TS 38.331 V15.2.1 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-1709897 3GPP TSG RAN WG1 NR Ad-hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: ZTE, Title: 4-step random access procedure. [cited by applicant]
R1-1710035 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: CATT, Title: Further details on NR 4-step RA Procedure. [cited by applicant]
R1-1710138 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Guangdong OPPO Mobile Telecom, Title: NR 4-Step Random Access Procedure. [cited by applicant]
R1-1710218 3GPP TSG-RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Mitsubishi Electric, Title: RACH transmission count. [cited by applicant]
R1-1710234 3GPP TSG-RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Fujitsu, Title: Discussion on 4-step RA procedure. [cited by applicant]
R1- 1710271 3GPP TSG RAN WG1 NR #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: LG Electronics, Title: RACH procedure. [cited by applicant]
R1-1710422 3GPP TSG RAN WG1 Ad hoc Meeting #2, Qingdao, P.R. China, Jun. 26-30, 2017, Source: AT&T, Title: DL Tx Beam Reporting in msg. 3. [cited by applicant]
R1-1710478 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Huawei, HiSilicon, Title: RACH procedures and resource configuration. [cited by applicant]
R1-1710513 3GPP TSG RAN WG1 NR Adhoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Intel Corporation, Title: 4-step PRACH procedures. [cited by applicant]
R1- 1710636 3GPP TSG RAN WG1 Meeting NR AH #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Samsung, Title: 4-step RACH procedure discussion. [cited by applicant]
R1-1710774 3GPP TSG RAN WG1 Meeting NR Adhoc, Qingdao, P.R. China, Jun. 27-30, 2017, Source: CMCC, Title: Discussion on RACH configuration. [cited by applicant]
R1-1710824 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: MediaTek Inc., Title: On 4-step RACH procedure. [cited by applicant]
R1-1710860 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Sony, Title: Considerations on 4-step RA Procedure. [cited by applicant]
R1-1710871 3GPP TSG-RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-20, 2017, Source: InterDigital Inc., Title: Multiple Msg1 transmissions for one monitored RAR window. [cited by applicant]
R1-1710892 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: NR 4-step RACH procedure. [cited by applicant]
R1-1711068 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: NTT Docomo, Inc., Title: Discussion on 4-step RA procedure for NR. [cited by applicant]
R1-1711148 3GPP TSG-RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Qualcomm Incorporated, Title: 4-step RACH procedure consideration. [cited by applicant]
R1-1711279 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Motorola Mobility, Lenovo, Title: RACH configuration and procedure. [cited by applicant]
R1-1711383 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, P.R. China, Jun. 27-30, 2017, Source: Ericsson, Title: 4-step random access procedure. [cited by applicant]
Dec. 16, 2019—European Extended Search Report—EP 19190988.6. [cited by applicant]
R1-1806545 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: Intel Corporation, Title: Potential enhancements to NR initial access and mobility to support unlicensed operation. [cited by applicant]
R2-1713954 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE Corporation, Sanechips, Title: Discussion on the beam failure recovery impact on RAN2. [cited by applicant]
R1-164131 3GPP TSG RAN WG1 Meeting #85, Nanjing, China, May 23-27, 2017, Source: Intel Corporation, Title: PRACH Transmission for eLAA. [cited by applicant]
R1-162358 3GPP TSG RAN WG1 Meeting #84bis, Busan, Korea, Apr. 11-15, 2016, Source: Intel Corporation, Title: PRACH Design for eLAA. [cited by applicant]
Apr. 22, 2021—European Office Action—EP 18718540.0. [cited by applicant]
3GPP TS 36.300 V8.5.0 (May 2008), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universial Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Acce… [cited by applicant]
“Further Consideration on two-step RACH,” Spokane, WA, 3GPP TSG RAN WG1 NR, Ad Hoc Meeting R1-1700035, Jan. 16-20, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“General discussion of UL power control for NR,” Spokane, WA, 3GPP TSG RAN WG1 NR, Ad Hoc Meeting R1-1700063, Jan. 16-20, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“Detailed considerations on UL power control design for NR,” Spokane, WA, 3GPP TSG RAN WG1 NR, Ad Hoc Meeting R1-1700064, Jan. 16-20, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“2-step Random Access Procedure,” Spokane, WA, 3GPP TSG RAN WG1 NR, AH_NR Meeting R1-1700105, Jan. 16-20, 2017, Source: ZTE, ZTE Microelectronics. [cited by applicant]
“Discussion on UL power control for NR,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting R1-1700142, Jan. 16-20, 2017, Source: ZTE, ZTE Microelectronics. [cited by applicant]
“On 2-step random access procedure and physical channel in NR,” Spokane, WA, 3GPP TSG RAN WG1 NR Meeting #87, R1-1700172, Jan. 16-20, 2017, Source: MediaTek Inc. [cited by applicant]
“NR two-step random access procedure,” Spokane, WA, 3GPP TSG-RAN WG1 NR adhoc, R1-1700300, Jan. 16-20, 2017, Source: Ericsson. [cited by applicant]
“Further considerations on a 2-step RA Procedure,” Spokane, WA, 3GPP TSG RAN WG1 AH_NR, R1-1700186, Jan. 16-20, 2017, Source: CATT. [cited by applicant]
“2-Step RA Procedure for NR,” Spokane, WA, 3GPP TSG RAN1 NR Ad-Hoc Meeting, R1-1700311, Jan. 16-20, 2017, Source: AT&T. [cited by applicant]
“On Uplink Power Control,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1700358, Jan. 16-20, 2017, Source: Intel Corporation. [cited by applicant]
“Discussion on 2-step RA procedure issues,” Spokane, WA, 3GPP TSG RAN WG1 Meeting #87, R1-1700426, Jan. 16-20, 2017, Source: ITRI. [cited by applicant]
“Discussion on 2 step RACH,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1700464, Jan. 16-20, 2017, Source: LG Electronics. [cited by applicant]
“Discussion on UL transmit power control for NR,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1700492, Jan. 16-20, 2017, Source: LG Electronics. [cited by applicant]
“Uplink power control for NR,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc, R1-1700553, Jan. 16-20, 2017, Source: Guangdong OPPO Mobile Telecom. [cited by applicant]
“On 2-step RA procedure for NR,” Spokane, WA, 3GPP TSG RAN WG1 Ad-Hoc Meeting, R1-1700577, Jan. 16-20, 2017, Source: ETRI. [cited by applicant]
“Design considerations for 2-step RACH,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1700587, Jan. 16-20, 2017, Source: HTC. [cited by applicant]
“Uplink power control considering waveform switching,” Spokane, WA, 3GPP TSG-RAN WG1-NR, R1-1700601, Jan. 16-20, 2017, Source: NTT Docomo, INC. [cited by applicant]
“On 2-step Random Access Procedure,” Spokane, WA, 3GPP TSG-RAN WG1 AH_NR Meeting, R1-1700652, Jan. 16-20, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell. [cited by applicant]
“Discussions on 2 Steps RACH Procedure,” Spokane, WA, 3GPP TSG RAN WG1 Meeting AH_NR Meeting, R1-1700668, Jan. 16-20, 2017, Source: Sony. [cited by applicant]
“2-step random access procedure,” Spokane, WA, 3GPP TSG RAN WG1 AH_NR Meeting, R1-1700703, Jan. 16-20, 2017, Source: InterDigital Communications. [cited by applicant]
“2-step RACH procedure consideration,” Spokane, WA, 3GPP TSG-RAN WG1 NR AdHoc Meeting, R1-1700792, Jan. 16-20, 2017, Source: Qualcomm Incorporated. [cited by applicant]
“UL power control in multi-beam based approaches,” Spokane, WA, 3GPP TSG RAN WG1 AH_NR Meeting, R1-1700868, Jan. 16-20, 2017, Source: Asus TeK. [cited by applicant]
“Physical channel design for 2-step RACH,” Spokane, WA, 3GPP TSG RAN WG1 Meeting NR, R1-1700880, Jan. 16-20, 2017, Source: Motorola Mobility. [cited by applicant]
“NR 2-step random access procedure,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad Hoc, R1-1700892, Jan. 16-20, 2017, Source: Samsung. [cited by applicant]
“UL Power Control Aspects,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1700940, Jan. 16-20, 2017, Source: Samsung. [cited by applicant]
“Dynamic network coordination for URLLC in the 5G New Radio,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1701108, Jan. 16-20, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell. [cited by applicant]
“Uplink Power Control for MIMO,” Spokane, WA, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, R1-1701109, Jan. 16-20, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell. [cited by applicant]
“General discussion of UL power control for NR,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1701687, Feb. 13-17, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“Detailed considerations on UL power control design for NR,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1701688, Feb. 13-17, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“Uplink power control for NR,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1701947, Feb. 13-17, 2017, Source: Guangdong OPPO Mobile Telecom. [cited by applicant]
“On UL Power Control,” Athens, Greece, 3GPP TSG-RAN WG1 Meeting #88, R1-1702216, Feb. 13-17, 2017, Source: Intel Corporation. [cited by applicant]
“Discussion on uplink power control for NR,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1702468, Feb. 13-17, 2017, Source: LG Electronics. [cited by applicant]
“Discussion on uplink power control,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1702623, Feb. 13-17, 2017, Source: Qualcomm Incorporated. [cited by applicant]
“On power control for NR,” Athens, Greece, 3GPP TSG-RAN WG1 Meeting #88, R1-1702695, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“UL Power Control Aspects,” Athens, Greece, 3GPP TSG RAN WG1 Meeting #88, R1-1702964, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“UL power control in multi-beam based approaches,” Spokane, WA, 3GPP TSG RAN WG1 AH_NR Meeting, R1-1703052, Jan. 16-20, 2017, Source: Asus TeK. [cited by applicant]
“Consideration on use cases of 2-step RACH procedure,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting #NR Ad Hoc, R2-1700023, Jan. 17-19, 2017, Source: Asus Tek. [cited by applicant]
“Consideration on fallback of 2-step RACH procedure,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting #NR Ad Hoc, R2-1700024, Jan. 17-19, 2017, Source: Asus TeK. [cited by applicant]
“Considerations on RACH procedure in NR,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700089, Jan. 17-19, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“Considerations on the Random-Access Procedure in Massive MIMO NR,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700103, Jan. 17-19, 2017, Source: National Instruments. [cited by applicant]
“2-step RACH to 4-step RACH fallback,” Spokane, WA, 3GPP TSG RAN WG2 NR Adhoc, R2-1700137, Jan. 17-19, 2017, Source: Sony. [cited by applicant]
“Considerations on the two-step RACH in NR,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700155, Jan. 17-19, 2017, Source: ZTE, ZTE Microelectronics. [cited by applicant]
“Considerations on 2-step RA,” Spokane, WA, 3GPP TSG RAN WG2 Meeting Ad Hoc, R2-1700205, Jan. 17-19, 2017, Source: CATT. [cited by applicant]
“2-Step Random Access Procedure in NR,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700237, Jan. 17-19, 2017, Source: InterDigital Communications. [cited by applicant]
“Consideration on use cases of 2-step RACH procedure,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting #NR Ad Hoc, R2-1700356, Jan. 17-19, 2017, Source: ASUSTeK, MediaTek Inc. [cited by applicant]
“Consideration on 2-step RACH,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting NR, R2-1700357, Jan. 17-19, 2017, Source: Samsung. [cited by applicant]
“Consideration on fallback of 2-step RACH procedure,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting #NR Ad Hoc, R2-1700358, Jan. 17-19, 2017, Source: ASUSTeK. [cited by applicant]
“Random Access enhancements,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700412, Jan. 17-19, 2017, Source: Ericsson. [cited by applicant]
“On Two-step Random Access and Random Access Latency,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad hoc, R2-1700413, Jan. 17-19, 2017, Source: Ericsson. [cited by applicant]
“Text Proposal to TR 38.804 on Random Access Procedure,” Spokane, WA, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700416, Jan. 17-19, 2017, Source: Ericsson. [cited by applicant]
“Discussions on 2 Steps RACH Procedure,” Spokane, WA, 3GPP TSG RAN WG2 Meeting AH_NR Meeting, R2-1700471, Jan. 17-19, 2017, Source: Sony. [cited by applicant]
“Flexible RACH,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting NR AH, R2-1700522, Jan. 17-19, 2017, Source: MediaTek Inc. [cited by applicant]
“2 step Random Access Procedure in NR,” Spokane, WA, 3GPP TSG-RAN WG2 Meeting NR ad-hoc, R2-1700564, Jan. 17-19, 2017, Source: Qualcomm Incorporated. [cited by applicant]
“Considerations on L2 handling for Handover,” Athens, Greece, 3GPP TSG-RAN WG2 NR Adhoc, R2-1700816, Feb. 13-17, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell. [cited by applicant]
“Random Access in NR—Flexible UE Bandwidth Aspects,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700821, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“Random Access Enhancements,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700850, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“Text proposal on RACH (E-mail discussion NR-AH#12),” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700851, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“Pcell change procedure for CA in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700855, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“Further details of handover execution in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700863, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“Conditional Handover,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700864, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“RLC ARQ vs. PDCP data recovery during mobility,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700865, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“SeNB to MeNB reconfiguration for NR dual-connectivity,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700866, Feb. 13-17, 2017, Source: Ericsson. [cited by applicant]
“RRC involved HO for cell-level mobility,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700883, Feb. 13-17, 2017, Source: MediaTek Inc. [cited by applicant]
“Mobility Enhancement for ‘0ms’ interruption,” Spokane, WA, 3GPP TSG-RAN WG2 NR, R2-1700897, Jan. 17-19, 2017, Source: MediaTek Inc., Asus TeK. [cited by applicant]
“Discussion on Handover Procedure Optimization,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700956, Feb. 13-17, 2017, Source: OPPO. [cited by applicant]
“Consideration on Random Access in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700962, Feb. 13-17, 2017, Source: OPPO. [cited by applicant]
“Design Principles for Random Access Procedure in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700969, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“Random Access Procedure in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700970, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“L2 Behaviors in NR Handover or Reconfiguration,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700984, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“Further Consideration on Inter-cell HO Mechanism,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700985, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“NR Mobility Enhancement on Single Connectivity,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700986, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“NR Mobility Enhancement on Dual Connectivity,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1700987, Feb. 13-17, 2017, Source: CATT. [cited by applicant]
“NW Activation-De-activation of autonomous handover in single connectivity,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701137, Feb. 13-17, 2017, Source: Sharp. [cited by applicant]
“Mobility in NR Connected-Active,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701148, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“Inter-cell and Inter-node UE RRC Driven Mobility in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701194, Feb. 13-17, 2017, Source: InterDigital Communications. [cited by applicant]
“Introduction of UE autonomous mobility,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701360, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“Discussion on intra-frequency operation for dual-connectivity in HF NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701361, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“Consideration on dual connected handover,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701384, Feb. 13-17, 2017, Source: ZTE, ZTE Microelectronics. [cited by applicant]
“Solutions for single connected handover,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701385, Feb. 13-17, 2017, Source: ZTE, ZTE Microelectronics. [cited by applicant]
“Remaining RAN2 aspects on random access procedure for NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701520, Feb. 13-17, 2017, Source: NTT Docomo, INC. [cited by applicant]
“RA enhancement for New RAT,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701539, Feb. 13-17, 2017, Source: LG Electronics Inc. [cited by applicant]
“NW controlled autonomous handover in single connectivity,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701711, Feb. 13-17, 2017, Source: Intel Corporation. [cited by applicant]
“Mobility type support for multiple beams in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701712, Feb. 13-17, 2017, Source: Intel Corporation. [cited by applicant]
“Further considerations of random access in NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701721, Feb. 13-17, 2017, Source: Intel Corporation. [cited by applicant]
“Considerations on NR RA procedure,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701771, Feb. 13-17, 2017, Source: Qualcomm Incorporated. [cited by applicant]
“Handover in single connectivity scenario,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701798, Feb. 13-17, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“0ms interruption handover for NR,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701799, Feb. 13-17, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“Enhancements for robust handover,” Athens, Greece, 3GPP TSG-RAN Meeting #97, R2-1701800, Feb. 13-17, 2017, Source: Huawei, HiSilicon. [cited by applicant]
“NR mobility in Connected,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701833, Feb. 13-17, 2017, Source: Sharp. [cited by applicant]
“Mobility Enhancements in NR phase 1 (Release 15),” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701905, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“How to define zero mobility interruption time,” Athens, Greece, 3GPP TSG-RAN WG2 Meeting #97, R2-1701906, Feb. 13-17, 2017, Source: Samsung. [cited by applicant]
“Condition based handover procedure in NR,” Athens, Greece, 3GPP TSG-RAN2 Meeting #97, R2-1701966, Feb. 13-17, 2017, Source: LG Electronics Inc. [cited by applicant]
“2-Step Random Access Procedure in NR,” Reno, Nevada, 3GPP TSG-RAN WG2 Meeting #96, R2-168520, Nov. 14-18, 2016, Source: Intel Corporation. [cited by applicant]
Jun. 21, 2018—Partial International Search Report and Written Opinion—PCT/US2018/023886. [cited by applicant]
“2-step Random Access Procedure,” Spokane, WA, 3GPP TSG RAN WG1 NR, AH_NR Meeting R1-1700105, Jan. 16-20, 2017, Source: ZTE, ZTE Microelectronics (Version 2). [cited by applicant]
Aug. 13, 2018—International Search Report and Written Opinion—PCT/2018/023886. [cited by applicant]
U.S. Appl. No. 62/427,736, filed Nov. 29, 2016. [cited by applicant]
3GPP TS 38.213 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.321 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]