Apparatus and methods for user equipment direct transmission when inactive

Abstract

Systems, methods, and circuitry are provided for direct transmission of uplink data by an inactive UE using a contention-free random access (CFRA) procedure. In one example, a method includes receiving, from a network, a configuration of dedicated physical random access channel (PRACH) resources or dedicated preamble resources (dedicated PRACH / preamble resources); and while in a radio resource control (RRC) inactive state, transmitting, to a base station, uplink data using the dedicated PRACH / preamble resources using a contention-free random access (CFRA) procedure without entering an RRC connected state.

Description

BACKGROUND

[0001] A random access channel (RACH) procedure is used by a user equipment (UE) to establish synchronization with a base station and obtain a network identifier and resources for transmission of uplink data. BRIEF DESCRIPTION OF DRAWINGS

[0002] Some examples of circuits, apparatuses, and / or methods will hereinafter be described merely by way of example in the context of the accompanying drawings.

[0003] Figure 1 is a state diagram of UE radio resource control (RRC) states.

[0004] Figure 2 is a flow diagram of an exemplary RRC resume procedure.

[0005] Figure 3A is a flow diagram of an exemplary four-step RACH procedure employed by a UE to perform the RRC resume procedure of FIG. 4.

[0006] Figure 3B is a flow diagram of an exemplary two-step RACH procedure employed by a UE to perform the RRC resume procedure of FIG. 4.

[0007] Figure 4A is a flow diagram illustrating a delay between data arrival at a UE in an inactive state and data transmission by the UE after transitioning to a connected state.

[0008] Figure 4B is a flow diagram illustrating a reduced latency between data arrival at a UE in an inactive state and data transmission by the UE remaining in an inactive state.

[0009] Figure 5A and Figure 5B is a flow diagram illustrating direct uplink transmission by an inactive UE via a contention free random access (CFRA) procedure in accordance with various disclosed aspects.

[0010] Figure 6 is a flow diagram illustrating direct uplink transmission by an inactive UE via a CFRA procedure using a resource validity indication in accordance with various disclosed aspects.

[0011] Figure 7 is a flow diagram illustrating direct uplink transmission by an inactive UE with various cells in a network in accordance with various disclosed aspects.

[0012] Figure 8 is a flow diagram illustrating direct uplink transmission by an inactive UE via a CFRA procedure using a timer in accordance with various disclosed aspects.

[0013] Figure 9A and Figure 9B This is a flowchart illustrating a direct uplink transmission by an inactive UE via a four-step CFRA, according to the disclosed aspects.

[0014] Figure 10A and Figure 10B This is a flowchart illustrating a direct uplink transmission by an inactive UE via a two-step CFRA, according to the disclosed aspects.

[0015] Figure 11 This is a flowchart illustrating an exemplary method for performing direct uplink transmission by an inactive UE via CFRA, according to the disclosed aspects.

[0016] Figure 12 An exemplary communication network is shown according to the disclosed aspects.

[0017] Figure 13 Examples of infrastructure equipment (e.g., BS, eNB, gNB) are shown according to the disclosed aspects.

[0018] Figure 14 Examples of user equipment (e.g., UE) based on the disclosed aspects are shown. Detailed Implementation

[0019] This disclosure is described with reference to the accompanying drawings. The drawings are not drawn to scale and are provided for illustrative purposes only. Several aspects of this disclosure are described below with reference to exemplary applications for illustration. Numerous specific details, relationships, and methods are set forth to provide an understanding of this disclosure. This disclosure is not limited to the order of the illustrated actions or events, as some actions may occur in a different order and / or simultaneously with other actions or events. Furthermore, not all illustrated actions or events are necessary to implement the method chosen according to this disclosure.

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

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

[0022] In 5G, an inactive state is introduced to provide an intermediate state between idle and connected states. This intermediate state accelerates the reconnection process by eliminating some of the signaling required for transitioning from idle to connected states. The inactive state is beneficial for UEs that do not communicate with the RAN frequently and achieves power savings compared to these UEs maintaining a connected state. To enter the inactive state, the UE performs an RRC suspend procedure 140, where the UE context is stored by both the UE and the serving gNB, followed by an RRC release procedure. While in the inactive state, the UE still has a non-access stratum (NAS) connection to the CN (i.e., it remains in a connection management (CM) connected state, as opposed to an idle state where the UE is not in a CM connected state).

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

[0024] To transition from an inactive state to a connected 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 transitioning from an idle state to a connected state, the RRC recovery procedure accelerates the transition to the connected state by allowing the restoration of the previous connection without having to perform a large amount of NAS signaling.

[0025] Figure 2 The exemplary RRC recovery procedure 250 is outlined below. The UE is initially in an inactive state. At 210, the UE uses the RACH procedure to transmit an RRC recovery request to the gNB residing on it. The RRC recovery request includes an Inactive Radio Network Temporary Identifier (I-RNTI) for the UE, which is assigned to the UE by the network when the UE enters an inactive state. The network uses the I-RNTI provided with the recovery request to identify the UE and the last serving cell, enabling the new serving cell to obtain the UE context from the last serving cell.

