TRANSMISSION OF A MESSAGE ON COMPLETION OF THE RADIO CORE RESOURCE CONTROL RECONFIGURATION

Abstract

Methods, systems, devices, and computer programs for transmitting a message to complete the reconfiguration of radio resource control (RRC) are disclosed. In one aspect, a UE performs operations that may include: receiving, from a base station, an initial downlink control information (DCI) specifying an initial uplink allocation for an initial transmission of a physical uplink shared channel (PUSCH), wherein the initial DCI includes a redundancy version (RV) corresponding to the initial PUSCH transmission; determining whether the RV is self-decoding; and determining whether to transmit a message to complete the RRC reconfiguration using the initial uplink allocation for the initial PUSCH transmission, based at least in part on the determination of whether the RV is self-decoding.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 540,497, filed September 26, 2023, entitled "TRANSMISSION OF RADIO RESOURCE CONTROL RECONFIGURATION COMPLETE MESSAGE," the contents of which are hereby incorporated by reference in their entirety. BACKGROUND

[0002] Wireless communication networks, such as fourth-generation (4G), fifth-generation (5G), etc., provide integrated communication platforms and telecommunication services for wireless user devices. The wireless communication networks include wireless access nodes that exchange wireless signals with the wireless user devices using wireless network protocols, such as those described in various telecommunication standards published by the Third Generation Partnership Project (3GPP). Examples of wireless communication networks include time-division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, long-term evolution (LTE), and fifth-generation new radio (5G NR).

[0003] A user equipment (UE) can use radio resource control (RRC) signaling to establish a communication link to an access node (e.g., a base station). Alignment at the RRC layer is used for a connection because it configures parameters across layers, from the higher Signaling Radio Bearer (SRB) / Data Radio Bearer (DRB) layers to the lower Physical Layer (PHY) / Radio Frequency (RF) layers. RRC signaling refers to the communication protocols and procedures used between the UE and the base station in wireless communication systems. RRC signaling is responsible for managing radio resources and controlling the establishment, maintenance, and release of the connection between the UE and the network. SUMMARY

[0004] According to an inventive aspect of the present disclosure, a method to be performed by the user equipment (UE) for transmitting a radio resource controller (RRC) reconfiguration completion message is disclosed. In one aspect, the method may include: receiving, from a base station, a first downlink control information (DCI) indicating a first uplink assignment for a first physical uplink shared channel (PUSCH) transmission, wherein the first DCI comprises a redundancy version (RV) corresponding to the first PUSCH transmission; determining whether the RV is self-decodable; and determining whether to transmit a radio resource controller (RRC) reconfiguration completion message using the first uplink assignment for the first PUSCH transmission based at least in part on the determination of whether the RV is self-decodable.

[0005] Other aspects include UE, facilities, systems and computer programs for carrying out the above-mentioned method.

[0006] The inventive method may include further optional features. For example, in some implementations, determining whether the RV is self-decodable comprises: determining that the RV is self-decodable; and determining to transmit the message to complete the RRC reconfiguration using the first uplink assignment for the first PUSCH transmission.

[0007] In some implementations, determining whether the RV is self-decodable includes: determining that the RV is not self-decodable; receiving, from the base station, a second DCI indicating a second uplink assignment for a second PUSCH transmission; and transmitting the message to complete the RRC reconfiguration using the second uplink assignment for the second PUSCH transmission.

[0008] In some implementations, determining whether the RV is self-decodable further includes transmitting information different from the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission.

[0009] In some implementations, the method further includes: prior to receiving the first DCI indicating the first uplink assignment for the first PUSCH transmission, receiving a DCI from the base station indicating an uplink assignment for a PUSCH transmission; and suspending the PUSCH transmission according to the DCI.

[0010] In some implementations, the RRC reconfiguration completion message is generated in response to RRC reconfiguration information received from the base station for a communication link.

[0011] In some implementations, the method further includes: terminating a communication connection to the base station; receiving new RRC reconfiguration information for a new communication connection from a new base station; receiving, from the new base station, a new DCI indicating a new uplink assignment for a new PUSCH transmission; suspending the new PUSCH transmission according to the new DCI; during the suspension, configuring a new RRC configuration for the new communication connection based at least on the new RRC reconfiguration information; receiving, from the new base station, a first new DCI indicating a first new uplink assignment for a first new PUSCH transmission, wherein the first new DCI includes a new RV corresponding to the first new PUSCH transmission; determining whether the new RV is self-decodable;and determining whether to transmit a new message to complete the RRC reconfiguration using the first new uplink assignment for the first new PUSCH transmission based at least in part on the determination of the new RV.;

[0012] In some implementations, the RV includes one of RV 1 or RV 2 and the second DCI includes a second RV and the second RV includes one of RV 0 or RV 3.

[0013] In some implementations, the first DCI includes a duration between receiving the first DCI and the first PUSCH transmission.

[0014] In some implementations, a format of each DCI includes one of DCI format 0_0 or DCI format 0_1.

[0015] According to another inventive aspect of the present disclosure, a method to be performed by a base station for transmitting a message to complete RRC reconfiguration is disclosed.In one aspect, the method may include transmitting, to a user equipment (UE), a first downlink control information (DCI) indicating a first uplink allocation for transmitting a first physical uplink shared channel (PUSCH), wherein the first DCI includes a redundancy version (RV) corresponding to the transmission of the first PUSCH; transmitting, to the UE, a second DCI indicating a second uplink allocation for transmitting a second PUSCH; in response to the transmission of the second DCI, receiving, from the UE, the second PUSCH corresponding to the second DCI, wherein the second PUSCH includes an RRC reconfiguration completion message generated in response to RRC reconfiguration information for a communication connection, wherein the RRC reconfiguration completion message is included in the second PUSCH based on the UE determining that the RV is not self-decodable.

[0016] Other aspects include base stations, facilities, systems and computer programs for carrying out the above-mentioned method.

[0017] The inventive method may include further optional features. For example, in some implementations, the method further includes receiving, from the UE, the first PUSCH corresponding to the first DCI, wherein the first PUSCH includes information other than the RRC reconfiguration completion message.

[0018] In some implementations, the method further includes: prior to transmitting the first DCI indicating the first uplink assignment for transmission of the first PUSCH, transmitting, to the UE, a DCI indicating an uplink assignment for transmission of a PUSCH; and detecting a failure to decode the PUSCH corresponding to the DCI.

[0019] In some implementations, the RV includes one of RV 1 or RV 2.

[0020] In some implementations, the second DCI includes one of RV 0 or RV 3.

