SYSTEM AND METHOD FOR EXTENDED RANDOM ACCESS PROCEDURES - Patent application

Abstract

The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for enhanced random access procedures. Presented are systems and methods for enhanced random access procedures. A wireless communication device may receive a first message from a wireless communication node to enable transmitting a user equipment (UE)-specific timing advance (TA) value. The wireless communication device may transmit a second message to the wireless communication node, the second message including a report containing the UE-specific TA value.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for enhanced random access procedures. [Background technology]

[0002] In a fifth-generation (5G) New Radio (NR) mobile network, before a user equipment (UE) can transmit data to a base station (BS), the UE is required to acquire uplink and downlink synchronization with the BS. Uplink timing synchronization can be achieved by implementing a random access procedure. To meet the demand for faster and more efficient communication, the random access procedure should be enhanced. Summary of the Invention [Means for solving the problem]

[0003] The exemplary embodiments disclosed herein are directed to solving problems associated with one or more of the problems presented in the prior art, and to providing additional features that will become readily apparent by reference to the following detailed description when considered in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. It should be understood, however, that these embodiments are presented by way of example, not limitation, and that various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art upon perusal of this disclosure.

[0004] At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A wireless communication device may receive a first message from a wireless communication node to enable transmitting a user equipment (UE)-specific timing advance (TA) value. In response to receiving the first message, the wireless communication device may transmit a second message to the wireless communication node, the second message including a report containing the UE-specific TA value.

[0005] In some implementations, the first message may be included in a System Information Block 1 (SIB1), an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message. The second message may be transmitted prior to contention resolution for a random access procedure between the wireless communication device and the wireless communication node. The second message may be transmitted via a Medium Access Control (MAC) Control Element (CE) or an Uplink (UL) Common Control Channel (CCCH). Prior to or subsequent to transmitting the second message, the wireless communication device may transmit a third message to the wireless communication node, including a scheduled transmission for the random access procedure.

[0006] In some implementations, the second message can be transmitted prior to contention resolution of a random access procedure between the wireless communication device and the wireless communication node. The size of the portion of the second message containing the UE ID may be reduced. The second message may be transmitted via an uplink (UL) common control channel (CCCH) or an uplink (UL) common control channel 1 (CCCH1). The second message may include at least one of an RRCSetupRequest1 message, an RRCResumeRequest2 message, or an RRCReestablishmentRequest1 message.

[0007] In some implementations, the second message may be transmitted following contention resolution of a random access procedure between the wireless communication device and the wireless communication node. The second message may be transmitted via a dedicated control channel (DCCH). The second message may include at least one of an RRCSetupComplete message, an RRCRResumeComplete message, or an RRCRestablishmentComplete message.

[0008] At least one aspect is directed to a system, method, apparatus, or computer-readable medium, wherein a wireless communication node may transmit a first message to a wireless communication device to enable transmitting a user equipment (UE)-specific timing advance (TA) value to the wireless communication device. Following transmitting the first message, the wireless communication node may receive a second message from the wireless communication device, the second message including a report containing the UE-specific TA value.

