US9363819B2 - Machine to machine (M2M) frame within a frame - Google Patents

Machine to machine (M2M) frame within a frame Download PDF

Info

Publication number
US9363819B2
US9363819B2 US13/984,270 US201213984270A US9363819B2 US 9363819 B2 US9363819 B2 US 9363819B2 US 201213984270 A US201213984270 A US 201213984270A US 9363819 B2 US9363819 B2 US 9363819B2
Authority
US
United States
Prior art keywords
allocating
processor
base station
preamble
zone
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.)
Expired - Fee Related, expires
Application number
US13/984,270
Other languages
English (en)
Other versions
US20140029568A1 (en
Inventor
Lei Wang
Ronald G. Murias
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings 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
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Priority to US13/984,270 priority Critical patent/US9363819B2/en
Assigned to INTERDIGITAL PATENT HOLDINGS, INC. reassignment INTERDIGITAL PATENT HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MURIAS, RONALD G., WANG, LEI
Publication of US20140029568A1 publication Critical patent/US20140029568A1/en
Application granted granted Critical
Publication of US9363819B2 publication Critical patent/US9363819B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H04W72/087
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J1/00Frequency-division multiplex systems
    • H04J1/02Details
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/16Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1694Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037Inter-user or inter-terminal allocation
    • H04L5/0039Frequency-contiguous, i.e. with no allocation of frequencies for one user or terminal between the frequencies allocated to another
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044Arrangements for allocating sub-channels of the transmission path allocation of payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/22Arrangements affording multiple use of the transmission path using time-division multiplexing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W56/00Synchronisation arrangements
    • H04W56/001Synchronization between nodes
    • H04W56/0015Synchronization between nodes one node acting as a reference for the others
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0473Wireless resource allocation based on the type of the allocated resource the resource being transmission power
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/541Allocation or scheduling criteria for wireless resources based on quality criteria using the level of interference
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/14Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1469Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems

Definitions

  • This application is related to wireless communications.
  • Machine to Machine (M2M) devices may use a lower complexity narrowband technology to access a frame structure within an existing wideband deployment.
  • a base station may allocate a narrow part of the spectrum specifically for M2M use.
  • a base station may manage low bandwidth M2M along with regular network use, while the M2M devices may be made less complex and with lower power consumption and lower cost than full-band devices.
  • M2M devices that process narrow band radio frequency (RF) channels may be referred to as Narrow-Band M2M (NB-M2M) Devices.
  • M2M devices may belong to one of the following three classes based on their capability of band processing: (1) Narrow-band only M2M devices that may only process narrow band (e.g., 1.25 MHz or 1.08 MHz); (2) Wide-band only M2M devices; or (3) Capable of processing both narrow-band and wide-band, but one at a time, i.e. configurable where the wide-band capability may be limited to some specific cases. For example, 2994298-1 an M2M device capable of processing both narrow-band and wide-band may use wide-band for network entry.
  • base station (BS) support for NB-M2M operations may include the following: (1) a BS scheduler may allocate the M2M regions to meet the quality of service (QoS) requirements for M2M traffic and also to minimize the impact on non-M2M devices; (2) a BS may provide NB-M2M region specific PHY support, (for example, NB-M2M region PHY synchronization signals, downlink/uplink (DL/UL) control signals, such as MAPs, UL ranging and feedback, and data bursts); and (3) a BS may provide the NB-M2M device specific MAC support to improve the system efficiency for NB-M2M operation, (for example, M2M device specific bandwidth management and allocation mechanisms, M2M device specific power saving procedures with long sleep/idle intervals).
  • the BS may be a logical node in wireless communication systems that facilitates wireless communication between a subscriber station (SS)/wireless transmit/receive unit (WTRU) and a network.
  • a method for use in a wireless communications system includes transmitting M2M signals in an allocated narrow portion of bandwidth in a wideband structure, wherein the allocated portion of the bandwidth is allocated to narrow band M2M (NB-M2M) devices using a low complexity narrowband technology to access a frame structure within an existing wideband deployment.
  • NB-M2M narrow band M2M
  • FIG. 1A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1B is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A ;
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram of an example radio access network and an example core network that may be used within the communications system illustrated in FIG. 1A ;
  • FIG. 2 is an example of M2M frame-within-a-frame for LTE
  • FIG. 3 is an example of 802.16e OFDMA TDD frame structure with only mandatory zone
  • FIG. 4 is an example of 802.16e TDD frame structure with NB-M2M region allocated in AMC zone;
  • FIG. 5 is an example of 802.16e TDD frame structure with NB-M2M region allocated in AMC zone with FCH included in the NB-M2M region;
  • FIG. 6 is a table of 128 FFT OFDMA AMC subcarrier allocations
  • FIG. 7 is an example of 802.16m TDD frame supporting legacy 802.16e operation.
  • FIG. 8 is an example of 802.16m with wireless MAN-OFDMA legacy frame operating for NB-M2M.
  • FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102 a , 102 b , 102 c , 102 d , a radio access network (RAN) 104 , a core network 106 , a public switched telephone network (PSTN) 108 , the Internet 110 , and other networks 112 , though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • Each of the WTRUs 102 a , 102 b , 102 c , 102 d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102 a , 102 b , 102 c , 102 d may be configured to transmit and/or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and the like.
  • the communications systems 100 may also include a base station 114 a and a base station 114 b .
  • Each of the base stations 114 a , 114 b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102 a , 102 b , 102 c , 102 d to facilitate access to one or more communication networks, such as the core network 106 , the Internet 110 , and/or the networks 112 .
  • the base stations 114 a , 114 b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114 a , 114 b are each depicted as a single element, it will be appreciated that the base stations 114 a , 114 b may include any number of interconnected base stations and/or network elements.
  • BTS base transceiver station
  • AP access point
  • the base station 114 a may be part of the RAN 104 , which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114 a and/or the base station 114 b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown).
  • the cell may further be divided into cell sectors.
  • the cell associated with the base station 114 a may be divided into three sectors.
  • the base station 114 a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114 a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • the base stations 114 a , 114 b may communicate with one or more of the WTRUs 102 a , 102 b , 102 c , 102 d over an air interface 116 , which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114 a in the RAN 104 and the WTRUs 102 a , 102 b , 102 c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1 ⁇ , CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1 ⁇ , CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • the base station 114 b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like.
  • the base station 114 b and the WTRUs 102 c , 102 d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • the base station 114 b and the WTRUs 102 c , 102 d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • WPAN wireless personal area network
  • the base station 114 b and the WTRUs 102 c , 102 d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.
  • the base station 114 b may have a direct connection to the Internet 110 .
  • the base station 114 b may not be required to access the Internet 110 via the core network 106 .
  • the RAN 104 may be in communication with the core network 106 , which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102 a , 102 b , 102 c , 102 d .
  • the core network 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104 and/or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106 may also serve as a gateway for the WTRUs 102 a , 102 b , 102 c , 102 d to access the PSTN 108 , the Internet 110 , and/or other networks 112 .
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • the WTRUs 102 a , 102 b , 102 c , 102 d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102 a , 102 b , 102 c , 102 d may include multiple transceivers for communicating with different wireless networks over different wireless links.
  • the WTRU 102 c shown in FIG. 1A may be configured to communicate with the base station 114 a , which may employ a cellular-based radio technology, and with the base station 114 b , which may employ an IEEE 802 radio technology.
  • FIG. 1B is a system diagram of an example WTRU 102 .
  • the WTRU 102 may include a processor 118 , a transceiver 120 , a transmit/receive element 122 , a speaker/microphone 124 , a keypad 126 , a display/touchpad 128 , non-removable memory 130 , removable memory 132 , a power source 134 , a global positioning system (GPS) chipset 136 , and other peripherals 138 .
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120 , which may be coupled to the transmit/receive element 122 . While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114 a ) over the air interface 116 .
  • a base station e.g., the base station 114 a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122 . More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116 .
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122 .
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124 , the keypad 126 , and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124 , the keypad 126 , and/or the display/touchpad 128 .
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132 .
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102 , such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134 , and may be configured to distribute and/or control the power to the other components in the WTRU 102 .
  • the power source 134 may be any suitable device for powering the WTRU 102 .
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136 , which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102 .
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114 a , 114 b ) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138 , which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game
  • FIG. 1C is a system diagram of the RAN 104 and the core network 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102 a , 102 b , 102 c over the air interface 116 .
  • the RAN 104 may also be in communication with the core network 106 .
  • the RAN 104 may include eNode-Bs 140 a , 140 b , 140 c , though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 140 a , 140 b , 140 c may each include one or more transceivers for communicating with the WTRUs 102 a , 102 b , 102 c over the air interface 116 .
  • the eNode-Bs 140 a , 140 b , 140 c may implement MIMO technology.
  • the eNode-B 140 a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102 a.
  • Each of the eNode-Bs 140 a , 140 b , 140 c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. As shown in FIG. 1C , the eNode-Bs 140 a , 140 b , 140 c may communicate with one another over an X2 interface.
  • the core network 106 shown in FIG. 1C may include a mobility management gateway (MME) 142 , a serving gateway 144 , and a packet data network (PDN) gateway 146 . While each of the foregoing elements are depicted as part of the core network 106 , it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MME mobility management gateway
  • PDN packet data network
  • the MME 142 may be connected to each of the eNode-Bs 142 a , 142 b , 142 c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 142 may be responsible for authenticating users of the WTRUs 102 a , 102 b , 102 c , bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102 a , 102 b , 102 c , and the like.
  • the MME 142 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
  • the serving gateway 144 may be connected to each of the eNode Bs 140 a , 140 b , 140 c in the RAN 104 via the S1 interface.
  • the serving gateway 144 may generally route and forward user data packets to/from the WTRUs 102 a , 102 b , 102 c .
  • the serving gateway 144 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102 a , 102 b , 102 c , managing and storing contexts of the WTRUs 102 a , 102 b , 102 c , and the like.
  • the serving gateway 144 may also be connected to the PDN gateway 146 , which may provide the WTRUs 102 a , 102 b , 102 c with access to packet-switched networks, such as the Internet 110 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and IP-enabled devices.
  • the PDN gateway 146 may provide the WTRUs 102 a , 102 b , 102 c with access to packet-switched networks, such as the Internet 110 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and IP-enabled devices.
  • the core network 106 may facilitate communications with other networks.
  • the core network 106 may provide the WTRUs 102 a , 102 b , 102 c with access to circuit-switched networks, such as the PSTN 108 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and traditional land-line communications devices.
  • the core network 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN 108 .
  • the core network 106 may provide the WTRUs 102 a , 102 b , 102 c with access to the networks 112 , which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • IMS IP multimedia subsystem
  • a Machine to Machine (M2M) device may be configured to use a low complexity narrowband technology to access a frame structure within an existing wideband deployment. More specifically, a base station may be configured to allocate a narrow part of the spectrum specifically for M2M use. By embedding a narrowband structure inside a wideband structure, one base station may manage low bandwidth M2M along with regular network use, while the M2M devices may be made less complex and with lower power consumption and lower cost than full-band devices.
  • M2M Machine to Machine
  • M2M devices that process narrow band radio frequency (RF) channels may be referred to as Narrow-Band M2M (NB-M2M) Devices.
  • M2M devices may belong to one of the following three classes based on their capability of band processing: (1) Narrow-band only M2M devices that may only process narrow band (e.g., 1.25 MHz or 1.08 MHz); (2) Wide-band only M2M devices; or (3) Capable of processing both narrow-band and wide-band, but one at a time, i.e. configurable where the wide-band capability may be limited to some specific cases.
  • an M2M device capable of processing both narrow-band and wide-band may use wide-band for network entry.
  • base station (BS) support for NB-M2M operations may include the following: (1) a BS scheduler may allocate the M2M regions to meet the quality of service (QoS) requirements for M2M traffic and also to minimize the impact on non-M2M devices; (2) a BS may provide NB-M2M region specific PHY support, (for example, NB-M2M region PHY synchronization signals, downlink/uplink (DL/UL) control signals, such as, MAPs, UL ranging and feedback, and data bursts); and (3) a BS may provide the NB-M2M device specific MAC support to improve the system efficiency for NB-M2M operation, (for example, M2M device specific bandwidth management and allocation mechanisms, M2M device specific power saving procedures with long sleep/idle intervals).
  • QoS quality of service
  • the BS may be a logical node in wireless communication systems that facilitates wireless communication between a subscriber station (SS)/wireless transmit/receive unit (WTRU) and a network.
  • a logical node may be NB/eNB in 3GPP systems or BS/ABS in 802.16 systems.
  • Some existing multicarrier systems may use a fixed subcarrier spacing that may be independent of the bandwidth in use.
  • Fixed subcarrier spacing (either 15 kHz or 7.5 kHz in the case of LTE) generally means that a radio operating in a 1.25 MHz band would have subcarriers spaced the same distance apart as a radio operating in a 20 MHz band.
  • One difference between the two radios is that the radio operating in the 1.25 MHz band operates with a sample rate 16 times slower than the radio operating in the 20 MHz band.
  • Another difference between the two is that the narrower band allows for a less expensive radio as well as a less complex and lower power baseband processor (e.g. 128 point FFT instead of a 2048 point FFT).
  • the preamble and synchronization process may be confined to the “center” 72 carriers, with a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (BCH) all confined to this area.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • BCH broadcast channel
  • the M2M devices are tuned to this part of the band, they may receive the same information as their full-bandwidth counterparts.
  • an M2M-specific frame structure may remain on these center carriers, while other resources can be allocated to wideband devices.
  • FIG. 2 illustrates an example of M2M frame-within-a-frame for LTE.
  • the smallest specified channel bandwidth for LTE may be 1.4 MHz; (using 6 resource blocks).
  • OFDM downlink
  • DFTS-OFDM uplink
  • M2M devices may be limited to the same inner 72 subcarriers (6 resource blocks) used for PSS 202 , SSS 204 , and BCH 206 .
  • Some higher layer frame planning may be required to allow the M2M specific frames 208 to coexist with regular data frames.
  • FIG. 3 illustrates an example of 802.16e OFDMA (Orthogonal Frequency Division Multiplexing Access) TDD (Time Division Duplex) frame structure with only mandatory zone.
  • the frames show uplink 302 , and downlink 304 , as well as the preamble 306 , DL-MAP 308 , FCH 310 , ranging channel 312 , and bursts including, for example, DL bursts 314 1-11 and UL bursts 316 1-5 .
  • a separate synchronization signal (not shown) may be required for the M2M devices because an 802.16 preamble may span the entire wide band.
  • subcarrier mapping such as Band Adaptive Modulation and Coding (Band AMC) may be used to allocate a portion of the bandwidth to narrowband M2M devices.
  • Band AMC Band Adaptive Modulation and Coding
  • the regular frame structure may be used, but once the mandatory transmissions are complete, the M2M preamble may be sent and any downlink transmissions specific to M2M devices may be identified by a special M2M MAP, followed by the data.
  • M2M uplink space within the special narrow band may be allocated by the base station and used by the M2M devices.
  • FIG. 4 illustrates an example of 802.16e TDD frame structure 400 with NB-M2M region allocated AMC zone 402 , as well as the preamble 404 , partial usage of sub-carriers (PUSC) zone 406 , full usage of sub-carriers (FUSC) 408 , and corresponding uplink PUSC and AMC zones 418 , 420 . Bursts 414 , 416 are also shown.
  • An issue that may require parameter adjustment is the subcarrier spacing used for various bandwidths in 802.16e.
  • the subcarrier spacing may not match the value for the 1.25 MHz band and changes to the parameters for these bands may be required.
  • the preamble defined for the 1.25 MHz band may be embedded within the downlink frame to allow the M2M device to synchronize to the base station in the same manner currently defined in 802.16e.
  • the M2M Ranging subchannel 412 may also be required.
  • FIG. 4 also shows an example of using a FDM (Frequency Division Multiplexing) way to accommodate both legacy wide-band traffic and narrow-band M2M traffic in an 802.16e frame.
  • FDM Frequency Division Multiplexing
  • the presence of NB-M2M traffic in an 802.16e frame may also be supported in a TDM (Time Division Mulipexing) manner or a combined FDM and TDM manner.
  • a DL NB-M2M region may be allocated in full or in any portion of an AMC zone.
  • FIG. 5 illustrates an example of 802.16e TDD frame structure 500 with NB-M2M region allocated in AMC zone with Frame Control Header (FCH) 502 included in the NB-M2M region, for example, in the M2M DL-MAP, as shown.
  • FCH Frame Control Header
  • an FCH is included in the frame to allow 802.16e narrow band mobile stations (MSs) to use this portion of the frame.
  • the BS scheduler allocates NB-M2M regions in the 802.16e OFDMA frames, as shown in the example in FIG. 4 .
  • the available air link resource to the legacy 802.16e subscriber stations (SSs)/MSs is reduced due to the introduction of the NB-M2M region.
  • SSs subscriber stations
  • such impact may be minimized by carefully scheduling such NB-M2M regions.
  • the non-M2M traffic load may be classified as high, medium, and low.
  • the non-M2M traffic load is high, during peak hours, minimum NB-M2M regions are scheduled to meet the need of transporting the delay-sensitive M2M data, such as alarm/exception reporting.
  • the non-M2M traffic load is low (e.g., midnight)
  • more NB-M2M regions are scheduled where the M2M data may be transported. Due to the long delay tolerance of select M2M applications, M2M data may be accumulated in the time-domain.
  • FIG. 6 is a table of OFDMA AMC subcarrier allocations for the narrow-band (128 bin) case, and those parameters may be applied in both the DL and in the UL.
  • the guard subcarriers are included to combat out-of-band emissions found in the typical OFDM signal. Although this may be an issue for the NB-M2M devices in the UL, the full band (all carriers except DC) may be used for the DL. This may cause an increase in spectral efficiency for the DL.
  • the NB-M2M device may have an RF front end designed to allow the full spectrum and the baseband processor must process all 128 data points.
  • the synchronization signals defined for the 128-FFT mode of 802.16e may be re-used for the NB-M2M devices.
  • the preamble series for the 128-FFT mode may be transmitted in the special NB-M2M subband.
  • the NB-M2M preamble is transmitted as the first NB-M2M symbol in the allocated NB-M2M region (see FIG. 4 ).
  • the NB-M2M device uses the same mechanism defined for 802.16e 128-FFT devices.
  • the location of the ranging channel is communicated to the NB-M2M MS through the NB-M2M UL MAP.
  • one of the embodiments for the 802.16e BS MAC may support the NB-M2M.
  • the MAC design including MAC PDU, MAC control signals, MAC protocols, function modules and MAC procedures, may be used for the BS to support the NB-M2M devices with the traffic in the newly proposed NB-M2M regions.
  • the enhanced NB-M2M specific MAC designs and features may be introduced in an incremental manner at the 802.16e BS to improve the NB-M2M operation for the traffic in the NB-M2M region, with a proper capability negotiation between the BS and the NB-M2M devices.
  • a first MAC may support small-size MAC headers, extended headers, and control messages. For example, design a compressed MAC header format and MAC control messages just for M2M traffic only, (i.e. remove all the unnecessary fields for 802.16e legacy traffic).
  • a second MAC may use NB-M2M Specific MAC addresses and identifiers. For example, using time-division to activate different groups of M2M devices so that the number of simultaneously active M2M devices can be reduced, thus resulting in a smaller size of address field and/or identifiers. Some address translation/mapping mechanisms can be considered to maintain the correspondences between the original but long addresses/identifiers and the compressed addresses/identifiers used at the MAC layer for the active M2M devices.
  • a third MAC may use enhanced power saving mechanisms. For example, allowing long sleep/idle intervals, requiring no or minimal paging, introducing new subscriber states and state machines just for M2M devices.
  • a fourth MAC may use enhanced network reentry procedure for M2M devices. For example, allowing different handlings for the M2M device resource retention timer so that the M2M device context information can be retained at the BS/network with long inactive time periods.
  • a fifth MAC may use enhanced random accesses for initial ranging, handover (HO) ranging, periodic ranging, and contention-based UL bandwidth request.
  • periodic ranging may be skipped or minimized due to highly concentrated data bursts from a M2M device during normal M2M operation.
  • HO ranging may be skipped or minimized due to the consideration of M2M devices being fixed in location for certain M2M applications.
  • a sixth MAC may use enhanced UL bandwidth request/grant procedures for NB-M2M devices. For example, using a highly coordinated way between the network entry/reentry procedure and UL bandwidth request/grant procedure under the consideration that most UL traffic from M2M devices is during a short active period following network entry/re-entry.
  • the resources may be allocated in the form of n symbols*m subchannels rectangle by DL MAP IEs.
  • the resources are allocated by UL MAP IEs in the form of number of UL resource slots (e.g x symbols*1 subchannel, where x depends on the UL permutations zones).
  • the DL/UL MAPs may be transmitted to and decoded by all the SSs/MSs, which means all the SSs/MSs know the sizes and locations of the DL/UL allocations.
  • the 802.16e MSs/SSs may be designed to skip the DL/UL allocations that are not destined to them, and also in DL the 802.16e MSs/SSs may be designed to skip the DL allocations that they cannot receive/decode correctly.
  • FIG. 7 illustrates an example of 802.16m TDD frame supporting 802.16e operation.
  • the Advanced Air Interface frames 704 support the WirelessMAN-OFDMA for 5 MHz, 10 MHz, 20 MHz channel bandwidths, all AAI subframes in the Advanced Air Interface DL Zone 708 are type-1 AAI subframes.
  • the number of symbols in the first WirelessMAN-OFDMA DL Zone 710 is 5+6 ⁇ (FRAME_OFFSET ⁇ 1).
  • all AAI subframes in the Advanced Air Interface DL Zone 708 are type-1 AAI subframes.
  • the number of symbols in the first WirelessMAN-OFDMA DL Zone 701 may be 3+6 ⁇ (FRAME_OFFSET ⁇ 1) for 8.75 MHz and 9+6 ⁇ (FRAME_OFFSET ⁇ 1) for 7 MHz.
  • the maximum value of parameter K is equal to the number of DL AAI subframes minus two.
  • the minimum value of FRAME_OFFSET shall be two for 8.75 MHz channel bandwidth, and the minimum value of FRAME_OFFSET shall be one for other bandwidths.
  • a subset of DL AAI subframes may be dedicated to the WirelessMAN-OFDMA operation to enable one or more WirelessMAN-OFDMA DL zones 710 .
  • the subset may include the first WirelessMAN-OFDMA DL zone 710 to support the transmission of the preamble, FCH and MAP.
  • the subset of DL AAI subframes dedicated to the WirelessMAN-OFDMA operation may comprise either one group of contiguous DL AAI subframes or two separate groups of contiguous DL AAI subframes.
  • the second group may include the last DL AAI subframe.
  • Data bursts for the R1 MSs may not be transmitted in the DL AAI subframes for operation of the Advanced Air Interface.
  • Those DL AAI subframes shall be indicated as a DL time zone by transmitting an STC_DL_ZONE_IE( ) with the Dedicated Pilots field set to 1 in the DL-MAP messages.
  • DL/UL MAPs and bursts for AMS may be scheduled in either zone (Advanced Air Interface DL Zone 708 or WirelessMAN-OFDMA DL Zone 710 ) according to the mode (Advanced Air Interface or WirelessMANOFDMA) with which the AMS is connected to the ABS, but shall not be scheduled in both zones in the same frame.
  • zone Advanced Air Interface DL Zone 708 or WirelessMAN-OFDMA DL Zone 710
  • mode Advanced Air Interface or WirelessMANOFDMA
  • the following configurations may be applicable.
  • FDM mode a group of subcarriers (subchannels), spanning the entire UL transmission, is dedicated to the WirelessMAN-OFDMA operation.
  • the remaining subcarriers denoted the Advanced Air Interface UL subchannels group and forming the Advanced Air Interface UL AAI subframes, are dedicated to the Advanced Air Interface operation.
  • ABS shall transmit TLV 157 of the UCD i.e., “UL allocated subchannels bitmap” for MSs to recognize the available subchannels.
  • Available subchannels for R1 MSs shall be logically contiguous in terms of subchannel index and shall not be allocated for AMSs.
  • Data bursts from the R1 MSs may not be transmitted in the UL subchannels group for operation of the Advanced Air Interface.
  • Control channels and bursts for AMS may be scheduled in either group of UL subchannels (group of UL subchannels for Advanced Air Interface or WirelessMAN-OFDMA) according to the mode (Advanced Air Interface or WirelessMAN-OFDMA) with which the AMS is connected to the ABS, but may not be scheduled in both groups in the same frame.
  • FIG. 8 is an example of an 802.16m with wireless MAN-OFDMA legacy frame operating for NB-M2M. While the legacy mode in 802.16m is defined for use of the full bandwidth, a narrow band portion as shown in FIG. 8 may be used to insert a legacy frame for NB-M2M devices while the remaining bandwidth is used for 802.16m devices. This is similar to the technique used for 802.16e systems, except the NB-M2M allocation is accommodated by allocating a time/frequency block with a narrow bandwidth, treating that block as a narrowband 802.16e UL/DL area, and simultaneously using the remaining bandwidth for 802.16m communications. Any control structures or other system definitions prescribed for the 802.16e version may apply to the WirelessMAN-OFDM mode of 802.16m.
  • Another alternative may define a narrowband 802.16m configuration, similar to what was done in 802.16e for the 128-FFT, and allocate a portion of the frame for an NB-M2M structure, again, similar to what was done for 802.16e. While this option requires more structural additions to 802.16m, it would allow a “pure” 802.16m system without the need for legacy support.
  • the 802.16m Advanced Mobile Station may be designed to skip the DL/UL allocations that are not destined to it.
  • the NB-M2M devices transmit and receive in a narrowband channel, e.g., 1.25 MHz, and are designed to be cost-effective and power-efficient for the M2M applications with low data traffic and small data bursts.
  • the NB-M2M devices may be supported in some existing wideband wireless access systems, such as, 802.16e, 802.16m, and 3GPP LTE/LET-A, in addition to NB-M2M access systems.
  • the following discusses the NB-M2M devices supported in the existing wideband wireless access systems, including but not limited to 802.16e, 802.16m, and 3GPP LTE/LTE-A.
  • the NB-M2M devices as a new subscriber type in the 802.16p systems are proposed. Since both 802.16e OFDMA systems and 802.16m systems are considered as baseline systems for the 802.16p development, the proposed NB-M2M devices need to be supported in the 802.16e-based 802.16p systems and the 802.16m-based 802.16p systems.
  • the NB-M2M devices may transmit and receive in the NB-M2M regions as allocated by the BS, as shown in the example in FIG. 4 .
  • the NB-M2M devices may be designed to process the radio frames with discontinuous DL areas (frequency domain*time domain) that they may or may not receive/decode correctly and discontinuous UL areas that they may or may not transmit.
  • the NB-M2M devices may support the subscriber side narrowband PHY design and processing, to communicate with the BS in the NB-M2M region as described above.
  • the NB-M2M devices may support the 802.16 MAC design and procedures for the basic support of NB-M2M operation in 802.16p systems.
  • the NB-M2M devices may support the capability negotiation signaling and procedures with the BS to initialize any NB-M2M specific MAC enhancements as described above.
  • the NB-M2M devices can also support the MAC enhancements as described above.
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
  • a method for use in a wireless communication system comprising allocating a narrowband structure inside of a wideband structure to access a frame structure, wherein the narrowband structure is allocated using a base station such that the narrowband structure includes spectrum for Machine-to-Machine (M2M) communications.
  • M2M Machine-to-Machine
  • the narrowband structure is allocated to satisfy quality of service (QoS) requirements for M2M communications and to minimize impact on other devices in the wireless communication system.
  • QoS quality of service
  • FCH Frame Control Header
  • a method for use in a wireless communications system comprising: transmitting M2M signals, the signals are transmitted in an allocated narrow portion of bandwidth in a wideband structure, wherein the allocated portion of the bandwidth is allocated to narrow band M2M (NB-M2M) devices using a low complexity narrowband technology to access a frame structure within an existing wideband deployment.
  • NB-M2M narrow band M2M

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
US13/984,270 2011-02-09 2012-02-09 Machine to machine (M2M) frame within a frame Expired - Fee Related US9363819B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/984,270 US9363819B2 (en) 2011-02-09 2012-02-09 Machine to machine (M2M) frame within a frame

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201161441119P 2011-02-09 2011-02-09
PCT/US2012/024472 WO2012109439A1 (fr) 2011-02-09 2012-02-09 Trames imbriquées de machine à machine (m2m)
US13/984,270 US9363819B2 (en) 2011-02-09 2012-02-09 Machine to machine (M2M) frame within a frame

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/024472 A-371-Of-International WO2012109439A1 (fr) 2011-02-09 2012-02-09 Trames imbriquées de machine à machine (m2m)

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/150,479 Continuation US20160255636A1 (en) 2011-02-09 2016-05-10 Machine to machine (m2m) frame within a frame

