TW201911939A - Uplink early data transmission - Google Patents

Abstract

A method of wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station includes receiving system information from the base station and transmitting a data communication to the base station over a control plane without establishing an RRC connection with the base station. A UE in an RRC suspended state may transmit a data communication to the base station over a user plane without resuming an RRC connection with the base station. The data communication may comprise data and UE identity information and/or a cause indication. A base station may indicate resources in the system information for the transmission of the data communication information and receive the data communication over the control plane without establishing an RRC connection with the UE or over a user plane without resuming an RRC connection with an RRC suspended UE.

Description

Early uplink data transmission

This application was filed on April 27, 2018 and is named `` Uplink Small Data Transmission For Enhanced Machine-Type-Communication (EMTC) And Internet Of Things (IOT) Communication '' U.S. Application No. 15 / 964,523 Part of the continuation of the case, the US application claims the rights of the following applications: the application filed on May 4, 2017 and named "Uplink Small Data Transmission For Enhanced Machine-Type-Communication (EMTC) And Internet Of Things (IOT ) Communication '' US Provisional Patent Application No. 62 / 501,358, filed on August 11, 2017 and named `` Uplink Early Data Transmission for Cellular Internet of Things Evolved Packet System '' US Provisional Application No. 62 / No. 544,703, and the US Patent Application No. 16 / 024,421 filed on June 29, 2018 and named "Uplink Early Data Transmission", the content of each of these applications is expressly cited The way is incorporated as a whole.

In general, this disclosure relates to communication systems, and more specifically, this disclosure relates to early uplink data transmission for enhanced machine type communication (eMTC) and Internet of Things (IoT) communication.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging and broadcasting. A typical wireless communication system may employ multiplexing access technology that can support communication with multiple users by sharing available system resources. Examples of such multiplexing access technologies include code division multiplexing access (CDMA) systems, time division multiplexing access (TDMA) systems, frequency division multiplexing access (FDMA) systems, orthogonal frequency division multiplexing storage Access (OFDMA) system, single carrier frequency division multiplexing access (SC-FDMA) system and time division synchronization code division multiplexing access (TD-SCDMA) system.

These multiple access technologies have been adopted in various telecommunication standards to provide public agreements that enable different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous action broadband evolution released by the 3rd Generation Partnership Project (3GPP) to meet the new requirements and latency associated with latency, reliability, security, and scalability (eg, along with IoT) other requirements. Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvement of 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunication standards that use these technologies.

Machine type communication (MTC) is usually characterized by the communication of automatic data generation, exchange, processing and actuation between machines with little or no human intervention.

IoT is a network interconnection of physical devices, vehicles (sometimes called "connected devices" and / or "smart devices"), buildings, and other items that can be embedded with: electronic devices, software, Sensors, actuators, and network connections that enable these objects to collect and exchange data and other information.

Many MTC and IoT applications may involve relatively infrequent exchanges of small amounts of data (for example, an uplink packet). For example, a small amount of uplink (UL) data is expected to be generated by metering, alarms, etc. Similarly, for example, queries, updated notifications, and commands to actuators produce small downlink (DL) data transmissions.

The following provides a simplified overview of one or more aspects in order to provide a basic understanding of this aspect. This summary is not an exhaustive overview of all expected aspects, and neither intends to identify key or important elements of all aspects, nor does it intend to illustrate the scope of any or all aspects. Its sole purpose is to provide some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

When the user equipment is in an idle state, in order to establish or restore a radio resource control (RRC) connection, a large amount of management burden is required. Therefore, for MTC or IoT applications, there may be a large consumption of resources for small data transmission (eg, 1 uplink packet or 1 media access control (MAC) block). Therefore, it is desirable to minimize the amount of resources used in MTC and IoT communications.

The various aspects of this disclosure relate to reducing the administrative burden for establishing or restoring RRC connections in order to send small data transfers. When the RRC connection of the UE is in an idle state or a suspended state, a large amount of management burden is required to establish or restore an RRC connection for data transmission. When data transmission is for MTC or IoT applications, this may require a large consumption of resources for small data transmission (eg, 1 media access control (MAC) block). For example, in the conventional technology, before the data can be transmitted, the UE and / or the base station performs many communication steps to establish or restore the RRC connection. In addition, after data transmission, additional steps are performed to release the RRC connection. In contrast, the various aspects of the present disclosure provide data transmission (eg, uplink data transmission) from UEs that have an RRC connection in an idle state or a suspended state (without transitioning to an RRC connected state). Data transmission without performing the RRC establishment procedure or without restoring the RRC connection may be referred to as early data transmission (EDT) or data transmission in RRC connectionless mode.

In one aspect of this disclosure, a method, computer-readable medium, and device for wireless communication at a user equipment (UE) are provided. The device includes a memory and one or more processors coupled to the memory. The device receives system information from the base station and sends data communication to the base station on the control plane without establishing an RRC connection with the base station, where the data communication includes data and at least the following One item: UE identity information and reason indication.

In another aspect of the present disclosure, a method, computer-readable medium, and device for wireless communication at a base station are provided. The device includes a memory and one or more processors coupled to the memory. The device indicates resources in the system information and receives data communication from the UE on the control plane without establishing an RRC connection with the UE, where the data communication includes data and at least one of the following: UE Identity information and reason instructions.

In another aspect of the present disclosure, a method, computer-readable medium, and device for wireless communication at a UE (eg, in an RRC suspended state) are provided. The device includes a memory and one or more processors coupled to the memory. The device receives system information from the base station and sends data communications to the base station on the user plane without restoring the RRC connection to the base station, where the data communications include data and the following At least one item: UE identity information and reason indication.

In one aspect of this disclosure, a method, computer-readable medium, and device for wireless communication at a base station are provided. The device includes a memory and one or more processors coupled to the memory. The device indicates resources in the system information and receives data communication from the UE on the user plane without restoring the RRC connection to the UE, where the data communication includes data and at least one of the following: UE identity information and reason indication.

In order to achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the scope of the patent application. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these characteristics indicate that only some of the various ways in which the principles of each aspect can be adopted, and the description is intended to include all such aspects and their equivalents.

The detailed description set forth below in conjunction with the drawings is intended as a description of various configurations, and is not intended to represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that such concepts can be practiced without such specific details. In some instances, well-known structures and components are illustrated in block diagram form in order to avoid obscuring such concepts.

Several aspects of the telecommunications system will now be provided with reference to various devices and methods. Such devices and methods will be described in the following detailed description and shown in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

For example, an element, or any part of an element, or any combination of elements can 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 arithmetic (RISC) processors, System on chip (SoC), baseband processor, field programmable gate array (FPGA), programmable logic device (PLD), state machine, gate control logic, individual hardware circuits, and configured to execute throughout this disclosure The content describes various functions of other suitable hardware. One or more processors in the processing system can execute software. Whether it is called software, firmware, middleware, microcode, hardware description language, or other names, software should be interpreted broadly to mean instructions, instruction sets, codes, code fragments, code, programs, Programs, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

Accordingly, in one or more exemplary embodiments, the described functions may be implemented in hardware, software, or any combination thereof. If implemented by software, these functions can be stored on the computer-readable medium or encoded as one or more instructions or codes on the computer-readable medium. Computer readable media includes computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electronically erasable programmable ROM (EEPROM), optical disk storage, Disk storage, other magnetic storage devices, a combination of computer-readable media of the type described above, 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 the computer.

Various aspects of this disclosure relate to MTC and / or IoT communications, where the UE is in idle mode or suspended mode when data transmission is initiated. When the UE is in an idle mode or a suspended mode when data transmission is initiated, the conventional technology performs a complete radio resource control connection establishment procedure before data transmission. The complete radio resource control (RRC) connection establishment procedure for idle user equipment (UE) involves a random access (RA) procedure. The RA program can be used to initiate data transfer, but it has a large management burden cost and delay. For example, in the conventional technology, the RA procedure may include a series of messages, such messages include: Msg1 (physical random access channel PRACH preamble), Msg2 (random access request (RAR)), Msg3 (RRC connection request RRC connection re-establishment request, RRC connection recovery request, etc., depending on the reason of the RA procedure), Msg4 (early contention resolution, RRC connection establishment, etc.), and finally Msg5 (which can be used for UL data (unless the SR / BSR is required before payload transmission)). This involves 5 or more messages used for UL data before actual payload transmission. For applications that send uplink data that fits in one transport block size (TBS), this is a large administrative burden.

After the RA procedure is completed, DL / UL transmission can be performed. Therefore, the traditional method performs a large amount of message exchange before the actual payload transmission (even for very small and / or infrequent payloads).

To address these and other issues, the various aspects of this disclosure provide early uplink data transmission and other enhancements for MTC and / or IoT communications. That is, the data transmission in UL can send data (eg, payload) in, for example, Msg1 or Msg3, instead of scheduling the first UL data transmission in Msg5 or later messages as in the conventional technology. In some aspects, these enhancements can be applied to the control plane (CP) / user plane (UP) cellular IoT evolution packet system. By providing early uplink data transmission for UEs in idle or suspended mode for MTC and IoT, it is beneficial to reduce power consumption, delay, and system management burden.

In an example aspect, the data transmission information may be included in Msg3 and sent to the base station (eg, eNodeB). As used in this article, data transmission may represent user data. The transmission of Msg3 may be performed on the initial UL grant provided by a random access request (RAR). Msg3 can also send NAS UE identifiers for initial access without non-access layer (NAS) messages (eg, mobile management messages). A separate Msg3 buffer may be used to perform Msg3 transmission, and the Msg3 buffer may have a higher priority than the UL buffer. Msg3 can use hybrid automatic repeat request (HARQ). In addition, the UE Media Access Control (MAC) layer includes HARQ entities, and can retransmit messages without the UE receiving a MAC layer response from the base station. For example, if the UE does not receive Msg4 (which may cause contention resolution to fail), the UE (MAC) layer may retry access from the idle state.

As provided herein, the RA procedure can be enhanced to support UL data transmission in Msg3. In one example, the payload (eg, service data unit (SDU)) may be included as a common control channel (CCCH) SDU.

FIG. 1 is a diagram showing an example of a wireless communication system and an access network 100. A wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, and an evolved packet core (EPC) 160. The base station 102 may include macro cells (high power honeycomb base station) and / or small cells (low power honeycomb base station). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

The base station 102 (collectively referred to as the Evolutionary Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) is interfaced with the EPC 160 via a backhaul link 132 (eg, S1 interface). In addition to other functions, the base station 102 can also perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobile control functions (eg, communication Delivery, dual connection), inter-cell interference coordination, connection establishment and release, load balancing, non-access layer (NAS) message distribution, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcasting Broadcast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and warning message delivery. The base stations 102 can communicate with each other directly or indirectly (eg, via the EPC 160) via a backhaul link 134 (eg, X2 interface). The backhaul link 134 may be wired or wireless.

