Systems and methods for providing random access channel (RACH) signaling to user equipment (UE) during inactive direct transmission

Abstract

The techniques discussed herein can facilitate inactive state transmissions of a base station (BS) via a 4-step or 2-step inactive state RACH procedure. One exemplary aspect is a base station comprising: a communication circuit; and one or more processors communicatively coupled to the communication circuit and configured to: receive a message 1 (Msg1) or a message A (MsgA) preamble via the communication circuit based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receive a message 3 (Msg3) or a MsgA physical uplink shared channel (PUSCH) including uplink (UL) data via the communication circuit via configured resources; and transmit a message 4 (Msg4) or a message B (MsgB) via the communication circuit in response to the Msg3 or the MsgA PUSCH.

Description

Background Art

[0001] Mobile communications in 5G, the next generation of wireless communication systems, 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 will target common and sometimes conflicting performance standards and provide services for a wide range of application domains, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and other communications. Generally speaking, NR will evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) Advanced technology and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 is a state diagram illustrating three radio resource control (RRC) states in which a device such as user equipment (UE) may operate.

[0003] Figure 2 An exemplary radio resource control (RRC) resumption procedure for a UE in an inactive state is shown.

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

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

[0006] Figure 4A The delay in data transmission for a UE transitioning from an inactive state to a connected state is shown.

[0007] Figure 4B Delay in data transmission when the UE performs direct data transmission to a base station (BS) while in an inactive state is shown.

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

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

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

[0011] Figure 6B A flow chart of a method for performing 2-step RACH inactive state communication between a BS and a UE with a repetition scheme is shown.

[0012] Figure 7A A flow chart of a method for performing 4-step RACH inactive state communication between a BS and a UE with RACH and UE differentiation based on an Inactive Radio Network Temporary Identifier (I-RNTI) or a truncated I-RNTI is shown.

[0013] Figure 7B A flow chart of a method for performing 2-step RACH inactive state communication between a BS and a UE with I-RNTI or truncated I-RNTI based differentiation of RACH and UE is shown.

[0014] Figure 8A A flow chart of a method for performing 4-step RACH inactive state communication between a BS and a UE with feedback of successful transmissions is shown.

[0015] Figure 8B A flow chart of a method for performing 2-step RACH inactive state communication between a BS and a UE with feedback of successful transmissions is shown.

[0016] Figure 9A A flow chart of a method for performing RACH inactive state communication between a BS and a UE with a fallback mechanism to an RRC recovery procedure by failing the RACH procedure or reaching a physical RACH (PRACH) retransmission value is shown.

[0017] Figure 9B A flow chart of a method for performing RACH inactive state communication between a BS and a UE with a fallback mechanism to an RRC recovery procedure by failing to reach a radio quality threshold is shown.

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

[0019] Figure 11 It is a flowchart of RRC inactive data transmission of BS.

[0020] Figure 12 The flowchart is a fallback mechanism of the RRC recovery process to perform RRC inactive data transmission of the UE.

[0021] Figure 13 is a block diagram illustrating the architecture of a system including a core network (CN), eg, a fifth generation (5G) CN (5GC), according to various aspects.

[0022] Figure 14is a diagram illustrating example components of an apparatus that may be employed in accordance with various aspects discussed herein.

[0023] Figure 15 is a diagram illustrating an exemplary interface of baseband circuitry that may be employed in accordance with various aspects discussed herein.

[0024] Figure 16 is a block diagram illustrating a system that facilitates power management associated with a wireless modem in accordance with various aspects discussed herein. DETAILED DESCRIPTION

[0025] The present disclosure will now be described with reference to the accompanying drawings, wherein similar reference numerals are used to refer to similar elements throughout the text, and the structures and devices shown therein need not be 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, a 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 a user equipment with a processing device (e.g., a mobile phone or other devices configured to communicate via a 3GPP RAN, etc.). By way of example, an application and a server running on a server can also be a component. One or more components can reside in a process, and a component can be located on a computer and / or distributed between two or more computers. A group of elements or a group of other components can be described herein, wherein the term "group" can be interpreted as "one or more" unless the context indicates otherwise (e.g., "empty group", "a group of two or more Xs", etc.).

[0026] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to 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 across a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0027] As another example, a component may be a device that has a specific functionality provided by a mechanical component that operates through electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific functionality through an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that provides the functionality of the electronic component.

[0028] The use of the word "exemplary" is intended to present concepts in a concrete 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 specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive permutation. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more," unless otherwise specified or clear from the context to be directed to the singular. 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 inclusive in a manner similar to the term "comprising." Furthermore, where one or more numbered items are discussed (e.g., "a first X," "a second X," etc.), generally, the one or more numbered items can be different or they can 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 "circuitry" may refer to, may be a part of, or may include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functionality. In some aspects, a circuit may be implemented in one or more software or firmware modules, or functionality 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 may operate at least partially in hardware.

[0030]

[0010] Various aspects discussed herein may be directed to facilitating wireless communications, and the nature of these communications may vary.

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

[0032] An important aspect of wireless devices is the ability to enter a low-power state when not engaged in data transmission or reception. By entering a low-power state, devices are able to achieve a balance between acceptable communication performance, acceptable battery consumption, and resource management. As such, devices have evolved to initially support Idle and Connected transition states, and now include Paused and Inactive transition states, which improve latency and optimize battery consumption.

[0033] The primary purpose of the Inactive state is to enable the device to return to the Connected state and establish data communications as efficiently and quickly as possible. To facilitate efficient transitions between the Connected and Inactive states, information such as identifiers and security information is stored and passed between the device and the network before the device enters the Inactive state. This stored information is then used to facilitate efficient transitions from the Inactive state to the Connected state.

[0034] While the inactive state improves latency and optimizes battery consumption, latency and battery consumption still come at a cost in existing systems when a user equipment (UE) communicates uplink (UL) or downlink (DL) data with the network. For a UE to perform any dedicated transmission or reception according to existing technologies, resources, time, and battery consumption are spent transitioning between states. Therefore, to achieve further optimized devices and networks, data transmission needs to occur while the device is in the inactive state.

[0035] Various aspects of the present disclosure are directed to New Radio (NR) devices that are capable of data transmission and reception when the device is in an idle state without transitioning to a connected state. One way to establish data communications when in the idle state is by using a random access channel (RACH) procedure configured for inactive direct data transmission with large data packet sizes. In doing so, data up to a size associated with an inactive data limit can be transmitted in the inactive state. Various aspects can facilitate inactive state data transmission in accordance with one or more advantageous features discussed in the present disclosure. The features discussed herein in conjunction with inactive direct data transmission can enable one or more of the following: large packet sizes, efficient transmission of data, differentiation of RACH configurations for device states, differentiation of RACH for inactive devices, support for feedback to inactive devices, and fallback to a recovery procedure when appropriate.

[0036] Figure 11 is a state diagram illustrating three radio resource control (RRC) states in which a device such as a UE may operate. In the idle state, the UE is disconnected from the core network (CN). While idle, the UE performs cell reselection and may receive paging messages from the CN via the cell in which the UE is camped. To enter the connected state, the UE performs an RRC connection procedure 110, in which the UE connects to the CN and the radio access network (RAN) using a RACH procedure (described in more detail below). 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 both the UE and the RAN know all parameters required for unicast communication between the UE and the RAN. The UE context, including the UE's access stratum (AS) context (e.g., the UE's cell radio network temporary identifier (C-RNTI) and the cell identity of the primary cell) and the RRC configuration for the UE (e.g., radio bearers and security information), is stored in the RAN and also in the UE.

