SYSTEM AND METHOD FOR STORING WIRELESS TRANSMISSIONS - Patent application

Abstract

To provide a method for preserving an msg3 transmission in various aspects.SOLUTION: The method may include receiving, by a UE device, a CI that overlaps with an msg3 transmission from a base station. The msg3 transmission is not canceled in response to receiving the CI. Another method disclosed herein includes continuing an RA procedure. The method may include coding a first part of an msgB. The method may include coding a second part of the msgB. The method may include attempting to decode, by the UE device, the first part of the msgB. The method may include attempting to decode, by the UE device, the second part of the msgB. The method may include continuing the RA procedure on the basis that the decoding of the first part of the msgB was successful and that decoding of the second part of the msgB failed.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present embodiment relates to a wireless network system, and more particularly to a system and method for preserving msg3 Physical Uplink Shared Channel (PUSCH) transmission upon uplink cancellation indication (CI) and for continuing a random access (RA) procedure even if part of msgB does not pass error correction and detection procedures.

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 62 / 875,754, filed July 18, 2019, which is incorporated herein by reference. [Background technology]

[0003] During the RA procedure, the user equipment (UE) first attempts to connect to the base station. The UE device may transmit a preamble over a physical random access channel (PRACH) configured by the system information. The UE device then receives a grant for PUSCH transmission from the network for contention resolution.

[0004] CI is an instruction from the network to the UE device to cancel PUSCH transmission, including time and frequency resources that the network previously allocated to the UE device. The reason behind such cancellation is to free up some resources for other users that have higher priority information to transmit, for example for ultra-reliable and low-latency communication (URLLC).

[0005] Uplink (UL) transmissions may follow the CI described above, however, constantly canceling all types of UL transmissions based on the CI may degrade system performance. Summary of the Invention

[0006] Various embodiments of the present disclosure include a method for preserving a msg3 transmission. The method may include receiving, by a UE device, from a base station, a CI that overlaps with the msg3 transmission. In response to receiving the CI, the transmission of msg3 is not canceled.

[0007] Some embodiments include a method for partial decoding of a msgB transmission. The method may include encoding, by a base station, a first portion of msgB. The method may include encoding, by the base station, a second portion of msgB. The method may include attempting, by a UE device, to decode the first portion of msgB. The method may include attempting, by the UE device, to decode the second portion of msgB. Based on successful decoding of the first portion of msgB and unsuccessful decoding of the second portion of msgB, the method may include continuing with an RA procedure. [Brief description of the drawings]

[0008] The above and additional features and advantages of the present disclosure will become more readily apparent from the following detailed description, which proceeds with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates a system including a network and one or more UE devices, each having cancellation indication monitoring logic, in accordance with some embodiments disclosed herein. [Diagram 2] FIG. 2 shows the messaging in a time-line timing diagram, which includes four messaging steps within the RA procedure. [Diagram 3] FIG. 3 illustrates a frequency and timing diagram associated with an RA procedure, according to certain embodiments disclosed herein. [Figure 4] FIG. 4 illustrates the frequency and timing diagram of FIG. 3 in relation to an RA procedure, including cancellation, in accordance with certain embodiments disclosed herein. [Diagram 5] FIG. 5 illustrates a frequency and timing diagram associated with msg3 transmission in an RA procedure, according to certain embodiments disclosed herein. [Figure 6] FIG. 6 illustrates the frequency and timing diagram of FIG. 5 related to msg3 transmission in an RA procedure involving no resource cancellation, according to certain embodiments disclosed herein. [Figure 7] FIG. 7 shows the messaging in a timeline timing diagram including two message steps within the RA procedure. [Figure 8] FIG. 8 is a block diagram illustrating a procedure for preparing a physical downlink shared channel (PDSCH) in accordance with certain embodiments disclosed herein. [Figure 9] FIG. 9 is an example block diagram illustrating a procedure for splitting msgB according to certain embodiments disclosed herein. [Figure 10] FIG. 10 is a flow chart illustrating a technique for storing a msg3 transmission in accordance with certain embodiments disclosed herein. [Figure 11] FIG. 11 is a flow chart illustrating another technique for storing msg3 transmissions in accordance with certain embodiments disclosed herein. [Figure 12] FIG. 12 is a flow chart illustrating a technique for partial decoding of a msgB transmission in accordance with certain embodiments disclosed herein. [Figure 13]FIG. 13 is a flow chart illustrating another technique for partial decoding of a msgB transmission in accordance with certain embodiments disclosed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Reference will now be made in detail to the presently disclosed embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to enable a thorough understanding of the inventive concepts. However, it should be understood that one skilled in the art may practice the inventive concepts without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0010] It will be understood that, although terms such as first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first interface may be referred to as a second interface, and similarly, a second interface may be referred to as a first interface without departing from the scope of the inventive concept.

