Transmission of radio resource control reconfiguration completion messages

Abstract

The present disclosure relates to transmission of radio resource control (RRC) reconfiguration completion messages, and in particular to methods, systems, apparatuses, and computer programs for transmission of radio resource control (RRC) reconfiguration completion messages. In one aspect, operations are performed by a UE and may include receiving, from a base station, first downlink control information (DCI) indicating a first uplink grant for a first physical uplink shared channel (PUSCH) transmission, where the first DCI includes a redundancy version (RV) corresponding to the first PUSCH transmission; determining whether the RV is capable of self-decoding; and determining whether to transmit an RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission based at least in part on the determination of whether the RV is self-decodable.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Application Serial No. 63 / 540,497, filed on September 26, 2023, entitled “TRANSMISSION OF RADIORESOURCE CONTROL RECONFIGURATION COMPLETE MESSAGE,” the contents of which are hereby incorporated by reference in their entirety. Background Art

[0003] Wireless communication networks such as the fourth generation (4G), fifth generation (5G), etc. provide integrated communication platforms and telecommunication services to wireless user devices. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols (such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP)). Exemplary 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).

[0004] User equipment (UE) can use radio resource control (RRC) signaling to establish a communication connection with an access node (e.g., a base station). Alignment at the RRC layer is used for connection because it configures parameters across layers (from the upper layers of signaling radio bearers (SRB) / data radio bearers (DRB) to the lower layers of the physical layer (PHY) / radio frequency (RF)). RRC signaling refers to the communication protocols and procedures used between the UE and the base station in a wireless communication system. RRC signaling is responsible for managing radio resources and controlling the establishment, maintenance, and release of connections between the UE and the network. Summary of the invention

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

[0006] Other aspects include UEs, devices, systems and computer programs for performing the aforementioned methods.

[0007] The innovative method may include other optional features. For example, in some implementations, determining whether the RV is self-decodable includes: determining that the RV is self-decodable; and determining to use the first uplink grant for the first PUSCH transmission to transmit the RRC reconfiguration complete message.

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

[0009] In some implementations, determining whether the RV is self-decodeable further comprises transmitting information different from the RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission.

[0010] In some specific implementations, the method also includes: before receiving the first DCI indicating the first uplink grant for the first PUSCH transmission, receiving a DCI indicating an uplink grant for PUSCH transmission from the base station; and suspending the PUSCH transmission corresponding to the DCI.

[0011] In some implementations, the RRC reconfiguration complete message is generated in response to RRC reconfiguration information for the communication connection received from the base station.

[0012] In some specific implementations, the method also includes: terminating the communication connection with the base station; receiving new RRC reconfiguration information for the new communication connection from the new base station; receiving new DCI indicating a new uplink authorization for a new PUSCH transmission from the new base station; suspending the new PUSCH transmission corresponding 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 a first new DCI indicating a first new uplink authorization for a first new PUSCH transmission from the new base station, 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, at least in part based on the determination of the new RV, whether to use the first new uplink authorization for the first new PUSCH transmission to transmit a new RRC reconfiguration completion message.

[0013] 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.

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

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

[0016] According to another innovative aspect of the present disclosure, a method for transmitting an RRC reconfiguration completion message performed by a base station is disclosed. In one aspect, the method may include: transmitting a first downlink control information (DCI) indicating a first uplink grant for transmission of a first physical uplink shared channel (PUSCH) to a user equipment (UE), wherein the first DCI includes a redundancy version (RV) corresponding to the transmission of the first PUSCH; transmitting a second DCI indicating a second uplink grant for transmission of a second PUSCH to the UE; in response to transmitting the second DCI, receiving the second PUSCH corresponding to the second DCI from the UE, 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.

[0017] Other aspects include base stations, devices, systems and computer programs for performing the aforementioned methods.

[0018] The innovative method may include other optional features. For example, in some specific implementations, the method further includes receiving the first PUSCH corresponding to the first DCI from the UE, wherein the first PUSCH includes information different from the RRC reconfiguration complete message.

[0019] In some specific implementations, the method also includes: transmitting a DCI indicating an uplink authorization for transmission of the PUSCH to the UE before transmitting the first DCI indicating the first uplink authorization for transmission of the first PUSCH; and detecting a failure to decode the PUSCH corresponding to the DCI.

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

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

[0022] In some implementations, the format of each DCI includes one of DCI format 0_0 or DCI format 0_1. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 An example wireless network according to some implementations is shown.

[0024] Figure 2A An example system frame illustrating an example process for transmitting an RRC reconfiguration complete message according to some implementations is shown.

[0025] Figure 2B About Figure 2A A flow chart of an exemplary process is disclosed.

[0026] Figure 2C is a flow chart of another exemplary process for transmitting an RRC reconfiguration complete message according to some implementations.

[0027] Figure 2D is a flow chart of another exemplary process for transmitting an RRC reconfiguration complete message according to some implementations.

[0028] Figure 2E is a flow chart of another exemplary process for transmitting an RRC reconfiguration complete message according to some implementations.

[0029] Figure 3 Another example process for transmitting an RRC reconfiguration complete message according to some implementations is shown.

[0030] Figure 4 An example process for transmitting an RRC reconfiguration complete message when the RV is not self-decodable according to some implementations is shown.

[0031] Figure 5 An example process for transmitting an RRC reconfiguration complete message during a handover procedure according to some implementations is shown.

[0032] Figure 6 An example process for transmitting an RRC reconfiguration complete message when the RV is self-decodable according to some implementations is shown.

