Baseband processor, ue device, and method for non-active direct transmission from user equipment (UE) via random access channel (RACH) procedure

Abstract

The techniques discussed herein facilitate inactive state transmission of user equipment (UE) via a 4-step or 2-step inactive state RACH process. An exemplary aspect is a UE device comprising: a communication circuit; and a processor configured to perform operations including: in response to determining to perform Radio Resource Control (RRC) inactive data transmission: transmitting a message 1 (Msg1) or message A (MsgA) preamble via the communication circuit based on a Random Access Channel (RACH) configuration for the RRC inactive data transmission; transmitting a message 3 (Msg3) or MsgA Physical Uplink Shared Channel (PUSCH) containing uplink (UL) data via configured resources via the communication circuit; and receiving a message 4 (Msg4) or message B (MsgB) via the communication circuit in response to the Msg3 or MsgA PUSCH.

Description

Background Technology

[0001] Next-generation wireless communication systems, such as 5G or New Radio (NR) networks, will provide ubiquitous connectivity and access to information and the ability to share data globally. 5G networks and network slicing will be a unified, service-based framework that aims to meet common and sometimes conflicting performance standards and serve an extremely diverse range of application domains, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and others. Generally, NR will evolve based on 3GPP Long Term Evolution (LTE) Advanced technologies and additional Enhanced Radio Access Technologies (RATs) to achieve seamless and faster wireless connectivity solutions. Attached Figure Description

[0002] Figure 1 It is a state diagram showing the three radio resource control (RRC) states in which equipment such as user equipment (UE) can operate.

[0003] Figure 2 This illustrates an exemplary Radio Resource Control (RRC) recovery process for a UE that is in an inactive state.

[0004] Figure 3A The four-step contention-based random access channel (RACH) (CBRA) process is shown.

[0005] Figure 3B The 2-step CBRA process is shown.

[0006] Figure 4A The delay in data transmission during the transition of a UE from an inactive state to a connected state is shown.

[0007] Figure 4B This illustrates the latency in data transmission of a UE performing direct data transmission to a base station (BS) when inactive.

[0008] Figure 5A A flowchart is shown for a method of conducting inactive state communication between a BS and a UE using a radio link quality threshold.

[0009] Figure 5B A flowchart is shown for a method of inactive state communication between a BS and a UE using a radio link timing threshold.

[0010] Figure 6A A flowchart is shown for a method of performing 4-step RACH inactive state communication between the BS and UE using a repetition scheme.

[0011] Figure 6B A flowchart is shown for a method of performing two-step RACH inactive state communication between the BS and UE using a repetition scheme.

[0012] Figure 7A A flowchart is shown for a method for 4-step RACH inactive state communication between the BS and the UE, wherein the RACH and the UE are distinguished based on the Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI.

[0013] Figure 7B A flowchart is shown for a method for two-step RACH inactive state communication between the BS and the UE, wherein the RACH and the UE are distinguished based on the I-RNTI or a truncated I-RNTI.

[0014] Figure 8A A flowchart is shown for a method to perform 4-step RACH inactive state communication between the BS and UE using feedback from successful transmission.

[0015] Figure 8B A flowchart is shown for a method to perform two-step RACH inactive state communication between the BS and UE using feedback from successful transmission.

[0016] Figure 9A A flowchart is shown of a method for RACH inactive state communication between the BS and UE by using the fallback mechanism of the RRC recovery process to make the RACH process fail or reach the physical RACH (PRACH) retransmission value.

[0017] Figure 9B A flowchart is shown of a method for RACH inactive state communication between BS and UE by using the fallback mechanism of the RRC recovery process when the radio quality threshold is not reached.

[0018] Figure 10 This is a flowchart for RRC inactive data transmission for UE.

[0019] Figure 11 This is a flowchart for RRC inactive data transfer used in BS.

[0020] Figure 12 This is a flowchart for using the rollback mechanism of the RRC recovery process to perform RRC inactive data transmission for the UE.

[0021] Figure 13 This is a block diagram illustrating the architecture of a system, including the core network (CN) (e.g., fifth-generation (5G) CN (5GC)), based on various aspects.

[0022] Figure 14This is an illustration showing exemplary components of a device that may be employed according to the various aspects discussed herein.

[0023] Figure 15 This is a diagram illustrating an exemplary interface of a baseband circuit that may be employed according to the various aspects discussed herein.

[0024] Figure 16 This is a block diagram illustrating a system that combines a wireless modem to facilitate power management according to the various aspects discussed herein. Detailed Implementation

[0025] This disclosure will now be described with reference to the accompanying drawings, in which similar reference numerals are used throughout to denote similar elements, and the structures and devices shown are not necessarily drawn to scale. As used herein, the terms “component,” “system,” “interface,” etc., are intended to refer to entities, hardware, software (e.g., in execution), and / or firmware related to a computer. For example, a component can be a processor (e.g., a microprocessor, controller, or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer, and / or user equipment with processing capabilities (e.g., a mobile phone or other device configured to communicate via 3GPP RAN, etc.). By way of example, an application running on a server and a server can also be components. One or more components may reside in a process, and components may be located on a single computer and / or distributed among two or more computers. A group of elements or a group of other components may be described herein, wherein the term “group” may be interpreted as “one or more” unless the context otherwise indicates (e.g., “empty group,” “a group of two or more Xs,” etc.).

[0026] Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored, such as by utilizing modules, for example. Components can communicate via local and / or remote processes, for example, based on signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or throughout a network, such as the Internet, a local area network, a wide area network, or similar networks with other systems via signals).

[0027] For example, a component can be a device with a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry can be operated by a software application or firmware application executed by one or more processors. The one or more processors can be internal or external to the device and can execute at least a portion of the software or firmware application. As another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component may include one or more processors to execute software and / or firmware that at least partially endows the electronic component with that function.

[0028] The use of the term “exemplary” is intended to present the concept in a specific manner. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise stated or clearly apparent from the context, “X adopts A or B” is intended to mean any natural inclusive arrangement. That is, “X adopts A or B” is satisfied if X adopts A; X adopts B; or X adopts both A and B. Additionally, the articles “a” and “an” used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise stated or clearly apparent from the context to refer to the singular form. Furthermore, to the extent that the terms “comprising,” “including,” “having,” “having,” “with,” or variations thereof are used in the Detailed Description and Claims, such terms are intended to be included in a manner similar to the term “comprising.” Furthermore, in the context of discussing one or more numbered items (e.g., “first X,” “second X,” etc.), generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0029] As used herein, the term "circuit" may refer to, be part of, or may include: an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functions. In some aspects, a circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include logic components that operate at least partially in hardware.

[0030] The various aspects discussed in this article may involve facilitating wireless communication, and the nature of these communications may vary.

[0031] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

[0032] A key aspect of wireless devices is their ability to enter a low-power state when not involved in data transmission or reception. By entering a low-power state, devices can achieve a balance between acceptable communication performance, acceptable battery consumption, and resource management. Consequently, devices have evolved from initially supporting idle and connected transition states to now including paused and inactive transition states that improve latency and optimize battery consumption.

[0033] The primary purpose of the inactive state is to enable devices to return to the connected state and establish data communication as efficiently and quickly as possible. To facilitate a smooth transition between the connected and inactive states, information, such as identifiers and security information, is transferred between the device and the network before the device enters the inactive state. This stored information is then used to facilitate a smooth transition from the inactive to the connected state.

[0034] While inactivity improves latency and optimizes battery consumption, latency and battery consumption costs still exist in existing systems when user equipment (UE) transmits uplink (UL) or downlink (DL) data over the network. Resources, time, and battery consumption are spent on state transitions so that the UE can perform any dedicated transmission or reception according to existing technologies. Therefore, to achieve further optimization of devices and networks, data transmission is required when the device is inactive.

[0035] Various aspects of this disclosure relate to novel radio (NR) devices capable of data transmission and reception while the device is in an idle state and has not transitioned to a connected state. One way to establish data communication while in an idle state is by using a random access channel (RACH) procedure configured for inactive direct data transmission with large packet sizes. In doing so, data up to a size associated with inactive data limits can be transmitted in the inactive state. Various aspects can facilitate inactive data transmission according to one or more advantageous features discussed in this disclosure. The features discussed herein in conjunction with inactive direct data transmission enable one or more of the following: large packet sizes, efficient data transmission, differentiation of RACH configurations for device states, differentiation of RACH for inactive devices, support for feedback from inactive devices, and fallback to the recovery process when appropriate.

[0036] Figure 1This is a state diagram illustrating the three Radio Resource Control (RRC) states in which a device such as a UE can operate. In the idle state, the UE disconnects from the core network (CN). While idle, the UE performs cell reselection and can receive paging messages from the CN through the cell on which the UE camps. To enter the connected state, the UE performs RRC connection procedure 110, where the UE uses the RACH procedure (described in more detail below) to connect to the CN and the Radio Access Network (RAN). In the connected state, the UE connects to the CN and registers with the CN. A control and user plane connection is established between the RAN and the CN for the UE. The RAN knows which cell the UE belongs to, and all parameters necessary for unicast communication between the UE and the RAN are known to both the UE and the RAN. The UE context, including the UE's access layer (AS) context (e.g., the UE's Cell Radio Network Temporary Identifier (C-RNTI) and the cell identifier of the primary cell) and the UE's RRC configuration (e.g., radio bearer and security information), are stored in the RAN and also in the UE.

[0037] From the connected state, the UE can move back to the idle state by executing RRC release procedure 120. When the UE returns to the idle state, the UE context is removed from both the UE and the RAN. The UE can also default to the idle state from the connected or inactive state when no cell for camping can be found, as indicated by 130 and 160.

[0038] In 5G, an inactive state is introduced to provide an intermediate state between idle and connected states. This intermediate state accelerates the reconnection process by eliminating some of the signaling used to transition from idle to connected states. The inactive state is beneficial for UEs that do not communicate frequently with the RAN and allows for power savings compared to these UEs remaining in a connected state. To enter the inactive state, the UE performs an RRC pause procedure 140, where the UE context is stored by both the UE and the serving base station (BS), followed by an RRC release. The BS can be any type of BS, such as a next-generation Node B (gNB) or an NR Node B (gNB). In the inactive state, the UE still has a non-access stratum (NAS) connection to the CN (i.e., it remains in a connection management (CM) connected state, as opposed to the idle state where the UE is not in a CM connected state).