[0011] The terms used in the description of the inventive concept herein are for the purpose of describing particular embodiments only and are not intended to limit the inventive concept. As used in describing the inventive concept and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and includes any and all combinations of one or more of the associated listed items. As used herein, the terms "comprises" and / or "comprising" specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups. Components and features in the drawings are not necessarily drawn to scale.

[0012] The embodiments disclosed herein provide a system and method whereby message 3 (msg3) PUSCH transmission during an RA procedure does not need to follow a CI. Thus, msg3 PUSCH transmission, which may have an important role during an RA procedure, can be transmitted and received reliably. In addition, for a two-step random access channel (2-step RACH), partial decoding of message B (msgB) can be performed to extract time advance (TA), random access preamble identifier (RAPID), and / or uplink (UL) grant information prior to other parts of msgB. Thus, the probability of successful completion of the two-step RACH can be increased.

[0013] A CI is an instruction from the network to the UE device to cancel the UE device's transmissions, including time and frequency resources that the network previously assigned to the UE device. To perform this cancellation, the UE device may first receive a CI during a monitoring occasion (MO).

[0014] FIG. 1 illustrates a system 100 including a network 102 and one or more UE devices (e.g., 105a, 105b, 105c), each having a transmission cancellation logic section (e.g., 110a, 110b, 110c), according to some embodiments disclosed herein. The network 102 may include a cellular network or other type of wireless network. The UE devices may include, for example, a mobile computer 105a, a smart tablet 105b, a smart mobile phone 105c, etc. The one or more UE devices (e.g., 105a, 105b, 105c) may be communicatively connected to one or more remote base station devices (e.g., 115) via the network 102. The network 102 may include one or more towers, such as cell towers 120a and 120b, to facilitate transmission of information between the one or more UE devices (e.g., 105a, 105b, 105c) and the network 102. The network 102 may include one or more remote base station devices 115. A transmission cancellation logic section (e.g., 110a, 110b, 110c) may be embedded within each of the corresponding UE devices (e.g., 105a, 105b, 105c). The transmission cancellation logic section (e.g., 110a, 110b, 110c) may be embodied as software, firmware, hardware, or any suitable combination thereof.

[0015] FIG. 2 illustrates messaging in a timing diagram 200 along a time axis 202 that includes four messaging steps between a UE device (e.g., 105a, 105b, 105c) and a base station device (e.g., 115) within an RA procedure. The base station device 115 may be, for example, a gNodeB (gNB) device. The UL CI is an instruction from the network (e.g., 102) to the UE device (e.g., 105a, 105b, 105c) to cancel the UE device's transmissions in time and frequency resources that the network 102 (of FIG. 1) previously assigned to the UE device. One reason for such cancellation is to free up some resources for users with higher priority information, e.g., URLLC, to transmit. Any UL transmission may follow the CI. In the systems and methods disclosed herein, UL transmissions in an RA procedure may be preserved due to their importance, as further described below.