[0021] In some implementations, a format of each DCI includes one of DCI format 0_0 or DCI format 0_1. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 illustrates a wireless network according to some implementations. Fig. 2A illustrates example system frames for an example process for transmitting an RRC reconfiguration completion message according to some implementations. Fig. Figure 2B is a flow diagram of the Fig. 2A disclosed exemplary process. Fig. Figure 2C is a flowchart of another example process for transmitting a message to complete RRC reconfiguration, according to some implementations. Fig. Figure 2D is a flowchart of another example process for transmitting a message to complete RRC reconfiguration according to some implementations. Fig. Figure 2E is a flowchart of another example process for transmitting a message to complete RRC reconfiguration, according to some implementations. Fig. Figure 3 illustrates another example process for transmitting a message to complete RRC reconfiguration according to some implementations. Fig. Figure 4 illustrates an example process for transmitting a message to complete RRC reconfiguration when the RV is not self-decodable, according to some implementations. Fig. 5 illustrates an example process for transmitting an RRC reconfiguration completion message in a handover procedure according to some implementations. Fig. 6 illustrates an example process for transmitting a message to complete RRC reconfiguration when the RV is self-decodable, according to some implementations. Fig. Figure 7 illustrates an example process for transmitting a message to complete RRC reconfiguration when the RV is self-decodable, according to some implementations. Fig. 8 illustrates another example process for transmitting an RRC reconfiguration completion message in a handover procedure according to some implementations. Fig. 9 is a block diagram of an example UE according to some implementations. Fig. 10 is a block diagram of an example access node according to some implementations. Fig. 11 is a block diagram of an example device according to some implementations.

[0022] Similar reference numerals in the various drawings indicate similar elements. DETAILED DESCRIPTION

[0023] This disclosure describes methods and systems for transmitting a radio resource control (RRC) reconfiguration completion message that enable the selection of a target physical uplink shared channel (PUSCH) for the RRC reconfiguration completion message based on the redundancy version (RV). In these methods and systems, a user equipment (UE) receives an RRC reconfiguration message for establishing a communication link from a base station. After establishing the RRC configuration in the UE, the target PUSCH is to be transmitted to the base station with an RRC reconfiguration completion message. In some implementations, the UE may check the value of an RV included in downlink control information (DCI) that schedules a first PUSCH.The RV value is specified by 2 bits in the DCI and indicates a level of error correction redundancy applied to transport blocks (TB) corresponding to the PUSCH scheduled by the DCI. If the RV is self-decodable, the first PUSCH is selected as the target PUSCH. If the RV is not self-decodable, the UE monitors a communication channel for new DCIs scheduling a new PUSCH before transmitting the first PUSCH. In this context, self-decodability refers to the property that the base station is able to decode a PUSCH based on a single transmission without combining that single transmission with other transmissions. The RV is specified by 2 bits in the DCI and can have the values ​​0, 1, 2, or 3. Transmissions (e.g.,PUSCH) in NR with RV values ​​of 0 or 3 (RV 0 or RV 3) are self-decodable because these transmissions contain sufficient redundancy or error correction coding to allow independent decoding. Transmissions with other RV values ​​(RV 1 and RV 2) are typically not self-decodable (except at very low code rates) because these transmissions do not contain sufficient redundancy or error correction coding for independent decoding, so the base station must rely on additional transmissions to decode a PUSCH by combining it with these other transmissions. If a new DCI is available before the first PUSCH is transmitted, the new PUSCH is selected as the destination PUSCH. However, if no new DCI is available before the first PUSCH is transmitted, the first PUSCH is selected as the destination PUSCH.Among other examples, the techniques of the disclosure describe methods for sending the RRC reconfiguration completion message in a destination PUSCH, thereby avoiding retransmissions, resulting in a reduction in the overall delay in completing the RRC configuration setup.

[0024] Fig. Figure 1 illustrates a wireless network according to some implementations. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B over an air interface 108. The UE 102 and the base station 104 communicate using a system that supports controls for managing access of the UE 102 to a network via the base station 104.

[0025] In some implementations, the wireless network 100 may be a non-standalone (NSA) network that incorporates the Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards according to the Third Generation Partnership Project (3GPP) technical specifications. For example, the wireless network 100 may be an Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. However, the wireless network 100 may also be a standalone (SA) network that incorporates only 5G NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G) systems), Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology (e.g., IEEE 802.11a); IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future developed IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like. While aspects may be described herein using terminology commonly associated with 5G NR, aspects of the present disclosure may be applied to other systems such as 3G, 4G, and / or systems subsequent to 5G (e.g., 6G).

[0026] In the wireless network 100, the UE 102 and any other UEs in the system may be, for example, laptop computers, smartphones, tablet computers, machine-like devices such as smart meters or specialized healthcare devices, intelligent transportation systems, or any other wireless devices with or without a user interface. In the network 100, the base station 104 provides the UE 102 with network connectivity to a wider network (not shown). This connectivity of the UE 102 is provided over the air interface 108 in a base station service area provided by the base station 104. In some implementations, such a wider network may be a wide area network operated by a mobile operator or the Internet. Each base station service area associated with the base station 104 is supported by antennas integrated into the base station 104.Service areas are divided into a series of sectors associated with specific antennas. Such sectors may be physically associated with fixed antennas or assigned to a physical area with tunable antennas or antenna settings that can be adjusted in a beamforming process to direct a signal to a specific sector.

[0027] The UE 102 includes control circuitry 110 coupled to transmit circuitry 112 and receive circuitry 114. The transmit circuitry 112 and receive circuitry 114 may each be coupled to one or more antennas. The control circuitry 110 may include various combinations of application-specific circuitry and baseband circuitry. The transmit circuitry 112 and receive circuitry 114 may be configured to transmit and receive data, respectively, and may include radio frequency (RF) or front-end module (FEM) circuitry.

[0028] In various implementations, aspects of transmit circuitry 112, receive circuitry 114, and control circuitry 110 may be integrated in various ways to implement the operations described herein. Control circuitry 110 may be adapted or configured to perform various operations, such as those described elsewhere in this disclosure with respect to a UE.

[0029] Transmit circuitry 112 may perform various operations described in this specification. Transmit circuitry 112 may transmit a plurality of multiplexed physical uplink channels. The plurality of physical uplink channels may be multiplexed using time division multiplexing (TDM) or frequency division multiplexing (FDM) along with carrier aggregation. Transmit circuitry 112 may be configured to receive block data from control circuitry 110 for transmission across air interface 108.

[0030] Receive circuitry 114 may perform various operations described in this specification. Similarly, receive circuitry 114 may receive a plurality of multiplexed physical downlink channels from air interface 108 and forward the physical channels to control circuitry 110. The plurality of physical downlink channels may be multiplexed according to TDM or FDM along with carrier aggregation. Transmit circuitry 112 and receive circuitry 114 may transmit and receive both control data and content data (e.g., messages, images, videos, etc.) structured into data blocks transmitted over the physical channels.

[0031] Fig. 1 also illustrates the base station 104. In some implementations, the base station 104 may be an NG radio access network (RAN) or a 5G RAN, an E-UTRAN, a non-terrestrial cell, or a legacy RAN such as a UTRAN or GERAN. As used herein, the term “NG-RAN” or the like may refer to the base station 104 operating in an NR or 5G wireless network 100, and the term “E-EUTRAN” or the like may refer to a base station 104 operating in an LTE or 4G wireless network 100. The UE 102 utilizes links (or channels) 106A, 106B, each including a physical communication interface / layer.

[0032] The switching logic of base station 104 may include control circuitry 116 coupled to transmit circuitry 118 and receive circuitry 120. Transmit circuitry 118 and receive circuitry 120 may each be coupled to one or more antennas that may be used to enable communications over air interface 108. Transmit circuitry 118 and receive circuitry 120 may be adapted to transmit and receive data, respectively, to each UE connected to base station 104. Transmit circuitry 118 may transmit physical downlink channels including a plurality of downlink subframes. Receive circuitry 120 may receive a plurality of physical uplink channels from various UEs, including UE 102.