[0009] The systems and methods presented herein include a novel approach for an enhanced random access procedure. Specifically, the systems and methods presented herein discuss a novel solution for time delay compensation during UE transmission of uplink signals. For example, a UE can receive an indication to enable UE-specific timing advance reporting. The UE can report a UE-specific timing advance (TA) value during a random access (RA) procedure. The indication to enable UE-specific timing advance reporting can be transmitted via at least one of SIB1, an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message. In some cases, the UE may report the UE-specific TA via a MAC CE or a radio resource control (RRC) message to be transmitted to the network (NW) before contention resolution. In some other cases, the UE can report the UE-specific TA via at least one of an RRC Setup Complete, an RRC Resume Complete, or an RRC Reestablishment Complete message. In some implementations, the UE can report the UE-specific TA via the aforementioned messages, but is not limited to the messages discussed herein. The present invention provides, for example, the following. (Item 1) 1. A wireless communication method, comprising: receiving, by a wireless communication device, from a wireless communication node, a first message for enabling transmission of a user equipment (UE)-specific timing advance (TA) value; transmitting, by the wireless communication device in response to receiving the first message, a second message to the wireless communication node, the second message including a report containing the UE-specific TA value; A method comprising: (Item 2) Item 1, wherein the first message is included in a system information block 1 (SIB1), an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message. (Item 3) Item 10. The method of item 1, further comprising transmitting the second message prior to contention resolution of a random access procedure between the wireless communication device and the wireless communication node. (Item 4) Item 4. The method of item 3, wherein the second message is transmitted via a Medium Access Control (MAC) Control Element (CE) or an Uplink (UL) Common Control Channel (CCCH). (Item 5) Item 4. The method of item 3, further comprising, prior to or subsequent to transmitting the second message, transmitting, by the wireless communication device to the wireless communication node, a third message including a scheduled transmission related to the random access procedure. (Item 6) Item 10. The method of item 1, further comprising transmitting the second message prior to contention resolution of a random access procedure between the wireless communication device and the wireless communication node, wherein the size of the portion of the second message containing a UE ID is reduced. (Item 7) Item 7. The method according to item 6, wherein the second message is transmitted via an uplink (UL) common control channel (CCCH) or an uplink (UL) common control channel 1 (CCCH1). (Item 8) 7. The method of claim 6, wherein the second message includes at least one of an RRCSetupRequest1 message, an RRCResumeRequest2 message, or an RRCReestablishmentRequest1 message. (Item 9) Item 10. The method of item 1, further comprising transmitting the second message following contention resolution of a random access procedure between the wireless communication device and the wireless communication node. (Item 10) Item 10. The method of item 9, wherein the second message is transmitted via a dedicated control channel (DCCH). (Item 11) 10. The method of claim 9, wherein the second message includes at least one of an RRCSetupComplete message, an RRCResumeComplete message, or an RRCRestablishmentComplete message. (Item 12) 1. A wireless communication method, comprising: transmitting, by a wireless communication node, a first message for enabling a wireless communication device to transmit a user equipment (UE) specific timing advance (TA) value; subsequent to transmitting the first message, receiving, by the wireless communication node, from the wireless communication device, a second message including a report containing the UE-specific TA value; A method comprising: (Item 13) A wireless communication device comprising at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and to implement a method recited in any of items 1-12. (Item 14) 13. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by at least one processor, causing the at least one processor to perform a method recited in any of items 1-12. [Brief explanation of the drawings]

[0010] Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the scope, scope, or applicability of the present solution. Please note that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0011] [Figure 1] FIG. 1 illustrates an example cellular communication network in which the techniques disclosed herein may be implemented, according to certain embodiments of the present disclosure.

[0012] [Figure 2] FIG. 2 illustrates a block diagram of an example base station and user equipment device, in accordance with some embodiments of the present disclosure.

[0013] [Figure 3] FIG. 3 illustrates an example contention-based random access (CBRA) with a four-step random access (RA) procedure / type, according to some embodiments of the present disclosure.

[0014] [Figure 4] FIG. 4 illustrates an exemplary CBRA with a two-step RA procedure, according to some embodiments of the present disclosure.

[0015] [Figure 5] FIG. 5 illustrates an example contention-free random access (CFRA) with a four-step RA procedure, in accordance with some embodiments of the present disclosure.

[0016] [Figure 6] FIG. 6 illustrates an exemplary CFRA involving a two-step RA procedure, according to some embodiments of the present disclosure.

[0017] [Figure 7] FIG. 7 illustrates an example fallback for CBRA with a two-step RA procedure, according to some embodiments of the present disclosure.

[0018] [Figure 8] 8-9 illustrate examples of message transmissions containing UE-specific TAs according to some embodiments of the present disclosure. [Figure 9] 8-9 illustrate examples of message transmissions containing UE-specific TAs according to some embodiments of the present disclosure.

[0019] [Figure 10]FIG. 10 illustrates an example UE-specific TA reporting MAC CE according to some embodiments of the present disclosure.

[0020] [Figure 11] FIG. 11 illustrates a flow diagram of an example method for an extended random access procedure, in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0021] Detailed Description 1. Mobile communication technology and environment 1 illustrates an exemplary wireless communication network and / or system 100 in which the techniques disclosed herein may be implemented, according to certain embodiments of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NE-IoT) network, and will be referred to herein as “network 100.” Such exemplary network 100 includes a base station 102 (hereinafter “BS 102,” also referred to as a wireless communication node), user equipment devices 104 (hereinafter “UE 104,” also referred to as a wireless communication device), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 overlaying a geographic area 101, which may communicate with each other via communication links 110 (e.g., wireless communication channels). In FIG. 1, the BS 102 and the UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its allocated bandwidth and providing adequate radio coverage to its intended users.

[0022] For example, the BS 102 may operate within an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of "communication nodes" that may practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0023] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols within a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as described above.

[0024] The system 200 generally includes a base station 202 (hereinafter “BS 202”) and a user equipment device 204 (hereinafter “UE 204”). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected, as needed, with one another via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected, as needed, with one another via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which may be any wireless channel or other medium suitable for the transmission of data as described herein.