[0033] Figure 7 An example process for transmitting an RRC reconfiguration complete message when the RV is self-decodable according to some implementations is shown.

[0034] Figure 8 Another example process for transmitting an RRC reconfiguration complete message during a handover procedure according to some implementations is shown.

[0035] Fig. 9 is a block diagram of an exemplary UE according to some specific implementations.

[0036] Fig.10 is a block diagram of an exemplary access node according to some implementations.

[0037] Fig.11 is a block diagram of an exemplary apparatus according to some implementations.

[0038] Like reference symbols in the various drawings indicate like elements. DETAILED DESCRIPTION

[0039] The present disclosure describes methods and systems for the transmission of a radio resource control (RRC) reconfiguration complete message, allowing the selection of a target physical uplink shared channel (PUSCH) for the RRC reconfiguration complete message based on a redundancy version (RV). In these methods and systems, a user equipment (UE) receives an RRC reconfiguration message from a base station for establishing a communication connection. When the RRC configuration is established at the UE, a target PUSCH with an RRC reconfiguration complete message will be transmitted to the base station. In some specific implementations, the UE may check the value of the RV included in the downlink control information (DCI) that schedules the first PUSCH. The RV value is indicated by 2 bits in the DCI, and it indicates the level of error correction redundancy applied to the transport block (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, before the transmission of the first PUSCH, the UE monitors the communication channel for any new DCI that schedules a new PUSCH. In this context, self-decodability refers to the property that the base station can decode the PUSCH based on a single transmission without combining the single transmission with other transmissions. The RV is indicated by 2 bits in the DCI and can have 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 include sufficient redundancy or error correction coding to allow independent decoding. Transmissions with other RV values ​​(RV 1 and RV 2) are generally not self-decodable (except at very low coding rates) because these transmissions do not include sufficient redundancy or error correction coding for independent decoding, causing the base station to rely on additional transmissions to decode the PUSCH by combining with these other transmissions. If there is a new DCI available before the transmission of the first PUSCH, the new PUSCH is selected as the target PUSCH. However, if there is no new DCI available before the transmission of the first PUSCH, the first PUSCH is selected as the target PUSCH. In other examples, the techniques of this disclosure describe processes for transmitting an RRC reconfiguration complete message in a target PUSCH that avoids retransmissions, thereby resulting in a reduction in the overall delay to complete the establishment of an RRC configuration.

[0040] Figure 1 An exemplary wireless network according to some implementations is shown. Wireless network 100 includes UE 102 and base station 104 connected via one or more channels 106A, 106B across air interface 108. UE 102 and base station 104 communicate using a system that supports control for managing access of UE 102 via base station 104 to the network.

[0041] In some implementations, the wireless network 100 may be a non-standalone (NSA) network that combines Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the Third Generation Partnership Project (3GPP) technical specifications. For example, the wireless network 100 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-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 combines 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 technologies (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE802.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.), etc. Although various aspects may be described herein using terms generally associated with 5G NR, various aspects of the present disclosure may be applied to other systems, such as 3G, 4G, and / or systems after 5G (e.g., 6G).

[0042] In the wireless network 100, the UE 102 and any other UE in the system may be, for example, a laptop computer, a smart phone, a tablet computer, a machine type device such as a smart meter or a dedicated device for healthcare, an intelligent transportation system, or any other wireless device 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). The UE 102 connectivity is provided via an air interface 108 in a base station service area provided by the base station 104. In some specific implementations, this wider network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with the base station 104 is supported by an antenna integrated with the base station 104. The service area is divided into a plurality of sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas, or may be assigned to a physical area with a tunable antenna or antenna setting that may be adjusted in a beamforming process for directing signals to a particular sector.

[0043] UE 102 includes control circuitry 110 coupled to transmit circuitry 112 and receive circuitry 114. Transmit circuitry 112 and receive circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry or front end module (FEM) circuitry.

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

[0045] The transmission circuit 112 may perform various operations described in this specification. In addition, the transmission circuit 112 may transmit a plurality of multiplexed uplink physical channels. The plurality of uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. The transmission circuit 112 may be configured to receive block data from the control circuit 110 for transmission across the air interface 108.

[0046] The receiving circuit 114 may perform various operations described in this specification. Additionally, the receiving circuit 114 may receive a plurality of multiplexed downlink physical channels from the air interface 108 and relay these physical channels to the control circuit 110. The plurality of downlink physical channels may be multiplexed according to TDM or FDM and carrier aggregation. The transmitting circuit 112 and the receiving circuit 114 may transmit and receive both control data and content data (e.g., messages, images, videos, etc.) structured within data blocks carried by the physical channels.

[0047] Figure 1 A base station 104 is also shown. In a specific implementation, the base station 104 can be an NG radio access network (RAN) or 5G RAN, E-UTRAN, non-terrestrial cell, or a traditional RAN such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to a base station 104 operating in an NR or 5G wireless network 100, and the term "EUTRAN" or the like may refer to a base station 104 operating in an LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each connection including a physical communication interface or layer.

[0048] The base station 104 circuitry may include control circuitry 116 coupled to transmit circuitry 118 and receive circuitry 120. The transmit circuitry 118 and receive circuitry 120 may each be coupled to one or more antennas that may be used to enable communication via the air interface 108. The transmit circuitry 118 and receive circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. The transmit circuitry 118 may transmit a downlink physical channel including a plurality of downlink subframes. The receive circuitry 120 may receive a plurality of uplink physical channels from various UEs including the UE 102.

