Patent Grant
12170986
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present disclosure relates generally to the field of wireless networks and specifically, in one or more exemplary embodiments, to methods and apparatus for dynamically reassigning radio frequency spectrum, such as for example those providing connectivity via quasi-licensed Citizens Broadband Radio Service (CBRS) technologies.
A multitude of wireless networking technologies, also known as Radio Access Technologies (“RATs”), provide the underlying means of connection for radio-based communication networks to user devices. Such RATs often utilize licensed radio frequency spectrum (i.e., that allocated by the FCC per the Table of Frequency Allocations as codified at Section 2.106 of the Commission's Rules. In the United States, regulatory responsibility for the radio spectrum is divided between the U.S. Federal Communications Commission (FCC) and the National Telecommunications and Information Administration (NTIA). The FCC, which is an independent regulatory agency, administers spectrum for non-Federal use (i.e., state, local government, commercial, private internal business, and personal use) and the NTIA, which is an operating unit of the Department of Commerce, administers spectrum for Federal use (e.g., use by the Army, the FAA, and the FBI). Currently only frequency bands between 9 kHz and 275 GHz have been allocated (i.e., designated for use by one or more terrestrial or space radio communication services or the radio astronomy service under specified conditions). For example, a typical cellular service provider might utilize spectrum for so-called “3G” (third generation) and “4G” (fourth generation) wireless communications as shown in Table 1 below:
Alternatively, unlicensed spectrum may be utilized, such as that within the so-called ISM-bands. The ISM bands are defined by the ITU Radio Regulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of the Radio Regulations. In the United States, uses of the ISM bands are governed by Part 18 of the Federal Communications Commission (FCC) rules, while Part 15 contains the rules for unlicensed communication devices, even those that share ISM frequencies. Table 2 below shows typical ISM frequency allocations:
ISM bands are also been shared with (non-ISM) license-free communications applications such as wireless sensor networks in the 915 MHz and 2.450 GHz bands, as well as wireless LANs and cordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.
Additionally, the 5 GHz band has been allocated for use by, e.g., WLAN equipment, as shown in Table 3:
User client devices (e.g., smartphone, tablet, phablet, laptop, smartwatch, or other wireless-enabled devices, mobile or otherwise) generally support multiple RATs that enable the devices to connect to one another, or to networks (e.g., the Internet, intranets, or extranets), often including RATs associated with both licensed and unlicensed spectrum. In particular, wireless access to other networks by client devices is made possible by wireless technologies that utilize networked hardware, such as a wireless access point (“WAP” or “AP”), small cells, femtocells, or cellular towers, serviced by a backend or backhaul portion of service provider network (e.g., a cable network). A user may generally access the network at a “hotspot,” a physical location at which the user may obtain access by connecting to modems, routers, APs, etc. that are within wireless range.
CBRS—
In 2016, the FCC made available Citizens Broadband Radio Service (CBRS) spectrum in the 3550-3700 MHz (3.5 GHz) band, making 150 MHz of spectrum available for mobile broadband and other commercial users. The CBRS is unique, in that it makes available a comparatively large amount of spectrum (frequency bandwidth) without the need for expensive auctions, and without ties to a particular operator or service provider.
Moreover, the CBRS spectrum is suitable for shared use between government and commercial interests, based on a system of existing “incumbents,” including the Department of Defense (DoD) and fixed satellite services. Specifically, a three-tiered access framework for the 3.5 GHz is used; i.e., (i) an Incumbent Access tier 102, (ii) Priority Access tier 104, and (iii) General Authorized Access tier 106. See
Incumbent Access (existing DOD and satellite) users 102 include authorized federal and grandfathered Fixed Satellite Service (FSS) users currently operating in the 3.5 GHz band shown in
The Priority Access tier 104 (including acquisition of spectrum for up to three years through an auction process) consists of Priority Access Licenses (PALs) that will be assigned using competitive bidding within the 3550-3650 MHz portion of the band. Each PAL is defined as anon-renewable authorization to use a 10 MHz channel in a single census tract for three years. Up to seven (7) total PALs may be assigned in any given census tract, with up to four PALs going to any single applicant. Applicants may acquire up to two-consecutive PAL terms in any given license area during the first auction.
The General Authorized Access tier 106 (for any user with an authorized 3.5 GHz device) is licensed-by-rule to permit open, flexible access to the band for the widest possible group of potential users. General Authorized Access (GAA) users are permitted to use any portion of the 3550-3700 MHz band not assigned to a higher tier user and may also operate opportunistically on unused Priority Access License (PAL) channels. See
The FCC's three-tiered spectrum sharing architecture of
Under the FCC system, the standard SAS 202 includes the following elements: (1) CBSD registration; (2) interference analysis; (3) incumbent protection; (4) PAL license validation; (5) CBSD channel assignment; (6) CBSD power limits; (7) PAL protection; and (8) SAS-to-SAS coordination. As shown in
An optional Domain Proxy (DP) 208 is also provided for in the FCC architecture. Each DP 208 includes: (1) SAS interface GW including security; (2) directive translation between CBSD 206 and domain commands; (3) bulk CBSD directive processing; and (4) interference contribution reporting to the SAS.
A domain is defined is any collection of CBSDs 206 that need to be grouped for management; e.g.: large enterprises, venues, stadiums, train stations. Domains can be even larger/broader in scope, such as for example a terrestrial operator network. Moreover, domains may or may not use private addressing. A Domain Proxy (DP) 208 can aggregate control information flows to other SAS, such as e.g., a Commercial SAS (CSAS, not shown), and generate performance reports, channel requests, heartbeats, etc.
CBSDs 206 can generally be categorized as either Category A or Category B. Category A CBSDs have an EIRP or Equivalent Isotropic Radiated Power of 30 dBm (1 Watt)/10 MHz, fixed indoor or outdoor location (with an antenna <6 m in length if outdoor). Category B CBSDs have 47 dBm EIRP (50 Watts)/10 MHz, and fixed outdoor location only. Professional installation of Category B CBSDs is required, and the antenna must be less than 6 m in length. All CBSD's have a vertical positioning accuracy requirement of +/−3 m. Terminals (i.e., user devices akin to UE) have 23 dBm EIRP (0.2 Watts)/10 MHz requirements, and mobility of the terminals is allowed.
In terms of spectral access, CBRS utilizes a time division duplex (TDD) multiple access architecture.
Unaddressed Issues of Service Continuity and Frequency Management—
Extant CBRS architectures, while promising from the standpoint of reduced contention for spectrum, currently lack mechanisms for maintaining service continuity under various scenarios such as frequency change. In particular, in the extant CBRS ecosystem, many devices including higher-power outdoor devices functioning as Consumer Premises Equipment (CPE) are treated or classified as CBSD Category B devices, and must register with the cognizant SAS similar to an eNB/CBSD. As previously noted, Category A devices can transmit up 30 dbm (1 watt)/10 MHz, while Category B devices can transmit up to about 50 dbm/10 MHz, so the average coverage area can vary widely. In practical terms, a Category A device may have a working range on the order of hundreds of feet, while a Category B device may operate out to thousands of feet or more, the propagation and working range dictated by a number of factors, including the presence of RF or other interferers, physical topology of the venue/area, energy detection or sensitivity of the receiver, etc.
Currently, as shown in
However, the SAS 201, 202 currently has no mechanism by which to associate a CPE 220 with any given CBSD/eNB 206. Rather, the SAS sees both devices effectively as separate CBSDs registered to that SAS. If, for any reason, the SAS changes the CBSD/eNB's frequency (such as e.g., due to incumbent detection), the CBSD/eNB 206 will have to restart or block its cells for a time period until the frequency change is effected. The CPE 220 will not receive the same frequency change command from the SAS, because the SAS views the CBSD/eNB and the CPE as separate entities. Moreover, if a SAS invokes a global frequency change to all registered CBSDs within a given area, there is no guarantee that the CBSD/eNB and CPE connected to it will be assigned the same frequency. This is because the SAS views both the CPE and the CBSD/xNB as “CBSD,” but does not (under the prior art) have a way to identify which CPE is connected to which CBSD/eNB. For example, in a given geographical location or region, a CBSD/eNB and any CPE attached to it may be subject to a frequency change invoked by the cognizant SAS. Because the SAS has no data on the relationship between the (attached) CPE and the CBSD/eNB, each may be assigned a different frequency. Alternatively, the SAS may simply order the CBSD/eNB to change frequency (without similarly ordering the attached CPE to do so). Either of the aforementioned cases will result in the CPE losing connection, and again scanning the entire band to find the CBSD/eNB, resulting in long delays and less-than-optimal service to the end customer.
As shown in
Moreover, the CPE 220 reattaching and scanning the entire band can, based on the implementation, take an appreciable period of time (up to several minutes), which means long periods of “downtime” for any users or customers which may be utilizing the CPE 220 as an access point for data or other services. This significantly degrades user experience, and may lead to users or customers not choosing to utilize or subscribe to the service(s).
The present disclosure addresses the foregoing needs by providing, inter alia, methods and apparatus for providing wireless spectrum allocation/re-allocation while maintaining service continuity for, inter alia, attached CPE.
In one aspect, a method for providing wireless spectrum reassignment is disclosed. In one embodiment, the wireless spectrum being allocated comprises CBRS-band spectrum with the GAA portion, and the method includes communicating data between at least one CBSD/xNB to one or more CPE attached thereto to both (i) cause the CPE to wait a prescribed period of time before attempting to re-attach to the CBSD/xNB, and (ii) use the SAS-designated new channel for direct re-attachment (versus using a broad band scan or similar search method).
In one variant, the new channel is the new (final) target channel. In another variant, the new channel comprises a temporary or ephemeral channel that is used as a “bridge” channel to the final new target channel.
In another aspect, a method for reassigning at least a portion of available wireless spectrum for a wireless access point is disclosed. In one embodiment, the method includes: determining that at least one RF (radio frequency) carrier requires reassignment to a new carrier; transmitting from a node a first information element (IE) to the wireless access point specifying (i) the selected new RF carrier and (ii) a timer value; receiving communication at the node from the wireless access point via the selected new RF carrier after the timer value expires.
In one implementation, the method is further configured to maintain data session continuity, and further includes: causing the wireless access point to suspend one or more operations on constituent UE or served devices until the timer expires and the access point successfully re-attaches to the node.
In a further implementation, the wireless access point includes a CBRS (Citizens Broadband Radio Service)-compliant CPE, and the node includes a CBRS-compliant and 3GPP compliant eNB or gNB.
In yet a further variant, the determining that at least one RF carrier requires reassignment is performed by a CBRS SAS (spectrum access system) entity.
In another aspect of the disclosure, a computerized wireless access apparatus configured for providing wireless access to a plurality of computerized wireless-enabled mobile devices via a quasi-licensed portion of a radio frequency (RF) spectrum is disclosed. In one embodiment, the computerized wireless access includes: a wireless interface configured to transmit and receive RF waveforms in the quasi-licensed portion; digital processor apparatus in data communication with the wireless interface; and a storage device in data communication with the digital processor apparatus and comprising at least one computer program.
In one variant, the node comprises a Category B CBSD that also includes a 3GPP 4G/4.5/5G protocol stack.
In another variant, the at least one computer program is configured to, when executed by the digital processor apparatus: receive a first protocol message from a computerized network node, the first protocol message including a first information element (IE) to the wireless access point specifying (i) a selected new RF carrier and (ii) a timer value, the message causing the wireless access apparatus to use the selected new RF carrier after the timer value expires.
In another aspect of the disclosure, network apparatus for use within a first network is disclosed. In one embodiment, the network apparatus is configured to generate messaging to one or more attached devices regarding RF carrier migration/reassignment plans, and includes: digital processor apparatus; network interface apparatus in data communication with the digital processor apparatus and configured to transact data with the one or more attached devices; and a storage apparatus in data communication with the digital processor apparatus and comprising at least one computer program.
In a further aspect of the disclosure, a fixed wireless access (FWA) apparatus for use within a wireless network is disclosed. In one embodiment, the FWA apparatus comprises a premises device operated by a network operator (e.g., MSO) that is configured to communicate wirelessly with one or more CBSD/xNB devices to obtain wireless backhaul from the premises. In one variant, the FWA apparatus is configured as a Category B CBSD CBRS device, and is mounted on the user's premises so as to enable the aforementioned backhaul for WLAN or wireline interfaces within the premises.
In a further aspect, a method of operating a wireless access point is disclosed. In one embodiment, the method includes: based at least on a determination that at least one RF (radio frequency) carrier in use by the wireless access point requires reassignment, generating a first information element (IE) comprising: (i) data relating to a selected new RF carrier, and (ii) a temporal value; transmitting the first IE to a wireless device associated with the wireless access point; causing transition of operation of the wireless access point to the selected new RF carrier; and subsequent to the transition and after expiration of the temporal value, establishing wireless data communication between the wireless device and the wireless access point using the selected new RF carrier.
In another aspect, a computer readable apparatus having a storage medium is disclosed. In one embodiment, the storage medium includes at least one computer program having a plurality of instructions which are configured to, when executed on a computerized wireless access device with digital processor apparatus, cause the computerized wireless access device to: generate, based at least on a determination that at least one RF (radio frequency) carrier in use by the computerized wireless access device as part of a communication session with a wireless user device requires reassignment, a first information element (IE) comprising: (i) data relating to a selected new RF carrier, and (ii) reattachment criterion data; transmit the first IE to the wireless user device using the at least one RF carrier, the transmitted first IE configured to cause transition of operation of the wireless user device to the selected new RF carrier; and receive a reattachment request form the wireless user device via at least the selected new carrier, the reattachment request having been transmitted from the wireless user device after at least one criterion specified by the reattachment criterion data has been met; and based at least on the received reattachment request, establish wireless data communication between the wireless user device and the computerized wireless access device using the selected new RF carrier.
In yet another aspect, a computerized wireless-enabled user device configured for quasi-licensed band operation is disclosed. In one embodiment, the computerized wireless-enabled user device includes: a first wireless data interface configured to utilize at least quasi-licensed radio frequency (RF) spectrum; digital processor apparatus in data communication with the first wireless data interface; and a storage device in data communication with the digital processor apparatus and comprising at least one computer program.
In one variant, the at least one computer program includes a plurality of instructions which are configured to, when executed by the digital processor apparatus, cause the computerized wireless-enabled user device to: receive data from a wireless base station via at least a first RF carrier within the quasi-licensed RF spectrum and a communications session between at least the wireless base station and the computerized wireless-enabled user device, the received data comprising at least (i) first data relating to a new RF carrier assignment, and (ii) data relating to a protocol to be utilized in attempt of at least one subsequent re-attachment to the wireless base station by the computerized wireless enabled user device; and based at least on the received data, perform a truncated re-attachment procedure according to the protocol while maintaining the communications session.
In an additional aspect of the disclosure, computer readable apparatus is described. In one embodiment, the apparatus includes a storage medium configured to store one or more computer programs. In one embodiment, the apparatus includes a program memory or HDD or SDD on a computerized controller device, such as an MSO controller, DP, or SAS entity. In another embodiment, the apparatus includes a program memory, HDD or SSD on a computerized access node (e.g., CBSD/xNB or CPE).
In a further aspect, a system architecture for reassignment of unlicensed or quasi-licensed spectrum among a plurality of CBSD/xNB (and associated CPE) is disclosed.
These and other aspects shall become apparent when considered in light of the disclosure provided herein.
All figures © Copyright 2017-2019 Charter Communications Operating, LLC. All rights reserved.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “access node” refers generally and without limitation to a network node which enables communication between a user or client device and another entity within a network, such as for example a CBRS CBSD, a Wi-Fi AP, or a Wi-Fi-Direct enabled client or other device acting as a Group Owner (GO).
As used herein, the term “application” (or “app”) refers generally and without limitation to a unit of executable software that implements a certain functionality or theme.
The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could include a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the term “CBRS” refers without limitation to the CBRS architecture and protocols described in Signaling Protocols and Procedures for Citizens Broadband Radio Service (CBRS): Spectrum Access System (SAS)—Citizens Broadband Radio Service Device (CBSD) Interface Technical Specification—Document WINNF-TS-0016, Version V1.2.1. 3, January 2018, incorporated herein by reference in its entirety, and any related documents or subsequent versions thereof.
As used herein, the terms “client device” or “user device” or “UE” include, but are not limited to, set-top boxes (e.g., DSTBs), gateways, modems, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones, and vehicle infotainment systems or portions thereof.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.) and the like.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0 and 3.1.
As used herein, the term “headend” or “backend” refers generally to a networked system controlled by an operator (e.g., an MSO) that distributes programming to MSO clientele using client devices. Such programming may include literally any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, interactive TV, over-the-top services, streaming services, and the Internet.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet. Other common examples include but are not limited to: a network of external servers, “cloud” entities (such as memory or storage not local to a device, storage generally accessible at any time via a network connection, and the like), service nodes, access points, controller devices, client devices, etc.
As used herein, the term “LTE” refers to, without limitation and as applicable, any of the variants or Releases of the Long-Term Evolution wireless communication standard, including LTE-U (Long Term Evolution in unlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed Assisted Access), LTE-A (LTE Advanced), and 4G/4.5G LTE.
As used herein, the term “memory” includes any type of integrated circuit or other storage device adapted for storing digital data including, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3D memory, and PSRAM.
As used herein, the terms “microprocessor” and “processor” or “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “MNO” or “mobile network operator” refer to a cellular, satellite phone, WMAN (e.g., 802.16), or other network service provider having infrastructure required to deliver services including without limitation voice and data over those mediums.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
As used herein, the term “network interface” refers to any signal or data interface with a component or network including, without limitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), LTE/LTE-A/LTE-U/LTE-LAA, Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN (e.g., 802.15), or power line carrier (PLC) families.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over e.g., cable or other networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a network. A QAM may also refer to a physical channel modulated according to the schemes.
As used herein, the term “SAS (Spectrum Access System)” refers without limitation to one or more SAS entities which may be compliant with FCC Part 96 rules and certified for such purpose, including (i) Federal SAS (FSAS), (ii) Commercial SAS (e.g., those operated by private companies or entities), and (iii) other forms of SAS.
As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network.
As used herein, the term “storage” refers to without limitation computer hard drives, DVR device, memory, RAID devices or arrays, optical media (e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices or media capable of storing content or other information.
As used herein, the term “Wi-Fi” refers to, without limitation and as applicable, any of the variants of IEEE Std. 802.11 or related standards including 802.11 a/b/g/n/s/v/ac or 802.11-2012/2013, 802.11-2016, as well as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer (P2P) Specification”, incorporated herein by reference in its entirety).
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth/BLE, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CBRS, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
As used herein, the term “xNB” refers to any 3GPP-compliant node including without limitation eNBs (eUTRAN) and gNBs (5G NR).
In one exemplary aspect, the present disclosure provides improved methods and apparatus for reassignment or re-allocation of wireless spectrum, such as “quasi-licensed” spectrum such as that provided by the recent CBRS technology initiatives (e.g., GAA or General Authorized Access) spectrum as shown in
In an exemplary embodiment, a CPE (e.g., Category B device) and CBSD/xNB architecture is provided which allows, inter alia, passing of data on frequency reassignments (such as due to a SAS withdraw or grant revocation of a current allocated frequency band) to an attached CPE so as to minimize disruption or loss of continuity to existing data sessions of the CPE and its constituent user devices, such as e.g., ongoing VoIP or VoLTE voice data sessions. In one variant, the CBSD/xNB undergoing frequency reassignment notifies the relevant attached CPE (which may be one or more CPE) of the impending frequency change to a target frequency (e.g., F1) as well as a timer value of how long it will be off-line to effect the carrier change. The CPE use(s) this information to, among other things, (i) wait only as long as needed for the CBSD/xNB to switch frequencies, and (ii) obviate a full band-scan to detect the CBSD/xNB at the new frequency. The CPE's use of this specific frequency when performing registration with SAS also may decrease the SAS grant time response.
As such, the CBSD/xNB acts as a “SAS proxy” of sorts for the CPE (and vice versa), providing communication between the two entities in instances such as frequency withdrawals/reassignments.
Advantageously, exemplary embodiments of the methods and apparatus described herein utilize existing 3GPP signaling mechanisms between, inter alia, the UE and CPE (including EUTRAN eNodeB or 5G NR gNodeB functionality), thereby obviating any changes to extant UEs in use. This is accomplished by maintaining two technology “stacks” in the CPE (i.e., a CBRS-compliant stack, and a 3GPP-compliant eNB or gNB stack for communication with 4G or 5G UEs respectively. CBRS-plane communications (e.g., between the CPE and its parent CBSD) include new information elements (IEs) or objects which, inter alia, direct the CPE to invoke both the aforementioned wait period, and the “targeted” carrier reattach procedure with the CBSD/xNB after frequency migration.
Exemplary embodiments of the apparatus and methods of the present disclosure are now described in detail. While these exemplary embodiments are described in the context of the previously mentioned wireless access points (e.g., CBSDs) associated with e.g., a managed network (e.g., hybrid fiber coax (HFC) cable architecture having a multiple systems operator (MSO), digital networking capability, IP delivery capability, and a plurality of client devices), the general principles and advantages of the disclosure may be extended to other types of radio access technologies (“RATs”), networks and architectures that are configured to deliver digital data (e.g., text, images, games, software applications, video and/or audio). Such other networks or architectures may be broadband, narrowband, or otherwise, the following therefore being merely exemplary in nature.
It will also be appreciated that while described generally in the context of a network providing service to a customer or consumer or end user or subscriber (i.e., within a prescribed venue, or other type of premises), the present disclosure may be readily adapted to other types of environments including, e.g., outdoors, commercial/retail, or enterprise domain (e.g., businesses), or even governmental uses, such as those outside the proscribed “incumbent” users such as U.S. DoD and the like. Yet other applications are possible.
Also, while certain aspects are described primarily in the context of the well-known Internet Protocol (described in, inter alia, Internet Protocol DARPA Internet Program Protocol Specification, IETF RCF 791 (September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6) Specification, IETF RFC 2460 (December 1998), each of which is incorporated herein by reference in its entirety), it will be appreciated that the present disclosure may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Moreover, while the current SAS framework is configured to allocate spectrum in the 3.5 GHz band (specifically 3,550 to 3,700 MHz), it will be appreciated by those of ordinary skill when provided the present disclosure that the methods and apparatus described herein may be configured to utilize other “quasi licensed” or other spectrum, including without limitations above 4.0 GHz (e.g., currently proposed allocations up to 4.2 GHz).
Additionally, while described primarily in terms of GAA 106 spectrum allocation (see
Moreover, while described in the context of quasi-licensed or unlicensed spectrum, it will be appreciated by those of ordinary skill given the present disclosure that various of the methods and apparatus described herein may be applied to reallocation/reassignment of spectrum or bandwidth within a licensed spectrum context; e.g., for cellular voice or data bandwidth/spectrum allocation, such as in cases where a given service provider must alter its current allocation of available spectrum to users.
Moreover, while various aspects of the present disclosure are described in detail with respect to so-called “4G/4.5G” 3GPP Standards (aka LTE/LTE-A), such aspects—including allocation/use/withdrawal of CBRS spectrum—are generally access technology “agnostic” and hence may be used across different access technologies, including so-called 5G “New Radio” (3GPP Release 15 and TS 38.XXX Series Standards and beyond). Other features and advantages of the present disclosure will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Service Provider Network—
The exemplary service provider network 300 is used in one embodiment of the disclosure to provide backbone and Internet access from the service provider's wireless access nodes (e.g., CBSDs, Wi-Fi APs, FWA devices or base stations 314 operated or maintained by the service provider or its customers/subscribers), one or more stand-alone or embedded cable modems (CMs) 312, 313 in data communication therewith, or even third party access points accessible to the service provider via, e.g., an interposed network such as the Internet 311 (e.g., with appropriate permissions from the access node owner/operator/user). As discussed in greater detail elsewhere herein, the exemplary enhanced CBSD/xNB nodes 314 include the capability of communication with served nodes such as the enhanced CPE 324 discussed infra for, inter alia, more efficient and seamless frequency re-allocations from SAS so as to preserve end-user experience.
As described in greater detail subsequently herein with respect to
In certain embodiments, the service provider network 300 also advantageously permits the aggregation and/or analysis of subscriber- or account-specific data (including inter alia, particular mobile devices associated with such subscriber or accounts) as part of the provision of services to users under the exemplary delivery models described herein. As but one example, device-specific IDs (e.g., MAC address or the like) can be cross-correlated to MSO subscriber data maintained at e.g., the network head end(s) 307 so as to permit or at least facilitate, among other things, (i) user authentication; (ii) correlation of aspects use cases or applications to particular subscriber demographics, such as for delivery of targeted advertising; and (iii) determination of subscription level, and hence subscriber privileges and access to content/features. Moreover, device profiles for particular user devices can be maintained by the MSO, such that the MSO (or its automated proxy processes) can model the user device for wireless capabilities.
The CBSD/xNB wireless access nodes 314 disposed at the service location(s) (e.g., areas or venue(s) of interest) can be coupled to the bearer managed network 300 (
The various components of the exemplary embodiment of the network 300 generally include (i) one or more data and application origination sources 302; (ii) one or more content sources 303, (iii) one or more application distribution servers 304; (iv) one or more video-on-demand (VOD) servers 305, (v) client devices 306, (vi) one or more routers 308, (vii) one or more wireless access node controllers 310 (may be placed more locally as shown or in the headend or “core” portion of network), (viii) one or more cable modems 312, 313, and/or (ix) one or more access nodes 314 (which may include 3GPP-compliant EUTRAN eNodeB functionality as described elsewhere herein). The application server(s) 304, VOD servers 305 and client device(s) 306 are connected via a bearer (e.g., HFC) network 301. A simple architecture comprising one of each of certain components 302, 303, 304, 305, 308, 310 is shown in
It is also noted that cable network architecture is typically a “tree-and-branch” structure, and hence multiple tiered CBSD/xNB access nodes 314 (and other components) may be linked to each other or cascaded via such structure.
The network architecture 320 of
Various content sources 303, 303a are used to provide content to content servers 304, 305 and origin servers 321. For example, content may be received from a local, regional, or network content library as discussed in co-owned U.S. Pat. No. 8,997,136 entitled “APPARATUS AND METHODS FOR PACKETIZED CONTENT DELIVERY OVER A BANDWIDTH-EFFICIENT NETWORK”, which is incorporated herein by reference in its entirety. Alternatively, content may be received from linear analog or digital feeds, as well as third party content sources. Internet content sources 303a (such as e.g., a web server) provide Internet content to a packetized content origin server(s) 321. Other IP content may also be received at the origin server(s) 321, such as voice over IP (VoIP) and/or IPTV content. Content may also be received from subscriber and non-subscriber devices (e.g., a PC or smartphone-originated user made video).
The centralized media server(s) 321, 304 located in the headend 307 may also be replaced with or used in tandem with (e.g., as a backup) to hub media servers (not shown) in one alternative configuration. By distributing the servers to the hub stations 317, the size of the fiber transport network associated with delivering VOD services from the central headend media server is advantageously reduced. Multiple paths and channels are available for content and data distribution to each user, assuring high system reliability and enhanced asset availability. Substantial cost benefits are derived from the reduced need for a large content distribution network, and the reduced storage capacity requirements for hub servers (by virtue of the hub servers having to store and distribute less content).
It will also be recognized that a heterogeneous or mixed server approach may be utilized consistent with the disclosure. For example, one server configuration or architecture may be used for servicing cable, satellite, etc., subscriber CPE-based session requests (e.g., from a user's DSTB or the like), while a different configuration or architecture may be used for servicing mobile client requests. Similarly, the content servers 321, 304 may either be single-purpose/dedicated (e.g., where a given server is dedicated only to servicing certain types of requests), or alternatively multi-purpose (e.g., where a given server is capable of servicing requests from different sources).
The network architecture 320 of
In one exemplary content delivery paradigm, MPEG-based video content (e.g., MPEG-2, H.264/AVC) may be delivered to user IP-based client devices over the relevant physical transport (e.g., DOCSIS channels); that is as MPEG-over-IP-over-MPEG. Specifically, the higher layer MPEG or other encoded content may be encapsulated using an IP network-layer protocol, which then utilizes an MPEG packetization/container format of the type well known in the art for delivery over the RF channels or other transport, such as via a multiplexed transport stream (MPTS). In this fashion, a parallel delivery mode to the normal broadcast delivery exists; e.g., in the cable paradigm, delivery of video content both over traditional downstream QAMs to the tuner of the user's DSTB or other receiver device for viewing on the television, and also as packetized IP data over the DOCSIS QAMs to the user's PC or other IP-enabled device via the user's cable modem 312 (including to end users of the CBSD/xNB access node 314). Delivery in such packetized modes may be unicast, multicast, or broadcast.
Delivery of the IP-encapsulated data may also occur over the non-DOCSIS QAMs, such as via IPTV or similar models with QoS applied.
Individual client devices such as cable modems 312 and associated end-user devices 306a, 306b of the implementation of
The edge switch forwards the packets receive from the CMTS to the QAM modulator, which transmits the packets on one or more physical (QAM-modulated RF) channels to the client devices. The IP packets are typically transmitted on RF channels that are different than the “in band” RF channels used for the broadcast video and audio programming, although this is not a requirement. As noted above, the premises devices such as cable modems 312 are each configured to monitor the particular assigned RF channel (such as via a port or socket ID/address, or other such mechanism) for IP packets intended for the subscriber premises/address that they serve.
In one embodiment, both IP data content and IP-packetized audio/video content is delivered to a user via one or more universal edge QAM devices 340. According to this embodiment, all of the content is delivered on DOCSIS channels, which are received by a premises gateway 360 or cable modem 312, and distributed to one or more respective client devices/UEs 306a, 306b, 306c in communication therewith.
In one implementation, the CM 312 shown in
In parallel with (or in place of) the foregoing delivery mechanisms, the MSO backbone 331 and other network components can be used to deliver packetized content to the user's mobile client device 306c via non-MSO networks. For example, so-called “OTT” content (whether tightly coupled or otherwise) can be ingested, stored within the MSO's network infrastructure, and delivered to the user's mobile device via an interposed ISP (Internet Service Provider) network and public Internet 311 (e.g., at a local coffee shop, via a Wi-Fi AP connected to the coffee shop's ISP via a modem, with the user's IP-enabled end-user device 306c utilizing an Internet browser or MSO/third-party app to stream content according to an HTTP-based approach).
Wireless Services Architecture—
It will be appreciated that while described primarily in terms of CBSD/xNBs 314 which also include EUTRAN (3GPP) compliant eNodeB and/or gNodeB functionality, the latter is by no means of requirement of practicing the broader features of the invention, and in fact non-3GPP signaling and protocols may be utilized to support the various functions described herein. Due to its current ubiquity (especially in mobile devices or UEs), however, the extant 3GPP protocols provide a convenient and effective platform which can be leveraged for CBRS-based operation.
As shown, the illustrated embodiment of the architecture may generally include if desired an MSO-maintained CBRS controller 310 (which may be disposed remotely at the backend or headend of the system within the MSO domain as shown or at the served venue, or at an intermediary site), a CBRS Core/Neutral Host/Private Network Controller 413, an analytics engine 413 in data communication with the CBRS controller 310, an MSO-maintained subscriber and CBRS database 404, one or more CBSD/xNB access nodes 314 in data communication with the CBRS controller 310 (e.g., via existing network architectures including any wired or wireless connection), as well as any number of client devices 306c (smartphones, laptops, tablets, watches, vehicles, etc.). The CBSD/xNB 314 includes in the illustrated embodiment an embedded cable modem 312 used for communication with a corresponding CMTS 339 (
As described subsequently herein, the presence of the MSO controller 310 and analytics engine 413 is optional for purposes of implementing the frequency reassignment methodologies and functions described herein; notably, certain embodiments utilize direct communication between the cognizant SAS (or DP) and the target CBSDs/xNBs, with no need for controller support. However, certain analytics and control functions may be performed by the MSO controller 310 and associated analytics engine in support of efficient frequency management and utilization (including mitigation of session disruption due to e.g., SAS-initiated spectrum withdrawals), depending on inter alia, the degree of integration between the cognizant SAS/DP and the MSO desired. For example, in one implementation, certain sets of rules or priorities may be implemented at the MSO level via logic on the controller 310 and analytics engine 413 which are not visible to the SAS (the SAS being largely agnostic to particulars of each MSO/MNO domain which it serves). As such, the SAS (or DP) may provide the MSO domain with higher-level instructions or directives on frequency/carrier use, reclamation, time periods, etc., and effectively let the MSO domain decide how to execute the process consistent with those instructions or directives.
Likewise, the controller 310 and associated logic can act merely as a passive monitor of the transactions between the SAS/DP and relevant target CBSDs/xNBs (and CPE 324), so as to maintain accurate accounting of user/frequency/CBSD mapping (i.e., which UE is using what frequencies via what CPE and/or CBSD/xNB at any given time, as well as which CPE 324 are utilizing what frequencies for communication with which CBSD/xNBs 314), without actively participating in the reassignment process.
As shown in
The MSO controller 310 in the illustrated embodiment communicates with the DP 208 via an MSO CBRS access network 410, which may be a public internetwork (e.g., the Internet), private network, or other, depending on any security and reliability requirements mandated by the MSO and/or SAS.
As used herein, a CBRS “domain” is defined is any collection of CBSDs/xNBs 314 that are or need to be grouped for management, whether logically or by other scheme; e.g.: according to network operator (NO), according to a serving SAS vendor, and/or by physical disposition (e.g., within a large enterprise, venues, certain geographic area, etc.) In the embodiment of
As shown in
Referring now to
Returning again to
In certain embodiments, each CPE 324 is located within and/or services one or more areas within one or more venues (e.g., a building, room, or plaza for commercial, corporate, academic purposes, and/or any other space suitable for wireless access). Each CBSD/xNB 324 is configured to provide wireless network coverage within its coverage or connectivity range. For example, a venue may have a wireless modem installed within the entrance thereof for prospective customers to connect to, including those in the parking lot via inter alia, their LTE-enabled vehicles or personal devices of operators thereof. Notably, different classes of CPE 324 and CBSD/xNB 314 may be utilized. For instance, as previously noted, Category A devices can transmit up 30 dbm (1 watt), while Category B devices can transmit up to approximately 50 dbm, so the average area can vary widely. In practical terms, a Category A device may have a working range on the order of hundreds of feet, while a Category B device may operate out to thousands of feet or more, the propagation and working range dictated by a number of factors, including the presence of RF or other interferers, physical topology of the venue/area, energy detection or sensitivity of the receiver, etc.
In the exemplary embodiment, one or more CBSDs/xNBs 314 may be indirectly controlled by the CBRS controller 310 (i.e., via infrastructure of the MSO network), or directly controlled by a local or “client” CBRS controller disposed at the venue (not shown). Various combinations of the foregoing direct and indirect control may be implemented within the architecture 400 of
Methods—
Various methods and embodiments thereof for providing quasi-licensed (e.g., CBRS GAA) spectrum reassignment according to the present disclosure are now described with respect to
Referring now to
As discussed above, the CBSD/xNB(s) may interface with the host SAS directly, or via one or more interposed entities such as computerized domain proxy (DP) entities 408. For the purposes of illustration, it will be assumed that each of the registering CBSD/xNBs is/are associated with a common network operator (NO) domain, although this is not a requirement for practicing the method 500.
At step 502 of the method 500, the SAS assigns one or more RF carrier (s) to a given CBSD/xNB or group thereof, based on for instance lack of DoD usage of those carriers in the prescribed area(s). This assignment may occur for example via CBRS-compliant protocol messages transmitted from the SAS or DP to the target CBSD/xNBs indicating their frequency assignment(s) via wired or wireline communication (e.g., backhaul) between the target CBSD/xNBs and the SAS/DP.
Per step 504, the CBSD/xNB(s) establishes operation on the assigned carrier(s), including transmission or broadcast of signals detectable by CPE 324 operating in the area and within communication range.
Per step 506, the CPE 324 invokes its discovery procedures (such as upon UE service request, according to a prescribed schedule, after CPE device re-initialization, etc.) and begins its scan of one or more prescribed frequency bands to attempt to detect and identify a serving CBSD/xNB 314. As previously discussed, such scans can be comparatively time-consuming, and per step 508, the CPE eventually detects one or more of the CBSD/xNBs operating on the SAS-assigned carriers from steps 502-504.
Per step 510, the CPE 324 invokes an attach procedure toward a detected CBSD/xNB 314, and at completion of the procedure, is logically attached with (and in data communication with) the CBSD/xNB. At this point, the CPE forwards its registration data via the CBSD/xNB to the cognizant SAS/DP (step 512), and the CPE is subsequently registered with the SAS per step 514.
Per step 516, after a period of time, the cognizant SAS determines that one or more of the assigned RF carriers require reclamation or reassignment, such as based on incumbent detection or other conditions. The affected CBSD/xNBs accordingly receive instructions issued by the SAS to migrate to the new carrier(s).
Per step 518, the CBSD/xNBs receiving instructions from the SAS each notify their attached CPE 324 via, e.g., protocol messaging, of the impending migration of the carrier(s). As part of this notification (discussed below in greater detail with respect to FIG. 5a), an instructing CBSD/xNB includes data in the notification that instructs the CPE 324 as to the subsequent carrier(s) to be utilized for re-attachment after the migration, and temporal data regarding the migration.
Per step 520 of the method 500, the CBSD/xNB conducts the requisite migration to the new carrier(s) per the SAS allocation (including de-establishing operation on the carrier(s) being migrated away from), and the affected CPE 324 implement the instructions provided by the CBSD/xNB per step 518. In one variant (
In other variants, the temporal value (T) described above is replaced with another metric for determining the duration of suspension, which is not a temporal value per se. For example, in one implementation, a metric such as a number of machine processing, clock, or communication cycles (which may or may not correspond to a prescribed time value) is used to specify the suspension behavior of the device (e.g., CPE 324). As referenced above, it may be that under the prescribed protocols in place, a communication session is determined to be “timed out” or will be terminated after the occurrence of one or more events, such as failure of a prescribed number of retries, failure to receive a prescribed number of ACKs for messages sent, failure to receive a predetermined number of heartbeats, failure to receive a sufficient number of packets within a given time (e.g., in support of a QoS or other requirement), failure of a cryptographic negotiation procedure (e.g., key generation/exchange procedure to authenticate the CPE to the wireless access point) to resolve or complete, or any number of other “preconditions” for determination that an extant session is in fact dead. As such, the various implementations of the present disclosure may use one or more of the foregoing, whether alone or in combination with T, to more finely assess when the CPE should attempt re-attach or conduct other related operations. It may be, for example, that certain sessions or types of sessions can persist longer than others (e.g., until one or more of the above events occurs), and hence the re-attach commencement can be set to anticipate such events sufficiently that the session is not torn down before reattachment on the new carrier occurs.
Lastly, per step 524, the CPE 324 forwards its registration data to the SAS via the now-attached CBSD/xNB 314. In one embodiment, the registration data includes data relating to the reassigned carrier (i.e., the same carrier that the SAS/DP previously instructed the CBSD/xNB to switch to), and hence the SAS accordingly has both the CBSD/xNB and CPE registered as operating on that same carrier within its database.
In the exemplary embodiment, the SAS has knowledge of the individual channels (both GAA and PAL) in a given region, and the identities of the CBSD/xNBs (and CPE 324) to which a given channel is assigned or being used. In situations where there is need for revocation of a given channel (e.g., due to incumbent needs), the SAS needs to identify the impacted CBSDs/CPE. Note that the revocation may be applicable only to a particular geographic region, and hence only a subset of CBSDs/CPE may need to relinquish the channel needed by some incumbent. The SAS having knowledge of both (i) the information regarding the channel needed by an incumbent, and (ii) the affected region, enables identification of CBSDs which are required to relinquish their assigned channel.
Referring now to
Currently, as shown and discussed previously with respect to
In contrast, the inventive approach of
Moreover, it will be recognized that different affected CPE 324 may be granted different values of T based on their configuration, status, current operations (e.g., support of more or less critical applications or processes for end users, whether bearing traffic requiring a prescribed QoS or temporal/latency requirements, etc.). As such, CPE 324 may also be “staggered” in time if desired, as to notification and/or as to the value of T.
Per step 542 of
During the period T, the CPE 324 may signal its connected UE or other devices with a “suspend” command or data, which causes applications or other processes on the UE to also wait a prescribed period, ostensibly so as to avoid the application/process from inadvertently “timing out” while waiting for T to expire. This may be an active process (e.g., a particular command from CPE to UE process configured to cause suspension), or a passive one (e.g., the CPE may simply send the application/process some extant protocol message or communication to avoid any potential timeout.
At step 544, after T expires, the CPE 324 invokes its particular frequency re-acquisition instructions, which obviates a more comprehensive scan or other normal acquisition operations and hence greatly reduces the time for the CPE to acquire the CBSD/xNB on the new carrier(s) and re-attach. In one variant, the CPE 324 is provided a single carrier on which to acquire the CBSD/xNB 314 (F1 in the example of
Once the CPE detects and attaches to the CBSD/xNB on the new carrier(s), the CPE registers with the SAS as operating on the assigned frequency (F1 in the example of
It is noted that as part of the communication of step 538, the SAS may also indicate to the target CBSD/xNB whether the provided RF carrier is the “final” RF carrier as well, or merely a temporary or ephemeral carrier to be used for a transition only. This may be accomplished either by inclusion of information in the protocol message (e.g., an IE specifying the RF carrier status or condition), or the absence of data (e.g., where no IE is provided or the IE is empty, the CBSD/xNB can infer that the RF carrier is of one type or the other). See co-owned and co-pending U.S. patent application Ser. No. 15/986,614 entitled “METHODS AND APPARATUS FOR INTRA-CELL AND INTER-FREQUENCY MOBILITY OPTIMIZATION AND MITIGATION OF SESSION DISRUPTION IN A QUASI-LICENSED WIRELESS SYSTEM” filed May 22, 2018 previously incorporated herein for exemplary frequency migration schemes involving temporary or “bridge” carriers, which may be utilized consistent with the present disclosure. For instance, in one such variant, the SAS signals the bridge or temporary carrier (F1) and the final carrier (F2) to the CBSD/xNB 314 per step 508, and the value of T is determined to accommodate both migrations (from F0 to F1, and F1 to F2). In another variant, individual operations such as that shown in
As referenced above, the CBSD/xNB defines a timer parameter that is given to affected CPE to be used to allow completion of the inter-frequency transition within the time defined by the timer parameter (T). It will be recognized, however, that the SAS or DP may provide and forward this parameter to the CBSD/xNB. For instance, as part of the protocol communication of step 538, the SAS may utilize a defined IE (information element) present in a configuration or status message, with the value of the timer specified. For example, in one variant, the SAS and CBSDs continuously exchange Heartbeat (HB) messages to maintain the status of the allocated channels, perform “health” checks, etc. These messages may also be used by a SAS to terminate a grant/revoke previously granted channel. In one implementation, an IE is added to the HB message to enable the SAS to provide data including: (i) data indicating one or more alternate channels to be utilized (ii) data indicative of whether the channel is temporary or permanent; and (iii) data indicating duration of the CPE “wait” period T corresponding to the CBSD/xNB to change to alternate channel(s) provided (which the CBSD/xNB then forwards to the CPE per step 540).
Likewise, the CPE 324 itself may maintain data on various specific CBSD/xNB devices (or classes of devices) and apply its own indigenously selected value of T when it receives notification of the impending CBSD/xNB non-availability per step 540. For example, the CBSD/xNB may include a device identifier for itself which enables the CPE 324 to select an appropriate value of T. As noted above, these values may also be dynamically selected or situationally dependent; e.g., the CPE may maintain different values of T for a given CBSD/xNB 314 or class of devices based on data forwarded to the CPE relating to the CBSD/xNB current configuration or operational condition. Longer or shorter values of T may be appropriate based on the condition/operations of the CBSD/xNB at the time the SAS dictates a frequency change.
It is also noted that the CPE's use of a specific frequency when performing registration with the SAS (i.e., after re-attachment) also may decrease the SAS grant time response. For instance, in one configuration, the SAS may be required to conduct less processing to register the CPE within its database in association with a prescribed frequency, since that frequency has already been assigned to the parent CBSD/xNB that the CPE is re-attaching to. In one variant, the SAS does not have to research/identify a “new” frequency for the CPE (which it sees in some aspects as merely another CBSD), but rather is presented with, in a sense, a “pre-approved” frequency (i.e., that very recently allocated to the CBSD/xNB) and hence can directly register the CPE with that same frequency with which the CPE is necessarily already operating.
Referring now to
As shown in
Next, per step 604, the CPE 324 scans one or more designated frequency bands to detect the presence of the CBSD/xNB (in response to the UE/device service request). Per step 606, the CPE detects the CBSD/xNB on one or more carriers within the band, and invokes its attach protocol with the CBSD/xNB per step 608.
Per step 610, the CPE forwards its registration data to the cognizant SAS via the (now attached) CBSD/xNB 314, and the CPE is registered with the SAS per step 612.
After a period of time, the CPE invokes a detach operation directed toward the CBSD/xNB per step 614. This may be the result of any number of circumstances, such as lack of UE/device traffic or service for a period of time, reboot of the CPE, testing/maintenance, etc. Per step 616, the CBSD/xNB receives and records the detach request (such as within a mass storage device of the CBSD/xNB or a proxy storage device), and generates a priority list for transmission (notification) of the detaching CPE 324. As discussed above, this priority list is in one implementation a “cheat sheet” for the CPE 324 to use on subsequent attachment so that it can ideally obviate a full scan of the relevant band(s) to detect the CBSD/xNB; rather, the listed carriers in the priority list are used in order to attempt to detect the CBSD/xNB during such subsequent re-attachment. The generation of the priority list may be based on for example historical or recent data relating to SAS RF carrier assignments for that CBSD/xNB, such as where the SAS tends to routinely allocate carriers to that particular CBSD/xNB from within a small/repetitive group of carriers within the 3.55 to 3.7 GHz band. As can be appreciated, this technique will have more benefit when such limited or repeating allocations are made, as opposed to for instance a wholly random process used by the SAS for carrier allocations (the latter having no predictability from the CPE's perspective).
Per step 618, the CBSD/xNB transmits the priority list to the CPE 324, and upon receipt, the CPE invokes its detach procedure to detach from the CBSD/xNB.
After a period of time, the CBSD/xNB receives instructions from the SAS or DP to migrate to a new RF carrier or carriers (step 620); upon receipt of the instructions, the CBSD/xNB conducts the migration. Since the CPE is not attached at this point, the CBSD/xNB does not need to notify it (as in the method 500 of
After a period of time, the UE (or other device) again invokes a service request to its CPE 324 per step 622. In response, the (unattached) CPE accesses its priority list previously received from the CBSD/xNB, and begins attempting detection on discrete ones of the listed RF carriers in order of priority (step 624). Ideally, as noted above, the SAS is somewhat predictable, and hence the CPE can save appreciable time by avoiding a full-scan of the entire band as would be otherwise used in such cases.
Note also that the priority list may include “band” values (e.g., center frequency plus/minus a prescribed band) to search such that the SAS is predictable as to certain bands (versus discrete frequencies). For instance, the SAS may, for a given CBSD/xNB, almost always pick frequencies between 3.660 and 3.665 GHz for allocation; as such, the CPE can scan that band alone, and avoid having to scan say the entire 3.55 to 3.70 GHz band (which is 30 times larger in frequency bandwidth, and hence presumably take proportionately longer to scan).
Returning again to
CBSD/xNB Apparatus—
At a high level, the exemplary CBSD/xNB 314 of
In the exemplary embodiment, the processor 702 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or plurality of processing components mounted on one or more substrates. The processor 702 may also comprise an internal cache memory, and is in communication with a memory subsystem 804, which can comprise, e.g., SRAM, flash and/or SDRAM components. The memory subsystem may implement one or more of DMA type hardware, so as to facilitate data accesses as is well known in the art. The memory subsystem of the exemplary embodiment contains computer-executable instructions which are executable by the processor 702.
The RF antenna(s) 710 are configured to detect and transceive signals from radio access technologies (RATs) in the service area or venue with which the CBSD/xNB is associated. For example, LTE (including, e.g., LTE, LTE-A, LTE-U, LTE-LAA) signals may be used as the basis of communication between the CBSD/xNB 314 and the various mobile devices (e.g., UEs) and/or CPE 324 being served. The antenna(s) 710 may include multiple spatially diverse individual elements in e.g., a MIMO- or MISO-type configuration, such that spatial diversity of the transceived signals can be utilized.
In the exemplary embodiment, the radio interface(s) comprise one or more LTE-based radios compliant with 3GPP. Additional unlicensed, licensed, or quasi-licensed air interfaces may also be used within the CBSD/xNB, including e.g., Wi-Fi, non-CBRS band LTE, 5G NR, or others. Moreover, the LTE radio functionality may be extended to incipient 3GPP-based 5G NR protocols; e.g., at maturation of LTE deployment and when 5G NR-enabled handsets are fielded, such adaptation being accomplished by those of ordinary skill given the contents of the present disclosure. As a brief aside, NG-RAN or “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G” next generation radio system. 3GPP is currently specifying Release 15 NG-RAN, its components, and interactions among the involved nodes including so-called “gNBs” (next generation Node B's or eNBs). NG-RAN will provide very high-bandwidth, very low-latency (e.g., on the order of 1 ms or less “round trip”) wireless communication and efficiently utilize, depending on application, both licensed and unlicensed spectrum of the type described supra in a wide variety of deployment scenarios, including indoor “spot” use, urban “macro” (large cell) coverage, rural coverage, use in vehicles, and “smart” grids and structures. NG-RAN will also integrate with 4G/4.5G systems and infrastructure, and moreover new LTE entities are used (e.g., an “evolved” LTE eNB or “eLTE eNB” which supports connectivity to both the EPC (Evolved Packet Core) and the NR “NGC” (Next Generation Core).
In some aspects, exemplary Release 15 NG-RAN leverages technology and functions of extant LTE/LTE-A technologies (colloquially referred to as 4G or 4.5G), as bases for further functional development and capabilities. For instance, in an LTE-based network, upon startup, an eNB (base station) establishes S1-AP connections towards the MME (mobility management entity) whose commands the eNB is expected to execute. An eNB can be responsible for multiple cells (in other words, multiple Tracking Area Codes corresponding to E-UTRAN Cell Global Identifiers). The procedure used by the eNB to establish the aforementioned S1-AP connection, together with the activation of cells that the eNB supports, is referred to as the S1 SETUP procedure; see inter alia, 3GPP TS 36.413 V14.4. entitled “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 14)” dated September 2017, which is incorporated herein by reference in its entirety.
As such, the various aspects of the present disclosure can be readily adapted for use within the 5G NR context, including use of a CBSD/gNB, and associated CU/DU functionality and “splits” to implement the seamless handover functions described herein.
The tuner 715 in one embodiment comprises a digitally controlled RF tuner capable of reception of signals via the RF front end (receive chain) of the LTE radio 709 in the aforementioned bands, including in one variant simultaneous reception (e.g., both 2.300 to 2.500 and 3.550 to 3.700 GHz bands at the same time).
The processing apparatus 702 is configured to execute at least one computer program stored in memory 804 (e.g., a non-transitory computer readable storage medium); in the illustrated embodiment, such programs include logic to implement the frequency reassignment logic described previously herein (see e.g.,
In some embodiments, the controller logic program 706 utilizes memory 704 or other storage 705 configured to temporarily hold a number of data reports or files before transmission via the backend interface(s) 710 to the SAS 202, 203, DP 208, and/or CC 310 (if present). In other embodiments, application program interfaces (APIs) such as those included in an MSO-provided application or those natively available on the CBSD/xNB (e.g., as part of the computer program noted supra or associated with the controller logic 706) may also reside in the internal cache or other memory 704. Such APIs may include common network protocols or programming languages configured to enable communication between the CBSD/xNB 314 and SAS/DP, and/or CC 310 and other network entities as well as use procedures for collecting, compressing and/or parsing information obtained via the antenna(s) 708 and radio 709. Data stored may relate for example to prescribed 3GPP or CBRS reporting from the UEs (e.g., measurement report data, RSSI, active applications operative on a given UE for purposes of evaluating session activity/currency, etc.) such that a receiving device (e.g., SAS/DP, controller 310, or other EUTRAN or 5GC entity) may interpret the reports in order to extract and analyze the relevant information.
CPE Apparatus—
In the exemplary embodiment, the processor 802 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or plurality of processing components mounted on one or more substrates. The processor 802 may also comprise an internal cache memory, and is in communication with a memory subsystem 804, which can comprise, e.g., SRAM, flash and/or SDRAM components. The memory subsystem may implement one or more of DMA type hardware, so as to facilitate data accesses as is well known in the art. The memory subsystem of the exemplary embodiment contains computer-executable instructions which are executable by the processor 802.
The processor 802 is configured to execute at least one computer program stored in memory 904 (e.g., a non-transitory computer readable storage medium); in the illustrated embodiment, such programs include logic to implement the RF carrier pool maintenance and migration logic described previously herein. Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co-processors (not shown).
The CBRS stack of the CPE is implemented and controlled via the controller process (logic) 806 of the CPE 324 such that CBSD/xNB-to-CPE communication protocols are used to enhance session continuity and perform the frequency reassignment functionality previously described, including CPE functions such as (i) receipt of the instructions and/or priority list data from the CBSD/xNB, implementing the wait timer (T), frequency band scanning or reduced scans (e.g., direct attach attempts at one or more prescribed frequencies, such as those designated in the instructions or the priority list). The logic 806 may also manage other aspects of CPE operation, including “intelligent” detach procedures such as when no UE or other user traffic exists.
In the illustrated embodiment, the CPE 324 may communicate directly with the UE 306c as shown, such as via WLAN or 3GPP LTE/LTE-A/NR protocols, in effect acting as a base station thereto. For use of the 3GPP protocols, this may be the case where the CBSD/xNB is out of wireless range of the UE.
It will be recognized that while certain aspects of the disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the disclosure, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the disclosure disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the disclosure. The scope of the disclosure should be determined with reference to the claims.
It will be further appreciated that while certain steps and aspects of the various methods and apparatus described herein may be performed by a human being, the disclosed aspects and individual methods and apparatus are generally computerized/computer-implemented. Computerized apparatus and methods are necessary to fully implement these aspects for any number of reasons including, without limitation, commercial viability, practicality, and even feasibility (i.e., certain steps/processes simply cannot be performed by a human being in any viable fashion).
This application is a divisional of and claims priority to co-owned and co-pending U.S. patent application Ser. No. 16/427,186 filed on May 30, 2019 entitled “METHODS AND APPARATUS FOR FREQUENCY TRANSITION MANAGEMENT IN A QUASI-LICENSED WIRELESS SYSTEM,” and issuing as U.S. Pat. No. 10,980,025 on Apr. 23, 2021, which claims priority benefit of U.S. Provisional Patent Application Ser. No. 62/799,454 filed Jan. 31, 2019 and entitled “METHODS AND APPARATUS FOR FREQUENCY TRANSITION MANAGEMENT IN A QUASI-LICENSED WIRELESS SYSTEM, each of which are incorporated herein by reference in its entirety. The subject matter of this application is generally related to co-owned and co-pending U.S. patent application Ser. No. 15/902,833 filed Feb. 22, 2018 and entitled “METHODS AND APPARATUS FOR ALLOCATION AND RECONCILIATION OF QUASI-LICENSED WIRELESS SPECTRUM ACROSS MULTIPLE ENTITIES,” which claims priority to U.S. Provisional Patent Application Ser. No. 62/617,549 filed Jan. 15, 2018 of the same title, as well as U.S. patent application Ser. No. 15/677,940 filed Aug. 15, 2017 and entitled “METHODS AND APPARATUS FOR DYNAMIC CONTROL AND UTILIZATION OF QUASI-LICENSED WIRELESS SPECTRUM”, as well as Ser. No. 15/785,283 filed Oct. 16, 2017 and entitled “METHODS AND APPARATUS FOR COORDINATED UTILIZATION OF QUASI-LICENSED WIRELESS SPECTRUM,” and Ser. No. 15/814,133 filed Nov. 15, 2017 and entitled “METHODS AND APPARATUS FOR UTILIZATION OF QUASI-LICENSED WIRELESS SPECTRUM FOR IoT (INTERNET-OF-THINGS) SERVICES,” each of the foregoing incorporated herein by reference in its entirety. The subject matter of this application is also generally related to the subject matter of U.S. patent application Ser. No. 15/986,614 entitled “METHODS AND APPARATUS FOR INTRA-CELL AND INTER-FREQUENCY MOBILITY OPTIMIZATION AND MITIGATION OF SESSION DISRUPTION IN A QUASI-LICENSED WIRELESS SYSTEM” filed May 22, 2018 and incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3999051 | Petschauer | Dec 1976 | A |
| 4339657 | Larson et al. | Jul 1982 | A |
| 4574364 | Tabata et al. | Mar 1986 | A |
| 4604751 | Aichelmann, Jr. et al. | Aug 1986 | A |
| 4692757 | Tsuhara et al. | Sep 1987 | A |
| 4710761 | Kapur et al. | Dec 1987 | A |
| 4845644 | Anthias et al. | Jul 1989 | A |
| 4890098 | Dawes et al. | Dec 1989 | A |
| 4890257 | Anthias et al. | Dec 1989 | A |
| 5113517 | Beard et al. | May 1992 | A |
| 5121475 | Child et al. | Jun 1992 | A |
| 5129055 | Yamazaki et al. | Jul 1992 | A |
| 5155731 | Yamaguchi | Oct 1992 | A |
| 5175813 | Golding et al. | Dec 1992 | A |
| 5245615 | Treu | Sep 1993 | A |
| 5276437 | Horvath et al. | Jan 1994 | A |
| 5408602 | Giokas et al. | Apr 1995 | A |
| 5463768 | Cuddihy et al. | Oct 1995 | A |
| 5487143 | Southgate | Jan 1996 | A |
| 5502839 | Kolnick | Mar 1996 | A |
| 5522025 | Rosenstein | May 1996 | A |
| 5564002 | Brown | Oct 1996 | A |
| 5581686 | Koppolu et al. | Dec 1996 | A |
| 5596702 | Stucka et al. | Jan 1997 | A |
| 5621879 | Kohda | Apr 1997 | A |
| 5664046 | Abecassis | Sep 1997 | A |
| 5673403 | Brown et al. | Sep 1997 | A |
| 5675755 | Trueblood | Oct 1997 | A |
| 5692142 | Craycroft et al. | Nov 1997 | A |
| 5734380 | Adams et al. | Mar 1998 | A |
| 5764230 | Baradel et al. | Jun 1998 | A |
| 5790779 | Ben-Natan et al. | Aug 1998 | A |
| 5831609 | London et al. | Nov 1998 | A |
| 5850544 | Parvathaneny et al. | Dec 1998 | A |
| 5856826 | Craycroft | Jan 1999 | A |
| 5862316 | Hagersten et al. | Jan 1999 | A |
| 5867160 | Kraft, IV et al. | Feb 1999 | A |
| 5874960 | Mairs et al. | Feb 1999 | A |
| 5877755 | Hellhake | Mar 1999 | A |
| 5895472 | Brodsky et al. | Apr 1999 | A |
| 5973702 | Orton et al. | Oct 1999 | A |
| 5991308 | Fuhrmann et al. | Nov 1999 | A |
| 5995103 | Ashe | Nov 1999 | A |
| 5995499 | Hottinen et al. | Nov 1999 | A |
| 6031530 | Trueblood | Feb 2000 | A |
| 6092107 | Eleftheriadis et al. | Jul 2000 | A |
| 6154648 | Comer | Nov 2000 | A |
| 6160872 | Karnowski et al. | Dec 2000 | A |
| 6169725 | Gibbs et al. | Jan 2001 | B1 |
| 6181713 | Patki et al. | Jan 2001 | B1 |
| 6192403 | Jong et al. | Feb 2001 | B1 |
| 6216152 | Wong et al. | Apr 2001 | B1 |
| 6219044 | Ansberry et al. | Apr 2001 | B1 |
| 6233611 | Ludtke et al. | May 2001 | B1 |
| 6240555 | Shoff et al. | May 2001 | B1 |
| 6252889 | Patki et al. | Jun 2001 | B1 |
| 6313880 | Smyers et al. | Nov 2001 | B1 |
| 6317881 | Shah-Nazaroff et al. | Nov 2001 | B1 |
| 6330010 | Nason et al. | Dec 2001 | B1 |
| 6336122 | Lee et al. | Jan 2002 | B1 |
| 6337717 | Nason et al. | Jan 2002 | B1 |
| 6356560 | Venters et al. | Mar 2002 | B1 |
| 6366876 | Looney | Apr 2002 | B1 |
| 6381710 | Kim | Apr 2002 | B1 |
| 6381735 | Hunt | Apr 2002 | B1 |
| 6397262 | Hayden et al. | May 2002 | B1 |
| 6430570 | Judge et al. | Aug 2002 | B1 |
| 6456892 | Dara-Abrams et al. | Sep 2002 | B1 |
| 6460141 | Olden | Oct 2002 | B1 |
| 6469742 | Trovato et al. | Oct 2002 | B1 |
| 6496864 | McCartney | Dec 2002 | B1 |
| 6505298 | Cerbini et al. | Jan 2003 | B1 |
| 6510152 | Gerszberg et al. | Jan 2003 | B1 |
| 6529965 | Thomsen et al. | Mar 2003 | B1 |
| 6532552 | Benignus et al. | Mar 2003 | B1 |
| 6542500 | Gerszberg et al. | Apr 2003 | B1 |
| 6546016 | Gerszberg et al. | Apr 2003 | B1 |
| 6546419 | Humpleman et al. | Apr 2003 | B1 |
| 6600958 | Zondag | Jul 2003 | B1 |
| 6606711 | Andrews et al. | Aug 2003 | B2 |
| 6625274 | Hoffpauir et al. | Sep 2003 | B1 |
| 6630943 | Nason et al. | Oct 2003 | B1 |
| 6631350 | Celi, Jr. et al. | Oct 2003 | B1 |
| 6631403 | Deutsch et al. | Oct 2003 | B1 |
| 6651248 | Alpern | Nov 2003 | B1 |
| 6654722 | Aldous et al. | Nov 2003 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6714534 | Gerszberg et al. | Mar 2004 | B1 |
| 6750879 | Sandberg | Jun 2004 | B2 |
| 6762796 | Nakajoh et al. | Jul 2004 | B1 |
| 6762798 | Messer et al. | Jul 2004 | B1 |
| 6771953 | Chow et al. | Aug 2004 | B1 |
| 6782262 | Lundborg | Aug 2004 | B1 |
| 6802056 | Chaiken et al. | Oct 2004 | B1 |
| 6847649 | Sutanto | Jan 2005 | B2 |
| 6850533 | Gerszberg et al. | Feb 2005 | B2 |
| 6856330 | Chew et al. | Feb 2005 | B1 |
| 6873877 | Tobias et al. | Mar 2005 | B1 |
| 6895573 | Norgaard et al. | May 2005 | B2 |
| 6938254 | Mathur et al. | Aug 2005 | B1 |
| 6941341 | Logston et al. | Sep 2005 | B2 |
| 6944185 | Patki et al. | Sep 2005 | B2 |
| 6948175 | Fong et al. | Sep 2005 | B1 |
| 6948183 | Peterka | Sep 2005 | B1 |
| 6952836 | Donlan et al. | Oct 2005 | B1 |
| 6968364 | Wong et al. | Nov 2005 | B1 |
| 6973050 | Birdwell et al. | Dec 2005 | B2 |
| 6996808 | Niewiadomski et al. | Feb 2006 | B1 |
| 7010796 | Strom et al. | Mar 2006 | B1 |
| 7039633 | Dey et al. | May 2006 | B1 |
| 7055146 | Durr et al. | May 2006 | B1 |
| 7058964 | Khandelwal et al. | Jun 2006 | B2 |
| 7068597 | Fijolek et al. | Jun 2006 | B1 |
| 7080356 | Atallah et al. | Jul 2006 | B2 |
| 7096459 | Keller et al. | Aug 2006 | B2 |
| 7111072 | Matthews et al. | Sep 2006 | B1 |
| 7137106 | Herman et al. | Nov 2006 | B2 |
| 7146305 | Made et al. | Dec 2006 | B2 |
| 7158993 | Schwabe | Jan 2007 | B1 |
| 7181725 | Posegga et al. | Feb 2007 | B1 |
| 7194249 | Phillips et al. | Mar 2007 | B2 |
| 7203869 | Gwak | Apr 2007 | B2 |
| 7213213 | Sekiguchi et al. | May 2007 | B2 |
| 7216170 | Ludvig et al. | May 2007 | B2 |
| 7240104 | Gautney | Jul 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7290253 | Agesen | Oct 2007 | B1 |
| 7316003 | Dulepet et al. | Jan 2008 | B1 |
| 7328333 | Kawano et al. | Feb 2008 | B2 |
| 7370322 | Matena et al. | May 2008 | B1 |
| 7394473 | Asai | Jul 2008 | B2 |
| 7401324 | Dmitriev | Jul 2008 | B1 |
| 7478341 | Dove | Jan 2009 | B2 |
| 7487534 | Peterka et al. | Feb 2009 | B1 |
| 7546602 | Hejlsberg et al. | Jun 2009 | B2 |
| 7552450 | Evans et al. | Jun 2009 | B1 |
| 7698606 | Ladd et al. | Apr 2010 | B2 |
| 7814544 | Wilhelm | Oct 2010 | B1 |
| 7945902 | Sahoo | May 2011 | B1 |
| 8024607 | Ladd et al. | Sep 2011 | B2 |
| 8042113 | Clohessy et al. | Oct 2011 | B2 |
| 8046636 | Ladd et al. | Oct 2011 | B2 |
| 8189465 | Pawar et al. | May 2012 | B1 |
| 8218422 | Venturino et al. | Jul 2012 | B2 |
| 8302111 | Ladd et al. | Oct 2012 | B2 |
| 8321723 | Ladd et al. | Nov 2012 | B2 |
| 8799723 | Ladd et al. | Aug 2014 | B2 |
| 8997136 | Brooks et al. | Mar 2015 | B2 |
| 9166891 | Hu et al. | Oct 2015 | B2 |
| 9258809 | Liao et al. | Feb 2016 | B2 |
| 9386496 | Gupta et al. | Jul 2016 | B2 |
| 9413651 | Tsym et al. | Aug 2016 | B2 |
| 9473957 | Wellington | Oct 2016 | B2 |
| 9526056 | Tomici et al. | Dec 2016 | B2 |
| 9564932 | Pack et al. | Feb 2017 | B1 |
| 9591491 | Tapia et al. | Mar 2017 | B2 |
| 9612816 | Choi et al. | Apr 2017 | B2 |
| 9654149 | Piipponen et al. | May 2017 | B2 |
| 9699663 | Jovancevic | Jul 2017 | B1 |
| 9730135 | Rahman | Aug 2017 | B1 |
| 9730143 | Gormley et al. | Aug 2017 | B2 |
| 9769692 | Freda et al. | Sep 2017 | B2 |
| 9807778 | Ma | Oct 2017 | B2 |
| 9813148 | Syed et al. | Nov 2017 | B2 |
| 9887864 | Han et al. | Feb 2018 | B1 |
| 10098565 | Gazdzinski | Oct 2018 | B2 |
| 10135730 | Chou | Nov 2018 | B2 |
| 10340976 | Kakinada et al. | Jul 2019 | B2 |
| 10405192 | Kakinada et al. | Sep 2019 | B2 |
| 10484876 | Shah et al. | Nov 2019 | B2 |
| 10492204 | Kakinada et al. | Nov 2019 | B2 |
| 10499409 | Shattil | Dec 2019 | B2 |
| 10506456 | Lou et al. | Dec 2019 | B2 |
| 10531309 | Li et al. | Jan 2020 | B1 |
| 10536859 | Gunasekara et al. | Jan 2020 | B2 |
| 10680883 | Hall et al. | Jun 2020 | B2 |
| 10805562 | Nakamura et al. | Oct 2020 | B2 |
| 11026205 | Hmimy et al. | Jun 2021 | B2 |
| 11317296 | Vaidya et al. | Apr 2022 | B2 |
| 11363466 | Khalid et al. | Jun 2022 | B2 |
| 20010007138 | Iida et al. | Jul 2001 | A1 |
| 20010049691 | Asazu | Dec 2001 | A1 |
| 20020009149 | Rodriguez et al. | Jan 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020034193 | Patki et al. | Mar 2002 | A1 |
| 20020038358 | Sweatt et al. | Mar 2002 | A1 |
| 20020040470 | Guthrie et al. | Apr 2002 | A1 |
| 20020044567 | Voit et al. | Apr 2002 | A1 |
| 20020044569 | Kwok et al. | Apr 2002 | A1 |
| 20020049978 | Rodriguez et al. | Apr 2002 | A1 |
| 20020052977 | Stall | May 2002 | A1 |
| 20020073244 | Davies et al. | Jun 2002 | A1 |
| 20020083214 | Heisig et al. | Jun 2002 | A1 |
| 20020112090 | Bennett et al. | Aug 2002 | A1 |
| 20020122040 | Noyle | Sep 2002 | A1 |
| 20020126144 | Chenede | Sep 2002 | A1 |
| 20020126748 | Rafie et al. | Sep 2002 | A1 |
| 20020144193 | Hicks et al. | Oct 2002 | A1 |
| 20020170033 | Chen | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020174433 | Baumgartner et al. | Nov 2002 | A1 |
| 20020191028 | Senechalle et al. | Dec 2002 | A1 |
| 20020198868 | Kinzhalin et al. | Dec 2002 | A1 |
| 20030005454 | Rodriguez et al. | Jan 2003 | A1 |
| 20030009765 | Linden et al. | Jan 2003 | A1 |
| 20030009769 | Hensgen et al. | Jan 2003 | A1 |
| 20030037331 | Lee | Feb 2003 | A1 |
| 20030041291 | Hashem et al. | Feb 2003 | A1 |
| 20030056155 | Austen et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061240 | McCann et al. | Mar 2003 | A1 |
| 20030081664 | Lu et al. | May 2003 | A1 |
| 20030105995 | Schroath et al. | Jun 2003 | A1 |
| 20030107604 | Ording | Jun 2003 | A1 |
| 20030110331 | Kawano et al. | Jun 2003 | A1 |
| 20030110511 | Schutte et al. | Jun 2003 | A1 |
| 20030121055 | Kaminski et al. | Jun 2003 | A1 |
| 20030122879 | Inui et al. | Jul 2003 | A1 |
| 20030140285 | Wilkie | Jul 2003 | A1 |
| 20030158906 | Hayes | Aug 2003 | A1 |
| 20030163811 | Luehrs | Aug 2003 | A1 |
| 20030181241 | Oakes et al. | Sep 2003 | A1 |
| 20030188320 | Shing | Oct 2003 | A1 |
| 20030204848 | Cheng et al. | Oct 2003 | A1 |
| 20030217197 | Chan et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030229899 | Thompson et al. | Dec 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20030231855 | Gates et al. | Dec 2003 | A1 |
| 20040001021 | Choo et al. | Jan 2004 | A1 |
| 20040003400 | Carney et al. | Jan 2004 | A1 |
| 20040034697 | Fairhurst et al. | Feb 2004 | A1 |
| 20040040041 | Crawford | Feb 2004 | A1 |
| 20040073944 | Booth | Apr 2004 | A1 |
| 20040078695 | Bowers et al. | Apr 2004 | A1 |
| 20040078829 | Patel et al. | Apr 2004 | A1 |
| 20040083464 | Cwalina et al. | Apr 2004 | A1 |
| 20040098730 | Foote et al. | May 2004 | A1 |
| 20040103434 | Ellis | May 2004 | A1 |
| 20040107451 | Khandelwal et al. | Jun 2004 | A1 |
| 20040143836 | McCormack et al. | Jul 2004 | A1 |
| 20040158829 | Beresin et al. | Aug 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186603 | Sanford et al. | Sep 2004 | A1 |
| 20040187152 | Francis et al. | Sep 2004 | A1 |
| 20040196834 | Ofek et al. | Oct 2004 | A1 |
| 20040199903 | Iizuka | Oct 2004 | A1 |
| 20040205339 | Medin | Oct 2004 | A1 |
| 20040218736 | Fang et al. | Nov 2004 | A1 |
| 20040230754 | Gumm et al. | Nov 2004 | A1 |
| 20040236759 | Young | Nov 2004 | A1 |
| 20040261092 | Addington et al. | Dec 2004 | A1 |
| 20040261114 | Addington et al. | Dec 2004 | A1 |
| 20040261116 | McKeown et al. | Dec 2004 | A1 |
| 20040261126 | Addington et al. | Dec 2004 | A1 |
| 20050015799 | Park | Jan 2005 | A1 |
| 20050021766 | McKeowen et al. | Jan 2005 | A1 |
| 20050027851 | McKeown et al. | Feb 2005 | A1 |
| 20050071818 | Reissman et al. | Mar 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050120385 | Stalker | Jun 2005 | A1 |
| 20050132346 | Tsantilis | Jun 2005 | A1 |
| 20050160045 | Watanabe et al. | Jul 2005 | A1 |
| 20050162267 | Khandelwal et al. | Jul 2005 | A1 |
| 20050177832 | Chew | Aug 2005 | A1 |
| 20050273762 | Lesh | Dec 2005 | A1 |
| 20060005183 | Minear et al. | Jan 2006 | A1 |
| 20060020950 | Ladd et al. | Jan 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060070051 | Kuck et al. | Mar 2006 | A1 |
| 20060129947 | Hamzy et al. | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060143492 | Leduc et al. | Jun 2006 | A1 |
| 20060161946 | Shin | Jul 2006 | A1 |
| 20060188004 | Kizu et al. | Aug 2006 | A1 |
| 20070094345 | Rabbers et al. | Apr 2007 | A1 |
| 20070207771 | Bowser et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070261090 | Miller et al. | Nov 2007 | A1 |
| 20070288897 | Branda et al. | Dec 2007 | A1 |
| 20070294673 | Guerrera et al. | Dec 2007 | A1 |
| 20080010506 | Tabei et al. | Jan 2008 | A1 |
| 20080097913 | Dicks et al. | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080126540 | Zeng et al. | May 2008 | A1 |
| 20080178153 | Fox et al. | Jul 2008 | A1 |
| 20080196011 | Bhandari et al. | Aug 2008 | A1 |
| 20080220786 | Beacham | Sep 2008 | A1 |
| 20080220788 | Stanwood et al. | Sep 2008 | A1 |
| 20080256510 | Auerbach | Oct 2008 | A1 |
| 20080288930 | Chen et al. | Nov 2008 | A1 |
| 20090034443 | Walker et al. | Feb 2009 | A1 |
| 20090129273 | Zou | May 2009 | A1 |
| 20090170472 | Chapin et al. | Jul 2009 | A1 |
| 20090222867 | Munetsugu | Sep 2009 | A1 |
| 20090253438 | Chater-Lea et al. | Oct 2009 | A1 |
| 20090323516 | Bhagwan et al. | Dec 2009 | A1 |
| 20100035610 | Narang et al. | Feb 2010 | A1 |
| 20100094956 | Zuckerman et al. | Apr 2010 | A1 |
| 20100128608 | Zou et al. | May 2010 | A1 |
| 20100234042 | Chan et al. | Sep 2010 | A1 |
| 20100262722 | Vauthier et al. | Oct 2010 | A1 |
| 20100309806 | Wu et al. | Dec 2010 | A1 |
| 20110014924 | Hwang et al. | Jan 2011 | A1 |
| 20110124335 | Martin et al. | May 2011 | A1 |
| 20110292970 | Lansford et al. | Dec 2011 | A1 |
| 20130007413 | Thomson et al. | Jan 2013 | A1 |
| 20130122903 | Farnsworth et al. | May 2013 | A1 |
| 20130201316 | Binder et al. | Aug 2013 | A1 |
| 20130247027 | Shah et al. | Sep 2013 | A1 |
| 20130281092 | Gassend | Oct 2013 | A1 |
| 20130288675 | Gassend | Oct 2013 | A1 |
| 20130303145 | Harrang et al. | Nov 2013 | A1 |
| 20130315124 | Rapaport et al. | Nov 2013 | A1 |
| 20130336175 | Um | Dec 2013 | A1 |
| 20140035182 | Boyer et al. | Feb 2014 | A1 |
| 20140106672 | Jeon et al. | Apr 2014 | A1 |
| 20140194068 | Coppage et al. | Jul 2014 | A1 |
| 20140241187 | Barkay et al. | Aug 2014 | A1 |
| 20140269526 | Mitola, III | Sep 2014 | A1 |
| 20140282704 | Tumuluru et al. | Sep 2014 | A1 |
| 20140282802 | Bowler et al. | Sep 2014 | A1 |
| 20140308986 | Yang et al. | Oct 2014 | A1 |
| 20140354442 | Maity et al. | Dec 2014 | A1 |
| 20150055623 | Li et al. | Feb 2015 | A1 |
| 20150058861 | Zheng et al. | Feb 2015 | A1 |
| 20150071239 | Zhang et al. | Mar 2015 | A1 |
| 20150156095 | Lu | Jun 2015 | A1 |
| 20150208262 | Siomina | Jul 2015 | A1 |
| 20150280847 | Somasundaram et al. | Oct 2015 | A1 |
| 20150304856 | Garcia et al. | Oct 2015 | A1 |
| 20150334664 | Sawai et al. | Nov 2015 | A1 |
| 20150341753 | Chen et al. | Nov 2015 | A1 |
| 20150373741 | Yerramalli et al. | Dec 2015 | A1 |
| 20160007138 | Palanisamy et al. | Jan 2016 | A1 |
| 20160007147 | Zhang et al. | Jan 2016 | A1 |
| 20160073259 | Lee et al. | Mar 2016 | A1 |
| 20160127185 | McAllister et al. | May 2016 | A1 |
| 20160128001 | Tsuda | May 2016 | A1 |
| 20160165066 | Yang et al. | Jun 2016 | A1 |
| 20160182134 | Kol et al. | Jun 2016 | A1 |
| 20160212031 | Jain et al. | Jul 2016 | A1 |
| 20160234746 | Gopal et al. | Aug 2016 | A1 |
| 20160330743 | Das et al. | Nov 2016 | A1 |
| 20160381600 | Aksu | Dec 2016 | A1 |
| 20170026203 | Thomas et al. | Jan 2017 | A1 |
| 20170094527 | Shattil et al. | Mar 2017 | A1 |
| 20170111846 | Kang | Apr 2017 | A1 |
| 20170149937 | Ren et al. | May 2017 | A1 |
| 20170155703 | Hao et al. | Jun 2017 | A1 |
| 20170164326 | Worrall | Jun 2017 | A1 |
| 20170188241 | Mueck et al. | Jun 2017 | A1 |
| 20170208540 | Egner et al. | Jul 2017 | A1 |
| 20170237767 | George et al. | Aug 2017 | A1 |
| 20170257750 | Gunasekara et al. | Sep 2017 | A1 |
| 20170295497 | MacMullan et al. | Oct 2017 | A1 |
| 20170295578 | Khoshnevisan et al. | Oct 2017 | A1 |
| 20170303138 | Barmettler et al. | Oct 2017 | A1 |
| 20170311290 | Adjakple et al. | Oct 2017 | A1 |
| 20170316233 | Kherani et al. | Nov 2017 | A1 |
| 20170318472 | Yu et al. | Nov 2017 | A1 |
| 20170359731 | Soldati et al. | Dec 2017 | A1 |
| 20180007587 | Feldman et al. | Jan 2018 | A1 |
| 20180035463 | Mallik | Feb 2018 | A1 |
| 20180049036 | Sethi et al. | Feb 2018 | A1 |
| 20180063736 | Sadeghi et al. | Mar 2018 | A1 |
| 20180063758 | Velu | Mar 2018 | A1 |
| 20180115903 | Badic | Apr 2018 | A1 |
| 20180124613 | Kang et al. | May 2018 | A1 |
| 20180132112 | Khoshnevisan et al. | May 2018 | A1 |
| 20180146058 | Somayazulu et al. | May 2018 | A1 |
| 20180146408 | Meylan et al. | May 2018 | A1 |
| 20180167948 | Egner et al. | Jun 2018 | A1 |
| 20180199214 | Shen | Jul 2018 | A1 |
| 20180234403 | Casella et al. | Aug 2018 | A1 |
| 20180235007 | Gou et al. | Aug 2018 | A1 |
| 20180242184 | Yerramalli et al. | Aug 2018 | A1 |
| 20180255576 | Bhorkar et al. | Sep 2018 | A1 |
| 20180279212 | Malik et al. | Sep 2018 | A1 |
| 20180316563 | Kumar et al. | Nov 2018 | A1 |
| 20180323938 | Takeda et al. | Nov 2018 | A1 |
| 20180351665 | Fukuta et al. | Dec 2018 | A1 |
| 20180352386 | Gunasekara et al. | Dec 2018 | A1 |
| 20180375887 | Dezent et al. | Dec 2018 | A1 |
| 20190021012 | Beck et al. | Jan 2019 | A1 |
| 20190028182 | Smyth et al. | Jan 2019 | A1 |
| 20190037480 | Sun et al. | Jan 2019 | A1 |
| 20190044614 | Khoshnevisan et al. | Feb 2019 | A1 |
| 20190081690 | Mueck et al. | Mar 2019 | A1 |
| 20190082447 | Harsha et al. | Mar 2019 | A1 |
| 20190098510 | Guo et al. | Mar 2019 | A1 |
| 20190098632 | Martin et al. | Mar 2019 | A1 |
| 20190104551 | Deenoo et al. | Apr 2019 | A1 |
| 20190115950 | Kakinada et al. | Apr 2019 | A1 |
| 20190150182 | Koorapaty et al. | May 2019 | A1 |
| 20190167948 | Klocke et al. | Jun 2019 | A1 |
| 20190182895 | Di Girolamo et al. | Jun 2019 | A1 |
| 20190222266 | Cui et al. | Jul 2019 | A1 |
| 20190230613 | Kim et al. | Jul 2019 | A1 |
| 20190239190 | Patel et al. | Aug 2019 | A1 |
| 20190253878 | Yu | Aug 2019 | A1 |
| 20190296789 | Yu et al. | Sep 2019 | A1 |
| 20190319814 | Das | Oct 2019 | A1 |
| 20190320490 | Liu et al. | Oct 2019 | A1 |
| 20190349848 | Bali | Nov 2019 | A1 |
| 20190364565 | Hmimy et al. | Nov 2019 | A1 |
| 20190373615 | Cimpu et al. | Dec 2019 | A1 |
| 20190393926 | Kakinada et al. | Dec 2019 | A1 |
| 20190394790 | Damnjanovic et al. | Dec 2019 | A1 |
| 20200021689 | Sultana et al. | Jan 2020 | A1 |
| 20200025629 | Zinger et al. | Jan 2020 | A1 |
| 20200053545 | Wong et al. | Feb 2020 | A1 |
| 20200059795 | Kakinada et al. | Feb 2020 | A1 |
| 20200083892 | Kundu et al. | Mar 2020 | A1 |
| 20200084759 | Liu et al. | Mar 2020 | A1 |
| 20200146058 | Xu et al. | May 2020 | A1 |
| 20200178237 | Kakinada et al. | Jun 2020 | A1 |
| 20200187150 | Eisner | Jun 2020 | A1 |
| 20200221392 | Xue et al. | Jul 2020 | A1 |
| 20200228993 | Gunasekara | Jul 2020 | A1 |
| 20200252933 | Hmimy et al. | Aug 2020 | A1 |
| 20200275457 | Hmimy | Aug 2020 | A1 |
| 20200344515 | Wong et al. | Oct 2020 | A1 |
| 20210014693 | Syed et al. | Jan 2021 | A1 |
| 20210026711 | Ovadia et al. | Jan 2021 | A1 |
| 20210037444 | Harel | Feb 2021 | A1 |
| 20210051653 | Park et al. | Feb 2021 | A1 |
| 20210076424 | Mukherjee et al. | Mar 2021 | A1 |
| 20210105633 | Vaidya et al. | Apr 2021 | A1 |
| 20210126662 | Solichien | Apr 2021 | A1 |
| 20210127423 | Park et al. | Apr 2021 | A1 |
| 20210136838 | Khalid et al. | May 2021 | A1 |
| 20210204322 | Lou et al. | Jul 2021 | A1 |
| 20210235495 | Xu et al. | Jul 2021 | A1 |
| 20210266914 | Yoo et al. | Aug 2021 | A1 |
| 20210274506 | Raghavan et al. | Sep 2021 | A1 |
| 20210376905 | Zhou et al. | Dec 2021 | A1 |
| 20220007200 | Sevindik et al. | Jan 2022 | A1 |
| 20220007374 | Sevindik et al. | Jan 2022 | A1 |
| 20220167176 | Khalid | May 2022 | A1 |
| 20220183093 | Sevindik et al. | Jun 2022 | A1 |
| 20220191675 | Mukherjee | Jun 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 1046259 | Oct 2000 | EP |
| 2294860 | Apr 2017 | EP |
| 2585394 | Jan 2021 | GB |
| WO-0024192 | Apr 2000 | WO |
| WO-0213039 | Feb 2002 | WO |
| WO-2005065198 | Jul 2005 | WO |
| WO-2013020599 | Feb 2013 | WO |
| WO-2017130494 | Aug 2017 | WO |
| WO-2017186294 | Nov 2017 | WO |
| WO-2019140461 | Jul 2019 | WO |
| WO-2019226838 | Nov 2019 | WO |
| WO-2021050957 | Mar 2021 | WO |
| WO-2021067810 | Apr 2021 | WO |
| Entry |
|---|
| Palola M., et al., “Field Trial of the 3.5 GHz Citizens Broadband Radio ServiceGoverned by a Spectrum Access System (SAS),” IEEE International Symposium on Dynamic Spectrum Access Networks, 2017, 9 pages. |
| Souryal, Michael R., et al., “Effect of Federal Incumbent Activity or on CBRS Commercial Service”, International Symposium on Dynamic Spectrum Access Networks (DySPAN), IEEE 2019, 5 pages. |
| Allen, et al., The Case for Run-Time Types in Generic Java, Rice University 2002 pp. 1-6. |
| Chapter 16—Window Management. Xlib Programming Manual, No Date. 38 pages. |
| Chapter 4—Window Manager for Mac ©. Apple Computer. Inc., Jul. 11, 1996, 4 pages. |
| Chapter 7—Window Management, SOL library Documentation vU.3-rev 1, Sep. 2001, 2 pages. |
| Chou, et al., Open CPE Architecture: A Solution to the Delivery of Integrated Services over Broadband, Intel Communication Group, Corp. pp. 1-10, 2001. |
| Curran, et al., 8th IEEE International Conference on Communication Systems Singapore, Nov. 25-28, 2002 the Use of Dynamically Reconfigurable Protocol Stacks for Streaming Multimedia to Mobile Devices, http://www.infm.ulst.ac.uk/.about.kevin/pubs.htm. |
| Day, “Java Media Framework Player API”, Apr. 1997, XP-002093309, www.javaworld.com. |
| Deering, S., et al., “Internet Protocol, Version 6 (IPv6) Specification”, Internet Engineering Task Force (IETF) RFC 2460, Dec. 1998, 39 pages. |
| Eldering, Charles, Customer Permises Epuipment Residential Broadband Networks, Jun. 1997, IEEE, p. 114-212. |
| Ellis, “Getting to Know the OpenCable Application Platform,” Sun microsystems, Jun. 2006. |
| Evain, “The Multimedia Home Platform” EBU Review—Technical, European Broadcasting Union. Brussels, BE, No. 275, Mar. 21, 1998, pp. 4-10, XP000767493. |
| Han, et al., Websplitter copyright 2000. |
| Hentschel et al., Video Quality of Service for Consumer Terminal a Novel System for Programmable Componets, 2002, IEEE, pp. 28-29. |
| Hutchings, et al., New Operation for Display Space Management and Window Management Technical Report GIT-GVU-02-18, Aug. 2002, College of Computing/GVU Center. 20 pages. |
| Hutchings, et al., “Display Space Usage and Window Management Operation Comparison between Single Monitor and Multiple Monitor Users” nodate. 8 pages. |
| “Internet Protocol DARPA Internet Program Protocol Specification, IETF RCF 791 (Sep. 1981) and Deering et al., Internet Protocol, Version 6 (IPv6) Specification, IETF RFC 2460 (Dec. 1998).” |
| “Internet Protocol, DARPA Internet Program, Protocol Specification”, IETF RCF 791, Sep. 1981, 50 pages. |
| Java Media Players, V.1.0.5, May 5, 1998, X940410443, Sun Microsystems, Inc. |
| “JMFRegistry User's Guide”, Sun Microsystems, XP-002573305, Mar. 8, 2010. |
| Kar, et al., Cable's Home Digital Network Interface of Choice, 1999, Cable Television Lab. IEEE, pp. 34-35. |
| Luu, MainWin and Window Managers for Mainsoft © Sep. 27, 2000, 5 pages. |
| Mayer, “Analyzing the Use of Interfaces in Large OO Projects,” ACM, Oct. 2003. |
| Motorola, Control Management Module (CMM 2000) information sheets: 4 pages; C Motorola, Inc. 2001; www.motorola.comfbroadband. |
| Motorola, HFC Manager, Integrated Element Management System information sheets; 4 pages; .COPYRGT. Motorola, Inc. 2003; www.motorola.com/broadband. |
| Motorola Product Detail, HFC Manager HFC Element Management System; 1 page: © Motorola, Inc. 2004; www.motorola.com/lbroadband. |
| Motorola—DCT2000 Digital Consumer Terminal Installation Manual; 70 pgs. |
| Motorola—DCT5100 Digital Consumer Terminal Installation Manual; 81 pgs. |
| OCAP Applications in Detail (pp. 1-8), www.tvwithoutborders.com, Feb. 13, 2010. |
| OpenCable Application Platform Specification OC-SP-OCAP1.0-IF-I09-031121. |
| OpenCable Application Platform Specification (“OpenCable” copyright 2001-2003 pp. 1-398). |
| OpenCable Host Device, Core Functional Requirements, Issued Specification (OC-SP-HOST-CFR-114-030905), Sep. 5, 2003, 81 pages. |
| Scientific Atlanta Company Overview web pages, 3 pages, no date http://www.scientificatlanta.com/newscentedifrarne.sub.--companyoverview.- htm. |
| Scientific Atlanta, Recognize, Trouble-Shoot, Correct information sheet; 1 page; no date; www.scientificatlanta.com. |
| Scientific Atlanta, ROSA Network Management System and Element Management web pages, 10 pages, © Scientific Atlanta 2006, www.scientiicatlanta.com. |
| Scientific Atlanta, Subscriber Networks; Explorer.RTM. 3100HD High Definition DHCT information pages; Oct. 2001; 2 pgs. |
| Scientific Atlanta, Subscriber Networks; Explorer.RTM. 4200 Home Gateway information pages; Sep. 2003; 3 pgs. |
| Scientific Atlanta, Subscriber Products; Explorer.RTM. 8000.TM. Home Entertainment Server information pages; Nov. 2003; 4 pgs. |
| Signaling Protocols and Procedures for Citizens Broadband Radio Service (CBRS): Spectrum Access System, (SAS)—Citizens Broadband Radio Service Device (CBSD) Interface Technical Specification—Document WINNF-TS-0016, Version V1.2.1.3, Jan. 3, 2018, 60 pages. |
| Tan, et al., WinCuts: Manipulating Arbitrary Window Regions for More Effective Use of Screen Space⋅ Microsoft Research. No Date. 4 pages. |
| Xie, et al., “MAPO: Mining API Usages from Open Source Repositories,” ACM, May 2006. |
| Kulacz L., et al., “Coordinated Spectrum Allocation and Coexistence Management in CBRS-SAS Wireless Networks” IEEE Access 07, pp. 139294-139316. (Year: 2019). |
| Number | Date | Country | |
|---|---|---|---|
| 20210274499 A1 | Sep 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62799454 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16427186 | May 2019 | US |
| Child | 17228556 | US |
