Cross Reference to Related Applications

[0001] This application claims the benefit of Indian Pat. App. No. 2020 41017610, entitled “RELEASE ASSISTANCE DURING EARLY DATA TRANSMISSION” and filed on April 24, 2020, which is expressly incorporated by reference herein in its entirety.

Technical Field

[0002] The present disclosure relates generally to communication systems, and more particularly in some examples, to using a release assistance indication to end a random access process at a user equipment after early data transmission has been completed and before the time for receiving a conventional release from a base station.

Introduction

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems. These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0005] The technology disclosed herein includes a method of wireless communication during a random access (RA) procedure by a user equipment (UE) of a access network, comprising transmitting both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission. The method further includes monitoring a downlink control channel of the base station upon the transmitting. Additionally, the method further includes from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 comprising an instruction for the UE to end monitoring of the downlink control channel. Additionally, the method further includes ending, in response to receiving the instruction, continuous monitoring of the downlink control channel.

[0006] Another example implementation includes an apparatus for wireless communication during a random access (RA) procedure by a user equipment (UE) of an access network, comprising a memory and a processor in communication with the memory. The processor is configured to transmit both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission. The processor is further configured to monitor a downlink control channel of the base station upon the transmitting. Additionally, the processor further configured to receive, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 comprising an instruction for the UE to end monitoring of the downlink control channel. Additionally, the processor further configured to end, in response to receiving the instruction, continuous monitoring of the downlink control channel.

[0007] Another example implementation includes an apparatus for wireless communication during a random access (RA) procedure by a user equipment (UE) of a access network, comprising means for transmitting both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission. The apparatus further includes means for monitoring a downlink control channel of the base station upon the transmitting. Additionally, the apparatus further includes means for receiving, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel. Additionally, the apparatus further includes means for ending, in response to receiving the instruction, continuous monitoring of the downlink control channel.

[0008] Another example implementation includes a computer-readable medium comprising stored instructions for wireless communication during a random access (RA) procedure by a user equipment (UE) of a access network, executable by a processor to transmit both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission. The instructions are further executable to monitor a downlink control channel of the base station upon the transmitting. Additionally, the instructions are further executable to receive, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel. Additionally, the instructions are further executable to end, in response to receiving the instruction, continuous monitoring of the downlink control channel.

[0009] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0011] FIGs. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a first 5G/NR frame, DL channels within a 5G/NR subframe, a second 5G/NR frame, and UL channels within a 5G/NR subframe, respectively.

[0012] FIG. 3 is a diagram illustrating a base station and user equipment (UE) in an access network, in accordance with examples of the technology disclosed herein.

[0013] FIG. 4 is a diagram illustrating data transfer between a UE, a base station, and a core network for mobile originated (MO) data transfer in wireless communication.

[0014] FIG. 5 is a diagram illustrating data transfer between a UE, a base station, and a core network for mobile originated data (MO) transfer in wireless communication.

[0015] FIG. 6 is a diagram illustrating data transfer between a UE, a base station, and a core network for mobile originated (MO) data transfer in wireless communication, in accordance with examples of the technology disclosed herein.

[0016] FIG. 7 is a flowchart of methods of wireless communication in accordance with examples of the technology disclosed herein.

[0017] FIG. 8 is a block diagram of a UE, in accordance with examples of the technology disclosed herein.

[0018] FIG. 9 is a flowchart of methods of wireless communication in accordance with examples of the technology disclosed herein.

[0019] FIG. 10 is a block diagram of a core network, in accordance with examples of the technology disclosed herein. DETAILED DESCRIPTION