[0049] exist Figure 1 In the figure, one or more channels 106A, 106B are shown as air interfaces for implementing communication coupling, and may comply with cellular communication protocols, such as GSM protocols, CDMA network protocols, UMTS protocols, 3GPP LTE protocols, Advanced Long Term Evolution (LTE-A) protocols, LTE-based unlicensed spectrum access (LTE-U), 5G protocols, NR protocols, NR-based unlicensed spectrum access (NR-U) protocols, and / or any of the other communication protocols discussed herein. In a specific implementation, UE 102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink control channel (PSCCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0050] RRC signaling process

[0051] UE (e.g. Figure 1 UE 102) uses RRC signaling to communicate with an access node (e.g., Figure 1 The RRC signaling process involves the UE receiving an RRC reconfiguration message (or RRC reconfiguration information) from the base station, locally verifying / applying parameters included in the RRC reconfiguration message at the UE, and transmitting an RRC reconfiguration complete message back to the base station, indicating that the RRC configuration has been established at the UE. The RRC signaling process can be used for initial RRC connection establishment and update of an RRC connection.

[0052] In some cases, during the RRC signaling process, due to the refreshed configured local UE adaptation from the RRC reconfiguration message, the processing of physical layer channels such as physical uplink shared channel (PUSCH) / physical downlink control channel (PDCCH) is suspended at the UE for a period of time. For example, the suspension may occur between the UE receiving an uplink grant from the base station and the UE transmitting a reconfiguration complete message to the base station. In some cases, the suspension includes the UE skipping the PUSCH scheduled during the adaptation period by an uplink grant (UL grant) specified by downlink control information (DCI). In some cases, the suspension includes the UE losing the DCI for the UL grant due to the closure of the PDCCH and therefore failing to know the scheduling of the PUSCH.

[0053] After completing the local RRC configuration, the UE transmits an RRC reconfiguration complete message to the base station. In some cases, the RRC reconfiguration complete message may be included in the PUSCH after the UE resumes its physical layer channel from the suspension. However, since the base station fails to decode (e.g., receive) the skipped PUSCH during the suspension period, the hybrid automatic repeat request (HARQ) mechanism of the base station requests retransmission of the skipped PUSCH. In some cases, the UE includes the RRC complete message in the retransmitted PUSCH.

[0054] Uplink HARQ transmission mechanism

[0055] DCI format 0_0 or 0_1 is used for PUSCH scheduling, and the base station specifies a redundancy version (RV) in the DCI payload. As previously noted, the value of the RV indicates the level of error correction redundancy applied to the transport block (TB) corresponding to the PUSCH scheduled by the DCI. The RV is selected from bits in the same TB based on rules defined by the specification. In the absence of HARQ combining, not all RVs may be self-decodable. DCI format 0_0 is used when only one UE is scheduled for uplink transmission. DCI format 0_1 ​​is used when multiple UEs associated with the same DCI message are scheduled for uplink transmission.

[0056] The duration between the DCI and the corresponding PUSCH may be included in the DCI payload as a K2 field, and the value of the duration refers to a lookup table defined in the RRC configuration. The duration may be in milliseconds, seconds, time slots in a subframe, etc. The duration between the first PUSCH and the subsequent retransmission (RETX) is dynamic, and the base station is flexible in scheduling. The K2 field may also carry additional control information or parameters related to downlink transmissions.

[0057] Transmission of RRC reconfiguration completion message for RV based on PUSCH

[0058] The RRC reconfiguration complete message is transmitted to the base station, confirming the configuration establishment at the UE. The payload size of the RRC reconfiguration complete message is small (typically less than 10 bytes) and it is sensitive to delay. When the RRC reconfiguration complete message is included in the PUSCH, the existing RRC signaling process does not check the value of the RV, so that the UE can transmit the RRC reconfiguration complete message in response to a DCI with an RV that cannot be self-decoded. This may cause the base station to receive a PUSCH with an RRC reconfiguration complete message that the base station cannot decode, causing the base station to transmit additional DCI for retransmission of the PUSCH. The end result is that the UE retransmits the PUSCH with the RRC reconfiguration complete message multiple times, increasing the overall delay in completing the establishment of the RRC connection.

[0059] The disclosed implementation describes a process of transmitting an RRC reconfiguration complete message in a PUSCH that avoids retransmissions, thereby resulting in a reduction in the overall delay to complete the establishment of the RRC configuration.

[0060] Figure 2A An example system frame illustrating an example process for transmitting an RRC reconfiguration complete message according to some implementations is shown. Figure 2B About Figure 2A Flowchart of an exemplary process 200 disclosed. In some implementations, process 200 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0061] refer to Figure 2A and Figure 2B In one exemplary process 200, a system frame / time slot is referred to as X / Y (Xth frame and Yth time slot). The duration of a time slot depends on the configuration of the frame structure. For example, in frequency division duplex (FDD) mode, a time slot may be 1 millisecond, while in time division duplex (TDD) mode, a time slot may be 0.5 milliseconds. Each frame may include multiple time slots, for example, ten time slots. At 202, in a first system frame (system frame 0), a UE (e.g., Figure 1 UE 102 or Fig. 9 UE 900) receives a signal from a base station (eg, Figure 1 Base station 104 or Fig.10The base station 1000 of the RRC reconfiguration message receives the RRC reconfiguration message and starts to verify / process the RRC reconfiguration message. At 204, the UE receives a first DCI (e.g., DCI 0_0 or DCI 0_1) including an uplink grant at 0 / 1 (system frame 0 / time slot 0), which schedules PUSCH transmission to the base station at 0 / 5 (system frame 0 / time slot 5, K2 time slots later). At 206, the UE adapts its local communication layer using the new RRC configuration as specified by the RRC reconfiguration message, thereby suspending uplink (UL) / downlink (DL) during the adaptation period from 0 / 3 (system frame 0 / time slot 3) to 0 / 7 (system frame 0 / time slot 7), and thus skipping the scheduled PUSCH at 0 / 5 (system frame 0 / time slot 5). At 208, the UE completes establishment of the new RRC configuration, locally generates an RRC reconfiguration complete message, and resumes UL / DL at 0 / 8 (system frame 0 / time slot 8). However, due to the earlier UL / DL suspension, no immediate UL resources are available for transmission of the PUSCH including the RRC reconfiguration complete message. At 210, the UE receives another DCI at 0 / 9 (system frame 0 / time slot 9) that schedules a PUSCH at 1 / 3 (system frame 1 / time slot 3), which is a retransmission of the previously skipped PUSCH at 0 / 5 (system frame 0 / time slot 5). At 212, without checking the RV corresponding to the DCI at 0 / 9 (system frame 0 / time slot 9) (e.g., the DCI includes a bit field indicating the RV), the UE adds the RRC reconfiguration complete message to the PUSCH transmitted at 1 / 3 (system frame 1 / time slot 3). If the RV is not RV0 or RV3, there will be a base station decoding failure at the base station to decode the RRC reconfiguration complete message received in the PUSCH at 1 / 3 (system frame 1 / time slot 3). At 214, the decoding failure causes the base station to transmit another DCI at 1 / 7 (system frame 1 / time slot 7), requesting the PUSCH to be retransmitted using the same HARQ ID. At 216, in response to the DCI at 1 / 7 (system frame 1 / time slot 7), the UE performs a second retransmission of the PUSCH at 2 / 1 (system frame 2 / time slot 1). In some specific implementations, the base station can correctly decode the reconfiguration complete message by combining the PUSCH at 1 / 3 (system frame 1 / time slot 3) + 2 / 1 (system frame 2 / time slot 1). In some implementations, the base station still fails to decode the reconfiguration complete message through the combined PUSCH at 1 / 3 (system frame 1 / time slot 3) + 2 / 1 (system frame 2 / time slot 1) and requests one or more additional retransmissions.

[0062] Figure 2C2 is a flow chart of another exemplary process 200C for transmitting an RRC reconfiguration complete message according to some implementations. In some implementations, the process 200C is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0063] refer to Figure 2A and Figure 2C , the UE performs a modified RRC signaling procedure 200C that reduces the number of transmissions. Block 210C is Figure 2B The same as box 210 of . 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). After such determination, the UE monitors the communication channel (e.g., L1 / L2 control channel) for any new DCI from the base station between the time of the DCI at 0 / 9 and the scheduled time of retransmission of the PUSCH at 1 / 3. The UE receives the new DCI at 1 / 1 that schedules the new PUSCH at 1 / 5. 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 RRC reconfiguration complete message to the new PUSCH transmitted at 1 / 5. At 216C, in order to avoid waste of resources, the UE adds other data to the PUSCH transmitted at 1 / 3. The other data can be any data other than the RRC reconfiguration complete message. Although the initial transmission time for the RRC reconfiguration complete message is delayed by two time slots (compared to the retransmission at 1 / 3), the new PUSCH at 1 / 5 can be successfully decoded by the base station, so that there is no additional retransmission of the RRC reconfiguration complete message. Therefore, the overall delay is reduced. If no new DCI is received between the time of the DCI at 0 / 9 and the scheduled time of the retransmission of the PUSCH at 1 / 3, the UE performs a retransmission at 1 / 3, which is the same as block 212.