[0016] The RA procedure shown in FIG. 2 may include, for example, four steps. Diagram 200 may include a four-step RACH. The four-step RACH may be an RA procedure performed in four steps. Before initializing the RA procedure, the UE device (e.g., 105a, 105b, 105c) may receive broadcasted system information 215 from the base station device 115 (e.g., gNB device). The broadcasted system information 215 may include, for example, Master Information Block (MIB) and / or System Information Block (SIB) information. The broadcasted system information 215 may inform the UE device (e.g., 105a, 105b, 105c) regarding the configuration of the RA procedure.

[0017] In a first step, a message 1 (msg1) may be transmitted from a UE device (e.g., 105a, 105b, 105c) to the base station device 115. In msg1, the UE device may transmit a preamble 220 on the PRACH based on the broadcasted system information 215. The base station device 115 may use the preamble 220 to calculate or determine a TA 225, which may be used by the UE device to adjust the UL timing of the UE device. In some embodiments, the UE device may use one or more preambles, and the UE device may select one preamble (e.g., 220) from the one or more preambles.

[0018] In a second step, a message 2 (msg2) may be transmitted from the base station apparatus 115 to the UE device (e.g., 105a, 105b, 105c). The msg2 may include the TA 225, which is calculated after the base station apparatus 115 receives msg1. The msg2 may also include a temporary identifier 230 and / or an UL grant 235. The temporary identifier 230 may be a temporary cell radio network temporary identifier (TC-RNTI). The UL grant 235 may be used by the UE device to transmit msg3. In other words, the msg3 transmitted by the UE device may be based on the UL grant 235.

[0019] In a third step, message 3 (msg3) may be transmitted from the UE device (e.g., 105a, 105b, 105c) to the base station apparatus 115. In some embodiments, msg3 may be transmitted on a PUSCH based on resources allocated by the UL grant 235 received in msg2. msg3 may include a contention resolution sequence 240.

[0020] In a fourth step, a message 4 (msg4) may be sent from the base station apparatus 115 to the UE device (e.g., 105a, 105b, 105c). The msg4 may contain the same contention resolution sequence 240 to be verified by the UE device. The UE device may verify the contention resolution sequence 240. Once the UE device receives msg4 and verifies that the contention resolution sequence 240 is the contention resolution sequence 240 previously transmitted in msg3, the UE device considers itself to be in a connected state and may promote the temporary identifier 230 to a UE identifier 245. The UE identifier 245 may be a cell radio network temporary identifier (C-RNTI).

[0021] The illustrated RA procedure may be the first procedure that a UE device (e.g., 105a, 105b, 105c) executes when the UE device attempts to establish an initial connection to the network 102. While the initial msg1 has special importance in the RA procedure, msg3 is also important, since failure of msg3 would mean that the RA procedure is not successful. Thus, in some embodiments disclosed herein, cancellation of msg3 is not allowed even in the presence of any form of CI that may otherwise indicate cancellation of msg3. In other words, the UE device may always transmit msg3 over PUSCH, regardless of any possibility that the CI overlaps with the msg3 PUSCH allocation. In some embodiments, a transmission cancellation logic section (e.g., 110a, 110b, 110c in FIG. 1) of a UE device (e.g., 105a, 105b, 105c) may cause transmission of msg3 over PUSCH regardless of any possibility that the CI overlaps with the msg3 PUSCH allocation.

[0022] Figure 3 illustrates a frequency and timing diagram 300 associated with an RA procedure, according to certain embodiments disclosed herein. Figure 4 illustrates the frequency and timing diagram 300 of Figure 3 associated with an RA procedure including a cancellation 405, according to certain embodiments disclosed herein. Reference is now made to Figures 3 and 4.