[0025] As will be understood by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2 . Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0026] According to some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230, including a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210, including an RF transmitter and an RF receiver, each with circuitry coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the downlink transmitter is coupled to the downlink antenna 212 at the same time that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 may be coordinated in time such that the uplink transmitter is coupled to the uplink antenna 232 at the same time that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250. In some embodiments, there is close time synchronization with minimal guard time between changes in duplex direction.

[0027] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with a suitably configured RF antenna array 212 / 232 that may support a particular wireless communication protocol and modulation scheme. In some demonstrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards and equivalents. However, it should be understood that the present disclosure is not necessarily limited in application to any particular standard and associated protocol. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0028] According to various embodiments, the BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 may be implemented or realized with a general-purpose processor, an associative memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. As such, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0029] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, firmware, software modules, or any practical combination thereof, executed directly by processor modules 214 and 236, respectively. Memory modules 216 and 234 may be implemented 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 storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 may read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated within their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0030] The network communications module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communications between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communications module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 may communicate with conventional Ethernet-based computer networks. As such, the network communications module 218 may include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to specified operations or functions, the terms “configured for,” “configured to,” and conjugations thereof, refer to devices, components, circuits, structures, machines, signals, etc. that are physically constructed, programmed, formatted, and / or arranged to perform the specified operations or functions.

[0031] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each representing a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes computer packet transfers by using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer may be another layer.

[0032] Various exemplary embodiments of the present solution are described below with reference to the accompanying figures to enable those skilled in the art to make and use the present solution. As will be apparent to those skilled in the art after reading this disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, any specific order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the specific order or hierarchy of steps in a disclosed method or process can be rearranged while remaining within the scope of the present solution. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and that the present solution is not limited to the specific order or hierarchy presented, unless explicitly stated otherwise. 2. Systems and methods for extended random access procedures

[0033] In some systems, the UE can compensate for the timing advance (TA) at the UE side. In this case, the network should be aware of the UE-specific TA to assist in uplink (UL) and / or downlink (DL) scheduling. Furthermore, the UE may report information (e.g., the UE-specific TA) during the random access (RA) procedure.

[0034] Generally, referring to Figures 3-7, depicted are examples of contention-based random access (CBRA) and contention-free random access (CFRA) procedures with a four-step RA procedure / type and a two-step RA type, according to some implementations. In some systems, two types of RA procedures can be supported for accessing resources (e.g., RACH resources). For example, the two types can include a four-step RA type with MSG1 (e.g., message 1 or first message) and a two-step RA type with MSGA (e.g., message A). In some other systems, the types may not be limited to four-step and / or two-step RA types.

[0035] Referring now to Figure 3, depicted is an exemplary contention-based random access (CBRA) with four-step RA procedure / type, according to some embodiments of the present disclosure. The CBRA with four-step RA procedure (RACH) 300 is implemented between a base station (BS) 304 (e.g., a gNB) and a UE 302. The BS 304 and the UE 302 may be identical to or similar to the BS 202 and the UE 204, respectively, of Figure 2. In some embodiments, in step 1 (306), the UE 302 transmits a random access channel (RACH) preamble or a physical random access channel (PRACH) preamble in message 1 (MSG1) over an uplink random access channel (RACH) to the BS 304. In step 2 (308), once the preamble is successfully received by the BS 304, the BS 304 sends back to the UE 302 Message 2 (MSG2), which may include a Medium Access Control (MAC) Random Access Response (RAR) as a response to the preamble. MSG2 may be a response message transmitted by the BS 304 and received by the UE 302. In step 3 (310), once the MAC RAR with the corresponding Random Access Preamble (RAP) Identifier (ID) is received, the UE 302 can transmit Message 3 (MSG3) to the BS 304 with the grant carried in the MAC RAR (e.g., using the UL grant scheduled in the RA response). The UE 302 can transmit MSG3 to the BS 304 to schedule the transmission of the RA procedure. The UE 302 can monitor contention resolution. In step 4 (312), once MSG3 is received, the BS 304 transmits message 4 (MSG4) to the UE 302 in response to receiving MSG3 (e.g., the second response message). MSG4 may include a conflict resolution ID that may be included for conflict resolution purposes. In some implementations, if conflict resolution is not successful after the MSG3 transmission / retransmission, the UE 302 may retransmit or revert to MSG1.In some implementations, to reduce latency and speed up the initial access procedure, a two-step random access procedure can be used as described below in conjunction with FIG.