[0037] The UE can move from the connected state back to the idle state by performing an RRC release procedure 120. When the UE returns to the idle state, the UE context is deleted from the UE and the RAN. As indicated by 130 and 160, the UE can also default to the idle state from the connected state or the inactive state when no camped cell can be found.

[0038] The inactive state is introduced in 5G to provide an intermediate state between the idle state and the connected state, which will speed up the reconnection process by eliminating some of the signaling used to transition from the idle state to the connected state. The inactive state is beneficial for UEs that do not communicate with the RAN frequently and allows power savings compared to these UEs remaining in the connected state. To enter the inactive state, the UE performs an RRC suspension procedure 140, in which the UE context is stored by the UE and the serving base station (BS), and then an RRC release procedure occurs. The BS can be any kind of BS, for example, 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 with the CN (i.e., it is still in connection management (CM)-CONNECTED, unlike the idle state where the UE is not in CM-CONNECTED).

[0039] While in the Inactive state, a 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 does not have dedicated AS resources for unicast communication and is therefore unable to perform any dedicated data transmission or reception. Since the UE cannot perform dedicated data reception while in the Inactive state, when downlink data is to be transmitted to the UE, the RAN pages the UE to trigger the UE to enter the Connected state. When the UE has uplink data to transmit, it first enters the Connected state before transmitting the uplink data.

[0040] To enter the connected state from the inactive state, the UE performs an RRC recovery procedure 150, in which the UE context is retrieved from the UE's last serving cell and restored to the UE and the (new) serving cell. Compared to the transition from the idle state to the connected state, the RRC recovery procedure speeds up the transition to the connected state by allowing the previous connection to be restored without having to perform extensive NAS signaling.

[0041] Figure 2 An exemplary RRC resume procedure 250 is outlined in FIG. The UE is initially in an inactive state. At 210, the UE transmits an RRC ResumeRequest to the BS on which it is camped using a RACH procedure. The RRC ResumeRequest includes the UE's Inactive Radio Network Temporary Identifier (I-RNTI), which was assigned by the network to the UE when it entered the inactive state. The network uses the I-RNTI provided with the ResumeRequest to identify the UE and the last serving cell so that the new serving cell can obtain the UE context from the last serving cell.

[0042] exist Figure 3A and Figure 3B Two types of contention-based RACH (CBRA) procedures 310 and 360 that may be used to transmit an RRC ResumeRequest are shown in more detail in FIG. Although the RACH procedure is described herein in the context of transmitting a ResumeRequest, the UE uses the RACH procedure whenever it desires to achieve uplink synchronization with the BS to enter a connected state from an idle state or an inactive state, or to obtain resources for uplink transmission in the connected state.

[0043] Figure 3AA 4-step contention-based RACH (CBRA) process is shown. At 320, using a predetermined RACH preamble opportunity, the UE transmits Msg1 including a preamble that identifies 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 state or idle state, the UE is configured with contention-free RACH (CFRA), a preamble, and optionally also a physical uplink shared channel (PUSCH) resource. Because it is possible that another UE selects the same preamble via the same preamble RACH resource, 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 measures.

[0044] At 330, the BS transmits Msg2 containing a random access response (RAR), which includes downlink control information (DCI) that may be scrambled based on the preamble transmitted by the UE. The DCI includes information that allows the UE to decode the physical downlink shared channel (PDSCH) that conveys the UE's identifier and the allocation of uplink (UL) resources for use by the UE. At 340, the UE transmits Msg3 using the UL resources received in the RAR. In this example, Msg3 will include a ResumeRequest. In other examples, Msg3 may include other data.

[0045] The UE may establish a contention timer when sending Msg3 and monitor the Physical Downlink Control Channel (PDCCH) for Msg4 sent by the BS at 350. Msg4 includes a Level 2 Medium Access Control Physical Data Unit (L2 MAC PDU) that includes a Contention Resolution MAC Control Element (CE) used by the UE to determine whether the RACH procedure was successful. When the UE does not receive Msg4 before the timer expires, it assumes that the RACH procedure was unsuccessful. At this point, the UE has successfully notified the gNB (e.g., Figure 2 Step 210 is completed).

[0046] Figure 3B A 2-step CBRA process 360 is shown. At 370, the UE transmits the Figure 3AThe UE sends a message to the BS (e.g., a gNB) at 380 that includes a fallback RAR that includes an uplink grant for the UE to retransmit MsgA when the gNB detects MsgA but is unable to decode it. If the gNB successfully decodes MsgA, then MsgB includes a success RAR that includes a new UL or downlink (DL) grant for subsequent transmission of data (not a retransmission of the RRC ResumeRequest). At this point, the UE has successfully notified the BS (e.g., a gNB) of its intent to enter the connected state. Figure 2 Step 210 is completed).

[0047] Return to Figure 2 , at 220, after the BS has received the ResumeRequest, the BS requests the UE context information stored by the last serving BS as part of the RRC suspension procedure. At 230, the last serving BS provides the UE context information to the new serving BS. At 240, the BS transmits an RRC resume 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 switch request to update the radio bearers of the UE to the access and mobility management function (AMF) which is the interface between the BS and the CN. At 280, the AMF confirms in response to the BS that the path switch is complete. At 290, the BS notifies the last 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 also Figure 4A , it can be seen that the recovery process introduces a significant delay between the time the UE has data to transmit and the time the UE is able to transmit the data. This document discloses systems, circuits, and techniques for allowing a UE to perform a data transmission directly to a BS while in an inactive state without transitioning to a connected state, such as Figure 4B shown.