[0023] In some embodiments, a UE device (e.g., 105a, 105b, 105c in FIG. 1) may be assigned resources 305 in time 310 and frequency 315 for use in one or more UL transmissions 325. In FIG. 3, a base station (e.g., 115 in FIG. 1) may transmit a command 320 to the UE device, which may indicate to the UE device that one or more UL transmissions 325 and / or resources 305 should be canceled. The command 320 may be a CI. The CI 320 may point to some or all of the resources 305. The one or more UL transmissions 325 may be for sending transmissions other than msg3 (e.g., PUSCH and / or sounding reference signal (SRS)). 4, the UE device may cancel (e.g., 405) one or more UL transmissions 325 on some or all of the resources 305 previously allocated for the one or more UL transmissions 325. In other words, after receiving the CI 320, the UE device may not transmit on some or all of the resources 305. Thus, at least some of the resources 305 may be freed up for other UE devices (e.g., 105a, 105b, 105c in FIG. 1) that may have higher priority information to transmit.

[0024] Figure 5 illustrates a frequency and timing diagram 500 associated with a msg3 transmission 525 in an RA procedure, according to certain embodiments disclosed herein. Figure 6 illustrates the frequency and timing diagram 500 of Figure 5 associated with a msg3 transmission 525 in an RA procedure, including not canceling resources 505, according to certain embodiments disclosed herein.

[0025] A UE device (e.g., 105a, 105b, 105c of FIG. 1) may be assigned resources 505 in time 510 and frequency 515 for transmitting a msg3 transmission 525 in an RA procedure. The resources 505 may be assigned by a UL grant (e.g., 235 of FIG. 2) previously received by the UE device from a base station (e.g., 115 of FIG. 1). The base station 115 may transmit a command 520 to the UE device, which may indicate to the UE device that the msg3 transmission 525 and / or the resources 505 should be canceled. The command 520 may be a CI. In accordance with some embodiments disclosed herein, the UE device may ignore at least a portion of the command 520, which indicates that the resources 505 that would otherwise be used to transmit the msg3 transmission 525 are subject to cancellation. In other words, the UE device may ignore (e.g., 605) the command 520 indicating the cancellation of the msg3 transmission 525 and / or the associated resources 505. Thus, the UE device (eg, 105a, 105b, 105c in FIG. 1) may continue to transmit the msg3 transmission 525, and thus the msg3 transmission 535 may be preserved despite the CI 520.

[0026] If a CI (e.g., 320, 520) indicates cancellation of resources other than the resource 505 used to transmit a msg3 transmission 525, then the UE device (e.g., 105a, 105b, 105c of FIG. 1) may comply with the CI (e.g., 320, 520) and cancel one or more UL transmissions (e.g., 325 of FIG. 3) and / or associated resources (e.g., 305 of FIG. 3) not used for the msg3 transmission. Thus, the CI (e.g., 320, 520) may be honored for non-msg3 UL transmissions.

[0027] FIG. 7 illustrates messaging in a timing diagram 700 along a time axis 702, including two messaging steps within an RA procedure. Diagram 700 may include partial decoding of msgB in a two-step RACH. The two-step RACH may be an RA procedure performed in two steps. Prior to initializing the RA procedure, the UE device (e.g., 105a, 105b, 105c) may receive broadcasted system information 715 from the base station device 115 (e.g., gNB device). The broadcasted system information 715 may include, for example, master information block (MIB) and / or system information block (SIB) information. The broadcasted system information 715 may inform the UE device (e.g., 105a, 105b, 105c) about the configuration of the RA procedure.

[0028] In a first step, message A (msgA) may be transmitted from a UE device (e.g., 105a, 105b, 105c) to the base station device 115. msgA may be essentially equivalent to a combination of msg1 and msg3 as shown in the four-step RACH of FIG. 2. msgA may be carried in two separate transmissions, one containing the same content of msg1 and the other containing the same content of msg3. In a second step, message B (msgB) may be transmitted from the base station device 115 to the UE device (e.g., 105a, 105b, 105c). msgB may be essentially equivalent to a combination of msg2 and msg4 as shown in the four-step RACH of FIG. 2.