[0026] When a UE wishes to communicate with the network but does not have allocated UL resources, it uses the RACH procedure to contact the network. Therefore, the UE uses the RACH procedure to transmit a recovery request to the network. There are two types of RACH procedures: contention-based RACH (CBRA) and contention-free RACH (CFRA). In CBRA, the UE randomly selects a preamble to identify itself in the initial message with the network. In CFRA, when the UE enters a state where it does not have allocated UL resources, the network assigns a preamble to the UE. CFRA will be discussed in more detail in the context of an inactive UE performing a direct transmission using CFRA.

[0027] exist Figure 3A and Figure 3BThe diagram illustrates in more detail two types of contention-based RACH (CBRA) procedures 310 and 360, which can be used to transmit RRC recovery requests. Although the RACH procedure is described here in the context of transmitting recovery requests, the RACH procedure is used by the UE at any time when the UE expects to achieve uplink synchronization with the gNB, enter a connected state from an idle or inactive state, or obtain resources for uplink transmission while in a connected state.

[0028] Figure 3A A four-step contention-based RACH (CBRA) procedure is illustrated. At 320, the UE transmits Msg1, including a preamble identifying the UE, using a predetermined PRACH timing. In CBRA, the preamble is randomly selected by the UE from a set of possible preambles. In another type of RACH procedure, when the UE enters an inactive or idle state, a contention-free RACH (CFRA), a preamble, and optionally dedicated PRACH resources are allocated to the UE. Because in CBRA, another UE can select the same preamble via the same PRACH resources, CBRA includes a contention resolution step 350 as described below. In addition to the preamble, the UE also indicates a response window during which the UE expects a response from the gNB. If the UE does not receive a response within the window, the UE will retransmit the preamble and / or take other remedial actions.

[0029] At 330, the gNB transmits Msg2 containing a RACH response (RAR), which includes downlink control information (DCI) scrambled based on a preamble transmitted by the UE. The DCI includes information enabling the UE to decode the Physical Downlink Shared Channel (PDSCH), which transmits an identifier for the UE and an allocation of UL resources for the UE's use. At 340, the UE uses the UL resources received in the RAR to transmit Msg3. In this example, Msg3 will include a recovery request. In other examples, Msg3 may include other data.

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

