Patent Description:
A wireless communication network, as is for example described in <CIT>, may include a number of base stations or node Bs that can support communication for a number of user equipments (UEs). A UE may communicate with a base station via downlink (DL) and uplink (UL).

With the growing demand for mobile broadband access comes an increase in communications between an eNB and a UE. Traditionally, a UE is not constantly connected with an eNB because a constant connection would waste network bandwidth and UE battery life. As such, every time a disconnected UE desires to send or receive data from the network, a series of specific steps and communications between the eNB and the UE are performed in order to setup a two way connection between the UE and eNB before the desired data is transmitted. This process has traditionally been called the Random Access Procedure (RAP).

RAP involves a great number of setup steps before a connection is established and data is transmitted. Traditionally, all of the mobile originated (MO) data transmission steps are performed before each MO transmission, and every mobile terminated (MT) transmission step is performed before every MT transmission. Typically, all of the setup steps are repeated a multitude of times throughout an hour tying up a considerable about of network bandwidth and UE battery life. Further, because these steps are repeated for each transmission, the setup steps increase data latency.

The invention is described in further detail with reference to <FIG> and <FIG>, whereas <FIG> and <FIG> are provided for illustrative purposes.

This disclosure relates generally to providing or participating in authorized shared access between two or more wireless communications systems, also referred to as wireless communications networks. In various embodiments, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably.

A CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, and the like.

3GPP defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM/EDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may comprise one or more GERANs, which may be coupled with UTRANs in the case of a UMTS/GSM network. An operator network may also include one or more LTE networks, and/or one or more other networks. The various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS). 3GPP long term evolution (LTE) is a 3GPP project aimed at improving the universal mobile telecommunications system (UMTS) mobile phone standard. For clarity, certain aspects of the apparatus and techniques may be described below for LTE implementations or in an LTE-centric way, and LTE terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to LTE applications. Indeed, the present disclosure is concerned with shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

A new carrier type based on LTE/LTE-A including in unlicensed spectrum has also been suggested that can be compatible with carrier-grade WiFi, making LTE/LTE-A with unlicensed spectrum an alternative to WiFi. LTE/LTE-A, when operating in unlicensed spectrum, may leverage LTE concepts and may introduce some modifications to physical layer (PHY) and media access control (MAC) aspects of the network or network devices to provide efficient operation in the unlicensed spectrum and meet regulatory requirements. The unlicensed spectrum used may range from as low as several hundred Megahertz (MHz) to as high as tens of Gigahertz (GHz), for example. In operation, such LTE/LTE-A networks may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it may be apparent to one of skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications.

System designs may support various time-frequency reference signals for the downlink and uplink to facilitate beamforming and other functions. A reference signal is a signal generated based on known data and may also be referred to as a pilot, preamble, training signal, sounding signal, and the like. A reference signal may be used by a receiver for various purposes such as channel estimation, coherent demodulation, channel quality measurement, signal strength measurement, and the like. MIMO systems using multiple antennas generally provide for coordination of sending of reference signals between antennas; however, LTE systems do not in general provide for coordination of sending of reference signals from multiple base stations or eNBs.

In some implementations, a system may utilize time division duplexing (TDD). For TDD, the downlink and uplink share the same frequency spectrum or channel, and downlink and uplink transmissions are sent on the same frequency spectrum. The downlink channel response may thus be correlated with the uplink channel response. Reciprocity may allow a downlink channel to be estimated based on transmissions sent via the uplink. These uplink transmissions may be reference signals or uplink control channels (which may be used as reference symbols after demodulation). The uplink transmissions may allow for estimation of a space-selective channel via multiple antennas.

In LTE implementations, orthogonal frequency division multiplexing (OFDM) is used for the downlink - that is, from a base station, access point or eNodeB (eNB) to a user terminal or UE. Use of OFDM meets the LTE requirement for spectrum flexibility and enables cost-efficient solutions for very wide carriers with high peak rates, and is a well-established technology. For example, OFDM is used in standards such as IEEE <NUM>. 11a/g, <NUM>, High Performance Radio LAN-<NUM> (HIPERLAN-<NUM>, wherein LAN stands for Local Area Network) standardized by the European Telecommunications Standards Institute (ETSI), Digital Video Broadcasting (DVB) published by the Joint Technical Committee of ETSI, and other standards.