[0049] Figure 5AA flow chart of a method 500A for performing inactive state communication between a BS and a UE using a radio link quality threshold is shown. At 502, at a time before the UE can transmit or receive data, the BS can broadcast a message including various parameters to the UE. The parameters may include a RACH configuration (e.g., multiple configured or predefined configured Cfg#N, etc.), a RACH preamble, an UL grant, and transmission conditions specified for inactive state communication. The RACH preamble may include an identifier of the UE. The UL grant may include a threshold that limits the maximum message size for transmission. The transmission conditions may include a radio link quality threshold. The predefined radio link quality threshold 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 plus 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 determining at 502 that the UL data available for communication is less than a UL grant threshold broadcast or determining that the radio link quality of the UE is within a predefined radio link quality threshold.

[0051] After the above determination, the UE may proceed to 504, where the UE transmits a Msg1 RACH preamble to the BS via the PRACH. The preamble may include an identifier identifying the UE. The preamble may be selected from the preambles designated by the BS for inactive state communications in 502. Msg1 may be transmitted according to the RACH configuration (e.g., Cfg#N, etc.) designated by the BS for inactive state communications in 502.

[0052] At 506, the BS may transmit Msg2 as a random access response (RAR) to the UE, which Msg2 may indicate timing (e.g., via a timing advance command (TAC)) and the UE's UL grant for RRC inactive data transmission. At 507, the UE transmits Msg3 PUSCH to the BS. Msg3 PUSCH includes UL data transmission for inactive state communication. At 508, the BS may transmit Msg4 to the UE during a 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 may be performed while the UE remains in the inactive state. Figure 2 Compared to the RRC recovery process described in , method 500A can reduce the delay in transmitting data to the BS.

[0053] Figure 5BA flow chart of a method 500A for performing inactive state communication between a base station and a user equipment terminal (UE) using radio link timing thresholds is shown. At 510, at a time before the UE can transmit or receive data, the base station can broadcast a message including various parameters to the UE. The parameters can include a RACH configuration (e.g., multiple configured or predefined configured Cfg#N, etc.), a RACH preamble, an UL grant, and transmission conditions specified for inactive state communication. The RACH preamble can include an identifier for the UE. The UL grant can include a threshold that limits the maximum message size for transmission. The transmission conditions can include a radio link timing threshold. The predefined radio link timing threshold can include a TAC threshold.

[0054] After 510, the UE may have data available for communication with the BS, and the UE may determine to perform RRC inactive data transmission.In 510, the UE may determine that UL data available for communication is less than a UL grant threshold.

[0055] After the above determination, the UE may proceed to 512, where the UE may transmit a Msg1 RACH preamble to the BS via the PRACH. The Msg1 RACH preamble may include an identifier identifying the UE. At 510, a preamble may be selected from preambles designated by the BS for inactive state communications. At 510, Msg1 may be transmitted according to the RACH configuration designated by the BS for inactive state communications (e.g., Cfg#N, etc.).

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

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

[0058] At 518, the BS may transmit Msg4 to the UE during the CR window, and the UE may determine that the RRC inactive data transmission has been successfully completed in response to receiving Msg4. The method 500B may be performed while the UE remains in the inactive state. Figure 2 Compared to the RRC recovery process described in , method 500B can reduce the delay in transmitting data to the BS.

[0059] Figure 6A A flow chart of a method 600A for performing four-step RACH inactive state communication between a base station and a user equipment terminal (UE) using a repetition scheme is shown. At 602, at a time before the UE can transmit or receive data, the base station can broadcast a message including various parameters to the UE. The parameters can include a RACH configuration (e.g., multiple configured or predefined configured Cfg#N, etc.), a RACH preamble, and an UL grant designated for inactive state communication. The RACH preamble can include an identifier for the UE. The UL grant can include a threshold that limits the maximum message size for transmission.

[0060] At 604, the UE may determine to transmit a Msg1 RACH preamble to the base station via a PRACH. The Msg1 RACH preamble may include an identifier identifying the UE. At 602, a preamble may be selected from preambles designated by the base station for inactive state communications. Msg1 may be transmitted according to a RACH configuration (e.g., Cfg#N, etc.) designated by the base station for inactive state communications.

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

[0062] Figure 6B A flow chart of a method 600B for performing 2-step RACH inactive state communication between a BS and a UE using a repetition scheme is shown. At 612, at a time before the UE can transmit or receive data, the BS can broadcast a message including various parameters to the UE. The parameters may include a RACH configuration (e.g., multiple configured or predefined configured Cfg#N, etc.), a RACH preamble, an UL grant, and a number of MsgA repetitions designated for inactive state communication. Alternatively, the number of MsgA repetitions may be configured by L1, L2, or L3 signaling, or the UE may configure the number of repetitions based on radio quality. Radio quality may include one or more of RSRQ, RSRP, or SINR. The RACH preamble may include an identifier of the UE. The UL grant may include a threshold that limits the maximum message size for transmission.

[0063] After 612, the UE may determine to transmit MsgA to the BS at 614 and 616. At 614, the UE may transmit a MsgA RACH preamble via a PRACH, which may include an identifier identifying the UE. At 612, a preamble may be selected from preambles designated by the BS for inactive state communications. At 612, the MsgA may be transmitted according to the RACH configuration designated by the BS for inactive state communications (e.g., Cfg#N, etc.).

[0064] At 616, the UE may further prepare a MsgAPUSCH including UL data transmission for inactive state communication. Hybrid automatic repeat request (HARQ) may repeatedly transmit MsgA until the BS acknowledges MsgA or until the number of repetitions is reached. Alternatively, the L1 process repeatedly transmits MsgA until the number of repetitions is reached. After the number of repetitions is reached, a RAR window associated with MsgB may be initiated. Upon receiving MsgA, the BS may transmit MsgB to the UE at 618 during the RAR window, and the UE may determine that the inactive data transmission has been successfully completed in response to receiving MsgB. Method 600B may be performed while the UE remains in an inactive state. With Figure 2 Compared to the RRC recovery process described in , method 600B can reduce the delay in transmitting data to the BS.

[0065] Figure 7AA flow chart of a method 700A for performing four-step RACH inactive state communication between a base station and a user equipment terminal (UE) using RACH and a UE-based I-RNTI (e.g., a full I-RNTI (comprising 24 bits) or a truncated I-RNTI (comprising 16 bits)) is shown. At 702, at a time before the UE can transmit or receive data, the base station can broadcast a message to the UE including various parameters, which may include an UL grant designated for inactive state communication. The UL grant may include a threshold that limits the maximum message size for transmission.

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

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

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

[0069] Figure 7B A flow chart of a method 700A for performing two-step RACH inactive state communication between a base station and a UE using RACH and UE-based I-RNTI differentiation (e.g., which can be the UE's full I-RNTI or the UE's truncated I-RNTI) is shown. The I-RNTI can consist of 24 bits, and the truncated I-RNTI can consist of 16 bits. At 712, some time before the UE can transmit or receive data, the base station can broadcast a message to the UE including various parameters, which can include an UL grant designated for inactive state communication. The UL grant can include a threshold that limits the maximum size for transmission.

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

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

[0072] In an alternative aspect, at 714 and 716, the UE may use I-RNTI / truncated I-RNTI to scramble the MsgAPUSCH transmission. After the BS receives MsgA, the BS may descramble MsgA containing UL data. The BS may descramble MsgA with a set of one or more possible I-RNTI / truncated I-RNTI including I-RNTI. At 718, the BS may transmit MsgB to the UE, and the UE may determine that the RRC inactive data transmission has been successfully completed in response to receiving MsgB. The BS may use I-RNTI / truncated I-RNTI to schedule MsgB transmission or subsequent data transmission that may occur in the inactive state. Method 700B may be performed while the UE remains in the inactive state. Figure 2 Compared to the RRC recovery process described in , method 700B can reduce the delay in transmitting data to the BS.

[0073] Figure 8A A flow chart of a method 800A for performing four-step RACH inactive state communication between a base station and a user equipment terminal (UE) with feedback on successful transmissions is shown. At 802, at a time before the UE can transmit or receive data, the base station can broadcast a message to the UE including various parameters, which may include an UL grant designated for inactive state communication. The UL grant may include a threshold that limits the maximum message size for transmission.

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

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

[0076] After the BS receives Msg3, the BS may read the MAC CE with the I-RNTI / truncated I-RNTI and may distinguish the RACH as inactive communication and may identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. In some embodiments, at 810, the BS may transmit Msg4 in response to Msg3. Msg4 of 810 may include a DL allocation scheduled by a temporary cell radio network temporary identifier (TC-RNTI), and the DL allocation may include a MAC CE. When the UE receives Msg4 within the CR duration limit, the UE may consider the RRC inactive data transmission to be successful.

[0077] In an alternative aspect, at 808, the UE may scramble the Msg3 PUSCH transmission using the I-RNTI / truncated I-RNTI. When transmitting the Msg3, the UE may start a contention CR with the CR timer set to end at the CR duration limit. After the BS receives the Msg3, the BS may descramble the Msg3 containing the MAC CE with the I-RNTI / truncated I-RNTI and UL data. The BS may descramble the Msg3 with a set of one or more possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI. The BS may read the MAC CE with the I-RNTI / truncated I-RNTI and may distinguish the RACH as an inactive communication and may identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. In some embodiments, instead of transmitting Msg4 as described in conjunction with 810, the BS may transmit Msg4 in response to Msg3 at 812, and Msg4 may include an UL grant / DL allocation for new data scrambled by the 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 flow chart of a method 800B for performing two-step RACH inactive state communication between a base station and a user equipment terminal (UE) with feedback on successful transmissions is shown. At 814, at a time before the UE can transmit or receive data, the base station can broadcast a message to the UE including various parameters, which may include an UL grant designated for inactive state communication. The UL grant may include a threshold that limits the maximum message size for transmission.

[0079] After 814, at 816 and 818, the UE may determine to transmit MsgA to the BS. At 816, the UE may transmit the MsgA RACH preamble using the PRACH. At 818, the UE may transmit the MsgA PUSCH, which includes UL data transmission for inactive state communication. MsgA may include a MAC CE with an I-RNTI / truncated I-RNTI. The MAC CE with the I-RNTI / truncated I-RNTI may be configured for inactive state communication and may identify the UE. When the UE transmits MsgA, the UE may open the MsgB window.

[0080] After the BS receives MsgA, it may read the MAC CE with the I-RNTI / truncated I-RNTI and may distinguish the RACH as inactive communication and may identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At 820 Option A, the BS may 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 may consider the RRC inactive data transmission successful.

[0081] In an alternative aspect, at 818, the UE may scramble the MsgA PUSCH transmission using the I-RNTI / truncated I-RNTI. After the BS receives the MsgA, the BS may descramble the MsgA containing the MAC CE with the I-RNTI / truncated I-RNTI and UL data. The BS may descramble the Msg3 with a set of one or more possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI. The BS may read the MAC CE with the I-RNTI / truncated I-RNTI and may distinguish the RACH as an inactive communication and may identify the UE based on the MAC CE with the I-RNTI / truncated I-RNTI. At 822, Option B, the BS may transmit MsgB in response to the MsgA. MsgB may include an UL grant / DL allocation for new data scrambled by the I-RNTI / truncated I-RNTI. When the UE receives a MsgB within the MsgB window, the UE may regard the RRC inactive data transmission as successful.

[0082] In various embodiments, in combination with Figures 5A to 8BIn the embodiments described, the RACH may be a dedicated RACH configuration for RRC inactive data communications. The BS may provide the dedicated RACH configuration to the UE, for example, in a broadcast transmission prior to the UE performing inactive state communications. The UE in the inactive state may use the dedicated RACH configuration to perform inactive state communications.

[0083] In various embodiments, in combination with Figures 5A to 8B In the described embodiments, the RACH preamble may be a dedicated RACH preamble from a dedicated RACH preamble group for RRC inactive data communications. The BS may provide the shared RACH preamble group to the UE, for example, in a broadcast transmission prior to the UE performing inactive state communications. The inactive UE may select a dedicated RACH preamble from the dedicated group for inactive state communications.

[0084] In various embodiments, these embodiments include combining Figures 5A to 8B For those embodiments described, the RACH preamble may be a shared RACH preamble for both the RACH procedure used for RRC inactive data communication and the RACH procedure used for the RRC recovery procedure.

[0085] Figure 9A A flow chart of a method 900A for performing RACH inactive state communication between a base station and a UE using a fallback mechanism to an RRC resume procedure by failing the RACH procedure or reaching a RACH preamble retransmission value is shown. The UE may 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 may follow the RRC Resume Request by transmitting an RRC Resume Request. Figure 1 and Figure 2 The recovery procedure outlined in the procedure falls back to the RRC recovery procedure.

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

[0087] The UE and BS may engage in inactive state communication via a 4-step or 2-step RACH procedure for RRC inactive data communication. The suspension criteria may include any failure of the RACH procedure, as shown in 904. At some time before or after the RACH procedure may fail, either MsgA or MsgB; or Msg1, Msg2, Msg3, or Msg4. Examples of failed RACH procedures would include information about Figures 5A to 8B If the RACH procedure fails, the UE may suspend the RACH procedure and return to the Msg1 or MsgA RRC recovery procedure by transmitting an RRC ResumeRequest to the BS as in 908. The Msg1 or MsgA RRC recovery procedure may include Figure 1 and Figure 2 The RRC recovery process described in .

[0088] In an alternative aspect, the UE may be configured to retransmit the RACH preamble for RRC inactive data transmission according to the retransmission value, such as shown at 906. The 4-step or 2-step RACH procedure for RRC inactive data communication may be repeated in the middle steps of the RACH procedure (e.g., Figures 5A to 8B However, the UE may retransmit the RACH preamble and reach the retransmission value. When the retransmission value is reached, the UE may suspend the RACH procedure and fall back to the Msg1 or MsgA RRC recovery procedure by transmitting an RRC ResumeRequest to the BS as in 908. The Msg1 or MsgA RRC recovery procedure may include Figure 1 and Figure 2 The RRC recovery process described in .

[0089] Figure 9B A flow chart of a method 900B for performing RACH inactive state communication between a base station and a UE using a fallback mechanism to an RRC resume procedure due to failure to meet a radio quality threshold is shown. The UE is configured to suspend the RACH procedure 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 may follow the RRC Resume Request that may be included in the Figure 1 and Figure 2 The recovery procedure outlined in the procedure falls back to the RRC recovery procedure.

[0090] At 910, at some time before the UE can transmit or receive data, the BS can broadcast a message including various parameters to the UE. The parameters can include a radio link quality threshold and one or more additional parameters described at 902.

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

[0092] In an alternative aspect, when the radio link quality threshold is not met at 912, the UE may suspend the RACH procedure and return to the Msg1 or MsgA RRC recovery procedure by transmitting an RRC ResumeRequest to the BS as in 916 Option B, and may subsequently complete the RRC recovery procedure, e.g., as Figure 1 and Figure 2 As stated.

[0093] Figure 10 FIG1000 is a flow chart of RRC inactive data transmission for a UE. At 1010, at a time before the UE can transmit or receive data, the UE can receive a broadcast message with various parameters. The parameters can include one or more of RACH configuration, RACH preamble, UL grant, transmission conditions, and a specified number of Msg1 repetitions for inactive state communications.

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

[0095] At 1014, the UE receives Msg2 and may include Figures 5A to 8B At 1016, the UE may transmit a Msg3 PUSCH with UL data via the configured resources. The UE may Figure 6A The repeated transmission Msg3. Msg3 may include Figures 5A to 8B One or more of the Msg3 features and operations described in .

[0096] At 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 .

[0097] In an alternative aspect, after 1010 and in response to determining to perform RRC inactive data communication, the UE may start a 2-step RACH procedure for RRC inactive data communication at 1020. The UE may transmit a MsgA that may include a MsgA RACH preamble with a PRACH and may include a MsgA PUSCH. The UE may Figure 6B The repeated transmission of Msg3. MsgA may also include Figures 5A to 8B One or more of the MsgA features and operations described in .

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

[0099] Figure 10 The 2-step and 4-step RACH described in

[15] 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 the RRC recovery procedure.

[0100] Figure 11 FIG11 is a flow chart of RRC inactive data transmission of a BS 1100. At 1110, the BS may transmit a broadcast message with various parameters. The parameters may include one or more of RACH configuration, RACH preamble, UL grant, transmission conditions, and the number of Msg1 repetitions specified for inactive state communications.

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

[0102] At 1114, the BS may transmit Msg2, which may include Figures 5A to 8BAt 1116, the BS may receive a Msg3 PUSCH with UL data via the configured resources. The BS may Figure 6A The repeated reception of Msg3. Msg3 may include Figures 5A to 8B One or more of the Msg3 features and operations described in .

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

[0104] In an alternative aspect, after 1110, the BS may receive a MsgA designated for a 2-step RACH procedure for RRC inactive data transmission at 1120. 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 Figure 6B The repeated reception of MsgA. MsgA may also include Figures 5A to 8B One or more of the MsgA features and operations described in .

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

[0106] Figure 11 The 2-step and 4-step RACH described in

[15] 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 the RRC recovery procedure.

[0107] Figure 12 1200 is a flow chart of RRC inactive data transmission for a UE with a fallback mechanism to an RRC recovery procedure. At 1210, at a time before the UE can transmit or receive data, the UE can receive a broadcast message including various parameters. The parameters can include one or more of a RACH preamble, a number of RACH preamble retransmissions, a RACH configuration, an UL grant, a radio link quality threshold, a radio link timing threshold, and a Msg3 and / or MsgA repetition value.

[0108] At 1212, the UE may engage in inactive state communications via a 4-step or 2-step RACH procedure for RRC inactive data communications. The 4-step or 2-step RACH procedure for RRC inactive data communications may follow Figures 5A to 8B At 1214, the UE may initiate a fallback to the RRC recovery procedure by satisfying a suspension criterion. The suspension criterion may include any failure of the RACH procedure. The RACH procedure may fail before or after MsgA or MsgB; or Msg1, Msg2, Msg3, or Msg4. Additionally, the failed RACH procedure may include information about Figures 5A to 8B Unsuccessful completion of any step that meets the suspension criteria is described.

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

[0110] The suspension criteria may include failure to meet a radio quality threshold. At some time before MsgA or MsgB; or before Msg1, Msg2, Msg3 or Msg4, the radio link quality threshold may not meet the suspension criteria.

[0111] After the suspension criteria are met, the UE may continue RACH inactive data communications and may generate a Msg3 or MsgA PUSCH including an RRCResumeRequest, such as shown at 1218, instead of UL data. After the UE transmits the Msg3 or MsgA with the RRCResumeRequest, at 1220, the UE may suspend the RACH process associated with the inactive state communications. Then, at 1226, the UE may complete the RRC recovery process, for example, as shown in FIG. Figure 1 and Figure 2 As stated.

[0112] After the suspension criteria are met, the UE may suspend the RACH procedure associated with the inactive state communication, such as shown at 1222. At 1224, the UE may fall back to the Msg1 or MsgA RRC resumption procedure by transmitting an RRC ResumeRequest. At 1226, the UE may complete the RRC resumption procedure, e.g., as shown in FIG. Figure 1 and Figure 2 As stated.

[0113] If the suspension criteria are not met, the UE may Figures 5A to 8B The aspects described in complete the RACH inactive data transmission at 1216.

[0114] Aspects described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 13 The architecture of a system 1300 including a CN 1320, such as a fifth generation (5G) CN (5GC), according to various aspects is shown. The system 1300 is shown to include: a UE 1301, which can be the same as or similar to one or more other UEs discussed herein; a third generation partnership project (3GPP) radio access network (wireless AN or RAN) or other (e.g., non-3GPP) AN, (R) AN 210, which can 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 a data network (DN) 1303, which can be, for example, an operator service, Internet access, or a third party service; and a fifth generation core network (5GC) 1320. 5GC 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 NSSF may be connected through various interfaces and / or reference points, such as Figure 13 shown.

[0115] Figure 14Example components of a device 1400 according to some aspects are shown. In some aspects, the device 1400 may include 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 at least as shown. The components of the illustrated device 1400 may be included in a UE or a RAN node. In some aspects, the device 1400 may include fewer components (e.g., a RAN node may not utilize application circuitry 1402 but instead include a processor / controller to process IP data received from a CN such as the 5GC 1320 or an evolved packet core (EPC)). In some aspects, the device 1400 may include additional components such as memory / storage, a display, a camera, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 1400, etc.), or input / output (I / O) interfaces. In other aspects, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

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

[0117] The baseband circuitry 1404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1404 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuitry 1406 and generate baseband signals for the transmit signal path of the RF circuitry 1406. The baseband circuitry 1404 may interact with the application circuitry 1402 to generate and process baseband signals and control the operation of the RF circuitry 1406. For example, in some aspects, the baseband circuitry 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 baseband processors 1404D of other existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). Baseband circuitry 1404 (e.g., one or more baseband processors 1404A-D) may handle various radio control functions, which may communicate with one or more radio networks via RF circuitry 1406. In other aspects, some or all of the functionality of baseband processors 1404A-D may be included in modules stored in memory 1404G and executed via central processing unit (CPU) 1404E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, and the like. In some aspects, the modulation / demodulation circuitry of baseband circuitry 1404 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functionality. In some aspects, the encoding / decoding circuitry of baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Aspects of modulation / demodulation and encoder / decoder functionality are not limited to these examples and, in other aspects, may include other suitable functionality.

[0118] In some aspects, the baseband circuitry 1404 may include one or more audio digital signal processors (DSPs) 1404F. The audio DSPs 1404F may include elements for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, the 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 of the 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, the baseband circuitry 1404 can provide communications compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 1404 can support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Aspects in which the baseband circuitry 1404 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

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

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

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

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

[0124] In some aspects, the output baseband signal and the input baseband signal can be analog baseband signals, although the scope of the various aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative aspects, the RF circuitry 1406 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 1404 can include a digital baseband interface to communicate with the RF circuitry 1406.

[0125] In some dual-mode aspects, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the various aspects is not limited in this respect.

[0126] In some aspects, the synthesizer circuit 1406 d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the various aspects is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1406 d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0128] In some aspects, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuitry 1404 or the application circuitry 1402 according to the desired output frequency. In some aspects, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuitry 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 frequency 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 a carry output) to provide a fractional division ratio. In some exemplary aspects, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these aspects, the delay element may be configured to divide the VCO cycle 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 cycle.

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

[0131] The FEM circuitry 1408 may include a receive signal path that 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 the RF circuitry 1406 for further processing. The FEM circuitry 1408 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 1406 for transmission via one or more of the one or more antennas 1410. In various aspects, amplification by either the transmit signal path or the receive signal path may be performed solely in the RF circuitry 1406, solely in the FEM circuitry 1408, or in both the RF circuitry 1406 and the FEM circuitry 1408.

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

[0133] In some aspects, the PMC 1412 can manage the power provided to the baseband circuitry 1404. Specifically, the PMC 1412 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1400 is capable of being powered by a battery, such as when the device is included in a UE, the PMC 1412 is typically included. The PMC 1412 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

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

[0135] In some aspects, the PMC 1412 can control or otherwise be 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, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 1400 can be powered down for short intervals, thereby saving power.

[0136] If there is no data traffic activity for an extended period of time, the device 1400 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The 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 down again. The device 1400 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0137] An additional power saving mode can disable the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0138] The processor of the application circuitry 1402 and the processor of the baseband circuitry 1404 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 1404 can be used, alone or in combination, to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of the application circuitry 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 a Radio Resource Control (RRC) layer, which is described in further detail below. As mentioned herein, Layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in further detail below. As mentioned herein, Layer 1 may include a Physical (PHY) layer of the UE / RAN node, which is described in further detail below.

[0139] Figure 15 1 shows an exemplary interface of a baseband circuit according to some aspects. As discussed above, Figure 14 The baseband circuit 1404 may include processors 1404A to 1404E and a memory 1404G utilized by the processors. Each of the processors 1404A to 1404E may include a memory interface 1504A to 1504E, respectively, for sending / receiving data to / from the memory 1404G.

[0140] The baseband circuit 1404 may also 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); an application circuit interface 1514 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1404); Figure 14 RF circuit interface 316 (for example, for sending / receiving data to / from the application circuit 1402); Figure 14 an interface for sending / receiving data to / from a RF circuit 1406); a wireless hardware connection interface 1518 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 1520 (eg, an interface for sending / receiving power or control signals to / from the PMC 1412).