[0064] Figure 2D 2 is a flow chart of another exemplary process 200D for transmitting an RRC reconfiguration complete message according to some implementations. In some implementations, the process 200D is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0065] refer to Figure 2A and Figure 2D , the UE performs a modified RRC signaling procedure 200D that reduces the number of transmissions. Blocks 202D to 210D are related to Figure 2BThe same as boxes 202 to 210 of . At 212D, 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). After such determination, the UE monitors the communication channel (e.g., L1 / L2 control channel) for any new DCI from the base station between the time of the DCI at 0 / 9 and the scheduled time of retransmission of the PUSCH at 1 / 3. The UE receives the new DCI at 1 / 1 that schedules the new PUSCH at 1 / 5. 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 RRC reconfiguration complete message to the new PUSCH transmitted at 1 / 5. At 216D, in order to avoid waste of resources, the UE adds other data to the PUSCH transmitted at 1 / 3. The other data can be any data other than the RRC reconfiguration complete message. Although the initial transmission time for the RRC reconfiguration complete message is delayed by two time slots (compared to the retransmission at 1 / 3), the new PUSCH at 1 / 5 can be successfully decoded by the base station, so that there is no additional retransmission of the RRC reconfiguration complete message. Therefore, the overall delay is reduced. If no new DCI is received between the time of the DCI at 0 / 9 and the scheduled time of the retransmission of the PUSCH at 1 / 3, the UE performs a retransmission at 1 / 3, which is the same as block 212.

[0066] Figure 2E is a flow chart of another exemplary process 200E for transmitting an RRC reconfiguration complete message according to some implementations. In some implementations, the process 200E is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0067] At 202E, the UE receives a first DCI from the base station indicating a first uplink grant for a first PUSCH transmission. 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 an RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission based at least in part on the determination of whether the RV is self-decodable.