[0033] In Fig. 1, the one or more channels 106A, 106B are illustrated as an air interface to enable communicative coupling and may be consistent with cellular communication protocols, such as a GSM protocol, a CDMA network protocol, a UMTS protocol, a 3GPP LTE protocol, an Advanced Long Term Evolution (LTE-A) protocol, an LTE-based access to unlicensed spectrum (LTE-U), a 5G protocol, an NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any of the other communication protocols discussed herein. In implementations, the UE 102 may exchange communication data directly over a ProSe interface.The ProSe interface may alternatively be referred to as a sidelink interface (SL interface), which comprises one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSCCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH). RRC signaling procedure

[0034] A UE (e.g. UE 102 of Fig. 1) communicates with an access node (e.g. a base station 104 of Fig. 1) Using RRC signaling to establish a communication connection. The RRC signaling procedure involves the UE receiving an RRC reconfiguration message (or RRC reconfiguration information) from the base station, validating / applying the parameters contained in the RRC reconfiguration message locally in the UE, and sending an RRC reconfiguration completion message back to the base station, indicating that the RRC configuration has been established in the UE. The RRC signaling procedure can be used for the initial establishment of the RRC connection and for updating the RRC connection.

[0035] In some cases, during the RRC signaling procedure, the processing of physical layer channels, such as Physical Uplink Shared Channel (PUSCH) / Physical Downlink Control Channel (PDCCH), in the UE is suspended for a period of time while the local UE adapts updated configurations from an RRC reconfiguration message. For example, the suspension may occur between the UE receiving an uplink assignment from a base station and the UE sending a reconfiguration completion message to the base station. In some cases, the suspension involves the UE skipping a PUSCH scheduled during the adaptation phase by an uplink assignment (UL assignment) indicated by downlink control information (DCI).In some cases, the suspension includes the UE missing DCIs for UL assignment due to PDCCH shutdown and consequently failing to detect PUSCH scheduling.

[0036] After completing the local RRC configuration, the UE transmits an RRC reconfiguration completion message to the base station. In some cases, this RRC reconfiguration completion message may be included in the PUSCH after the UE has restored its physical layer channels after the suspension. However, because the base station fails to decode the skipped PUSCH (e.g., upon receiving it) during the suspension phase, the base station's Hybrid Automatic Repeat Request (HARQ) mechanism requests a retransmission of the skipped PUSCH. In some cases, the UE includes the RRC completion message in a retransmitted PUSCH. Uplink HARQ transmission mechanism

[0037] For PUSCH scheduling, the DCI format 0_0 or 0_1 is used, and the base station specifies a redundancy version (RV) in the DCI payload. As previously mentioned, the RV value specifies a degree of error correction redundancy applied to the transport blocks (TBs) corresponding to the PUSCH scheduled by the DCI. The RV is a selection of bits from the same TB based on rules defined in the specification. Not all RVs can be self-decodable without HARQ combination. The DCI format 0_0 is used when only one UE is scheduled for uplink transmission. The DCI format 0_1 ​​is used when multiple UEs associated with the same DCI message are scheduled for uplink transmission.

[0038] The duration between the DCI and the corresponding PUSCH can be included as a K2 field in the DCI payload, and the duration value refers to a lookup table defined in the RRC configuration. The duration unit can be milliseconds, seconds, slots in a subframe, or the like. The duration between the first PUSCH and the subsequent retransmission (RETX) is dynamic, allowing the base station flexibility in scheduling. The K2 field can also contain additional control information or parameters related to downlink transmission. Transmission of the message to complete the RRC reconfiguration based on the RV of the PUSCH

[0039] The RRC Reconfiguration Completion message is transmitted to the base station and confirms the configuration setup in the UE. The payload size of the RRC Reconfiguration Completion message is small (typically less than 10 bytes) and sensitive to latency. Existing RRC signaling procedures do not check the RV value when the RRC Reconfiguration Completion message is enclosed in a PUSCH, so the UE may transmit an RRC Reconfiguration Completion message in response to a DCI with an RV that is not self-decodable. This may result in the base station receiving a PUSCH containing an RRC Reconfiguration Completion message that the base station cannot decode, resulting in the base station sending additional DCIs to retransmit the PUSCH.The net result is that the UE retransmits the PUSCH with the RRC reconfiguration completion message multiple times, increasing the overall delay in completing the RRC connection setup.

[0040] The disclosed implementations describe methods for sending the RRC reconfiguration completion message in a PUSCH, thereby avoiding retransmissions and reducing the overall delay in completing the RRC configuration setup.

[0041] Fig. 2A illustrates example system frames for an example process for transmitting an RRC reconfiguration completion message according to some implementations. Fig. Figure 2B is a flow diagram of the Fig. 2A. The process 200 is described in some implementations as being performed by a UE such as the UE 102 Fig. 1 or the UE 900 Fig. 9 executed.

[0042] With reference to Fig. 2A and Fig. 2B, in an exemplary process 200, the system frame / slot is referred to as X / Y (Xth Frame and Yth Slot). The duration of a slot depends on the configuration of a frame structure. For example, a slot in Frequency Division Duplex (FDD) mode may be 1 millisecond long, while in Time Division Duplex (TDD) mode, it may be 0.5 milliseconds long. Each frame may include multiple slots, e.g., ten slots. At 202, in a first system frame (System Frame 0), a UE (e.g., UE 102 from Fig. 1 or UE 900 from Fig. 9) an RRC reconfiguration message from a base station (e.g. base station 104 of Fig. 1 or base station 1000 of Fig. 10) at 0 / 0 (System Frame 0 / Slot 0) and begins validating / processing the RRC Reconfiguration message. At 204, the UE receives a first DCI (e.g., DCI 0_0 or DCI 0_1) including an uplink assignment at 0 / 1 (System Frame 0 / Slot 0) that schedules the transmission of a PUSCH to the base station at 0 / 5 (System Frame 0 / Slot 5, K2 slots later). At 206, the UE adapts its local communication layers with a new RRC configuration, as indicated by the RRC Reconfiguration message, suspending uplink (UL) / downlink (DL) during the adaptation phase from 0 / 3 (System Frame 0 / Slot 3) to 0 / 7 (System Frame 0 / Slot 7), thus skipping the scheduled PUSCH at 0 / 5 (System Frame 0 / Slot 5). At 208, the UE completes the establishment of the new RRC configuration, locally generates an RRC Reconfiguration Completion message, and resumes UL / DL at 0 / 8 (System Frame 0 / Slot 8).However, due to the previous UL / DL suspension, no immediate UL resource is available to send a PUSCH including the RRC Reconfiguration Completion message. At 210, the UE receives another DCI at 0 / 9 (System Frame 0 / Slot 9) scheduling a PUSCH at 1 / 3 (System Frame 1 / Slot 3), which is a retransmission of the previously skipped PUSCH at 0 / 5 (System Frame 0 / Slot 5). At 212, without checking the RV corresponding to the DCI at 0 / 9 (System Frame 0 / Slot 9) (e.g., the DCI includes a bit field indicating the RV), the UE includes the RRC Reconfiguration Completion message in the PUSCH transmitted at 1 / 3 (System Frame 1 / Slot 3). If the RV is not RV0 or RV3, a decoding failure would occur at the base station if the message received in the PUSCH at 1 / 3 (system frame 1 / slot 3) could not be decoded to complete the RRC reconfiguration.At 214, the decoding failure causes the base station to send another DCI at 1 / 7 (System Frame 1 / Slot 7) and request a retransmission of the PUSCH with the same HARQ ID. At 216, in response to the DCI at 1 / 7 (System Frame 1 / Slot 7), the UE performs the second retransmission of the PUSCH at 2 / 1 (System Frame 2 / Slot 1). In some implementations, the base station can correctly decode the message to complete the RRC reconfiguration by combining the PUSCHs at 1 / 3 (System Frame 1 / Slot 3) + 2 / 1 (System Frame 2 / Slot 1). In some implementations, the base station still fails to decode the RRC reconfiguration completion message by combined PUSCHs at 1 / 3 (system frame 1 / slot 3) + 2 / 1 (system frame 2 / slot 1) and one or more additional retransmissions are requested.