[0141] As discussed in greater detail herein, various aspects that can be employed, for example, at a UE can facilitate power management associated with a wireless modem. Various aspects can employ the power management techniques discussed herein, wherein, based on monitored power consumption and temperature levels, one or more power management phases discussed herein can be employed to mitigate overheating. 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 also Figure 16 , a block diagram of a system 1600 is shown that can be employed at a UE (user equipment), a next-generation Node B (gNodeB or gNB), or other BS (base station) / TRP (transmit / receive point), or another component of a 3GPP (3rd Generation Partnership Project) network (e.g., a 5GC (fifth generation core network) component or function, such as a UPF (user plane function)) in accordance with various aspects discussed herein to facilitate power management associated with a wireless modem. System 1600 may include a processor 1610, communication circuitry 1620, and memory 1630. Processor 1610 (e.g., the processor may include one or more of processors 1402 and / or 1404A through 1404F, etc.) may include processing circuitry and associated interfaces (e.g., a communication interface (e.g., RF circuit interface 1516) for communicating with communication circuitry 1620, a memory interface (e.g., memory interface 1512) for communicating with memory 1630, etc.). The communication circuit 1620 may include, for example, circuits for wired and / or wireless connections (e.g., 1406 and / or 1408), which may include transmitter circuits (e.g., associated with one or more transmit chains) and / or receiver circuits (e.g., associated with one or more receive chains), wherein the transmitter circuits and the receiver circuits may employ common and / or different circuit elements, or a combination 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 various storage media (e.g., volatile and / or non-volatile according to any of various technologies / configurations, etc.), and may store instructions and / or data associated with one or more of the processor 1610 or the communication circuit 1620.

