EP3666025A1 - Methods and apparatuses for uplink early data transmission - Google Patents

Methods and apparatuses for uplink early data transmission

Info

Publication number
EP3666025A1
EP3666025A1 EP18746366.6A EP18746366A EP3666025A1 EP 3666025 A1 EP3666025 A1 EP 3666025A1 EP 18746366 A EP18746366 A EP 18746366A EP 3666025 A1 EP3666025 A1 EP 3666025A1
Authority
EP
European Patent Office
Prior art keywords
base station
data communication
data
rrc
rrc connection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP18746366.6A
Other languages
German (de)
English (en)
French (fr)
Inventor
Umesh PHUYAL
Mungal Singh Dhanda
Alberto Rico Alvarino
Miguel Griot
Luis Fernando Brisson Lopes
Sebastian Speicher
Haris Zisimopoulos
Peter Gaal
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/964,523 external-priority patent/US20180324854A1/en
Priority claimed from US16/024,421 external-priority patent/US20180324869A1/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3666025A1 publication Critical patent/EP3666025A1/en
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to early uplink data transmission for enhanced machine-type- communication (eMTC) and Internet of Things (IoT) communication.
  • eMTC enhanced machine-type- communication
  • IoT Internet of Things
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with IoT), and other requirements.
  • 3GPP Third Generation Partnership Project
  • 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • a Machine-type-communication generally refers to communications that are characterized by automatic data generation, exchange, processing, and actuation among machines with little or no human intervention.
  • the IoT is the inter-networking of physical devices, vehicles (sometimes referred to as “connected devices” and/or “smart devices”), buildings, and other items that may be embedded with electronics, software, sensors, actuators, and network connectivity that enable these objects to collect and exchange data and other information.
  • Many MTC and IoT applications may involve relatively infrequent exchange of small amounts of data (e.g., one uplink packet). For example, metering, alarms and etc. are expected to produce a small amount uplink (UL) data. Similarly, queries, notifications of an update, and commands to actuators, for example, generate small downlink (DL) data transmissions.
  • DL downlink
  • RRC radio resource control
  • MTC or IoT applications there may be a significant expenditure of resources for a small data transmission (e.g. 1 uplink packet or 1 medium access control (MAC) Block). Therefore, it is desirable to minimize the amount of resources used in MTC and IoT communication.
  • aspects of the present disclosure are directed to reducing the overhead for setting up or resuming an RRC connection in order to transmit small data transmissions.
  • MAC medium access control
  • numerous communication steps are performed by the UE and/or a base station to establish an RRC connection or resume an RRC connection before data may be transmitted.
  • additional steps are performed to release the RRC connection.
  • aspects of the present disclosure provide for data transmission (e.g., uplink data transmission) from a UE having an RRC connection in an idle state or a suspended state, without transitioning to an RRC connected state.
  • the data transmission without performing an RRC establishment process, or without resuming an RRC connection may be referred to as early data transmission (EDT) or data transmission in an RRC connectionless mode.
  • a method, a computer readable medium, and an apparatus are provided for wireless communication at a User Equipment (UE).
  • the apparatus includes a memory and one or more processors coupled to the memory.
  • the apparatus receives system information from a base station and transmits a data communication to the base station over a control plane without establishing an RRC connection with the base station, wherein the data communication comprises data and at least one of UE identity information and a cause indication.
  • a method, a computer readable medium, and an apparatus are provided for wireless communication at a base station.
  • the apparatus includes a memory and one or more processors coupled to the memory.
  • the apparatus indicates resources in system information and receives a data communication from a UE over a control plane without establishing an RRC connection with the UE, wherein the data communication comprises data and at least one of UE identity information and a cause indication.
  • a method, a computer readable medium, and an apparatus are provided for wireless communication at a UE, e.g., in an RRC suspended state.
  • the apparatus includes a memory and one or more processors coupled to the memory.
  • the apparatus receives system information from a base station and transmits a data communication to the base station over a user plane without resuming an RRC connection with the base station, wherein the data communication comprises data and at least one of UE identity information and a cause indication.
  • a method, a computer readable medium, and an apparatus are provided for wireless communication at a base station.
  • the apparatus includes a memory and one or more processors coupled to the memory.
  • the apparatus indicates resources in system information and receives a data communication from a UE over a user plane without resuming an RRC connection with the UE, wherein the data communication comprises data and at least one of UE identity information and a cause indication.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
  • FIGs. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a DL frame structure
  • FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE).
  • UE user equipment
  • FIG. 4 is a diagram illustrating an example communication system comprising a base station and UEs.
  • FIGS. 5 and 6 are example call flow diagrams in accordance with aspects of the present disclosure.
  • FIG 7 is a flowchart of a method of wireless communication.
  • FIG. 8 is a conceptual data flow diagram illustrating the data flow between different means/components in an example apparatus.
  • FIG. 9 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • FIG. 10 is a flowchart of a method of wireless communication.
  • FIG. 11 is a conceptual data flow diagram illustrating the data flow between different means/components in an example apparatus.
  • FIG. 12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • FIG. 13 is a flowchart of a method of wireless communication.
  • FIG. 14 is a conceptual data flow diagram illustrating the data flow between different means/components in an example apparatus.
  • FIG. 15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • FIG. 16 is a flowchart of a method of wireless communication.
  • FIG. 17 is a conceptual data flow diagram illustrating the data flow between different means/components in an example apparatus.
  • FIG. 18 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • aspects of the present disclosure are directed to MTC and /or IoT communications, in which the UE is in an Idle mode or suspend mode at the time when a data transmission is initiated.
  • conventional techniques perform a full Radio Resource Control Connection establishment procedure prior to the data transmission.
  • Full Radio Resource Control (RRC) Connection establishment procedure for Idle user equipments (UEs) involves a random access (RA) procedure.
  • the RA procedure may be used to initiate a data transfer but has a large overhead cost and latency.
  • the RA procedure may include a sequence of messages including Msgl (physical random access channel PRACH preamble), Msg2 (random access request (RAR)), Msg3 (RRC Connection Request, RRC Connection Re-establishment Request, RRC Connection Resume Request or the like depending on the reason for RA procedure), Msg4 (early contention resolution, RRC Connection Setup etc.), and finally Msg5 which can be used for the UL data (unless SR/BSR is required before actual payload transmission). This involves 5 or more messages for UL data before actual payload transmission. This is a large overhead for applications that transmit uplink data that fits into one transport block size (TBS).
  • TBS transport block size
  • a DL/UL transmission may be performed.
  • conventional approaches perform a large number of message exchanges before the actual payload transmission, even for very small and/or infrequent payload.
  • aspects of the present disclosure provide for early uplink data transmission and other enhancements for MTC and/or IoT communications. That is, rather than scheduling the first UL data transmission in Msg 5 or later, as in conventional techniques, the data transmission in the UL may transit data (e.g., payload) in Msgl or Msg3, for example.
  • the enhancements may be applicable to control plane (CP)/User plane (UP) Cellular IoT Evolved Packet Systems.
  • the data transmission information may be included in Msg3 and transmitted to a base station (e.g., an eNodeB).
  • a data transmission may refer to user data.
  • the transmission of Msg3 may be performed on an initial UL grant provided by a random access request (RAR).
  • RAR random access request
  • the Msg3 may also convey a Non- Access Stratum (NAS) UE identifier for initial access, without a NAS message (e.g., mobility management message).
  • Msg3 transmission may be performed using a separate Msg3 buffer, which may have a higher priority than the UL buffer.
  • Msg3 may use Hybrid Automatic Repeat Requests (HARQ).
  • HARQ Hybrid Automatic Repeat Requests
  • the UE Medium Access Control (MAC) layer includes a HARQ entity and may retransmit a message in case the UE does not receive MAC layer response from the base station. For example, if the UE does not receive Msg4, which could lead to contention resolution failure, the UE (MAC) layer can re-attempt access from an idle state.
  • the RA procedure may be enhanced to support UL data transmission in Msg3.
  • the payload e.g., service data unit (SDU)
  • SDU Common Control Channel
  • CCCH Common Control Channel
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WW AN)) includes base stations 102, UEs 104, and an Evolved Packet Core (EPC) 160.
  • the base stations 102 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station).
  • the macro cells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the base stations 102 (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN)) interface with the EPC 160 through backhaul links 132 (e.g., S I interface).
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages.
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160) with each other over backhaul links 134 (e.g., X2 interface).
  • the backhaul links 134 may
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 1 10. There may be overlapping geographic coverage areas 1 10. For example, the small cell 102' may have a coverage area 1 10' that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macro cells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).
  • eNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include UL (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or DL (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple- output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • MIMO multiple-input and multiple- output
  • the communication links may be through one or more carriers.
  • the base stations 102 / UEs 104 may use spectrum up to y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.
  • the carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
  • PCell primary cell
  • SCell secondary cell
  • D2D communication link 192 may use the DL/UL WW AN spectrum.
  • the D2D communication link 192 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
  • the wireless communications system may further include a Wi-Fi access point (AP)
  • AP Wi-Fi access point
  • the STAs 152 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • STAs Wi-Fi stations
  • the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • the gNodeB (gNB) 180 may operate in millimeter wave (mmW) frequencies and/or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station.
  • mmW millimeter wave
  • EHF Extremely high frequency
  • EHF Extremely high frequency
  • Radio waves in the band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 184 with the UE 104 to compensate for the extremely high path loss and short range.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a display, or any other similar functioning device.
  • Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.).
  • the UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • the UE 104 / base station 180 may be respectively configured to send and receive data communication information without establishing a RRC connection (198).
  • FIG. 2A is a diagram 200 illustrating an example of a DL frame structure.
  • FIG. 2B is a diagram 230 illustrating an example of channels within the DL frame structure.
  • FIG. 2C is a diagram 250 illustrating an example of an UL frame structure.
  • FIG. 2D is a diagram 280 illustrating an example of channels within the UL frame structure.
  • Other wireless communication technologies may have a different frame structure and/or different channels.
  • a frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include two consecutive time slots.
  • a resource grid may be used to represent the two time slots, each time slot including one or more time concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)).
  • RBs time concurrent resource blocks
  • the resource grid is divided into multiple resource elements (REs).
  • REs resource elements
  • an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of 84 REs.
  • an RB may contain 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.
  • some of the REs carry DL reference (pilot) signals (DL- RS) for channel estimation at the UE.
  • DL- RS DL reference (pilot) signals
  • the DL-RS may include cell-specific reference signals (CRS) (also sometimes called common RS), UE-specific reference signals (UE-RS), and channel state information reference signals (CSI-RS).
  • CRS cell-specific reference signals
  • UE-RS UE-specific reference signals
  • CSI-RS channel state information reference signals
  • FIG. 2A illustrates CRS for antenna ports 0, 1, 2, and 3 (indicated as Ro, Ri, R2, and R3, respectively), UE-RS for antenna port 5 (indicated as R5), and CSI-RS for antenna port 15 (indicated as R).
  • FIG. 2B illustrates an example of various channels within a DL subframe of a frame.
  • the physical control format indicator channel (PCFICH) is within symbol 0 of slot 0, and carries a control format indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies 1, 2, or 3 symbols (FIG. 2B illustrates a PDCCH that occupies 3 symbols).
  • the PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol.
  • DCI downlink control information
  • CCEs control channel elements
  • Each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol.
  • a 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 shows two RB pairs, each subset including one RB pair).
  • the physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also within symbol 0 of slot 0 and carries the HARQ indicator (HI) that indicates HARQ acknowledgement (ACK) / negative ACK (NACK) feedback based on the physical uplink shared channel (PUSCH).
  • the primary synchronization channel (PSCH) may be within symbol 6 of slot 0 within subframes 0 and 5 of a frame.
  • the PSCH carries a primary synchronization signal (PSS) that is used by a UE 104 to determine subframe/symbol timing and a physical layer identity.
  • the secondary synchronization channel (SSCH) may be within symbol 5 of slot 0 within subframes 0 and 5 of a frame.
  • the SSCH carries a secondary synchronization signal (SSS) that is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DL-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB), may be logically grouped with the PSCH and SSCH to form a synchronization signal (SS) block.
  • the MIB provides a number of RBs in the DL system bandwidth, a PHICH configuration, and a system frame number (SFN).
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.
  • SIBs system information blocks
  • some of the REs carry demodulation reference signals (DM- RS) for channel estimation at the base station.
  • the UE may additionally transmit sounding reference signals (SRS) in the last symbol of a subframe.
  • SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency- dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various channels within an UL subframe of a frame.
  • a physical random access channel may be within one or more subframes within a frame based on the PRACH configuration.
  • the PRACH may include six consecutive RB pairs within a subframe.
  • the PRACH allows the UE to perform initial system access and achieve UL synchronization.
  • a physical uplink control channel may be located on edges of the UL system bandwidth.
  • the PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK/NACK feedback.
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network.
  • IP packets from the EPC 160 may be provided to a controller/processor 375.
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction
  • the transmit (TX) processor 316 and the receive (RX) processor 370 implement layer
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)).
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX.
  • Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354RX receives a signal through its respective antenna
  • Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT).
  • FFT Fast Fourier Transform
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160.
  • the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with header compression
  • Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318RX receives a signal through its respective antenna 320.
  • Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
  • the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160.
  • the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • one or both of the base station 310 and the UE 350 may have logic, software, firmware, configuration files, etc., to allow the MCT/IoT communications described herein.
  • FIG. 4 is a diagram 400 illustrating a communication system in accordance with various aspects of the present disclosure.
  • FIG. 4 includes a node 402 and multiple UEs 404, 406.
  • UE 404 may comprise an MTC UE, IoT UE, a Bandwidth reduced Low complexity (BL) UE, etc.
  • UE 406 may also comprise an MTC UE, IoT UE, or BL UE, or UE 406 may communicate with the base station in a manner different than MTC, IoT, BL.
  • the node 402 can be a macro node (e.g., a base station), femto node, pico node, or similar base station, a mobile base station, a relay, a UE (e.g., communicating in peer-to-peer or ad-hoc mode with another UE), a portion thereof, and/or substantially any component that communicates control data in a wireless network.
  • the UE 404 and UE 406 can each be a mobile terminal, a stationary terminal, a modem (or other tethered device), a portion thereof, and/or substantially any device that receives control data in a wireless network.
  • the UE 404 receives DL transmissions 410 from base station 402 and sends UL transmissions 408 to the base station 402.
  • the DL and UL transmissions 410 and 408 may include either MTC/IoT/BL control information or MTC/IoT/BL data.
  • the UE 406 receives DL transmissions 412 from base station 402 and sends UL transmissions 414 to the base station 402.
  • the communication between UE 404 and base station 402 may include, e.g., cellular IoT (CIoT) Evolved Packet System (EPS) optimization procedures that include early data transmission during a Random Access procedure without transitioning to an RRC connected state.
  • the early data transmission may comprise UL and/or DL data.
  • FIG. 5 is an example call flow diagram 500 in accordance with aspects of the present disclosure.
  • the call flow diagram 500 illustrates communication between a UE 502, a base station 504, a MME 506, and a SGW 508.
  • the UE 502 may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE.
  • the UE 502 may be in an idle state 501 (e.g., RRC Idle).
  • a resource determination may be made by base station 504.
  • the base station determines the resources to be used by UE 502 for PRACH attempts.
  • the PRACH resources determined at 510 may comprise PRACH resources associated with early data transmission, e.g., PRACH resources allocated for early data transfer without establishing an RRC connection.
  • base station may allow transmission of small data packet sizes (e.g., 10 bytes to 50 bytes) without establishing a full RRC connection.
  • the early data transmission may comprise a single data packet.
  • the PRACH resources associated with early data transmission may be different than those allocated by the base station for data transmission after an RRC connection establishment. Additionally, the allocated PRACH resources may be different for different coverage enhancement (CE) levels.
  • CE coverage enhancement
  • the UE may select from a PRACH resource set associated with early data transfer for a selected enhanced coverage level.
  • the enhanced early data transmission (Tx) mode may include transmission of data in
  • Msgl e.g., transmission with a RACH preamble
  • Msg3 e.g., transmission following a RAR
  • other data transmission modes may require the data to be transmitted after RRC connection establishment
  • the base station 504 may announce the allocated PRACH resources via a system information broadcast (SIB) (512).
  • SIB system information broadcast
  • the SIB may indicate separate PRACH resources for early data transmission, e.g., data transfer prior to or without an RRC connection establishment.
  • the SIB announcement may also indicate the transport block size (TBS) that can be used for early data transmission, which may be used by the UE to make determination of whether to use the early data transmission.
  • TBS transport block size
  • the UE 502 selects a PRACH/NPRACH resource based on the announced resources in the SIB and the amount of data to be transmitted. In some aspects, the resource selection may be based on a random selection from the corresponding PRACH pool or a dedicated allocation.
  • the UE may indicate an intention to perform an early data transfer to the network (e.g., base station 504) through the UE's selection of the PRACH/NPRACH resources. For example, the UE may select the PRACH resources from the separate pool allocated for enhanced early data transmission when the UE intends to transmit the data prior to/without establishing an RRC connection with the base station. The UE may determine whether to transmit the data using the enhanced early data transmission based on the amount of data to be transmitted to the base station. For example, when the UE has a single uplink packet to transmit to the base station which can be fit into a single MAC block transmission based on the SIB announcement of TBS size, the UE may select from among the PRACH resources allocated for early data transmission.
  • the network e.g., base station 504
  • the UE may select the PRACH resources from the separate pool allocated for enhanced early data transmission when the UE intends to transmit the data prior to/without establishing an RRC connection with the base station.
  • the UE may determine whether to transmit the data
  • the UE may select from among the other PRACH resources.
  • the UE may determine whether to perform early data transmission based on a number of bytes of data to be transmitted upon comparison with the information provided in the SIB.
  • the size may be limited to a single MAC block, for example. For example, when the number of bytes is less than 50 bytes, the UE may select from among the PRACH resources allocated for early data transmission. Otherwise, the UE may select from among the other PRACH resources.
  • the selection of the PRACH resources may be based on the amount of data to be transmitted.
  • the UE 502 transmits a PRACH preamble 516 using the selected PRACH/NPRACH resources, as a first communication message to the base station 504 (516).
  • the PRACH preamble may be referred to as Msgl, in an example.
  • the PRACH/NPRACH preamble selected by the UE may be based on the PRACH resources associated with early data transmission.
  • the UE may include data in this first transmission to the base station.
  • the Msgl may comprise, optionally a PRACH preamble, and a NAS PDU.
  • the base station 504 sends a RA response (RAR) to the UE (at 518) in the second communication message, including an uplink grant for the UE to perform the early data transmission.
  • the RAR may be referred to as Msg2, in an example.
  • the RAR may contain an uplink grant for transmission of RRC connection establishment/reestablishment/resume message.
  • the RAR may also include a timing advance (TA) (in addition to Temporary C-RNTI etc.).
  • TA timing advance
  • the RAR 518 may include uplink grant for early data transmission in addition to, one or more of timing advance, temporary C-RNTI, power control information etc. If the power control information is not included, alternatively, the UE 502 may use open-loop power control in which the UE determines the transmit power.
  • the UE 502 may transmit the data to base station using an initial UL grant indicated in the RAR 518.
  • the message may be referred to as an RRC Early Data Request message.
  • the message may be referred to as an RRC Connectionless Request.
  • the payload may be included in the message 520 on CCCH, e.g., as a CCCH SDU.
  • the data may be transmitted as a NAS protocol data unit (PDU) over the control plane.
  • PDU NAS protocol data unit
  • the transmission at 520 is performed during the random access procedure and without establishing an RRC connection.
  • the transmission 520 is illustrated as the third communication message to the base station 504, and may be referred to as Msg3.
  • the transmission 520 may further comprise a UE identification (UEID).
  • UEID UE identification
  • the UEID may comprise a temporary mobile subscriber identity (e.g., a System Architecture Evolution TMSI (S-TMSI)).
  • S-TMSI System Architecture Evolution TMSI
  • the UEID may comprise a Resume ID.
  • the message 520 may also include an indication of a cause.
  • the cause may indicate an RRC connectionless mode.
  • the cause may be referred to as a "cause code,” and a code included in the message may indicate whether the message 520 comprises data for transmission in an RRC connectionless mode.
  • the indication of the cause may also be referred to as an 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 a contention resolution timer after this step.
  • the contention resolution timer may be implemented using the controller/processor 359 in the example UE 350 of FIG. 3.
  • the contention resolution timer value for early data transmission may be different compared to the contention resolution timer value for the communication that requires an RRC connection to be established prior to data transmission.
  • the message 520 may comprise data stored in a separate early data transmission buffer, e.g., which may be referred to as a Msg3 buffer. This buffer may have a higher priority than an UL buffer for transmission after an RRC connection.
  • the message 520 may further include an indication regarding the RRC connectionless early UL data transmission. The indication may enable the base station 504 to differentiate a UE requesting the early data transmission before or after RRC connection establishment. As a result, the base station 504 may provide an additional message comprising a fast UL grant for connectionless UL transmission (e.g., providing an UL grant to the UE without the UE transitioning to RRC connected state). The UE may then respond with the data transfer without transitioning to the RRC connected state.
  • the message 520 may include the NAS PDU, as well as an indication that further UL data is pending at the UE.
  • the base station may respond to the message by providing further UL grants for transmission using the RRC connectionless mode.
  • the base station selects the MME 506 based on the UE identifying information (e.g., S-TMSI) in the message 520 and forwards the NAS PDU to the MME 506.
  • the base station 504 may also provide MME 506 an indication that there is only one uplink NAS PDU. This may be done, for example, by including a cause code (e.g., "RRC Connectionless Mode") in the message 522 to the MME.
  • a cause code e.g., "RRC Connectionless Mode
  • the SGW 508 provides the DL data to the MME 506, which forwards the DL data as NAS PDU to the base station 504 to be delivered to 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 SI application protocol (Sl-AP) connection after forwarding any downlink NAS PDU. As illustrated, the message 524 may comprise the DL NAS PDU and the release command. Further, the base station indication of one UL NAS PDU may also be used by MME 506 to prioritize processing of the UL data and expedite or prioritize the transmission of DL data by SGW 508 to the MME 506.
  • SI application protocol SI application protocol
  • the base station 504 may transmit a message confirming reception of the data in message 520.
  • the message 526 may be called an RRC Early Data Complete message.
  • the message may be called an RRC Connectionless Confirm message.
  • This message may comprise a fourth message between the UE and base station and may be referred to as Msg4, in some examples. If a UE 502 receives message 526, it may consider the early data transmission to be successfully completed and consider the contention is resolved.
  • the message 526 may include a DL NAS PDU. If NAS PDU is included, the NAS may confirm that it is communicating with a valid network. If DL data is included in message 526, the UE may respond with HARQ 528 to include reception of the DL data.
  • the UE may retransmit the message 520 if the UE does not receive a response, e.g., a MAC level response, from the base station.
  • a response e.g., a MAC level response
  • the failure to receive a response within the contention resolution timer indicates a contention resolution failure leading the UE to re-attempt access from the idle state.
  • the message 526 may merely provide a confirmation that the UL data was received.
  • the UE may continue in an RRC idle state 530.
  • the UL data may be transmitted, e.g., at 516 or 520 during the random access procedure, without establishing an RRC connection and without the UE transitioning to an RRC connected state.
  • message 524 may be missing (e.g., the base station sends data to
  • the base station 504 may, for example, start a timer after message 522. Upon the expiration of the timer, the base station 504 may proceed to message 526 with a positive ACK of successful reception of message 520. In another example, the base station 504 may start a timer after message 522. Upon the expiration of such timer, the base station 504 may proceeds to message 526 with a positive ACK of successful reception of the message 520 with a further indication that the base station 504 has failed to receive an ACK from MME 506. In this example, the absence of the NAS PDU in message 524 may be indicated to upper layers of the protocol stack by the UE 502. The UE returns to idle, at 530.
  • the MME 506 instead of or in addition to confirming the reception of NAS PDU from the base station 504, may indicate that the UE 502 is to transition to RRC connected state from idle state instead of completing the RRC connectionless transmission session.
  • Sl-AP may not be closed immediately and the base station in message 526 may send an indication to the UE 502 to transition to RRC connected state (e.g., RRC Connection Setup).
  • FIG. 6 is an example call flow diagram 600 in accordance with aspects of the present disclosure.
  • the call flow diagram 600 illustrates communication between a UE 602, a base station 604, a MME 606, and a SGW 608.
  • the UE 602 may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE.
  • the UE 602 may be in an idle state 601 (e.g., an RRC suspended state).
  • a resource determination may be made by the base station. The determination may be similar to that described in connection with 510 in FIG. 5.
  • base station 604 may allow transmission of small data packet sizes (e.g., 10 bytes to 50 bytes) without establishing a full RRC connection, e.g., during random access without the UE transitioning from the RRC suspended state to an RRC connected state.
  • the data transmission in FIG. 6 may be performed over a user plane, whereas the data transmission in FIG. 5 may be performed over a control plane.
  • the base station may determine the resources to be used by UE 602 for PRACH attempts.
  • the base station 604 may allocate PRACH resources for this purpose.
  • the PRACH resources determined at 610 may comprise PRACH resources associated with enhanced early data transmission, e.g., PRACH resources allocated for data transfer prior to or without an RRC connection establishment.
  • the PRACH resources allocated for early data transmission may be different than those allocated by the base station for data transmission after an RRC connection establishment. Additionally, the allocated PRACH resources may be different for different CE levels.
  • the UE may select from a PRACH resource set associated with early data transfer for a selected enhanced coverage level.
  • the enhanced early data transmission may include transmission of data in Msgl (e.g., with a RACH preamble) or in Msg3 (e.g., a transmission following a RAR)rather than being transmitted after completion of RRC connection resume.
  • the UE may indicate an intention to perform an early data transmission without resumption of RRC connection to the network (e.g., base station 604) by selecting the PRACH/NPRACH resources from a separate pool allocated for such RRC connectionless early data transfer.
  • the base station 604 may announce the pool of resources via a system information broadcast (SIB) (612).
  • SIB system information broadcast
  • the UE 602 selects a PRACH/NPRACH resource based on the announced resources in the SIB and the amount of data to be transmitted. For example, if the size of the data to be transmitted meets a size limit received from the base station, then the UE may select a PRACH/NPRACH resource from the pool associated with early data transfer. As described in connection with the example in FIG. 5, the UE may determine whether to transmit the uplink data using an RRC connectionless early data transmission based on the amount of data to be transmitted. Thus, if the size of the data is beyond the limit, then the UE may select different PRACH/NPRACH resources for performing random access. In some aspects, the resource selection may be based on a random selection from the corresponding PRACH pool or a dedicated allocation.
  • the UE 602 transmits the selected PRACH/NPRACH preamble in a first communication message to the base station 604 (616).
  • the first communication message may be referred to as Msgl , and may initiate an early data transmission.
  • the PRACH/NPRACH preamble selected by the UE may be based on the PRACH resources associated with early data transmission. In one example, data for early transmission may be included in this first message to the base station.
  • the base station 604 sends an RAR to the UE (at 618) in a second communication message (e.g., that may be referred to as Msg2).
  • the RAR may contain an uplink grant for early data transmission.
  • the RAR may also include timing advance (in addition to Temporary C-RNTI etc.).
  • the RAR may also include power control information.
  • the UE 502 may use open-loop power control (e.g., the UE decides on the transmit power).
  • the UE 602 may transmit data to the base station based on the uplink grant indicated in the RAR 618.
  • the data may be included in the message 620 on CCCH.
  • the message 620 may be a third communication message to the base station and may be referred to as Msg3.
  • the data may be transmitted as a data PDU over the user plane.
  • the transmission at 620 may be performed during the random access procedure and without resuming previously suspended RRC connection.
  • the message 620 may include a UE identifier. As the UE is in an RRC suspended state 601, the UE identifier may include the UE's resume ID.
  • Msg3 may comprise of a message similar to an RRCConnectionResumeRequest comprising the UE's Resume ID and including application data.
  • the message may also indicate a cause, e.g., indicating early data transmission as a cause for the message. This indication of the cause may be referred to as a "resume cause" or an "establishment cause.” For example, only a subset of the cause values may be applicable for early data transmission.
  • a new resume cause value may be defined for the early transmission of data in message 620. If this new cause value is signaled, the base station may forward the data to the MME 606 without resuming RRC.
  • a new message may be defined to carry a combination of unciphered and ciphered payload.
  • the UE 602 may apply security to data PDU carried by message 620.
  • the message 620 may also include an authentication token.
  • FIG. 6 illustrates the message including an example authentication token called shortResumeMAC-I.
  • the authentication token may also be referred to by other names. Integrity may also be applied to the entire message 620.
  • the UE 602 While being in RRC suspended state, stores security keys to use for integrity which can be resumed to be used. In some aspects, the UE 602 may also have stored keys for ciphering. Thus, user data both on the uplink and the downlink may be ciphered.
  • the UE 602 may be provided with a NextHopChainingCount as well as resumelD during suspension, e.g., at 601 from previous session or in 634 of current session to be used for next session.
  • a copy of the PDU (e.g. data) may be left in the PDCP stack for possible repeat transmission attempts in the event of a transmission failure of message 620.
  • the UE 602 may also use security parameters based (at 620) on the
  • the UE 602 may cipher data PDU and compute an integrity key (e.g., over entire RRC Connectionless Resume Request message).
  • an integrity key e.g., over entire RRC Connectionless Resume Request message.
  • the eNodeB base key (KeNB) integrity key for RRC signaling (KRRCint), encryption key for RRC (KRRCenc) or other security parameters may be used for MAC calculation and optional ciphering, for example.
  • the security parameters may be based on information previously provided to the UE, e.g., during the previous suspension.
  • the resumelD, resumeCause and shortResumeMAC-I may be transmitted without ciphering.
  • the base station 604 optionally decodes the RRC message, fetches UE context and verifies integrity. If the integrity is successfully verified, then the base station deciphers the data.
  • the base station transmits S 1 -AP UE context resume request to the MME 606, which triggers MME 606 to resume the suspended connection.
  • the base station initiates the Sl-AP context resume procedure to resume the SI user plane external interface (Sl-U) bearers.
  • the base station 604 may signal to the MME 606 that there is only one uplink NAS PDU. This may be done, for example, by including a cause code e.g., "RRC Connectionless Mode". This indication may also be used by the MME 606 to prioritize processing of the UL data and expedite or prioritize sending confirmation of the resume.
  • the MME 606 configures/resumes bearers at 626, e.g., requesting the S-GW to reactivate the Sl-U bearers for the UE.
  • the MME transmits a Sl-AP UE context resume response to the base station 604 to confirm the configuration and resuming of the bearers, e.g., to confirm the UE context resumption to the base station.
  • the UE context may retrievable/unable to resume (e.g., the base station is a new base station and there is no X2 interface).
  • the MME 606 may indicate failure in the context resume response at 628.
  • the UE context resume response may be missing (e.g., base station 604 sends UE context resume request to the MME but MME does not respond for various reasons. In such cases, UE 602 may resume to full RRC connection by the base station 604 sending an indication to establish/resume RRC connection.
  • the base station forwards data PDU to the SGW 608. Similar to the example described in connection with FIG. 5, if 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.
  • the early data transmission may comprise a single uplink data transmission, e.g., 620.
  • the early data transmission may comprise a single downlink data transmission, described in connection with FIG. 6.
  • the SI context may be released after the data has been forwarded, at 632.
  • the SI connection can be suspended and the Sl-U bearers can be deactivated.
  • the UE may return to the RRC idle, suspended state.
  • the base station may send a message 634 that indicates that the early data transmission is finished and the UE can return to the RRC idle, suspended state 638.
  • the message 634 may comprise a contention resolution message.
  • the message 634 may be integrity protected and may include a count, such as a next hop chaining count, and a resume ID for the UE.
  • the order of messages 630 and 634 may be adjusted so that the confirmation message 634 is sent to the UE prior to the base station forwarding the data 630 to the SGW.
  • the UE 602 may transmit a HARQ after Access Stratum (AS) security has been passed for the received AS message.
  • AS Access Stratum
  • the MME 606 instead of or in addition to confirming the reception of NAS PDU from the base station 604, may indicate that the UE 602 is to transition to RRC connected state from idle state instead of completing a RRC connectionless transmission session. In such case, SI context may not be released may not be closed immediately and the base station may send an indication to the UE 602 to transition to RRC connected state (e.g., RRC Connection Setup).
  • FIG. 7 is a flowchart 700 of a method of wireless communication for early data transmission without an RRC connection to a base station.
  • the UE may be in RRC idle state, as described in connection with FIG. 5.
  • Optional aspects are illustrated with a dashed line.
  • the method may be performed by a UE (e.g., the UE 104, 350, 502, 602, the apparatus 802/802').
  • the UE may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE.
  • the UE receives SI from the base station.
  • FIGs. 5 and 6 illustrate examples of SI 512, 612 received by a UE.
  • the SI may indicate PRACH resources to the UE.
  • the PRACH resources may include a set of PRACH resources for early data transmission, e.g., data that is transmitted without establishing an RRC connection.
  • the SI may also indicate the maximum size of UL data that can be transmitted by using early data transmission. The indications can be separate corresponding to different CE levels of different NPRACH resources.
  • the UE may select an RRC connection mode to transmit the data communication, e.g., selecting between an active RRC connection transmission mode and an RRC connectionless transmission mode. The selection may be based on any of a number of factors, including the size of the data to be transmitted.
  • the UE may send an indication of an RRC connection mode for sending the data communication to the base station, at 706.
  • the indication may comprise a selection of a PRACH resource from a pool of PRACH resources associated with early data transfer.
  • the PRACH resource may comprise a NPRACH.
  • the selected PRACH resources may also indicate an intention to perform a connectionless early data transmission.
  • the SI may be broadcast from the base station and may indicate PRACH resources associated early data transmission without the UE transitioning to an RRC connected state.
  • the UE may select a resource based at least in part on an amount of data to be transmitted in the data communication.
  • the data communication may be transmitted to the base station during a random access procedure in which the UE does not establish the RRC connection.
  • the UE may transmit a random access preamble to the base station.
  • the random access preamble may be based on the selection at 706 from amount PRACH resources associated with early data transfer.
  • the UE may receive a grant for an uplink transmission without establishing the RRC connection, at 710.
  • the UE transmits a data communication to the base station over a control plane without establishing the RRC connection with the base station.
  • the data communication may be transmitted to the base station, at 712, based on the grant received at 710.
  • the data communication comprises data and a cause indication for the data communication.
  • the cause indication may inform the base station to receive the data communication comprised in message without establishing an RRC connection.
  • the cause indication may be referred to as a cause code, an establishment cause, etc.
  • the cause indication may indicate to the base station that the UE intends to perform an early data transmission without establishing an RRC connection.
  • the data communication may be transmitted on a CCCH, e.g., in a NAS message.
  • the data communication may be transmitted to the base station without the UE transitioning to an RRC connected state.
  • the data communication may comprise a single uplink data transmission.
  • a size of the data comprised in the single uplink data transmission may less than a size limit indicated by the base station.
  • the data may comprise a NAS PDU transmitted over a control plane, as described in connection with FIG. 5.
  • the data communication may further comprise UE identity information, e.g., an S- TMSI for the UE.
  • UE identity information e.g., an S- TMSI for the UE.
  • the early data transfer may further include a small amount of downlink data received from the network.
  • the UE may receive a downlink data communication from the base station over the control plane without establishing the RRC connection with the base station.
  • the downlink data communication may be received in an RRC message indicating that an early data transfer is complete.
  • the UE may receive a single downlink data transmission, e.g., as illustrated in FIG. 5. Additional aspects described in connection with either of FIGs. 5 or 6 may be performed by the UE in connection with the method of FIG. 7.
  • the UE may continue in an RRC idle state after transmitting and/or receiving the early data transmission.
  • FIG. 8 is a conceptual data flow diagram 800 illustrating the data flow between different means/components in an example apparatus 802.
  • the apparatus may be a UE (e.g., UE 104, 350, 502, 602).
  • the UE may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE, etc.
  • the apparatus includes a reception component 804 for receiving downlink communication from a base station 850 and a transmission component 806 for transmitting uplink communication to the base station 850.
  • the apparatus includes a system information component 808 for receiving system information from the base station 850 and a data communication component 810 for transmitting a data communication to the base station over a control plane without establishing the RRC connection with the base station, wherein the data communication comprises data and a cause indication for the data communication.
  • the apparatus may include an RRC mode component 812 for selecting an RRC connection mode to transmit the data communication and an indication component 814 for sending an indication of a RRC connection mode for sending the 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 component 816 for transmitting a random access preamble to the base station.
  • the apparatus may include a RAR component 818 for receiving a RAR from the base state, which may include a grant for an uplink transmission without establishing the RRC connection.
  • the apparatus may include a downlink data component 820 for receiving a downlink data communication from the base station over the control plane without establishing the RRC connection with the base station.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIG. 5, 6, and 7. As such, each block in the aforementioned flowcharts of FIGs. 5, 6, and 7 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902' employing a processing system 914.
  • the processing system 914 may be implemented with a bus architecture, represented generally by the bus 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.
  • the bus 924 links together various circuits including one or more processors and/or hardware components, represented by the processor 904, the components 804, 806, 808, 810, 812, 814, 816, 818, 820 and the computer-readable medium / memory 906.
  • the bus 924 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • the processing system 914 may be coupled to a transceiver 910.
  • the transceiver 910 is coupled to one or more antennas 920.
  • the transceiver 910 provides a means for communicating with various other apparatus over a transmission medium.
  • the transceiver 910 receives a signal from the one or more antennas 920, extracts information from the received signal, and provides the extracted information to the processing system 914, specifically the reception component 804.
  • the transceiver 910 receives information from the processing system 914, specifically the transmission component 810, and based on the received information, generates a signal to be applied to the one or more antennas 920.
  • 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 supra for any particular apparatus.
  • the computer- readable medium / memory 906 may also be used for storing data that is manipulated by the processor 904 when executing software.
  • the processing system 914 further includes at least one of the components 804, 806, 808, 810, 812, 814, 816, 818, 820.
  • the components may be software components running in the processor 904, resident/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 the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the processing system 914 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
  • the apparatus 802/802' for wireless communication includes means for receiving system information from the base station; means for transmitting a data communication to the base station over a control plane without establishing the RRC connection with the base station, wherein the data communication comprises data and a cause indication for the data communication, means for selecting an RRC connection mode to transmit the data communication, means for sending an indication of a RRC connection mode for sending the data communication to the base station, means for transmitting a random access preamble to the base station, means for receiving a grant for an uplink transmission without establishing the RRC connection, wherein the data communication is transmitted to the base station based on the grant, and means for receiving a downlink data communication from the base station without establishing the RRC connection with the base station.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 802 and/or the processing system 914 of the apparatus 802' configured to perform the functions recited by the aforementioned means.
  • the processing system 914 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • FIG. 10 is a flowchart 1000 of a method of wireless communication for early data reception without an RRC connection to a UE.
  • the method may be performed by a base station (e.g., base station 102, 180, 310, 504, 604, 850, the apparatus 1102, 1102').
  • a base station e.g., base station 102, 180, 310, 504, 604, 850, the apparatus 1102, 1102'.
  • Optional aspects are illustrated with a dashed line.
  • the base station indicates resources in system information.
  • FIGs. 5 and 6 illustrate examples of SI 512, 612 transmitted by a base station.
  • the SI may indicate PRACH resources to the UE.
  • the PRACH resources may include a set of PRACH resources for early data transmission, e.g., data that is transmitted without establishing an RRC connection.
  • the SI may also indicate the maximum size of UL data that can be transmitted by using early data transmission. The indications can be separate corresponding to different CE levels of different NPRACH resources.
  • the base station receives a data communication from the UE without establishing the RRC connection with the UE, wherein the data communication comprises data and a cause indication.
  • the cause indication may inform the base station to receive the data communication comprised in the RRC connection resume message without resuming the RRC connection.
  • the cause indication may be referred to as a cause code, an establishment cause, etc.
  • the cause indication may indicate to the base station that the UE intends to perform an early data transmission without establishing an RRC connection.
  • the data communication may be comprised in an RRC message indicating an intention to perform a connectionless early data transmission.
  • the data communication may be received on a CCCH, e.g., in a NAS message.
  • the data communication may be received from the UE and forwarded to a core network component, at 1014, without establishing an RRC connected state with the UE, e.g., without the UE transitioning to an RRC connected state.
  • the data communication may comprise a single uplink data transmission.
  • the data may comprise a NAS PDU received over a control plane, as described in connection with FIG. 5.
  • the data may comprise a Data PDU received over a user plane, as described in connection with FIG. 6.
  • the data communication may further comprise UE identity information, e.g., an S- TMSI when the data is received over a control plane or a resume ID for the UE when the data is received over a user plane.
  • the data communication may further comprise an authentication token, e.g., when the data is received over a user plane.
  • the data may be received over the user plane, e.g., when a UE begins from an RRC idle, suspended state.
  • the data communication may be received in an RRC connection resume message and the cause indication may inform the base station to receive the data communication comprised in the RRC connection resume message without resuming the RRC connection.
  • the data communication may further comprise an authentication token.
  • the data communication may be received from the UE during a random access procedure, as illustrated in the examples in FIGs. 5 and 6.
  • the base station may receive a random access preamble from the UE based on the PRACH resources (e.g., NPRACH resources) associated with early data transfer. Different resources may be associated with different CE levels.
  • the base station may transmit a RAR to the UE, at 1008, the RAR comprising an uplink grant for an early data transmission without establishing the RRC connection with the UE.
  • the data communication may be received, at 1012 from the UE based on the uplink grant.
  • the early data transfer may further include a small amount of downlink data transmitted to the UE.
  • the base station may transmit a downlink data communication from the base station without establishing the RRC connection with the UE.
  • the downlink data communication may be transmitted to the UE in an RRC message indicating to the UE that an early data transfer is complete.
  • the base station may transmit a single downlink data transmission, e.g., as illustrated in FIG. 5. Additional aspects described in connection with either of FIGs. 5 or 6 may be performed by the base station in connection with the method of FIG. 10.
  • FIG. 1 1 is a conceptual data flow diagram 1 100 illustrating the data flow between different means/components in an exemplary apparatus 1 102.
  • the apparatus may be a base station (e.g., base station 102, 180, 310, 504, 604, 850).
  • the apparatus includes a reception component 1104 for receiving uplink communication from UE 1150 and a downlink component 1 106 for transmitting downlink communication to UE and/or for communicating with a core network 1 155.
  • the apparatus includes an SI component 1108 for indicating resources in system information and a data communication component 11 10 for receiving a data communication from the UE without establishing the RRC connection with the UE, wherein the data communication comprises data and a cause indication.
  • the apparatus may include a preamble component 1 112 for receiving a random access preamble from the UE based on the PRACH resources associated with early data transfer, and a RAR component 1 114 for transmitting a random access response to the UE comprising an uplink grant for an early data transmission without establishing the RRC connection with the UE.
  • the apparatus may include a core network component 11 16 for forwarding the data to a core network without establishing the RRC connection with the UE.
  • the apparatus may include a downlink data component 1 1 18 for transmitting a downlink data communication to the UE without establishing the RRC connection with the UE.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGs. 5, 6, and 10. As such, each block in the aforementioned flowcharts of FIGs. 5, 6, and 10 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1102' employing a processing system 1214.
  • the processing system 1214 may be implemented with a bus architecture, represented generally by the bus 1224.
  • the bus 1224 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1214 and the overall design constraints.
  • the bus 1224 links together various circuits including one or more processors and/or hardware components, represented by the processor 1204, the components 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118, and the computer- readable medium / memory 1206.
  • the bus 1224 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • the processing system 1214 may be coupled to a transceiver 1210.
  • the transceiver 1210 may be coupled to a transceiver 1210.
  • the transceiver 1210 is coupled to one or more antennas 1220.
  • the transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium.
  • the transceiver 1210 receives a signal from the one or more antennas 1220, extracts information from the received signal, and provides the extracted information to the processing system 1214, specifically the reception component 1104.
  • the transceiver 1210 receives information from the processing system 1214, specifically the transmission component 1106, and based on the received information, generates a signal to be applied to the one or more antennas 1220.
  • 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 supra for any particular apparatus.
  • the computer- readable medium / memory 1206 may also be used for storing data that is manipulated by the processor 1204 when executing software.
  • the processing system 1214 further includes at least one of the components 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118.
  • the components may be software components running in the processor 1204, resident/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 the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the apparatus 1102/1102' for wireless communication includes means for indicating resources in system information, means for receiving a data communication from the UE without establishing the RRC connection with the UE, wherein the data communication comprises data and a cause indication, means for receiving a random access preamble from the UE based on the PRACH resources associated with early data transfer, means for transmitting a random access response to the UE comprising an uplink grant for an early data transmission without establishing the RRC connection with the UE, means for forwarding the data to a core network without establishing the RRC connection with the UE, means for transmitting a downlink data communication to the UE without establishing the RRC connection with the UE.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 1102 and/or the processing system 1214 of the apparatus 1102' configured to perform the functions recited by the aforementioned means.
  • the processing system 1214 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
  • the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.
  • FIG. 13 is a flowchart 1300 of a method of wireless communication for early data transmission without resuming an RRC connection to a base station.
  • the UE may be in an RRC suspended state, e.g., as described in connection with FIG. 6.
  • Optional aspects are illustrated with a dashed line.
  • the method may be performed by a UE (e.g., the UE 104, 350, 502, 602, the apparatus 1402/1402').
  • the UE may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE.
  • the UE receives SI from the base station.
  • FIG. 6 illustrate an example of SI
  • the SI may indicate PRACH resources to the UE.
  • the PRACH resources may include a set of PRACH resources for early data transmission, e.g., data that is transmitted without resuming an RRC connection.
  • the SI may also indicate the maximum size of UL data that can be transmitted by using early data transmission, e.g., over the user plane without resuming an RRC connection.
  • the indications can be separate corresponding to different CE levels of different NPRACH resources.
  • the UE may select an RRC connection mode to transmit the data communication, e.g., selecting between an active RRC connection transmission mode and an RRC connectionless transmission mode in which the UE does not resume the RRC connection.
  • the selection may be based on any of a number of factors, including the size of the data to be transmitted.
  • the UE may send an indication of an RRC connection mode for sending the data communication to the base station, at 1306.
  • the indication may comprise a selection of a PRACH resource from a pool of PRACH resources associated with early data transfer.
  • the PRACH resource may comprise a NPRACH.
  • the selected PRACH resources may also indicate an intention to perform a connectionless early data transmission.
  • the SI may be broadcast from the base station and may indicate PRACH resources associated early data transmission without the UE transitioning to an RRC connected state.
  • the UE may select a resource based at least in part on an amount of data to be transmitted in the data communication.
  • the data communication may be transmitted to the base station during a random access procedure in which the UE does not resume the RRC connection.
  • the UE may transmit a random access preamble to the base station.
  • the random access preamble may be based on the selection at 1306 from amount PRACH resources associated with early data transfer.
  • the UE may receive a grant for an uplink transmission without resuming the RRC connection, at 1310.
  • the UE transmits a data communication to the base station over a user plane without resuming the RRC connection with the base station.
  • the data communication may be transmitted to the base station, at 1312, based on the grant received at 1310.
  • the data communication may comprise data and a cause indication.
  • the data communication may comprise an RRC message.
  • the data may be multiplexed along with the RRC message, e.g., in the same transmission. This may be in contrast to the example in FIG. 7, in which the data is comprised in the RRC message and sent over the control plane.
  • the cause indication may be comprised in the RRC message.
  • the cause indication may be separate from the RRC message yet included in the same data communication transmission.
  • the RRC message may comprise an RRC connection resume request along with a cause indication for the data communication.
  • the data communication may also include a UE ID, which may be comprised in the RRC message.
  • the user data may be multiplexed with an RRC message comprising a cause indication and/or a UE ID and sent together in the same transmission over the user plane.
  • the data and cause may be comprised in an RRC message.
  • the data may be transmitted together with a RRC connection resume message, and the cause indication may inform the base station to receive the data multiplexed with the RRC connection resume message without resuming the RRC connection.
  • the cause indication may be referred to as a cause code, a resume cause, etc.
  • the data communication may be transmitted on a CCCH, e.g., in aNAS message.
  • the data communication may be transmitted to the base station without the UE transitioning to an RRC connected state.
  • the data communication may comprise a single uplink data transmission.
  • a size of the data comprised in the single uplink data transmission may less than or equal to a size limit indicated by the base station.
  • the data may comprise a Data PDU transmitted over a user plane, as described in connection with FIG. 6.
  • the data communication may further comprise UE identity information, e.g., a resume ID comprised in the RRC message, the for the UE transmitting the data over a user plane.
  • the data communication may further comprise an authentication token.
  • the data may be transmitted over the user plane, e.g., when a UE is in an RRC idle, suspended state.
  • the early data transfer may further include a small amount of downlink data received from the network.
  • the UE may receive a downlink data communication from the base station over the user plane without resuming the RRC connection with the base station.
  • the downlink data communication may comprise an RRC message indicating that an early data transfer is complete.
  • the UE may receive a single downlink data transmission, e.g., as illustrated in FIG. 6. Additional aspects described in connection with either of FIGs. 5 or 6 may be performed by the UE in connection with the method of FIG. 13.
  • the UE may remain in the RRC idle, suspended state, after transmitting and/or receiving the early data transmission.
  • FIG. 14 is a conceptual data flow diagram 1400 illustrating the data flow between different means/components in an example apparatus 1402.
  • the apparatus may be a UE (e.g., UE 104, 350, 502, 602) in an RRC suspended state with base station 1450.
  • the UE may comprise an NB-IoT UE, a BL UE, eMTC UE, or CE UE, etc.
  • the apparatus includes a reception component 1404 for receiving downlink communication from a base station 1450 and a transmission component 1406 for transmitting uplink communication to the base station 1450.
  • the apparatus includes a system information component 1408 for receiving system information from the base station 1450 and a data communication component 1410 for transmitting a data communication to the base station over a user plane without resuming the RRC connection with the base station, wherein the data communication comprises data and a cause indication for the data communication.
  • the apparatus may include an RRC mode component 1412 for selecting an RRC connection mode to transmit the data communication and an indication component 1414 for sending an indication of a RRC connection mode for sending the 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 component 1416 for transmitting a random access preamble to the base station.
  • the apparatus may include a RAR component 1418 for receiving a RAR from the base state, which may include a grant for an uplink transmission without resuming the RRC connection.
  • the apparatus may include a downlink data component 1420 for receiving a downlink data communication from the base station over the user plane without establishing the RRC connection with the base station.
  • the apparatus may further comprise a token component 1422 configured to include an authentication token with the data transmitted to the base station.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGs. 6 and 13, as well as FIGs. 5 and 7. As such, each block in the aforementioned flowcharts of FIGs. 5, 6, 7, and 13 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1402' employing a processing system 1514.
  • the processing system 1514 may be implemented with a bus architecture, represented generally by the bus 1524.
  • the bus 1524 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1514 and the overall design constraints.
  • the bus 1524 links together various circuits including one or more processors and/or hardware components, represented by the processor 1504, the components 1404, 1406, 1408, 1410, 1412, 1414, 1416, 1418, 1420, 1422 and the computer-readable medium / memory 1506.
  • the bus 1524 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • the processing system 1514 may be coupled to a transceiver 1510.
  • the transceiver 1510 may be coupled to a transceiver 1510.
  • the transceiver 1510 is coupled to one or more antennas 1520.
  • the transceiver 1510 provides a means for communicating with various other apparatus over a transmission medium.
  • the transceiver 1510 receives a signal from the one or more antennas 1520, extracts information from the received signal, and provides the extracted information to the processing system 1514, specifically the reception component 1404.
  • the transceiver 1510 receives information from the processing system 1514, specifically the transmission component 1410, and based on the received information, generates a signal to be applied to the one or more antennas 1520.
  • 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 supra for any particular apparatus.
  • the computer- readable medium / memory 1506 may also be used for storing data that is manipulated by the processor 1504 when executing software.
  • the processing system 1514 further includes at least one of the components 1404, 1406, 1408, 1410, 1412, 1414, 1416, 1418, 1420, 1422.
  • the components may be software components running in the processor 1504, resident/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 the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the processing system 1514 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
  • the apparatus 1402/1402' for wireless communication includes means for receiving system information from the base station while in an RRC suspended state; means for transmitting a data communication to the base station over a user plane without resuming an RRC connection with the base station, wherein the data communication comprises data and a cause indication for the data communication, means for selecting an RRC connection mode to transmit the data communication, means for sending an indication of a RRC connection mode for sending the data communication to the base station, means for transmitting a random access preamble to the base station, means for receiving a grant for an uplink transmission without resuming the RRC connection, wherein the data communication is transmitted to the base station based on the grant, and means for receiving a downlink data communication from the base station over the user plane without resuming the RRC connection with the base station.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 1402 and/or the processing system 1514 of the apparatus 1402' configured to perform the functions recited by the aforementioned means.
  • the processing system 1514 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • FIG. 16 is a flowchart 1600 of a method of wireless communication for early data reception without resuming an RRC connection to a UE.
  • the method may be performed by a base station (e.g., base station 102, 180, 310, 504, 604, 850, the apparatus 1702, 1702').
  • the base station may be in an RRC suspended state, as described in connection with FIG. 6.
  • Optional aspects are illustrated with a dashed line.
  • the base station indicates resources in system information.
  • FIG. 6 illustrates an example of SI 612 transmitted by a base station.
  • the SI may indicate PRACH resources to the UE.
  • the PRACH resources may include a set of PRACH resources for early data transmission, e.g., data that is transmitted without establishing an RRC connection.
  • the SI may also indicate the maximum size of UL data that can be transmitted by using early data transmission. The indications can be separate corresponding to different CE levels of different NPRACH resources.
  • the base station receives a data communication from the UE over the user plane without resuming the RRC connection with the UE, wherein the data communication comprises data and a cause indication.
  • the data communication may comprise an RRC message.
  • the data may be multiplexed along with the RRC message, e.g., in the same transmission.
  • the cause indication may be comprised in the RRC message.
  • the cause indication may be separate from the RRC message yet included in the same data communication transmission.
  • the RRC message may comprise an RRC connection resume request along with a cause indication for the data communication.
  • the data communication may also include a UE ID, e.g., which may be comprised in the RRC message.
  • the user data may be multiplexed with an RRC message comprising a cause indication and/or a UE ID and sent together in the same transmission over the user plane.
  • the data and cause may be comprised in an RRC message.
  • the cause indication may inform the base station to receive the data multiplexed with the RRC connection resume message without resuming the RRC connection.
  • the cause indication may be referred to as a cause code, a resume cause, etc.
  • the cause indication may indicate to the base station that the UE intends to perform an early data transmission without resuming an RRC connection.
  • the data may be sent together, e.g., multiplexed, in a single transmission with an RRC message indicating an intention to perform a connectionless early data transmission, e.g., without resuming the RRC connection.
  • the data communication may be received on a CCCH, e.g., in a data PDU.
  • the data may be received from the UE and forwarded to a core network component, at 1614, without resuming an RRC connected state with the UE, e.g., without the UE transitioning from the RRC suspended state to an RRC connected state.
  • the data communication may comprise a single uplink data transmission.
  • the data may comprise a Data PDU received over a user plane, as described in connection with FIG. 6.
  • the data communication may further comprise UE identity information, e.g., a resume ID for the UE.
  • the data communication may further comprise an authentication token, as illustrated in message 620 in FIG. 6.
  • the data may be received over the user plane, e.g., while a UE is in an RRC idle, suspended state.
  • the data communication may comprise an RRC connection resume message and the cause indication may inform the base station to receive the data comprised in the data communication along with the RRC connection resume message without resuming the RRC connection.
  • the data communication may further comprise an authentication token.
  • the data communication may be received from the UE during a random access procedure, as illustrated in the examples in both FIGs. 5 and 6.
  • the base station may receive a random access preamble from the UE based on the PRACH resources (e.g., NPRACH resources) associated with early data transfer. Different PRACH resources may be associated with different CE levels.
  • the base station may transmit a RAR to the UE, at 1608, the RAR comprising an uplink grant for an early data transmission without resuming the RRC connection with the UE.
  • the data communication may be received, at 1612 from the UE based on the uplink grant.
  • FIG. 6 illustrates an example message 620 as the transmission.
  • the early data transfer may further include a small amount of downlink data transmitted to the UE.
  • the base station may transmit a downlink data communication from the base station over the user plane without establishing the RRC connection with the UE.
  • the downlink data communication may be transmitted to the UE in an RRC message indicating to the UE that an early data transfer is complete.
  • the base station may transmit a single downlink data transmission, e.g., as illustrated in FIG. 6. Additional aspects described in connection with either of FIGs. 5 or 6 may be performed by the base station in connection with the method of FIG. 16.
  • FIG. 17 is a conceptual data flow diagram 1700 illustrating the data flow between different means/components in an exemplary apparatus 1702.
  • the apparatus may be a base station (e.g., base station 102, 180, 310, 504, 604, 850).
  • the apparatus includes a reception component 1704 for receiving uplink communication from UE 1750 and a downlink component 1706 for transmitting downlink communication to UE and/or for communicating with a core network 1755.
  • the apparatus includes an SI component 1708 for indicating resources in system information and a data communication component 1710 for receiving a data communication from the UE over a use plane without resuming the RRC connection with the UE, wherein the data communication comprises data and a cause indication.
  • the data communication may be comprised in a Msg3 from the UE.
  • the apparatus may include a preamble component 1712 for receiving a random access preamble from the UE based on the PRACH resources associated with early data transfer, and a RAR component 1714 for transmitting a random access response to the UE comprising an uplink grant for an early data transmission without resuming the RRC connection with the UE.
  • the apparatus may include a core network component 1716 for forwarding the data to a core network without resuming the RRC connection with the UE.
  • the apparatus may include a downlink data component 1718 for transmitting a downlink data communication to the UE over the user plane without resuming the RRC connection with the UE.
  • the apparatus may include token component 1720 for authenticating the UE based on an authentication token comprised in the data communication.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGs. 5, 6, and 10, and 16. As such, each block in the aforementioned flowcharts of FIGs. 5, 6, and 10, and 16 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer- readable medium for implementation by a processor, or some combination thereof.
  • FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for an apparatus 1702' employing a processing system 1814.
  • the processing system 1814 may be implemented with a bus architecture, represented generally by the bus 1824.
  • the bus 1824 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1814 and the overall design constraints.
  • the bus 1824 links together various circuits including one or more processors and/or hardware components, represented by the processor 1804, the components 1704, 1706, 1708, 1710, 1712, 1714, 1716, 1718, 1720, and the computer-readable medium / memory 1806.
  • the bus 1824 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • the processing system 1814 may be coupled to a transceiver 1810.
  • the transceiver 1810 may be coupled to a transceiver 1810.
  • the transceiver 1810 is coupled to one or more antennas 1820.
  • the transceiver 1810 provides a means for communicating with various other apparatus over a transmission medium.
  • the transceiver 1810 receives a signal from the one or more antennas 1820, extracts information from the received signal, and provides the extracted information to the processing system 1814, specifically the reception component 1704.
  • the transceiver 1810 receives information from the processing system 1814, specifically the transmission component 1706, and based on the received information, generates a signal to be applied to the one or more antennas 1820.
  • 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 supra for any particular apparatus.
  • the computer- readable medium / memory 1806 may also be used for storing data that is manipulated by the processor 1804 when executing software.
  • the processing system 1814 further includes at least one of the components 1704, 1706, 1708, 1710, 1712, 1714, 1716, 1718, 1720.
  • the components may be software components running in the processor 1804, resident/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 the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the apparatus 1702/1702' for wireless communication includes means for indicating resources in system information, means for receiving a data communication from the UE over a user plane without resuming an RRC connection with the UE, wherein the data communication comprises data and a cause indication; means for receiving a random access preamble from the UE based on the PRACH resources associated with the early data transmission; means for forwarding the data to a core network without resuming the RRC connection with the UE; and means for transmitting a downlink data communication to the UE over the user plane without resuming the RRC connection with the UE.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 1702 and/or the processing system 1814 of the apparatus 1702' configured to perform the functions recited by the aforementioned means.
  • the processing system 1814 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
  • the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.
  • Combinations such as "at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and "A, B, C, or any combination thereof include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
EP18746366.6A 2017-08-11 2018-07-02 Methods and apparatuses for uplink early data transmission Withdrawn EP3666025A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201762544703P 2017-08-11 2017-08-11
US15/964,523 US20180324854A1 (en) 2017-05-04 2018-04-27 Uplink small data transmission for enhanced machine-type-communication (emtc) and internet of things (iot) communication
US16/024,421 US20180324869A1 (en) 2017-05-04 2018-06-29 Uplink early data transmission
PCT/US2018/040603 WO2019032222A1 (en) 2017-08-11 2018-07-02 METHODS AND APPARATUSES FOR EARLY DATA TRANSMISSION IN UPLINK

Publications (1)

Publication Number Publication Date
EP3666025A1 true EP3666025A1 (en) 2020-06-17

Family

ID=65271375

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18746366.6A Withdrawn EP3666025A1 (en) 2017-08-11 2018-07-02 Methods and apparatuses for uplink early data transmission

Country Status (4)

Country Link
EP (1) EP3666025A1 (zh)
CN (1) CN111034329A (zh)
TW (1) TW201911939A (zh)
WO (1) WO2019032222A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2952371T3 (es) * 2018-08-03 2023-10-31 Ericsson Telefon Ab L M Optimizaciones del plano de usuario para internet de las cosas celular de 5G
GB201820171D0 (en) * 2018-12-11 2019-01-23 Nordic Semiconductor Asa Efficient cellular communication
WO2020252659A1 (zh) * 2019-06-18 2020-12-24 Oppo广东移动通信有限公司 一种数据发送方法、网络设备、终端设备
WO2020258182A1 (zh) * 2019-06-27 2020-12-30 Oppo广东移动通信有限公司 数据传输方法、装置和通信设备
CN112218383A (zh) * 2019-07-09 2021-01-12 华硕电脑股份有限公司 无线通信系统用于载波选择和早期数据传送的方法和设备
US20220287101A1 (en) * 2019-07-19 2022-09-08 Lenovo (Beijing) Limited Method and apparatus for data transmission
WO2021025246A1 (en) * 2019-08-06 2021-02-11 Lg Electronics Inc. Method and apparatus for handling security information between a wireless device and a network for a fast rrc release procedure in a wireless communication system
CN112566273B (zh) * 2019-09-26 2022-12-23 维沃移动通信有限公司 一种数据接收、发送方法、终端及网络侧设备
CN110650533A (zh) * 2019-09-29 2020-01-03 中兴通讯股份有限公司 一种数据传输和信息确定方法、装置和存储介质
CN111641976A (zh) * 2020-05-22 2020-09-08 广东小天才科技有限公司 一种数据传输的方法、终端设备及网络设备
US20220086899A1 (en) * 2020-09-17 2022-03-17 Asustek Computer Inc. Method and apparatus for small data transmission (sdt) procedure in a wireless communication system
CN116830780A (zh) * 2021-01-14 2023-09-29 欧芬诺有限责任公司 非活动上下文管理
CN116830758A (zh) * 2021-01-29 2023-09-29 高通股份有限公司 上行链路信号辅助的经预配置的上行链路资源
WO2022178797A1 (en) * 2021-02-26 2022-09-01 Qualcomm Incorporated Message transmission via non-terrestrial network
EP4307776A4 (en) * 2021-05-11 2024-05-01 Guangdong Oppo Mobile Telecommunications Corp Ltd COMMUNICATION METHOD AND DEVICE

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120071229A (ko) * 2010-12-22 2012-07-02 한국전자통신연구원 이동통신 시스템의 데이터 전송 방법
EP2955881B1 (en) * 2013-02-28 2020-05-27 Huawei Technologies Co., Ltd. Data sending method and receiving method and device
US10009926B2 (en) * 2014-07-11 2018-06-26 Qualcomm Incorporated Methods and apparatus for connectionless access
US20170099660A1 (en) * 2015-10-01 2017-04-06 Electronics And Telecommunications Research Institute Method and apparatus for transmitting uplink data

Also Published As

Publication number Publication date
WO2019032222A1 (en) 2019-02-14
CN111034329A (zh) 2020-04-17
TW201911939A (zh) 2019-03-16

Similar Documents

Publication Publication Date Title
US20180359786A1 (en) Uplink early data transmission
EP3837900B1 (en) Downlink data transmission in rrc inactive mode
US11627635B2 (en) Expedited release of a user equipment
EP3666025A1 (en) Methods and apparatuses for uplink early data transmission
US11895585B2 (en) Data transfer between an inactive mode user equipment and a wireless network
WO2021056384A1 (en) Back-off mechanisms for transmission of data over control plane
US11356894B2 (en) Method and apparatus for configuring uplink hybrid automatic repeat request (HARQ) retransmission timer for narrowband communications
US11991751B2 (en) Identification of user equipment in a random access procedure
US10863484B2 (en) Indication of random-access channel MSG3 resource duration via random-access channel MSG2
US11895697B2 (en) Integrated access and backhaul network random access parameter optimization
EP3520474B1 (en) Signaling to indicate whether physical broadcast channel repetition is enabled in a target cell
US20220132584A1 (en) Ra-rnti formula for extended random access response windows
WO2020252189A1 (en) Evolved packet system (eps) mobility configuration of non access stratum (nas) count from wireless system
CN112534901B (zh) Rrc不活动模式下的下行链路数据传输

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200116

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20211103

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/00 20090101ALN20221223BHEP

Ipc: H04W 52/02 20090101ALN20221223BHEP

Ipc: H04W 88/08 20090101ALN20221223BHEP

Ipc: H04W 88/02 20090101ALN20221223BHEP

Ipc: H04L 5/00 20060101ALN20221223BHEP

Ipc: H04W 74/08 20090101AFI20221223BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/00 20090101ALN20230125BHEP

Ipc: H04W 52/02 20090101ALN20230125BHEP

Ipc: H04W 88/08 20090101ALN20230125BHEP

Ipc: H04W 88/02 20090101ALN20230125BHEP

Ipc: H04L 5/00 20060101ALN20230125BHEP

Ipc: H04W 74/08 20090101AFI20230125BHEP

INTG Intention to grant announced

Effective date: 20230216

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20230627