[0020] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0021] Cellular IoT (CIoT) includes a set of 3GPP standards for low power IoT devices as UEs. UEs that are Category M (Cat-M) and Category NarrowBand IoT (NB-IoT) can use the CIoT protocols described in the 3GPP standards. Two types of CIoT are described in the 3GPP standards: Control Plane CIoT (CP-CIoT), and User Plane CIoT (UP-CIoT). CP-CIoT may be applicable to NB-IoTs UEs only; while UP-CIoT may be applicable to both NB-IoT UEs and Cat-M UEs. Both NB-IoT UEs and Cat-M UEs are characterized by low power, low cost, and short and infrequent data transfer (both uplink and downlink) in comparison to UEs such as smartphones. One example application for CIoT is sensor data collection - such as utility meter reading.

[0022] UEs connect to base stations as part of an access networks (described in greater detail below). The initial connection between a UE and the base station includes a random access (RA) procedure at lower levels of the protocol stack characterizing the wireless communication system in accordance with a Radio Resource Control (RRC) protocol to establish an RRC connection. Once an RRC connection is established between the UE, the base station, and a core network that connects UEs (via base stations) to applications such as telephony, video, data, messaging, broadcast, and sensor data collection and processing, then data can be transferred between the UE and these applications.

[0023] Under Early Data Transmission (EDT), short and infrequent data originating from a UE (such as an NB-IoT UE or a Cat-M UE) can be transferred from the UE through the base station and core network to an application (such sensor data collection and processing) as during the RA procedure without completing an RRC connection. EDT can be advantageous because the cost (e.g., in power, bandwidth, and latency) to set up an RRC channel often does not justify the short and infrequent data transfer - especially for NB-IoT UEs and Cat-M UEs. [0024] However, even with EDT, there is a cost to the UE in power, latency, and bandwidth to monitor a downlink control channel (typically continuously) between the UE and the base station during the RA procedure.

[0025] In aspects of the present disclosure, methods, non-transitory computer readable media, and apparatuses are provided to reduce the cost of EDT. In some examples of the technology disclosed herein, during an RA procedure by a UE of a access network, the UE transmits both uplink application data and a release assistance indication (RAI) under EDT in an RA message 3 (MSG3) to a base station of the access network. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission. The UE monitors a downlink control channel of the base station upon the transmitting. The UE then receives, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel. The UE ends, in response to receiving the instruction, continuous monitoring of the downlink control channel.

[0026] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents

[0027] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0028] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer- readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0029] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells. The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., SI interface). The base stations 102 configured for 5G R (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through second backhaul links 186. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first, second and third backhaul links 132, 184 and 134 may be wired or wireless.

[0030] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. In some examples of the technology disclosed herein, both the DL and the UL between the base station and a UE use the same set of multiple beams to transmit/receive physical channels. For example, a given set of beams can carry the multiple copies of a Physical Downlink Shared Channel (PDSCH), described further infra , on the DL and can carry multiple copies of a Physical Uplink Control Channel (PUCCH), also described further infra , on the UL.

[0031] The communication links may be through one or more carriers. The base stations 102 / UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

[0032] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR. The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

[0033] A base station 102, whether a small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band (e.g., 3 GHz - 300 GHz) has extremely high path loss and a short range - making mmW transmissions susceptible to blocking and attenuation resulting in, e.g., unsuccessfully decoded data. The mmW base station 180 may utilize beamforming 182 with the UE 104/184 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

[0034] The base station 180 may transmit a beamformed signal to the UE 104/184 in one or more transmit directions 182'. The UE 104/184 may receive the beamformed signal from the base station 180 in one or more receive directions 182". The UE 104/184 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104/184 may perform beam training to determine the best receive and transmit directions for each of the base station 180 /UE 104/184. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104/184 may or may not be the same.

[0035] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

[0036] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

[0037] The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). In particular, some devices 188, such a utility meters, parking meters, appliances, remote sensors, etc. can be characterized by infrequent and small data packet communications - especially in relation to smart phones. The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. [0038] Continuing to refer to FIG. 1, in certain aspects, the UE 104 (such as UE 188) is configured to transmit during an RA procedure, both uplink application data and a release assistance indication (RAI) under EDT in an RA message 3 (MSG3) to a base station 102 of the access network. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission. The UE 104 monitors a downlink control channel of the base station 102 upon the transmitting. Additionally, the UE 104 receives, from the base station 102, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE 104 to end monitoring of the downlink control channel. The UE 104 ends, in response to receiving the instruction, continuous monitoring of the downlink control channel. The UE 104 can use UE RAI EDT Component 142 for performing this transmitting, monitoring, receiving, and ending.