Time frequency physical resource blocks (also denoted here in as resource blocks or "RBs" for brevity) may be defined in OFDM systems as groups of transport carriers (e.g. sub-carriers) or intervals that are assigned to transport data. The RBs are defined over a time and frequency period. Resource blocks are comprised of time-frequency resource elements (also denoted here in as resource elements or "REs" for brevity), which may be defined by indices of time and frequency in a slot. Additional details of LTE RBs and REs are described in the 3GPP specifications, such as, for example, 3GPP TS <NUM>.

UMTS LTE supports scalable carrier bandwidths from <NUM> down to <NUM>. In LTE, an RB is defined as <NUM> sub-carriers when the subcarrier bandwidth is <NUM>, or <NUM> sub-carriers when the sub-carrier bandwidth is <NUM>. In an exemplary implementation, in the time domain there is a defined radio frame that is <NUM> long and consists of <NUM> subframes of <NUM> millisecond (ms) each. Every subframe consists of <NUM> slots, where each slot is <NUM>. The subcarrier spacing in the frequency domain in this case is <NUM>. Twelve of these subcarriers together (per slot) constitute an RB, so in this implementation one resource block is <NUM>. Six Resource blocks fit in a carrier of <NUM> and <NUM> resource blocks fit in a carrier of <NUM>.

<FIG> shows a wireless network <NUM> for communication, which may be an LTE-A network (other types of networks may also be utilized). The wireless network <NUM> includes a number of evolved node Bs (eNBs) <NUM> and other network entities. An eNB may be a station that communicates with the UEs and may also be referred to as a base station, a node B, an access point, and the like. Each eNB <NUM> may provide communication coverage for a particular geographic area. The term "cell" can refer to this particular geographic coverage area of an eNB and/or an eNB subsystem serving the coverage area, depending on the context in which the term is used.

An eNB may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB or a home eNB. In the example shown in <FIG>, the eNBs 105a, 105b and 105c are macro eNBs for the macro cells 110a, 110b and 110c, respectively. The eNBs 105x, 105y, and 105z are small cell eNBs, which may include pico or femto eNBs that provide service to small cells 110x, 110y, and 110z, respectively. An eNB may support one or multiple (e.g., two, three, four, and the like) cells.

For synchronous operation, the eNBs may have similar frame timing, and transmissions from different eNBs may be approximately aligned in time. Synchronous networks may organize cells into zones, wherein a zone comprises a plurality of cells. The zones of a wireless network may allocate zone specific resources such that a UE may move freely throughout a zone using the same zone specific resources as it travels from one cell to another. For asynchronous operation, the eNBs may have different frame timing, and transmissions from different eNBs may not be aligned in time.

The UEs <NUM> are dispersed throughout the wireless network <NUM>, and each UE may be stationary or mobile. A UE may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like. A UE may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, watch, or the like. Regarding the Internet of Things (IoT), a UE may be referred to as a IoT UE which may be an appliance, thermostat, water meter, electric meter, gas meter, sprinkler system, refrigerator, hot water heater, oven, car, navigation system, pace maker, implanted medical device, location tracker, bicycle computer, entertainment device, television, monitor, vehicular component, vending machine, medical device, and the like. A UE may be able to communicate with macro eNBs, pico eNBs, femto eNBs, relays, and the like. In <FIG>, a lightning bolt (e.g., communication links <NUM>) indicates desired transmissions between a UE and a serving eNB, which is an eNB designated to serve the UE on the downlink and/or uplink, or desired transmission between eNBs.

LTE/-A utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, or the like. Each subcarrier may be modulated with data. For example, K may be equal to <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> for a corresponding system bandwidth of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> megahertz (MHz), respectively. The system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover <NUM>, and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> sub-bands for a corresponding system bandwidth of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>, respectively. The devices illustrated in <FIG> are operable to carry out the techniques and operations disclosed herein.