[0143] Specific types of aspects of the system 1600 (eg, UE aspects) may be indicated via subscripts (eg, system 1600 UE Including processor 1610 UE 、Communication circuit 1620 UE and memory 1630UE In some aspects, such as BS aspects (eg, system 1600 gNB ) and network components (eg, UPF (User Plane Function), etc.) aspects (eg, system 1600 UPF ), processor 1610 gNB (etc.), communication circuits (e.g., 1620 gNB etc.) and memory (e.g., 1630 gNB 16001 and 16002) can be included in a single device or in different devices, such as part of a distributed architecture. In one aspect, signaling or messaging between different aspects of system 1600 (e.g., 16001 and 16002) can be generated by processor 16101, transmitted by communication circuitry 16201 over an appropriate 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) can participate in the communication. Baseband circuitry 1404 can also include one or more interfaces to communicatively couple to other circuits / devices, such as communication circuitry 1620.

[0144] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc. may be received from a gNB or other access point (e.g., via a processor 1610) via signaling (e.g., associated with one or more layers, such as L1 signaling or higher layer signaling (e.g., MAC, RRC, etc.)). gNB Generated by the communication circuit 1620 gNB Transmission, by communication circuit 1620 UE Received and processed by processor 1610 UE The UE is configured with information / features / parameters / etc., generated or processed by the UE. The type of signaling employed and / or the exact details of the operations performed at the UE and / or gNB in ​​the process (e.g., signaling structure, processing of PDUs / SDUs, etc.) may vary depending on the type of information, features, parameters, etc. However, for convenience, such operations may be referred to herein as configuring the UE with information / features / parameters / etc., generating or processing configuration signaling, or by similar terminology.