[0039] In similar aspects, the core network (such as core network 190 or EPC 160) is configured to receive, during an RA procedure of the UE 104 of a access network in communication with the base station 102, both uplink application data of an application executing on the UE 104 and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station 102. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission. The core network, in response to receiving the RAI, directs the base station 102 to instruct the UE 104, prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the access network, to end monitoring of the downlink control channel. The core network can use core network RAI EDT Component 144 for performing the functions described in this paragraph.

[0040] Although the following description may be focused on 5GNR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0041] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G/NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G/NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G/NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G/NR subframe. The 5G/NR frame structure may be FDD in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be TDD in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G/NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and X is flexible for use between DL/UL, and subframe 3 being configured with slot format 34 (with mostly UL). While subframes 3, 4 are shown with slot formats 34, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G/NR frame structure that is TDD.

[0042] Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s- OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC- FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies m 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology m, there are 14 symbols/slot and 2 ^m slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2 ^m * 15 kHz, where m is the numerology 0 to 5. As such, the numerology m=0 has a subcarrier spacing of 15 kHz and the numerology m=5 has a subcarrier spacing of 480 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology m=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps.

[0043] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0044] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R _x for one particular configuration, where lOOx is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS). Some examples of the technology disclosed herein use the DM- RS of the physical downlink control channel (PDCCH) to aid in channel estimation (and eventual demodulation of the user data portions) of the physical downlink shared channel (PDSCH).

[0045] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages. [0046] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0047] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

[0048] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375 The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0049] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M- QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

[0050] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

[0051] The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0052] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0053] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission. [0054] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0055] The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support FLARQ operations.

[0056] Continuing to refer to FIG. 3, and continuing to refer to prior figures for context, in certain aspects, the UE 350 is configured to transmit during an RA procedure, both uplink application data and a release assistance indication (RAI) under EDT in an RA message 3 (MSG3) to a base station 310 of the access network. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission. The UE 350 monitors a downlink control channel of the base station 310 upon the transmitting. Additionally, the UE 350 receives, from the base station 102, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE 350 to end monitoring of the downlink control channel. The UE 350 ends, in response to receiving the instruction, continuous monitoring of the downlink control channel. The UE 350 can use UE RAI EDT Component 142 for performing this transmitting, monitoring, receiving, and ending

[0057] Referring to FIG. 4, and continuing to refer to prior figures for context, a diagram illustrating data transfer between a UE 102, a base station 104, and a core network 190 for mobile originated (MO) data transfer in wireless communication is shown. As described above, UEs 104 connect to base stations 102 as part of an access networks. The initial connection between a UE 104 and the base station 102 includes a random access (RA) procedure at lower levels of the protocol stack characterizing the wireless communication system in accordance with a Radio Resource Control (RRC) protocol to establish an RRC connection. [0058] The RRC protocol includes a series of messages e.g., MSG1 through MSG 7 in FIG. 4. The UE 104 contends with other UEs in transmitting a MSG1 Random Access Preamble to the eNB base station 102 until the base station 102 replies with a MSG2 Random Access Response allocating resources for the UE 104 to specify a MSG3 Radio Resource Control (RRC) Connection Request. After transmitting the MSG3, the UE 104 monitors a downlink control channel from the base station 102. In typical scenarios, this monitoring is continuous. The base station 102 responds to MSG3 with a MSG4 RRC Connection Setup with information for the UE to configure for RRC Connection. The UE confirms that it has configured for the specified RRC connection and begins transmitting application data, e.g., Non-Access Strata (NAS) protocol data units (PDUs) using MSG5 to the base station 102. The base station forwards NAS PDUs to the core network 190 over the RRC connection. The core network 190 (or the EPC 160), as described in connection with FIG. 1, connects the UE 104 to various applications, and can send downlink NAS PDUs from such applications through the base station 102 to the UE 104 using one or more MSG6. Upon completion of the data transfer from/to the UE 104, the RRC connection is released using MSG7 - which allows the UE to end monitoring of the downlink control channel.