The base station 102 can communicate with the UE 104 wirelessly. Each base station 102 of the base station 102 can provide communication coverage for the corresponding 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 including both small cells and macro cells can be called a heterogeneous network. The heterogeneous network may also include a family evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed user group (CSG). The communication link 120 between the base station 102 and the UE 104 may include UL (also known as reverse link) transmission from the UE 104 to the base station 102 and / or DL (also called Called the forward link) transmission. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carrier waves. The base station 102 / UE 104 can use up to a total of Yx MHz ( x component carriers) for each carrier allocated for transmission in each direction up to Y MHz (for example, 5, 10, 15, 20, 100 MHz). The carrier waves may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (eg, 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. The primary component carrier may be called a primary cell (PCell), and the secondary component carrier may be called a secondary cell (SCell).

Some UEs 104 may use a device-to-device (D2D) communication link 192 to communicate with each other. The D2D communication link 192 can use DL / UL WWAN spectrum. The D2D communication link 192 may use one or more secondary link channels, for example, a physical secondary link broadcast channel (PSBCH), a physical secondary link discovery channel (PSDCH), a physical secondary link shared channel (PSSCH), and a physical secondary channel Link Control Channel (PSCCH). D2D communication can be via a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi, LTE, or NR based on the IEEE 802.11 standard.

The wireless communication system may also include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, STA 152 / AP 150 can perform an idle channel assessment (CCA) before communicating to determine whether the channel is available.

The small cell 102 'can operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102 'can adopt NR and use the same 5 GHz unlicensed spectrum as the 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. Small cells 102 'that use NR in unlicensed spectrum can increase coverage and / or increase access network capacity.

The gNodeB (gNB) 180 may operate in millimeter wave (mmW) frequency and / or near mmW frequency to communicate with the UE 104. When gNB 180 operates in mmW or near mmW frequency, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and has a wavelength between 1 mm and 10 mm. The radio waves in this frequency band may be called millimeter waves. Near mmW can be extended down to a frequency of 3 GHz, with a wavelength of 100 mm. The Ultra High Frequency (SHF) frequency band extends between 3 GHz and 30 GHz, also known as centimeter waves. Communication using the mmW / near mmW radio frequency band has extremely high path loss and short distance. The mmW base station 180 can utilize the beamforming 184 with the UE 104 to compensate for extremely high path loss and short distance.

The EPC 160 may include a mobile management entity (MME) 162, other MMEs 164, a service gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network Road (PDN) gate 172. The MME 162 can communicate with the home user server (HSS) 174. The MME 162 is a control node that handles the signal transfer between the UE 104 and the EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted via the service gateway 166, which is itself connected to the PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP service 176. IP services 176 may include the Internet, Intranet, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provision and delivery. BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS transmission volume to base stations 102 belonging to the Multicast Broadcast Single Frequency Network (MBSFN) area that broadcast specific services, and can be responsible for communication period management (start / stop) and collection of eMBMS related Billing information.

The base station can also be called gNB, Node B, Evolution Node B (eNB), access point, base station transceiver, radio base station, radio transceiver, transceiver functional unit, basic service set (BSS), extension Service Set (ESS) or some other appropriate terminology. The base station 102 provides the UE 104 with an access point to the EPC 160. Examples of UE 104 include cellular phones, smart phones, communication period activation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video equipment, digital audio Players (for example, MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare equipment, implants, monitors or Other devices with similar functions. Some of the UEs 104 may be referred to as IoT devices (eg, parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, Mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile service client, client, or some other appropriate terminology.

Referring again to FIG. 1, in some aspects, the UE 104 / base station 180 may be configured to send and receive data communication information without establishing an RRC connection (198), respectively.

FIG. 2A is a diagram 200 showing an example of a DL frame structure. FIG. 2B is a diagram 230 showing an example of channels in the DL frame structure. 2C is a diagram 250 showing an example of a UL frame structure. FIG. 2D is a diagram 280 showing an example of channels within the UL frame structure. Other wireless communication technologies may have different frame structures and / or different channels. The frame (10 ms) can be divided into 10 equal-sized subframes. Each sub-frame may include two consecutive time slots. A resource grid can be used to represent two time slots, and each time slot includes one or more resource blocks (RBs) (also called physical RBs (PRBs)) that are concurrent in time. The resource grid is divided into multiple resource elements (RE). For an ordinary cyclic prefix, RB can contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (for DL, OFDM symbols; for UL, SC-FDMA symbols), a total of 84 REs . For the extended cyclic prefix, the RB may include 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

As shown in FIG. 2A, some of the REs carry a DL reference (pilot frequency) signal (DL-RS) for channel estimation at the UE. The DL-RS may include a cell-specific reference signal (CRS) (sometimes referred to as a common RS), a UE-specific reference signal (UE-RS), and a channel status information reference signal (CSI-RS). FIG. 2A shows CRS for antenna ports ₀ , ₁ , ₂ , and 3 (indicated as R ₀ , R ₁ , R _2, and R _{3, respectively} ), and UE-RS for antenna port 5 (indicated as R ₅ ) And CSI-RS for antenna port 15 (indicated as R).

FIG. 2B shows an example of various channels in the DL sub-frame of the frame. The entity control format indicator channel (PCFICH) is in symbol 0 of slot 0, and carries indication whether the physical downlink control channel (PDCCH) occupies 1, 2 or 3 symbols (Figure 2B shows a PDCCH occupying 3 symbols ) Control format indicator (CFI). The PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs). Each CCE includes nine RE groups (REGs), and each REG includes four consecutive REs in one OFDM symbol. The UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCH may have 2, 4, or 8 RB pairs (FIG. 2B illustrates two RB pairs, and each subset includes one RB pair). The entity hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also in symbol 0 of slot 0, and carries the entity uplink shared channel (PUSCH) to indicate HARQ approval (ACK) / negative ACK (NACK) Feedback HARQ indicator (HI). The primary synchronization channel (PSCH) can be in symbol 6 of time slot 0 in subframes 0 and 5 of the frame. The PSCH carries the primary synchronization signal (PSS) used by the UE 104 to determine the subframe / symbol timing and physical layer identity. The secondary synchronization channel (SSCH) can be in symbol 5 of time slot 0 in sub-frames 0 and 5 of the frame. The SSCH carries a secondary synchronization signal (SSS) used by the UE to determine the 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 the physical cell identifier (PCI). Based on PCI, the UE can decide the location of the above DL-RS. The physical broadcast channel (PBCH) (which carries the main information block (MIB)) can be logically packaged with the PSCH and SSCH to form a synchronization signal (SS) block. The MIB provides the number of RBs in the DL system bandwidth, PHICH configuration, and system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as system information block (SIB)) and paging messages.

As shown in FIG. 2C, some of the REs carry demodulation reference signals (DM-RS) for channel estimation at the base station. In addition, the UE may send a sounding reference signal (SRS) in the last symbol of the subframe. The SRS may have a comb tooth structure, and the UE may transmit the SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

FIG. 2D shows examples of various channels in the UL subframe of the frame. Based on the physical random access channel (PRACH) configuration, PRACH can be in one or more sub-frames within the frame. The PRACH may include six consecutive RB pairs in the subframe. PRACH allows the UE to perform initial system access and achieve UL synchronization. The physical uplink control channel (PUCCH) can be located on the edge of the UL system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling request, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. PUSCH carries data and can additionally be used to carry buffer status reports (BSR), power headroom reports (PHR) and / or UCI.

FIG. 3 is a block diagram of communication between the base station 310 and the UE 350 in the access network. In the DL, the IP packet from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence agreement (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting of system information (eg, MIB, SIB), RRC connection control (eg, 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 reports; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption) , Integrity protection, integrity verification), and delivery support functions; RLC layer functions associated with the following: upper layer packet data unit (PDU) transmission, error correction via ARQ, RLC service data unit (SDU) Concatenation, segmentation and reassembly, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transmission channels, MAC SDU to Multiplexing on the transmission block (TB), MAC SDU demultiplexing from the TB, scheduling information report, error correction via HARQ, prioritization, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping onto the physical channel, and modulation of the physical channel / Demodulation and MIMO antenna processing. The TX processor 316 processes based on various modulation schemes (eg, binary shift phase keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)) to the signal cluster mapping. The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM sub-carrier, multiplexed with reference signals in the time and / or frequency domain (eg pilot frequency), and then combined using inverse fast Fourier transform (IFFT), To generate a physical channel that carries a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to produce multiple spatial streams. The channel estimate from the channel estimator 374 can be used to decide the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived based on the reference signal sent by the UE 350 and / or channel status feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can utilize a corresponding spatial stream to modulate the RF carrier for transmission.

At the UE 350, each receiver 354RX receives a signal via its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a reception (RX) processor 356. The TX processor 368 and RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to restore any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 may combine them 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 fast Fourier transform (FFT). The frequency domain signal includes a separate stream of OFDM symbols for each subcarrier of the OFDM signal. The symbols and reference signals on each sub-carrier are recovered and demodulated by determining the most likely signal cluster point sent by the base station 310. Such soft decisions may be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent 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 functions.

The controller / processor 359 may 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 UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission channel and the logical channel to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for using ACK and / or NACK protocols to support error detection of HARQ operations.

Similar to the functions described in connection with DL transmission by base station 310, the controller / processor 359 provides: RRC layer functions associated with: system information (eg, MIB, SIB) acquisition, RRC connection, and Measurement report; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: Transmission of upper layer PDU, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDU, re-segmentation of RLC data PDU, and reordering of RLC data PDU; and MAC layer functions associated with Mapping between logical channels and transmission channels, MAC SDU to TB multiplexing, MAC SDU demultiplexing from TB, scheduling information reporting, error correction via HARQ, prioritization, and logical channel prioritization.

The TX processor 368 may use the channel estimates derived by the channel estimator 358 from the reference signal or feedback sent by the base station 310 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use a corresponding spatial stream to modulate the RF carrier for transmission.

At the base station 310, UL transmissions are processed in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

The controller / processor 375 may be associated with a memory 376 that stores code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission channel and the logical channel to recover IP packets from the UE 350. The IP packet from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for using ACK and / or NACK protocols to support error detection of HARQ operations.

In one example aspect, one or both of the base station 310 and the UE 350 may have logic units, software, firmware, configuration files, etc. for allowing the MCT / IoT communication described herein.

FIG. 4 is a diagram 400 showing a communication system according to various aspects of the present disclosure. FIG. 4 includes a node 402 and multiple UEs 404, 406. The UE 404 may include MTC UE, IoT UE, bandwidth reduction low complexity (BL) UE, and the like. The UE 406 may also include an MTC UE, IoT UE, or BL UE, or the UE 406 may communicate with the base station in a different manner from MTC, IoT, BL. The node 402 may be a macro node (eg, a base station), a femto node, a pico node, or similar base station, mobile base station, repeater, UE (e.g., in a peer-to-peer or self-organizing mode with another UE Communication), part of it, and / or virtually any component that transmits control data over a wireless network. The UE 404 and the UE 406 may be mobile terminals, stationary terminals, modems (or other tethered devices), a part thereof, and / or substantially any devices that receive control data in a wireless network, respectively.