As explained above, the growing demand for mobile broadband access has created an increase in communications between an eNB and a UE. Traditionally, all of the mobile originated (MO) data transmission steps are performed before each MO transmission, and every mobile terminated (MT) transmission step is performed before every MT transmission. Typically, all of the setup steps are repeated a multitude of times throughout an hour tying up a considerable about of network bandwidth and UE battery life. Further, because these steps are repeated for each transmission, the setup steps increase data latency. As such, it would be desirable to have systems and methods that allow for the reduction of the aforementioned steps and communications prior to MO and/or MT communications. That being said, there may be times when performing most or all of the aforementioned steps may be appropriate due to the type of data being sent, the mobility of the UE, and/or the status of the UE. Thus, it would be further desirable to have systems and methods operable to determine which steps and communications are appropriate given the circumstances and configure the UE to perform a reduced set of steps and communications when appropriate and perform a robust set of steps and communications when appropriate.

<FIG> shows a block diagram of a design of a base station/eNB <NUM> and a UE <NUM>, which may be one of the base stations/eNBs and one of the UEs in <FIG>. For a restricted association scenario, the eNB <NUM> may be the small cell eNB 105z in <FIG>, and the UE <NUM> may be the UE 115z, which in order to access small cell eNB 105z, would be included in a list of accessible UEs for small cell eNB 105z. The eNB <NUM> may also be a base station of some other type. The eNB <NUM> may be equipped with antennas 234a through 234t, and the UE <NUM> may be equipped with antennas 252a through 252r.

At the eNB <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the PBCH, PCFICH, PHICH, PDCCH, etc. The data may be for the PDSCH, etc. The transmit processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor <NUM> may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal. A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a through 232t. Downlink signals from modulators 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.

At the UE <NUM>, the antennas 252a through 252r may receive the downlink signals from the eNB <NUM> and may provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.

On the uplink, at the UE <NUM>, a transmit processor <NUM> may receive and process data (e.g., for the PUSCH) from a data source <NUM> and control information (e.g., for the PUCCH) from the controller/processor <NUM>. The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the eNB <NUM>. At the eNB <NUM>, the uplink signals from the UE <NUM> may be received by the antennas <NUM>, processed by the demodulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE <NUM>. The processor <NUM> may provide the decoded data to a data sink <NUM> and the decoded control information to the controller/processor <NUM>.

The controllers/processors <NUM> and <NUM> may direct the operation at the eNB <NUM> and the UE <NUM>, respectively. The controller/processor <NUM> and/or other processors and modules at the eNB <NUM> may perform or direct the execution of various processes for the techniques described herein. The controllers/processor <NUM> and/or other processors and modules at the UE <NUM> may also perform or direct the execution of the functional blocks illustrated in <FIG>, and/or other processes for the techniques described herein. The memories <NUM> and <NUM> may store data and program codes for the eNB <NUM> and the UE <NUM>, respectively.

<FIG> shows an example flow diagram of method <NUM>, which is an Event Driven Access and Data Transmission Procedure <NUM>. In method <NUM>, an event triggers performance of all the steps of the Event Driven Access and Data Transmission Procedure <NUM>. An example triggering event is a scheduled reading report, wherein the UE is schedule to take a reading (e.g., temperature reading) and report the reading to the network. Upon taking the reading, the UE would perform method <NUM> in order to transmit the mobile originated (MO) data to the network. Another example triggering event is the reception of a Keep Alive (KA) message or a paging message from the eNB warning the UE that a data transmission will soon be sent to the UE. A KA is used to tell the UE to wake up and setup a connection with the eNB, for example, because the eNB is getting ready to send mobile terminated (MT) data to the UE. In embodiments, a KA may be as small as one bit.

In <NUM>, an eNB broadcasts synchronization information, which may include but is not limited to, Primary Synchronization Signals (PSS), Secondary Synchronization Signals (SSS), downlink reference signals, Master Information Block (MIB), Physical Hybrid-ARQ Indicator Channel (PHICH) configuration, System Frame Number, QPSK modulation, cell-specific scrambling, basic network data, and the like. In <NUM>, one or more UE receives the eNB broadcasted synchronization information. The eNB broadcasted synchronization information may be received directly from the eNB or from another device.