[0031] Figure 3B The two-step CBRA procedure is shown at 360. At 370, the UE transmits MsgA, which includes... Figure 3A The information sent in Msg1 and Msg3 of the 4-step RACH procedure. MsgA includes a randomly selected preamble transmitted on the PRACH resource and an RRC recovery request transmitted using the PUSCH resource. At 380, the gNB transmission may include MsgB of a fallback RAR, which includes an uplink grant for the UE to retransmit MsgA if the gNB detects MsgA but cannot decode it. If the gNB successfully decodes MsgA, MsgB includes a success RAR, which may include a new UL / DL grant for subsequent communication of data (not a retransmission of the RRC recovery request). At this point, the UE has successfully notified the gNB of its intention to enter the connected state (e.g., Figure 2 Step 210 is completed. In CFRA, at 360, a pre-assigned preamble and a dedicated PRACH resource (assigned by gNB) can be used.

[0032] Return to Figure 2 The RRC recovery process outlined in the table is as follows: At 220, after receiving the recovery request from the gNB, the gNB requests the UE context information, which is stored by the last serving gNB as part of the RRC suspension procedure. At 230, the last serving gNB provides the UE context information to the new serving gNB. At 240, the gNB transmits an RRC recovery message to the UE to indicate that the UE can enter the connected state. At 260, the UE indicates to the gNB that it has successfully entered the connected state. At 270, the gNB transmits a path handover request to the Access and Mobility Management Function (AMF), the interface between the gNB and the CN, to update the radio bearer for the UE. At 280, the AMF responds to the gNB, confirming the path handover is complete. At 290, the gNB notifies the last serving gNB that the UE context can be deleted. After these communications have occurred, the UE can transmit and receive data from the gNB.

[0033] Reference Figure 4A It can be seen that the recovery process introduces a significant delay between when the UE has data to transmit and when the UE is able to transmit data. This paper discloses systems, circuits, and techniques for enabling a UE to perform direct data transmission to a gNB using CFRA while inactive without transitioning to a connected state, such as... Figure 4B As shown.

[0034] In CFRA, the network can identify a UE via dedicated Physical Random Access Channel (PRACH) resources (e.g., resources that can be used to transmit RACH messages or data) and / or dedicated preamble resources (e.g., preambles assigned to the UE for transmission using preamble resources). These dedicated PRACH resources and / or dedicated preamble resources are referred to herein as "dedicated PRACH / preamble resources," which are configured to the UE by the network. The dedicated PRACH / preamble configuration is given to the UE via RRC or Physical Downlink Control Channel (PDCCH) commands and is valid within the serving cell. CFRA is triggered by the following events: uplink synchronization, downlink data arrival, handover, and beam fault recovery. This paper proposes an extension to CFRA where dedicated PRACH / preamble resources are used to identify inactive UEs, enabling them to transmit uplink data. The UE uses dedicated PRACH / preamble resources to establish the CFRA procedure, where the UE performs direct uplink transmissions while inactive.

[0035] Figure 5A and Figure 5B This diagram illustrates a network in which a UE roams within a Radio Access Network (RAN) comprising five cells. The UE accesses the core network via one or more cells of the RAN. For the purposes of this specification, "cell" means a collection of infrastructure equipment (such as base stations, eNBs, gNBs, etc.) serving a given geographic area. When a UE is in a connected or inactive state, it selects and camps on at least one cell (e.g., a serving cell). When the UE exchanges messages or data with a base station or gNB, it should be understood that these terms are abbreviations for any infrastructure equipment constituting the serving cell for the UE. The RAN includes a RAN notification area containing cells 1 through 4. A UE can roam within the RAN notification area without notifying the RAN, as cells 1 through 4 are for any UE with a serving cell within the RAN notification area that broadcasts paging messages. The RAN also includes a CFRA configuration area, which includes cells that support direct uplink transmissions by inactive UEs using CFRA.

[0036] The network (using serving cell 1) assigns dedicated PRACH / preamble resources to the UE as part of the RRC suspension procedure. When inactive, the UE identifies uplink data to be transmitted to the network. If cell 1 is still the serving cell for the UE, the UE can use the dedicated PRACH / preamble resources received during the RRC suspension procedure to perform CFRA to transmit uplink data to the network using cell 1.

[0037] However, if the UE has performed a cell reselection and is now camped on cell 3 (which is within the CFRA configuration area), a question arises regarding how the new serving cell allocates dedicated PRACH / preamble resources to the UE for direct uplink transmission. In one example, such as... Figure 5A As shown, each cell broadcast in the CFRA configuration area indicates that the cell supports messages for direct uplink transmission by inactive UEs. In this example, the UE can assume that it can use the dedicated PRACH / preamble resources received during RRC suspension to transmit uplink data to any cell transmitting messages using CFRA.

[0038] For example, such as Figure 5B As shown, the broadcast message includes which "supported" PRACH / preamble resources are configured for the cell. In this example, the UE can assume that it can use the dedicated PRACH / preamble resources received during RRC suspension to transmit uplink data only to cells that broadcast messages where the supported PRACH / preamble resources match the dedicated PRACH / preamble resources (using CFRA). In another example, not shown, the broadcast message includes which "supported" PRACH / preamble resources are configured for direct transmissions by an inactive UE to the cell. In this example, the UE can assume that it can use the dedicated PRACH / preamble resources received during RRC suspension to transmit uplink data only to cells that broadcast messages where the supported PRACH / preamble resources match the dedicated PRACH / preamble resources (using CFRA).

[0039] For example, during the RRC hangup process, the network configures dedicated preamble resources to the UE, and the UE obtains dedicated PRACH / preamble resources from broadcast messages broadcast by each cell in which the UE is camped. The UE can use the dedicated preamble to perform direct uplink transmissions (using CFRA) using any PRACH resources configured by the broadcast message of a given camped cell. Alternatively, the UE can use the dedicated preamble to perform direct uplink transmissions (using CFRA) with any camped cell that broadcasts a message indicating that the cell supports direct uplink transmissions using dedicated PRACH / preamble resources. Alternatively, the UE can use the dedicated preamble to perform direct uplink transmissions (using CFRA) with any camped cell that broadcasts a message indicating that the cell supports direct uplink transmissions.

[0040] Figure 6A message flow 610 is shown outlining an example of a direct uplink transmission using CFRA. At 620, the network (e.g., cell 1) utilizes dedicated PRACH / preamble resources to configure a UE entering an inactive state. When in an inactive state, the UE performs a direct uplink transmission using CFRA and dedicated PRACH / preamble resources. At 630, the UE transmits MsgA of a two-step RACH procedure to the cell using dedicated PRACH / preamble resources. MsgA includes uplink data. In response, at 640, the cell transmits MsgB of a two-step RACH procedure including a CFRA resource validity indication value. When the CFRA resource validity indication value is 1, the dedicated PRACH / preamble resources remain valid for future direct uplink transmissions using CFRA. If the CFRA resource validity indication value is 0, the dedicated PRACH / preamble resources are invalid for future direct uplink transmissions using CFRA. In one example, an L2 control packet data unit (PDU) (e.g., a Media Access Control (MAC) control element (CE)) is used to transmit CFRA resource validity indication values. As another example, the cell provides dedicated PRACH / preamble resources via an L2 control PDU (e.g., a MAC CE) for next direct uplink transmissions using CFRA.

[0041] Figure 7 This is an overview of where the UE can be configured to... Figure 5A and Figure 5B This is a flowchart illustrating an example of uplink data transmission patterns between different cells in a network. Note that even though cell 2 is in the CFRA configuration area, cell 2 does not support direct uplink transmissions using CFRA for the UE. During the RRC hang-up procedure, the UE receives a configured dedicated PRACH / preamble resource from cell 1 and enters an inactive state. While in the inactive state, the UE can perform direct uplink transmissions using CFRA with both cell 1 (the serving cell with the configured dedicated PRACH / preamble resource) and cell 3 (which is in the CFRA configuration area). The UE can also perform direct uplink transmissions using contention-based random access (CBRA) with cell 2 (which does not support direct uplink transmissions using CFRA for the UE) and cell 4 (which is in the RAN notification area). To transmit uplink data to cell 5, which is outside the RAN notification area, the UE triggers an RRC recovery procedure to enter a connected state and transmits uplink data upon connection. Alternatively, in some examples, the UE can perform direct uplink transmissions with cell 5 (outside the RAN notification area) using CBRA.

[0042] Figure 8This is a flowchart outlining an exemplary use of a timer to limit the validity of dedicated PRACH / preamble resources. During an RRC suspension procedure, the UE receives dedicated PRACH / preamble resources and a time limit value. At this time, the UE starts a timer. When the UE performs a direct uplink transmission using CFRA, the UE suspends the timer and restarts it after the uplink transmission is complete. The dedicated PRACH / preamble resources are suspended or deleted by the UE when the timer expires (e.g., when the timer value reaches the time limit) or when entering a connected state.

[0043] Figure 9A A flowchart outlining the four-step CFRA procedure 900 is shown, which can be used by the UE for direct uplink transmission when inactive. At 910, the UE transmits a dedicated preamble in Msg1 and begins the RAR window. At 920, the network (e.g., the cell or base station) transmits Msg2 (RAR) within the RAR window, which includes uplink grants, signifying a successful CFRA procedure. At 930, the UE transmits uplink data based on the uplink grants in Msg2 while still inactive. The network may provide a validity timer or CFRA resource validity indication value in Msg2.

[0044] Figure 9B A flowchart outlining a four-step process 940 is shown, which can be used by a UE for direct uplink transmission when inactive. At 910, the UE transmits a dedicated preamble to the network (e.g., a cell or base station). At 950, the network transmits a dedicated physical downlink control channel (PDCCH) schedule, which is scrambled using the inactive radio network temporary identifier (I-RNTI) assigned to the UE when it enters an inactive state. The dedicated PDCCH schedule tracks the PUSCH transmission of the area code (TAC) MAC CE. At 960, while still inactive, the UE transmits uplink data via the TAC MAC CE according to the dedicated PDCCH schedule.

[0045] Figure 10AA flowchart outlining a two-step CFRA procedure 1000 is shown, which can be used by a UE for direct uplink transmission during inactivity. At 1010, the UE transmits a dedicated preamble and uplink data in the MsgA-PUSCH resource and begins the MsgB window. At 1020, the network (e.g., the cell or base station) transmits the MsgB, which includes the uplink grant within the MsgB window, meaning the network cannot decode this uplink transmission. At 1030, the UE transmits uplink data based on the uplink grant in the MsgB while still inactive. If the UE receives a new uplink grant instead of the MsgB, the UE is notified that the uplink transmission was successful and that subsequent data can be transmitted using the new uplink grant. The network may provide a validity timer or CFRA resource validity indication value in the MsgB.

[0046] Figure 10B A flowchart outlining the two-step process 1040 is shown, which can be used by the UE for direct uplink transmission during inactivity. At 1010, the UE transmits a dedicated preamble and uplink data in the PUSCH resource. At 1050, when the UE enters an inactive state, network transmission uses a dedicated PDCCH schedule scrambled with the I-RNTI assigned to the UE. The dedicated PDCCH schedule is the PUSCH transmission of the tracking area code TAC MAC CE performed by the UE transmitting uplink data. At 1060, while still inactive, the UE transmits uplink data via TAC MAC CE according to the dedicated PDCCH schedule.

[0047] The following are several flowcharts outlining example methods. In this specification and the appended claims, the term "determine" is used broadly when describing method steps or functions, referring to entities (e.g., parameters, variables, etc.). For example, "determine" is interpreted to cover, for example, communication that receives and parses an encoded entity or the value of an entity. "Determine" should be interpreted to cover accessing and reading storage entities or memory (e.g., lookup tables, registers, device memory, remote memory, etc.) for the values ​​of entities. "Determine" should be interpreted to cover calculating or deriving the value of an entity or entity based on other quantities or entities. "Determine" should be interpreted to cover any manner in which an entity or the value of an entity is inferred or identified.

[0048] As used herein, when referring to an entity or value of an entity, the term "identify" will be interpreted broadly to cover any manner in which an entity or value of an entity is determined. For example, the term "identify" is interpreted to cover, for example, communication that receives and parses encoded entities or values ​​of entities. The term "identify" should be interpreted to cover accessing and reading storage entities or memory used for the values ​​of entities (e.g., device queues, lookup tables, registers, device memory, remote memory, etc.).

[0049] As used herein, when referring to an entity or value of an entity, the term "selection" will be broadly interpreted to encompass any manner of determining an entity or entity value from a plurality of or a series of possible selections. For example, the term "selection" is interpreted to encompass accessing and reading storage entities or memory used for entity values ​​(e.g., lookup tables, registers, device memory, remote memory, etc.) and returning an entity or entity value from those stored. The term "selection" is interpreted to apply one or more constraints or rules to a set of input parameters to determine an appropriate entity or entity value. The term "selection" is interpreted broadly to encompass any manner of selecting an entity based on one or more parameters or conditions.

[0050] As used herein, the term "derive" is interpreted broadly when used with reference to an entity or the value of an entity. "Derivation" should be interpreted to encompass accessing and reading memory (e.g., lookup tables, registers, device memory, remote memory, etc.) that stores some initial or underlying values, and performing processing and / or logical / mathematical operations on one or more values ​​to generate a derived entity or value for that entity. "Derivation" should be interpreted to encompass calculating or measuring the value of an entity or entity based on other quantities or entities. "Derivation" should be interpreted to encompass any manner in which an entity or the value of an entity is inferred or identified.

[0051] Figure 11 A flowchart outlining method 1100 to be performed by the UE is shown. The method includes: at 1110, receiving dedicated PRACH / preamble resources from the network. At 1120, the method includes: when in an inactive state, without entering a connected state, using CFRA to transmit uplink data using the dedicated PRACH / preamble resources.

[0052] Figure 12 An exemplary architecture of a communication network system 1200 is illustrated according to various aspects. The following description is provided for an exemplary system 1200 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary aspects are not limited in this respect, and the aspects described can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 702.16 protocols (e.g., WLAN, WiMAX, etc.), etc.

[0053] like Figure 12As shown, system 1200 includes UE 1201a and UE 1201b (collectively referred to as "UE 1201"). In this example, multiple UEs 1201 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine electronic control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0054] In some aspects, any of UEs in UE 1201 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0055] UE 1201 can be configured to connect to RAN 1210, for example, for communication coupling. In this context, RAN 1210 can be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 1210 operating in an NR or 5G system 1200, while the term "E-UTRAN," etc., can refer to RAN 1210 operating in an LTE or 4G system 1200. UE 1201 utilizes connections (or channels) 1203 and 1204, each connection including a physical communication interface or layer (discussed in further detail below).