[0043] Fig. Figure 2C is a flowchart of another example process 200C for transmitting an RRC reconfiguration completion message according to some implementations. Process 200C is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0044] With reference to Fig. 2A and Fig. 2C, the UE performs a modified RRC signaling process 200C that reduces the number of transmissions. Block 210C is the same as block 210 of Fig. 2B. At 212C, the UE checks the RV corresponding to the DCI at 0 / 9 and determines that the RV value is 1 or 2 (the RV is not self-decodable). Following such a determination, the UE monitors a communication channel (e.g., the L1 / L2 control channels) for a new DCI from the base station between the time of the DCI at 0 / 9 and the scheduled PUSCH retransmission time at 1 / 3. The UE receives a new DCI at 1 / 1, which schedules a new PUSCH at 5 / 1. At 214C, the UE checks the RV value for the new DCI; if the RV is a self-decodable RV (e.g., RV value 0 or 3), the UE adds the message to the new PUSCH transmitted at 1 / 5 to complete the RRC reconfiguration. To avoid resource waste, at 216C, the UE adds other data to the PUSCH transmitted at 1 / 3. The other data can be any data except the RRC reconfiguration completion message.Although the initial transmission time for the RRC reconfiguration completion message is delayed by two slots (compared to the retransmission at 1 / 3), the new PUSCH at 1 / 5 can be successfully decoded by the base station, so no additional retransmission of the RRC reconfiguration completion message is required. This reduces the overall latency. If no new DCI is received between the DCI at 0 / 9 and the scheduled PUSCH retransmission time at / 3, the UE performs a retransmission at 1 / 3, which is the same as in block 212.

[0045] Fig. Figure 2D is a flowchart of another example process 200D for transmitting an RRC reconfiguration completion message according to some implementations. Process 200C is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0046] With reference to Fig. 2A and Fig. 2D, the UE performs a modified RRC signaling process 200D, which reduces the number of transmissions. Blocks 202D to 210D are the same as blocks 202 to 210 of Fig. 2B. At 212C, the UE checks the RV corresponding to the DCI at 0 / 9 and determines that the RV value is 1 or 2 (the RV is not self-decodable). Following such a determination, the UE monitors a communication channel (e.g., the L1 / L2 control channels) for a new DCI from the base station between the time of the DCI at 0 / 9 and the scheduled PUSCH retransmission time at 1 / 3. The UE receives a new DCI at 1 / 1, which schedules a new PUSCH at 5 / 1. At 214D, the UE checks the RV value for the new DCI; if the RV is a self-decodable RV (e.g., RV value 0 or 3), the UE adds the message to the new PUSCH transmitted at 1 / 5, completing the RRC reconfiguration. To avoid resource waste, at 216C, the UE adds other data to the PUSCH transmitted at 1 / 3. The other data can be any data except the RRC reconfiguration completion message.Although the initial transmission time for the RRC reconfiguration completion message is delayed by two slots (compared to the retransmission at 1 / 3), the new PUSCH at 1 / 5 can be successfully decoded by the base station, so no additional retransmission of the RRC reconfiguration completion message is required. This reduces the overall latency. If no new DCI is received between the DCI at 0 / 9 and the scheduled PUSCH retransmission time at / 3, the UE performs a retransmission at 1 / 3, which is the same as in block 212.

[0047] Fig. Figure 2E is a flowchart of another example process 200E for transmitting an RRC reconfiguration completion message according to some implementations. The process 200C is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0048] At 202E, the UE receives a first DCI indicating a first uplink assignment for a first PUSCH transmission from the base station. The first DCI includes an RV corresponding to the first PUSCH transmission. At 204E, the UE determines whether the RV is self-decodable. At 206E, the UE determines whether to transmit a message to complete the RRC reconfiguration using the first uplink assignment for the first PUSCH transmission, based at least in part on the determination of whether the RV is self-decodable.

[0049] If it is determined that the RV is self-decodable, the UE transmits the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission. For example, the UE appends the RRC completion message to the first PUSCH and transmits the first PUSCH, which includes the RRC completion message, to the base station.

[0050] If it is determined that the RV is not self-decodable, the UE receives a second DCI indicating a second uplink assignment for a second PUSCH transmission from the base station. The UE transmits the RRC reconfiguration completion message using the second uplink assignment for the second PUSCH transmission. The UE transmits information other than the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission. For example, the UE adds the RRC completion message to the second PUSCH and transmits the second PUSCH, which includes the RRC completion message, to the base station. The UE adds information other than the RRC reconfiguration completion message to the first PUSCH and transmits the first PUSCH, which includes the RRC completion message, to the base station.

[0051] Fig. Figure 3 illustrates another example process 300 for transmitting an RRC reconfiguration completion message according to some implementations. The process 300 is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0052] At 302, the UE determines that an RRC completion message has been generated and is pending transmission. At 304, the UE sets the first available PUSCH (as scheduled by the first DCI) for the first retransmission as the initial target PUSCH. At 306, the UE checks whether the RV of the PUSCH is self-decodable. If the RV of the PUSCH is self-decodable, the UE proceeds to block 312. If the RV of the PUSCH is not self-decodable, the selection mechanism kicks in. At 308, the UE checks whether a new DCI corresponding to a self-decodable new PUSCH occurs in the period between receiving the first available DCI and its corresponding first retransmission. If no new DCI occurs in the meantime, the UE proceeds to block 312.If a new DCI occurs in the meantime, at 310, the UE sets the new PUSCH as the updated target PUSCH and adds other data to the previous target PUSCH to avoid resource waste. At 312, the UE adds the RRC completion message to the target PUSCH and transmits the target PUSCH, which includes the RRC completion message, to the base station.

[0053] The techniques of the disclosure provide a mechanism for selecting a target PUSCH based on the RV value to transmit a message to complete RRC reconfiguration. Advantages of the disclosed techniques include transmitting a new PUSCH to reduce the latency caused by retransmitting the PUSCH due to an undecodable RV, while providing a fallback when no new PUSCH is available.

[0054] Fig. Figure 4 illustrates an example process for transmitting a message to complete RRC reconfiguration when the RV is not self-decodable, according to some implementations. The process 400 is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0055] In process 400, the UE receives RRC reconfiguration information for a communication link from a base station at 402. The RRC reconfiguration information refers to a set of parameters and configuration updates that are made during an RRC reconfiguration process in wireless communication systems between the base station (such as base station 104 of Fig. 1 or the base station 1000 Fig. 10) and the UE. RRC reconfiguration is a process that allows the base station to change or update the configuration of an established RRC connection with the UE. This may include changes to radio resource allocation, mobility-related parameters, handover settings, security parameters, and other network-specific configuration updates.