[0068] If it is determined that the RV is self-decodeable, the UE transmits an RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission. For example, the UE adds the RRC complete message to the first PUSCH and transmits the first PUSCH including the RRC complete message to the base station.

[0069] If it is determined that the RV is not self-decodable, the UE receives a second DCI indicating a second uplink grant for a second PUSCH transmission from the base station. The UE transmits an RRC reconfiguration complete message using the second uplink grant for the second PUSCH transmission. The UE uses the first uplink grant for the first PUSCH transmission to transmit information different from the RRC reconfiguration complete message. For example, the UE adds the RRC complete message to the second PUSCH and transmits the second PUSCH including the RRC complete message to the base station. The UE adds information different from the RRC reconfiguration complete message to the first PUSCH and transmits the first PUSCH including the RRC complete message to the base station.

[0070] Figure 3 Another exemplary process 300 for transmitting an RRC reconfiguration complete message according to some implementations is shown. In some implementations, the process 300 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0071] At 302, the UE determines that there is a generated RRC completion message and a pending transmission. At 304, the UE sets the first available PUSCH for the first retransmission (as scheduled by the first DCI) 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 execute box 312. If the RV of the PUSCH is not self-decodable, the selection mechanism is initiated. At 308, the UE checks whether the new DCI corresponding to the new PUSCH that can be self-decoded appears in the duration between receiving the first available DCI and the first retransmission corresponding to it. If no new DCI appears in between, the UE proceeds to execute box 312. If a new DCI appears in between, 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 including the RRC completion message to the base station.

[0072] The disclosed techniques provide a mechanism for selecting a target PUSCH based on an RV value to transmit an RRC reconfiguration complete message. Advantages of the disclosed techniques include transmitting a new PUSCH to reduce delays caused by retransmissions of the PUSCH due to non-decodable RVs, while providing fallback when no new PUSCH is available.

[0073] Figure 4An exemplary process for transmitting an RRC reconfiguration complete message when the RV is not self-decodable according to some implementations is shown. In some implementations, process 400 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE900 executes.

[0074] In process 400, at 402, the UE receives RRC reconfiguration information for a communication connection from a base station. RRC reconfiguration information refers to information received during an RRC reconfiguration process in a wireless communication system at a base station (such as Figure 1 Base station 104 or Fig.10 A set of parameters and configuration updates exchanged between a base station 1000 and a UE. RRC reconfiguration is a process that allows a base station to modify or update the configuration of an established RRC connection with a UE. This may include changes to radio resource allocations, mobility-related parameters, handover settings, security parameters, and other network-specific configuration updates.

[0075] At 404, the UE receives a first DCI including an uplink (UL) grant. An uplink grant refers to a resource allocation and permission given by a base station to a UE to transmit data on an uplink channel. An uplink grant specifies resources, such as a time slot, frequency band, and modulation scheme, that the UE can utilize to transmit its data to the base station.

[0076] At 406, in response to receiving the RRC reconfiguration information, the UE suspends transmission of the first PUSCH scheduled by the first DCI. Due to the refreshed configured local UE adaptation from the RRC reconfiguration message, the UE suspends transmission of the first PUSCH for a period of time. Transmission of the first PUSCH is skipped during the suspension period.

[0077] At 408, during the suspension, the UE adapts the RRC configuration for the communication connection based at least on the RRC reconfiguration information.

[0078] At 410, the UE receives a second DCI scheduling retransmission of the first PUSCH from the base station. 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.

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

[0080] At 414, the UE receives a third DCI scheduling a new PUSCH from the base station prior to transmission of the first PUSCH as scheduled by the second DCI. The UE receives the third DCI in a duration between receiving the second DCI and transmitting the first PUSCH.

[0081] 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 complete message to the new PUSCH and initiates transmission of the new PUSCH including the RRC reconfiguration complete message as scheduled by the third DC.

[0082] At step 418, the UE adds other data (eg, information different from the RRC reconfiguration complete message) to the first PUSCH; and initiates transmission of the first PUSCH as scheduled by the second DCI.

[0083] Figure 5 An exemplary process for transmitting an RRC reconfiguration complete message during a handover process according to some implementations is shown. In some implementations, process 500 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0084] In process 500, at 502, the UE terminates a communication connection with a current base station. As the UE moves, the network initiates a handover when it determines that the signal from the current base station is weakening or degrading. The UE terminates the communication connection with the current base station and is ready to establish a communication connection with a new base station. A handover (also known as handoff) is a process in a cellular network where an ongoing call or data session is seamlessly transferred from one base station to another as the user moves through coverage areas. The purpose of a handover is to maintain the continuity of a communication session without interruption or loss of quality.

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

[0086] At 506, the UE receives a new DCI including a new uplink grant.

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

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

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

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

[0091] At 516, upon receiving the second new DCI and in response to determining that the RV is self-decodeable, the UE adds a new RRC reconfiguration complete message for the new communication connection to the second new PUSCH and initiates transmission of the second new PUSCH as scheduled by the second new DCI.

[0092] Figure 6 An exemplary process for transmitting an RRC reconfiguration complete message when the RV is self-decodable according to some implementations is shown. In some implementations, process 600 is described as being performed by a base station such as Figure 1 Base station 104 or Fig.10 The base station 1000 executes.

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

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

[0095] At 606, the base station detects a failure to decode the first PUSCH as scheduled by the first DCI because the first PUSCH was not received due to a pause at the UE. The pause occurred during a refreshed configured adaptation period from the RRC reconfiguration message.

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

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