[0056] In this example, connections 1203 and 1204 are shown as air interfaces for communication coupling and are compatible with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, 5G, NR, and / or any other communication protocols discussed herein. In this aspect, UE 1201 can directly exchange communication data via ProSe interface 1205. ProSe interface 1205 may also be referred to as SL interface 1205 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0057] UE 1201b is shown configured to access AP 1206 (also referred to as "WLAN Node 1206", "WLAN 1206", "WLAN Terminal 1206", "WT 1206", etc.) via connection 1207. Connection 1207 may include a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, where AP 1206 will include Wireless Fibre. Router. In this example, AP 1206 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various aspects, UE 1201b, RAN 1210, and AP 1206 can be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1201b in the RRC_CONNECTED state, configured by RAN nodes 1211a-b to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 1201b using WLAN radio resources (e.g., connection 1207) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 1207. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0058] RAN 1210 includes one or more AN nodes or RAN nodes 1211a and 1211b (collectively referred to as "RAN node 1211") that enable connectivity between 1203 and 1204. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 1211 (e.g., gNB) operating in NR or 5G system 1200, while the terms "E-UT RAN node," etc., can refer to RAN node 1211 (e.g., eNB) operating in LTE or 4G system 1200. Depending on the specifics, RAN node 1211 can be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0059] Depending on the specifics, UE 1201 and RAN node 1211 transmit data (e.g., transmit and receive data) via licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0060] To operate in unlicensed spectrum, UE 1201 and RAN node 1211 may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 1201 and RAN node 1211 may perform one or more known medium sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0061] LBT is a mechanism that equipment (e.g., UE 1201, RAN node 1211, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when that medium is sensed to be idle (or when a specific channel in that medium is sensed to be unoccupied). Medium sensing operations may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0062] Typically, existing systems in the 5GHz band are WLANs based on IEEE 702.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1201, AP 1206, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between the X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 8 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0063] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0064] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides the PCC for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require UE 1201 to undergo handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0065] The PDSCH carries user data and higher-layer signaling to UE 1201. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 1201 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1201b within the cell) can be performed at any of the RAN nodes 1211 based on channel quality information fed back from any of the UEs 1201. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UE 1201.