As shown in FIG. 4, UE 404 receives DL transmission 410 from base station 402 and sends UL transmission 408 to base station 402. In one aspect, DL transmission 410 and UL transmission 408 may include MTC / IoT / BL control information or MTC / IoT / BL data. UE 406 receives DL transmission 412 from base station 402 and sends UL transmission 414 to base station 402. The communication between the UE 404 and the base station 402 may include, for example, a cellular IoT (CIoT) evolution packetization system (EPS) optimization procedure, which includes early data during the random access procedure without transitioning to the RRC connection state transmission. Early data transmission may include UL and / or DL data.

FIG. 5 is an example dialing flowchart 500 according to various aspects of the present disclosure. Referring to FIG. 5, the dialing flowchart 500 shows the communication between the UE 502, the base station 504, the MME 506, and the SGW 508. The UE 502 may include NB-IoT UE, BL UE, eMTC UE or CE UE. In some aspects, the UE 502 may be in an idle state 501 (eg, RRC idle). In block 510, the base station 504 may make a resource decision. The base station determines the resources to be used by the UE 502 for PRACH attempts. The PRACH resources decided at 510 may include PRACH resources associated with early data transmission, for example, PRACH resources allocated for early data transfer without establishing an RRC connection. For example, the base station may allow transmission of small data packet sizes (eg, 10 bytes to 50 bytes) without establishing a complete RRC connection. For example, early data transmission may include a single data packet. The PRACH resources associated with early data transmission may be different from those resources allocated by the base station for data transmission after RRC connection establishment. In addition, for different coverage enhancement (CE) levels, the allocated PRACH resources may be different. Therefore, for early data transmission, the UE may select from the set of PRACH resources associated with the early data transmission for the selected enhanced coverage level.

Enhanced early data transmission (Tx) modes can be included in Msg1 (for example, transmission with RACH preamble) or Msg3 (for example, transmission after RAR), while other data transmission modes may require RRC Send the data after the connection is established.

The base station 504 may announce the allocated PRACH resources via system information broadcasting (SIB) (512). As shown in FIG. 5, the SIB may indicate a separate PRACH resource used for early data transmission (for example, data transfer before RRC connection establishment or without RRC connection establishment). In addition, the SIB announcement can also indicate the transport block size (TBS) that can be used for early data transmission, which can be used by the UE to make a decision about whether to use early data transmission.

In block 514, the UE 502 selects PRACH / NPRACH resources based on the resources advertised in the SIB and the amount of data to be sent. In some aspects, resource selection may be based on random selection or dedicated allocation from the corresponding PRACH pool. The UE may indicate an intention to perform early data transfer to the network (eg, base station 504) via the UE's selection of PRACH / NPRACH resources. For example, when the UE intends to send data before establishing an RRC connection with the base station / without establishing an RRC connection with the base station, the UE may select PRACH from a separate pool allocated for enhanced early data transmission Resources. The UE may decide whether to use enhanced early data transmission to send data based on the amount of data to be sent to the base station. For example, when the UE has a single uplink packet to send to the base station (based on the SIB announcement for the TBS size, which can be adapted in a single MAC block transmission), the UE Choose from PRACH resources. Otherwise, the UE can choose from other PRACH resources. In another example, when comparing with the information provided in the SIB, the UE may decide whether to perform early data transmission based on the number of bytes of data to be transmitted. For example, the size may be limited to a single MAC block. For example, when the number of bytes is less than 50 bytes, the UE may select from PRACH resources allocated for early data transmission. Otherwise, the UE can choose from other PRACH resources. Therefore, the selection of PRACH resources can be based on the amount of data to be sent.

The UE 502 uses the selected PRACH / NPRACH resource to send the PRACH preamble signal 516 as the first communication message to the base station 504 (516). In one example, the PRACH preamble signal may be referred to as Msg1. The PRACH / NPRACH preamble signal selected by the UE may be based on PRACH resources associated with early data transmission. In one example, the UE may include the data in the first transmission to the base station. For example, Msg1 may optionally include a PRACH preamble signal and NAS PDU.

The base station 504 sends the RA response (RAR) to the UE in the second communication message (at 518), the second communication message includes an uplink authorization for the UE to perform early data transmission. In one example, RAR may be referred to as Msg2. In communications that need to establish an RRC connection before data transmission, the RAR may include an uplink grant for the transmission of RRC connection establishment / re-establishment / recovery messages. RAR may also include timing advance (TA) (except temporary C-RNTI, etc.). To enable early data transmission before establishing an RRC connection, in addition to one or more of timing advance, temporary C-RNTI, power control information, etc., RAR 518 may also include an uplink grant for early data transmission. If no power control information is included, the UE 502 may instead use open loop power control in which the UE determines the transmit power.

At 520, the UE 502 may use the initial UL grant indicated in RAR 518 to send the data to the base station. In one example, this message may be referred to as an RRC early data request message. In another example, the message may be called RRC connectionless request. The payload may be included in the message 520 on the CCCH (for example, as a CCCH SDU). Data can be sent on the control plane as a NAS protocol data unit (PDU). The transmission at 520 is performed during the random access procedure and without establishing an RRC connection. Transmission 520 is shown as a third communication message to base station 504, and may be referred to as Msg3. Transmission 520 may also include a UE identification (UEID). In some aspects, the UEID may include a temporary mobile user identity (eg, System Architecture Evolution TMSI (S-TMSI)). In some aspects, if the UE has been previously suspended, the UEID may include a resume ID. As shown in FIG. 5, the message 520 may also include an indication of the cause. The reason may indicate RRC connectionless mode. The cause may be referred to as a "reason code", and the code included in the message may indicate whether the message 520 includes data for transmission in RRC connectionless mode. The indication of the cause may also be referred to as the establishment cause. The UE 502 may take into account the power control information from the RAR (if included in the RAR). The UE 502 may start the contention resolution timer after this step. For example, the controller / processor 359 in the example UE 350 of FIG. 3 may be used to implement a contention resolution timer. The contention resolution timer value for early data transmission can be different compared to the contention resolution timer value for communications that need to establish an RRC connection before data transmission.

The message 520 may include data stored in a separate early data transmission buffer (eg, it may be referred to as an Msg3 buffer). Such a buffer may have a higher priority than a UL buffer used for transmission after RRC connection.

In some aspects, the message 520 may also include an indication of RRC connectionless early UL data transmission. The indication may enable the base station 504 to distinguish the UE's request for early data transmission before the RRC connection is established or after the RRC connection is established. Therefore, the base station 504 may provide additional information, including a fast UL grant for connectionless UL transmission (eg, providing the UE with a UL grant if the UE does not transition to the RRC connected state). The UE can then respond with data transfer without transitioning to the RRC connected state.

In addition, in some aspects, the message 520 may include a NAS PDU and an indication that additional UL data at the UE is pending. Therefore, the base station can respond to this message by providing additional UL authorization for transmission using RRC connectionless mode.

At 522, the base station selects the MME 506 based on the UE identification information (eg, S-TMSI) in the message 520, and forwards the NAS PDU to the MME 506. The base station 504 may also provide the MME 506 with an indication that there is only one uplink NAS PDU. This can be done, for example, by including a reason code (eg, "RRC connectionless mode") in the message 522 to the MME.

At 524, if the DL data is available to the UE 502, the SGW 508 provides the DL data to the MME 506, and the MME 506 forwards the DL data to the base station 504 as a NAS PDU to be transmitted to the UE 502. If the base station 504 has indicated that there is only one UL NAS PDU, in response, the MME 506 may close the S1 application protocol (S1-AP) connection after forwarding any downlink NAS PDU. As shown, the message 524 may include the DL NAS PDU and release command. In addition, the base station indication for a UL NAS PDU can also be used by MME 506 to prioritize the processing of UL data and accelerate or prioritize the transmission of DL data by SGW 508 to MME 506.

At 526, the base station 504 may send a message confirming receipt of the data in the message 520. In one example, the message 526 may be referred to as an RRC early data completion message. In another example, the message may be referred to as an RRC connectionless confirmation message. In some examples, the message may include a fourth message between the UE and the base station, and may be referred to as Msg4. If the UE 502 receives the message 526, it may consider that the early data transmission was successfully completed and that the contention is resolved. The message 526 may include DL NAS PDU. If the NAS PDU is included, the NAS can confirm that it is communicating with a valid network. If the DL data is included in the message 526, the UE may respond with HARQ 528 including the reception of the DL data. If the UE does not receive a response (eg, MAC level response) from the base station, the UE may retransmit the message 520. Failure to receive a response indication within the contention resolution timer causes the contention resolution of the UE to retry access from the idle state to fail. If there is no DL data for the UE, the message 526 may only provide confirmation that the UL data is received. After message 526 or message 528, the UE may continue to be in RRC idle state 530. Therefore, UL data may be sent, for example, during a random access procedure at 516 or 520, without establishing an RRC connection and without the UE transitioning to the RRC connected state.

In some aspects, the message 524 may be missing (for example, the base station sends the data to the MME 506, but for some reason, the MME 506 did not respond). In this case, the base station 504 may start a timer after the message 522, for example. When the timer expires, the base station 504 may proceed to the message 526 with a positive ACK for the successful reception of the message 520. In another example, the base station 504 may start a timer after the message 522. When this timer expires, the base station 504 may proceed to the message 526 with a positive ACK for the successful reception of the message 520, which has additional indications that the base station 504 failed to receive an ACK from the MME 506. In this example, the UE 502 may indicate to the upper layer of the protocol stack that there is no NAS PDU in the message 524. At 530, the UE returns to idle.

In addition, in some aspects, instead of confirming the receipt of the NAS PDU from the base station 504 or otherwise, the MME 506 may also indicate in the message 524 that the UE 502 is to transition from the idle state to the RRC connected state instead of completing RRC connectionless transmission communication period. In this case, the S1-AP may not be turned off immediately, and the base station may send an instruction to the UE 502 in the message 526 about transition to the RRC connection state (eg, RRC connection establishment).

In the example dialing flow 500, no dedicated radio bearer (DRB) and packet data convergence agreement (PDCP) layer and radio link control layer RLC are established for early data transmission. This is because early data transmission may be performed without establishing an RRC connection and instead using control plane RRC messaging. Therefore, the UE 502 remains in the RRC_idle state.

FIG. 6 is an example dialing flowchart 600 illustrating various aspects of the present disclosure. Referring to FIG. 6, a dialing flowchart 600 shows communication between the UE 602, the base station 604, the MME 606, and the SGW 608. UE 602 may include NB-IoT UE, BL UE, eMTC UE or CE UE. In some aspects, the UE 602 may be in an idle state 601 (eg, RRC suspended state). In block 610, the base station may make resource decisions. This decision may be similar to that described in connection with 510 in FIG. 5. For example, the base station 604 may allow a small data packet size (eg, during random access, where the UE does not transition from the RRC suspended state to the RRC connected state) (eg, 10 bytes to 50 bytes) transmission. The data transmission in FIG. 6 may be performed on the user plane, and the data transmission in FIG. 5 may be performed on the control plane. The base station may decide the resources to be used by the UE 602 for PRACH attempts. In some aspects, the base station 604 may allocate PRACH resources for this purpose. The PRACH resources decided at 610 may include PRACH resources associated with enhanced early data transmission, for example, PRACH resources allocated for data transfer before the RRC connection is established or when the RRC connection is not established. The PRACH resources allocated for early data transmission may be different compared to their PRACH resources allocated by the base station for data transmission after RRC connection establishment. In addition, for different CE levels, the allocated PRACH resources may be different. Therefore, for early data transmission, the UE can select from the set of PRACH resources associated with the early data delivery for the selected enhanced coverage level.