[0098] In response to transmitting the third DCI, the base station receives a new PUSCH from the UE as scheduled by the third DCI at 612. The new PUSCH includes an RRC reconfiguration complete message.

[0099] The base station also receives the first PUSCH as scheduled by the second DCI at 614. The first PUSCH includes other data (eg, information different from the RRC reconfiguration complete message) to avoid resource waste.

[0100] Figure 7 An exemplary process for transmitting an RRC reconfiguration complete message when the RV is self-decodable according to some implementations is shown. In some implementations, process 700 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE900 executes.

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

[0102] At 704, the UE receives a first DCI including an uplink grant.

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

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

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

[0106] The UE determines that the RV is self-decodable at 712. The UE identifies that the RV value is RV 0 or RV 3.

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

[0108] Figure 8 Another exemplary process for transmitting an RRC reconfiguration complete message during a handover process according to some implementations is shown. In some implementations, process 800 is described as being performed by a UE such as Figure 1 UE 102 or Fig. 9 UE 900 executes.

[0109] In process 800, at 802, a UE terminates a communication connection with a base station.

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

[0111] At 806, the UE receives a new DCI including a new uplink grant from the new base station.

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

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

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

[0115] The UE determines that the new RV is not self-decodable at 814. The UE identifies whether the new RV value is RV 1 or RV 2.

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

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

[0118] At 820, the UE adds other data (eg, information different from the new RRC reconfiguration complete message) to the second new PUSCH and initiates transmission of the second new PUSCH as scheduled by the second new DCI.

[0119] Fig. 9 is a block diagram of an exemplary UE according to some specific implementations. UE 900 may be similar to Figure 1 UE 102 and is substantially interchangeable therewith.

[0120] UE 900 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video monitoring / surveillance equipment (e.g., camera, camcorder, etc.), a wearable device (e.g., a smart watch), or a loose IoT device.

[0121] UE 900 may include a processor 902, RF interface circuitry 904, memory / storage 906, a user interface 908, a sensor 910, a driver circuit 912, a power management integrated circuit (PMIC) 914, antenna structures 916, and a battery 918. The components of UE 900 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig. 9The block diagram of UE 900 is intended to show a high-level view of certain of the components of UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0122] 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, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0123] The processor 902 may include processor circuits such as, for example, a baseband processor circuit (BB) 922A, a central processor unit circuit (CPU) 922B, and a graphics processor unit circuit (GPU) 922C. The processor 902 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 906) to cause the UE 900 to perform operations as described herein.

[0124] In some implementations, the baseband processor circuit 922A may access a communication protocol stack 924 in the memory / storage device 906 to communicate over a 3GPP compatible network. Generally speaking, the baseband processor circuit 922A may access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some implementations, the PHY layer operations may be additionally / alternatively performed by components of the RF interface circuit 904. The baseband processor circuit 922A may generate or process a baseband signal or waveform that carries information in a 3GPP compatible network. In some implementations, the waveform for NR may be based on cyclic prefix OFDM "CP-OFDM" in the uplink or downlink, and discrete Fourier transform spread OFDM "DFT-S-OFDM" in the uplink.

[0125] The memory / storage 906 may include one or more non-transitory computer-readable media including instructions (e.g., a communication protocol stack 924) that may be executed by one or more processors in the processor 902 to enable 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 specific implementations, some of the memory / storage 906 may be located on the processor 902 itself (e.g., L1 cache and L2 cache), while other memory / storage 906 are located outside the processor 902 but can be accessed 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 memory device technology.

[0126] The RF interface circuit 904 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 900 to communicate with other devices through a radio access network. The RF interface circuit 904 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0127] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 916 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a receiver of the transceiver, which down-converts the RF signal to a baseband signal provided to a baseband processor of the processor 902.

[0128] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 916.

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

[0130] Antenna 916 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 916 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. Antenna 916 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 916 may have one or more panels that are designed for a specific frequency band included in a band in FR1 or FR2.

[0131] The user interface 908 includes various input / output (I / O) devices designed to enable the user to interact with the UE 900. The user interface 908 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 900.

[0132] Sensor 910 may include a device, module, or subsystem whose purpose is to detect events or changes in its environment and to communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0133] The driver circuit 912 may include software elements and hardware elements for controlling specific devices embedded in the UE 900, attached to the UE 900, or otherwise communicatively coupled to the UE 900. The driver circuit 912 may include separate drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in the UE 900 or connected to the UE. For example, the driver circuit 912 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor 910 and controlling and allowing access to the sensor 910, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0134] The PMIC 914 may manage power provided to various components of the UE 900. Specifically, with respect to the processor 902, the PMIC 914 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0135] In some implementations, the PMIC 914 may control or otherwise be part of various power saving mechanisms of the UE 900, including DRX, as discussed herein. The battery 918 may power the UE 900, but in some examples, the UE 900 may be installed or deployed in a fixed location and may have a power source coupled to the 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, etc.). In some implementations, such as in vehicle-based applications, the battery 918 may be a typical lead-acid automotive battery.

[0136] Fig.10 is a block diagram of an exemplary access node according to some implementations. Fig.10 An access node 1000 (e.g., a base station or gNB) according to some implementations is shown. The access node 1000 may be similar to Figure 1 The access node 1000 may include a processor 1002, an RF interface circuit 1004, a core network (CN) interface circuit 1006, a memory / storage device circuit 1008, and an antenna structure 1010.