[0029] FIG. 8 is a block diagram 800 illustrating a procedure for preparing a physical downlink shared channel (PDSCH) according to some embodiments disclosed herein. A data payload 815 may be provided by a media access control (MAC) layer to a physical (PHY) layer 802 of the base station 115 to be prepared for transmission. The process of preparing the data payload 815 may include error correction and detection encoding by an error correction and detection encoding unit 805. The error correction and detection encoding unit 805 may perform, for example, cyclic redundancy check (CRC) generation and appending 820, as well as code block partitioning and low density parity check (LDPC) encoding 825. The error correction and detection encoding by the base station 115 allows a UE device (e.g., 105a, 105b, 105c in FIG. 1) to correctly receive (or at least detect errors in) a PDSCH transmitted through relatively harsh channel conditions. The error correction and detection coding unit 805 of the base station 115 may perform channel coding 830, rate matching 835, and / or code block concatenation 840. Following the operations performed by the error correction and detection coding unit 805, additional physical layer procedures 810 may include scrambling, modulation, etc., as indicated at 845.

[0030] In accordance with some embodiments disclosed herein, msgB may be split into two portions (e.g., part 1 and part 2), as shown at 850. The splitting may be performed, for example, on data from the MAC layer 815. Each separate portion of msgB (e.g., part 1 and part 2) may be fed through an error correction and detection coding unit 805 for individual processing. In this way, if one of the portions fails during subsequent decoding by a UE device (e.g., 105a, 105b, 105c of FIG. 1), the UE device may still be able to successfully decode the other portion of msgB and successfully complete the RA procedure, as described further below.

[0031] In some embodiments, the splitting may be performed at the code block splitting and LDPC encoding stage 825, as indicated at 855, rather than on the data from the MAC layer 815 stage. Each separate portion of msgB (e.g., part 1 and part 2) may be fed through the remaining phases of the error correction and detection encoding unit 805 for individual processing. In this way, if one of the portions is subsequently unsuccessfully decoded by a UE device (e.g., 105a, 105b, 105c of FIG. 1), the UE device may still be able to successfully decode the other portion and complete the RA procedure, as described further below.

[0032] msgB may be split into multiple portions and transmitted separately from the base station 115 to the UE device (e.g., 105a, 105b, 105c in FIG. 1). In some embodiments, each individual portion may be checked independently for errors by the UE device. In some embodiments, msgB remains as a single transmission rather than being split into multiple portions, and instead, the UE device may detect errors in different portions of the single transmission.

[0033] 9 is an example block diagram 900 illustrating a procedure for splitting msgB, according to some embodiments. The first part (e.g., part 1) of msgB may be identical or substantially equivalent to msg2 from the four-step RACH disclosed above. Thus, the first part (e.g., part 1) may include at least a TA (e.g., 225 in FIG. 2) and a TC-RNTI (e.g., 230 in FIG. 2). The second part (e.g., part 2) may include a Contention Resolution Identifier (CRID) 915.

[0034] If a UE device (e.g., 105a, 105b, 105c in FIG. 1) can successfully decode the first portion (e.g., part 1), there is not necessarily a way for the UE device to determine that a particular message is intended for the UE device. Furthermore, if RAPID 905 is not included in the first portion (e.g., part 1) of msgB, there is not necessarily a way for the UE device to determine whether a collision has occurred. Thus, RAPID 905 may be included in the first portion (e.g., part 1) of msgB.

[0035] If the second part (e.g., part 2) of msgB fails (e.g., is not successfully decoded), the UE device (e.g., 105a, 105b, 105c of FIG. 1) may need to return to the first step of establishing a connection with the base station (e.g., 115 of FIG. 1) if the UE device does not have a UL grant 910 that can be used for transmitting a contention resolution sequence (e.g., 240 of FIG. 2). Thus, the first part (e.g., part 1) of msgB may include RAPID 905 and identify the UE device for which the transmission is intended. Additionally, the first part (e.g., part 1) of msgB may include the UL grant 910, which may prevent the UE device from returning to the first stage in the RA procedure.