Publications (2)

Publication Number Publication Date
US20140029568A1 US20140029568A1 (en) 2014-01-30
US9363819B2 true US9363819B2 (en) 2016-06-07

Family

ID=45607835

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/984,270 Expired - Fee Related US9363819B2 (en) 2011-02-09 2012-02-09 Machine to machine (M2M) frame within a frame
US15/150,479 Abandoned US20160255636A1 (en) 2011-02-09 2016-05-10 Machine to machine (m2m) frame within a frame

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/150,479 Abandoned US20160255636A1 (en) 2011-02-09 2016-05-10 Machine to machine (m2m) frame within a frame

Country Status (3)

Country Link
US (2) US9363819B2 (fr)
EP (1) EP2674003A1 (fr)
WO (1) WO2012109439A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9781259B1 (en) 2016-07-27 2017-10-03 At&T Intellectual Property I, L.P. Method and apparatus for asset location tracking in a communication network
US20180241495A1 (en) * 2015-07-22 2018-08-23 Samsung Electronics Co., Ltd. Method for operating iot in cellular system and system therefor
US10142905B2 (en) 2016-08-26 2018-11-27 At&T Intellectual Property I, L.P. Method and apparatus for dynamic routing of low power wide area wireless communication devices
US10212639B2 (en) 2016-07-26 2019-02-19 At&T Intellectual Property I, L.P. Method and apparatus for dynamic data path selection for narrow band wireless communication
US20220330214A1 (en) * 2007-03-07 2022-10-13 Wi-Lan Inc. Multi-band channel aggregation