Upon a triggering event occurring, it is determined that communication between the UE and eNB is desired. If the triggered communication is to be MO, the method performs alternative A. Alternative A begins with 303a, wherein the UE sends a Chirp using at least a portion of the synchronization information, which may include the Random Access Channel Reference Signal (RACH-RS), the UE ID, Buffer Status Report, and/or the like. In embodiments, the eNB may not have network resources available at the time the Chirp is received. For example, the eNB may not have an UL channel available at the time the UE sends the Chirp. In such a circumstance, the eNB has the option to respond to the Chirp by sending a KA message to the UE indicting that the eNB is willing to receive the data but does not currently have the resources available (optional 303b). Upon network resources becoming available, the eNB may proceed to <NUM>.

Alternatively, if the triggered communication is to be MT, the method performs alternative B. In alterative B, the UE has the option of sending a Chirp using at least a portion of the synchronization information, which may include the Random Access Channel Reference Signal (RACH-RS), the UE ID, Buffer Status Report, and/or the like. In 303d, the eNB sends a Keep Alive (KA) to the UE. After steps 303b or 303d (depending on which of the alternative routes were taken), the method moves to <NUM>.

At <NUM>, in response to the Chirp or KA, the eNB creates and sends a Connection Setup, which may include network information, such as but not limited to, a Cell ID, the UL or DL assignment, a Timing Advance (TA), a Modulation and Coding Scheme (MCS), Channel State Information (CSI), and/or the like. The UE may receive the Connection Setup directly from the eNB or from another device.

In <NUM> the data payload is send on the assigned UL or DL. In a MO example, the UE sends the data payload (e.g., a temperature reading) the eNB on the UL in <NUM>. If a MT example, the eNB sends the data payload to the UE on the DL in <NUM>.

After the initial data payload is transmitted in <NUM>, the UE and eNB may maintain the connection so that additional data payloads may be communicated back and forth between the UE and eNB. Upon the UE and eNB ceasing to send data to each other for a period of time, <NUM> may transition the UE into an Idle state or Standby mode. In <NUM>, another triggering event occurs, thereby causing all steps of the Event Driven Access and Transmission Data Procedure <NUM> to repeat again.

The Event Driven Access and Data Transmission Procedure of <FIG> can be repeated each and every time an event occurs, for example, when a data transfer is initiated. As such, while method <NUM> performs less steps as compared to traditional RAP, steps of this method may be repeated several times throughout a time period (e.g., minute, hours, day, and the like). Performing the steps of method <NUM> may consume a considerable amount of resources including time, battery life, and network traffic. When appropriate, it would be desirable to conserve the aforementioned resources by offering a method that allows one or more of the steps of <FIG> to be skipped for defined periods of time.

<FIG> is an example Network Configurable Access and Data Transmission Procedure useful for mobile originated (MO) data transfers. It is generally designed to reduce the Access Procedure's frequency so some of method <NUM>'s actions may be skipped. Method <NUM> is split into two procedures: the Access Procedure 400a, which is performed once during a predetermined time period (e.g., once an hour, once a day, once a week, or the like) and the Data Transmission Procedure 400b, which is performed at the initiation of each data transfer. Thus, Access Procedure 400a is performed less frequently as compared to Data Transmission Procedure 400b. Further, according to Data Transmission Procedure 400b, multiple data transmission are conducted using and reusing access data saved during Access Procedure 400a until the predetermined time period expires. When the predetermined time period expires, the Access Procedure 400a is performed again to allow saved access data to be refreshed. As such, method <NUM> minimizes and/or eliminates the repeated expenditure of time, battery life, and data traffic involved in performing the steps of the Access Procedure 400a by minimizing its frequency. Further, the network determines whether the UE should be configured to operate according to the Event Driven Access and Data Transmission Procedure <NUM> or the Network Configurable Access and Data Transmission Procedure <NUM>.

In <NUM>, an eNB broadcasts synchronization information. Synch information may include but is not limited to, Primary Synchronization Signals (PSS), Secondary Synchronization Signals (SSS), downlink reference signals, Master Information Block (MIB), Physical Hybrid-ARQ Indicator Channel (PHICH) configuration, System Frame Number, QPSK modulation, cell-specific scrambling, basic network data, and the like. In <NUM>, one or more UE receives the eNB broadcasted synchronization information. The eNB broadcasted synchronization information may be received directly from the eNB or from another device.