[0137] The components of access node 1000 may be coupled to various other components via one or more interconnects 1012. Processor 1002, RF interface circuitry 1004, memory / storage circuitry 1008 (including communication protocol stack 1014), antenna structures 1010, and interconnects 1012 may be similar to those of reference 1000. Fig. 9 Like-named elements are shown and described.For example, processor 1002 may include processor circuits such as, for example, baseband processor circuit (BB) 1016A, central processor unit circuit (CPU) 1016B, and graphics processor unit circuit (GPU) 1016C.

[0138] The CN interface circuit 1006 may provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the access node 1000 via optical fiber or wireless backhaul. The CN interface circuit 1006 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1006 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0139] As used herein, the terms "access node", "access point", etc. may be described as equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, 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 terms "NG RAN node", etc. may refer to an access node 1000 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node", etc. may refer to an access node 1000 (e.g., an eNB) operating in an LTE or 4G system. According to various specific implementations, the access node 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 a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0140] In some implementations, all or part of the access node 1000 may be implemented as one or more software entities running on a server computer as part of a virtual network that 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 split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by the access node 1000; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by the access node 1000; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP and the lower portions of the PHY layers are operated by the access node 1000.

[0141] In the V2X scenario, the access node 1000 may be an RSU or act as an RSU. The term "road side unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationed (or relatively stationed) UE, wherein 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 so on.

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

[0143] As shown, the device 1100 includes one or more processors 1116A and 1116B and a memory / storage device 1108 that stores instructions 1114 that are executed by the one or more processors 1116A and 1116B. Fig.11 Device 1100 is shown as having multiple processors, but in some cases device 1100 may include a single processor (eg, one of processor 1116A or processor 1116B).

[0144] The device 1100 is electrically and communicatively coupled to the RF circuit 1104 and the associated antenna structure 1110 via the RF interface 1112. In some implementations, one or more of the processors 1116A and 1116B execute instructions 1114 to control communications through the RF interface circuit 1104 and the antenna structure 1110. For example, one or more of the processors 1116A and 1116B may execute instructions 1114 to generate or process baseband signals or waveforms that carry information using a wireless channel, and / or manage radio functions of the RF circuit 1104 and the antenna structure 1110, such as signal modulation, coding, and radio frequency shifting, as described in connection with the present invention. Fig. 9 The baseband processor circuit 922A and Fig.10 The baseband processor circuit 1016A may be used in addition to or in place of the user plane or control plane functionality described herein. In doing so, the apparatus 1100 enables communications over a 3GPP compatible network, such as wireless cellular communications.

[0145] Additionally, in some implementations, the device 1100 may include a device for transmitting data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), The instructions 1114 may include a wireless hardware connection interface for transmitting / receiving data between the 802.11 components and other communication components, and a power management interface (e.g., an interface for transmitting / receiving power). In such a specific implementation, the instructions 1114 may include instructions that, when executed by one or more of the processors 1116A and 1116B, cause the processors to perform Wi-Fi communications on an 802.11 network and / or perform Bluetooth communications.

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

[0147] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Representing a component configured to perform one or more tasks expressly intends that the component does not invoke 35 U.S.C. §112(f) of the interpretation.

[0148] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0149] Example

[0150] In the following sections, additional exemplary embodiments are provided.

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

[0152] Embodiment 2 includes a method according to embodiment 1, wherein determining whether the RV is self-decodable comprises: determining that the RV is self-decodable; and determining to transmit the RRC reconfiguration completion message using the first uplink grant for the first PUSCH transmission.

[0153] Embodiment 3 includes a method according to embodiment 1 or 2, wherein determining whether the RV is capable of self-decoding includes: determining that the RV is not capable of self-decoding; receiving a second DCI indicating a second uplink grant for a second PUSCH transmission from the base station; and transmitting the RRC reconfiguration completion message using the second uplink grant for the second PUSCH transmission.

[0154] Embodiment 4 includes the method of embodiment 3, wherein determining whether the RV is self-decodeable further comprises transmitting information different from the RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission.

[0155] Embodiment 5 includes the method described in any one of Embodiments 1 to 4, and the method further includes: before receiving the first DCI indicating the first uplink authorization for the first PUSCH transmission, receiving a DCI indicating an uplink authorization for PUSCH transmission from the base station; and suspending the PUSCH transmission corresponding to the DCI.

[0156] Embodiment 6 includes the method of any one of Embodiments 1 to 5, wherein the RRC reconfiguration complete message is generated in response to RRC reconfiguration information for a communication connection received from the base station.

[0157] Embodiment 7 includes the method described in any one of Embodiments 1 to 6, and the method further includes: terminating the communication connection with the base station; receiving new RRC reconfiguration information for the new communication connection from the new base station; receiving new DCI indicating a new uplink authorization for a new PUSCH transmission from the new base station; suspending the new PUSCH transmission corresponding 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 a first new DCI indicating a first new uplink authorization for a first new PUSCH transmission from the new base station, 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 use the first new uplink authorization for the first new PUSCH transmission to transmit a new RRC reconfiguration completion message based at least in part on the determination of the new RV.

[0158] Embodiment 8 includes the method of any one of Embodiments 1 to 7, wherein 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.

[0159] Embodiment 9 includes the method of any one of Embodiments 1 to 8, wherein the first DCI comprises a duration between receiving the first DCI and the first PUSCH transmission.

[0160] Embodiment 10 includes the method of any one of Embodiments 1 to 9, wherein the format of each DCI includes one of DCI format 0_0 or DCI format 0_1.