In some aspects, the enhanced early data transmission may be included in Msg1 (for example, with RACH preamble signal) or in Msg3 (for example, transmission after RAR) instead of after the RRC connection recovery is completed send. The UE may indicate to the network (e.g., base station 604) about performing the early stage without restoring the RRC connection by selecting PRACH / NPRACH resources from a separate pool allocated for such RRC connectionless early data transfer Intent of data transmission. The base station 604 may announce the resource pool (612) via system information broadcasting (SIB).

In block 614, the UE 602 selects PRACH / NPRACH resources based on the resources advertised in the SIB and the amount of data to be sent. For example, if the size of the data to be transmitted meets the size limit received from the base station, the UE may select PRACH / NPRACH resources from the pool associated with the early data transfer. As described in connection with the example in FIG. 5, the UE can decide whether to use RRC connectionless early data transmission to send uplink data based on the amount of data to be sent. Therefore, if the size of the data exceeds the limit, the UE may select different PRACH / NPRACH resources for performing random access. In some aspects, resource selection may be based on random selection or dedicated allocation from the corresponding PRACH pool.

The UE 602 sends the selected PRACH / NPRACH preamble signal to the base station 604 in the first communication message (616). The first communication message may be called Msg1, and may initiate early data transmission. The PRACH / NPRACH preamble signal selected by the UE may be based on PRACH resources associated with early data transmission. In one example, the data for early transmission may be included in the first message to the base station.

The base station 604 sends the RAR to the UE (at 618) in a second communication message (eg, it may be referred to as Msg2). RAR may include uplink grants for early data transmission. RAR may also include timing advance (in addition to temporary C-RNTI, etc.). In order to realize the transmission of data without the UE 502 recovering the RRC connection, the RAR may also include power control information. Alternatively, the UE 502 may use open loop power control (eg, the UE decides to transmit power).

At 620, the UE 602 may send the data to the base station based on the uplink grant indicated in the RAR 618. The data can be included in the message 620 on the CCCH. The message 620 may be the third communication message to the base station, and may be called Msg3. Data can be sent on the user plane as a data PDU. The transmission at 620 may be performed during the random access procedure and without resuming the previously suspended RRC connection. The message 620 may include the UE identifier. Because the UE is in the RRC suspended state 601, the UE identifier may include the recovery ID of the UE. Because the UE 602 has been previously suspended, Msg3 may include a message similar to the RRC connection recovery request (which includes the recovery ID of the UE and includes application data). The message may also indicate the cause, for example, indicating early data transmission as the cause of the message. Such an indication of the cause may be referred to as "recovery reason" or "establishment reason". For example, only a subset of cause values may be suitable for early data transmission. Alternatively, a new recovery reason value may be defined for the early transmission of data in the message 620. If the new cause value is signaled, the base station can forward the data to MME 606 without restoring RRC. Alternatively, a new message can be defined to carry a combination of unencrypted and encrypted payload.

The UE 602 may apply security to the data PDU carried by the message 620. Therefore, the message 620 may also include an authentication token. FIG. 6 shows a message including an example authentication token called short recovery MAC-I. The authentication token can also be called other names. Integrity can also be applied to the entire message 620. When in the RRC suspended state, the UE 602 stores a security key to be used for integrity that can be resumed. In some aspects, the UE 602 may also store the key used for encryption. Therefore, user data on both the uplink and downlink can be encrypted. The UE 602 may be provided with the Next Hop Chaining Count (NextHopChainingCount) and the resume ID (for example, at 601 from the previous communication period, or at 634, both of the current communication period may be provided to use In the next communication period).

In some aspects, a copy of the PDU (eg, data) may be left in the PDCP stack to make possible repeated transmission attempts if the transmission of the message 620 fails.

The UE 602 may also use a security parameter (at 620) based on the next-hop connection count provided during the most recent suspension period (eg, in the RRC connection release message from the previous RRC connection). Therefore, the data can be encrypted based on the count (such as the next hop link count). The UE 602 can encrypt the data PDU and calculate the integrity key (for example, on the entire RRC connectionless recovery request message). In some aspects, the eNodeB fund key (KeNB), the integrity key for RRC signal transmission (KRRCint), the encryption key for RRC (KRRCenc), or other security parameters may be used for, for example, MAC calculation and optional encryption . The security parameter may be based on information previously provided to the UE (eg, during a previous suspension). The recovery ID, recovery reason, and short recovery MAC-I can be sent without encryption.

At block 622, the base station 604 optionally decodes the RRC message, obtains the UE context and verifies the integrity. If the integrity is successfully verified, the base station decrypts the data.

At 624, the base station sends an S1-AP UE context recovery request to the MME 606, and the S1-AP UE context recovery request triggers the MME 606 to resume the suspended connection. Therefore, the base station initiates the S1-AP context restoration procedure to restore the S1 user plane external interface (S1-U) bearer. In some aspects, the base station 604 may signal the MME 606 that there is only one uplink NAS PDU. This can be done, for example, by including a reason code (eg, "RRC connectionless mode"). This indication can also be used by MME 606 to prioritize the processing of UE data, and accelerate or prioritize the sending of confirmations for recovery. At 626, the MME 606 configures / resumes the bearer, for example, requests the S-GW to restart the S1-U bearer for the UE. At 628, the MME sends the S1-AP UE context recovery response to the base station 604 to confirm the configuration and recovery of the bearer, for example, to confirm the UE context recovery to the base station.

In some aspects, the UE context may be available / unrecoverable (for example, the base station is a new base station and there is no X2 interface). Therefore, at 628, the MME 606 may indicate failure in the context recovery response.

In some aspects, the UE context recovery response may be missing (for example, the base station 604 sends the UE context recovery request to the MME, but for various reasons, the MME does not respond). In this case, by the base station 604 sending an instruction about establishing / restoring the RRC connection, the UE 602 can restore to the complete RRC connection.

At 630, the base station forwards the data PDU to SGW 608. Similar to the example described in conjunction with FIG. 5, if the downlink data is available for the UE, the S-GW may send the downlink data to the base station after receiving the uplink data at 630. As shown in FIG. 6, early data transmissions may include a single uplink data transmission (eg, 620). Similarly, early data transmission may include a single downlink data transmission described in connection with FIG. 6.

If there is only one UL NAS PDU, at 632, the S1 context may be released after the data has been forwarded. For example, when no additional data is expected, the S1 connection can be suspended and the S1-U bearer can be activated. The UE can return to the RRC idle and suspended state. As shown, the base station may send a message 634 indicating that early data transmission is completed and the UE may return to the RRC idle, suspended state 638. The message 634 may include a contention resolution message. The message 634 may be integrity protected, and may include a count (such as a next hop connection count) and a recovery ID for the UE. The order of the messages 630 and 634 can be adjusted so that the confirmation message 634 is sent to the UE before the base station forwards the data 630 to the SGW.

In some aspects, after having passed AS security for the received access layer (AS) message, the UE 602 may send HARQ.

In some aspects, instead of confirming the receipt of the NAS PDU from the base station 604 or otherwise, the MME 606 may also instruct the UE 602 to transition from the idle state to the RRC connected state instead of completing the RRC connectionless transmission communication period . In this case, the S1 context may not be released, or the S1 context may not be immediately closed, and the base station may send an indication to the UE 602 about transition to the RRC connection state (eg, RRC connection establishment).