At <NUM>, the UE initiates the Access Procedure 400a by sending a Chirp, which may include the UE ID, Buffer Status Report, Random Access Channel Reference Signal (RACH-RS), and/or the like. The eNB receives the Chirp either directly from the UE or from another device. In a Network Configurable Access and Data Transmission Procedure <NUM>, the network configures when and if Access Procedure 400a is performed. For example, the network may configure the UE to initiate the Access Procedure 400a upon the UE powering up, upon the UE entering a new cell, upon the UE entering a new zone, upon the UE entering a new network, and/or upon the expiration of a predetermined period of time, x, which is set by the network. Methodology the network uses to set the predetermined time period will be discussed below with reference to <FIG>.

In embodiments, the eNB may not have network resources available at the time the Chirp is received. For example, the eNB may not have an UL channel available at the time the UE sends the Chirp. In such a circumstance, the eNB has the option respond to the Chirp by sending a KA message to the UE indicting that the eNB is willing to receive the data but does not currently have the resources available (optional 403a). Upon network resources becoming available, the eNB may proceed to <NUM> wherein the eNB creates and sends the Connection Setup.

At <NUM>, in response to receiving the Chirp, the eNB creates and sends a Connection Setup, which may include network information, such as but not limited to, a Cell ID, a Timing Advance (TA), a Modulation and Coding Scheme (MCS), Channel State Information (CSI), a UL assignment, and/or the like. SIB information may also be sent to the UE. In embodiments, the SIB information may be sent in a separate transmission subsequent to the transmission that included the Cell ID, TA, MCS, CSI, etc. The UE may receive the Connection Setup directly from the eNB or from another device.

In <NUM>, the UE saves access data for future transmissions. Preferably, the saved access data is system, information that is unlikely to change for the predetermined period of time (e.g. an hour, a day, days, weeks, years, and the like) such as the Cell ID, the TA, the MCS, a resource configuration within the SIB, and/or the like. An uplink and downlink assignment is likely to change during the predetermined period of time, so the uplink and downlink assignment may be omitted from the saved access data. In some embodiments, such as UEs operating in a network that allocates zone specific resources and/or UEs sending small data, <NUM> may choose to exclude the TA from the saved access data. In these circumstances, the TA may be omitted from the saved access data because the TA may not be needed to transfer data at a later time. Steps <NUM>-<NUM> may be referred to as the UE's Access Procedure 400a, and the information saved during the Access Procedure 400a may be used by the UE at a later time to transmit data to the eNB.

As explained above, the network configures when and if the Access Procedure 400a is performed. If the network has configured the Access Procedure 400a to be performed upon expiration of a predetermined period of time, x, then at <NUM>, the predetermined period of time begins. As explained above, the saved access data is saved for future use, and is unlikely to change during the predetermined period of time. As such, the predetermined period of time, x, is set to match the expected life span of the saved access data. For example, if the access data is expected to become stale after an hour, then x is set to one hour or less. If the access data is expected to become stale after a day, x is set to one day or less. The network is free to configure x to be any value and preferably is set to match the expected life span of the saved access data.

<NUM> monitors whether the predetermined period of time has expired. At the expiration of the predetermined period of time, the method moves to <NUM> and the Access Procedure 400a is repeated in order to refresh the saved access data. Prior to the predetermined period of time expiring, the UE may perform any number of operations including but not limited to transitioning into an Idle state or Standby mode.