[0036] 4 illustrates an exemplary CBRA with a two-step RA procedure according to some embodiments of the present disclosure. In some implementations, the two-step random access procedure (RACH) 400 can complete the four steps in two messages or two steps in FIG. 3. In some implementations, at least some content of MSG1 and MSG3 from the four-step RACH may be included in MSG1 of the two-step RACH, and at least some content of MSG2 and MSG4 (RAR and contention resolution) in the four-step RACH may be included in MSG2 of the two-step RACH. For example, the two-step random access procedure 400 can be performed between a BS 304 (e.g., a gNB) and a UE 302. The BS 304 and the UE 302 may be the same as or similar to the BS 202 and the UE 204 of FIG. 2, respectively. In some implementations, the UE 302 may transmit an MSGA to the BS 304 for access to the BS 304, the MSGA including a preamble (e.g., an RA preamble) (404) and a data payload (e.g., a physical uplink channel (PUSCH) payload) (408). In some implementations, the payload may be optional. In some implementations, the preamble may be optional. In response to receiving the MSGA, the BS 304 may transmit an MSGB to the UE 302 (412). The MSGB may be a response message to the MSGA or a contention resolution for the UE 302 (e.g., the UE 302 monitoring for contention resolution). If the contention resolution is successful in response to receiving a response (e.g., a network response), the UE 302 may terminate the random access procedure, as shown in FIG. 1(b). Details of the two-step RA procedure may be described in further detail herein.

[0037] FIG. 5 illustrates an example contention-free random access (CFRA) with four-step RA procedure (500) in accordance with some embodiments of the present disclosure. One or more messages (e.g., MSG0, MSG1, MSG2, etc.) may include information in addition to, corresponding to, or as part of one or more messages, at least in conjunction with FIG. 3. In step 504, the BS 304 (e.g., a gNB or NW) may transmit an RA preamble assignment (e.g., a dedicated preamble) to the UE 302 as part of MSG0. The UE 302 may be allocated / assigned / provided with a portion of resources from the BS 304 for transmitting one or more subsequent messages to the BS 304. In response to receiving MSG0, the UE 302 may transmit MSG1, including the RA preamble, to the BS 304 (508). In response to receiving MSG1, the BS 304 may transmit a response message or random access response to the UE 302 (512). In some implementations, the UE 302 may terminate the RA procedure in response to receiving an RA response from the BS 304.

[0038] FIG. 6 illustrates an example CFRA (600) involving a two-step RA procedure according to some embodiments of the present disclosure. One or more messages (e.g., MSGO, MSGA, MSGB, etc.) may include information in addition to, corresponding to, or part of one or more messages, at least in conjunction with FIGS. 4-5. The BS 304 may send / transmit / provide an RA preamble and a PUSCH assignment to the UE 302 as part of MSGO (604). The UE 302 may receive MSGO, indicating that at least a portion of resources have been allocated or assigned to the UE 302. MSGO may indicate a dedicated preamble for MSG1 transmission assigned by the BS 304 / NW. In response to receiving MSGO, the UE 302 may transmit an MSGA to the BS 304, including at least an RA preamble (608) and a PUSCH payload (612). In some cases, the UE 302 may not transmit an RA preamble. In some other cases, the UE 302 may not transmit a PUSCH payload. In response to receiving the MSGA, the BS 304 may transmit 616 an RA response to the UE 302. In some implementations, the UE 302 may terminate the RA procedure in response to receiving the RA response.

[0039] FIG. 7 illustrates an example fallback (700) for CBRA with a two-step RA procedure in accordance with some embodiments of the present disclosure. The example fallback 700 for CBRA with a two-step RA procedure may be implemented between a UE 302 and a BS 304. Messages transmitted between the UE 302 and the BS 304 (e.g., MSGA, MSGB, MSG3, MSG4, etc.) may include, correspond to, or be part of messages as discussed in conjunction with at least FIGS. 3-4 . The UE 302 may transmit an RA preamble (704) and a PUSCH payload (708) to the BS 304 as part of the MSGA. In some cases, the BS 304 may transmit a fallback indication (712) to the UE 302 as part of the MSGB. If the fallback indication is received within the MSGB, the UE 302 may implement an MSG3 transmission (716) using the UL grant scheduled within the fallback indication. The UE 302 may monitor for contention resolution from the BS 304. In response to receiving MSG3, the BS 304 may transmit 720 the contention resolution to the UE 302. If the contention resolution is not successful after transmitting / retransmitting MSG3, the UE 302 may revert to transmitting MSGA or perform at least one of steps 704 or 708. For example, in some cases, the UE 302 may not transmit a payload. In some other cases, the UE 302 may not transmit an RA preamble.

[0040] In some implementations, in a non-terrestrial network (NTN), a UE 302 with location information can compensate for a timing advance based on at least the location of the UE 302 and an estimated transmission delay between the UE 302 and a satellite, among other components or devices that introduce the transmission delay. In some systems, the BS 304 (e.g., a gNB or a network) may not be aware of the compensated value at the UE side. Thus, the BS 304 may not be able to efficiently schedule the UE 302. Therefore, the UE 302 can report at least the location information and the estimated transmission delay to the BS 304 to improve the efficiency of UE scheduling.