[0145] Additional Examples

[0146] Embodiments herein may include subject matter such as a method, components for performing the actions or blocks of the method, and at least one machine-readable medium comprising 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 the actions of the method or apparatus or system for concurrent communication using multiple communication technologies according to the described aspects and examples.

[0147] Embodiment 1 is a baseband processor comprising: a memory interface; and a processing circuit, the processing circuit being communicatively coupled to the memory interface and configured to perform the following operations, the operations comprising: 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 a random access channel (RACH) configuration for the RRC inactive data transmission; generating a message 3 (Msg3) or MsgA physical uplink shared channel (PUSCH) including uplink (UL) data via configured resources; and receiving a message 4 (Msg4) or message B (MsgB) in response to the Msg3 or the MsgA PUSCH.

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

[0149] Embodiment 3 includes the subject matter of any variation of any one of Embodiment 1, wherein the operations further comprise selecting the preamble from a dedicated preamble group for the RRC inactive data transmission.

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

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

[0152] Embodiment 6 includes the subject matter of any variation of any one of embodiments 1 to 5, wherein a repetition value is assigned to the Msg3 or MsgA PUSCH, the repetition value being determined by the processing circuit 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 generates one or more repetitions of the Msg3 or MsgA PUSCH based at least in part on the repetition value; and wherein the operation further comprises: after a final repetition of the one or more repetitions, starting one of a random access response (RAR) window associated with the MsgB or a contention resolution (CR) timer associated with the Msg4.

[0153] Embodiment 7 includes the subject matter of any variation of any one of embodiments 1 to 6, wherein the Msg3 or MsgA PUSCH includes a medium access control element (MAC CE), the MAC CE including an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the operation further includes scrambling the Msg3 or MsgA PUSCH based on the I-RNTI / truncated I-RNTI.

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

[0155] Embodiment 9 includes the subject matter of any variation of any one of Embodiments 7, wherein the operation includes generating Msg3, and wherein the operation further includes: starting a contention resolution (CR) timer after transmitting the Msg3, the CR timer being set to end at a CR duration limit; and receiving the Msg4 before the CR duration limit; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) allocation scrambled by the I-RNTI / truncated I-RNTI, or the Msg4 includes a downlink (DL) allocation for scheduling the baseband processor based at least on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation for scheduling the baseband processor based at least on the TC-RNTI includes the MAC CE including the I-RNTI.

[0156] Embodiment 10 is a user equipment (UE) device, comprising: a communication circuit; and a processor, the processor being configured to perform operations, the operations comprising: in response to determining to perform radio resource control (RRC) inactive data transmission: transmitting a message 1 (Msg1) or a 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 a MsgA physical uplink shared channel (PUSCH) including uplink (UL) data via the communication circuit via configured resources; and receiving a message 4 (Msg4) or a message B (MsgB) via the communication circuit in response to the Msg3 or the MsgA PUSCH.

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

[0158] Embodiment 12 includes the subject matter of any variation of any one of Embodiment 10, wherein the operations further comprise selecting the preamble from a dedicated preamble group for the RRC inactive data transmission.

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

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

[0161] Embodiment 15 includes the subject matter of any variation of any one of Embodiments 10 to 15, wherein a repetition value is assigned to the Msg3 or MsgA PUSCH, the repetition value being determined by the 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 repetitions of the Msg3 or MsgA PUSCH based at least in part on the repetition value; and after a final repetition of the one or more repetitions, the operation further comprises starting one of an RAR window associated with the MsgB or a contention resolution (CR) timer associated with the Msg4.