[0056] At 404, the UE receives a first DCI that includes an uplink assignment (UL assignment). The uplink assignment is the allocation of resources and the permission granted by the base station to a UE to transmit data on the uplink channel. The uplink assignment specifies the resources, such as time slots, frequency bands, and modulation schemes, that the UE can use to transmit its data to the base station.

[0057] At 406, in response to receiving the RRC reconfiguration information, the UE suspends the transmission of a first PUSCH scheduled by the first DCI. The UE suspends the transmission of the first PUSCH for a period of time due to the UE's local adaptation of the updated configurations from the RRC reconfiguration message. The transmission of the first PUSCH is skipped during the suspension.

[0058] At 408, during the suspension, the UE adjusts the RRC configuration for the communication link based at least on the RRC reconfiguration information.

[0059] At 410, the UE receives a second DCI from the base station scheduling a retransmission of the first PUSCH. The second DCI includes an RV value corresponding to the first PUSCH. For example, the RV value is RV 1 or RV 2, indicating that the RV is not self-decodable.

[0060] At 412, the UE determines that the RV is not self-decodable. The UE identifies that the RV value is RV 1 or RV 2.

[0061] At 414, before transmitting the first PUSCH as scheduled by the second DCI, the UE receives a third DCI from the base station scheduling a new PUSCH. The UE receives the third DCI in the time between receiving the second DCI and transmitting the first PUSCH.

[0062] At 416, after receiving the third DCI and in response to determining that the RV is not self-decodable, the UE adds the RRC reconfiguration completion message to the new PUSCH and initiates transmission of the new PUSCH including the RRC reconfiguration completion message as scheduled by the third DCI.

[0063] At 418, the UE adds other data (e.g., other information than in the RRC reconfiguration completion message) to the first PUSCH and initiates the transmission of the first PUSCH as scheduled by the second DCI.

[0064] Fig. Figure 5 illustrates an example process for transmitting an RRC reconfiguration completion message in a handover procedure according to some implementations. Process 500 is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0065] In process 500, the UE terminates the communication link with the current base station at 502. While the UE is moving, the network initiates a handover if it determines that the current base station's signal is weakening or degrading. The UE terminates the communication link with the current base station and is ready to establish a communication link with a new base station. Handover, also called handoff, is a process in cellular networks where an ongoing call or data session is seamlessly transferred from one base station to another as a user moves through the coverage area. The purpose of handover is to maintain the continuity of the communication session without interruption or loss of quality.

[0066] At 504, the UE receives new RRC reconfiguration information for a new communication connection from a new base station.

[0067] At 506, the UE receives a new DCI that includes a new uplink assignment.

[0068] At 508, in response to receiving the new RRC reconfiguration information, the UE suspends transmission of a second new PUSCH to the new base station as scheduled by the new DCI.

[0069] At 510, during the suspension, the UE configures a new RRC configuration for the new communication connection based at least on the new RRC reconfiguration information.

[0070] At 512, the UE receives a second new DCI from the new base station scheduling a retransmission of the second new PUSCH. The second new DCI includes a new RV corresponding to the second new PUSCH.

[0071] At 514, the UE determines that the new RV is self-decodable. The UE identifies that the new RV value is RV 0 or RV 3.

[0072] At 516, after receiving the second new DCI and in response to determining that the RV is self-decodable, the UE adds a new RRC reconfiguration completion message for the new communication link to the second new PUSCH and initiates transmission of the second new PUSCH as scheduled by the second new DCI.

[0073] Fig. Figure 6 illustrates an exemplary process for transmitting a message to complete RRC reconfiguration when the RV is self-decodable, according to some implementations. Process 600 is described in some implementations as being initiated from a base station such as base station 104. Fig. 1 or the base station 1000 Fig. 10 executed.

[0074] In process 600, the base station transmits RRC reconfiguration information for a communication link to a UE at 602.

[0075] At 604, the base station transmits a first DCI including an uplink assignment to the UE.

[0076] At 606, the base station detects a failure to decode a first PUSCH as scheduled by the first DCI because no first PUSCH is received due to a suspension at the UE. The suspension occurs during the adaptation phase of updated configurations from an RRC reconfiguration message.

[0077] At 608, the base station transmits a second DCI, scheduling a retransmission of the first PUSCH. The second DCI contains a redundancy version (RV) corresponding to the first PUSCH.

[0078] At 610, based on the RV not being self-decodable, the base station transmits a third DCI scheduling a new transmission of a new PUSCH to the UE prior to retransmitting the first PUSCH as scheduled by the second DCI.

[0079] At 612, in response to transmitting the third DCI, the base station receives the new PUSCH from the UE as scheduled by the third DCI. The new PUSCH contains the RRC reconfiguration completion message.

[0080] At 614, the base station also receives the first PUSCH, as scheduled by the second DCI. The first PUSCH contains other data (e.g., information other than the RRC reconfiguration completion message) to avoid wasting resources.

[0081] Fig. Figure 7 illustrates an example process for transmitting a message to complete RRC reconfiguration when the RV is self-decodable, according to some implementations. The process 700 is described in some implementations as being performed by a UE, such as UE 102 of Fig. 1 or UE 900 Fig. 9.

[0082] In process 700, the UE receives RRC reconfiguration information for a communication link from a base station at 702.

[0083] At 704, the UE receives a first DCI including an uplink assignment.

[0084] At 706, in response to receiving the RRC reconfiguration information, the UE suspends transmission of a first PUSCH as scheduled by the first DCI.

[0085] At 708, during the suspension, the UE configures the RRC configuration for the communication link based at least on the RRC reconfiguration information.

[0086] At 710, the UE receives a second DCI scheduling a retransmission of the first PUSCH from the base station. The second DCI includes an RV corresponding to the first PUSCH.

[0087] At 712, the UE determines that the RV is self-decodable. The UE identifies that the RV value is RV 0 or RV 3.

[0088] At 714, in response to determining that the RV is self-decodable, the UE adds the RRC reconfiguration completion message to the first PUSCH and initiates transmission of the first PUSCH as scheduled by the second DCI.

[0089] Fig. Figure 8 illustrates another example process for transmitting an RRC reconfiguration completion message in a handover procedure according to some implementations. Process 800 is described in some implementations as being initiated by a UE such as UE 102. Fig. 1 or the UE 900 Fig. 9 executed.

[0090] In process 800, the UE terminates the communication connection to the base station at 802.

[0091] At 804, the UE receives new RRC reconfiguration information for a new communication connection from a new base station.

[0092] At 806, the UE receives a new DCI from the new base station, which includes a new uplink assignment.

[0093] At 808, in response to receiving the new RRC reconfiguration information, the UE suspends the transmission of a second new PUSCH to the new base station as scheduled by the new DCI.

[0094] At 810, during the suspension, the UE configures a new RRC configuration for the new communication connection based at least on the new RRC reconfiguration information.

[0095] At 812, the UE receives a second new DCI from the new base station scheduling a retransmission of the second new PUSCH. The second new DCI includes a new RV corresponding to the second new PUSCH.