[0041] To compensate for transmission delays between the UE 302 and the satellite, the UE 302 (e.g., a wireless communication device) can receive an indication to enable UE-specific timing advance reporting from the BS 304 (e.g., a wireless communication node, gNB, or network). For example, the indication to enable UE-specific timing advance reporting (sometimes generally referred to as timing reporting) can be transmitted via at least one of an SIB1, an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message. In some cases, the message (e.g., an SIB1, an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message) may be part of or correspond to at least one of MSGO, MSG1, MSG2, MSG3, MSG4, MSGA, MSGB, etc., as discussed in conjunction with at least Figures 3-7. In response to receiving the indication, the UE 302 can report a UE-specific timing advance (TA) value during the RA procedure to the BS 304. To report the UE-specific TA value, the UE 302 may consider / utilize one or more options considering / based on certain conditions / parameters (e.g., as follows): In some implementations, the UE 302 may consider other options for implementing features or functionality for reporting the UE-specific TA value. Exemplary Option 1 for Reporting UE-Specific TA Values

[0042] In some implementations, the UE 302 can report a UE-specific TA to be transmitted to the NW / BS 304 via a MAC CE or UL Common Control Channel (CCCH) message (e.g., newly generated / introduced). The MAC CE or UL CCCH message can be transmitted to the BS 304 before contention resolution. In this case, the UE 302 may transmit two MSG3s during the RA procedure. The first MSG3 can be for the first scheduled transmission of the RA procedure. The second MSG3 can include a UE-specific TA (e.g., a TA value). To transmit the two MSG3 messages, the BS 304 can configure an UL grant for the two MSG3 transmissions before contention resolution.

[0043] A new value / codepoint / index of the Logical Channel ID (LCID) for the UL Shared Channel (UP-SCH) for MAC CE transmission of UE-specific TA reports can be predetermined / provided / configured for the UE 302 and the BS 304. For example, the UE 302 and / or the BS 304 can be configured with a new LCID value from reserved codepoints or indices (e.g., 35-44, 47, etc.) for use for MAC CE. Examples of LCID values ​​can include the following values, as in Table 1: LCID values ​​may include other values ​​in addition to the examples provided in Table 1. [Table 1]

[0044] Referring to FIG. 8, a first example of a message transmission includes a UE-specific TA (800) according to some embodiments of the present disclosure. In some implementations, the first MSG3 may be the first scheduled transmission of an RA procedure. For example, the UE 302 may transmit an RA preamble to the NW 802 (804). The NW 802 may include or correspond to the features or functionality of the BS 304, such as those shown in FIG. 3-7. In response to receiving the RA preamble, the NW 802 may transmit an RA response to the UE 302 (808). In this case, the UE 302 may transmit the first MSG3 to the NW 802 (812), which includes the first scheduled transmission. Concurrently with / during / during the transmission of the first MSG3, the UE 302 may transmit / send / forward a second MSG3, which may be a MAC CE or RRC message, including the UE-specific TA. Thus, the UE 302 may receive a response message (eg, contention resolution) from the NW 802.

[0045] Referring to FIG. 9, a second example of message transmission includes a UE-specific TA (900) according to some embodiments of the present disclosure. In some implementations, the first MSG3 can be a first MAC CE or RRC message including the UE-specific TA, and the second MSG3 can carry / include the content of the original first scheduled transmission of the RA procedure. For example, the UE 302 can transmit an RA preamble to the NW 802 (904). In response to receiving the RA preamble, the NW 802 can transmit an RA response to the UE 302 (908). In this case, the UE 302 can transmit the first MSG3, which can be a MAC CE or RRC message including the UE-specific TA (912). In parallel with or in response to transmitting the first MSG3, the UE 302 can transmit a second MSG3 including the content of the scheduled transmission of the RA procedure (916). In some cases, the first and second MSG3 may correspond to or be part of a single MSG3. The UE 302 may monitor for contention resolution. In response to receiving the MSG3 from the UE 302, the NW 802 may transmit 920 a contention resolution (e.g., a response message) to the UE 302. Exemplary Option 2 for Reporting UE-Specific TA Values

[0046] In some implementations, the UE 302 can report the UE-specific TA via a new UL CCCH / CCCH1 message. For example, the existing UL CCCH message may not have room for the UE-specific TA report. In this case, in the new UL CCCH / CCCH1 message, the size of the UE ID portion of the message can be reduced to allow room / allocated space for the UE-specific TA report. Thus, the UE 302 can report the UE-specific TA value to the BS 304 (or NW 802) via the new UL CCCH / CCCH1. Exemplary Option 3 for Reporting UE-Specific TA Values