[0039] When inactive, the UE can move within the RAN Notification Area (RNA) without notifying the RAN, perform cell reselection, and receive paging messages from the RAN. However, the UE lacks dedicated AS resources for performing unicast communication and therefore cannot perform any dedicated data transmission or reception. Because the UE cannot perform dedicated data reception when inactive, the RAN pagees the UE to trigger it to enter the connected state when downlink data needs to be transmitted. When the UE has uplink data to transmit, it first enters the connected state before transmitting the uplink data.

[0040] To transition from an inactive state to a connected state, the UE executes an RRC recovery procedure 150, in which the UE context is retrieved from the UE's previous serving cell and restored to the UE and the (new) serving cell. Compared to the transition from an idle state to a connected state, the RRC recovery procedure accelerates the transition to the connected state by allowing the restoration of the previous connection without having to perform a large amount of NAS signaling.

[0041] Figure 2 The exemplary RRC recovery process 250 is outlined below. The UE is initially in an inactive state. At 210, the UE uses the RACH procedure to transmit an RRC ResumeRequest to the BS where it resides. The RRC ResumeRequest includes the UE's Inactive Radio Network Temporary Identifier (I-RNTI), which is assigned to the UE by the network when the UE enters an inactive state. The network uses the I-RNTI with the ResumeRequest set to identify the UE and the previous serving cell, allowing the new serving cell to obtain the UE context from the previous serving cell.

[0042] exist Figure 3A and Figure 3B The diagram illustrates in more detail two types of contention-based RACH (CBRA) processes 310 and 360 that can be used to transmit RRC Resume Requests. Although the RACH process is described here in the context of transmitting a Resume Request, the RACH process is used by the UE whenever the UE desires to achieve uplink synchronization with the BS, to transition from an idle or inactive state to a connected state, or to acquire uplink transmission resources in a connected state.

[0043] Figure 3AA four-step contention-based RACH (CBRA) process is illustrated. At 320, using a predetermined RACH preamble timing, the UE transmits Msg1, which includes a preamble identifying the UE. In CBRA, the preamble is randomly selected by the UE from a set of possible preambles. In another type of RACH process, when the UE enters an inactive or idle state, a contention-free RACH (CFRA), a preamble, and optionally, Physical Uplink Shared Channel (PUSCH) resources are allocated to the UE. Because it is possible for another UE to select the same preamble via the same preamble RACH resources, CBRA includes a contention resolution step 350 as described below. Along with the preamble, the UE also indicates a response window during which the UE expects a response from the BS. If the UE does not receive a response within the window, the UE can retransmit the preamble and / or take other remedial actions.

[0044] At 330, the BS transmits Msg2, which includes a Random Access Response (RAR). This RAR includes Downlink Control Information (DCI) that can be scrambled based on a preamble transmitted by the UE. The DCI includes information allowing the UE to decode the Physical Downlink Shared Channel (PDSCH), which transmits the UE's identifier and the allocation of uplink (UL) resources for the UE's use. At 340, the UE uses the UL resources received in the RAR to transmit Msg3. In this example, Msg3 will include a Resume Request. In other examples, Msg3 may include other data.