[0036] In the case of separate decoding of the msgB portion, RAPID 905 and UL grant 910 may be transmitted in a first part (e.g., part 1) from a base station (e.g., 115 in FIG. 1) to a UE device (e.g., 105a, 105b, 105c in FIG. 1). RAPID 905 may be used for identification and UL grant 910 may be used for transmission of msg3 if the second part (e.g., part 2) of msgB fails (e.g., is not successfully decoded by the UE device).

[0037] A base station (e.g., 115 of FIG. 1) may generate msgB in a manner that RAPID 905 and UL grant 910 may be detected separately with respect to the remainder of msgB. In some embodiments, base station 115 may generate msgB in a manner that RAPID 905 and UL grant 910 may be detected first with respect to the remainder of msgB. Specifically, MAC layer 920 may take as input data such as RAPID 905, UL grant 910, and CRID 915, among other data. The MAC layer 920 procedures may then generate separate sets of data (e.g., part 1 and part 2) that are passed to a PHY layer (e.g., 802 of FIG. 8). The first part (e.g., part 1) may include information such as RAPID 905 and UL grant 910. The second part (e.g., part 2) may include information such as CRID 915.

[0038] The procedure by which the base station (e.g., 115 of FIG. 1) can achieve such separation in msgB can be realized in at least two ways. According to a first way, the base station 115 can transmit each of the two parts (e.g., part 1 and part 2) of the data output from the MAC layer 920 to the PHY layer 802 (of FIG. 8) as two separate data payloads from the MAC layer 920, as described above. According to a second way, the base station 115 can transmit the two parts (e.g., part 1 and part 2) of the data output from the MAC layer 920 to the PHY layer 802 (of FIG. 8) as one data input packet, as described above. In some embodiments, the code block partitioning and LDPC encoding stage 825 ensures that the first part (e.g., part 1) of the output of the MAC layer 920 belongs to an individual code block that is separate from another individual code block that comprises the second part (e.g., part 2) of the output of the MAC layer 920. A second approach may use a different procedure for receiving data at a UE device (e.g., 105a, 105b, 105c in FIG. 1) such that the UE device can use the data in the first part (e.g., part 1) of the MAC layer 920 if it is received correctly, even if the data in the second part (e.g., part 2) of the MAC layer 920 is not received correctly.

[0039] The UE device (e.g., 105a, 105b, 105c of FIG. 1) can attempt to decode the first portion (e.g., part 1) of the msgB data. Once it has correctly received and decoded the first portion, the UE device can correctly identify the RAPID 905 and the UL grant 910. The UE device is then ready to proceed with the RA procedure because a) the UE device has determined that it is addressed by that particular msgB since the RAPID 905 matches, and 2) the UE device has correctly determined the UL grant 910. And, therefore, the UE device can transmit a response to the base station 115 (of FIG. 1) using the resources and configuration indicated in the UL 910.

[0040] 10 is a flowchart 1000 illustrating a technique for preserving a msg3 transmission according to some embodiments disclosed herein. At 1005, a UE device (e.g., 105a, 105b, 105c of FIG. 1) may receive a CI from a base station (e.g., 115 of FIG. 1) that overlaps with the msg3 transmission. At 1010, in response to receiving the CI, the msg3 transmission is not canceled. In other words, the UE device may decide not to cancel the msg3 transmission.

[0041] 11 is a flow chart 1100 illustrating another technique for preserving a msg3 transmission in accordance with some embodiments disclosed herein. At 1105, a UE device (e.g., 105a, 105b, 105c of FIG. 1) may receive a CI from a base station (e.g., 115 of FIG. 1) that overlaps with a msg3 transmission. At 1110, one or more resources (e.g., 505 of FIG. 5) allocated for a msg3 transmission may be preserved. At 1115, the UE device may ignore the CI that overlaps with the msg3 transmission. At 1120, the UE device may perform the msg3 transmission.