Families Citing this family (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9048970B1 (en) 2011-01-14 2015-06-02 Marvell International Ltd. Feedback for cooperative multipoint transmission systems
KR20120093559A (ko) * 2011-02-15 2012-08-23 삼성전자주식회사 무선통신 시스템에서 기기 간 통신 데이터를 송수신하기 위한 장치 및 방법
WO2012131612A1 (fr) 2011-03-31 2012-10-04 Marvell World Trade Ltd. Retour de canal pour transmission multipoint coopérative
GB2491859C (en) * 2011-06-14 2021-02-17 Sca Ipla Holdings Inc Telecommunications method and system
US9504034B2 (en) * 2011-07-05 2016-11-22 Tait Limited Overlay of bearers in a radio communication system
KR101788424B1 (ko) * 2011-07-12 2017-10-19 인텔 코포레이션 사물 통신 장치들을 위한 자원 스케줄링
US9137655B2 (en) * 2011-10-07 2015-09-15 Qualcomm Incorporated Methods and apparatus for supporting peer to peer communications
WO2013068974A1 (fr) 2011-11-10 2013-05-16 Marvell World Trade Ltd. Codage cqi différentiel pour rétroaction multipoints coopérative
US9220087B1 (en) * 2011-12-08 2015-12-22 Marvell International Ltd. Dynamic point selection with combined PUCCH/PUSCH feedback
US20130194997A1 (en) * 2012-02-01 2013-08-01 Fujitsu Limited Low Power Narrowband Operation By An Endpoint
EP2842361B1 (fr) 2012-04-27 2019-03-27 Marvell World Trade Ltd. Transmission multipoint coordonnée (comp) entre des stations de base et des terminaux de communication mobiles
US9622230B2 (en) * 2012-05-17 2017-04-11 Qualcomm Incorporated Narrow band partitioning and efficient resource allocation for low cost user equipments
GB2502274B (en) * 2012-05-21 2017-04-19 Sony Corp Telecommunications systems and methods
CN103442438B (zh) * 2012-07-23 2017-04-12 英特尔公司 用于隧道通用寻呼消息的装置和方法
US9124377B2 (en) 2012-11-07 2015-09-01 Qualcomm Incorporated Methods and apparatus for enabling peer-to-peer (P2P) communication in LTE time division duplex (TDD) system
GB2510141A (en) 2013-01-24 2014-07-30 Sony Corp Mobile communications network including reduced capability devices
GB2510137A (en) * 2013-01-24 2014-07-30 Sony Corp Mobile communications network including reduced capability devices
EP2984898B1 (fr) * 2013-04-10 2019-11-27 Telefonaktiebolaget LM Ericsson (publ) Procédé et dispositif sans fil pour assurer une communication de dispositif à dispositif
US9241340B2 (en) * 2014-01-23 2016-01-19 Humax Holdings Co., Ltd. Apparatus for scheduling in LTE machine type communication
EP2924885B1 (fr) * 2014-03-28 2020-09-16 Sony Corporation Procédé, station de base et terminal pour la détermination de caractéristiques de canal dans un système à entrées multiples et à sorties multiples cellulaires
CN104065608B (zh) * 2014-06-03 2018-01-26 北京创毅视讯科技有限公司 一种通信设备的数据处理方法及通信设备
EP3165041B1 (fr) 2014-07-04 2019-02-27 Telefonaktiebolaget LM Ericsson (publ) Gestion de fonctionnement de multiples technologies d'accès radio
WO2016026126A1 (fr) * 2014-08-21 2016-02-25 华为技术有限公司 Dispositif et procédé d'identification de cellule, procédé d'envoi de signal d'identification de cellule et dispositif de station de base
US10326546B2 (en) 2014-09-19 2019-06-18 Qualcomm Incorporated Directional synchronization signals in wireless communications
EP3035754B1 (fr) * 2014-12-18 2018-10-24 Alcatel Lucent Méthode pour l'allocation de ressources de liaison montante pour des communications mtc, sur des ressources déjà allouées à un autre appareil cellulaire
US10750464B2 (en) 2015-06-11 2020-08-18 Lg Electronics Inc. Method and apparatus for supporting time division duplex for cellular internet-of-things in wireless communication system
WO2017018966A1 (fr) * 2015-07-24 2017-02-02 Intel Corporation Structure de canal et signaux de synchronisation pour déploiements de lte à bande étroite
EP3329627A1 (fr) * 2015-07-27 2018-06-06 Intel IP Corporation Système et procédés de fonctionnement d'un système pour la lte à bande étroite destinée à l'internet des objets cellulaire
WO2017039374A1 (fr) * 2015-09-02 2017-03-09 Lg Electronics Inc. Procédé et appareil d'exécution d'une procédure d'accès aléatoire dans une porteuse nb-iot dans un système de communication sans fil
US10104629B2 (en) * 2015-12-02 2018-10-16 Verizon Patent And Licensing Inc. Narrowband synchronization and paging in long-term evolution networks
WO2017117340A1 (fr) 2015-12-30 2017-07-06 Idac Holdings, Inc. Gestion d'interférences dans une wtru multi-rat
JP6750029B2 (ja) * 2016-03-30 2020-09-02 アイディーエーシー ホールディングス インコーポレイテッド ロングタームエボリューション支援nrフレキシブル無線アクセス
HUE052050T2 (hu) * 2016-05-19 2021-04-28 Samsung Electronics Co Ltd Eljárás és berendezés átvitelre és vételre vezetéknélküli kommunikációs rendszerben, amely támogat skálázható keretszerkezetet
WO2018137213A1 (fr) * 2017-01-25 2018-08-02 华为技术有限公司 Procédé de transmission de données, dispositif terminal et dispositif de réseau
US10469159B2 (en) 2017-02-14 2019-11-05 Qualcomm Incorporated Narrowband time-division duplex frame structure for narrowband communications
US10420102B2 (en) 2017-02-15 2019-09-17 Qualcomm Incorporated Narrowband time-division duplex frame structure for narrowband communications
WO2019095188A1 (fr) 2017-11-16 2019-05-23 Qualcomm Incorporated Techniques et appareils de gestion de porteuses
WO2019193540A1 (fr) 2018-04-06 2019-10-10 Glaxosmithkline Intellectual Property Development Limited Dérivés hétéroaryles de formule (i) utilisés en tant qu'inhibiteurs d'atf4

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120176975A1 (en) * 2011-01-06 2012-07-12 Lg Electronics Inc. Method and apparatus for transmitting or receiving system information in wireless communication system
US20120178464A1 (en) * 2011-01-07 2012-07-12 Samsung Electronics Co., Ltd. Methods and apparatus to support efficient and reliable machine to machine communications

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120176975A1 (en) * 2011-01-06 2012-07-12 Lg Electronics Inc. Method and apparatus for transmitting or receiving system information in wireless communication system
US20120178464A1 (en) * 2011-01-07 2012-07-12 Samsung Electronics Co., Ltd. Methods and apparatus to support efficient and reliable machine to machine communications

Non-Patent Citations (27)

* Cited by examiner, † Cited by third party
Title
Alcatel-Lucent, M2M Communication, 3GPP TSG-RAN-WG1 Meeting #54bis, Prague, Czech Republic, Sep. 29-Oct. 3.
Draft Amendment to IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Broadband Wireless Access Systemsl Advanced Air Interface, IEEE P802.16m/D11 (Jan. 27, 2011).
Huawei Technologies Co., Ltd, The Way Forward on M2M Discussion in GERAN, 3GPP TSG GERAN #46, Jeju, South Korea, May 17-21, 2010, TDoc GP-100758.
IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Broadband Wireless Access Systems, IEEE Std. 80216-2009 (May 29, 2009).
IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems; Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1, IEEE Std 802.16e-2005 and IEEE Std 80216-2004/Cor1-2005 (Feb. 28, 2006).
Jung et al., "IEEE 802.16p Machine to Machine (M2M) System Requirements Document (SRD)," IEEE 802.16 Broadband Wireless Access Working Group, IEEE 802.16p-10/0004r3 (Sep. 29, 2011).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description (Release 10)," 3GPP TS 36.201 V10.0.0 (Dec. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description (Release 9)," 3GPP TS 36.201 V9.1.0 (Mar. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Physical Layer-General Description (Release 8)," 3GPP TS 36.201 V8.3.0 (Mar. 2009).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 10)," 3GPP TS 36.212 V10.0.0 (Dec. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 10)," 3GPP TS 36.212 V10.4.0 (Dec. 2011).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 8)," 3GPP TS 36.212 V8.8.0 (Dec. 2009).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 9)," 3GPP TS 36.212 V9.3.0 (Sep. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 9)," 3GPP TS 36.212 V9.4.0 (Sep. 2011).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 10)," 3GPP TS 36.211 V10.0.0 (Dec. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 10)," 3GPP TS 36.211 V10.4.0 (Dec. 2011).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8)," 3GPP TS 36.211 V8.9.0 (Dec. 2009).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 9)," 3GPP TS 36.211 V9.1.0 (Mar. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 10)," 3GPP TS 36.213 V10.0.1 (Dec. 2010).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 10)," 3GPP TS 36.213 V10.4.0 (Dec. 2011).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 8)," 3GPP TS 36.213 V8.8.0 (Sep. 2009).
Third Generation Partnership Project, "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 9)," 3GPP TS 36.213 V9.3.0 (Sep. 2010).
Third Generation Partnership Project, "Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications (Release 11)," 3GPP TR 23.888 V1.6.1 (Feb. 2012).
Third Generation Partnership Project, "Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications; (Release 11)," 3GPP TR 23.888 V1.0.0 (Jul. 2010).
Third Generation Partnership Project, "Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications; (Release 11)," 3GPP TR 23.888 V1.2.0 (Apr. 2011).
ZTE, Discussion on MTC Features priorities, 3GPP TSG-RAN-WG@ Meeting #69bis, Prague, Czech Republic, Sep. 29-Oct. 3.
ZTE, Discussion on MTC Features priorityes, 3GPP TSG-RAN-WG2 Meeting #69bis, Prague, Czech Republic, Sep. 29-Oct. 3.

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220330214A1 (en) * 2007-03-07 2022-10-13 Wi-Lan Inc. Multi-band channel aggregation
US20180241495A1 (en) * 2015-07-22 2018-08-23 Samsung Electronics Co., Ltd. Method for operating iot in cellular system and system therefor
US10454606B2 (en) * 2015-07-22 2019-10-22 Samsung Electronics Co., Ltd. Method for operating IoT in cellular system and system therefor
US11115145B2 (en) * 2015-07-22 2021-09-07 Samsung Electronics Co., Ltd. Method for operating IoT in cellular system and system therefor
US10212639B2 (en) 2016-07-26 2019-02-19 At&T Intellectual Property I, L.P. Method and apparatus for dynamic data path selection for narrow band wireless communication
US9781259B1 (en) 2016-07-27 2017-10-03 At&T Intellectual Property I, L.P. Method and apparatus for asset location tracking in a communication network
US10142905B2 (en) 2016-08-26 2018-11-27 At&T Intellectual Property I, L.P. Method and apparatus for dynamic routing of low power wide area wireless communication devices