[0045] At position 350, the UE can establish a contention timer when sending Msg3 and monitor the Physical Downlink Control Channel (PDCCH) for Msg4 sent by the BS. Msg4 includes a Level 2 Media Access Control Physical Data Unit (L2 MAC PDU), which includes a Contention Resolution MAC Control Element (CE) used by the UE to determine whether the RACH process was successful. If the UE does not receive Msg4 before the timer expires, it is assumed that the RACH process failed. At this point, the UE has successfully notified the gNB of its intention to enter the connected state (e.g., Figure 2 Step 210 is complete.

[0046] Figure 3B The 2-step CBRA process is shown at 360. At 370, the UE transmits MsgA, which includes... Figure 3AThe information sent in Msg1 and Msg3 of the 4-step RACH process. MsgA includes a randomly selected preamble transmitted on physical RACH (PRACH) resources and an RRC ResumeRequest transmitted using PUSCH resources. At 380, the gNB transmission may include MsgB of a fallback RAR, which includes uplink grants for the UE to retransmit MsgA if the gNB detects MsgA but cannot decode it. If the gNB successfully decodes MsgA, MsgB includes a success RAR, which may include a new UL or downlink (DL) grant for subsequent data communication (not a retransmission of the RRC ResumeRequest). At this point, the UE has successfully notified the BS of its intention to enter the connected state (e.g., Figure 2 Step 210 is complete.

[0047] Return to Figure 2 The RRC recovery process outlined in the table is as follows: At 220, after the BS has received the ResumeRequest, as part of the RRC pause process, the BS requests the UE context information stored by the previous serving BS. At 230, the previous serving BS provides the UE context information to the new serving BS. At 240, the BS transmits an RRC recovery message to the UE to indicate that the UE can enter the connected state. At 260, the UE indicates to the BS that the UE has successfully entered the connected state. At 270, the BS transmits a path handover request to the Access and Mobility Management Function (AMF), which acts as the interface between the BS and the CN, to update the UE's radio bearers. At 280, the AMF responds to the BS, thus confirming the path handover is complete. At 290, the BS notifies the previous serving BS that it can delete the UE context. After these communications have occurred, the UE can transmit data to and receive data from the BS.

[0048] See Figure 4A As can be seen, the recovery process introduces a significant delay between when the UE has data to transmit and when the UE is able to transmit data. For example... Figure 4B As shown, this document discloses systems, circuits, and techniques for allowing a UE to perform direct data transmission to a BS while in an inactive state without transitioning to a connected state.

[0049] Figure 5AA flowchart of method 500A for inactive state communication between a BS and a UE using radio link quality thresholds is shown. At 502, at some point before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters. These parameters may include a RACH configuration specified for inactive state communication (e.g., multiple configurations or a predefined configuration such as Cfg#N), a RACH preamble, UL authorization, and transmission conditions. The RACH preamble may include the UE's identifier. The UL authorization may include a threshold limiting the maximum message size used for transmission. Transmission conditions may include radio link quality thresholds. Predefined radio link quality thresholds may include one or more of a Reference Signal Received Power (RSRP) threshold, a Reference Signal Received Quality (RSRQ) threshold, or a Signal-to-Interference-Noise Ratio (SINR) threshold.

[0050] After 502, the UE may have data available for communication with the BS, and the UE may determine to perform RRC inactive data transmission. The determination to perform RRC inactive data transmission may be based on one or more of the following: determining that the available UL data for communication is less than the UL authorization threshold broadcast at 502, or determining that the UE's radio link quality is within a predefined radio link quality threshold.

[0051] After the above determinations are made, the UE can proceed to step 504, whereby the UE transmits the Msg1 RACH preamble to the BS via PRACH. This preamble may include an identifier identifying the UE. The preamble can be selected from the preamble specified by the BS for inactive state communication in step 502. At step 502, Msg1 can be transmitted according to the RACH configuration specified by the BS for inactive state communication (e.g., Cfg#N, etc.).

[0052] At 506, the BS may transmit Msg2 as a Random Access Response (RAR) to the UE, which indicates the timing of RRC inactive data transmission (e.g., via a Timing Advance Command (TAC)) and the UE's UL authorization. At 507, the UE transmits Msg3PUSCH to the BS. Msg3PUSCH includes UL data transmission for inactive state communication. At 508, the BS may transmit Msg4 to the UE during the Contention Resolution (CR) window, and the UE may determine that the RRC inactive data transmission has been successfully completed in response to receiving Msg4. Method 500A can be executed while the UE remains in an inactive state. Figure 2 Compared to the RRC recovery process described in the previous section, method 500A can provide reduced latency for transmitting data to the BS.

[0053] Figure 5BA flowchart of method 500A for inactive state communication between a BS and a UE using radio link timing thresholds is shown. At 510, at some point before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters. These parameters may include a RACH configuration specified for inactive state communication (e.g., multiple configurations or a predefined configuration such as Cfg#N), a RACH preamble, UL authorization, and transmission conditions. The RACH preamble may include the UE's identifier. The UL authorization may include a threshold limiting the maximum message size used for transmission. Transmission conditions may include radio link timing thresholds. Predefined radio link timing thresholds may include TAC thresholds.

[0054] Following section 510, the UE may have data available for communication with the BS, and the UE may determine to perform RRC inactive data transmission. The UE may determine that the UL data available for communication is less than the UL authorization threshold described in section 510.

[0055] After the above determinations are made, the UE can proceed to step 512, whereby the UE can transmit the Msg1 RACH preamble to the BS via PRACH. This preamble may include an identifier identifying the UE. The preamble can be selected from the preamble specified by the BS for inactive state communication in step 510. At step 510, Msg1 can be transmitted according to the RACH configuration specified by the BS for inactive state communication (e.g., Cfg#N, etc.).

[0056] In some implementations, the BS can determine the TAC adjustment based on the time it receives Msg1 at 512. At 514, the BS can transmit Msg2 as a RAR to the UE, which may include the TAC adjustment for inactive RRC data transmission and the UE's UL authorization. The UE receives Msg2 from the BS, and the UE determines to prepare Msg3PUSCH by comparing the TAC adjustment with a TAC threshold. After the UE determines to prepare Msg3PUSCH, the UE transmits Msg3PUSCH including UL data transmission for inactive state communication. The UE adjusts the timing of Msg3 based on the TAC adjustment sent by the BS at 514.

[0057] In some implementations, the UE determines whether to prepare the Msg3 PUSCH by estimating a timing advance (TA) value and comparing it with a TAC threshold. After the UE determines whether to prepare the Msg3 PUSCH, the UE transmits the Msg3 PUSCH, which includes UL data transmission for inactive state communication. The UE adjusts the timing of Msg3 based on the estimated TA value determined by the UE before transmitting Msg3.

[0058] At point 518, the BS can transmit Msg4 to the UE during the CR window, and the UE can determine that the RRC inactive data transmission has been successfully completed in response to receiving Msg4. Method 500B can be executed while the UE remains in an inactive state. Figure 2 Compared to the RRC recovery process described in the previous section, method 500B can provide reduced latency for transmitting data to the BS.

[0059] Figure 6A A flowchart of method 600A for 4-step RACH inactive state communication between BS and UE using a repetition scheme is shown. At 602, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters. These parameters may include the RACH configuration specified for inactive state communication (e.g., multiple configurations or predefined configurations such as Cfg#N), the RACH preamble, and the UL authorization. The RACH preamble may include the UE's identifier. The UL authorization may include a threshold limiting the maximum message size used for transmission.

[0060] At 604, the UE can determine to transmit a Msg1 RACH preamble to the BS via PRACH. This preamble may include an identifier identifying the UE. The preamble can be selected from the preamble specified by the BS for inactive state communication in 602. Msg1 can be transmitted according to the RACH configuration specified by the BS for inactive state communication (e.g., Cfg#N, etc.).

[0061] At 606, the BS can transmit Msg2 as a RAR to the UE, which may include the number of Msg3 repetitions for RRC inactive data transmission and the UE's UL authorization. Alternatively, the number of Msg3 repetitions can be configured via Layer 1 (L1), Layer 2 (L2), or Layer 3 (L3) signaling, or the UE can configure the repetition number based on radio quality. Radio quality may include one or more of RSRQ, RSRP, or SINR. At 608, the UE can prepare a Msg3 PUSCH including UL data transmission for inactive state communications. Hybrid Automatic Repeat Request (HARQ) can repeatedly transmit Msg3 until Msg3 is acknowledged by the BS or until the repetition number is reached. Alternatively, the L1 process can repeatedly transmit Msg3 until the repetition number is reached. After the repetition number is reached, the UE can start a (CR) timer associated with the Msg4 CR window. Upon receiving Msg3, the BS can transmit Msg4 to the UE at 610 during the Msg4 CR window, and the UE can determine that the RRC inactive data transmission was successfully completed in response to the receipt of Msg4. Method 600A can be executed while the UE remains in an inactive state. Figure 2Compared to the RRC recovery process described in the previous section, method 600A can provide reduced latency for transmitting data to the BS.

[0062] Figure 6B A flowchart of method 600B for two-step RACH inactive state communication between BS and UE using a repetition scheme is shown. At 612, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters. These parameters may include the RACH configuration specified for inactive state communication (e.g., multiple configurations or predefined configurations such as Cfg#N), the RACH preamble, the UL authorization, and the MsgA repetition count. Alternatively, the MsgA repetition count may be configured via L1, L2, or L3 signaling, or the UE may configure the repetition count based on radio quality. Radio quality may include one or more of RSRQ, RSRP, or SINR. The RACH preamble may include the UE's identifier. The UL authorization may include a threshold limiting the maximum message size used for transmission.

[0063] Following step 612, the UE can determine at points 614 and 616 to transmit MsgA to the BS. At 614, the UE can transmit the MsgA RACH preamble via PRACH, which may include an identifier identifying the UE. The preamble can be selected from the preamble specified by the BS for inactive state communication in step 612. In step 612, MsgA can be transmitted according to the RACH configuration specified by the BS for inactive state communication (e.g., Cfg#N, etc.).

[0064] At 616, the UE can further prepare MsgAPUSCH, including UL data transmission for inactive state communication. Hybrid Automatic Repeat Request (HARQ) can repeatedly transmit MsgA until MsgA is acknowledged by the BS or until a repeat count is reached. Alternatively, the L1 process repeatedly transmits MsgA until a repeat count is reached. After the repeat count is reached, a RAR window associated with MsgB can be initiated. Upon receiving MsgA, the BS can transmit MsgB to the UE at 618 during the RAR window, and the UE can determine that the RRC inactive data transmission has been successfully completed in response to receiving MsgB. Method 600B can be executed while the UE remains in an inactive state. Figure 2 Compared to the RRC recovery process described in the previous section, method 600B can provide reduced latency for transmitting data to the BS.

[0065] Figure 7AA flowchart of method 700A for 4-step RACH inactive state communication between BS and UE is shown, wherein RACH and UE are distinguished based on I-RNTI (e.g., which may be the UE's full I-RNTI (including 24 bits) or the UE's truncated I-RNTI (including 16 bits)). At 702, at some point before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters, which may include a UL authorization specified for inactive state communication. The UL authorization may include a threshold limiting the maximum message size used for transmission.

[0066] At 704, the UE can determine to transmit the Msg1 RACH preamble to the BS via PRACH. At 706, the BS can transmit Msg2 as a RAR to the UE.

[0067] At 708, the UE can transmit a Msg3 PUSCH including UL data transmission for inactive state communication. Msg3 may include a Media Access Control (MAC) control element (CE), where the MAC CE has an I-RNTI / truncated I-RNTI. The MAC CE with the I-RNTI / truncated I-RNTI can be configured for inactive state communication and can identify the UE. After the BS receives Msg3, the BS can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish the RACH as inactive state communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At 710, the BS can transmit Msg4 to the UE during the CR window, and the UE can determine that the RRC inactive data transmission was successfully completed in response to receiving Msg4. The BS can use the I-RNTI / truncated I-RNTI to schedule the transmission of Msg4 or subsequent data transmissions that may occur in the inactive state.

[0068] Alternatively, at 708, the UE can use an I-RNTI / truncated I-RNTI to scramble the Msg3 PUSCH transmission. After the BS receives Msg3, the BS can descramble Msg3 containing UL data. The BS can descramble Msg3 using a set of one or more potential I-RNTIs / truncated I-RNTIs, including the I-RNTI / truncated I-RNTI. At 710, the BS can transmit Msg4 to the UE during the CR window, and the UE can determine that the RRC inactive data transmission has been successfully completed in response to receiving Msg4. The BS can use an I-RNTI / truncated I-RNTI to schedule the Msg4 transmission or subsequent data transmissions that may occur in the inactive state. Method 700A can be performed while the UE remains in an inactive state. Figure 2Compared to the RRC recovery process described in the previous section, method 700A can provide reduced latency for transmitting data to the BS.

[0069] Figure 7B A flowchart of method 700A for two-step RACH inactive state communication between BS and UE is shown, wherein RACH and UE are distinguished based on I-RNTI (e.g., which may be the UE's full I-RNTI or a truncated I-RNTI). The I-RNTI may consist of 24 bits, and the truncated I-RNTI may consist of 16 bits. At 712, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters, which may include a UL authorization specified for inactive state communication. The UL authorization may include a threshold limiting the maximum size used for transmission.

[0070] After 712, the UE can determine at 714 and 616 to transmit MsgA to the BS. At 714, the UE can transmit the MsgA RACH preamble via PRACH.

[0071] At 716, the UE can transmit a MsgA PUSCH including UL data transmission for inactive state communication. MsgA may include a MAC CE, where the MAC CE has an I-RNTI / truncated I-RNTI. The MAC CE with the I-RNTI / truncated I-RNTI can be configured for inactive state communication and can identify the UE. After the BS receives MsgA, the BS can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish the RACH as inactive state communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At 718, the BS can transmit MsgB to the UE, and the UE can determine that the RRC inactive data transmission was successfully completed in response to receiving MsgB. The BS can use the I-RNTI / truncated I-RNTI to schedule MsgB transmission or subsequent data transmissions that may occur in the inactive state.

[0072] Alternatively, at points 714 and 716, the UE can use an I-RNTI / truncated I-RNTI to scramble the MsgA PUSCH transmission. After the BS receives MsgA, the BS can descramble MsgA containing UL data. The BS can descramble MsgA using a set of one or more potential I-RNTIs / truncated I-RNTIs, including the I-RNTI / truncated I-RNTI. At point 718, the BS can transmit MsgB to the UE, and the UE can determine that the RRC inactive data transmission was successfully completed in response to receiving MsgB. The BS can use the I-RNTI / truncated I-RNTI to schedule the MsgB transmission or subsequent data transmissions that may occur in the inactive state. Method 700B can be executed while the UE remains in an inactive state. Figure 2 Compared to the RRC recovery process described in the previous section, method 700B can provide reduced latency for transmitting data to the BS.

[0073] Figure 8A A flowchart of method 800A for 4-step RACH inactive state communication between BS and UE using feedback from successful transmission is shown. At 802, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters, which may include a UL authorization specified for inactive state communication. The UL authorization may include a threshold limiting the maximum message size used for transmission.

[0074] At 804, the UE can determine to transmit the Msg1 RACH preamble to the BS using PRACH. At 806, the BS can transmit Msg2 as RAR to the UE.

[0075] At 808, the UE can transmit a Msg3 PUSCH including UL data transmission for inactive state communication. Msg3 may include a MAC CE, where the MAC CE has an I-RNTI / truncated I-RNTI. The MAC CE with I-RNTI / truncated I-RNTI can be configured for inactive state communication and can identify the UE. When transmitting Msg3, the UE can start a contention-resolved timer, where the CR timer is set to end at the CR duration limit.

[0076] After the BS receives Msg3, it can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish the RACH as inactive communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. In some implementations, at 810, the BS can transmit Msg4 in response to Msg3. Msg4 at 810 may include a DL assignment scheduled by a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), and the DL assignment may include a MAC CE. When the UE receives Msg4 within the CR duration limit, the UE can consider the RRC inactive data transmission successful.

[0077] Alternatively, at 808, the UE can use an I-RNTI / truncated I-RNTI to scramble the Msg3 PUSCH transmission. When transmitting Msg3, the UE can start a CR timer, which is set to end at a CR duration limit. After the BS receives Msg3, the BS can descramble the Msg3 containing the MAC CE using the I-RNTI / truncated I-RNTI and UL data. The BS can descramble the Msg3 using a set of one or more potential I-RNTIs / truncated I-RNTIs, including the I-RNTI / truncated I-RNTI. The BS can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish RACH as inactive communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. In some implementations, instead of transmitting Msg4 as described in conjunction with 810, the BS may transmit Msg4 at 812 in response to Msg3. This Msg4 may include a UL authorization / DL assignment for new data scrambled with an I-RNTI / truncated I-RNTI. When the UE receives Msg4 within the CR duration limit, the UE may consider the RRC inactive data transmission successful.

[0078] Figure 8B A flowchart of method 800B for performing two-step RACH inactive state communication between the BS and UE using feedback from successful transmission is shown. At 814, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters, which may include a UL authorization specified for inactive state communication. The UL authorization may include a threshold limiting the maximum message size used for transmission.

[0079] Following step 814, at points 816 and 818, the UE can determine whether to transmit MsgA to the BS. At 816, the UE can transmit a MsgA RACH preamble with PRACH. At 818, the UE can transmit a MsgA PUSCH including UL data transmission for inactive state communication. MsgA may include a MAC CE with I-RNTI / truncated I-RNTI. The MAC CE with I-RNTI / truncated I-RNTI can be configured for inactive state communication and can identify the UE. When the UE transmits MsgA, the UE can initiate a MsgB window.

[0080] After the BS receives MsgA, it can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish the RACH as inactive communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At option 820A, the BS can transmit MsgB in response to MsgA. MsgA may include a RAR and / or MAC CE with the I-RNTI / truncated I-RNTI from MsgB. When the UE receives MsgB within the MsgB window, the UE can consider the RRC inactive data transmission successful.

[0081] Alternatively, at 818, the UE can use an I-RNTI / truncated I-RNTI to scramble the MsgA PUSCH transmission. After the BS receives MsgA, the BS can descramble MsgA, including the MAC CE, using the I-RNTI / truncated I-RNTI and UL data. The BS can descramble Msg3 using a set of one or more potential I-RNTIs / truncated I-RNTIs, including the I-RNTI / truncated I-RNTI. The BS can read the MAC CE with the I-RNTI / truncated I-RNTI, distinguish RACH as inactive communication, and identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At option 822B, the BS can transmit MsgB in response to MsgA. MsgB can include UL authorization / DL assignment for new data scrambled with the I-RNTI / truncated I-RNTI. When the UE receives MsgB within the MsgB window, the UE can consider the RRC inactive data transmission to be successful.

[0082] In various implementation schemes (such as combination) Figures 5A to 8BIn the described implementations, the RACH can be a dedicated RACH configuration for RRC inactive data communication. The BS can provide the dedicated RACH configuration to the UE, for example, during a broadcast transmission, before the UE performs inactive state communication. The UE in an inactive state can use the dedicated RACH configuration to perform inactive state communication.

[0083] In various implementation schemes (such as combination) Figures 5A to 8B In the described implementations, the RACH preamble can be a dedicated RACH preamble from a dedicated RACH preamble group for RRC inactive data communications. Before the UE performs inactive state communications, the BS can provide the UE with a shared RACH preamble group, for example, during a broadcast transmission. The UE in an inactive state can select a dedicated RACH preamble from the dedicated group for inactive state communications.

[0084] In various implementation schemes (including combinations) Figures 5A to 8B In the described implementations, the RACH preamble can be a shared RACH preamble for both the RACH procedure used for RRC inactive data communication and the RACH procedure used for RRC recovery.

[0085] Figure 9A A flowchart of method 900A for RACH inactive state communication between BS and UE using a fallback mechanism of the RRC recovery process by causing the RACH procedure to fail or reaching the RACH preamble retransmission value is shown. The UE can be configured to suspend the RACH procedure for RRC inactive data transmission according to a suspension criterion. When the suspension criterion is met, the UE can comply with the RACH procedure by transmitting an RRC ResumeRequest, which may include... Figure 1 and Figure 2 The recovery process outlined in the document involves reverting back to the RRC recovery process.

[0086] At point 902, some time before the UE can transmit or receive data, the BS can broadcast a message to the UE including various parameters. These parameters may include one or more of the following: RACH preamble, RACH preamble retransmission count, RACH configuration, UL authorization, radio link quality threshold, radio link timing threshold, and Msg3 and / or MsgA repetition value.

[0087] UE and BS can participate in inactive state communication via a 4-step or 2-step RACH procedure for RRC inactive data communication. Suspension criteria may include any failure of the RACH process, as shown at 904. The RACH process may fail sometime before or after MsgA or MsgB; or Msg1, Msg2, Msg3, or Msg4. Examples of failed RACH processes will include information regarding... Figures 5A to 8BThe failure to complete any of the described steps. If the RACH process fails, the UE can suspend the RACH process and fall back to Msg1 or MsgA RRC resumption process by transmitting an RRC ResumeRequest to the BS, as may be included in 908. Figure 1 and Figure 2 The RRC recovery process described in [the document].

[0088] Alternatively, the UE can be configured to retransmit the RACH preamble for RRC inactive data transmission based on the retransmission value, as shown at 906. The 4-step or 2-step RACH procedure for RRC inactive data communication occurs in the intermediate steps of the RACH procedure (e.g., Figures 5A to 8B Failure may not occur during the steps described in [the document]. However, the UE can retransmit the RACH preamble and reach the retransmission value. Upon reaching the retransmission value, the UE can suspend the RACH procedure and fall back to Msg1 or MsgA RRC recovery procedure by transmitting an RRC Resume Request to the BS, as may be included in [the document] in 908. Figure 1 and Figure 2 The RRC recovery process described in [the document].

[0089] Figure 9B A flowchart of method 900B for RACH inactive state communication between BS and UE using a fallback mechanism to the RRC recovery process when a radio quality threshold is not met is shown. The UE is configured to suspend the RACH process for RRC inactive data transmission according to an alternative suspension criterion different from that described in 900A. When the alternative suspension criterion is met, the UE can comply with the RACH process by transmitting an RRC ResumeRequest, which may include... Figure 1 and Figure 2 The recovery process outlined in the document involves reverting back to the RRC recovery process.

[0090] At point 910, sometime before the UE can transmit or receive data, the BS may broadcast a message to the UE including various parameters. These parameters may include radio link quality thresholds and one or more additional parameters described at point 902.

[0091] Alternative suspension criteria may include a radio link quality threshold. At 912, before MsgA or MsgB; or at some point during Msg1, Msg2, Msg3, or Msg4, the radio link quality threshold may not be met. The UE may continue RACH inactive data communication and generate Msg3 or MsgA PUSCH including an RRC ResumeRequest, as shown at 914, in place of UL data. When the radio link quality threshold is not met, the UE may generate Msg3 or MsgA PUSCH. After the UE transmits Msg3 or MsgA with an RRC ResumeRequest, the RACH process associated with inactive state communication can be suspended and the RRC recovery process can subsequently be completed, for example, as... Figure 1 and Figure 2 As described in [the text].

[0092] Alternatively, when the radio link quality threshold is not met at 912, the UE may suspend the RACH procedure and fall back to the Msg1 or MsgA RRC recovery process (as in option B of 916) by transmitting an RRC Resume Request to the BS, and may subsequently complete the RRC recovery process, for example, as... Figure 1 and Figure 2 As described in [the text].

[0093] Figure 10 This is flowchart 1000 for RRC inactive data transmission for the UE. At 1010, at some point before the UE can transmit or receive data, the UE can receive a broadcast message with various parameters. These parameters may include one or more of the following: RACH configuration specified for inactive state communication, RACH preamble, UL authorization, transmission conditions, and Msg1 repetition count.

[0094] In response to determining to perform RRC inactive data communication, at point 1012, the UE can initiate the 4-step RACH procedure for RRC inactive data communication. The UE can transmit Msg1, including the RACH preamble, via PRACH. Msg1 may also include... Figures 5A to 8B One or more of the Msg1 features and operations described in the text.

[0095] At position 1014, the UE receives Msg2 and may include... Figures 5A to 8B The Msg2 feature and operation described herein may be one or more of these. At 1016, the UE may transmit a Msg3 PUSCH with UL data via configured resources. The UE may repeatedly transmit Msg3, as follows: Figure 6A As described in [the document / reference], Msg3 may include [the following]. Figures 5A to 8B One or more of the Msg3 features and operations described in the document.

[0096] At position 1018, the UE receives Msg4 in response to the Msg3 PUSCH transmission. Msg4 may include... Figures 5A to 8B One or more of the Msg4 features and operations described in the document.

[0097] Alternatively, after 1010 and in response to determining to perform RRC inactive data communication, at 1020, the UE may initiate a two-step RACH procedure for RRC inactive data communication. The UE may transmit MsgA, which may include a MsgA RACH preamble with PRACH, and may include a MsgA PUSCH. The UE may repeatedly transmit Msg3, such as... Figure 6B As described above. MsgA may also include Figures 5A to 8B One or more of the MsgA features and operations described in the document.

[0098] At position 1022, the UE may receive MsgB in response to a MsgA PUSCH transmission. MsgB may include... Figures 5A to 8B One or more of the MsgB features and operations described in the document.

[0099] Figure 10 The 2-step and 4-step RACH described herein can also be dedicated RACH configurations for RRC inactive data transmission. The UE can select a RACH preamble from a dedicated preamble group for RRC inactive data transmission. Alternatively, the RACH preamble can be a shared preamble for both the RACH procedure for RRC inactive data transmission and the RACH procedure for RRC recovery.

[0100] Figure 11 This is flowchart 1100 for RRC inactive data transmission for a BS. At 1110, the BS can transmit a broadcast message with various parameters. These parameters may include one or more of the following: RACH configuration specified for inactive state communication, RACH preamble, UL authorization, transmission conditions, and Msg1 repetition count.

[0101] The BS can receive Msg1, which may include a RACH preamble with PRACH. The RACH preamble with PRACH can be associated with RRC inactive data transmission. After receiving Msg1, at 1112, the BS can initiate a 4-step RACH procedure for RRC inactive data communication. Msg1 may also include... Figures 5A to 8B One or more of the Msg1 features and operations described in the text.

[0102] At position 1114, the BS can transmit Msg2 and may include... Figures 5A to 8BThe Msg2 feature and operation described herein may be one or more of the following. At 1116, the BS may receive Msg3 PUSCH with UL data via the configured resources. The BS may repeatedly receive Msg3, as follows: Figure 6A As described in [the document]. Msg3 may include [the following]. Figures 5A to 8B One or more of the Msg3 features and operations described in the document.

[0103] At 1118, the BS can respond to Msg3 PUSCH by transmitting Msg4 during the CR window. Msg4 may include... Figures 5A to 8B One or more of the Msg4 features and operations described in the document.

[0104] Alternatively, after 1110, the BS may receive at 1120 a MsgA designated for a two-step RACH procedure for RRC inactive data transmission. The MsgA may include a MsgA RACH preamble with a PRACH and may include a MsgA PUSCH with UL data via configured resources. The BS may repeatedly receive the MsgA, as follows: Figure 6B As described above. MsgA may also include Figures 5A to 8B One or more of the MsgA features and operations described in the document.

[0105] At 1122, the BS may transmit MsgB in response to a MsgA PUSCH transmission. MsgB may include... Figures 5A to 8B One or more of the MsgB features and operations described in the document.

[0106] Figure 11 The 2-step and 4-step RACH described herein can also be dedicated RACH configurations for RRC inactive data transmission. The BS can configure a dedicated RACH preamble group for RRC inactive data transmission, and the RACH preamble can be one of the dedicated RACH preamble groups for RRC inactive data transmission. Alternatively, the RACH preamble can be a shared preamble for both the RACH procedure for RRC inactive data transmission and the RACH procedure for RRC recovery.

[0107] Figure 12 This is flowchart 1200, used for UE RRC inactive data transmission via a fallback mechanism to the RRC recovery process. At 1210, at some point before the UE can transmit or receive data, the UE may receive a broadcast message including various parameters. These parameters may include one or more of the following: RACH preamble, RACH preamble retransmission count, RACH configuration, UL authorization, radio link quality threshold, radio link timing threshold, and Msg3 and / or MsgA repetition values.

[0108] At point 1212, the UE can participate in inactive state communication via a 4-step or 2-step RACH procedure for RRC inactive data communication. The 4-step or 2-step RACH procedure for RRC inactive data communication can follow... Figures 5A to 8B Any aspect described herein. At 1214, the UE can initiate a rollback to the RRC recovery procedure by satisfying the suspension criteria. The suspension criteria can include any failure of the RACH process. The RACH process can fail before or after MsgA or MsgB; or Msg1, Msg2, Msg3, or Msg4. Furthermore, a failed RACH process can include information regarding... Figures 5A to 8B The description refers to any step that fails to complete successfully if it meets the pause criteria.

[0109] The suspension criteria may include meeting a retransmission value. The UE can be configured to retransmit the RACH preamble for inactive RRC data transmission based on the retransmission value. The UE can retransmit the RACH preamble and meet the retransmission value that satisfies the suspension criteria.

[0110] Suspension criteria may include failure to meet radio quality thresholds. At some point before MsgA or MsgB; or before Msg1, Msg2, Msg3, or Msg4, the radio link quality thresholds may not be met, thus satisfying the suspension criteria.

[0111] After the suspension criteria are met, the UE can continue RACH inactive data communication and can generate a Msg3 or MsgA PUSCH including an RRC ResumeRequest, as shown at 1218, in place of UL data. After the UE transmits the Msg3 or MsgA with an RRC ResumeRequest, at 1220, the UE can suspend the RACH process associated with inactive state communication. Then at 1226, the UE can complete the RRC recovery process, for example, as shown below. Figure 1 and Figure 2 As described in [the text].

[0112] After meeting the suspension criteria, the UE can suspend the RACH process associated with inactive state communication, as shown at 1222. At 1224, the UE can fall back to the Msg1 or MsgA RRC recovery process by transmitting an RRC ResumeRequest. At 1226, the UE can complete the RRC recovery process, for example, as shown below. Figure 1 and Figure 2 As described in [the text].

[0113] If the pause criteria are not met, the UE can... Figures 5A to 8B The aspect described herein completes the RACH inactive data transmission at position 1216.

[0114] The aspects described herein can be implemented into a system using any appropriately configured hardware and / or software. Figure 13 The architecture of system 1300, including CN 1320 (e.g., 5G CN (5GC)), is shown according to various aspects. System 1300 is shown as including UE 1301, which may be the same as or similar to one or more other UEs discussed herein; 3GPP radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN 210, which may include one or more RAN nodes (e.g., evolved Node B (eNB)), next-generation Node B (gNB and / or other nodes) or other nodes or access points; and data network (DN) 1303, which may be, for example, operator services, Internet access or third-party services; and 5G core network (5GC) 1320. 1320 may include one or more of the following functions and network components: Authentication Server Function (AUSF) 1322, Access and Mobility Management Function (AMF) 1321, Session Management Function (SMF) 1324, Network Exposure Function (NEF) 1323, Policy Control Function (PCF) 1326, Network Repository Function (NRF) 1325, Unified Data Management (UDM) 1327, Application Function (AF) 1328, User Plane (UP) Function (UPF) 1302, and Network Slice Selection Function (NSSF) 1329, which can be connected through various interfaces and / or reference points, for example, such as Figure 13 As shown.

[0115] Figure 14Exemplary components of device 1400 according to some aspects are shown. In some aspects, device 1400 may include at least application circuitry 1402, baseband circuitry 1404, radio frequency (RF) circuitry 1406, front-end module (FEM) circuitry 1408, one or more antennas 1410, and power management circuitry (PMC) 1412 coupled together as shown. Components of the illustrated device 1400 may be included in a UE or RAN node. In some aspects, device 1400 may include fewer components (e.g., the RAN node may not utilize application circuitry 1402, but instead include a processor / controller to process IP data received from a CN such as 5GC 1320 or Evolved Packet Core (EPC). In some aspects, device 1400 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in device 1400, etc.) or input / output (I / O) interfaces. In other respects, the following components may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0116] Application circuitry 1402 may include one or more application processors. For example, application circuitry 1402 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 1400. In some aspects, the processor of application circuitry 1402 may process IP data packets received from the EPC.

[0117] Baseband circuit 1404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1404 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 1406 and generate baseband signals for the transmit signal path of RF circuit 1406. Baseband circuit 1404 may interact with application circuitry 1402 to generate and process baseband signals and control the operation of RF circuit 1406. For example, in some aspects, baseband circuit 1404 may include a third-generation (3G) baseband processor 1404A, a fourth-generation (4G) baseband processor 1404B, a fifth-generation (5G) baseband processor 1404C, or other existing, under development, or future generations of baseband processors 1404D (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuitry 1404 (e.g., one or more baseband processors 1404A-D) can handle various radio control functions that can communicate with one or more radio networks via RF circuitry 1406. In other aspects, some or all of the functions of the baseband processors 1404A-1404D may be included in modules stored in memory 1404G and executed via a central processing unit (CPU) 1404E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some aspects, the modulation / demodulation circuitry of the baseband circuitry 1404 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some aspects, the encoding / decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. The aspects of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other aspects.

[0118] In some aspects, the baseband circuitry 1404 may include one or more audio digital signal processors (DSPs) 1404F. The audio DSP 1404F may include elements for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some aspects, some or all components of the baseband circuitry 1404 and the application circuitry 1402 may be implemented together, for example, on a system-on-a-chip (SoC).

[0119] In some aspects, baseband circuit 1404 can provide communication compatible with one or more radio technologies. For example, in some aspects, baseband circuit 1404 can support communication with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN), etc. Aspects in which baseband circuit 1404 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuitry.

[0120] RF circuit 1406 can communicate with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various aspects, RF circuit 1406 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1406 may include a receive signal path that includes circuitry for down-converting an RF signal received from FEM circuit 1408 and providing a baseband signal to baseband circuit 1404. RF circuit 1406 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 1404 and providing an RF output signal to FEM circuit 1408 for transmission.

[0121] In some aspects, the receive signal path of RF circuit 1406 may include mixer circuit 1406a, amplifier circuit 1406b, and filter circuit 1406c. In some aspects, the transmit signal path of RF circuit 1406 may include filter circuit 1406c and mixer circuit 1406a. RF circuit 1406 may also include synthesizer circuit 1406d for synthesizing frequencies used by mixer circuit 1406a for both the receive and transmit signal paths. In some aspects, mixer circuit 1406a for the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1408 based on the synthesized frequency provided by synthesizer circuit 1406d. Amplifier circuit 1406b may be configured to amplify the down-converted signal, and filter circuit 1406c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1404 for further processing. In some respects, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some respects, the mixer circuit 1406a of the receiving signal path may include a passive mixer, but the range of respects is not limited in this respect.

[0122] In some respects, the mixer circuit 1406a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1406d to generate an RF output signal for the FEM circuit 1408. The baseband signal can be provided by the baseband circuit 1404 and can be filtered by the filter circuit 1406c.

[0123] In some aspects, the mixer circuit 1406a for the receive signal path and the mixer circuit 1406a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some aspects, the mixer circuit 1406a for the receive signal path and the mixer circuit 1406a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some aspects, the mixer circuit 1406a for the receive signal path and the mixer circuit 1406a may be arranged for direct downconversion and direct upconversion, respectively. In some aspects, the mixer circuit 1406a for the receive signal path and the mixer circuit 1406a for the transmit signal path may be configured for superheterodyne operation.

[0124] In some aspects, the output baseband signal and the input baseband signal may be analog baseband signals, but the range of aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative aspects, the RF circuit 1406 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1404 may include a digital baseband interface for communication with the RF circuit 1406.

[0125] In some dual-mode aspects, separate radio IC circuits can be provided to process signals for each spectrum, but the range of each aspect is not limited in this respect.

[0126] In some respects, synthesizer circuit 1406d can be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the range of respects is not limited in this respect, as other types of frequency synthesizers can be suitable. For example, synthesizer circuit 1406d can be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0127] Synthesizer circuit 1406d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1406a of RF circuit 1406. In some aspects, synthesizer circuit 1406d can be a fractional N / N+1 synthesizer.

[0128] In some respects, the frequency input can be provided by a voltage-controlled oscillator (VCO), but this is not required. The divider control input can be provided by the baseband circuit 1404 or the application circuit 1402 according to the desired output frequency. In some respects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application circuit 1402.

[0129] The synthesizer circuit 1406d of the RF circuit 1406 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry output) to provide a fractional division ratio. In some exemplary aspects, the DLL may include cascaded, tunable, delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. In these aspects, the delay elements may be configured to divide the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0130] In some aspects, the synthesizer circuit 1406d can be configured to generate a carrier frequency as the output frequency, while in others, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some aspects, the output frequency can be the LO frequency (fLO). In some aspects, the RF circuit 1406 may include an IQ / polarity converter.

[0131] FEM circuit 1408 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1410, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1406 for further processing. FEM circuit 1408 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1406 for transmission through one or more of the one or more antennas 1410. In various aspects, amplification via the transmit or receive signal path may be performed only in RF circuit 1406, only in FEM circuit 1408, or in both RF circuit 1406 and FEM circuit 1408.

[0132] In some aspects, FEM circuit 1408 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 1406). The transmit signal path of FEM circuit 1408 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 1406); and one or more filters for generating RF signals for subsequent transmission (e.g., through one or more antennas in one or more antennas 1410).

[0133] In some respects, the PMC 1412 can manage the power supplied to the baseband circuitry 1404. Specifically, the PMC 1412 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1412 is typically included when the device 1400 can be powered by a battery, for example, when the device is included in a UE. The PMC 1412 can improve power conversion efficiency while providing the desired specific implementation size and thermal characteristics.

[0134] Although Figure 14 The PMC 1412 is shown coupled only to the baseband circuit 1404. However, in other respects, the PMC 1412 may be additionally or alternatively coupled to other components (such as, but not limited to, the application circuit 1402, the RF circuit 1406, or the FEM 1408) and perform similar power management operations.

[0135] In some respects, the PMC 1412 can control or otherwise become part of various power-saving mechanisms of the device 1400. For example, if the device 1400 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, it can enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the device 1400 can be powered down for short intervals, thereby saving power.

[0136] If there is no data traffic activity during the extended period, device 1400 can transition to the RRC_Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1400 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 1400 may not receive data in this state; to receive data, the device can transition back to the RRC_Connected state.

[0137] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0138] The processors of application circuit 1402 and baseband circuit 1404 are elements that can be used to execute one or more instances of a protocol stack. For example, the processor of baseband circuit 1404 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of application circuit 1402 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0139] Figure 15 An exemplary interface for a baseband circuit is shown, based on some aspects. As discussed above, Figure 14 The baseband circuit 1404 may include processors 1404A-1404E and memory 1404G utilized by the processors. Each of the processors 1404A-1404E may respectively include memory interfaces 1504A-1504E for sending / receiving data to / from memory 1404G.

[0140] The baseband circuit 1404 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1512 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1404); and an application circuit interface 1514 (e.g., for sending / receiving data to / from a memory external to the baseband circuit 1404); Figure 14 Application circuit 1402 (interface for transmitting / receiving data); RF circuit interface 316 (e.g., for transmitting / receiving data to / from...). Figure 14 The RF circuit 1406 is an interface for transmitting / receiving data; the wireless hardware connection interface 1518 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) LowEnergy), Interfaces for sending / receiving data to / from components and other communication components; and power management interface 1520 (e.g., an interface for sending / receiving power or control signals to / from PMC 1412).