[0096] At 814, the UE determines that the new RV is not self-decodable. The UE identifies that the new RV value is RV 1 or RV 2.

[0097] At 816, prior to transmitting the second new PUSCH as scheduled by the second new DCI, the UE receives a third new DCI scheduling a third PUSCH from the base station.

[0098] At 818, after receiving the third new DCI and in response to determining that the RV is not self-decodable, the UE adds a new RRC reconfiguration completion message for the new communication link to the third PUSCH and initiates transmission of the third PUSCH as scheduled by the third new DCI.

[0099] At 820, the UE adds other data (e.g., different information than in the new RRC reconfiguration completion message) to the second new PUSCH and initiates the transmission of the second new PUSCH as scheduled by the second new DCI.

[0100] Fig. Figure 9 is a block diagram of an example UE according to some implementations. The UE 900 may be the UE 102 of Fig. 1 be similar to and essentially interchangeable with it.

[0101] The UE 900 may be any mobile or non-mobile computing device, such as mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, liquid level sensors, inventory sensors, electrical voltage / current measuring devices, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, video cameras, etc.), wearable devices (e.g., a smartwatch), Relaxed IoT devices.

[0102] The UE 900 may include processors 902, RF interface circuitry 904, memory / storage 906, user interface 908, sensors 910, driver circuitry 912, power management integrated circuits (PMIC) 914, antenna structure 916, and battery 918. The components of the UE 900 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of Fig. Figure 9 is intended to show an overview of some of the components of the UE 900. However, some of the components shown may be omitted, additional components may be present, and other arrangements of the components shown may occur in other implementations.

[0103] The components of the UE 900 may be coupled to various other components via one or more interconnects 920, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, lane, optical connection, etc., that enables various circuit components (on common or different chips or chipsets) to interact with each other.

[0104] Processors 902 may include processor circuitry such as baseband processor (BB) circuitry 922A, central processing unit (CPU) circuitry 922B, and graphics processing unit (GPU) circuitry 922C. Processors 902 may include any type of circuitry or processor circuitry that executes or otherwise processes computer-executable instructions such as program code, software modules, or functional processes from memory / storage 906 to cause UE 900 to perform the operations described herein.

[0105] In some implementations, baseband processor circuitry 922A may access a communications protocol stack 924 in memory / storage 906 to communicate over a 3GPP-compliant network. In general, baseband processor circuitry 922A may access the communications protocol stack to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some implementations, the PHY layer operations may additionally / alternatively be performed by the components of RF interface circuitry 904. Baseband processor circuitry 922A may generate or process baseband signals or waveforms that carry information in 3GPP-compliant networks.In some implementations, the waveforms for NR may be based on cyclic prefix OFDM “CP-OFDM” in the uplink or downlink and on discrete Fourier transform spread OFDM “DFT-S-OFDM” in the uplink.

[0106] The memory / storage 906 may comprise one or more non-transitory, computer-readable media containing instructions (e.g., communication protocol stack 924) that can be executed by one or more of the processors 902 to cause the UE 900 to perform various operations described herein. The memory / storage 906 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 900. In some implementations, a portion of the memory / storage 906 may be located on the processors 902 themselves (e.g., L1 and L2 cache), while other memory / storage 906 may be external to the processors 902 but accessible to them via a memory interface.The memory / storage 906 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of storage device technology.

[0107] The RF interface circuitry 904 may include transceiver circuitry and a radio frequency front-end module (RFEM), which enables the UE 900 to communicate with other devices over a radio access network. The RF interface circuitry 904 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0108] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna structure 916 and proceed with filtering and amplifying the signal (with a low-noise amplifier). The signal may be provided to a receiver of the transceiver, which downconverts the RF signal to a baseband signal, which is provided to the baseband processor of processors 902.

[0109] In the transmit path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal using a power amplifier before the signal is radiated over the air interface via antenna 916.

[0110] In various implementations, the RF interface circuitry 904 may be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0111] The antenna array 916 includes one or more antenna elements, each configured to convert electrical signals into radio waves for traveling through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 916 may include antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and communication with multiple inputs and outputs. The antenna 916 may include microstrip antennas, printed antennas fabricated on the surface of one or more circuit boards, patch antennas, phased array antennas, etc. The antenna 916 may include one or more panels designed for specific frequency bands, including bands in FRI or FR2.

[0112] The user interface 908 includes various input / output (I / O) devices intended to enable user interaction with the UE 900. The user interface 908 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for accepting input, including, but not limited to, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, or the like. The output device circuitry includes any physical or virtual means for displaying or otherwise conveying information, such as sensor readings, actuator position(s), or other similar information.The output device circuitry may include any number or combination of audio or visual displays, including, but not limited to, one or more simple visual outputs / displays (e.g., binary status indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (such as liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, and the like is generated or produced by the operation of the UE 900.

[0113] The sensors 910 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to another device, module, subsystem, etc. Examples of such sensors include, but are not limited to, inertial measurement units including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g.,Thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors and the like); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0114] Driver circuitry 912 may include software and hardware elements operable to control particular devices embedded within, attached to, or otherwise communicatively coupled to the UE 900. Driver circuitry 912 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 900.For example, the driver circuitry 912 may include a display driver to control and enable access to a display device, a touchscreen driver to control and enable access to a touchscreen interface, sensor drivers to obtain sensor readings from the sensors 910 and to control and enable access to the sensors 910, drivers to obtain actuator positions from electromechanical components or to control and enable access to the electromagnetic components, a camera driver to control and enable access to an embedded image capture device, and audio drivers to control and enable access to one or more audio devices.

[0115] The PMIC 914 can manage the power supply to various components of the UE 900. In particular, the PMIC 914 can control power source selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuitry 902.

[0116] In some implementations, the PMIC 914 may control various power-saving mechanisms of the UE 900, including DRX, as discussed herein. A battery 918 may power the UE 900, although in some examples, the UE 900 may be mounted or deployed at a fixed location and may have a power supply coupled to an electrical grid. The battery 918 may be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 918 may be a typical automotive lead-acid battery.

[0117] Fig. 10 is a block diagram of an example access node according to some implementations. Fig. Figure 10 illustrates an access node 1000 (e.g., a base station or gNB) according to some implementations. The access node 1000 may be the base station 104 of Fig. 1 and substantially interchangeable therewith. Access node 1000 may include processors 1002, RF interface circuitry 1004, core network (CN) interface circuitry 1006, memory / storage circuitry 1008, and an antenna structure 1010.

[0118] The components of the access node 1000 may be coupled to various other components via one or more interconnect elements 1012. The processors 1002, the RF interface circuitry 1004, the memory / storage circuitry 1008 (including the communication protocol stack 1014), the antenna structure 1010, and the interconnects 1012 may be similar to the elements of the same name described with respect to Fig. 9. For example, processors 1002 may include processor circuitry such as baseband processor (BB) circuitry 1016A, central processing unit (CPU) circuitry 1016B, and graphics processor unit (GPU) circuitry 1016C.