[0059] Referring to FIG. 5, and continuing to refer to prior figures for context, a diagram illustrating EDT data transfer between a UE 102, a base station 104, and a core network 190 for mobile originated (MO) data transfer in wireless communication is shown. The RRC protocol under EDT includes a series of messages e.g., MSG1 through MSG 4 in FIG. 5 - each message with similar function as described in connection with FIG. 4. As with non-EDT RA procedure, the UE 104 contends with other UEs in transmitting a MSG1 Random Access Preamble to the eNB base station 102 until the base station 102 replies with a MSG2 Random Access Response allocating resources for the UE 104 to specify a MSG3 Radio Resource Control (RRC) Connection Request.

[0060] In EDT data transfer, MSG3 includes a small amount of application data (typically NAS data). The base station 102 transfers the application data to the core network 190, e.g., so that the core network can transfer the application data to an application server (not shown in FIG. 5). Upon transmitting MSG3, the UE 104 monitors (typically continuously) a downlink control channel from the base station 102, in part in anticipation of MSG4 (which can contain a termination of the RA procedure along with (optionally) NAS PDUs from the application server via the core network 190. [0061] However, typical application servers are located outside the system shown in FIG. 1 (where those outside systems are shown as “IP Services 176” and “IP Services 197”). For example, the base station 102 may wait on the core network 190, which in turn may wait on application servers outside the Public Land Mobile Network (PLMN) for possible downlink application data intended for the UE 104. In EDT data transfer, network specifications allow for as long as sixty (60) seconds for Cat-M UEs and one hundred twenty (120) seconds for NB- IoT UEs before the base station times out and sends a MSG4 terminating the RA procedure. A UE expends resources (power, bandwidth, and latency) continuing to monitor a downlink control channel from the base station while waiting between MSG3 and MSG4. Note that if the EDT of FIG. 5 is successful, the UE does not move to a fully connected RRC state. A UE would typically use the EDT procedure when there is a sufficiently small, single data packet that does not have more than 1 data packet in response from the application server.

[0062] Referring to FIG. 6, and continuing to refer to prior figures for context, a diagram illustrating RAI EDT data transfer between a UE, a base station, a core network, and an application server for mobile originated (MO) data transfer in wireless communication is shown, in accordance with examples of the technology disclosed herein. In particular, FIG. 6 describes a continuing example where the UE is a NB-IoT enabled parking meter 188 within the coverage of base station 189 using EDT in CP-CIoT mode. Base station 189 is in communication with core network 190 over backhaul 186. Core network 190 has access to a parking meter server as part of IP services 197. Parking meter 188 has short (less than 1000 bits) and infrequent (typically less an one per hour) uplink application data to pass to the application server 197 - and even shorter and less frequent downlink application data to receive from the application server 197.

[0063] Referring to FIG. 7, and continuing to refer to prior figures for context, a flowchart of methods 700 of wireless communication is shown, in accordance with examples of the technology disclosed herein. In such methods 700, during a random access (RA) procedure by a UE of an access network, the UE transmits both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network - Block 702. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission.

[0064] In the continuing example, parking meter NB-IoT UE 188 has a small amount or UE- originated data, e.g., meter ID, desired parking duration, and payment account information from a parker. The UE 188 initiates an RA process with eNB base station 189 using MSG1 RandomAccessPreamble. Absent collisions from other UEs attempting to connect to the base station 189, the base station 189 responds with MSG2 RandomAccessResponse. Upon receiving MSG2, the UE 188 transmits both the application data (meter ID, parking duration, and payment account information) (as an NAS PDU) and an RAI to the base station as part of a MSG3 EDT RRCEarlyDataRequest. The RAI indicates that completion of EDT requires no further uplink application data transmission.

[0065] Referring to FIG. 8, and continuing to refer to prior figures for context, a UE 350 for wireless communication is shown, in accordance with examples of the technology disclosed herein. UE 350 includes, in addition to a processor 359 and memory 360, a UE RAI EDT component 142 as described in conjunction with FIG. 3 above. UE RAI EDT component 142 includes transmitting component 142a. In some examples, the transmitting component 142a transmits both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network. Accordingly, the transmitting component 142a may provide means for transmitting both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network.

[0066] The UE monitors, during the RA procedure, a downlink control channel of the base station upon the transmitting - Block 704. In the continuing example, the UE 188 monitors NB-IoT PDCCH for downlink control information (DCI) from the base station 189. During this time, the base station 189 transmits the NAS PDU containing the application information to the core network 190. The core network routes the application information to the parking application server 197.

[0067] Referring again to FIG. 8, and continuing to refer to prior figures for context, UE RAI EDT component 142 includes monitoring component 142b. In some examples, the monitoring component 142b monitors, during the RA procedure, a downlink control channel of the base station upon the transmitting. Accordingly, the monitoring component 142b may provide means for monitoring, during the RA procedure, a downlink control channel of the base station upon the transmitting.

[0068] The UE receives, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 comprising an instruction for the UE to end monitoring of the downlink control channel - Block 706. In the continuing example the UE 188, while monitoring the NB-IoT PDCCH in downlink from the base station 189 receives an RRCEarlyDataComplete MSG4 including confirmation that a full RRC will not be set up, the EDT is complete, and that the UE can end monitoring NB-IoT PDCCH for DCI. In some examples, the application server 197, after receiving the application data, has other NAS PDU application data to pass to the UE 188 in downlink, e.g., that the payment account information was approved. In such examples, the application server sends the downlink application data through the core network 190 to the base station 189 for transmission to the UE 188 as part of the RRCEarlyDataComplete MSG4.

[0069] Referring again to FIG. 8, and continuing to refer to prior figures for context, UE RAI EDT component 142 includes receiving component 142c. In some examples, the receiving component 142c receives, from the base station during the RA procedure, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel. Accordingly, the receiving component 142c may provide means for receiving, from the base station during the RA procedure, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel.

[0070] The UE ends, during the RA procedure and in response to receiving the instruction, monitoring of the downlink control channel - Block 708. In the continuing example, the UE 188 ends monitoring of the NPCCH, thereby saving resources that would have been spent waiting for the access network to reach the latest time for the base station 189 to transmit a MSG4.

[0071] Referring again to FIG. 8, and continuing to refer to prior figures for context, UE RAI EDT component 142 includes ending component 142d. In some examples, the ending component 142d ends, during the RA procedure and in response to receiving the instruction, monitoring of the downlink control channel. Accordingly, the ending component 142d may provide means for ending, during the RA procedure and in response to receiving the instruction, monitoring of the downlink control channel.

[0072] Referring to FIG. 9, and continuing to refer to prior figures for context, a flowchart of methods 900 of wireless communication is shown, in accordance with examples of the technology disclosed herein. In such methods 900, during a random access (RA) procedure of a user equipment (UE) of a access network, the core network in communication with a base station of the access network, receives both uplink application data of an application executing on the UE and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station - Block 902. The RAI indicates that completion of the EDT requires no further uplink or downlink application data transmission.

[0073] In the continuing example, during the RA procedure, the core network 190 in communication with the base station 189 receives the uplink application data as an NAS PDU and the RAI under EDT via the base station 189 receiving MSG3 RRCEarlyDataRequest.

[0074] Referring to FIG. 10, and continuing to refer to prior figures for context, a core network 160/190 for wireless communication is shown, in accordance with examples of the technology disclosed herein. Core network 160/190 includes, in addition to a processor 1059 and memory 1060, a Core Network RAI EDT component 144. Core Network RAI EDT component 144 includes receiving component 144a. In some examples, the receiving component 144a, in communication with a base station of the access network, receives both uplink application data of an application executing on the UE and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station. Accordingly, the transmitting component 142a may provide means for receiving both uplink application data of an application executing on the UE and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station.

[0075] The core network directs, during the RA procedure and in response to receiving the RAI, the base station to instruct the UE, prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of a downlink control channel - Block 904. In the continuing example, the core network 190, upon receiving the RAI directs the base station 189 to instruct the UE 188 to end the RA process, thereby ending monitoring of the NB-IoT PDCCH downlink for DCI. This saves resources at the UE 188 over the conventional approach. In some examples, the directing is independent of the core network receiving downlink data from an application server of the application intended for the UE. In some examples, the MSG4 includes downlink data from an application server via the core network intended for the UE. Such data is provided by the application server to the core network (and then passed to the base station) in a timely fashion to allow the base station to include this downlink application data as an NAS PDU in the MSG4 RRCEarlyDataComplete message.

[0076] Referring again to FIG. 10, and continuing to refer to prior figures for context, Core Network RAI EDT component 144 includes directing component 144b. In some examples, the directing component 144b directs, during the RA procedure and in response to receiving the RAI, the base station to instruct the UE, prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel. Accordingly, the directing component 144b may provide means for directing, during the RA procedure and in response to receiving the RAI, the base station to instruct the UE, prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel.

[0077] While the continuing example describes RAI EDT where the UE is a NB-IoT enabled parking meter 188 (with only short and infrequent NAS application data transfer requirements) using CP-CIoT mode EDT, base station 189, core network 190, and application server 197, other UEs (including CAT-M UEs) and other modes (e.g., UP-CIoT for NB-IoT UEs) operate in similar fashion - though typically with slightly different message formats. For example, in UP-CIoT, the EDT MSG3 is RRCConnectionResumeRequest and EDT MSG4 is RRCConnectionSuspend. In some examples, IoT applications on the UE side would provide the RAI info if the UE knows that there will be no more originating data and the response from the application server would be none or at max a single data packet. In some examples, IoT UE will use EDT procedure only if RAI is available. If RAI is not available, to avoid the additional power drain due to EDT, EDT will be used by the UE to send the qualified mobile originated (MO) data only when the eNB does not support connected mode discontinuous reception (C-DRX). In some examples, the base station can act on the RAI rather than requiring the core network to direct the base station.

[0078] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented. [0079] The following examples are illustrative only and aspects thereof may be combined with aspects of other embodiments or teaching described herein, without limitation.

[0080] Example 1 is any one of a method, apparatus, computer readable media, apparatus comprising means for executing feature, of wireless communication including during a random access (RA) procedure by a user equipment (UE) of a access network: transmitting both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission; monitoring a downlink control channel of the base station upon the transmitting; receiving, from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel; and ending, in response to receiving the instruction, monitoring of the downlink control channel.

[0081] In Example 2, Example 1 further includes wherein the UE is a narrowband Internet of things (NB IoT) device. In Example 3, any of Example 1-2 includes the EDT being under at least one of control plane cellular IoT (CP-CIoT) or user plane cellular IoT (UP-CIoT).

[0082] In Example 4, any of Examples 1-3 further includes wherein the UE is a CAT -Ml device. In Example 5, any of Examples 1-4 includes the EDT being under user plane - cellular Internet of things (UP-CIoT).

[0083] In Example 6, any of Examples 1-4 further includes, prior to and as a condition of transmitting, determining that the characteristic of the application data and the base station are such that EDT is available. In Example 7, and of Examples 1-6 further includes, prior to and as a condition of transmitting, determining that the base station does not support connected mode discontinuous reception (C-DRX).

[0084] In Example 8, an apparatus for wireless communication includes a memory and at least one processor coupled to the memory. The memory includes instructions executable by the at least one processor to cause the apparatus to perform the method of any one or more of Examples 1-6.

[0085] In Example 9, a computer-readable medium stores computer executable code. The code when executed by a processor cause the processor to execute the method of any one or more of Examples 1-6. [0086] In Example 10, an apparatus for wireless communications includes means for transmitting, during a random access (RA) procedure and by a user equipment (UE) of a access network, both uplink application data and a release assistance indication (RAI) under early data transmission (EDT) in an RA message 3 (MSG3) to a base station of the access network, the RAI indicating that completion of the EDT requires no further uplink application data transmission; means for monitoring, during the RA procedure and by the UE, a downlink control channel of the base station upon the transmitting; means for receiving, during the RA procedure and by the UE from the base station, in response to transmitting the RAI and prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the network, an RA MSG4 instructing the UE to end monitoring of the downlink control channel; and means for ending, during the RA procedure and by the UE, continuous monitoring of the downlink control channel in response to receiving the instruction.

[0087] In Example 11 , the apparatus of Example 10 includes wherein the UE is a narrowband Internet of things (NB IoT) device, and the EDT is under at least one of control plane cellular IoT (CP-CIoT) or user plane cellular IoT (UP-CIoT).

[0088] In Example 12, the apparatus of any of Examples 10 and 11 includes wherein the UE is a CAT -Ml device, and the EDT is under user plane - cellular Internet of things (UP-CIoT).

[0089] In Example 13, any of Examples 10-12 further includes means for, prior to and as a condition of transmitting, determining that the characteristic of the application data and the base station are such that EDT is available. In Example 14, and of Examples 10-13 further includes means for, prior to and as a condition of transmitting, determining that the base station does not support connected mode discontinuous reception (C-DRX).

[0090] In Example 14, a method of wireless communication includes, during a random access (RA) procedure of a user equipment (UE) of a access network: receiving, by a core network in communication with a base station of the access network, both uplink application data of an application executing on the UE and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station, the RAI indicating that completion of the EDT requires no further uplink application data transmission; and directing, by the core network and in response to receiving the RAI, the base station to instruct the UE, prior a latest time for the base station to transmit an RA message 4 (MSG4) specified for the access network, to end monitoring of the downlink control channel. [0091] In example 15, the method of Example 14 includes wherein the directing is independent of the core network receiving downlink data from an application server of the application intended for the UE.

[0092] In Example 16, the method of any of Examples 14-15 includes wherein the MSG4 includes downlink data from an application server of the application intended for the UE.

[0093] In Example 17, an apparatus for wireless communication includes a memory and at least one processor coupled to the memory. The memory includes instructions executable by the at least one processor to cause the apparatus to perform the method of any one or more of Examples 14-16.

[0094] In Example 18, a computer-readable medium stores computer executable code. The code when executed by a processor cause the processor to execute the method of any one or more of Examples 14-16.

[0095] In Example 19, an apparatus for wireless communications includes means for receiving, by a core network in communication with a base station of the access network, both uplink application data of an application executing on the UE and a release assistance indication (RAI) under early data transmission (EDT) via an RA message 3 (MSG3) received by the base station, the RAI indicating that completion of the EDT requires no further uplink application data transmission; and means for directing, by the core network and in response to receiving the RAI, the base station to instruct the UE, prior to a latest time for the base station to transmit an RA message 4 (MSG4) specified for the access network, to end monitoring of the downlink control channel.

[0096] In Example 20, the apparatus of Example 19 includes wherein the directing is independent of the core network receiving downlink data from an application server of the application intended for the UE.

[0097] In Example 21, the apparatus of any of Examples 19-20 includes wherein the MSG4 includes downlink data from an application server of the application intended for the UE.

[0098] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A,

B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and/or

C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”