[0066] RAN 1210 is shown as communication-coupled to the core network—in this aspect, communication-coupled to the core network (CN) 1220. CN 1220 may include multiple network elements 1222 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 1201) connected to CN 1220 via RAN 1210. Components of CN 1220 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some aspects, NFV can be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1220 may be referred to as a network slice, and a logical instance of a portion of CN 1220 may be referred to as a network subslice. NFV architectures and infrastructure can be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally implemented by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0067] Figure 13 Examples of infrastructure equipment 1300 according to various aspects are shown. Infrastructure equipment 1300 (or "system 1300") may be implemented as a base station, a radio head unit, a RAN node (such as the previously shown and described RAN node 1211 and / or AP 1206), an application server 1230, and / or any other element / device discussed herein. In other examples, system 1300 may be implemented in or by a UE.

[0068] System 1300 includes: application circuitry 1305, baseband circuitry 1310, one or more radio front-end modules (RFEMs) 1315, memory circuitry 1320, power management integrated circuit (PMIC) 1325, power tee circuitry 1330, network controller circuitry 1335, network interface connector 1340, satellite positioning circuitry 1345, and user interface 1350. In some aspects, device 1300 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other aspects, the following components may be included in more than one device. For example, the circuitry may be individually included in more than one device for CRAN, vBBU, or other similar implementations.

[0069] Application circuitry 1305 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low-dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a universal programmable serial interface module, a real-time clock (RTC), a timer / counter (including interval timers and watchdog timers), a general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of application circuitry 1305 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1300. In some specific implementations, the memory / storage element may be an on-chip memory circuit, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0070] The processor of application circuit 1305 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some aspects, application circuit 1305 may include or may be a dedicated processor / controller for operation according to various aspects of this document. As an example, the processor of application circuit 1305 may include one or more processor, Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some aspects, system 1300 may not utilize application circuitry 1305 and may instead include a dedicated processor / controller for processing, for example, IP data received from EPC or 5GC.

[0071] User interface circuitry 1350 may include one or more user interfaces designed to enable a user to interact with system 1300 or peripheral component interfaces, wherein the peripheral component interfaces are designed to enable peripheral components to interact with system 1300. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power interfaces, etc.