[0141] As discussed in more detail herein, various aspects, such as those employed at the UE, can be combined with a wireless modem to facilitate power management. These aspects can employ the power management techniques discussed herein, where one or more power management phases discussed herein can be used to mitigate overheating based on monitored power consumption and temperature levels. The power management phases discussed herein can reduce power consumption and associated overheating caused by 5G (fifth generation) NR (New Radio) operation, LTE (Long Term Evolution) operation, or both.

[0142] See Figure 16 This diagram illustrates a block diagram of a system 1600 that can be employed at a UE (User Equipment), a next-generation Node B (gNodeB or gNB), or another BS (Base Station) / TRP (Transmit / Receive Point) or 3GPP (3rd Generation Partnership Project) network, in conjunction with a radio modem to facilitate power management, based on the various aspects discussed herein. System 1600 may include a processor 1610, communication circuitry 1620, and memory 1630. Processor 1610 (e.g., it may include one or more of 1402 and / or 1404A-1404F, etc.) may include processing circuitry and associated interfaces (e.g., a communication interface for communicating with communication circuitry 1620 (e.g., RF circuitry interface 1516), a memory interface for communicating with memory 1630 (e.g., memory interface 1512), etc.). The communication circuitry 1620 may include, for example, circuitry for wired and / or wireless connections (e.g., 1406 and / or 1408), which may include transmitter circuitry (e.g., associated with one or more transmission chains) and / or receiver circuitry (e.g., associated with one or more receiver chains), wherein the transmitter and receiver circuitry may employ common and / or different circuitry elements, or combinations thereof. The memory 1630 may include one or more memory devices (e.g., memory 1404G, local memory (e.g., including CPU registers of the processor discussed herein), etc.), which may have any of a variety of storage media (e.g., volatile and / or non-volatile according to any of a variety of technologies / constructions, etc.), and may store instructions and / or data associated with one or more of the processor 1610 or the communication circuitry 1620.

