Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
  • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
  • H04L1/0007—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
  • H04L5/0033—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation each allocating device acting autonomously, i.e. without negotiation with other allocating devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0058—Allocation criteria
  • H04L5/0066—Requirements on out-of-channel emissions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/0001—Arrangements for dividing the transmission path
  • H04L5/0003—Two-dimensional division
  • H04L5/0005—Time-frequency
  • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
  • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
  • H04W52/02—Power saving arrangements
  • H04W52/0209—Power saving arrangements in terminal devices
  • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
  • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

• the Federal Communications Commission recently issued a new rule that enables a scenario for secondary (or unlicensed) users to transmit on a television (TV) band, as long as their transmissions do not affect primary users.
• the primary users on a TV band may include digital TV signals, wireless microphones, and the like.
• TVWS television white space
• the TVWS databases may contain information about the location and transmission conditions of digital TV towers.
• An unlicensed user may check the TVWS databases to obtain a list of available TVWS channels at the user's location before transmitting on the TVWS channels.
• TV band devices TV band devices
• a fixed TVBD may refer to a device that is almost always fixed at certain locations, for example, a cellular base station.
• the antenna of a fixed TVBD may be as high as 30 meters, and its transmission power may be as large as 4 watts effective isotropic radiated power (EIRP).
• EIRP effective isotropic radiated power
• a fixed TVBD may not transmit on the same channel as a channel used by TV services, or the first adjacent channel to a channel used by TV services.
• a wireless system that simultaneously operates on these bands, for example, an enhanced wireless fidelity (WiFi) system.
• a wireless system may support different types of device. For example, the devices working on an ISM band, the devices working on a TVWS band, or the devices working on both the ISM band and the TVWS band.
• the wireless system may be desirable for the wireless system to have the capability of achieving the inter-band carrier aggregation to increase the data rate, and/or to provide a higher quality of services.
• this wireless system may strictly follow all of the FCC regulations for its operation on any license-exempt band.
• a license- exempt band may be TVWS database access, TVWS channel maintenance, and the like.
• this wireless system may be built on top of an existing wireless system, for example, an IEEE 802.11 ⁇ system, with as little modifications as possible.
• a method and apparatus for a multi-anchor system to support simultaneous operation on multiple bands comprises a medium access control (MAC) entity with multiple anchors, wherein a multiple anchor carries system information for an associated band, multiple physical (PHY) layers, each of the multiple PHY layers associated with a different radio access technology, and a PHY layer selector switch, wherein the PHY layer selector switch directs the multiple anchors to one of the multiple PHY layers.
• MAC medium access control
• FIG. 1A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented;
• FigurelB 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
• Figure 1C is a system diagram of an example radio access network and an example core network that may be used within the
• Figure 2 is an example IEEE 802.11 ⁇ medium access control (MAC) data plane architecture
• Figure 3 is an example of a high level multi- anchor carrier aggregation system deployment and architecture
• Figure 4 is an example of multi-anchor access point (AP)/wireless transmit/receive unit (WTRU) architecture;
• AP multi-anchor access point
• WTRU wireless transmit/receive unit
• Figure 5 is an example of a protocol stack of a multi- anchor
• AP/WTRU with a common sensing toolbox for all physical layers (PHYs);
• Figure 6 is an example of a protocol stack of a multi- anchor
• Figure 7 is an example of MAC data plane architecture of a multi- anchor network
• Figure 8 is an example of multi-anchor AP interfaces connecting different management functional blocks
• Figure 9 is an example of multi- anchor WTRU interfaces connecting functional blocks
• Figure 10 is an example functional block diagram at a transit side of an AP
• Fi ⁇ jure 11 is an example call flow for a sensing controller
• Fi ⁇ jure 12 is an example call flow for a buffer controller
• Fi ⁇ jure 13 is an example of "Weighted Round Robin Scheme 1"
• Fi ⁇ jure 14 is an example of "Weighted Round Robin Scheme 2"
• Fi ⁇ jure 15 is an example state transition of two buffers
• Fi ⁇ jure 16 is an example of trellis buffer evolution
• Fi ⁇ jure 17 is an example call flow of a frame controller;
• Figure 18 is an example of selective band power save (SBPS);
• Figure 19 is an example of a power-save multi-poll (PSMP) sequence in SBPS;
• PSMP power-save multi-poll
• Figure 20 is an example call flow of power saving management
• Figure 21 is an example of a device dependent routing and spectrum manager (DDRSM) registration procedure
• Figure 22 is an example of a DDRSM channel allocation procedure
• Figure 23 is an example of a table in a local database
• Figure 24 is an example call flow of a PHY selector switch
• Figure 25 is an example call flow of a buffer controller at a multi- anchor WTRU.
• FIG. 1A is a diagram of an example communications syste 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) 102a, 102b, 102c, 102d, 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.
• WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
• the WTRUs 102a, 102b, 102c, 102d 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
• Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d 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 114a, 114b 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 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
• the base station 114a 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 114a and/or the base station 114b 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 114a may be divided into three sectors.
• the base station 114a may include three transceivers, i.e., one for each sector of the cell.
• the base station 114a 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 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d 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 114a in the RAN 104 and the WTRUs 102a, 102b, 102c 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 114a and the WTRUs 102a are identical to the base station 114a and the WTRUs 102a.
• E-UTRA Evolved UMTS Terrestrial Radio Access
• LTE Long Term Evolution
• LTE-A LTE-Advanced
• the base station 114a and the WTRUs 102a are identical to the base station 114a and the WTRUs 102a.
• 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
• IS-95 IS-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 114b in Figure 1A may be a wireless router, Home
• Node B, Home eNode B, or access point 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 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
• the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
• WLAN wireless local area network
• WPAN wireless personal area network
• the base station 114b and the WTRUs 102c, 102d 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 114b may have a direct connection to the Internet 110.
• the base station 114b 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 102a, 102b, 102c, 102d.
• 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
• 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.
• Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links.
• the WTRU 102c shown in Figure 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
• FIG. IB 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 106, 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 Figure IB 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 114a) over the air interface 116.
• a base station e.g., the base station 114a
• 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 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 106 and/or the removable memory 132.
• the non-removable memory 106 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 114a, 114b) 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 player
• Figure 1C is a system diagram of the RAN 104 and the core network
• the RAN 104 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
• ASN access service network
• the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 104, and the core network 106 may be defined as reference points.
• the RAN 104 may include base stations
• the RAN 104 may include any number of base stations and ASN gateways while remaining consistent with an embodiment.
• the base stations 140a, 140b, 140c may each be associated with a particular cell (not shown) in the RAN 104 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
• the base stations 140a, 140b, 140c may implement MIMO technology.
• the base station 140a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
• the base stations 140a, 140b, 140c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like.
• the ASN gateway 142 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 106, and the like.
• RAN 104 may be defined as an Rl reference point that implements the IEEE 802.16 specification.
• each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 106.
• the logical interface between the WTRUs 102a, 102b, 102c and the core network 106 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.
• the R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 100c.
• the RAN 104 may be connected to the core network 106.
• the communication link between the RAN 104 and the core network 106 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example.
• the core network 106 may include a mobile IP home agent (MIP-HA) 144, an authentication, authorization, accounting (AAA) server 146, and a gateway 148. 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.
• MIP-HA mobile IP home agent
• AAA authentication, authorization, accounting
• the MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, 102c to roam between different ASNs and/or different core networks.
• the MIP-HA 144 may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
• the AAA server 146 may be responsible for user authentication and for supporting user services.
• the gateway 148 may facilitate interworking with other networks.
• the gateway 148 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
• the gateway 148 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
• the RAN 104 may be connected to other ASNs and the core network 106 may be connected to other core networks.
• the communication link between the RAN 104 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 104 and the other ASNs.
• the communication link between the core network 106 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.
• WLAN 160 may include an access router 165.
• the access router may contain gateway functionality.
• the access router 165 may be in communication with a plurality of access points (APs) 170a, 170b.
• the communication between access router 165 and APs 170a, 170b may be via wired Ethernet (IEEE 802.3 standards), or any type of wireless communication protocol.
• AP 170a is in wireless communication over an air interface with WTRU 102d.
• a multi- anchor system operating on multiple bands simultaneously for example, ISM band, Television White Space (TVWS) high band, TVWS low band, is described herein.
• the number of anchors in an operational band may be any number up to and including the number of channels in that band. For example, there may be at most one channel per band.
• the system architecture to support the operation of multiple bands and define new functional blocks and interfaces required for such a system is described.
• a mode II portable Television Band Device is an independent device that may be a cellular HeNB or a WLAN AP.
• a mode I portable TVBD refers to a client device such as a laptop or a cell phone.
• the transmission power of portable TVBD may be less than 100 mW EIRP.
• a portable TVBD may not transmit on TV channels below 21, nor transmit on the same channel as occupied by a digital TV signal. However, a portable TVBD may transmit on the first adjacent channel to a channel used by TV services at reduced transmission power.
• Both a fixed TVBD and a mode II portable TVBD may be aware of their geo-locations and have access to TVWS database.
• a fixed TVBD or a mode II portable TVBD may retrieve a list of vacant TVWS channels from TVWS database. Furthermore, a fixed TVBD may register to the TVWS database with its device manager contact information. Besides providing TVWS channel usage information, a TVWS database may also verify the TVBD device identity (ID) to see if it really is an FCC certified device.
• ID TVBD device identity
• a portable TVBD may not transmit on TV channels below 21.
• the operational channels for a portable TVBD include TV channels 21 to 36, (i.e., TVWS low band (512 MHz to 608 MHz)), and TV channels 38 to 51, (i.e., TVWS high band (614 MHz to 698 MHz)).
• Figure 2 is an example IEEE 802.1 In MAC data plane architecture.
• a MAC service data unit may go through at least one of MSDU aggregation (A-MSDU) 205(a), frame delivery deferral during power save mode 210, sequence number assignment 215, MSDU integrity and protection 220, fragmentation 225, encryption, integrity protection 230, frame formatting 235, and MAC protocol data unit (MPDU) aggregation (A-MPDU) 240.
• MSDU aggregation A-MSDU
• frame delivery deferral during power save mode 210 sequence number assignment 215, MSDU integrity and protection 220, fragmentation 225, encryption, integrity protection 230, frame formatting 235, and MAC protocol data unit (MPDU) aggregation (A-MPDU) 240.
• MPDU MAC protocol data unit
• a received data frame may go through at least one of A- MPDU de-aggregation 280, MPDU header and cyclic redundancy check (CRC) validation 275, duplicate removal 270, MPDU decryption and integrity 265, reordering for block positive acknowledgement (ACK) 260, defragmentation 255, integrity checking 250, replay detection 245, and A-MSDU de-aggregation 205(b).
• Figure 2 shows the case for a single access category. In general, this flow may apply for each of the 4 access categories.
• WiFi technologies may be applied on TVWS channels.
• a WLAN channel defined in 802.11a/b/g/n/ac may operate on an ISM band, with each channel having a 20 MHz bandwidth.
• a digital TV channel may have a 6 MHz bandwidth.
• a TV channel may only have one-quarter (1/4) the bandwidth of an ISM channel.
• IEEE 802.11af the existing WiFi system may be downclocked for its direct operations on TV channels.
• control channel messages may be developed to be compliant with FCC regulations.
• Control channels may support intra-band carrier aggregation in a TVWS band.
• a primary carrier sense multiple access (CSMA) scheme may be used that requires transmissions on multiple TVWS channels to endure approximately the same time in order to avoid a self -jamming problem, as the N TVWS channels are within a common TVWS band.
• the transmissions on one TVWS channel may significantly interfere in the reception on another TVWS channel of the same WTRU.
• a looser requirement may be that transmissions on the primary channel end last.
• the approximate over-the-air durations on all TVWS channels may lead to MAC layer modifications of the devices, for example, by controlling the frame size based on the conditions of different channels and by optimally assigning frames to different TVWS channels.
• a wireless system may simultaneously operate on multiple bands, for example, ISM band, TVWS high band, and TVWS low band.
• the transmissions on one band may be almost independent of other bands, which may result in a single anchor channel on each operational band.
• the term simultaneously may mean occurring at the same time or that the operation is done in the same period of time, not at the exact same time.
• An enhanced wireless system is described herein with a single MAC associated with multiple independent physical layer (PHY) entities across multiple bands, for example, a multi-anchor carrier aggregation (MACA) system.
• the MACA system does not exist in the current wireless systems, for example, IEEE 802.11 ⁇ or IEEE 802.11ac where one MAC is connected to only one PHY entity.
• An overall architecture and new data plane architecture for MACA system is described herein.
• An enhanced MAC architecture with new or modified functional blocks is described herein, which may include a sensing controller, a buffer controller, a frame controller, a channel monitor, device dependent routing and spectrum manager (DDRSM), power saving management, a local database and a PHY selector switch.
• DDRSM device dependent routing and spectrum manager
• a multi-anchor wireless system for example, multi-anchor WiFi
• the channels in these bands may have different features, for example, different bandwidths, different primary user list, and the like.
• This system may aggregate the carriers from multiple bands and may support different types of devices.
• the system may also be implemented in other wireless systems such as LTE.
• LTE Long Term Evolution
• a description of the system deployment of a multi- anchor network, the architecture of multi- anchor systems, which includes MAC layer architecture and data plane architecture, the interfaces required for multi-anchor system, and the detailed descriptions of functional blocks are described herein.
• Figure 3 is an example of a high level multi-anchor carrier aggregation system deployment and architecture.
• the operating frequency of band 1 325 may be much higher than that of band 2/band 3 330.
• the operating frequency of band 2 330 may be close to that of band 3 330.
• the bandwidth of the band 1 325 channel may be larger than that of the band 2/band 3 330 channel.
• the multi-anchor system may have a single multi-anchor AP 335 and several multi-anchor WTRUs 305, 310, 315, and 320.
• the multi-anchor AP 335 may serve multi-anchor WTRUs 305, 310, 315, and 320 within its coverage area.
• the multi-anchor AP 335 may also connect to the TVWS database 345 via the Internet 340.
• the multi-anchor AP may manage all wireless communication taking place in the local area, and may aggregate bandwidth over channels of multiple-bands, for example, ISM band channel and TVWS band channels.
• the multi-anchor AP may be interconnected to external networks, such as a TVWS database through wireless wide area network (WWAN) or wireline links.
• WWAN wireless wide area network
• the multi-anchor AP may be an inter-band device, (i.e., it may operate on multiple bands, e.g., ISM band and TVWS bands), equipped with one or more sensing toolboxes and multiple radio boards.
• Each radio board may aggregate multiple carriers within its operational band. For example, the radio board in a TVWS band may aggregate 4 carriers.
• multiple anchors may serve each band; when one anchor associated with a specific band fails, the other anchors associated with the other bands assume control.
• the multi-anchor AP may take on the role of a mode II portable device, since it may have access to the TVWS database and may have a geo- location capability. Furthermore, the multi-anchor AP may also operate in a sensing only mode, which may allow the MACA system to operate in a larger subset of channels than what the TVWS database allows.
• the multi-anchor system may have multiple multi-anchor WTRUs.
• Each multi-anchor WTRU may be served by a multi-anchor AP.
• a multi-anchor WTRU may be any type of device.
• the multi-anchor WTRU may be an inter-band device, an intra-band device which may operate on TVWS bands only, or a legacy device which may operate on an ISM band only.
• a multi-anchor WTRU may be equipped with multiple radio boards, for example, 3 radio boards, 1 commercial off-the-shelf (COTS) board and 2 wideband radio boards.
• a WTRU may have one or multiple sensing toolboxes and may perform sensing operations.
• a multi-anchor WTRU may take on the role of a mode I portable device, since its operations may be managed by a multi-anchor AP as a mode II portable device.
• a multi-anchor WTRU may be either intra-band device, (i.e., may operate on a single band), or inter-band device.
• Intra-band devices may have different capabilities. For example, some intra-band devices may only operate on a single channel, while other intra-band devices may aggregate several channels within the band. Similarly, inter -band devices may have different capabilities.
• the MAC layer architecture for example, enhanced IEEE 802.11
• Figure 4 is an example of multi-anchor AP/WTRU architecture.
• N channel access functions 425, 430, and 435 may be connected to a PHY 455 through a PHY selector switch 420, and each channel access function may correspond to a unique radio band 440, 445, and450.
• the number of anchors in a band may be any number, up to and including the number of channels in that band. For example, there may be at most one anchor per band.
• An anchor may be a logical channel and may sit on a PHY channel.
• the anchor may define system information and rules of engagement of the band, including for example, but not limited to, control information, synchronization information, and the like.
• the activated number of PHY entities in one device may depend on the device capability.
• an inter-band device may consist of one MAC entity and three active anchor carriers, which may correspond to 5 active PHY entities, (one serves an ISM channel and the other four serve as TVWS channels).
• Another inter-band device may consist of two anchor carriers, for example, an ISM anchor carrier and a TVWS anchor carrier, while only one active activated PHY entity may exist in the TVWS anchor carrier.
• a CSMA scheme may be applied for accessing a band with a single channel, for example, an ISM band.
• a band connected with multiple channels for example, a TVWS high band or a TVWS low band
• Figure 5 is an example of a protocol stack of a multi-anchor
• the PHY selector switch 530 may transmit PHY channel information/status to the multi-anchor MAC 525 through a station management entity (SME) 550.
• SME station management entity
• the SME 550 may then use such PHY channel information to make channel operation decisions accordingly. Such decisions may in turn affect the physical channel selections.
• the IP 515(a), in the IP layer 510 may transmit/receive user IP packets to/from the MAC layer 525(a).
• the MAC layer 525(a) may include a PHY selector switch 530(a).
• a sensing toolbox 540(a) may be located between the data link layer 520 and the PHY layer 535.
• the sensing toolbox 540(a) may include a sensing board 545(a).
• a SME 550(a) may also be located between the data link layer 520 and the PHY layer 535.
• the IP 515(b), in the IP layer 510 may transmit/receive user IP packets to/from the MAC layer 525(b).
• the MAC layer 525(b) may include a PHY selector switch 530(b).
• a sensing toolbox 540(b) may be located between the data link layer 520 and the PHY layer 535.
• the sensing toolbox 540(b) may include a sensing board 545(b).
• a SME 550(b) may also be located between the data link layer 520 and the PHY layer 535.
• Figure 6 is an example of a protocol stack of a multi-anchor
• the AP/WTRU with a common sensing toolbox for a subset of PHYs.
• the sensing toolbox 540 may integrate the sensing algorithms along with the PHY modules on some or all of the bands as required.
• the sensing may share the radio with the PHY module.
• the MAC 525 may configure the sensing toolbox 540 per band through the dedicated service access point (SAP) between each PHY and MAC.
• SAP dedicated service access point
• the MAC may receive data from a logical link control (LLC) layer through a MAC SDU (MSDU). The MAC may then process the MSDU and transfer the MSDU to a MAC protocol data unit (MPDU) or aggregated MPDU (A-MPDU).
• MPDU MAC protocol data unit
• A-MPDU aggregated MPDU
• a PHY selector switch residing in the MAC, may determine active PHY entities and deliver MPDUs (or A-MPDUs) to all active PHY entities.
• the size of each MPDU (or A- MPDU) and the number of MPDUs (or A-MPDUs) transmitted to each PHY entity may depend on different factors, such as the capability and the availability of the channel, quality of service (QoS) requirement, and the like.
• each active PHY may receive data from the common MAC in a PHY SDU (PSDU). All of these PHY entities may be independently operated. Thus, each PHY entity may depend on different factors of its connected channel, such as the availability and capability of the channel, to process the PSDU and transfer the PSDU to a PHY PDU (PPDU).
• PSDU PHY SDU
• FIG. 7 is an example of MAC data plane architecture of a multi- anchor network.
• an MSDU may go through some or all of the following processes: MSDU aggregation 701, frame delivery deferral during power save mode 702, sequence number assignment 703, MSDU integrity protection 704, fragmentation 705, MPDU encryption and integrity protection 706, frame formatting 707, and MPDU aggregation 708.
• the data frames that contain all or part of the MSDU may be queued per access category (AC)/traffic stream (TS).
• a PHY selector switch 710 may be introduced in the MAC 700 of a multi-anchor network.
• the PHY selector switch 710 may be an entity, residing at the bottom of the MAC 700, which connects the MAC 700 and the PHY 715 and processes and transfers the PHY information to some parts of the MAC 700 to enhance the MAC efficiency.
• a PHY selector switch may determine and enable active PHY entities in all bands, such as an ISM band, TVWS low band and TVWS high band. There are two main factors that may impact the activity of a PHY entity in the connected bands: 1) capability of the device; and 2) the availability of the channel. For example, if the device does not support the operation of certain bands or channels, (such as intra-band devices and legacy devices), then the PHY entities residing on those bands or channels may be disabled by the PHY selector switch. If the band or the channel is constantly unavailable or heavily congested, the PHY selector switch may decide to disable the PHY entity associated with the band or the channel. Alternatively, the PHY selector switch may switch to another good channel in the same band.
• the PHY selector switch may feedback the channel information to some parts of MAC, for example, MSDU aggregation or MPDU aggregation or fragmentation. Therefore, the fragmentation or aggregation may adapt to the real-time channel status.
• the channels connected to the active PHY entities may be in good condition, (less interference and high signal-to- interference plus noise ratio (SINR)), which may result in a high PHY rate used on these channels.
• SINR signal-to- interference plus noise ratio
• the PHY selector may then feedback this information to MSDU aggregation, MPDU aggregation and fragmentation. As a result, more aggregation or less fragmentation may take place, and then the size of an A- MPDU, which is transferred to one PPDU, may be increased.
• the PHY selector may use the real-time channel status information, for example, data rate, congestion, and the like, and the QoS requirement of each frame to schedule MPDU (or A-MPDU) delivered to an appropriated PHY entity.
• This may provide more flexibility of MPDU (or A-MPDU) transmission, and may reduce the transmission delay.
• the larger size of an MPDU (or A- MPDU) may be transmitted to the PHY entity with the high data rate, and a smaller size of a MPDU (A-MPDU) may be transmitted to the PHY entity with the low data rate.
• the channel is congested, then fewer MPDUs or MPDUs with a lower QoS requirement may be transmitted to the corresponding PHY entity. If the traffic on the channel is smooth, then more MPDUs or MPDUs with a higher QoS requirement may be transmitted to that PHY entity.
• Figure 8 is an example of multi-anchor interfaces connecting different blocks.
• Figure 8 shows interfaces connecting different management functional blocks in a multi-anchor AP 800 having an SME 805, as well as the interfaces connecting the blocks of SME 805, MAC 810, PHY 815, MAC layer management entity (MLME) 820, physical layer management entity (PLME) 825, local database 830 and TVWS database 835.
• SME 805 SME 805
• MAC 810 PHY 815
• MLME MAC layer management entity
• PLME physical layer management entity
• DSM dynamic spectrum management
• the device-dependent routing and spectrum manager (DDRSM) module 840 may allocate available channels to the network and manage the users for the channel operations.
• the major tasks of the DDRSM 840 may include 1) querying the TVWS database 835, (or other external databases), for the available TVWS channels, (or other channels), at the location; 2) verifying the device's FCC ID with the TVWS database 835 (or other databases); 3) interacting with the sensing controller module 842 for the necessary spectrum sensing operation; 4) determining the channels for use, and informing a buffer controller module 845; 5) interacting with a channel monitor module 850 for the instantaneous channel conditions; and 6) initiating the control channel messages related to TVWS channel (other channels) operations.
• a power saving management module 855 may optimize power consumption of the overall system by enabling/disabling different power modes. It may be based on different criteria, such as channel conditions, frame QoS, AP power status, buffer status and the like. The power saving management module 855 may transmit the signal to the MLME 820 and enable the power save mode in different bands.
• the local database 830 may store the WTRU's capability and policy information; QoS related information; TVWS operation related information; and operation information in every operational band.
• the local database 830 may host: receiving and distributing the channel usage information from/to registered devices; processing the sensing information transmitted from registered devices; and coordinating the channel usage of registered devices in multiple bands.
• the sensing controller module 842 may coordinate spectrum sensing related operations in multiple bands.
• the sensing controller module may support: silent period scheduling for multiple bands, (for example, different silencing periodicity in different bands with different bandwidth); spectrums sensing task assignment to different bands; processing and conclusion of spectrum sensing results collected from different bands; maintenance of a primary and secondary users list in multiple bands; and initiation of control channel messages related to spectrum sensing in multiple bands.
• some bands for example, ISM band, may not have primary users (i.e., each user has equal usage priority on this band) but some bands, for example, TVWS bands, may have primary users (i.e., primary users have high usage priority on the band, and the secondary user may quit the band if primary a user is detected).
• the messages may include device dependent station enablement (DSE) measurement report request and DSE measurement report response.
• DSE device dependent station enablement
• sensing toolbox(es) 860 There are two methods to implement sensing toolbox(es) 860 on multiple bands.
• a common sensing toolbox across multiple bands may receive the sensing requirements from the sensing controller module 842 and control the sensing on multiple bands.
• an individual sensing toolbox associated with each band may receive the sensing requirements related to its associated band and perform the sensing related task accordingly.
• the buffer controller module 845 may create and maintain multiple transmission buffers, each associated with a specific physical channel for a given AC, for the simultaneous transmissions over multiple bands.
• the buffer controller module 845 may achieve system load balancing, the optimal utilization of a channel resource, as well as robust QoS support.
• the major tasks of the buffer controller module 845 may include buffer creation, frame insertion, frame removal, frame reordering, buffer balancing and buffer removal, and the like.
• a frame controller module 865 may control the operations of an existing MAC layer block 810, (specifically, the A-MSDU aggregation block, the fragmentation block, and the A-MPDU aggregation block), such that the frame outputs to be transmitted on physical channels within a common band may have approximately the same over-the-air (OTA) duration to avoid a self-jamming problem.
• OTA over-the-air
• the channel monitor module 850 may monitor channel conditions in multiple bands and transmit this information to the buffer controller module 845, the frame controller module 865, and the DDRSM module 840 for their proper operations.
• the new interfaces connecting functional blocks in the SME 805 of the AP 800 may include Si— S17 interfaces.
• the sensing controller 842 may use this interface to indicate the silent periods (periodic and aperiodic) in multiple bands, as well as the spectrum sensing task assignments, to the sensing toolbox 860. Since each operational band may have its unique features (for example, different bandwidths, different set of primary users and secondary users, etc), the silent period duration and periodicity, and sensing task may be varied over bands.
• the sensing toolbox 860 of the AP 800 may learn the sensing requirements through this interface, while the WTRUs in the network may learn such requirements via the control messages (for example, beacon, or DSE measurement report request) from the AP 800.
• the sensing controller 842 may also acquire the individual spectrum sensing results in different bands from either the sensing toolbox 860 or other WTRUs in the network. Note that in the case of multiple sensing toolboxes 860, each associated with one band, the Si interface refers to each of the interfaces connecting between the sensing controller 842 and all sensing toolboxes 860.
• the sensing controller 842 may use this interface to inform the buffer controller about the scheduled silent period so that the latter may balance the buffers accordingly.
• the DDRSM 840 may use this interface to transmit an inquiry to the sensing controller 842 about the conditions of certain channels over multiple bands as well as update the channel status to the sensing controller 842.
• the sensing controller 842 may use this interface to report the spectrum sensing results.
• the buffer controller 845 may use this interface to control the buffers at the MAC layer 810.
• the DDRSM 840 may use this interface to inform the buffer controller 845 the operational channels in different bands, so that the latter may manage buffers for these channels accordingly.
• the buffer controller 845 may use this interface to inform the frame controller 865 the status of the buffers, so that the latter may control the frame size accordingly.
• the channel monitor 850 may use this interface to report the instantaneous channel conditions to the DDRSM 840.
• the DDRSM 840 may feedback the available channel information to the channel monitor 850 using this interface.
• the DDRSM 840 may use this interface to contact the TVWS database 835, for the verification of device FCC IDs and for the query of available TVWS channels at the location.
• the channel monitor 850 may use this interface to report the instantaneous channel conditions and activation status of different PHY entities 815 to the buffer controller 845.
• the buffer controller 845 may also use this interface to update the buffer status to the channel monitor 850.
• the frame controller 865 may use this interface to control certain functional blocks in the MAC layer 810 to output frames of similar over-the-air (OTA) duration when they are transmitted on physical channels within a common band.
• OTA over-the-air
• the channel monitor 850 may use this interface to report the instantaneous channel conditions to the frame controller 865.
• the channel monitor 850 may use this interface to obtain instantaneous channel conditions from a PHY selector switch 870.
• the PHY selector 870 may also use this interface to transmit the activation status of PHY entities 815 to the channel monitor 850 if the PHY selector 870 disables/enables PHY entities 815.
• the channel monitor 850 may also forward the buffer status and the channel availability information to the PHY selector switch 870 using this interface.
• the DDRSM 840 may use this interface to transmit the operational channel information and the related power information to the MLME 820.
• the power saving management module 855 may transmit the power related information to a channel power saving management function in the MLME 820.
• the power saving management module 855 may use this interface to obtain instantaneous channel conditions and activation status of PHY entities 815 from the channel monitor 850.
• the S16 interface may be used for communication between the buffer controller 845 and the power saving management module 855.
• the buffer controller 845 may use this interface to update the power saving management module 855 regarding the buffer status.
• the power saving management module 855 may also transmit the power save mode information to the buffer controller 845.
• the DDRSM 840 may use this interface to communicate with the local database 830 for different information, such as, QoS information, channel status of different bands, WTRU capability and policy information, and the like.
• Figure 9 is an example of multi-anchor STA interfaces connecting functional blocks.
• Figure 9 illustrates an example interfaces connecting functional blocks of a multi-anchor WTRU 900 having an SME 905.
• the functional blocks that may reside in the SME 905 include a buffer controller 910, a frame controller 915 and a channel monitor 920.
• the interfaces existing in the multi-anchor WTRU 900 may include the II - 16 interfaces.
• the II interface may be used by the buffer controller 910 to obtain different types of information transmitted from a MAC layer 925.
• the information may include scheduled silent periods in different bands, TVWS operational channels and a power save mode period in different bands.
• the buffer controller 910 may also use the II interface to control the buffers at the MAC layer 925.
• the 12 interface is equivalent to the S6 interface at an AP.
• the buffer controller 845 may use this interface to inform the frame controller 865 the status of the buffers, so that the latter may control the frame size accordingly.
• the 13 interface is equivalent to the Sll interface at an AP.
• the channel monitor 850 may use this interface to report the instantaneous channel conditions to the frame controller 865.
• the 14 interface is equivalent to the S12 interface at an AP.
• the channel monitor 850 may use this interface to obtain instantaneous channel conditions from a PHY selector switch 870.
• the PHY selector 870 may also use this interface to transmit the activation status of PHY entities 815 to the channel monitor 850 if the PHY selector 870 disables/enables PHY entities 815.
• the channel monitor 850 may also forward the buffer status and the channel availability information to the PHY selector switch 870 using this interface.
• the 15 interface is equivalent to the S9 interface at an AP.
• the channel monitor 850 may use this interface to report the instantaneous channel conditions and activation status of different PHY entities 815 to the buffer controller 845.
• the buffer controller 845 may also use this interface to update the buffer status to the channel monitor 850.
• the 16 interface is equivalent to the S10 interface at an AP.
• the frame controller 865 may use this interface to control certain functional blocks in the MAC layer 810 to output frames of similar over-the-air (OTA) duration when they are transmitted on physical channels within a common band.
• OTA over-the-air
• the sensing toolbox 930 shown in Figure 9 may refer to a common sensing toolbox across all the bands or a profile on the combination of multiple sensing toolboxes with each associated with one band.
• Figure 10 shows an example functional block diagram at a transit side of an AP.
• the AP has seven (7) more functional blocks: a sensing controller 1001, a buffer controller 1005, a frame controller 1010, a channel monitor 1015, a power saving management 1020, a device dependent routing and spectrum manager 1025, and a PHY selector switch 1030.
• the sensing controller 1001 may receive the channel inquiry from the DDRSM, which may want to obtain the channel availability information on multiple bands, for example, TVWS high and low bands, via spectrum sensing. The sensing controller 1001 may then schedule (different) silent periods for the spectrum sensing operation on different bands. The silent period may be either periodic or aperiodic and may depend on multiple factors, for example, channel bandwidth, traffic status, and the like. The spectrum sensing on different bands may be independent. The sensing controller 1001 may notify the buffer controller 1005 of the silent period on each band. It may also transmit the announcement to WTRUs via beacons. The silent period on each band may also be pre-determined by the sensing controller. [0137] The sensing controller 1001 may also determine which WTRUs or
• the AP may perform the spectrum sensing on which band. This decision may be based on the sensing capability of the WTRUs and/or AP. To this end, the sensing controller 1001 may retrieve such information from the DDRSM 1025.
• the sensing controller 1001 may inform the sensing toolbox about the details of the spectrum sensing. This may include the channels and the bands to execute spectrum sensing, a list of primary users and secondary users, silent period scheduling for each PHY, and the like. Then the AP may wait for the spectrum sensing results from the sensing toolbox(es). If a WTRU participates in the spectrum sensing, the sensing controller 1001 may initiate a DSE measurement report request message for that WTRU. The contents in the DSE measurement report request message may be similar to the sensing request message between sensing controller 1001 and sensing toolbox at AP side. Then the AP may wait for the spectrum sensing results of multiple bands from the WTRU via a DSE measurement report response message.
• the sensing controller 1001 may process the spectrum sensing results from different WTRUs or AP. Finally, it may transmit a spectrum response with the combined sensing results to the DDRSM 1025.
• FIG 11 is an example call flows for a sensing controller.
• the DDRSM 1120 may transmit a spectrum inquiry 1125 to the sensing controller 1110.
• the sensing controller 1110 may determine silent period on multiple bands 1130.
• the sensing controller 1110 may transmit information of silent periods on different bands 1135 to the buffer controller 1115.
• the sensing controller 1110 may also transmit silent period information, via beacon, 1140 to the WTRU 1101.
• the sensing controller 1110 and the DDRSM 1120 may communicate the WTRU's sensing capabilities 1145.
• the sensing controller 1110 may determine the spectrum sensing participants on each band 1150.
• the sensing controller 1110 may transmit a sensing request 1155 to the sensing toolbox 1105.
• the sensing controller 1110 may also transmit a DSE measurement report request 1160 to the WTRU 1101.
• the sensing toolbox 1105 may transmit a sensing response 1165 to the sensing controller 1110.
• the WTRU 1101 may transmit a DSE measurement report response 1170 to the sensing controller 1110.
• the sensing controller 1110 may collect and process the sensing results of multiple bands 1175.
• the sensing controller 1110 may transmit a spectrum response 1180 to the DDRSM 1120.
• the buffer controller 1115 may manage the transmission buffers for each physical channel within each access category. This involves the buffer creation, buffer removal, frame assignment (to buffers), and frame reordering. The frame reordering may be triggered by buffer imbalance, QoS requirement, and channel unavailability.
• the inter-band carrier aggregation is based on the device's capabilities. Specifically, it may not be possible to assign a frame, whose destination is an intra-band device, to the buffers corresponding to the channels in a different band.
• Figure 12 is an example call flow for a buffer controller.
• the buffer controller 1204 may receive the operational channel information 1207 from the DDRSM 1206.
• the buffer controller 1204 may also receive and the channel status information and the activation status of PHY entities 1208 from the channel monitor 1205.
• the buffer controller 1204 may then create logical buffers 1209 accordingly.
• the buffer controller 1204 may check the destination of the frames.
• the buffer controller 1204 may check the DDRSM 1206 to see the device capabilities 1210. Based on the device capabilities and the buffer status, the buffer controller 1204 assigns these frames to proper logical buffers 1211.
• the buffer controller 1204 schedules the frame transmissions and frame reordering process 1211.
• the buffer controller 1204 may inform the frame controller 1203 of the buffer status 1212, which is intended for buffer balancing, and hence load balancing.
• the buffer controller 1204 may also inform the power saving management 1202 of the buffer status 1213.
• the power saving management 1202 may determine to enter power save mode 1214.
• the power management entity 1202 may then notify the buffer controller 1204 of the power save mode 1215.
• the sensing controller 1201 may transmit silent period information on different bands 1216 to the buffer controller 1204.
• the buffer controller 1204 may perform frame reordering 1217.
• the DDRSM 1206 may transmit operational channel information 1218 to the buffer controller 1204.
• the channel monitor 1205 may transmit channel status information 1219 to the buffer controller 1204.
• the buffer controller 1204 may transmit buffer status 1220 to the channel monitor 1205.
• the buffer controller 1204 may then perform buffer reorganization 1221.
• FIGS 13 and 14 show weighted round robin frame allocation algorithms that may assign frames toward proper logical buffers named "weighted round robin schemes".
• the weight factors at time slot t on operating channel i may be called Wf .
• the weight factors may be defined flexible for different purposes. For example, the weight factors may be proportional to the available bandwidth of each channel that may be allocated at time slot t. With the system working on DCF mode, all WTRUs (including the AP) may contend the channels by CSMA/CA scheme without QoS support. There may be no need for differentiated services supports.
• Figure 13 is an example of "Weighted Round Robin Scheme 1".
• CSMA/CA processes deployed for different Access Categories may also provide contention-free access to the channel for a period named Transmit Opportunity (TXOP).
• TXOP Transmit Opportunity
• Figure 14 is an example of "Weighted Round Robin Scheme 2".
• the buffer controller periodically or aperiodically may update the power saving management the buffer status to help the power saving management to determine the power save period on different bands.
• the power saving management may transmit this information to the buffer controller and the buffer controller may change the order of frames accordingly.
• the buffer controller may also receive the silent period information from the sensing controller.
• the buffer controller may reorder frames after the silent period information is updated. If there is any change on the operational channels and channel conditions, the buffer controller may reorganize its buffers.
• a buffer may be controlled from a dynamic programming prospective, taking into account buffer stability, throughput maximization and the like.
• Buffer controlling may be modeled as a multistage problem, in which at each frame transmission, the AP may be faced with the problem of deciding on its own actions. For instance, an AP may decide to forward frames to a specific buffer to avoid overflow on other buffers or may even decide to drop some frames to avoid transmission failures.
• Figure 15 is an example of a state transition diagram of buffer 1 and buffer 2, with each state represented by two random variables that account for the number of current frames in buffer 1 and buffer 2.
• Figure 15 shows state transition of two buffers using an algorithm based on backward induction techniques which may be run in the "frame distribution to different buffers" stage. Backward induction techniques may use backward reasoning to solve multistage problems by finding optimal actions at each stage.
• a single AP may try to communicate N data frames in
• TXOPs transmit opportunities
• Arriving frames for channel x e ⁇ l, ...,x are buffered in a corresponding buffer x for transmission in the next available slot.
• Each buffer may have a size of K frames. If a frame arrives while its dedicated buffer is full, it gets dropped.
• b x For each buffer a random variable b x , which accounts for the current number of frames in the buffer, may be defined. For simplicity of analysis, consider the number of buffers to be two and the maximum size of each buffer to be 1 frame.
• each state is represented by two random variables (bl, b2) accounting for the current number of frames in buffer 1 and buffer 2 respectively, where d is the duty cycle or frame generation probability, t is the probability of directing frame to buffer 1, 1-t is the probability of directing frame to buffer 2, q is the probability of outage on channel 1, and p is the probability of outage on channel 2.
• d is the duty cycle or frame generation probability
• t is the probability of directing frame to buffer 1
• 1-t is the probability of directing frame to buffer 2
• q is the probability of outage on channel 1
• p is the probability of outage on channel 2.
• the self transition (1,1)— > (1,1) 1501 may correspond to the case where there may be: an unsuccessful transmission for both frames; an unsuccessful transmission for the frame in the first buffer but successful transmission for the frame in the second buffer and a new frame arrives at the second buffer, or a successful transmission for the first frame and a new frame arrives at the first buffer but unsuccessful transmission of the second.
• Each one of these cases has a different consequence.
• the first case results in no frame transmission while the second and the third cases result in 1 frame transmission. This may have an implication on the calculations on the achievable throughput as described below. All other transitions may be interpreted in a similar way.
• Random variables bl and b2 represent the conditions of buffer 1 and buffer 2, respectively. Each random variable may reflect the number of frames in the corresponding buffer: "0" meaning no frame (buffer is empty) and 1 meaning one frame (buffer is full). Specifically, state (1,0) 1500 indicates that the first buffer has one frame and the second buffer has no frames. State (0,1) 1502 indicates that the first buffer has no frames and the second buffer has one frame. State (1,1) 1501 indicates that both buffers have one frame each. Finally, state (0,0) 1503 indicates that both buffer have no frames.
• Figure 16 is an example of trellis buffer evolution.
• the trellis of Figure 16 may be derived to study the evolution of each buffer with time.
• the bold line may represent the optimal action for equal non-zero transition probabilities.
• the optimal action may be the one which has the highest number of 1— > 0 transitions.
• the starting state (0,0) 1600 represents the state where both buffers are empty and ready to store frames.
• the starting state may then evolve with time and may change to any of the four possible states according to the corresponding transition probability. For example, it may evolve to state (1,0) 1605 if one frame is generated and stored in buffer 1 and no frame is stored in buffer 2. Then it may evolve to state (0,1) 1610 if the frame in buffer 1 is transmitted successfully and a new frame is generated and stored in buffer 2. Finally, the ending state (0,0) 1615 may represent the desired state where both buffers are cleared and no more packets are generated.
• Each 1— » 0 transition may correspond to a successful frame transmission and buffer clearing.
• Pk may be defined as the transition probability at stage k and ⁇ ⁇ [ ⁇ ( ⁇ ] as an indicator function which equals 1 if buffer x is cleared and 0 otherwise.
• an AP may utilize the above approach to determine some factors such as frame generation probability and buffer assignment probabilities given link outage probabilities in order to maximize the total achievable throughput and the buffers stability.
• the major task of a frame controller is to control the A-MSDU aggregation, fragmentation, and the A-MPDU aggregation blocks such that each A-MPDU frame is designed to transmit on a specific physical channel, and the A- MPDU transmission duration over each physical channel is approximately the same. Similar to the buffer controller case, the frame controller may be modified to incorporate the support of different types of devices.
• FIG. 17 is an example call flows of a frame controller.
• the frame controller 1705 may receive the operational channel status information 1720 from the channel monitor 1715.
• the frame controller 1705 may then pre-specify an over-the-air duration for each operational band 1725, based on modulation coding scheme (MCS) values of the physical channels.
• MCS modulation coding scheme
• the frame controller 1705 may first check the destination of this frame. From the DDRSM 1710, the frame controller 1705 may learn the type of devices of the destination WTRU 1735 and subsequently, the physical channels this frame may be transmitted through. Furthermore, the frame controller 1705 may receive from the buffer controller 1701 the status of the buffers associated with those physical channels 1730. The frame controller 1705 may then control the A-MSDU, fragmentation, and A-MPDU blocks to generate A-MPDU frames of the desirable length 1740.
• MCS modulation coding scheme
• the channel monitor 1715 may obtain some channel condition information and the activation status of PHY entities from the PHY selector switch, and transmit this information to the frame controller 1705, buffer controller 1701, as well as the DDRSM 1710.
• the channel condition information may include a received signal strength indicator (RSSI), an MCS set used, frame loss rate, and data rate. These metrics may be physical channel independent and user independent.
• the power saving management is a newly introduced functionality in SME for the purpose of conserving power.
• the functions it hosts are: forwarding the related power information and policy from the DDRSM to MLME; and enabling or disabling power saving mode on a particular band or channel based on different criteria, for example, the channel condition, traffic status, buffer status and the like.
• the latter function may be referred to as selective band power save (SBPS).
• SBPS selective band power save
• the power save mode may imply a low activity level during the indicated period, for example, the WTRUs and the AP may not actively be transmitting or receiving frames.
• SBPS may provide an efficient channel utilization and power saving capability in a network operated on multiple bands.
• Figure 18 is an example of SBPS with an indicated power saving period in each band.
• the power saving management may be based on the channel/traffic condition and/or buffer status to determine which channel and what time the power save period should be enabled. For example, the channel in band 1 1801 may be highly interfered during a certain period of time. Then, the PHY selector of the AP may transmit out a frame to indicate the power save period 1815 in band 1 1801. In a second example, the PHY selector of the AP may transmit out a frame to indicate the power save period 1820 in band 2 1805. In a third example, the PHY selector of the AP may transmit out a frame to indicate the power save period 1825 in band 3 1810. Power-save multi-poll (PSMP), which is defined in IEEE 802.11 ⁇ , may be combined with SBPS to further reduce the power consumption.
• PSMP Power-save multi-poll
• FIG 19 is an example of a power-save multi-poll (PSMP) sequence in SBPS.
• the AP may transmit an enhanced PSMP (ePSMP) frame 1910, which contains the schedule for the subsequent downlink and uplink transmissions in different bands.
• ePSMP enhanced PSMP
• a WTRU may be awake for the PSMP downlink transmission time (PSMP-DTT) 1915 containing broadcast frames (if any), during its allotted PSMP-DTT 1920/1925 and during its PSMP uplink transmission time (PSMP-UTT) 1930/1935 on the indicated band.
• PSMP-DTT PSMP downlink transmission time
• PSMP-UTT PSMP uplink transmission time
• PPDUs may be transmitted as a continuous burst with individual PPDUs separated by short interframe spaces (SIFS) or reduced interframe spaces (RIFS).
• SIFS short interframe spaces
• RIFS reduced interframe spaces
• a WTRU that has one or more frames to transmit may start transmitting at the start of its PSMP-UTT 1930/1935 without performing CCA and disregarding any NAV setting.
• the WTRU may complete its transmission within the allocated PSMP-UTT 1930/1935.
• Cross-band scheduling may be proposed in this example, where the
• AP includes the scheduling information of bands 2/3 1902 in the ePSMP frame which is transmitted in band 1 1901 or vice versa.
• the power saving management in SME may be based on the size of MPDUs and the channel condition to perform the cross-band scheduling, thus minimizing the power consumption as well as increasing the system throughput.
• Figure 20 is an example call flows of power saving management.
• the power saving management 2010 may periodically or aperiodically receive the PHY information 2020, for example, channel status and the activation status of PHY entities, from the channel monitor 2015.
• the power saving management 2010 may also periodically or aperiodically receive buffer status 2025 from the buffer controller 2005.
• the power saving management 2010 may also request sensing controller for sensing results update if there is a need. Then the power saving management 2010 may use the sensing results and the channel/buffer status to determine if the SBPS should be enabled 2030. If SBPC is determined to be enabled, the power saving management 2010 may transmit the notice 2035 to the MLME 2001 for transmitting ePSMP frame.
• the power saving management 2010 may notify the buffer controller 2050 of the corresponding buffer management 2040.
• Figure 21 is an example of a device dependent routing and spectrum manager (DDRSM) registration procedure.
• the major task of the DDRSM 2105 is to allocate operational channels for WTRUs, based on the WTRUs' capabilities, channel availability and channel conditions. This may include two procedures: a registration procedure and a channel allocation procedure.
• the AP powers on 2115 it may first verify its device FCC ID 2120 with the TVWS database 2110.
• the DDRSM 2105 may obtain from the TVWS database 2110 a list of available channels at the specific location 2125.
• the DDRSM 2105 may then modify the proper fields in the beacon, association response, and probe response messages about the available TVWS channel information 2130.
• the DDRSM 2105 may verify this WTRU's device FCC ID 2140 with the TVWS database 2110. Upon verification, the DDRSM 2105 may save the WTRU's information 2145 in a local database 2101.
• Figure 22 is an example of a DDRSM channel allocation procedure.
• the DDRSM 2210 may wish to learn the instantaneous condition of those available channels. To this end, the DDRSM 2210 may transmit a spectrum inquiry 2230 to the sensing controller 2205 for certain channels of interest. Based on the spectrum response 2235 as well as the WTRUs' capability information, the DDRSM 2210 may make a decision on the operational channels 2240. The DDRSM 2210 may then transmit this decision 2245 to the channel monitor 2215 and the buffer controller 2201 for the latter to have certain buffering operations. The DDRSM 2210 may monitor channel operations 2250. The DDRSM 2210 may also receive the channel status information 2255 from the channel monitor 2215 from time to time. If a channel is not in good condition, the DDRSM 2210 may change the operational channels 2260 and may subsequently inform 2265 the buffer controller 2201 and the channel monitor 2215.
• DDRSM may also participate in the normal maintenance of the operational channels. This may involve the update of certain fields, for example, white space map, in the beacon, association response, and probe response messages. Furthermore, it may initiate several messages to different WTRUs, for example, channel control request, channel power saving management, contact verification signal, channel status query, and the like. These messages may control the operations of specific WTRUs.
• Figure 23 is an example of a table in a local database.
• the DDRSM may also contribute to the range extension use case.
• an inter-band WTRU (WTRU 3) 2325 sets up a link with an AP via both band 1 2305 and band 2 2310.
• WTRU 3 2325 sets up a link with an AP via both band 1 2305 and band 2 2310.
• the DDRSM may update its local database accordingly.
• Figure 23 illustrates that the band 2 channel condition 2310 for WTRU 3 2325 is bad 2330.
• the buffer controller learns this situation when accessing the local database. It may allocate the frames for WTRU 3 2325 to the buffers associated with the band 1 channels 2305.
• Figure 24 is an example call flow of a PHY selector switch.
• a channel monitor 2405 may receive the operational channel information 2420 and buffer status information 2425 from the DDRSM 2415 and the buffer controller 2410 respectively. The channel monitor 2405 may then forward this information 2430 to the PHY selector switch 2401. The PHY selector switch 2401 may use this information to disable or enable the corresponding PHY entities 2435. After that, the PHY selector switch 2401 may transmit the PHY information including the activation status of PHY entities and the PHY channel conditions 2440 to the channel monitor 2405.
• the multi-anchor WTRU may not be connected to the TVWS database and may not have the management functionality.
• the buffer controller may perform slightly different functions and procedures from the corresponding one in the multi- anchor AP.
• Figure 25 is an example call flow of a buffer controller at a multi- anchor WTRU.
• the buffer controller 2505 at the multi-anchor WTRU may obtain all secondary channel operation related information 250 from the MAC 2515, which may be included in the management/control frames transmitted from the multi-anchor AP.
• the information may include: scheduled silent period; TVWS operational channels; and power save mode period in different bands.
• the channel monitor 2510 may forward the channel status information and activation status of PHY entities 2525 to the buffer controller 2505. Using all the information received from the MAC 2515 and the channel monitor 2510, the buffer controller 2505 may create corresponding logical buffers 2530.
• the buffer controller 2505 may use a similar mechanism as used by the buffer controller of the multi-anchor AP to assign different sizes of frames to proper logical buffers, schedule frame transmissions and perform frame reordering processes 2535.
• the buffer controller 2505 may also inform the frame controller 2501 of the buffer status 2540 for the load balancing purpose.
• the buffer controller 2505 may use the silent period information to reorder frames in different buffers. During the silent period there may be no transmission or reception allowed on the channel(s) that may be effected. In this sensing period the sensing toolbox may only be the active part using the reception.
• the buffer controller may be aware of the silent period timing in order to configure itself. If there is any change on the operational channels and channel conditions, the buffer controller may reorganize its buffers accordingly.
• a multi-anchor access point comprising:
• MAC medium access control
• PHY physical
• DDRSM Device Dependent Routing and Spectrum Manager
• DDRSM Device Dependent Routing and Spectrum Manager
• DDRSM Device Dependent Routing and Spectrum Manager
• TVWS Television White Space
• a method for channel allocation in a physical (PHY) selector switch comprising:
• DDRSM Device Dependent Routing and Spectrum Manager
• the information includes an activation status of the PHY entity and a PHY channel condition.
• Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a 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).
• 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.

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Quality & Reliability (AREA)
• Mobile Radio Communication Systems (AREA)
• Small-Scale Networks (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=47843430

Family Applications (1)

Country Status (2)

Cited By (4)

Families Citing this family (1)

Family Cites Families (4)

• 2013
  • 2013-02-22 TW TW102106179A patent/TW201347480A/zh unknown
  • 2013-02-22 WO PCT/US2013/027278 patent/WO2013126666A2/en active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events