[0162] Embodiment 16 includes the subject matter of any variation of any one of Embodiments 10 to 13, wherein the Msg3 or MsgA PUSCH includes a medium access control element (MAC CE), the MAC CE including an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI), or the operation further includes scrambling the Msg3 or MsgA PUSCH based on the I-RNTI / truncated I-RNTI.

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

[0164] Embodiment 18 includes the subject matter of any variation of any one of Embodiments 16, wherein the operation includes transmitting Msg3, and wherein the operation further includes: starting a contention resolution (CR) timer after transmitting the Msg3, the CR timer being set to end at a CR duration limit; and receiving the Msg4 before the CR duration limit; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) allocation scrambled by the I-RNTI / truncated I-RNTI, or the Msg4 includes a downlink (DL) allocation for scheduling the UE device based at least on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation for scheduling the UE device based at least on the TC-RNTI includes the MACCE including the I-RNTI.

[0165] Embodiment 19 is a baseband processor comprising: a memory interface; and a processing circuit communicatively coupled to the memory interface and configured to perform operations including: suspending a random access channel (RACH) process for radio resource control (RRC) inactive data transmission; and generating an RRC resume request.

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

[0167] Embodiment 21 includes the subject matter of any variation of any one of Embodiments 19 to 20, wherein the operations further comprise: wherein the operations further comprise generating a RACH preamble for the RRC inactive data transmission N times, wherein N is one of a configured threshold or a predefined threshold, wherein in response to generating the RACH preamble for the RRC inactive data transmission N times, suspending the RACH process for the RRC inactive data transmission.

[0168] Embodiment 22 includes the subject matter of any variation of any one of Embodiments 19 to 21, wherein the operations further comprise determining whether a radio link quality satisfies a threshold for generating a RACH preamble for the RRC inactive data transmission, and wherein the RACH procedure is suspended in response to the radio link quality threshold not satisfying the threshold for generating the RACH preamble.

[0169] Embodiment 23 includes the subject matter of any variation of any one of Embodiments 19 to 22, wherein after suspending the RACH procedure, a new RACH procedure associated with an RRC resume request begins, including generating the RRC resume request.

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

[0171] Embodiment 25 is a baseband processor comprising: a memory interface; and a processing circuit communicatively coupled to the memory interface and configured to perform the following operations, the operations comprising: receiving a message 1 (Msg1) or a message A (MsgA) preamble based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receiving a message 3 (Msg3) or a MsgA physical uplink shared channel (PUSCH) comprising uplink (UL) data via configured resources; and generating a message 4 (Msg4) or a message B (MsgB) in response to the Msg3 or the MsgA PUSCH.

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

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

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

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

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

[0177] Embodiment 31 includes the subject matter of any variation of any one of embodiments 25 to 30, wherein the Msg3 or the MsgA PUSCH includes a medium access control element (MAC CE), the MAC CE including an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with the RRC inactive data transmission, or the Msg3 or the MsgA PUSCH is scrambled with the I-RNTI / truncated I-RNTI, and wherein the operation further includes determining the I-RNTI / truncated I-RNTI associated with the RRC inactive data transmission based on one of the following: the MAC CE including the I-RNTI / truncated I-RNTI, or descrambling the Msg3 or MsgA PUSCH with a set of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

[0178] Embodiment 32 includes the subject matter of any variation of any one of Embodiment 31, wherein the operation includes generating the MsgB, and wherein the MsgB includes a random access response (RAR) and the MAC CE includes the I-RNTI / truncated I-RNTI; or the MsgB includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI.

[0179] Embodiment 33 includes the subject matter of any variation of any one of Embodiment 31, wherein the operation comprises generating the Msg4; wherein the Msg4 comprises at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) allocation scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 comprises a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with scheduling based at least in part on the TC-RNTI comprises the MAC CE including the I-RNTI.

[0180] Embodiment 34 is a machine-readable medium comprising instructions that, when executed, cause a base station (BS) to perform the following operations: receive a message 1 (Msg1) or a message A (MsgA) preamble based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receive a message 3 (Msg3) or a MsgA physical uplink shared channel (PUSCH) comprising uplink (UL) data via configured resources; and transmit a message 4 (Msg4) or a message B (MsgB) in response to the Msg3 or the MsgA PUSCH.

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

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

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

[0184] Embodiment 38 includes the subject matter of any variant of any one of embodiments 34 to 37, wherein the instructions, when executed, further cause the BS to perform the following operations: configure the uplink data size for the RRC inactive data transmission based on one or more of a timing advance (TA) or a time alignment command (TAC), and configure a radio link quality threshold for the RRC inactive data transmission, or configure a radio link timing threshold for the RRC inactive data transmission.

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

[0186] Embodiment 40 includes the subject matter of any variation of any one of embodiments 34 to 39, wherein the Msg3 or the MsgA PUSCH includes a medium access control element (MAC CE), the MAC CE including an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with the RRC inactive data transmission, or the Msg3 or the MsgA PUSCH is scrambled with the I-RNTI / truncated I-RNTI, and wherein the instructions, when executed, further cause the BS to determine the I-RNTI / truncated I-RNTI associated with the RRC inactive data transmission based on one of: the MAC CE including the I-RNTI / truncated I-RNTI, or descrambling the Msg3 or MsgA PUSCH with a set of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

[0187] Embodiment 41 includes the subject matter of any variation of any one of Embodiment 40, wherein the instructions, when executed, transmit the MsgB, and wherein the MsgB includes a random access response (RAR) and the MAC CE includes the I-RNTI / truncated I-RNTI; or the MsgB includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI.

[0188] Embodiment 42 includes the subject matter of any variation of any one of Embodiment 40, wherein the instructions, when executed, transmit Msg4; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) allocation scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 includes a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with the scheduling based at least in part on the TC-RNTI includes the MAC CE including the I-RNTI.

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

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

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

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

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

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

[0195] Embodiment 49 includes the subject matter of any variation of any one of embodiments 43 to 48, wherein the Msg3 or the MsgA PUSCH includes a medium access control element (MAC CE), the MAC CE including an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI (I-RNTI / truncated I-RNTI) associated with the RRC inactive data transmission, or the Msg3 or the MsgA PUSCH is scrambled with the I-RNTI / truncated I-RNTI, and wherein the one or more processors are further configured to determine the I-RNTI / truncated I-RNTI associated with the RRC inactive data transmission based on one of: the MAC CE including the I-RNTI / truncated I-RNTI, or descrambling the Msg3 or MsgA PUSCH with a set of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

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

[0197] Embodiment 51 includes the subject matter of any variation of any one of Embodiment 49, wherein the one or more processors transmit the Msg4; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) allocation scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 includes a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with the scheduling based at least in part on the TC-RNTI includes the MAC CE including the I-RNTI.

[0198] Embodiment 52 includes an apparatus comprising means for performing any of the described operations of embodiments 1-24.

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

[0200] Embodiment 54 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the described operations of embodiments 1-24.

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

[0202] Embodiment 56 includes an apparatus comprising means for performing any of the described operations of embodiments 34-51.

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

[0204] Embodiment 58 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the described operations of embodiments 34 to 51.

[0205] Embodiment 59 includes a base station (BS) configured to perform any one of the described operations of embodiments 34 to 51.

[0206] The above description of exemplary aspects of the disclosed subject matter, including that described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific aspects and embodiments are described herein for illustrative purposes, various modifications are contemplated within the scope of such aspects and embodiments, as those skilled in the relevant art will recognize.