[0143] Specific types of aspects of system 1600 (e.g., UE aspects) can be indicated via subscripts (e.g., system 1600). UE Including processor 1610 UE Communication circuit 1620 UE and memory 1630 UEIn some aspects, such as the BS aspect (e.g., System 1600) gNB ) and network components (e.g., UPF (User Plane Function) etc.) (e.g., System 1600) UPF ), processor 1610 gNB (etc.), communication circuits (e.g., 1620) gNB (etc.) and memory (e.g., 1630) gNB Signaling or message transmissions between different aspects of system 1600 (e.g., 16001 and 16002) may be generated by processor 16101, transmitted by communication circuitry 16201 through a suitable interface or reference point (e.g., 3GPP air interfaces N3, N4, etc.), received by communication circuitry 16202, and processed by processor 16102. Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with systems 16001 and 16002) may participate in the communication. Baseband circuitry 1404 may also include one or more interfaces for communicatively coupling to other circuitry / devices, such as communication circuitry 1620.

[0144] In various aspects, one or more of the following—information (e.g., system information, resources associated with signaling, etc.), characteristics, parameters, etc.—may be transmitted via signaling (e.g., associated with one or more layers, such as L1 signaling or higher-layer signaling (e.g., MAC, RRC, etc.)) from the gNB or other access point (e.g., via processor 1610) gNB Generated by communication circuit 1620 gNB Transmission, via communication circuit 1620 UE Received, and processed by processor 1610 UE The signaling used (processed) is configured to the UE. Depending on the type, characteristics, parameters, etc. of the information, the exact details of the signaling used and / or the operations performed at the UE and / or gNB during processing (e.g., signaling structure, PDU / SDU processing, etc.) may vary. However, for convenience, such operations may be referred to herein as generating or processing configuration signaling for UE configuration information / characteristics / parameters / etc., or via similar terms.