[0047] In some implementations, the UE 302 may report the UE-specific TA via MSG5 (e.g., a new or different message). For example, the UE 302 may introduce a new information element in, but not limited to, the RRCSetupComplete, RRCResumeComplete, or RRCReestablishmentComplete message. In some cases, the UE 302 may transmit MSG5 following other messages (e.g., MSG1, MSG2, MSG3, MSG4, etc.). In some other cases, the UE 302 may transmit MSG5 in parallel with or prior to one or more other messages. Example Implementation for Enabling UE-Specific Timing Advance Reporting

[0048] The UE 302 can receive an indication from the BS 304 to enable UE-specific timing advance reporting. The indication can be included in SIB1->servingCellConfigCommon->uplinkConfigCommon->initialUplinkBWP->rach-ConfigCommon. For example, the BS 304 can send the indication via SIB1 to servingCellConfigCommon, uplinkConfigCommon, initialUplinkBWP, and / or rach-ConfigCommon. Example Implementation for Reporting UE-Specific TA Values ​​- Option 1

[0049] Referring to FIG. 10 , depicted is an exemplary UE-specific TA report MAC CE (1000) according to some embodiments of the present disclosure. The exemplary UE-specific TA report 1000 may include one or more UESpecificTAReport messages used to report a UE-specific TA value. The UE-specific TA report may be reported daily, weekly, monthly, etc. (e.g., on days 1 through N). For the UESpecificTAReport message, for example, the signaling radio bearer may be SRB0, the Radio Link Control (RLC)—Solution Architecture and Monetization Platform (SAP) may be in Transparent Mode (TM), the logical channel may be CCCH, and the direction may be from the UE 302 to the NW 802. The UE 302 may transmit one or more UESpecificTAReport messages to the NW 802. An example of a UESpecificTAReport message may be provided as follows: [ka]

[0050] INTEGER(0..(2 XX )-1) is the index value TA (e.g., 0, 1, 2...(2 XX )-1) may be used to control the amount of timing adjustment at the UE side, for example as specified in a system. Example Implementation for Reporting UE-Specific TA Values ​​- Option 2

[0051] In some implementations, the UE 302 can use an RRCSetupRequest1 message to request establishment of an RRC connection with the BS 304 (or another NW 802). The RRCSetupRequest1 message can be a new message of size 48 bits, among other sizes. The RRCSetupRequest1 message can include the signaling radio bearer, i.e., SRB0, the RLC-SAP, i.e., TM, the logical channel, i.e., CCCH, and the direction, i.e., from the UE 302 to the NW 802. An example of an RRCSetupRequest1 message can be as follows: [ka]

[0052] The characters " / / " in the example codes for messages herein represent or can be followed by a comment associated with an individual line of code. While certain examples of messages are provided, the UE 302 (or BS 304 and NW 802) can transmit or receive other configurations / modifications / parameters / scripts / text of messages to implement features or functionality such as those discussed herein.

[0053] In some implementations, the UE 302 may use the RRCResumeRequest2 message to request a re-initiation (e.g., resume) of an interrupted RRC connection or to perform an RNA update. The UE 302 may transmit the RRCResumeRequest2 message to the NW 802. For example, the RRCResumeRequest2 message may include the signaling radio bearer, i.e., SRB0, the RLC-SAP, i.e., TM, the logical channel, i.e., CCCH, and the direction, i.e., from the UE 302 to the network 802. An example of the RRCResumeRequest2 message may be as follows: [ka]

[0054] In some implementations, the UE 302 may use an RRCReestablishmentRequest1 message to request reestablishment of an RRC connection. The UE 302 can use the RRCReestablishmentRequest1 message for transmission to the NW 802. The RRCReestablishmentRequest1 message can include a signaling radio bearer, i.e., SRB0, an RLC-SAP, i.e., TM, a logical channel, i.e., CCCH, and a direction, i.e., from the UE 302 to the network 802. An example of an RRCReestablishmentRequest1 message can be as follows: [ka]

[0055] In some implementations, the UE 302 may use an RRCSetupRequest1 message to request re-establishment of an RRC connection to the NW 802. The RRCSetupRequest1 message may include the signaling radio bearer, i.e., SRB0, the RLC-SAP, i.e., TM, the logical channel, i.e., CCCH1, and the direction, i.e., from the UE 302 to the network 802. An example of an RRCSetupRequest1 message may be as follows: [ka]

[0056] In one implementation, the UE 302 can use the RRCResumeRequest2 message to request re-initiation of an interrupted RRC connection or to perform an RNA update. The UE 302 can transmit the RRCResumeRequest2 message to the NW 802. The RRCResumeRequest2 message may include the signaling radio bearer, i.e., SRB0, the RLC-SAP, i.e., TM, the logical channel, i.e., CCCH1, and the direction, i.e., from the UE 302 to the NW 802. An example of the RRCResumeRequest2 message can be as follows: [ka]