[0042] FIG. 12 is a flow chart 1200 illustrating a technique for partial decoding of a msgB transmission according to some embodiments disclosed herein. At 1205, a first portion of msgB may be encoded. At 1210, a second portion of msgB may be encoded. At 1215, a UE device (e.g., 105a, 105b, 105c of FIG. 1) may attempt to decode the first portion of msgB. At 1220, the UE device may attempt to decode the second portion of msgB. At 1225, based on the successful decoding of the first portion of msgB and the failure to decode the second portion of msgB, the base station (e.g., 115 of FIG. 1) and the UE device may continue with the RA procedure. For example, the UE device may continue with the RA procedure and transmit a msg3 transmission based on the UL grant (e.g., 910 of FIG. 9). If the UE device fails to decode the second part of msgB, it may transmit msg3 after returning to the four-step RACH. In other words, the UE device may transmit a UL transmission based on the decoded UL grant in the continuation of the RA procedure.

[0043] 13 is a flow chart 1300 illustrating another technique for partial decoding of a msgB transmission according to some embodiments disclosed herein. At 1305, the msgB transmission may be split into a first portion and a second portion. For example, a base station (e.g., 115 in FIG. 1) may split the msgB transmission into a first portion and a second portion and then encode the first portion and the second portion separately. Later, a UE device (e.g., 105a, 105b, 105c in FIG. 1) may attempt to decode the two separate portions of the already split msgB.

[0044] At 1310, the TA (e.g., 225 in FIG. 2), the temporary identifier (e.g., 230 in FIG. 2), the RAPID (e.g., 905 in FIG. 9), and the UL grant (e.g., 910 in FIG. 9) may be stored in a first portion of msgB. At 1315, the CRID (e.g., 915 in FIG. 9) may be stored in a second portion of msgB.

[0045] At 1320, the UE device (e.g., 105a, 105b, 105c of FIG. 1) may attempt to decode a first portion of msgB. At 1325, the UE device may attempt to decode a second portion of msgB. At 1330, based on the successful decoding of the first portion of msgB and the failure to decode the second portion of msgB, the base station (e.g., 115 of FIG. 1) and the UE device may continue the RA procedure. In other words, the RA procedure may continue even if the second portion of msgB was not successfully decoded by the UE device.

[0046] For example, the UE device may continue the RA procedure and transmit a msg3 transmission based on the UL grant (e.g., 910 in FIG. 9). The UE device may transmit msg3 after returning to the four-step RACH if decoding of the second part fails. In other words, the UE device may transmit a UL transmission based on the decoded UL grant in the continuation of the RA procedure.

[0047] It will be understood that any of the components described herein or any combination of components may be used to perform one or more of the operations of the flowcharts of Figures 10 through 13. Additionally, the operations illustrated in the flowcharts are example operations and may include various additional steps not explicitly covered. The temporal order of the operations may be altered.

[0048] The various operations of the methods described above may be performed by any suitable means capable of performing the operations, such as various hardware and / or software components, circuits, and / or modules.

[0049] The methods or algorithms and functional blocks or steps described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a tangible, non-transitory computer-readable medium. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any form of storage medium known in the art.

[0050] The following description is intended to provide a brief, general description of suitable machines or machines on which certain aspects of the inventive concepts may be implemented. Typically, a machine includes a system bus to which a processor, memory, e.g., RAM, ROM, or other state storage medium, storage device, video interface, and input / output interface ports are attached. A machine may be controlled, at least in part, by input from traditional input devices, such as a keyboard, mouse, etc., as well as by instructions received from another machine, interaction with a virtual reality (VR) environment, biometric feedback, or other input signals. As used herein, the term "machine" is intended to broadly encompass a single machine, virtual machine, or a system of communicatively connected machines, virtual machines, or devices operating together. Exemplary machines include computing devices, such as personal computers, workstations, servers, portable computers, handheld devices, phones, tablets, etc., as well as transportation devices, e.g., private or public transportation vehicles, such as automobiles, trains, cabs, etc.