[0119] The CN interface circuitry 1006 may establish the connection to a core network, for example, a 5th generation core network (5 thGeneration Core (5GC) using a 5GC-compatible network interface protocol such as Carrier Ethernet protocols or other suitable protocol. Network connectivity to / from the access node 1000 may be provided via a fiber optic cable or a wireless backhaul. The CN interface circuitry 1006 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1006 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0120] As used herein, the terms "access node," "access point," or the like may describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the term “NG-RAN node” or the like may refer to an access node 1000 operating in an NR or 5G system (e.g., a gNB), and the term “E-UTRAN node” or the like may refer to an access node 1000 operating in an LTE or 4G system (e.g., an eNB).According to various implementations, the access nodes 1000 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing femtocells, picocells, or other similar cells with smaller coverage areas, lower user capacity, or higher bandwidth compared to macrocells.

[0121] In some implementations, all or portions of the access nodes 1000 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP may implement a RAN functional division, such as a PDCP division, where RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by individual access nodes 1000; a MAC / PHY division, where RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by individual access nodes 1000; or a "lower PHY" split, where RRC, PDCP, RLC, MAC layers, and upper PHY layer sections are operated by the CRAN / vBBUP, and lower PHY layer sections are operated by individual access nodes 1000.

[0122] In V2X scenarios, the access node 1000 may be or act as an RSU. The term "RoadSide Unit" or "RSU" may refer to any transport infrastructure unit used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type" RSU, an RSU implemented in or by an eNB may be referred to as an "eNB-type" RSU, an RSU implemented in or by a gNB may be referred to as a "gNB-type" RSU, and the like.

[0123] Fig. 11 is a block diagram of an example device 1100 according to some implementations. In some implementations, device 1100 includes baseband processor circuitry. For example, in some cases, device 1100 may be similar to baseband processor (BB) circuitry 922A of Fig. 9 or the baseband processor circuitry 1016A of Fig. 10 are similar.

[0124] As shown, the device 1100 includes one or more processors 1116A and 1116B and a memory / storage 1108 that stores instructions 1114 executed by the one or more processors 1116A and 1116B. Although Fig. 11 shows the device 1100 with multiple processors, in some cases the device 1100 may include a single processor (e.g., one of the processors 1116A or 1116B).

[0125] Device 1100 is electrically and communicatively connected to RF circuitry 1104 and the associated antenna structure 1110 via RF interface 1112. In some implementations, one or more of processors 1116A and 1116B execute instructions 1114 to control communication via RF interface circuitry 1104 and antenna structure 1110. For example, the one or more processors 1116A and 1116B may execute instructions 1114 to generate or process baseband signals or waveforms that carry information over wireless channels and / or manage the radio functions of the RF circuitry 1104 and the antenna structure 1110, such as signal modulation, coding, radio frequency shifting, in addition to or as an alternative to the user plane or control plane functions, as described with respect to the baseband processor circuitry 922A of Fig. 9 and the baseband processor circuitry 1016A of Fig.10. Device 1100 enables communication, e.g., wireless mobile radio communication, via a 3GPP-compatible network.

[0126] Additionally, in some implementations, device 1100 may include wireless hardware connectivity interfaces for sending / receiving data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components, as well as a power management interface (e.g., an interface for sending / receiving power). In such implementations, instructions 1114 may include instructions that, when executed by one or more of processors 1116A and 1116B, cause those processors to perform Wi-Fi communication on an 802.11 network and / or perform Bluetooth communication.

[0127] In some implementations, one or more of processors 1116A and 1116B is a 3G baseband processor, a 4G baseband processor, a 5G baseband processor, or another suitable baseband processor. In some implementations, one or more of processors 1116A and 1116B may be configured as a field-programmable gate array (FPGA) and / or may have dedicated hardware components, possibly including an application-specific integrated circuit (ASIC).

[0128] Various components may, for convenience, be described in the specification as performing a task or tasks. Such descriptions should be interpreted to include the phrase "configured to." Citing a component as being configured to perform one or more tasks expressly does not invoke a 35 USC § 112(f) interpretation for that component.

[0129] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the Examples section below. For example, baseband circuitry, as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples set forth below. For another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples set forth below in the Examples section. Examples

[0130] Further exemplary embodiments are provided in the following sections.

[0131] Example 1 includes a method including: receiving, from a base station, a first downlink control information (DCI) indicating a first uplink assignment for a first physical uplink shared channel (PUSCH) transmission, the first DCI comprising a redundancy version (RV) corresponding to the first PUSCH transmission; determining whether the RV is self-decodable; and determining whether to transmit a radio resource controller (RRC) reconfiguration completion message using the first uplink assignment for the first PUSCH transmission based at least in part on the determination of whether the RV is self-decodable.

[0132] Example 2 includes the method of Example 1, wherein determining whether the RV is self-decodable includes: determining that the RV is self-decodable; and determining to transmit the message to complete the RRC reconfiguration using the first uplink assignment for the first PUSCH transmission.

[0133] Example 3 includes the method of example 1 or 2, wherein determining whether the RV is self-decodable includes: determining that the RV is not self-decodable; receiving, from the base station, a second DCI indicating a second uplink assignment for a second PUSCH transmission; and transmitting the message to complete the RRC reconfiguration using the second uplink assignment for the second PUSCH transmission.

[0134] Example 4 includes the method of Example 3, wherein determining whether the RV is self-decodable further comprises transmitting information different from the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission.

[0135] Example 5 includes the method of any one of Examples 1 to 4, further comprising: prior to receiving the first DCI indicating the first uplink assignment for the first PUSCH transmission, receiving a DCI from the base station indicating an uplink assignment for a PUSCH transmission; and suspending the PUSCH transmission according to the DCI.

[0136] Example 6 includes the method of any one of Examples 1 to 5, wherein the RRC reconfiguration completion message is generated in response to RRC reconfiguration information for a communication link received from the base station.

[0137] Example 7 includes the method of any one of Examples 1 to 6, further comprising: terminating a communication connection to the base station; receiving new RRC reconfiguration information for a new communication connection from a new base station; receiving, from the new base station, a new DCI indicating a new uplink assignment for a new PUSCH transmission; suspending the new PUSCH transmission according to the new DCI; during the suspension, configuring a new RRC configuration for the new communication connection based at least on the new RRC reconfiguration information; receiving, from the new base station, a first new DCI indicating a first new uplink assignment for a first new PUSCH transmission, wherein the first new DCI includes a new RV corresponding to the first new PUSCH transmission; determining whether the new RV is self-decodable;and determining whether to transmit a new message to complete the RRC reconfiguration using the first new uplink assignment for the first new PUSCH transmission based at least in part on the determination of the new RV.;

[0138] Example 8 includes the method of any one of Examples 1 to 7, wherein the RV comprises one of RV 1 or RV 2 and the second DCI comprises a second RV and the second RV comprises one of RV 0 or RV 3.

[0139] Example 9 includes the method of any of Examples 1 to 8, wherein the first DCI comprises a duration between receiving the first DCI and the first PUSCH transmission.

[0140] Example 10 includes the method of any one of Examples 1 to 9, wherein a format of each DCI comprises one of DCI format 0_0 or DCI format 0_1.

[0141] Example 11 includes one or more processors configured to perform the method of any of Examples 1 to 10.

[0142] Example 12 includes an apparatus comprising: one or more processors; and one or more memory devices storing instructions that, when executed, cause one or more processors to perform the method of any of Examples 1 to 10.