Among the aforementioned operations the UE performs one or more Data Transmission Procedure 400b to be performed before the expiration of the predetermined period of time. At <NUM>, the UE decides to send data to the network, which initiates the Data Transmission Procedure 400b. While the Data Transmission Procedure 400b is used to send several different types of data, small data is particularly suitable for transmission via Data Transmission Procedure 400b. Small data is a data packet that is comparatively smaller in size than a typical data packet. For example, small data may be limited to <NUM>-<NUM> bits while a typical data packet may range in size from <NUM>-<NUM> of bits. Because the small data has comparatively less bits than traditional data, small data may include a comparatively smaller payload and a comparatively smaller overhead. For example, small data may be limited to the small data payload and UE ID. Because small data is comparatively smaller than typical data packets, collisions and data loss are of less concern. Thus, small data may safely be treated differently from typical data packets. Further, small data may involve a data packet that the UE desires to send but to which no connection setup is desired. For example, small data may be time sensitive readings of the UE that are scheduled to be reported to the eNB, but to which no eNB response, other than an ACK/NACK response, is desired. In a more specific example, the UE may be configured to send a water meter reading every hour, but other than an ACK/NACK, desires no response from the network regarding the water meter reading. Because the UE desires no response, a two way connection between the UE and eNB is not necessary at the time the small data is sent. As such, it is desirable for the UE to send small data to the eNB without expending time or battery life establishing a two way connection, for example the two way connection required for a voice call or to browse the internet.

The Data Transmission Procedure 400b, e.g., steps <NUM>-<NUM>, sends data (e.g., small data) more quickly and efficiently as compared a traditional uplink of data sent in a two way communication between the UE and eNB. In embodiments, the Data Transmission Procedure 400b may be performed substantially more often than the Access Procedure 400a. For example, the UE may be configured to take interval readings (e.g., in <NUM> minute intervals, <NUM> minute intervals, hourly, and the like) and/or take readings in response to an event (e.g., when a door opens, when a light is turned on or off, when a TV or radio channel is changed) and report the readings using the Data Transmission Procedure 400b while in comparison, the Access Procedure 400a is only performed after expiration of an extended period of time (e.g., a day, days, a week, weeks, and the like).

In <NUM>, the UE decides to send a data transmission. The method then moves to <NUM>, which is similar to <NUM>. In <NUM>, the UE receives the synchronization information that the eNB is broadcasting at that time. The synchronization information may include but is not limited to, Primary Synchronization Signals (PSS), Secondary Synchronization Signals (SSS), downlink reference signals, Master Information Block (MIB), Physical Hybrid-ARQ Indicator Channel (PHICH) configuration, System Frame Number, QPSK modulation, cell-specific scrambling, basic network data, frame boundary, and/or the like.

In <NUM>, the data is transmitted. The UE uses the current synchronization information and at least a portion of the saved access information to send an I-Chirp comprising the data payload to the eNB. Preferably, the I-Chirp is small data including the data payload and UE-ID. If the UE decides to send another transmission before the predetermined time period expires, steps <NUM>-<NUM> are repeated without repeating Access Procedure 400a. Further, once <NUM> determines the predetermined period of time has expired, the method returns to <NUM> and the Access Procedure 400a is repeated in order to refresh the saves access data.

Optionally, the eNB may generate and send an ACK/NACK message in response to the I-Chirp. If this option is exercised, then upon receiving a NACK, the UE may repeat <NUM>, until an ACK is received, until a NACK time period has expired, and/or until a threshold number of attempts have been made.

As explained, Data Transmission Procedure 400b is repeated several times using some or all of the access data previously saved during <NUM>. Traditionally, a Random Access Procedure and two way connection setup is performed every time a data transmission is desired. Thus, the traditional procedure consumes substantial time, battery life, and data traffic performing multiple Random Access Procedures throughout the day. Method <NUM> performs its Access Procedure 400a once during a predetermined time period (e.g., once an hour, once a day, once a week, or the like) and reuses the access data saved from the previously performed Access Procedure 400a for each Data Transmission Procedure 400b performed during that predetermined time period. Thus, method <NUM> minimizes and/or prevents the repeated consumption of time, battery life, and data traffic during that time period.

<FIG> is an example Network Configurable Access and Data Transmission Procedure useful for mobile terminated (MT) data transfers, which is designed to reduce the Access Procedure's 500a frequency thereby allowing several of the steps to be omitted when appropriate. Method <NUM> is split into two procedures: the Access Procedure 500a, which is performed once during a predetermined time period (e.g., once a minute, once an hour, once a day, once a week, or the like) and the Data Transmission Procedure 500b, wherein multiple data transmissions are conducted using and reusing access data saved during Access Procedure 500a until the predetermined time period expires. When the predetermined time period expires, the Access Procedure 500a is performed again to refresh the saved access data. As such, method <NUM> minimizes and/or eliminates the repeated expenditure of time, battery life, and data traffic involved in the steps of the Access Procedure 500a by minimizing its frequency. Further, the network determines whether the UE should be configured to operate according to the Event Driven Access and Data Transmission Procedure <NUM> or the Network Configurable Access and Data Transmission Procedure <NUM>.