7 is a flowchart 700 of a method for wireless communication of early data transmission without an RRC connection to a base station. The UE may be in an RRC idle state, as described in connection with FIG. 5. The dashed line shows the optional aspect. The method may be performed by a UE (eg, UE 104, 350, 502, 602, device 802/802 '). The UE may include NB-IoT UE, BL UE, eMTC UE or CE UE.

At 702, the UE receives SI from the base station. 5 and 6 show examples of SI 512, 612 received by the UE. The SI may indicate the PRACH resource to the UE. The PRACH resource may include a set of PRACH resources used for early data transmission (for example, data sent without establishing an RRC connection). SI can also indicate the maximum size of UL data that can be sent by using early data transmission. Such indications may correspond to different CE levels of different NPRACH resources, respectively.

As shown at 704, the UE may select an RRC connection mode for sending data communications, for example, between an active RRC connection transmission mode and an RRC connectionless transmission mode. The selection can be based on any of a variety of factors, including the size of the material to be sent. At 706, the UE may send an indication of the RRC connection mode used to send the data communication to the base station. The indication may include selection of PRACH resources from the PRACH resource pool associated with early data transfer. The PRACH resource may include NPRACH. The selected PRACH resource may also indicate an intention to perform connectionless early data transmission. The SI may be broadcast from the base station and may indicate PRACH resources associated with early data transmission in the case where the UE has not transitioned to the RRC connected state. The UE may select resources based at least in part on the amount of data to be sent in the data communication.

The data communication can be sent to the base station during a random access procedure in which the UE has not established an RRC connection. At 708, the UE may send a random access preamble signal to the base station. The random access preamble signal may be based on a selection at 706 from PRACH resources associated with early data transfer. At 710, the UE may receive an authorization for uplink transmission without establishing an RRC connection.

At 712, the UE may send the data communication to the base station on the control plane without establishing an RRC connection with the base station. At 712, the data communication can be sent to the base station based on the authorization received at 710. Data communication includes data and instructions for the reasons for data communication. In some aspects, the cause indication may notify the base station to receive the data communication included in the message without establishing an RRC connection. For example, the reason indication may be referred to as a reason code, establishment reason, and so on. In some aspects, the cause indication may indicate to the base station that the UE intends to perform early data transmission without establishing an RRC connection. Data communications can be sent on CCCH (for example, in NAS messages). Therefore, the data communication can be sent to the base station without the UE transitioning to the RRC connected state. Data communication may include a single uplink data transmission. The size of the data included in a single uplink data transmission may be smaller than the size limit indicated by the base station. The data may include NAS PDUs sent on the control plane, as described in connection with FIG. 5.

The data communication may also include UE identity information, for example, S-TMSI for the UE.

Early data transfer may also include a small amount of downlink data received from the network. Therefore, at 714, the UE can receive downlink data communications from the base station on the control plane without establishing an RRC connection with the base station. Downlink data communications can be received in RRC messages indicating the completion of early data transfer. The UE may receive a single downlink data transmission, for example, as shown in FIG. 5. The additional aspect described in conjunction with FIG. 5 or 6 may be performed by the UE in conjunction with the method of FIG. 7. The UE may continue to be in the RRC idle state after sending and / or receiving early data transmission.

FIG. 8 is a conceptual data flow diagram 800 illustrating the data flow between different components / components in the example device 802. The device may be a UE (eg, UE 104, 350, 502, 602). The UE may include NB-IoT UE, BL UE, eMTC UE or CE UE, etc. The apparatus includes: a receiving unit 804 for receiving downlink communication from the base station 850; and a transmitting unit 806 for transmitting uplink communication to the base station 850. The device includes: a system information component 808 for receiving system information from the base station 850; and a data communication component 810 for transmitting data communication on the control plane without establishing an RRC connection with the base station To the base station, where the data communication includes data and instructions for the reasons for the data communication. The apparatus may include: an RRC mode component 812 for selecting an RRC connection mode for transmitting data communication; and an instruction component 814 for transmitting an indication of the RRC connection mode for transmitting data communication to the base station. The indication may be based on PRACH resources associated with early data transfer. The apparatus may include: a preamble signal part 816 for transmitting a random access preamble signal to the base station. The apparatus may include a RAR component 818 for receiving RAR from the base station, and the RAR may include an authorization for uplink transmission without establishing an RRC connection. The apparatus may include a downlink data component 820 for receiving downlink data communication from the base station on the control plane without establishing an RRC connection with the base station.

The apparatus may include additional components for each of the blocks executing the algorithm in the flowcharts of FIGS. 5, 6 and 7 described above. Therefore, each block of the flowcharts of FIGS. 5, 6, and 7 described above may be executed by a component, and the device may include one or more of those components. The component may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, and stored in a computer-readable medium for Implemented by a processor, or some combination thereof.

9 is a diagram 900 showing an example of a hardware implementation of a device 902 'employing a processing system 914. The processing system 914 may be implemented using a busbar architecture (typically represented by busbar 924). The bus 924 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 914 and the overall design constraints. Bus 924 will include one or more processors and / or hardware components (by processor 904, components 804, 806, 808, 810, 812, 814, 816, 818, 820 and computer readable media / memory 906 said) the various circuits are connected together. The bus 924 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described again.

The processing system 914 may be coupled to the transceiver 910. The transceiver 910 is coupled to one or more antennas 920. The transceiver 910 provides means for communicating with various other devices on the transmission medium. The transceiver 910 receives signals from one or more antennas 920, extracts information from the received signals, and provides the extracted information to the processing system 914 (specifically, the receiving unit 804). In addition, the transceiver 910 receives information from the processing system 914 (specifically, the transmitting part 810), and generates a signal to be applied to one or more antennas 920 based on the received information. The processing system 914 includes a processor 904 coupled to a computer-readable medium / memory 906. The processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 906. The software, when executed by the processor 904, causes the processing system 914 to perform the various functions described above for any particular device. The computer-readable medium / memory 906 can also be used to store data manipulated by the processor 904 when executing software. The processing system 914 also includes at least one of components 804, 806, 808, 810, 812, 814, 816, 818, 820. The component may be a software component running in the processor 904, located / stored in the computer-readable medium / memory 906, one or more hardware components coupled to the processor 904, or some combination thereof. The processing system 914 may be a component of the base station 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376. The processing system 914 may be a component of the UE 350, and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360.

In one configuration, the device 802/802 'for wireless communication includes: means for receiving system information from the base station; for sending data communication on the control plane without establishing an RRC connection with the base station A component for the base station, where the data communication includes data and an indication of the reason for the data communication; a component for selecting the RRC connection mode used to send the data communication; an instruction to use the RRC connection mode for sending the data communication A component sent to the base station; a component used to send random access preamble signals to the base station; a component used to receive authorization for uplink transmission without establishing an RRC connection, where data communication is based on The authorization is sent to the base station; and means for receiving downlink data communication from the base station without establishing an RRC connection with the base station. The aforementioned components may be one or more of the aforementioned components of the device 802 and / or the processing system 914 of the device 802 'configured to perform the functions recited by the aforementioned components. As previously mentioned, the processing system 914 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned components may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned components.

FIG. 10 is a flowchart 1000 of a method for wireless communication of early data reception without an RRC connection to a UE. The method may be performed by a base station (e.g., base stations 102, 180, 310, 504, 604, 850, devices 1102, 1102 '). The dashed line shows the optional aspect.

At 1002, the base station indicates resources in the system information. 5 and 6 show examples of SI 512, 612 transmitted by the base station. The SI may indicate the PRACH resource to the UE. The PRACH resource may include a set of PRACH resources used for early data transmission (for example, data sent without establishing an RRC connection). SI can also indicate the maximum size of UL data that can be sent by using early data transmission. Such indications may correspond to different CE levels of different NPRACH resources, respectively.

At 1012, the base station receives data communication from the UE without establishing an RRC connection with the UE, where the data communication includes data and a cause indication. The cause indication may notify the base station to receive the data communication included in the RRC connection recovery message without restoring the RRC connection. For example, the reason indication may be referred to as a reason code, establishment reason, and so on. The cause indication may indicate to the base station that the UE intends to perform early data transmission without establishing an RRC connection. The data communication may be included in an RRC message indicating the intention to perform connectionless early data transmission. Data communications can be received on CCCH (for example, in NAS messages). Therefore, at 1014, the data communication can be received from the UE and forwarded to the core network component without establishing an RRC connection state with the UE (for example, when the UE has not transitioned to the RRC connection state) . Data communication may include a single uplink data transmission. The data may include NAS PDUs received on the control plane, as described in connection with FIG. 5. The data may include data PDUs received on the user plane, as described in connection with FIG. 6.

Data communication may also include UE identity information (for example, when receiving data on the control plane, including S-TMSI; or when receiving data on the user plane, including the recovery ID for the UE). Data communication may also include authentication tokens, for example, when receiving data on the user plane. Data can be received on the user plane, for example, when the UE starts from the RRC idle, suspended state. In this example, the data communication can be received in the RRC connection recovery message, and the cause indication can notify the base station to receive the data communication included in the RRC connection recovery message without recovering the RRC connection. Data communication can also include authentication tokens.

Data communications may be received from the UE during the random access procedure, as shown in the examples in FIGS. 5 and 6. For example, at 1006, the base station may receive a random access preamble signal from the UE based on PRACH resources (eg, NPRACH resources) associated with early data transfer. Different resources can be associated with different CE levels. In response, at 1008, the base station may send a RAR to the UE, which includes an uplink grant for early data transmission without establishing an RRC connection with the UE. Subsequently, at 1012, data communications can be received from the UE based on the uplink grant.

Early data transfer may also include a small amount of downlink data sent to the UE. Therefore, at 1016, the base station can send downlink data communication from the base station without establishing an RRC connection with the UE. The downlink data communication may be sent to the UE in an RRC message indicating to the UE that early data transfer is complete. The base station may send a single downlink data transmission, for example, as shown in FIG. The additional aspect described in conjunction with FIG. 5 or 6 may be performed by the base station in conjunction with the method of FIG. 10.

11 is a conceptual data flow diagram 1100 illustrating the data flow between different components / components in the exemplary device 1102. The device may be a base station (eg, base stations 102, 180, 310, 504, 604, 850). The device includes: a receiving component 1104 for receiving uplink communication from the UE 1150; and a downlink component 1106 for transmitting downlink communication to the UE and / or for communicating with the core network 1155 . The device includes: SI component 1108 for indicating resources in system information; and data communication component 1110 for receiving data communication from the UE without establishing an RRC connection with the UE, wherein the data communication includes data And reason instructions. The apparatus may include: a preamble signal part 1112 for receiving a random access preamble signal from the UE based on PRACH resources associated with early data transfer; and a RAR part 1114 for sending a random access response to UE, the random access response includes an uplink grant for early data transmission without establishing an RRC connection with the UE. The apparatus may include: a core network component 1116, which is used to forward data to the core network without establishing an RRC connection with the UE. The apparatus may include a downlink data component 1118 for transmitting downlink data communication to the UE without establishing an RRC connection with the UE.

The apparatus may include additional components for each of the blocks executing the algorithm in the flowcharts of FIGS. 5, 6 and 10 described above. Therefore, each block of the flowcharts of FIGS. 5, 6, and 10 described above may be executed by a component, and the device may include one or more of those components. The component may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, and stored in a computer-readable medium for Implemented by a processor, or some combination thereof.

12 is a diagram 1200 showing an example of a hardware implementation of a device 1102 'that employs a processing system 1214. The processing system 1214 may be implemented using a busbar architecture (typically represented by the busbar 1224). The busbar 1224 may include any number of interconnecting busbars and bridges, depending on the specific application of the processing system 1214 and overall design constraints. The bus 1224 will include one or more processors and / or hardware components (represented by the processor 1204, components 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118 and computer readable media / memory 1206 ) Connect the various circuits together. The bus 1224 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described again.

The processing system 1214 may be coupled to the transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides means for communicating with various other devices on the transmission medium. The transceiver 1210 receives signals from one or more antennas 1220, extracts information from the received signals, and provides the extracted information to the processing system 1214 (specifically, the receiving component 1104). In addition, the transceiver 1210 receives information from the processing system 1214 (specifically, the transmitting unit 1106), and generates a signal to be applied to one or more antennas 1220 based on the received information. The processing system 1214 includes a processor 1204 coupled to a computer readable medium / memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer readable medium / memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described above for any particular device. The computer-readable medium / memory 1206 can also be used to store data manipulated by the processor 1204 when executing software. The processing system 1214 also includes at least one of components 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118. The component may be a software component running in the processor 1204, located / stored in the computer-readable medium / memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be a component of the base station 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376.

In one configuration, the device 1102/1102 'for wireless communication includes: means for indicating resources in system information; means for receiving data communication from the UE without establishing an RRC connection with the UE, wherein The data communication includes data and reason indications; a component for receiving random access preamble signals from the UE based on PRACH resources associated with early data transfer; a component for sending random access responses to the UE, the random storage The response includes an uplink grant for early data transmission without establishing an RRC connection with the UE; a means for forwarding data to the core network without establishing an RRC connection with the UE; A component that transmits downlink data communication to the UE without establishing an RRC connection with the UE. The aforementioned components may be one or more of the aforementioned components of the device 1102 and / or the processing system 1214 of the device 1102 'configured to perform the functions recited by the aforementioned components. As previously mentioned, the processing system 1214 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions recited by the aforementioned components.

FIG. 13 is a flowchart 1300 of a method for wireless communication of early data transmission in the case where the RRC connection to the base station is not restored. For example, the UE may be in an RRC suspended state, for example, as described in connection with FIG. 6. The dashed line shows the optional aspect. The method may be performed by a UE (eg, UE 104, 350, 502, 602, device 1402/1402 '). The UE may include NB-IoT UE, BL UE, eMTC UE or CE UE.

At 1302, the UE receives SI from the base station. FIG. 6 shows an example of SI 612 received by the UE. The SI may indicate the PRACH resource to the UE. The PRACH resource may include a set of PRACH resources used for early data transmission (for example, data sent without restoring the RRC connection). The SI can also indicate the maximum size of UL data that can be sent by using early data transmission (for example, on the user plane without restoring the RRC connection). Such indications may correspond to different CE levels of different NPRACH resources, respectively.

As shown at 1304, the UE may select an RRC connection mode for sending data communications, for example, to select between an active RRC connection transmission mode and an RRC connectionless transmission mode (where the UE does not restore the RRC connection). The selection can be based on any of a variety of factors, including the size of the material to be sent. At 1306, the UE may send an indication to the base station of the RRC connection mode used to send the data communication. The indication may include selection of PRACH resources from the PRACH resource pool associated with early data transfer. The PRACH resource may include NPRACH. The selected PRACH resource may also indicate an intention to perform connectionless early data transmission. The SI may be broadcast from the base station and may indicate PRACH resources associated with early data transmission in the case where the UE has not transitioned to the RRC connected state. The UE may select resources based at least in part on the amount of data to be sent in the data communication.

The data communication can be sent to the base station during the random access procedure in which the UE does not restore the RRC connection. At 1308, the UE may send a random access preamble signal to the base station. The random access preamble signal may be based on a selection at 1306 from PRACH resources associated with early data transfer. At 1310, the UE may receive an authorization for uplink transmission without restoring the RRC connection.

At 1312, the UE can send the data communication to the base station on the user plane without restoring the RRC connection with the base station. At 1312, the data communication can be sent to the base station based on the authorization received at 1310. Data communications can include data and cause indications. The data communication may include RRC messages. For example, data and RRC messages can be multiplexed together in the same transmission, for example. This may be the opposite of the example in FIG. 7, where the data is included in the RRC message and is sent on the control plane. In one example, the cause indication can be included in the RRC message. In another example, the cause indication may be separate from the RRC message, but included in the same data communication transmission. The RRC message may include an RRC connection restoration request together with an indication of the reason for data communication. The data communication may also include the UE ID, which may be included in the RRC message. Therefore, the user data and the RRC message including the cause indication and / or the UE ID can be multiplexed and sent together in the same transmission on the user plane. In another example, the data and reason can be included in the RRC message. In some aspects, the data may be sent together with the RRC connection recovery message, and the cause indication may notify the base station to receive the data multiplexed with the RRC connection recovery message without restoring the RRC connection. For example, the reason indication may be referred to as a reason code, recovery reason, and so on. Data communications can be sent on CCCH (for example, in NAS messages). Therefore, the data communication can be sent to the base station without the UE transitioning to the RRC connected state. Data communication may include a single uplink data transmission. The size of the data included in a single uplink data transmission may be less than or equal to the size limit indicated by the base station. The data may include data PDUs sent on the user plane, as described in connection with FIG. 6.

The data communication may also include UE identity information for the UE to send data on the user plane (for example, the recovery ID included in the RRC message). Data communication can also include authentication tokens. Data can be sent on the user plane, for example, when the UE is in RRC idle or suspended state.

Early data transfer may also include a small amount of downlink data received from the network. Therefore, at 1314, the UE can receive downlink data communications from the base station on the user plane without restoring the RRC connection with the base station. Downlink data communication may include RRC messages indicating the completion of early data transfer. The UE may receive a single downlink data transmission, for example, as shown in FIG. 6. The additional aspect described in conjunction with FIG. 5 or 6 may be performed by the UE in conjunction with the method of FIG. 13. The UE can remain in the RRC idle and suspended state after sending and / or receiving early data transmission.

14 is a conceptual data flow diagram 1400 illustrating the data flow between different components / components in the exemplary device 1402. The device may be a UE (eg, UE 104, 350, 502, 602) in an RRC suspended state with the base station 1450. The UE may include NB-IoT UE, BL UE, eMTC UE or CE UE, etc. The apparatus includes: a receiving unit 1404 for receiving downlink communication from the base station 1450; and a transmitting unit 1406 for transmitting uplink communication to the base station 1450. The device includes: a system information component 1408 for receiving system information from the base station 1450; and a data communication component 1410 for communicating data on the user plane without restoring the RRC connection with the base station Sent to the base station, where the data communication includes data and an indication of the reason for the data communication. The apparatus may include: an RRC mode component 1412 for selecting an RRC connection mode for transmitting data communication; and an instruction component 1414 for transmitting an indication of the RRC connection mode for transmitting data communication to the base station. The indication may be based on PRACH resources associated with early data transfer. The apparatus may include: a preamble signal part 1416 for transmitting a random access preamble signal to the base station. The apparatus may include a RAR component 1418 for receiving RAR from the base station, and the RAR may include an authorization for uplink transmission without restoring the RRC connection. The apparatus may include a downlink data component 1420 for receiving downlink data communication from the base station on the user plane without establishing an RRC connection with the base station. The device may also include a token component 1422 configured to include the authentication token and the data sent to the base station.

The apparatus may include additional components for each of the blocks executing the algorithm in the flowcharts of FIGS. 6 and 13 and FIGS. 5 and 7 described above. Therefore, each block of the flowcharts of FIGS. 5, 6, 7 and 13 described above may be executed by a component, and the device may include one or more of those components. The component may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, and stored in a computer-readable medium for Implemented by a processor, or some combination thereof.

15 is a diagram 1500 showing an example of a hardware implementation of a device 1402 'employing a processing system 1514. The processing system 1514 may be implemented using a busbar architecture (typically represented by the busbar 1524). The bus bar 1524 may include any number of interconnecting bus bars and bridges, depending on the specific application of the processing system 1514 and overall design constraints. Bus 1524 will include one or more processors and / or hardware components (by processor 1504, components 1404, 1406, 1408, 1410, 1412, 1414, 1416, 1418, 1420, 1422, and computer-readable media / Memory 1506 to represent) the various circuits are connected together. The bus 1524 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described again.

The processing system 1514 may be coupled to the transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides means for communicating with various other devices on the transmission medium. The transceiver 1510 receives signals from one or more antennas 1520, extracts information from the received signals, and provides the extracted information to the processing system 1514 (specifically, the receiving part 1404). In addition, the transceiver 1510 receives information from the processing system 1514 (specifically, the transmitting part 1410), and generates a signal to be applied to one or more antennas 1520 based on the received information. The processing system 1514 includes a processor 1504 coupled to a computer readable medium / memory 1506. The processor 1504 is responsible for general processing, including the execution of software stored on the computer readable medium / memory 1506. The software, when executed by the processor 1504, causes the processing system 1514 to perform the various functions described above for any particular device. The computer-readable medium / memory 1506 can also be used to store data manipulated by the processor 1504 when executing software. The processing system 1514 also includes at least one of components 1404, 1406, 1408, 1410, 1412, 1414, 1416, 1418, 1420, 1422. The component may be a software component running in the processor 1504, located / stored in the computer-readable medium / memory 1506, one or more hardware components coupled to the processor 1504, or some combination thereof. The processing system 1514 may be a component of the base station 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376. The processing system 1514 may be a component of the UE 350, and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360.

In one configuration, the device 1402/1402 'for wireless communication includes: means for receiving system information from the base station when in the RRC suspended state; for restoring the RRC connection with the base station without The component that sends data communication to the base station on the user plane, where the data communication includes data and an indication of the reason for the data communication; the component used to select the RRC connection mode used to send the data communication; The component that sends the RRC connection mode indication of the data communication to the base station; the component that sends the random access preamble signal to the base station; and it is used to receive authorization for uplink transmission without restoring the RRC connection Component, wherein the data communication is sent to the base station based on the authorization; and a component for receiving downlink data communication from the base station on the user plane without restoring the RRC connection with the base station. The aforementioned component may be one or more of the aforementioned components of the device 1402 and / or the processing system 1514 of the device 1402 'configured to perform the functions recited by the aforementioned component. As previously mentioned, the processing system 1514 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned components may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned components.

FIG. 16 is a flowchart 1600 of a method for wireless communication of early data reception in the case where RRC connection to the UE is not restored. The method may be performed by a base station (e.g., base stations 102, 180, 310, 504, 604, 850, devices 1702, 1702 '). The base station may be in the RRC suspended state, as described in connection with FIG. 6. The dashed line shows the optional aspect.

At 1602, the base station indicates the resource in the system information. FIG. 6 shows an example of SI 612 transmitted by the base station. The SI may indicate the PRACH resource to the UE. The PRACH resource may include a set of PRACH resources used for early data transmission (for example, data sent without establishing an RRC connection). SI can also indicate the maximum size of UL data that can be sent by using early data transmission. Such indications may correspond to different CE levels of different NPRACH resources, respectively.

At 1612, the base station receives the data communication from the UE on the user plane without restoring the RRC connection with the UE, where the data communication includes the data and the cause indication. The data communication may include RRC messages. For example, data can be multiplexed together with RRC messages in, for example, the same transmission. In one example, the cause indication can be included in the RRC message. In another example, the cause indication may be separate from the RRC message, but included in the same data communication transmission. The RRC message may include an RRC connection restoration request together with an indication of the reason for data communication. The data communication may also include the UE ID, for example it may be included in the RRC message. Therefore, the user data and the RRC message including the cause indication and / or the UE ID can be multiplexed and sent together in the same transmission on the user plane. In another example, the data and reason can be included in the RRC message. The reason indication may notify the base station to receive data of multiplexing with the RRC connection recovery message without restoring the RRC connection. For example, the reason indication may be referred to as a reason code, recovery reason, and so on. The cause indication may indicate to the base station that the UE intends to perform early data transmission without restoring the RRC connection. The data can be sent together with the RRC message in a single transmission (for example, to multiplex it), the RRC message indicates an intention to perform connectionless early data transmission (for example, in the case where the RRC connection is not restored). Data communications can be received on the CCCH (for example, in the data PDU). Therefore, at 1614, it is possible to receive data from the UE and forward it to the core without restoring the RRC connection state with the UE (eg, when the UE has not transitioned from the RRC suspended state to the RRC connected state) Network components. Data communication may include a single uplink data transmission. The data may include data PDUs received on the user plane, as described in connection with FIG. 6.

Data communications (eg, RRC messages) may also include UE identity information, such as the recovery ID used for the UE. The data communication may also include an authentication token, as shown in message 620 in FIG. 6. Data can be received on the user plane, for example, when the UE is in RRC idle or suspended state. In this example, the data communication may include an RRC connection recovery message, and the cause indication may notify the base station to receive data included in the data communication together with the RRC connection recovery message without restoring the RRC connection. Data communication can also include authentication tokens.

Data communications can be received from the UE during the random access procedure, as shown in the examples in both Figures 5 and 6. For example, at 1606, the base station may receive a random access preamble signal from the UE based on PRACH resources (eg, NPRACH resources) associated with early data transfer. Different PRACH resources can be associated with different CE levels. In response, at 1608, the base station can send a RAR to the UE, which includes an uplink grant for early data transmission without restoring the RRC connection with the UE. Subsequently, at 1612, data communications can be received from the UE based on the uplink grant. FIG. 6 shows an example message 620 as a transmission.

Early data transfer may also include a small amount of downlink data sent to the UE. Therefore, at 1616, the base station can send downlink data communication from the base station on the user plane without establishing an RRC connection with the UE. The downlink data communication may be sent to the UE in an RRC message indicating to the UE that early data transfer is complete. The base station may send a single downlink data transmission, for example, as shown in FIG. 6. Another aspect described in conjunction with FIG. 5 or 6 may be performed by the base station in conjunction with the method of FIG. 16.

17 is a conceptual data flow diagram 1700 showing the data flow between different components / components in the exemplary device 1702. The device may be a base station (eg, base stations 102, 180, 310, 504, 604, 850). The device includes: a receiving part 1704 for receiving uplink communication from the UE 1750; and a downlink part 1706 for sending downlink communication to the UE and / or for communicating with the core network 1755 . The device includes: an SI component 1708 for indicating resources in system information; and a data communication component 1710 for receiving data communication from the UE on the user plane without restoring the RRC connection with the UE, wherein Information communication includes information and instructions for reasons. Data communication can be included in Msg3 from UE. The apparatus may include: a preamble signal part 1712 for receiving a random access preamble signal from the UE based on PRACH resources associated with early data transfer; and a RAR part 1714 for sending a random access response to UE, the random access response includes an uplink grant for early data transmission without restoring the RRC connection with the UE. The apparatus may include a core network component 1716, which is used to forward data to the core network without restoring the RRC connection with the UE. The apparatus may include a downlink data component 1718 for transmitting downlink data communication to the UE on the user plane without restoring the RRC connection with the UE. The apparatus may include a token component 1720 for authenticating the UE based on the authentication token included in the data communication.

The apparatus may include additional components for each of the blocks executing the algorithm in the flowcharts of FIGS. 5, 6, and 10 and 16 described above. Therefore, each block of the flowcharts of FIGS. 5, 6, and 10 and 16 described above may be executed by a component, and the device may include one or more of those components. The component may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, and stored in a computer-readable medium for Implemented by a processor, or some combination thereof.

18 is a diagram 1800 showing an example of a hardware implementation of a device 1702 'employing a processing system 1814. The processing system 1814 may be implemented using a busbar architecture (typically represented by the busbar 1824). The bus bar 1824 may include any number of interconnecting bus bars and bridges, depending on the specific application of the processing system 1814 and overall design constraints. Bus 1824 will include one or more processors and / or hardware components (by processor 1804, components 1704, 1706, 1708, 1710, 1712, 1714, 1716, 1718, 1720 and computer readable media / memory 1806 indicates) the various circuits are connected together. The bus bar 1824 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described again.

The processing system 1814 may be coupled to the transceiver 1810. The transceiver 1810 is coupled to one or more antennas 1820. The transceiver 1810 provides means for communicating with various other devices on the transmission medium. The transceiver 1810 receives signals from one or more antennas 1820, extracts information from the received signals, and provides the extracted information to the processing system 1814 (specifically, the receiving part 1704). In addition, the transceiver 1810 receives information from the processing system 1814 (specifically, the transmitting part 1706), and generates a signal to be applied to one or more antennas 1820 based on the received information. The processing system 1814 includes a processor 1804 coupled to a computer readable medium / memory 1806. The processor 1804 is responsible for general processing, including the execution of software stored on the computer readable medium / memory 1806. The software, when executed by the processor 1804, causes the processing system 1814 to perform the various functions described above for any particular device. The computer-readable medium / memory 1806 can also be used to store data manipulated by the processor 1804 when executing software. The processing system 1814 also includes at least one of components 1704, 1706, 1708, 1710, 1712, 1714, 1716, 1718, 1720. The component may be a software component running in the processor 1804, located / stored in the computer-readable medium / memory 1806, one or more hardware components coupled to the processor 1804, or some combination thereof. The processing system 1814 may be a component of the base station 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376.

In one configuration, the device 1702/1702 'for wireless communication includes: means for indicating resources in system information; for receiving data from the UE on the user plane without restoring RRC connection with the UE A component for communication, where the data communication includes data and cause indications; a component for receiving random access preamble signals from the UE based on PRACH resources associated with early data transmission; A component that forwards data to the core network in the case; and a component that is used to send downlink data communication to the UE on the user plane without restoring the RRC connection to the UE. The aforementioned component may be one or more of the aforementioned components of the device 1702 and / or the processing system 1814 of the device 1702 'configured to perform the functions recited by the aforementioned component. As previously mentioned, the processing system 1814 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions recited by the aforementioned components.

It should be understood that the specific order or hierarchy of blocks in the disclosed processes / flowcharts is merely illustrative of example methods. It should be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks may be merged or omitted. The attached method request items provide the elements of each block in a sampling order, but are not meant to be limited to the specific order or hierarchy provided.

The foregoing 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the scope of applying for a patent is not intended to be limited to what is shown in this document, but conforms to the entire scope consistent with the language of the scope of applying for a patent, wherein unless explicitly stated otherwise, the mention of elements in the singular form is not intended to mean "One and only one," but "one or more." The word "exemplary" as used herein means "as an example, instance, or illustration." Any aspect described herein as "exemplary" need not be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. 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" The combination of "multiple" and "A, B, C, or any combination thereof" includes any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, 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", "in A, B, and C" The combination of "one or more" 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 combination may include one or more members or several members in A, B, or C. All structural and functional equivalents that are known to those of ordinary skill in the art or that will later be known throughout the elements of the various aspects described in this disclosure are expressly incorporated herein by reference and intended Covered by the scope of patent application. In addition, none of the content disclosed in this article is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the scope of the patent application. The words "module", "mechanism", "element", "equipment", etc. may not be substitutes for the word "component". Therefore, no request element is to be interpreted as a component plus function, unless the element is explicitly described using the phrase "component for ..."

100‧‧‧Wireless communication system and access network

102‧‧‧ base station

102’‧‧‧small cells

104‧‧‧UE

110‧‧‧ Coverage area

110 ‘‧‧‧ coverage area

120‧‧‧Communication link

132‧‧‧backhaul link

150‧‧‧Wi-Fi access point (AP)

152‧‧‧Wi-Fi station (STA)

154‧‧‧Communication link

160‧‧‧Evolved Packet Core (EPC)

162‧‧‧ mobile management entity (MME)

164‧‧‧Other MME

166‧‧‧Service Gateway

168‧‧‧ Multimedia Broadcast Multicast Service (MBMS) Gateway

170‧‧‧ Broadcast Multicast Service Center (BM-SC)

172‧‧‧Packet Data Network (PDN) Gateway

174‧‧‧Home User Server (HSS)

176‧‧‧IP service

180‧‧‧gNodeB (gNB)

184‧‧‧beamforming

192‧‧‧Communication link

198‧‧‧ Send and receive data communication information without establishing RRC connection

200‧‧‧Picture

230‧‧‧Picture

250‧‧‧Picture

280‧‧‧Picture

310‧‧‧ base station

316‧‧‧Transmit (TX) processor

318‧‧‧ Launcher

320‧‧‧ Antenna

350‧‧‧UE

352‧‧‧ Antenna

354‧‧‧Receiver

356‧‧‧RX processor

358‧‧‧channel estimator

359‧‧‧Controller / processor

360‧‧‧Memory

368‧‧‧TX processor

370‧‧‧ Receive (RX) processor

374‧‧‧channel estimator

375‧‧‧Controller / processor

376‧‧‧Memory

400‧‧‧Picture

402‧‧‧Node

404‧‧‧UE

406‧‧‧UE

408‧‧‧UL transmission

410‧‧‧DL transmission

412‧‧‧DL transmission

414‧‧‧UL transmission

500‧‧‧Dial flow chart

501‧‧‧Idle

502‧‧‧UE

504‧‧‧ base station

506‧‧‧MME

508‧‧‧SGW

510‧‧‧ block

512‧‧‧SIB notice

514‧‧‧ block

516‧‧‧PRACH preamble signal

518‧‧‧RAR

520‧‧‧Message

522‧‧‧Message

524‧‧‧Message

526‧‧‧Message

528‧‧‧Message

530‧‧‧RRC idle state

600‧‧‧Dial flow chart

601‧‧‧Idle

602‧‧‧UE

604‧‧‧ base station

606‧‧‧MME

610‧‧‧ block

612‧‧‧SIB notice

614‧‧‧ block

616‧‧‧PRACH preamble signal

618‧‧‧RAR

622‧‧‧ block

624‧‧‧S1-AP: UE context recovery request

626‧‧‧Modify load

628‧‧‧S1-AP: UE context recovery response

630‧‧‧Message / Data

632‧‧‧S1 context release

634‧‧‧Message

638‧‧‧UE is in RRC_idle (suspended state)

700‧‧‧Flowchart

702‧‧‧ block

704‧‧‧ block

706‧‧‧ block

708‧‧‧ block

710‧‧‧ block

712‧‧‧ block

714‧‧‧ block

800‧‧‧Data flow chart

802‧‧‧device

802’‧‧‧ device

804‧‧‧Receiving parts

806‧‧‧Sending parts

808‧‧‧System Information Parts

810‧‧‧Data communication components

812‧‧‧RRC mode parts

814‧‧‧Indicating parts

816‧‧‧Preamble signal components

818‧‧‧RAR parts

820‧‧‧downlink data component

850‧‧‧ base station

900‧‧‧Picture

904‧‧‧ processor

906‧‧‧ Computer readable media / memory

910‧‧‧ transceiver

914‧‧‧ processing system

920‧‧‧ Antenna

924‧‧‧Bus

1000‧‧‧Flowchart

1002‧‧‧ block

1006‧‧‧ block

1008‧‧‧ block

1012‧‧‧ block

1014‧‧‧ block

1016‧‧‧ block

1100‧‧‧Data flow chart

1102‧‧‧ installation

1102‘‧‧‧ installation

1104‧‧‧Receiving parts

1106‧‧‧downlink components

1108‧‧‧SI parts

1110‧‧‧Data Communication Parts

1112‧‧‧Preamble signal components

1114‧‧‧RAR parts

1116‧‧‧Core network components

1118‧‧‧downlink data component

1150‧‧‧UE

1155‧‧‧Core network

1200‧‧‧Picture

1204‧‧‧ processor

1206‧‧‧ Computer readable media / memory

1210‧‧‧Transceiver

1214‧‧‧ processing system

1220‧‧‧ Antenna

1224‧‧‧Bus

1300‧‧‧Flowchart

1302‧‧‧ block

1304‧‧‧ block

1306‧‧‧ block

1308‧‧‧ block

1310‧‧‧ block

1312‧‧‧ block

1314‧‧‧ block

1400‧‧‧Data flow chart

1402‧‧‧ device

1402’‧‧‧ device

1404‧‧‧Receiving parts

1406‧‧‧Sending parts

1408‧‧‧System Information Parts

1410‧‧‧Data Communication Parts

1412‧‧‧ RRC mode parts

1414‧‧‧Indicating parts

1416‧‧‧Preamble signal components

1418‧‧‧RAR parts

1420‧‧‧downlink data component

1422‧‧‧ Symbol Parts

1450‧‧‧ base station

1500‧‧‧Picture

1504‧‧‧ processor

1506‧‧‧ Computer readable media / memory

1510‧‧‧Transceiver

1514‧‧‧ processing system

1520‧‧‧ Antenna

1524‧‧‧Bus

1600‧‧‧Flowchart

1602‧‧‧ block

1606‧‧‧ block

1608‧‧‧ block

1612‧‧‧ block

1614‧‧‧ block

1616‧‧‧ block

1700‧‧‧Data flow chart

1702‧‧‧ installation

1702’‧‧‧ installation

1704‧‧‧Receiving parts

1706‧‧‧downlink components

1708‧‧‧SI parts

1710‧‧‧Data Communication Parts

1712‧‧‧Preamble signal components

1714‧‧‧RAR parts

1716‧‧‧Core network components

1718‧‧‧downlink data component

1750‧‧‧UE

1755‧‧‧Core network

1800‧‧‧Picture

1804‧‧‧ processor

1806‧‧‧ Computer readable media / memory

1810‧‧‧Transceiver

1814‧‧‧ processing system

1820‧‧‧ Antenna

1824‧‧‧Bus

FIG. 1 is a diagram showing an example of a wireless communication system and an access network.

2A, 2B, 2C, and 2D are diagrams showing examples of a DL frame structure, a DL channel in a DL frame structure, a UL frame structure, and a UL channel in a UL frame structure, respectively.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE).

4 is a diagram showing an example communication system including a base station and a UE.

5 and 6 are example dialing flowcharts according to various aspects of the present disclosure.

7 is a flowchart of a method of wireless communication.

8 is a conceptual data flow diagram illustrating the data flow between different components / components in an example device.

FIG. 9 is a diagram showing an example of hardware implementation for a device employing a processing system.

10 is a flowchart of a method of wireless communication.

11 is a conceptual data flow diagram illustrating the data flow between different components / components in an example device.

FIG. 12 is a diagram showing an example of a hardware implementation for a device adopting a processing system.

13 is a flowchart of a method of wireless communication.

14 is a conceptual data flow diagram illustrating the data flow between different components / components in an example device.

FIG. 15 is a diagram showing an example of a hardware implementation manner for a device employing a processing system.

16 is a flowchart of a method of wireless communication.

17 is a conceptual data flow diagram illustrating the data flow between different components / components in an example device.

FIG. 18 is a diagram showing an example of a hardware implementation for a device adopting a processing system.

Domestic storage information (please note in order of storage institution, date, number) No

Overseas hosting information (please note in order of hosting country, institution, date, number) No

Claims (57)

A method for wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station, including the following steps: receiving system information from the base station; and In the case of establishing the RRC connection with the base station, a data communication is sent to the base station on a control plane, where the data communication includes data and a cause indication for the data communication. The method of claim 1, wherein the data communication is sent to the base station during a random access procedure. The method of claim 1, wherein the data communication further includes UE identity information. The method of claim 3, wherein the UE identity information includes a system architecture evolution TMSI (S-TMSI) for the UE. The method of claim 1, wherein the data communication is included in an RRC message indicating an intention to perform an RRC connectionless early data transmission. The method of claim 1, wherein the data communication is sent in a non-access layer (NAS) message on a shared control channel (CCCH). The method of claim 1, wherein the data communication is sent to the base station without the UE transitioning to an RRC connected state. The method of claim 1, wherein the data communication includes a single uplink data transmission. The method of claim 8, wherein a size of the data included in the single uplink data transmission is less than a size limit indicated by the base station. The method according to claim 1, further comprising the following steps: The UE selects an RRC connection mode for transmitting the data communication, wherein the RRC connection mode is an active RRC connection transmission mode or an RRC connectionless transmission mode . The method of claim 1, further comprising the steps of: sending an RRC mode indication regarding an RRC connection mode used to send the data communication to the base station. The method of claim 11, wherein the RRC mode indication includes a selection of a PRACH resource from a physical random access channel (PRACH) resource pool associated with an early data transmission. The method according to claim 12, wherein the PRACH resource includes a narrow-band PRACH (NPRACH). The method according to claim 1, further comprising the steps of: sending a random access preamble signal to the base station; and receiving an authorization for an uplink transmission without establishing the RRC connection, The data communication is sent to the base station based on the authorization. The method of claim 1, wherein the system information is broadcast from the base station and indicates a physical random access channel associated with an early data transmission in the case where the UE has not transitioned to an RRC connected state (PRACH) resources. The method of claim 15, wherein the UE selects a resource based at least in part on a data volume to be sent in the data communication. The method according to claim 1, further comprising the steps of: receiving downlink data communication from the base station on the control plane without establishing the RRC connection with the base station. The method of claim 17, wherein the downlink data communication is received in an RRC message indicating the completion of an early data transfer. An apparatus for wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station, including: means for receiving system information from the base station; and A component used by the UE to send a data communication to the base station on a control plane without establishing the RRC connection with the base station, where the data communication includes data and a reason for the data communication Instructions. The apparatus of claim 19, wherein the data communication is sent to the base station during a random access procedure. The apparatus according to claim 19, further comprising: means for the UE to select an RRC connection mode for transmitting the data communication, wherein the RRC connection mode is an active RRC connection transmission mode or an RRC connectionless Transmission mode. The apparatus according to claim 19, further comprising: means for sending an RRC mode indication regarding an RRC connection mode used for sending the data communication to the base station. The apparatus of claim 19, further comprising: means for sending a random access preamble signal to the base station; and for receiving an uplink transmission for the case where the RRC connection is not established An authorized component of which the data communication is sent to the base station based on the authorization. The apparatus according to claim 19, further comprising: means for receiving downlink data communication from the base station on the control plane without establishing the RRC connection with the base station. An apparatus for wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station includes: a memory; and at least one processor, which is coupled to The memory is also configured to: receive system information from the base station; and the UE sends a data communication to the base station on a control plane without establishing the RRC connection with the base station, wherein The data communication includes data and an indication of a reason for the data communication. The apparatus of claim 25, wherein the data communication is sent to the base station during a random access procedure. The apparatus of claim 25, wherein the at least one processor is further configured to: select, by the UE, an RRC connection mode for transmitting the data communication, wherein the RRC connection mode is an active RRC connection transmission mode or An RRC connectionless transmission mode. The apparatus of claim 25, wherein the at least one processor is further configured to: send an RRC mode indication regarding an RRC connection mode used to transmit the data communication to the base station. The apparatus of claim 25, wherein the at least one processor is further configured to: send a random access preamble signal to the base station; and receive an uplink for when the RRC connection is not established An authorization for road transmission, in which the data communication is sent to the base station based on the authorization. The apparatus of claim 25, wherein the at least one processor is further configured to: receive downlink data from the base station on the control plane without establishing the RRC connection with the base station communication. A computer-readable medium storing computer-executable code for wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station, including for performing the following Operation code: receive system information from the base station; and the UE sends a data communication to the base station on a control plane without establishing the RRC connection with the base station, where the data communication includes Information and an indication of a reason for the communication of the information. The computer-readable medium of claim 31, wherein the data communication is sent to the base station during a random access procedure. A method for wireless communication by a base station without a radio resource control (RRC) connection to a user equipment (UE) includes the following steps: indicating resources in system information; In the case of the RRC connection of the UE, a data communication is received from the UE on a control plane, where the data communication includes data and a cause indication. The method of claim 33, wherein the data communication is received from the UE during a random access procedure. The method of claim 33, wherein the data communication is included in an Msg3 from the UE. The method of claim 33, wherein the data communication further includes UE identity information, and wherein the UE identity information includes a system architecture evolution TMSI (S-TMSI) for the UE. The method of claim 33, wherein the data communication is included in an RRC message, and the cause indication is used to indicate an intention to perform an RRC connectionless early data transmission. The method of claim 33, wherein the data communication is received in a non-access stratum (NAS) message on a shared control channel (CCCH). The method of claim 33, wherein the data communication is received from the UE without establishing an RRC connection state with the UE and forwarded to a core network component. The method of claim 33, wherein the data communication includes a single uplink data transmission. The method of claim 33, wherein the resources indicated in the system information include physical random access channel (PRACH) resources associated with an early data transmission. The method according to claim 41, wherein the PRACH resources include a narrow-band PRACH (NPRACH). The method of claim 42, wherein different NPRACH resources are associated with different coverage enhancement levels. The method of claim 41, further comprising the steps of: receiving a random access preamble signal from the UE based on the PRACH resources associated with the early data transmission. The method of claim 44, further comprising the steps of: sending a random access response to the UE, the random access response including for the early data transmission without establishing the RRC connection with the UE An uplink grant, where the data communication is received from the UE based on the uplink grant. The method of claim 33, wherein the data includes a non-access layer (NAS) protocol data unit (PDU) received on the control plane. The method according to claim 33, further comprising the steps of: forwarding the data to a core network without establishing the RRC connection with the UE. The method according to claim 33, further comprising the following steps: When the RRC connection with the UE is not established, the downlink data communication is sent to the UE on the control plane. The method of claim 48, wherein the downlink data communication is sent in an RRC message indicating the completion of an early data transmission. An apparatus for wireless communication by a base station without a radio resource control (RRC) connection to a user equipment (UE), including: means for indicating resources in system information; and In the case where the RRC connection with the UE is not established, a component that receives a data communication from the UE on a control plane, where the data communication includes data and a cause indication. The apparatus according to claim 50, further comprising: means for forwarding the data to a core network without establishing the RRC connection with the UE. An apparatus for wireless communication by a base station without a radio resource control (RRC) connection to a user equipment (UE) includes: a memory; and at least one processor, which is coupled to The memory is also configured to: indicate resources in system information; and receive the data communication from the UE on a control plane without establishing the RRC connection with the UE, where the data communication includes data and A reason indication. The apparatus of claim 52, wherein the resources indicated in the system information include physical random access channel (PRACH) resources associated with an early data transmission, wherein the at least one processor is further configured to: Based on the PRACH resources associated with the early data transmission, a random access preamble signal is received from the UE. The apparatus according to claim 53, wherein the at least one processor is further configured to: send a random access response to the UE, the random access response includes when the RRC connection with the UE is not established An uplink grant for the early data transmission, where the data communication is received from the UE based on the uplink grant. The apparatus of claim 52, wherein the at least one processor is further configured to: forward the data to a core network without establishing the RRC connection with the UE. The apparatus according to claim 52, wherein the at least one processor is further configured to: send downlink data communication to the UE on the control plane without establishing the RRC connection with the UE . A computer readable medium storing computer executable code for wireless communication by a base station without radio resource control (RRC) connection to a user equipment (UE), including for performing the following Codes of operation: indicate resources in the system information; and receive the data communication from the UE on a control plane without establishing the RRC connection with the UE, where the data communication includes data and a cause indication.