[0057] In some implementations, the UE 302 may use the RRCResumeRequest3 message to request re-initiation of an interrupted RRC connection or to perform an RNA update. The UE 302 may transmit the RRCResumeRequest3 message to the NW 802. The RRCResumeRequest3 message may include the signaling radio bearer, i.e., SRB0, the RLC-SAP, i.e., TM, the logical channel, i.e., CCCH1, and the direction, i.e., from the UE 302 to the NW 802. An example of the RRCResumeRequest3 message may be as follows: [ka]

[0058] In one implementation, the UE 302 can use an RRCReestablishmentRequest1 message to request reestablishment of an RRC connection. The UE 302 can transmit the RRCReestablishmentRequest1 message to the NW 802. The RRCReestablishmentRequest1 message can include a signaling radio bearer, i.e., SRB0, an RLC-SAP, i.e., TM, a logical channel, i.e., CCCH1, and a direction, i.e., from the UE 302 to the NW 802. An example of the RRCReestablishmentRequest1 message can be as follows: [ka] Example Implementation for Reporting UE-Specific TA Values ​​- Option 3

[0059] In one implementation, the UE 302 may use an RRCSetupComplete message to confirm completion of the RRC connection establishment (e.g., a status of successful completion or completion). The UE 302 may transmit the RRCSetupComplete message to the NW 802. The RRCSetupComplete message may include the signaling radio bearer, i.e., SRB1, the RLC-SAP, i.e., acknowledged mode (AM), the logical channel, i.e., DCCH, and the direction, i.e., from the UE 302 to the NW 802. An example of the RRCSetupComplete message may be as follows: [ka] [ka]

[0060] In one implementation, the UE 302 may use the RRCResumeComplete message to confirm successful completion (e.g., completion status) of the RRC connection re-initiation. The UE 302 may transmit the RRCResumeComplete message to the NW 802. The RRCResumeComplete message may include the signaling radio bearer, i.e., SRB1, the RLC-SAP, i.e., AM, the logical channel, i.e., DCCH, and the direction, i.e., from the UE 302 to the NW 802. An example of the RRCResumeComplete message may be as follows: [ka] [ka]

[0061] In some cases, one or more example messages may include optional data / messages / steps / text / code. For example, data (e.g., one or more lines) of an example message preceding the "OPTIONAL" description / indication may be removed / discarded / hidden from the message. In another example, data presented after the "OPTIONAL" indication may be removed from the message. In some implementations, a message may include at least one or all of the optional data within the message.

[0062] In one implementation, the UE 302 may use an RRCReestablishmentComplete message to confirm successful completion of the RRC connection reestablishment. For example, the UE 302 may transmit an RRCReestablishmentComplete message to the NW 802 to confirm completion of the RRC connection reestablishment. The RRCReestablishmentComplete message may include a signaling radio bearer, i.e., SRB1, an RLC-SAP, i.e., AM, a logical channel, i.e., DCCH, and a direction, i.e., from the UE 302 to the NW 802. An example of the RRCReestablishmentComplete message may be as follows: [ka]

[0063] Referring to Figure 11, a flow diagram of an example method 1100 for an extended random access procedure is shown, in accordance with an embodiment of the present disclosure. Method 1100 may be implemented using any of the components and devices detailed herein in conjunction with at least Figures 1-10. In overview, method 1100 may include transmitting a first message (1105). Method 1100 may include receiving the first message (1110). Method 1100 may include transmitting a second message (1115). Method 1100 may include receiving the second message (1120).

[0064] Referring now to operation (1105), in some implementations, a wireless communication node (e.g., a gNB, a BS, or a NW) may send / transmit / forward / provide a first message to a wireless communication device (e.g., a UE or a client device). In response to transmitting the first message, the wireless communication device may receive the first message from the wireless communication node (1110). The wireless communication device may receive the first message to enable sending the UE-specific TA value to the wireless communication node. In some implementations, the first message may be included / embedded in at least one of System Information Block 1 (SIB1), an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message.

[0065] Referring to operation 1115, in response to receiving the first message, the wireless communication device may send / transmit a second message to the wireless communication node. The second message may include a report (e.g., a UE-specific TA report) including a UE-specific TA value. The wireless communication node may receive 1120 the second message from the wireless communication device in response to the transmission.