[0143] Example 13 includes a method comprising: transmitting, to a user equipment (UE), a first downlink control information (DCI) indicating a first uplink allocation for transmission of a first physical uplink shared channel (PUSCH), wherein the first DCI includes a redundancy version (RV) corresponding to the transmission of the first PUSCH; transmitting, to the UE, a second DCI indicating a second uplink allocation for transmission of a second PUSCH; in response to the transmission of the second DCI, receiving, from the UE, the second PUSCH corresponding to the second DCI, wherein the second PUSCH includes an RRC reconfiguration completion message generated in response to RRC reconfiguration information for a communication connection, the RRC reconfiguration completion message being included in the second PUSCH based on the UE determining that the RV is not self-decodable.

[0144] Example 14 includes the method of Example 13, further comprising: receiving, from the UE, the first PUSCH corresponding to the first DCI, wherein the first PUSCH comprises information other than the RRC reconfiguration completion message.

[0145] Example 15 includes the method of example 13 or 14, further comprising: prior to transmitting the first DCI indicating the first uplink assignment for transmission of the first PUSCH, transmitting, to the UE, a DCI indicating an uplink assignment for transmission of a PUSCH; and detecting a failure to decode the PUSCH corresponding to the DCI.

[0146] Example 16 includes the method of any one of Examples 13 to 15, wherein the RV comprises one of RV 1 or RV 2.

[0147] Example 17 includes the method of any one of Examples 13 to 16, wherein the second DCI comprises either RV 0 or RV 3.

[0148] Example 18 includes the method of any one of Examples 13 to 17, wherein a format of each DCI comprises one of DCI format 0_0 or DCI format 0_1.

[0149] Example 19 includes one or more processors configured to perform the method of any of Examples 13 to 18.

[0150] Example 20 includes an apparatus comprising: one or more processors; and one or more memory devices storing instructions that, when executed, cause one or more processors to perform the method of any of Examples 13 to 18.

[0151] Various components may, for convenience, be described in the specification as performing a task or tasks. Such descriptions should be interpreted to include the phrase "configured to." Citing a component as being configured to perform one or more tasks expressly does not invoke a 35 USC § 112(f) interpretation for that component.

[0152] For one or more implementations, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the Examples section below. For example, baseband circuitry, as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples set forth below. For another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples set forth below in the Examples section.

[0153] Any of the examples described above may be combined with any other example (or combination of examples) unless explicitly stated otherwise.

[0154] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the implementations to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be learned from practice of various implementations.

[0155] Although the implementations have been described above in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be interpreted to encompass all such variations and modifications.

[0156] It goes without saying that when using personal data, data protection policies and practices should be followed that are generally accepted and that meet or exceed industry-specific or regulatory requirements to protect user privacy. In particular, personal data should be managed and handled in a manner that minimizes the risk of accidental or unauthorized access or use, and the nature of the authorized use should be clearly communicated to users. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] US 63 / 540,497

[0001]

Claims

[1] Method comprising: Receiving, from a base station, a first downlink control information (DCI) indicating a first uplink assignment for a first physical uplink shared channel (PUSCH) transmission, the first DCI comprising a redundancy version (RV) corresponding to the first PUSCH transmission; Determine whether the RV is self-decodable; and and determining whether to transmit a radio resource controller (RRC) reconfiguration completion message using the first uplink assignment for the first PUSCH transmission based at least in part on determining whether the RV is self-decodable. [2] The method of claim 1, wherein determining whether the RV is self-decodable comprises: Determining that the RV is self-decodable; and Determine to transmit the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission. [3] The method of claim 1, wherein determining whether the RV is self-decodable comprises: Determine that the RV is not self-decodable; Receiving, from the base station, a second DCI indicating a second uplink assignment for a second PUSCH transmission; and Transmit the message to complete the RRC reconfiguration using the second uplink assignment for the second PUSCH transmission. [4] The method of claim 3, wherein determining whether the RV is self-decodable further comprises transmitting information different from the RRC reconfiguration completion message using the first uplink assignment for the first PUSCH transmission. [5] The method of claim 1, further comprising: before receiving the first DCI indicating the first uplink assignment for the first PUSCH transmission, receiving a DCI from the base station, which specifies an uplink assignment for a PUSCH transmission; and Suspend PUSCH transmission according to DCI. [6] The method of claim 1, wherein the RRC reconfiguration completion message is generated in response to RRC reconfiguration information for a communication link received from the base station. [7] The method of claim 1, further comprising: Terminating a communication connection to the base station; Receiving new RRC reconfiguration information for a new communication link from a new base station; Receive, from the new base station, a new DCI indicating a new uplink assignment for a new PUSCH transmission; Suspension of the new PUSCH transmission according to the new DCI; during the suspension, configuring a new RRC configuration for the new communication link based at least on the new RRC reconfiguration information; Receiving, from the new base station, a first new DCI indicating a first new uplink assignment for a first new PUSCH transmission, wherein the first new DCI includes a new RV corresponding to the first new PUSCH transmission; Determining whether the new RV is self-decodable; and determining whether to transmit a new message to complete the RRC reconfiguration using the first new uplink assignment for the first new PUSCH transmission based at least in part on the determination of the new RV. [8] The method of claim 1, wherein the RV comprises one of RV 1 or RV 2 and the second DCI comprises a second RV and the second RV comprises one of RV 0 or RV 3. [9] The method of claim 1, wherein the first DCI comprises a duration between receiving the first DCI and the first PUSCH transmission. [10] The method of claim 1, wherein a format of each DCI comprises one of DCI format 0_0 or DCI format 0_1. [11] One or more processors of a device configured to carry out the method of claim 1. [12] Facility comprising: one or more processors; and one or more storage devices storing instructions which, when executed, cause the one or more several processors carry out the method according to claim 1. [13] Method comprising: Transmitting, to a user equipment (UE), a first downlink control information (DCI) indicating a first uplink assignment for the transmission of a first physical uplink shared channel (PUSCH), the first DCI comprising a redundancy version (RV) corresponding to the transmission of the first PUSCH; Sending, to the UE, a second DCI indicating a second uplink assignment for the transmission of a second PUSCH; in response to the transmission of the second DCI, receiving, from the UE, the second PUSCH corresponding to the second DCI, the second PUSCH including an RRC reconfiguration completion message generated in response to RRC reconfiguration information for a communication link, the RRC reconfiguration completion message being included in the second PUSCH based on the UE determining that the RV is not self-decodable. [14] The method of claim 13, further comprising: Receiving, by the UE, the first PUSCH corresponding to the first DCI, wherein the first PUSCH comprises information other than the RRC reconfiguration completion message. [15] The method of claim 13, further comprising: before transmitting the first DCI indicating the first uplink assignment for the transmission of the first PUSCH, transmitting, to the UE, a DCI indicating an uplink assignment for the transmission of a PUSCH; and Detecting a failure to decode the PUSCH corresponding to the DCI. [16] The method of claim 13, wherein the RV comprises one of RV 1 or RV 2. [17] The method of claim 13, wherein the second DCI comprises one of RV 0 or RV 3. [18] The method of claim 13, wherein a format of each DCI comprises one of DCI format 0_0 or DCI format 0_1. [19] One or more processors of a device configured to carry out the method of claim 13. [20] Facility comprising: one or more processors; and one or more storage devices storing instructions which, when executed, cause the one or more several processors carry out the method according to claim 13.

Images