[0072] Figure 13 The components shown can communicate with each other using interface circuitry, which may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI Express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0073] Figure 14 Examples of platform 1400 (or “device 1400”) according to various aspects are shown. In these aspects, computer platform 1400 may be adapted to function as UE 1201, application server 1230, and / or any other element / device discussed herein. Platform 1400 may include any combination of the components shown in the examples. Components of platform 1400 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 1400, or may be implemented as components otherwise integrated within the chassis of a larger system. Figure 14 The block diagram is intended to show a high-level view of the components of the computer platform 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific embodiments.

[0074] Application circuitry 1405 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: LDO, interrupt controller, serial interface (such as SPI), I2C or general programmable serial interface module, RTC, timer / counter (including interval timers and watchdog timers), general-purpose I / O, memory card controller (such as SD MMC or similar controllers), USB interface, MIPI interface, and JTAG test access port. The processor (or core) of application circuitry 1405 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1400. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0075] For example, the processor of application circuit 1405 may include a general-purpose or special-purpose processor, such as one purchased from [unclear - possibly a specific brand or manufacturer]. Inc., Cupertino, CA's A-series processors (e.g., the A13 Bionic) or any other such processor. The processor used in application circuit 1405 can also be one or more of the following: Advanced Micro Devices (AMD). Processor or Accelerated Processing Unit (APU); from Inc.'s kernel processor, from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments Open Multimedia ApplicationsPlatform(OMAP) TM Processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some specific implementations, the application circuit 1405 may be part of a system-on-a-chip (SoC), where the application circuit 1405 and other components are formed as a single integrated circuit or a single package.

[0076] The baseband circuit 1410 may be implemented, for example, as a soldered substrate, which includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0077] Platform 1400 may also include interface circuitry (not shown) for connecting external devices to platform 1400. External devices connected to platform 1400 via this interface circuitry include sensor circuitry 1421 and electromechanical components (EMC) 1422, as well as a removable memory device coupled to removable memory circuitry 1423.

[0078] Battery 1430 can power platform 1400, but in some examples, platform 1400 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 1430 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, battery 1430 may be a typical lead-acid automotive battery.

[0079] Although the method has been shown and described above as a series of actions or events, it should be understood that the order of such actions or events shown should not be construed as limiting. For example, some actions may occur in a different order and / or simultaneously with other actions or events besides those shown and / or described herein. Furthermore, not all of the shown actions may be required to implement one or more aspects or embodiments disclosed herein. Additionally, one or more of the actions shown herein may be performed in one or more separate actions and / or stages. In some embodiments, the method shown above can be implemented in a computer-readable medium using instructions stored in memory. Many other embodiments and variations are possible within the scope of this disclosure protected by the claims.

[0080] Example

[0081] Example 1 is an apparatus comprising: one or more processors configured to: receive configuration of a dedicated physical random access channel (PRACH) resource or a dedicated preamble resource (dedicated PRACH / preamble resource) from a network; and, when in a radio resource control (RRC) inactive state, to use a contention-free random access (CFRA) procedure to transmit uplink data to a base station using the dedicated PRACH / preamble resource without entering an RRC connected state.

[0082] Example 2 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to receive dedicated PRACH / preamble resources from the network during an RRC suspension process.

[0083] Example 3 includes the subject matter according to Example 1, including or omitting optional elements, wherein the one or more processors are configured to: identify a preamble in a dedicated PRACH / preamble resource; transmit the preamble to the base station in Msg1 of the Random Access Control Channel (RACH) procedure; receive an indication of a Physical Uplink Shared Channel (PUSCH) resource in Msg2 of the Random Access Control Channel (RACH) procedure; and transmit uplink data to the base station using the PUSCH resource.

[0084] Example 4 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to transmit a dedicated preamble indicated in a dedicated PRACH / preamble resource and uplink data in a MsgA PUSCH resource associated with the RACH procedure.

[0085] Example 5 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: transmit a dedicated preamble indicated in a dedicated PRACH / preamble resource to a base station; receive a dedicated physical downlink control channel (PDCCH) schedule from the base station; and transmit uplink data on a Tracking Area Code (TAC) Media Access Control (MAC) control element (CE) indicated by the received PDCCH schedule.

[0086] Example 6 includes the subject matter according to Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive a broadcast message from a base station indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE; and suppress transmission of uplink data to the base station when the broadcast message does not indicate that the cell supports direct uplink transmission from an inactive UE.

[0087] Example 7 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive a broadcast message from a base station indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE and identifying supported PRACH / preamble resources; and suppress the transmission of uplink data to the base station using CFRA when the supported PRACH / preamble resources are different from dedicated PRACH / preamble resources.

[0088] Example 8 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive a broadcast message from a base station indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE, and identify the supporting PRACH / preamble resources for direct uplink transmission from the inactive UE; and suppress the transmission of uplink data to the base station using CFRA when the direct uplink transmission using the supported PRACH / preamble resources from the inactive UE differs from the dedicated PRACH / preamble resources.

[0089] Example 9 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive a broadcast message from a base station identifying a dedicated PRACH / preamble resource for the cell on which the UE is camped; and transmit uplink data to the base station using the dedicated PRACH / preamble resource identified in the broadcast message.

[0090] Example 10 includes the subject matter according to Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive a validity indication identifier from a base station, the validity indication identifier indicating whether a dedicated PRACH / preamble resource is valid or invalid; and suppress the transmission of uplink data to the base station when the validity indication identifier indicates that the dedicated PRACH / preamble resource is invalid.