[0066] In some implementations, the wireless communication device may transmit a second message to the wireless communication node prior to contention resolution of the RA procedure (e.g., MSG4 or MSGB). The contention resolution of the RA procedure can be between the wireless communication device and the wireless communication node. For example, the wireless communication device may transmit the second message via at least one of a MAC CE or an UL CCCH. In some implementations, the wireless communication device may transmit a third message (e.g., MSG3) prior to or following the step of transmitting the second message. The third message may include a scheduled transmission for the RA procedure.

[0067] In some implementations, the wireless communication device may transmit a second message to the wireless communication node prior to contention resolution of the RA procedure between the wireless communication device and the wireless communication node. The size of the portion of the second message containing the UE ID may be reduced (e.g., to allow / allocate room / space for a UE-specific TA report). For example, the second message may be transmitted over at least one of an UL CCCH or an UP CCCH1. In some cases, the second message may include at least one of an RRCSetupRequest1 message, an RRCResumeRequest2 message, or an RRCReestablishmentRequest1 message.

[0068] In some implementations, the wireless communication device may transmit a second message following contention resolution of an RA procedure between the wireless communication device and the wireless communication node. For example, the second message may be transmitted via a dedicated control channel (DCCH). In some cases, the second message may include at least one of an RRCSetupComplete message, an RRCResumeComplete message, or an RRCRestablishmentComplete message.

[0069] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those skilled in the art to understand example features and functionality of the present solution. However, such skilled artisans will understand that the present solution is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. Additionally, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the scope and scope of the present disclosure should not be limited by any of the example embodiments described above.

[0070] It should also be understood that any designation of elements herein using designations such as "first," "second," etc., generally does not limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, the designation of a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some manner.

[0071] Additionally, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0072] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein for convenience as “software” or “software modules”), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

[0073] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented in or by integrated circuits (ICs), which may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and / or transceivers to communicate with various components within a network or device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

[0074] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable transfer of a computer program or code from one geographic location to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0075] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of discussion, various modules are described as discrete modules; however, as will be apparent to one skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of the present solution.

[0076] Additionally, memory or other storage and communication components may be employed in embodiments of the solution. It should be understood that, for purposes of clarity, the above description describes embodiments of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely references to suitable means for providing the described functionality.

[0077] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the following claims.

Claims

1. 1. A wireless communication method, comprising: receiving, by a wireless communication device, a first message from a wireless communication node, the first message comprising an indication to enable transmitting a user equipment (UE) specific timing advance (TA) value and included in a serving CellConfigCommon; In response to receiving the first message, the wireless communication device transmits to the wireless communication node a second message including a report containing the UE-specific TA value, the second message being transmitted via a Medium Access Control (MAC) Control Element (CE) corresponding to a Logical Channel ID (LCID) of a reserved codepoint or index; A wireless communication method comprising:

2. 1. A wireless communication method, comprising: transmitting, by a wireless communication node, to a wireless communication device, a first message, the first message comprising an indication to enable sending a user equipment (UE) specific timing advance (TA) value, the first message being included in a serving CellConfigCommon; subsequent to transmitting the first message, the wireless communication node receiving a second message from the wireless communication device including a report containing the UE-specific TA value, the second message being transmitted via a Medium Access Control (MAC) Control Element (CE) corresponding to a Logical Channel ID (LCID) of a reserved codepoint or index; A wireless communication method comprising:

3. 1. A wireless communication device comprising at least one processor, the at least one processor comprising: receiving, via a transceiver, a first message from a wireless communication node, the first message comprising an indication to enable transmitting a user equipment (UE) specific timing advance (TA) value, the first message being included in a serving CellConfigCommon; and In response to receiving the first message, transmitting via the transceiver to the wireless communication node a second message including a report containing the UE-specific TA value, the second message being transmitted via a Medium Access Control (MAC) Control Element (CE) corresponding to a Logical Channel ID (LCID) of a reserved codepoint or index; 10. A wireless communication device configured to:

4. 1. A wireless communication node comprising at least one processor, the at least one processor comprising: transmitting, via a transceiver, to a wireless communication device, a first message, the first message comprising an indication to enable sending a user equipment (UE)-specific timing advance (TA) value, the first message being included in a serving CellConfigCommon; and subsequent to transmitting the first message, receiving from the wireless communication device via the transceiver a second message including a report containing the UE-specific TA value, the second message being transmitted via a Medium Access Control (MAC) Control Element (CE) corresponding to a Logical Channel ID (LCID) of a reserved codepoint or index; A wireless communication node configured to:

5. 10. A non-transitory computer-readable program storage medium having code stored thereon that, when executed by at least one processor, causes the at least one processor to implement the wireless communication method of claim 1.

6. 10. A non-transitory computer-readable program storage medium having code stored thereon that, when executed by at least one processor, causes the at least one processor to implement the wireless communication method of claim 2.

Images