[0145] Additional Examples

[0146] Embodiments herein may include subjects such as methods, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform actions of a method, apparatus, or system for concurrent communication using various communication technologies according to the described aspects and examples.

[0147] Example 1 is a baseband processor including: a memory interface; and processing circuitry communicatively coupled to the memory interface and configured to perform operations including: in response to determining to perform Radio Resource Control (RRC) inactive data transmission: generating a message 1 (Msg1) or message A (MsgA) preamble based on the Random Access Channel (RACH) configuration for RRC inactive data transmission; generating a message 3 (Msg3) or message A (MsgA) Physical Uplink Shared Channel (PUSCH) including uplink (UL) data via the configured resources; and receiving a message 4 (Msg4) or message B (MsgB) via the PUSCH in response to Msg3 or MsgA.

[0148] Example 2 includes the subject matter of any variation of any of the embodiments in Example 1, wherein the RACH configuration is a dedicated RACH configuration for RRC inactive data transmission.

[0149] Example 3 includes the subject matter of any variation of any of the embodiments in Example 1, wherein the operation further includes selecting a preamble from a dedicated preamble group for RRC inactive data transmission.

[0150] Example 4 includes the subject matter of any variation of any of the embodiments in Example 1, wherein the preamble is a shared preamble for the RACH configuration of RRC inactive data transmission and the RACH procedure of the RRC recovery process.

[0151] Example 5 includes a subject matter of any variation of any of Examples 1 to 4, wherein the UL data is less than or equal to the pre-configured uplink data size; and wherein determination is based on at least one of a predefined radio link quality threshold or a predefined radio link timing threshold.

[0152] Example 6 includes the subject matter of any variation of any of Examples 1 to 5, wherein Msg3 or MsgAPUSCH is assigned a repeat value, which is determined by the processing circuitry based on one or more of radio link quality or L1, L2, or L3 signaling; wherein a Hybrid Automatic Repeat Request (HARQ) process or an L1 process generates one or more repeats of Msg3 or MsgAPUSCH based at least in part on the repeat value; and wherein the operation further includes, after the last repeat of one or more repeats, initiating one of a Random Access Response (RAR) window associated with MsgB or a Contention Resolution (CR) timer associated with Msg4.

[0153] Example 7 includes the subject matter of any variation of any of Examples 1 to 6, wherein Msg3 or MsgAPUSCH includes a Media Access Control CE (MAC CE) that includes an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the operation further includes scrambling Msg3 or MsgAPUSCH based on the I-RNTI / truncated I-RNTI.

[0154] Example 8 includes the subject matter of any variation of any of Examples 7, wherein the operation includes receiving MsgB, and wherein MsgB includes a Random Access Response (RAR) and the MAC CE includes an I-RNTI; or MsgB includes at least one of an uplink (UL) grant scrambled by an I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by an I-RNTI / truncated I-RNTI.

[0155] Example 9 includes the subject matter of any variation of any of Examples 7, wherein the operation includes generating Msg3, and wherein the operation further includes: starting a contention resolution (CR) timer after transmitting Msg3, the CR timer being set to end at a CR duration limit; and receiving Msg4 before the CR duration limit; wherein Msg4 includes at least one of an uplink (UL) grant scrambled by I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by I-RNTI / truncated I-RNTI, or Msg4 includes a downlink (DL) assignment that schedules the baseband processor at least based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), wherein the DL assignment that schedules the baseband processor at least based on a TC-RNTI includes a MAC CE containing an I-RNTI.

[0156] Example 10 is a user equipment (UE) device, the UE device including: a communication circuit; and a processor configured to perform operations including: in response to determining to perform Radio Resource Control (RRC) inactive data transmission: a random access channel (RACH) configuration based on RRC inactive data transmission, transmitting a message 1 (Msg1) or message A (MsgA) preamble via the communication circuit; transmitting a message 3 (Msg3) or message A Physical Uplink Shared Channel (PUSCH) including uplink (UL) data via the configured resources via the communication circuit; and receiving a message 4 (Msg4) or message B (MsgB) via the communication circuit in response to Msg3 or MsgA PUSCH.

[0157] Example 11 includes the subject matter of any variation of any of Examples 10, wherein the RACH configuration is a dedicated RACH configuration for RRC inactive data transmission.

[0158] Example 12 includes the subject matter of any variation of any of Examples 10, wherein the operation further includes selecting a preamble from a dedicated preamble group for RRC inactive data transmission.

[0159] Example 13 includes the subject matter of any variation of any of Examples 10, wherein the preamble is a shared preamble for the RACH configuration of RRC inactive data transmission and the RACH procedure of the RRC recovery process.

[0160] Example 14 includes a subject matter of any variation of any of Examples 10 to 14, wherein the UL data is less than or equal to the pre-configured uplink data size; and wherein determination is based on at least one of a predefined radio link quality threshold or a predefined radio link timing threshold.

[0161] Example 15 includes the subject matter of any variation of Examples 10 to 15, wherein Msg3 or MsgA PUSCH is assigned a repeat value, which is determined by a machine-readable medium based on radio link quality or one or more of L1, L2, or L3 signaling; wherein a Hybrid Automatic Repeat Request (HARQ) process or an L1 process transmits one or more repeats of Msg3 or MsgA PUSCH based at least in part on the repeat value; and after the last repeat of one or more repeats, the operation further includes initiating one of a RAR window associated with MsgB or a contention resolution (CR) timer associated with Msg4.

[0162] Example 16 includes the subject matter of any variation of any of Examples 10 to 13, wherein Msg3 or MsgA PUSCH includes a Media Access Control CE (MAC CE) that includes an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or operation further includes scrambling Msg3 or MsgA PUSCH based on I-RNTI / truncated I-RNTI.