[0091] Example 11 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: determine a contention-free RACH (CFRA) area comprising a set of cells; and suppress the transmission of uplink data to the base station using the CFRA procedure when the base station is not in the set of cells.

[0092] Example 12 includes the subject matter described in Example 11, including or omitting optional elements, wherein the one or more processors are configured to transmit uplink data as part of a contention-based RACH procedure in response to determining that the base station is not in the group of cells.

[0093] Example 13 includes the subject matter according to Example 11, including or omitting optional elements, wherein the one or more processors are configured to: trigger an RRC recovery process in response to determining that the base station is not in the group of cells; enter an RRC connection state; and transmit uplink data while in the RRC connection state.

[0094] Example 14 includes the subject matter described in Example 1, including or omitting optional elements, wherein the one or more processors are configured to: receive dedicated PRACH / preamble resources from the network during an RRC suspension process; start a timer when the RRC suspension process completes; and suppress the transmission of uplink data using the CFRA process after the timer expires.

[0095] Example 15 includes the subject matter described in Example 14, including or omitting optional elements, wherein the one or more processors are configured to: suspend a timer while transmitting uplink data using the CFRA procedure; and restart the timer after transmitting uplink data using the CFRA procedure.

[0096] Example 16 is a method comprising: configuring a user equipment wireless communication device (UE) to receive a dedicated physical random access channel (PRACH) resource or a dedicated preamble resource (dedicated PRACH / preamble resource) from a network; and, when in a radio resource control (RRC) inactive state, using a contention-free random access (CFRA) procedure to transmit uplink data to a base station using the dedicated PRACH / preamble resource without entering an RRC connected state.

[0097] Example 17 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: receiving dedicated PRACH / preamble resources from the network during the RRC suspension process.

[0098] Example 18 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: identifying a preamble in a dedicated PRACH / preamble resource; transmitting the preamble to the base station in Msg1 of the random access control channel (RACH) procedure; receiving an indication of a physical uplink shared channel (PUSCH) resource in Msg2 of the random access control channel (RACH) procedure; and transmitting uplink data to the base station using the PUSCH resource.

[0099] Example 19 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: transmitting a dedicated preamble indicated in a dedicated PRACH / preamble resource and uplink data in a MsgA PUSCH resource associated with the RACH procedure.

[0100] Example 20 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: transmitting a dedicated preamble indicated in a dedicated PRACH / preamble resource to a base station; receiving a dedicated physical downlink control channel (PDCCH) schedule from the base station; and transmitting uplink data on a Tracking Area Code (TAC) Media Access Control (MAC) control element (CE) indicated by the received PDCCH schedule.

[0101] Example 21 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: receiving a broadcast message from a base station indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE; and suppressing the transmission of uplink data to the base station when the broadcast message does not indicate that the cell supports direct uplink transmission from an inactive UE.

[0102] Example 22 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: receiving a broadcast message from a base station that identifies a dedicated PRACH / preamble resource for the cell on which the UE is camped; and transmitting uplink data to the base station using the dedicated PRACH / preamble resource identified in the broadcast message.

[0103] Example 23 includes the subject matter according to Example 16, including or omitting optional elements, and the method further includes: receiving a validity indication identifier from a base station, the validity indication identifier indicating whether a dedicated PRACH / preamble resource is valid or invalid; and suppressing the transmission of uplink data to the base station when the validity indication identifier indicates that the dedicated PRACH / preamble resource is invalid.

[0104] Example 24 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: determining a contention-free RACH (CFRA) area comprising a group of cells; and suppressing the transmission of uplink data to the base station using the CFRA procedure when the base station is not in the group of cells.

[0105] Example 25 includes the subject matter described in Example 16, including or omitting optional elements, and the method further includes: receiving dedicated PRACH / preamble resources from the network during an RRC suspension process; starting a timer when the RRC suspension process completes; suspending the timer when uplink data is transmitted using the CFRA process; restarting the timer after uplink data is transmitted using the CFRA process; and suppressing uplink data transmission using the CFRA process after the timer expires.

[0106] The term "coupled" is used throughout this specification. This term can cover any connection, communication, or signaling path that enables a functional relationship consistent with the description of this disclosure. For example, in a first example, if device A generates a signal to control device B to perform an action, then device A is coupled to device B via intermediate component C. Alternatively, in a second example, if intermediate component C substantially does not alter the functional relationship between device A and device B such that device B is controlled by device A via a control signal generated by the device, then device A is coupled to device B via intermediate component C.

[0107] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. An apparatus for a user equipment (UE), comprising: Memory; and One or more processors, said one or more processors being coupled to the memory and configured to: Configuration of receiving dedicated physical random access channel (PRACH) resources or dedicated preamble resources from the network during the Radio Resource Control (RRC) suspension process; Start the timer when the RRC suspension process is complete; When in an RRC inactive state, without entering an RRC connected state, the contention-free random access CFRA procedure is used to transmit uplink data to the base station using the dedicated PRACH resource or dedicated preamble resource. The timer is suspended during the transmission of the uplink data using the CFRA procedure. The timer is restarted after the uplink data is transmitted using the CFRA procedure. as well as After the timer expires, the uplink data is not transmitted using the CFRA procedure.