In method <NUM>, the Access Procedure 500a performs the same steps as those disclosed in Access Procedure 400a. Further, in <NUM>, the method <NUM> monitors whether the predetermined period of time has expired. At the expiration of the predetermined period of time, the method repeats Access Procedure 500a. Prior to the predetermined period of time expiring, the UE may perform any number of operations including by not limited to transitioning into an Idle state or Standby mode.

Among the aforementioned operations the UE may perform before the expiration of the predetermined period of time is Data Transmission Procedure 500b. At <NUM>, the eNB decides to send data to the UE, which initiates Data Transmission Procedure 500b.

In <NUM>, the eNB sends a Keep Alive (KA) message to the UE alerting the UE that a downlink (DL) transmission will soon be sent. The eNB may wait for Chirp or KA occasion before sending the KA message in <NUM>. In <NUM>, the UE listens for the DL transmission. Upon receiving the DL transmission, the UE decodes the DL transmission at least using some or all of the access data saved during the Access Procedure 500a such as the cell ID.

Data Transmission Procedure 500b may be repeated several times prior to expiration of the predetermined time period using at least some or all of the access data saved during Access Procedure 500a. Traditionally, a Random Access Procedure and two way connection setup is performed every time the eNB decides to send a data transmission. Thus, the traditional procedure consumes substantial time, battery life, and data traffic performing multiple Random Access Procedures throughout the day. Method <NUM> performs its Access Procedure 500a once during a predetermined time period (e.g., once a minute, once an hour, once a day, once a week, or the like) and reuses the access data saved from the previously performed Access Procedure 500a for each Data Transmission Procedure 500b performed during that predetermined time period. Thus, method <NUM> minimizes and/or prevents the repeated consumption of time, battery life, and data traffic during that time period.

<FIG> illustrate various methods for data transmission. As mentioned above, the network determines whether at any particular time one or more particular UEs should be configured to operate according to the Event Driven Access and Data Transmission Procedure <NUM> or the Network Configurable Access and Data Transmission Procedures <NUM> and <NUM>. <FIG> shows an example flow diagram of method <NUM>, wherein the network determines which configuration is appropriate for a particular UE at a particular time and then configures the manner in which the UE will send Mobile Originated (MO) data transmissions and receive Mobile Terminated (MT) data transmissions based on that determination.

In <NUM>, a UE comes into communication with a new wireless communication network. In examples, the UE may be powered on or otherwise move into an area covered by a different communication network. In <NUM>, the method determines whether the UE is a mobile UE or a non-mobile UE. If the UE is determined to be a non-mobile UE, the method moves to <NUM>, wherein the UE is configured to perform data transmissions according to the methods disclosed in <FIG> and <FIG>. Further, <NUM> sets the predetermine period of time, x. Because the UE is a non-mobile device, the saved access data of Access Procedures 400a and 500a is expected to have a long life span. Thus, x is set to be a high value thereby minimizing the number of time the Access Procedure 400a or 500a is performed. For example, x may be set as high as <NUM> hours, <NUM> hours, once a week, or the like. In <NUM>, the network has the option of configuring the UE to ignore Timing Advances (TA) and/or MCS when sending data transmissions. If desired, the network may configure the UE to ignore TA and/or MCS contingent on the type of data being transferred (e.g., TA may be ignored when transmitting small data). The UE remains in this configuration until the UE leaves the serving network ( <NUM>) and connects to a new network ( <NUM>).

If <NUM> determines that the UE is a mobile UE, the method moves to <NUM>, wherein the system determines the allocation granularity of the network resources. For example, some networks allocate cell specific resources and other networks allocate zone specific resources. In a network that allocates cell specific resources, assigned resources of a first cell are not used when communicating with a second cell. For example, each cell would send a UE a different SIB. In contrast, in a network that allocates zone specific resources, a plurality of cells share resource allocations. As such, zone specific resources are shared by a plurality of cells such that zone allocated resources can be used by a UE to communicate with any or a plurality of the cells within the zone. For example, the UE could communicate with a first cell and a second cell using the same SIB information.