[0161] Embodiment 11 includes one or more processors of a device, wherein the one or more processors are configured to perform the method of any one of embodiments 1 to 10.

[0162] Embodiment 12 includes an apparatus comprising: one or more processors; and one or more memory devices, wherein the one or more memory devices store instructions that, when executed, cause the one or more processors to perform the method described in any one of Embodiments 1 to 10.

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

[0164] Embodiment 14 includes the method of embodiment 13, further comprising: receiving the first PUSCH corresponding to the first DCI from the UE, wherein the first PUSCH includes information different from the RRC reconfiguration complete message.

[0165] Embodiment 15 includes the method described in Embodiment 13 or 14, and the scheme further includes: transmitting a DCI indicating an uplink authorization for transmission of the PUSCH to the UE before transmitting the first DCI indicating the first uplink authorization for transmission of the first PUSCH; and detecting a failure to decode the PUSCH corresponding to the DCI.

[0166] Embodiment 16 includes the method of any one of Embodiments 13-15, wherein the RV includes one of RV 1 or RV 2.

[0167] Embodiment 17 includes the method of any one of Embodiments 13-16, wherein the second DCI includes one of RV 0 or RV 3.

[0168] Embodiment 18 includes the method of any one of Embodiments 13 to 17, wherein the format of each DCI comprises one of DCI format 0_0 or DCI format 0_1.

[0169] Embodiment 19 includes one or more processors of a device, wherein the one or more processors are configured to perform the method of any one of embodiments 13 to 18.

[0170] Embodiment 20 includes an apparatus comprising: one or more processors; and one or more memory devices, wherein the one or more memory devices store instructions that, when executed, cause the one or more processors to perform the method described in any one of Embodiments 13 to 18.

[0171] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended to not invoke 35 USC § 112 (f) interpretation of that component.

[0172] For one or more specific implementations, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0173] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the specific implementations to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from the practice of various specific implementations.

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

[0175] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A method, comprising: Receiving first downlink control information DCI from a base station, the first DCI indicating a first uplink grant for a first physical uplink shared channel PUSCH transmission, wherein the first DCI includes a redundancy version RV corresponding to the first PUSCH transmission; determining whether the RV is self-decodable; as well as Based at least in part on the determination of whether the RV is self-decodeable, determining whether to transmit a radio resource control, RRC, reconfiguration complete message using the first uplink grant for the first PUSCH transmission.

2. The method of claim 1 , wherein determining whether the RV is self-decodable comprises: Determining that the RV is self-decodable; as well as Determining to transmit the RRC reconfiguration complete message using the first uplink grant for the first PUSCH transmission.

3. The method of claim 1 , wherein determining whether the RV is self-decodable comprises: determining that the RV is not self-decodable; receiving a second DCI from the base station, the second DCI indicating a second uplink grant for a second PUSCH transmission; as well as The RRC reconfiguration complete message is transmitted using the second uplink grant 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 complete message using the first uplink grant for the first PUSCH transmission.

5. The method according to claim 1, further comprising: receiving, before receiving the first DCI indicating the first uplink grant for the first PUSCH transmission, a DCI indicating an uplink grant for a PUSCH transmission from the base station; as well as The PUSCH transmission corresponding to the DCI is suspended.

6. The method of claim 1, wherein the RRC reconfiguration complete message is generated in response to RRC reconfiguration information for a communication connection received from the base station.

7. The method according to claim 1, further comprising: terminating the communication connection with 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 grant for a new PUSCH transmission; Suspending the new PUSCH transmission corresponding to the new DCI; configuring, during the suspension, 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 grant 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; as well as Based at least in part on the determination of the new RV, a determination is made as to whether to transmit a new RRC reconfiguration complete message using the first new uplink grant for the first new PUSCH transmission. 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 the format of each DCI comprises one of DCI format 0_0 or DCI format 0_1.

11. One or more processors of an apparatus, the one or more processors being configured to perform the method according to claim 1.

12. A device, comprising: one or more processors; and One or more memory devices storing instructions which, when executed, cause the one or more processors to perform the method of claim 1.

13. A method comprising: Transmitting first downlink control information DCI to a user equipment UE, the first DCI indicating a first uplink grant 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 grant for transmission of a second PUSCH; In response to transmitting the second DCI, receiving the second PUSCH corresponding to the second DCI from the UE, wherein the second PUSCH includes an RRC reconfiguration complete message generated in response to RRC reconfiguration information for a communication connection, wherein the RRC reconfiguration complete message is included in the second PUSCH based on the UE determining that the RV is not self-decodable.

14. The method according to claim 13, further comprising: The first PUSCH corresponding to the first DCI is received from the UE, wherein the first PUSCH includes information different from the RRC reconfiguration complete message.

15. The method according to claim 13, further comprising: before transmitting the first DCI indicating the first uplink grant for transmission of the first PUSCH, transmitting to the UE a DCI indicating an uplink grant for transmission of the PUSCH; as well as A failure in decoding the PUSCH corresponding to the DCI is detected. The method of claim 13 , wherein the RV comprises one of RV 1 or RV 2. The method of claim 13 , wherein the second DCI comprises one of RV 0 or RV 3.

18. The method of claim 13, wherein the format of each DCI comprises one of DCI format 0_0 or DCI format 0_1.

19. One or more processors of an apparatus, the one or more processors being configured to perform the method of claim 13.

20. A device, comprising: one or more processors; and One or more memory devices storing instructions which, when executed, cause the one or more processors to perform the method of claim 13.

Images