2. The apparatus of claim 1, wherein the one or more processors are configured to: Identify the preamble in the dedicated PRACH resource or dedicated preamble resource; The preamble is transmitted to the base station in Msg1 of the Random Access Control Channel (RACH) procedure; In Msg2 of the Random Access Control Channel (RACH) procedure, an indication for Physical Uplink Shared Channel (PUSCH) resources is received; and The uplink data is transmitted to the base station using the PUSCH resource.

3. The apparatus of claim 1, wherein the one or more processors are configured to: The dedicated preamble indicated in the dedicated PRACH resource or dedicated preamble resource, along with the uplink data, is transmitted in the MsgA PUSCH resource associated with the RACH procedure.

4. The apparatus of claim 1, wherein the one or more processors are configured to: Transmit the dedicated preamble indicated in the dedicated PRACH resource or dedicated preamble resource to the base station; Receive dedicated physical downlink control channel (PDCCH) scheduling from the base station; and The uplink data is transmitted on the Tracking Area Code (TAC) Medium Access Control (MAC) Control Element (CE) indicated by the received PDCCH scheduling.

5. The apparatus of claim 1, wherein the one or more processors are configured to: Receive a broadcast message from the base station, the broadcast message indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE; and When the broadcast message does not indicate that the cell supports direct uplink transmission from an inactive UE, the transmission of the uplink data to the base station is suppressed.

6. The apparatus of claim 1, wherein the one or more processors are configured to: The UE receives a broadcast message from the base station, the broadcast message indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE and identifying supported PRACH resources or preamble resources; and When the supported PRACH resource or preamble resource is different from the dedicated PRACH resource or dedicated preamble resource, the uplink data is transmitted to the base station without using CFRA.

7. The apparatus of claim 1, wherein the one or more processors are configured to: The UE receives a broadcast message from the base station, the broadcast message indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE and identifying the supported PRACH resources or preamble resources for direct uplink transmission from an inactive UE; and When the supported PRACH resource or preamble resource is different from the dedicated PRACH resource or dedicated preamble resource, the uplink data is transmitted to the base station without using CFRA.

8. The apparatus of claim 1, wherein the one or more processors are configured to: Receive a broadcast message from the base station, the broadcast message identifying the dedicated PRACH resource or dedicated preamble resource of the cell on which the UE is camped; and This enables the transmission of the uplink data to the base station using the dedicated PRACH resource or dedicated preamble resource identified in the broadcast message.

9. The apparatus of claim 1, wherein the one or more processors are configured to: Receive a validity indication flag from the base station, the validity indication flag indicating whether the dedicated PRACH resource or dedicated preamble resource is valid or invalid; and When the validity indicator flag indicates that the dedicated PRACH resource or dedicated preamble resource is invalid, the uplink data is not transmitted to the base station.

10. A method for wireless communication, comprising: Configuration of receiving dedicated physical random access channel (PRACH) resources or dedicated preamble resources from the network during the Radio Resource Control (RRC) suspension process; Start the timer when the RRC suspension process is complete; When in an RRC inactive state, without entering an RRC connected state, the contention-free random access CFRA procedure is used to transmit uplink data to the base station using the dedicated PRACH resource or dedicated preamble resource. The timer is suspended during the transmission of the uplink data using the CFRA procedure. The timer is restarted after the uplink data is transmitted using the CFRA procedure. as well as After the timer expires, the uplink data is not transmitted using the CFRA procedure.

11. The method of claim 10, further comprising: Identify the preamble in the dedicated PRACH resource or dedicated preamble resource; The preamble is transmitted to the base station in Msg1 of the Random Access Control Channel (RACH) procedure; In Msg2 of the Random Access Control Channel (RACH) procedure, an indication for Physical Uplink Shared Channel (PUSCH) resources is received; and The uplink data is transmitted to the base station using the PUSCH resource.

12. The method of claim 10, further comprising: The dedicated preamble indicated in the dedicated PRACH resource or dedicated preamble resource, along with the uplink data, is transmitted in the MsgA PUSCH resource associated with the RACH procedure.

13. The method of claim 10, further comprising: Transmit the dedicated preamble indicated in the dedicated PRACH resource or dedicated preamble resource to the base station; Receive dedicated physical downlink control channel (PDCCH) scheduling from the base station; as well as The uplink data is transmitted on the Tracking Area Code (TAC) Medium Access Control (MAC) Control Element (CE) indicated by the received PDCCH scheduling.

14. The method of claim 10, further comprising: The UE receives a broadcast message from the base station, the broadcast message indicating whether the cell on which the UE is camped supports direct uplink transmission from an inactive UE; as well as When the broadcast message does not indicate that the cell supports direct uplink transmission from an inactive UE, the transmission of the uplink data to the base station is suppressed.

15. The method of claim 10, further comprising: Receive a broadcast message from the base station, the broadcast message identifying the dedicated PRACH resource or dedicated preamble resource of the cell on which the UE is camped; as well as This enables the transmission of the uplink data to the base station using the dedicated PRACH resource or dedicated preamble resource identified in the broadcast message.

16. The method of claim 10, further comprising: Receive a validity indication flag from the base station, the validity indication flag indicating whether the dedicated PRACH resource or dedicated preamble resource is valid or invalid; as well as When the validity indicator flag indicates that the dedicated PRACH resource or dedicated preamble resource is invalid, the uplink data is not transmitted to the base station.

Images