If <NUM> determines that the network allocates cell specific resources, the method moves to <NUM>, wherein the UE is configured to perform data transmissions according to the method disclosed in <FIG>. The UE remains in this configuration until the UE leaves the serving network ( <NUM>) and connects to a new network ( <NUM>).

If <NUM> determines that the network allocates zone specific resources, the method moves to <NUM>, wherein the UE is configured to perform data transmissions according to the methods disclosed in <FIG> and <FIG>. Further, <NUM> sets the predetermine period of time, x. Because the UE is a mobile device, the saved access data of Access Procedures 400a and 500a is expected to have a life span that is shorter as compared to a non-mobile device. Further, the system may set the predetermined time period, x, of Access Procedure 400a to be different from the predetermined time period, x, of Access Procedure 500a. Again, the system sets x according to the expected life span of the saved access data. The saved access data of Access Procedure 400a may have a longer expected life span than that of the saved access data of Access Procedure 500a, for example because systems desire that MT data have less latency. Thus, in embodiments, x of Access Procedure 400a may be set at a moderately high value such as <NUM> hour, <NUM> hours, <NUM> hours, or the like while x of Access Procedure 500a may be set at seconds, minutes or the like. Thus, x is set to a value that balances latency expectations with the minimization of the number of times the Access Procedure 400a or 500a is performed. In <NUM>, the network has the option of configuring the UE to ignore TA and/or MCS when sending data transmissions. If desired, the network may configure the UE to ignore TA and/or MCS contingent on the type of data being transferred (e.g., TA may be ignored when transmitting small data). The UE remains in this configuration until the UE leaves the serving zone ( <NUM>). Upon the UE leaving the serving zone, the system determines whether the UE left the serving network ( <NUM>). If the UE remains in the serving network after leaving the serving zone, the system configures the UE to perform to <FIG> and <FIG> and set x in light of the new serving zone's resource allocations ( <NUM>). If, in <NUM>, the UE left the serving network and connects to a new network ( <NUM>), the system moves to <NUM>. A UE may be configured and reconfigured multiple times as it moves from one zone and/or network to another.

In an alternative embodiment to <FIG>, a UE may be preconfigured, wherein the access information (e.g., SIB) is preconfigured and stored in the UE. When the UE is preconfigured with saved access data, the Access Procedure 400a and 500a may be skipped because the UE already has the access data stored therein. For example, the UE may be preconfigured with SIB information that is compatible with the network to which it is expected to communicate. An example UE is a thermostat, which is expected to be installed at a particular location (e.g., address). Because the access data useful to communicate with the network serving that UE at that particular location will be know prior to installation, the thermostat may be preconfigured with the known access information (e.g. SIB). In such an embodiment, the thermostat may skip Access Procedures 400a and 400b and simply send and receive data using the preconfigured access data and Data Transmission Procedures 400b and 500b.

The functional blocks and modules in <FIG> may comprise processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof.

Claim 1:
A method for transmitting data, the method being performed by a UE (<NUM>) and comprising:
receiving a configuration from a network serving the UE (<NUM>), wherein the configuration configures the UE (<NUM>) to perform data transmissions and at least comprises a predetermined time period;
initiating an access procedure by sending (<NUM>) a chirp to the network;
receiving (<NUM>) at least a portion of UE access data from the network and saving (<NUM>) said received UE access data;
utilizing at least a portion of the saved UE access data to send more than one data transmission;
determining (<NUM>) that a predetermined time period has expired, wherein the predetermined time period is associated with the saved UE access data;
based on the determining, refreshing the saved UE access data by repeating the access procedure;
determining (<NUM>) whether the UE (<NUM>) is mobile;
determining (<NUM>) a resource allocation granularity of the network serving the UE (<NUM>); and
based at least on the mobility determination and the resource allocation granularity determination, setting the predetermined time period based on an expected life span of the saved UE access data in accordance with a configuration received from the network.