[0163] Example 17 includes the subject matter of any variation of any of Examples 16, wherein the operation includes receiving MsgB, wherein MsgB includes a Random Access Response (RAR) and the MAC CE includes an I-RNTI; or MsgB includes at least one of an uplink (UL) grant scrambled by an I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by an I-RNTI / truncated I-RNTI.

[0164] Example 18 includes the subject matter of any variation of any of Examples 16, wherein the operation includes transmitting Msg3, and wherein the operation further includes: starting a contention resolution (CR) timer after transmitting Msg3, the CR timer being set to end at a CR duration limit; and receiving Msg4 before the CR duration limit; wherein Msg4 includes at least one of an uplink (UL) grant scrambled by I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by I-RNTI / truncated I-RNTI, or Msg4 includes a downlink (DL) assignment that schedules the UE device at least based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), wherein the DL assignment that schedules the UE device at least based on a TC-RNTI includes a MAC CE containing an I-RNTI.

[0165] Example 19 is a baseband processor that includes: a memory interface; and processing circuitry communicatively coupled to the memory interface and configured to perform operations including: suspending a random access channel (RACH) procedure for inactive radio resource control (RRC) data transmission; and generating an RRC recovery request.

[0166] Example 20 includes the subject matter of any variation of any of Examples 19, wherein the RACH process for RRC inactive data transmission is suspended in response to a failure of the RACH process for RRC inactive data transmission.

[0167] Example 21 includes the subject matter of any variation of any of Examples 19 to 20, wherein the operation further includes generating N RACH preambles for RRC inactive data transmission, where N is a threshold that is configured or predefined, wherein the RACH process for RRC inactive data transmission is paused in response to generating N RACH preambles for RRC inactive data transmission.

[0168] Example 22 includes the subject matter of any variation of any of Examples 19 to 21, wherein the operation further includes determining whether the radio link quality meets a threshold for generating a RACH preamble for RRC inactive data transmission, and wherein the RACH process is suspended in response to the radio link quality threshold not meeting the threshold for generating the RACH preamble.

[0169] Example 23 includes the subject matter of any variation of any of Examples 19 to 22, wherein after the RACH process is suspended, a new RACH process associated with an RRC recovery request begins, the new RACH process including generating an RRC recovery request.

[0170] Example 24 includes the subject matter of any variation of any of Examples 19 to 23, wherein the operation further includes: generating a RACH preamble for RRC inactive data transmission; and generating a Physical Uplink Shared Channel (PUSCH) including message 3 (Msg3) or message A (MsgA) for RRC recovery request based at least in part on the RACH preamble for RRC inactive data transmission.

[0171] Example 25 is a baseband processor including: a memory interface; and processing circuitry communicatively coupled to the memory interface and configured to perform operations including: configuring a random access channel (RACH) for receiving a message 1 (Msg1) or message A (MsgA) preamble based on Radio Resource Control (RRC) inactive data transmission; receiving a message 3 (Msg3) or message A Physical Uplink Shared Channel (PUSCH) including uplink (UL) data via the configured resources; and generating a message 4 (Msg4) or message B (MsgB) in response to Msg3 or MsgA PUSCH.

[0172] Example 26 includes the subject matter of any variation of any of Examples 25, wherein the RACH configuration is a dedicated RACH configuration for RRC inactive data transmission.

[0173] Example 27 includes the subject matter of any variation of any of Examples 25, wherein the operation further includes configuring a dedicated preamble group, and the Msg1 or MsgA preamble is one of the dedicated preamble groups for RRC inactive data transmission.

[0174] Example 28 includes the subject matter of any variation of any of Examples 25, wherein the preamble is a shared preamble for the RACH configuration of RRC inactive data transmission and the RACH configuration of the RRC recovery process.

[0175] Example 29 includes the subject matter of any variation of any of Examples 25 to 28, wherein the operation further includes: configuring the uplink data size for RRC inactive data transmission and configuring the radio link quality threshold for RRC inactive data transmission, or configuring the radio link timing threshold for RRC inactive data transmission based on one or more of timing advance (TA) or timing alignment command (TAC).

[0176] Example 30 includes the subject matter of any variation of any of Examples 25 to 29, wherein the operation further includes: configuring a radio link quality threshold to determine a repetition value for Msg3 or MsgA PUSCH, or configuring a repetition value and generating message 2 (Msg2) using the repetition value; receiving one or more repetitions of Msg3 or MsgA PUSCH according to the repetition value; and generating Msg4 or MsgB after the final reception of one or more repetitions.

[0177] Example 31 includes the subject matter of any variation of any of Examples 25 to 30, wherein Msg3 or MsgA PUSCH includes a Media Access Control (MAC CE) comprising an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with inactive RRC data transmission, or Msg3 or MsgA PUSCH is scrambled with an I-RNTI / truncated I-RNTI, and wherein the operation further includes determining the I-RNTI / truncated I-RNTI associated with inactive RRC data transmission based on one of the following: a MAC CE including an I-RNTI / truncated I-RNTI, or descrambling Msg3 or MsgA PUSCH with a set of potential I-RNTIs / truncated I-RNTIs including an I-RNTI / truncated I-RNTI.

[0178] Example 32 includes the subject matter of any variation of any of Examples 31, wherein the operation includes generating MsgB, and wherein MsgB includes a Random Access Response (RAR) and the MAC CE includes an I-RNTI / truncated I-RNTI; or MsgB includes at least one of an uplink (UL) grant scrambled with an I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled with an I-RNTI / truncated I-RNTI.

[0179] Example 33 includes the subject matter of any variation of any of Examples 31, wherein the operation includes generating Msg4; wherein Msg4 includes at least one of an uplink (UL) grant scrambled by I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by I-RNTI / truncated I-RNTI, or wherein Msg4 includes a DL assignment with scheduling at least partially based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), wherein the DL assignment with scheduling at least partially based on TC-RNTI includes a MAC CE containing an I-RNTI.

[0180] Example 34 is a machine-readable medium including instructions that, when executed, cause a base station (BS) to: configure a random access channel (RACH) for receiving a preamble message 1 (Msg1) or message A (MsgA) based on Radio Resource Control (RRC) inactive data transmission; receive a physical uplink shared channel (PUSCH) message 3 (Msg3) or message A (MsgA) including uplink (UL) data via the configured resources; and transmit a message 4 (Msg4) or message B (MsgB) in response to Msg3 or MsgA PUSCH.

[0181] Example 35 includes the subject matter of any variation of any of the embodiments of Example 34, wherein the RACH configuration is a dedicated RACH configuration for RRC inactive data transmission.

[0182] Example 36 includes the subject matter of any variation of any of Examples 34, wherein the instructions, when executed, also cause the BS to configure a dedicated preamble group, and the Msg1 or MsgA preamble is one of the dedicated preamble groups for RRC inactive data transmission.

[0183] Example 37 includes the subject matter of any variation of any of Examples 34, wherein the preamble is a shared preamble for the RACH configuration of RRC inactive data transmission and the RACH configuration of the RRC recovery process.

[0184] Example 38 includes the subject matter of any variation of any of Examples 34 to 37, wherein the instructions, when executed, also cause the BS to: configure the uplink data size for RRC inactive data transmission and configure the radio link quality threshold for RRC inactive data transmission, or configure the radio link timing threshold for RRC inactive data transmission based on one or more of Timing Advance (TA) or Timing Alignment Command (TAC).

[0185] Example 39 includes the subject matter of any variation of any of Examples 34 to 38, wherein the instructions, when executed, further cause BS to: configure a radio link quality threshold to determine a repetition value for Msg3 or MsgA PUSCH, or configure a repetition value and transmit message 2 (Msg2) using the repetition value; receive one or more repetitions of Msg3 or MsgA PUSCH according to the repetition value; and transmit Msg4 or MsgB after the final reception of one or more repetitions.

[0186] Example 40 includes the subject matter of any variation of any of Examples 34 to 39, wherein Msg3 or MsgA PUSCH includes a Media Access Control CE (MAC CE) that includes an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with inactive RRC data transmission, or Msg3 or MsgA PUSCH is scrambled with an I-RNTI / truncated I-RNTI, and wherein the instructions, when executed, also cause the BS to determine the I-RNTI / truncated I-RNTI associated with inactive RRC data transmission based on one of the following: a MAC CE including an I-RNTI / truncated I-RNTI, or descrambling Msg3 or MsgA PUSCH with a set of potential I-RNTIs / truncated I-RNTIs including an I-RNTI / truncated I-RNTI.

[0187] Example 41 includes the subject matter of any variation of any of Examples 40, wherein the instruction transmits MsgB when executed, and wherein MsgB includes a Random Access Response (RAR) and the MAC CE includes an I-RNTI / truncated I-RNTI; or MsgB includes at least one of an uplink (UL) grant scrambled with an I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled with an I-RNTI / truncated I-RNTI.

[0188] Example 42 includes the subject matter of any variation of any of the embodiments of Example 40, wherein the instruction transmits Msg4 when executed; wherein Msg4 includes at least one of an uplink (UL) grant scrambled by I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by I-RNTI / truncated I-RNTI, or wherein Msg4 includes a DL assignment with scheduling at least partially based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), wherein the DL assignment with scheduling at least partially based on TC-RNTI includes a MAC CE containing an I-RNTI.

[0189] Example 43 is a base station (BS) including: a communication circuit; and one or more processors communicatively coupled to the communication circuit and configured to: receive a message 1 (Msg1) or message A (MsgA) preamble via the communication circuit using a random access channel (RACH) configuration based on radio resource control (RRC) inactive data transmission; receive a message 3 (Msg3) or message A (MsgA) physical uplink shared channel (PUSCH) via the communication circuit, including uplink (UL) data via the configured resources; and transmit a message 4 (Msg4) or message B (MsgB) via the communication circuit in response to Msg3 or MsgA PUSCH.

[0190] Example 44 includes the subject matter of any variation of any of the embodiments of Example 43, wherein the RACH configuration is a dedicated RACH configuration for RRC inactive data transmission.

[0191] Example 45 includes the subject matter of any variation of any of Examples 43, wherein one or more processors are configured with a dedicated preamble group, and the Msg1 or MsgA preamble is one of the dedicated preamble groups for RRC inactive data transmission.

[0192] Example 46 includes the subject matter of any variation of any of Examples 43, wherein the preamble is a shared preamble for the RACH configuration of RRC inactive data transmission and the RACH configuration of the RRC recovery process.

[0193] Example 47 includes the subject matter of any variation of any of Examples 43 to 46, wherein one or more processors are further configured to: configure the uplink data size for RRC inactive data transmission and configure the radio link quality threshold for RRC inactive data transmission, or configure the radio link timing threshold for RRC inactive data transmission based on one or more of timing advance (TA) or timing alignment command (TAC).