Also Published As

Publication number Publication date
US20160255636A1 (en) 2016-09-01
EP2674003A1 (fr) 2013-12-18
WO2012109439A1 (fr) 2012-08-16
US20140029568A1 (en) 2014-01-30

Similar Documents

Publication Publication Date Title
US9363819B2 (en) Machine to machine (M2M) frame within a frame
US11006404B2 (en) Apparatus and method for IoT control channel
US20210345263A1 (en) Methods for flexible resource usage
US11729753B2 (en) Framing, scheduling, and synchronization in wireless systems
EP4111796B1 (fr) Planification de communications sans fil
US20240348382A1 (en) Downlink control channel in wireless systems
JP6408004B2 (ja) 未使用の無認可スペクトルを介したセルラー通信のための装置および方法
JP7574233B2 (ja) Rrc状態の間でのue支援型高速遷移
EP3764581A1 (fr) Accès radio flexible nr assisté par évolution à long terme (lte)
JP2021503224A (ja) 位相トラッキング参照信号送信
CN108141809B (zh) 用于未许可频谱中的联合传输的技术
WO2023055631A1 (fr) Duplexage par répartition dans le temps pour dispositifs sans fil à capacité réduite
US20150256249A1 (en) Apparatuses, methods, and computer programs for a receiver and a transmitter of a wireless system
CN118251868A (zh) 减轻高功率窄带干扰源影响的稳健bwp方式
EP4457964A1 (fr) Capacité de commutation de canaux de transmission en liaison montante
JP2024530917A (ja) 半二重周波数分割複信(hd-fdd)モードにおけるランダムアクセスチャネル(rach)プロシージャのためのユーザ機器(ue)アップリンク送信
CN114128204A (zh) 降低能力/复杂度nr带宽部分配置

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERDIGITAL PATENT HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, LEI;MURIAS, RONALD G.;SIGNING DATES FROM 20130910 TO 20130912;REEL/FRAME:031427/0792

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20200607