[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 alternative functions of the disclosed subject matter without departing from the described aspects. Accordingly, the disclosed subject matter should not be limited to any single aspect described herein, but rather should be construed in accordance with the breadth and scope of the claims appended hereto.

[0208] In particular, with respect to the various functions performed by the aforementioned components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise indicated, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a number of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, as may be desirable and advantageous.

Claims

1. A base station (BS), comprising: Memory interface; and a processing circuit communicatively coupled to the memory interface and configured to perform operations comprising: Repeating values ​​are sent by the communication circuit; receiving a message 1 (Msg1) or message A (MsgA) preamble based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receiving one or more repetitions of a Message 3 (Msg3) or a MsgA Physical Uplink Shared Channel (PUSCH) including uplink (UL) data according to the repetition value; and In response to receiving the Msg3 or the MsgA PUSCH, the communication circuit transmits a message 4 (Msg4) or a message B (MsgB). 2 . The BS according to claim 1 , wherein the RACH configuration is a dedicated RACH configuration for the RRC inactive data transmission. 3 . The BS of claim 1 , wherein the operations further comprise configuring a dedicated preamble group, and the Msg1 or the MsgA preamble is one of the dedicated preamble groups used for the RRC inactive data transmission. 4 . The BS according to claim 1 , wherein the preamble is a shared preamble of the RACH configuration used for the RRC inactive data transmission and the RACH configuration of an RRC recovery procedure.

5. The BS according to any one of claims 1 to 4, wherein the operations further comprise: configuring a radio link timing threshold for the RRC inactive data transmission based on one or more of a timing advance (TA) or a time alignment command (TAC); sending the radio link timing threshold in a RACH message; as well as The Msg3 is received when the radio link timing threshold is met.

6. The BS according to any one of claims 1 to 4, wherein the operations further comprise: A radio link quality threshold is configured to determine the repetition value based on the radio link quality threshold.

7. The BS according to any one of claims 1 to 4, wherein the Msg3 or the MsgA PUSCH is scrambled with an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI, and The operations further include descrambling the Msg3 or MsgA PUSCH using a set of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

8. The BS of claim 7, wherein the operation comprises generating the MsgB, and wherein the MsgB comprises a random access response (RAR) and a medium access control element (MAC CE) including the I-RNTI / truncated I-RNTI; or The MsgB includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI.

9. The BS according to claim 7, wherein the operation comprises generating the Msg4; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 comprises a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with the scheduling based at least in part on the TC-RNTI comprises a medium access control element (MAC CE) including the I-RNTI.

10. A method for causing a base station (BS) to: Sending duplicate values; receiving a message 1 (Msg1) or message A (MsgA) preamble based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receiving, via the configured resources, one or more repetitions of a Message 3 (Msg3) or a MsgA Physical Uplink Shared Channel (PUSCH) including uplink (UL) data according to the repetition value; and Message 4 (Msg4) or message B (MsgB) is transmitted in response to receiving the Msg3 or the MsgA PUSCH.

11. The method of claim 10, wherein the RACH configuration is a dedicated RACH configuration for the RRC inactive data transmission. 12 . The method of claim 10 , wherein the method further causes the BS to configure a dedicated preamble group, and the Msg1 or the MsgA preamble is one of the dedicated preamble groups used for the RRC inactive data transmission.

13. The method of claim 10, wherein the preamble is a shared preamble of the RACH configuration used for the RRC inactive data transmission and the RACH configuration of an RRC recovery procedure.

14. The method according to any one of claims 10 to 13, wherein the method further causes the BS to: configuring a radio link timing threshold for the RRC inactive data transmission based on one or more of a timing advance (TA) or a time alignment command (TAC); sending the radio link timing threshold in a RACH message; as well as The Msg3 is received when the radio link timing threshold is met.

15. The method according to any one of claims 10 to 13, wherein the method further causes the BS to: A radio link quality threshold is configured to determine the repetition value based on the radio link quality threshold.

16. The method according to any one of claims 10 to 13, wherein the Msg3 or the MsgA PUSCH is scrambled with an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI, and The method further causes the BS to descramble the Msg3 or MsgAPUSCH using a group of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

17. The method according to claim 16, wherein the method further causes the BS to transmit the MsgB, and wherein the MsgB includes a random access response (RAR) and a medium access control element (MACCE) including the I-RNTI / truncated I-RNTI; or The MsgB includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI.

18. The method according to claim 16, wherein the method further causes the BS to transmit the Msg4; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 comprises a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with the scheduling based at least in part on the TC-RNTI comprises a medium access control element (MAC CE) including the I-RNTI.

19. A base station (BS) apparatus, comprising: Communication circuits; and one or more processors communicatively coupled to the communication circuitry and configured to: transmitting the repeating value via the communication circuit; receiving a Message 1 (Msg1) or Message A (MsgA) preamble via the communication circuit based on a random access channel (RACH) configuration for radio resource control (RRC) inactive data transmission; receiving, via the communication circuit via the configured resources, one or more repetitions of a Message 3 (Msg3) or a MsgA Physical Uplink Shared Channel (PUSCH) including uplink (UL) data according to the repetition value; and In response to receiving the Msg3 or the MsgA PUSCH, a message 4 (Msg4) or a message B (MsgB) is transmitted via the communication circuit.

20. The apparatus of claim 19, wherein the RACH configuration is a dedicated RACH configuration for the RRC inactive data transmission.

21. The apparatus of claim 19, wherein the one or more processors are further configured to configure a dedicated preamble group, and the Msg1 or the MsgA preamble is one of the dedicated preamble groups used for the RRC inactive data transmission.

22. The apparatus of claim 19, wherein the preamble is a shared preamble of the RACH configuration used for the RRC inactive data transmission and the RACH configuration of an RRC recovery procedure.

23. The apparatus of any one of claims 19 to 22, wherein the one or more processors are further configured to: configuring a radio link timing threshold for the RRC inactive data transmission based on one or more of a timing advance (TA) or a time alignment command (TAC); sending the radio link timing threshold in a RACH message; and The Msg3 is received when the radio link timing threshold is met.

24. The apparatus of any one of claims 19 to 22, wherein the one or more processors are further configured to: A radio link quality threshold is configured to determine the repetition value based on the radio link quality threshold.

25. The apparatus according to any one of claims 19 to 22, wherein the Msg3 or the MsgA PUSCH is scrambled with an inactive radio network temporary identifier (I-RNTI) or a truncated I-RNTI, and The one or more processors are further configured to descramble the Msg3 or MsgA PUSCH with a set of possible I-RNTIs / truncated I-RNTIs including the I-RNTI / truncated I-RNTI.

26. The apparatus of claim 25, wherein the one or more processors transmit the MsgB, and wherein the MsgB comprises a random access response (RAR) and a medium access control element (MAC CE) including the I-RNTI / truncated I-RNTI; or The MsgB includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI.

27. The apparatus of claim 25, wherein the one or more processors transmit the Msg4; wherein the Msg4 includes at least one of an uplink (UL) grant scrambled by the I-RNTI / truncated I-RNTI or a downlink (DL) assignment scrambled by the I-RNTI / truncated I-RNTI, or wherein the Msg4 comprises a DL allocation with scheduling based at least in part on a temporary cell radio network temporary identifier (TC-RNTI), wherein the DL allocation with the scheduling based at least in part on the TC-RNTI comprises a medium access control element (MAC CE) including the I-RNTI.

Images