[0194] Example 48 includes the subject matter of any variation of any of Examples 43 to 47, wherein one or more processors are further configured to: configure a radio link quality threshold to determine a repetition value for Msg3 or MsgA PUSCH, or configure a repetition value and transmit message 2 (Msg2) using the repetition value; receive one or more repetitions of Msg3 or MsgA PUSCH according to the repetition value; and transmit Msg4 or MsgB after the final reception of one or more repetitions.

[0195] Example 49 includes the subject matter of any variation of Examples 43 to 48, wherein Msg3 or MsgA PUSCH includes a Media Access Control CE (MAC CE) that includes an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with inactive RRC data transmission, or Msg3 or MsgA PUSCH is scrambled with an I-RNTI / truncated I-RNTI, and one or more processors are further configured to determine the I-RNTI / truncated I-RNTI associated with inactive RRC data transmission based on one of the following: a MAC CE including an I-RNTI / truncated I-RNTI, or descrambling Msg3 or MsgA PUSCH with a set of potential I-RNTIs / truncated I-RNTIs including an I-RNTI / truncated I-RNTI.

[0196] Example 50 includes a subject matter of any variation of any of Examples 49, wherein one or more processors transmit MsgB, and wherein MsgB includes a Random Access Response (RAR) and the MAC CE includes an I-RNTI / truncated I-RNTI; or MsgB includes at least one of an uplink (UL) grant scrambled with an I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled with an I-RNTI / truncated I-RNTI.

[0197] Example 51 includes a subject matter of any variation according to any one of Examples 49, wherein one or more processors transmit Msg4; wherein Msg4 includes at least one of an uplink (UL) grant scrambled by I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by I-RNTI / truncated I-RNTI, or wherein Msg4 includes a DL assignment with scheduling at least partially based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), wherein the DL assignment with scheduling at least partially based on TC-RNTI includes a MAC CE containing an I-RNTI.

[0198] Example 52 includes an apparatus comprising components for performing any of the operations described in Examples 1 to 24.

[0199] Example 53 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations described in Examples 1 to 24.

[0200] Example 54 includes an apparatus comprising: a memory interface; and processing circuitry configured to perform any of the operations described in Examples 1-24.

[0201] Example 55 includes a user equipment (UE) configured to perform any of the operations described in Examples 1 to 24.

[0202] Example 56 includes an apparatus comprising components for performing any of the operations described in Examples 34 to 51.

[0203] Example 57 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations described in Examples 34 to 51.

[0204] Example 58 includes an apparatus comprising: a memory interface; and processing circuitry configured to perform any one of the operations described in Examples 34 to 51.

[0205] Example 59 includes a base station (BS) configured to perform any of the operations described in Examples 34 to 51.

[0206] The above description of exemplary aspects of the subject matter of this disclosure, including those described in the specification summary, is not intended to be exhaustive or to limit the disclosed aspects to their precise forms. While specific aspects and embodiments have been described herein for illustrative purposes, various modifications may be contemplated within the scope of such aspects and embodiments, as will be appreciated by those skilled in the art.

[0207] In this regard, although the subject matter disclosed herein has been described in conjunction with various aspects and corresponding drawings, it should be understood that other similar aspects may be used, or modifications and additions may be made to the described aspects, to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the described aspects. Therefore, the disclosed subject matter should not be limited to any single aspect described herein, but should be interpreted in accordance with the breadth and scope of the appended claims.

[0208] In particular, regarding the various functions performed by the aforementioned components or structures (components, devices, circuits, systems, etc.), unless otherwise stated, the terminology used to describe such components (including references to "component") is intended to correspond to any component or structure that performs the specified function of the said component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs the function in the exemplary embodiments shown herein. Furthermore, while certain features have been disclosed with respect to only one of the plurality of embodiments, it may be desirable and advantageous for any given or particular application to combine such features with one or more other features of other embodiments.

Claims

1. A baseband processor, comprising: Memory interface and communication interface; as well as Processing circuitry, communicatively coupled to the memory interface and the communication interface, and performing operations upon execution of instructions received from the memory interface, the operations including: In response to determining that RRC inactive data transmission is being performed under the inactive state of Radio Resource Control (RRC), a random access channel (RACH) preamble is generated; Uplink (UL) data is provided to the communication interface for the RRC inactive data transmission, wherein the RRC inactive data transmission includes a Media Access Control (MAC) element (MAC CE) having an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the RRC inactive data transmission is scrambled based on the I-RNTI / truncated I-RNTI; A contention resolution (CR) timer is started after the RRC inactive data transmission, wherein the CR timer is set to end at the CR duration limit; and In response to the RRC inactive data transmission, a RACH message is received before the CR timer ends at the CR duration limit, wherein the RACH message includes at least one of an uplink (UL) grant or downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or the RACH message includes a DL assignment based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI) included in the MAC CE.

2. The baseband processor according to claim 1, wherein the RACH preamble is based on a RACH configuration, the RACH configuration being a dedicated RACH configuration for the RRC inactive data transmission.

3. The baseband processor of claim 1, wherein the operation further includes selecting the RACH preamble from a dedicated preamble group for the RRC inactive data transmission.

4. The baseband processor according to claim 1, wherein the RACH preamble is a shared preamble for the RACH configuration of the RRC inactive data transmission and the RACH procedure of the RRC recovery process.

5. The baseband processor according to any one of claims 1 to 4, wherein the UL data is less than or equal to the pre-configured uplink data size; and The determination to perform the RRC inactive data transmission is based on at least one of a predefined radio link quality threshold or a predefined radio link timing threshold.

6. The baseband processor according to any one of claims 1 to 4, wherein the RRC inactive data transmission is assigned a repetition value, the repetition value being determined by the processing circuitry based on radio link quality or one or more of L1, L2 or L3 signaling; The Hybrid Automatic Repeat Request (HARQ) process or L1 process generates one or more repeats of the RRC inactive data transmission based at least in part on the repeat value; and The operation further includes, after the last repetition of the one or more repetitions, initiating either a Random Access Response (RAR) window associated with the received RACH message or a Contention Resolution (CR) timer associated with the received RACH message.

7. A user equipment (UE) device, comprising: Communication circuits; as well as A processor, coupled to the communication circuit, and configured to cause the UE device to: In response to determining that Radio Resource Control (RRC) inactive data transmission is to be performed, a Random Access Channel (RACH) preamble is transmitted via the communication circuit. RRC inactive data transmission, including uplink (UL) data, is transmitted via the communication circuit, wherein the RRC inactive data transmission includes a Media Access Control (MAC) element (MAC CE) having an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the RRC inactive data transmission is scrambled based on the I-RNTI / truncated I-RNTI; After the RRC inactive data transmission is generated, a contention resolution (CR) timer is started, wherein the CR timer is set to end at the CR duration limit; as well as In response to the RRC inactive data transmission, a RACH message is received via the communication circuit before the CR timer ends at the CR duration limit, wherein the RACH message includes at least one of an uplink (UL) grant or downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or the RACH message includes a DL assignment based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI) included in the MAC CE.

8. The UE device according to claim 7, wherein the RACH preamble is based on a RACH configuration, the RACH configuration being a dedicated RACH configuration for the RRC inactive data transmission.

9. The UE device of claim 7, wherein the processor is further configured to cause the UE device to select the RACH preamble from a dedicated preamble group for the RRC inactive data transmission.

10. The UE device according to claim 7, wherein the RACH preamble is a shared preamble for the RACH configuration of the RRC inactive data transmission and the RACH procedure of the RRC recovery procedure.

11. The UE device according to any one of claims 7 to 10, wherein the UL data is less than or equal to the pre-configured uplink data size.

12. The UE device of claim 11, wherein determining to perform the RRC inactive data transmission is based on at least one of a predefined radio link quality threshold or a predefined radio link timing threshold.

13. The UE device according to any one of claims 7 to 10, wherein the RRC inactive data transmission is assigned a repeat value, the repeat value being determined by the processor based on one or more of radio link quality or L1, L2 or L3 signaling; The Hybrid Automatic Repeat Request (HARQ) process or L1 process transmits one or more repeats of the RRC inactive data transmission based at least in part on the repeat value; and After the last repetition of the one or more repetitions, the processor is further configured to cause the UE device to initiate either a Random Access Response (RAR) window associated with the received RACH message or a Contention Resolution (CR) timer associated with the received RACH message.

14. A method for a user equipment (UE) device, the method comprising: The random access channel (RACH) preamble associated with inactive data transmission of Radio Resource Control (RRC); Transmitting RRC inactive data transmission, wherein the RRC inactive data transmission is a Physical Uplink Shared Channel (PUSCH) message including uplink (UL) data, wherein the RRC inactive data transmission includes a Media Access Control (MAC) element (CE) having an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the RRC inactive data transmission is scrambled based on the I-RNTI / truncated I-RNTI; After transmitting the RRC inactive data, a contention resolution (CR) timer is started, wherein the CR timer is set to end at the CR duration limit; as well as In response to the RRC inactive data transmission, a RACH message is received before the CR timer ends at the CR duration limit, wherein the RACH message includes at least one of an uplink (UL) grant or downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or the RACH message includes a DL assignment based on a Temporary Cell Radio Network Temporary Identifier (TC-RNTI) included in the MAC CE.

15. The method of claim 14, wherein the RACH preamble is based on a RACH configuration, the RACH configuration being a dedicated RACH configuration for the RRC inactive data transmission.

16. The method of claim 14, further comprising selecting the RACH preamble from a dedicated preamble group for the RRC inactive data transmission.

17. The method of claim 14, wherein the RACH preamble is a shared preamble for the RACH configuration of the RRC inactive data transmission and the RACH procedure of the RRC recovery procedure.

18. The method according to any one of claims 14 to 17, wherein the UL data is less than or equal to a pre-configured uplink data size.

19. The method of claim 18, wherein the RRC inactive data transmission is performed based on at least one of a predefined radio link quality threshold or a predefined radio link timing threshold.

20. The method according to any one of claims 14 to 17, wherein the RRC inactive data transmission is assigned a repeat value, the repeat value being determined based on radio link quality or one or more of L1, L2 or L3 signaling; The Hybrid Automatic Repeat Request (HARQ) process or L1 process generates one or more repeats of the RRC inactive data transmission based at least in part on the repeat value; and After the last repetition of the one or more repetitions, the method further includes initiating either a Random Access Response (RAR) window associated with the received RACH message or a Contention Resolution (CR) timer associated with the received RACH message.

Images