[0051] A machine may include an embedded controller, such as a programmable or non-programmable logic device or array, an application specific integrated circuit (ASIC), an embedded computer, a smart card, etc. A machine may utilize one or more connections to one or more remote machines, such as via a network interface, a modem, or other communicative connection. Machines may be interconnected by physical and / or logical networks, such as an intranet, the Internet, a local area network, a wide area network, etc. One skilled in the art will appreciate that network communications may utilize a variety of wired and / or wireless short or long range carriers and protocols, including radio frequency (RF), satellite, microwave, Institute of Electrical and Electronics Engineers (IEEE) 545.11, Bluetooth, optical, infrared, cable, laser, etc.

[0052] The embodiments of the present disclosure may be described by reference to or in association with associated data, including functions, procedures, data structures, application programs, and the like, which, when accessed by a machine, result in the machine performing a task or define an abstract data type or low-level hardware context. The associated data may be stored, for example, in volatile and / or non-volatile memory, e.g., RAM, ROM, and the like, or other storage devices and their associated storage media, including hard drives, floppy disks, optical storage devices, tapes, flash memory, memory sticks, digital video disks, biological storage devices, and the like. The associated data may be distributed over transmission environments, including physical and / or logical networks, in the form of packets, serial data, parallel data, propagated signals, and the like, and may be used in compressed or encrypted formats. The associated data may be used in distributed environments and may be stored locally and / or remotely for machine access.

[0053] Although the principles of the present disclosure have been described and illustrated with reference to the illustrated embodiments, it will be recognized that the illustrated embodiments can be modified in arrangement and detail and can be combined in any desired manner without departing from such principles. And, although the above description has focused on specific embodiments, other arrangements are contemplated. In particular, even when expressions such as "in accordance with one embodiment of the inventive concept" are used herein, these phrases are meant to generally refer to possible embodiments and are not intended to limit the inventive concept to the arrangement of a specific embodiment. As used herein, these terms can refer to the same or different embodiments that can be combined into other embodiments.

[0054] Embodiments of the present disclosure may include a non-transitory machine-readable medium that includes instructions executable by one or more processors, the instructions including instructions for carrying out elements of the inventive concepts as described herein.

[0055] The above exemplary embodiments are not to be construed as limiting the concept of the present invention. Although a few embodiments have been described, those skilled in the art will easily understand that many modifications to these embodiments are possible without substantially departing from the novel teachings and advantages of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of this disclosure as defined in the claims.

Claims

1. A method for preserving msg3 transmissions over a physical uplink shared channel (PUSCH), comprising: receiving, by a user equipment (UE) device, from a base station, a cancel indication (CI) that overlaps during said msg3 transmission; determining, in response to receiving the CI, not to cancel the msg3 transmission over the PUSCH; Including, the CI indicates one or more resources allocated for transmitting the msg3; The method further comprises: in response to the CI, reserving one or more resources allocated for transmitting the msg3. method.

2. The method further comprises: ignoring, by the UE device, the CIs that overlap during the transmission of the msg3; The method of claim 1 , comprising:

3. the CI is a first CI, The method further comprises: receiving, by the UE device, from the base station, a second CI that overlaps during a non-msg3 transmission; canceling the non-msg3 transmission in response to receiving the second CI; The method of claim 1 , comprising:

4. The second CI indicates one or more resources allocated for the non-msg3 transmission. The method according to claim 3.

5. The method further comprises: canceling one or more resources allocated to said non-msg3 transmissions in response to said second CI; The method of claim 4 , comprising:

6. The method further comprises: receiving, by the UE device, an uplink (UL) grant from the base station; allocating one or more resources for transmitting the msg3 based on the UL grant; The method of claim 1 , comprising:

7. The method further comprises: reserving one or more resources for transmitting msg3 after receiving the overlapping CI during the transmission of msg3; The method of claim 6, comprising:

8. The method further comprises: performing, by the UE device, the msg3 transmission after receiving the CI that overlaps during the msg3 transmission; The method of claim 7, comprising:

Images