Patent ID: 12232190

DETAILED DESCRIPTION

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 cellular xNB, 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 inSignaling 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, 3.1 and 4.0.

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, (G)DDR/2/3/4/5/6 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3D memory, stacked memory such as HBM/HBM2, and spin Ram, 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 terms “5G” and “New Radio (NR)” refer without limitation to apparatus, methods or systems compliant with 3GPP Release 15, and any modifications, subsequent Releases, or amendments or supplements thereto which are directed to New Radio technology, whether licensed or unlicensed.

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 “quasi-licensed” refers without limitation to spectrum which is at least temporarily granted, shared, or allocated for use on a dynamic or variable basis, whether such spectrum is unlicensed, shared, licensed, or otherwise. Examples of quasi-licensed spectrum include without limitation CBRS, DSA, GOGEU TVWS (TV White Space), and LSA (Licensed Shared Access) spectrum.

As used herein, the term “SAE (Spectrum Allocation Entity)” refers without limitation to one or more entities or processes which are tasked with or function to allocate quasi-licensed spectrum to users. Examples of SAEs include SAS (CBRS). PMSE management entities, and LSA Controllers or Repositories.

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 “shared access” refers without limitation to (i) coordinated, licensed sharing such as e.g., traditional fixed link coordination in 70/80/90 GHz and the U.S. FCC's current rulemaking on potential database-coordinated sharing by fixed point-to-multipoint deployments in the C-band (3.7-4.2 GHz); (ii) opportunistic, unlicensed use of unused spectrum by frequency and location such as TV White Space and the U.S. FCC's proposal to authorize unlicensed sharing in the uplink C-band and other bands between 5925 and 7125 MHz; (iii) two-tier Licensed Shared Access (LSA) based on geographic areas and database assist such as e.g., within 3GPP LTE band 40 based on multi-year sharing contracts with tier-one incumbents; and (iv) three-tier shared access (including quasi-licensed uses) such as CBRS.

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 “users” may include without limitation end users (e.g., individuals, whether subscribers of the MSO network, the MNO network, or other), the receiving and distribution equipment or infrastructure such as a FWA/CPE or CBSD, venue operators, third party service providers, or even entities within the MSO itself (e.g., a particular department, system or processing entity).

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/ad 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, LoRa, IoT-NB, SigFox, 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).

Overview

In one exemplary aspect, the present disclosure provides methods and apparatus for enhancing wireless coverage area and data rates to served user devices (e.g., fixed wireless consumer premises equipment or CPE) via relaying through one or more other CPE.

In one embodiment, the CPE all utilize “quasi-licensed” spectrum provided by the recent CBRS technology initiative via 3GPP-based infrastructure and protocols. In One or more “in-coverage” CPE (i.e., those with sufficiently strong signals and data rates) are used as relays to provide requisite data rates to CPE that are at the edge of coverage of their servicing network (or are otherwise prevented from obtaining or establishing sufficiently strong signal, such as via topological obstructions or other such phenomena), and accordingly cannot meet user experience or service level agreement (SLA) requirements. In one variant, the participating or eligible CPE within the network have processes operative thereon (e.g., “iperf” agents) that can measure key performance metrics or indicators (KPIs) such as data throughput (TP), latency, jitter, or BER. Participating CPE that, e.g., can sustain data rates higher than required by their own SLAs or requirements, can act as the relays for other under-performing CPE, such that all the CPE can meet their performance requirements simultaneously.

In one implementation, the under-performing or “secondary” CPE can search for and acquire in-coverage or over-performing CPE (aka “primary” CPE), and establishes one or more Device-to-Device (D2D) connections to these primary CPE in order to supplement signal being received by the secondary CPE directly from its serving base station (e.g., 3GPP eNB or gNB operating as a CBRS CBSD). Once the connection(s) is/are established, the secondary CPE can receive/transmit data from/to the participating primary CPEs. In one configuration, CBRS GAA and/or PAL spectrum is allocated to the primary and secondary CPE (such as by a request to a SAS) in order to support the additional D2D connection(s).

The exemplary embodiment described above improves, inter alia, coverage area due to the gain and spatial diversity provided via relaying, without the need to use excessively large power at the serving transmitter (e.g., gNB/CBSD).

In addition, the provision of enhanced signal quality in both uplink (UL) and downlink (DL) directions for the secondary CPE at the cell edge via relaying increases the network capacity without the need to install additional infrastructure such as CBSDs and associated backhaul, thereby effectively adding more customers to the network with a given CAPEX (capital expenditure).

The methods and apparatus described herein may also advantageously be extended to other shared-access architectures (i.e., other than CBRS) such as for example DSA, LSA, and TVWS systems.

Detailed Description of Exemplary Embodiments

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 base station (e.g., gNB) 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), or a mobile network operator (MNO), 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., indoors, 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, Version6 (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 limitation DSA, LSA, or TVWS systems, and those above 4.0 GHz (e.g., currently proposed allocations up to 4.2 GHz, and even millimeter wave bands such as those between 24 and 100 GHz).

Additionally, while described primarily in terms of GAA106spectrum allocation (seeFIG.1), the methods and apparatus described herein may also be adapted for allocation of other “tiers” of CBRS or other unlicensed spectrum (whether in relation to GAA spectrum, or independently), including without limitation e.g., so-called Priority Access License (PAL) spectrum104.

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 some aspects of the present disclosure are described in detail with respect to so-called “4G/4.5G” 3GPP Standards (aka LTE/LTE-A) and so-called 5G “New Radio” (3GPP Release 15 and TS 38.XXX Series Standards and beyond), such aspects—including allocation/use/withdrawal of CBRS spectrum—are generally access technology “agnostic” and hence may be used across different access technologies, and can be applied to, inter alia, any type of P2MP (point-to-multipoint) or MP2P (multipoint-to-point) technology, including e.g., Qualcomm Multefire.

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.

Relaying Architecture—

FIGS.3A and3Bare block diagrams illustrating an exemplary embodiment of a fixed wireless configuration with relaying functionality utilizing CBRS frequency bands according to the present disclosure. As shown, the configuration300includes one or more xNB's301a,301b(e.g., 3GPP eNBs or gNBs), several “in-coverage” premises or houses302a,302b,302d, and one “out-of-coverage” house302c. The houses302a-dare each equipped with respective CPE/FWA apparatus303a-d, each of the latter comprising CPE devices3110, Wi-Fi or other routers323, PoE apparatus325(such as in the architecture ofFIG.2Bdiscussed above), one or more antenna elements321, and performance monitoring (e.g., “iPerf” or other performance assessment logic or software) agents317. Each CPE/FWA also includes D2D and packet networking functions as described subsequently herein (not shown inFIGS.3A-3Bfor simplicity).

As discussed in greater detail below, in the exemplary embodiment, the iPerf agent at each house measures key performance indicators (KPIs) such as data throughput (TP), latency and jitter, which are useful in assessing the needs and capabilities of each individual premises. Deficient or sub-SLA performing CPE/FWA (such as that303cassociated with House 3302cin the illustration ofFIGS.3A-3B, by virtue of its location at or near the edge of the serving cell309a, and also being out of range of other cells309b) are accordingly suitable candidates for relaying or supplementation of their data service by other CPE/FWA303a,303b,303d, whether within the same cell309aor not.

It will be appreciated that the use of exemplary performance measurement (e.g., iPerf) processes at the various CPE/FWA devices advantageously allows for a very low-overhead and efficient mechanism by which to judge whether a given CPE/FWA is (i) deficient in terms of meeting one or more criteria relating to e.g., its SLA, and/or (ii) can sustain provision of relay or supplementation services to one or more other CPE/FWA. Specifically, using a performance-based mechanism such as iPerf in the exemplary embodiments obviates more sophisticated analyses of channel conditions such as link budgets/path loss estimates, channel parameter measurement such as RSSI or RSSQ, determination of PER or BER, etc. Rather, the net or actual performance of any given link and its associated channel conditions at any given time are readily determined and used as a basis of determining whether supplementation is required.

For instance, if House 1302ahas an SLA (service level agreement) requirement of 35/4 Mbps (DL/UL), House 2302bhas an SLA of 40/6 Mbps (DL/UL), and House 3302chas an SLA of 25/3 Mbps (DL/UL), each house will require actual performance (data throughput or TP as determined by its iPerf client) that at least meets the foregoing requirements. As such, if say House 3302ccan only achieve 75% of its SLA on the DL, and say 90% of its SLA on the UL, then its performance is deficient or sub-SLA, and House 3 is considered to be “out-of-coverage” and require supplementation. As shown in FIG.3A, House 3 is not completely outside the footprint of the service cell in this example (in a geographic sense), but for purposes of determining its performance level relative to the prevailing SLA, it is deficient and hence categorized as such.

It will be appreciated that while the foregoing “in/out” of coverage model is effectively binary in nature (i.e., deficient in one or more aspects or not), the present disclosure also contemplates more gradient or progressive categorization models or structures, such as where CPE/FWA are ranked or rated against their SLA (e.g., individually for each of DL and UL), and a score given that indicates their proximity to falling below the relevant SLA. For instance, in one such approach, a given CPE/FWA303may be rated as “at risk” for scoring below a prescribed threshold on its DL or UL relative to its SLA. As the margin to the SLA criterion is approached, the risk-level or degree of “precariousness” for the CPE/FWA is increased, and hence this data may be used in certain embodiments to prioritize between CPE/FWA to supplement (e.g., an order in which limited supplementation resources are allocated within the MSO wireless infrastructure). It may also be utilized to structure polling or operation of the performance monitoring algorithms; i.e., more at-risk CPE/FWA may be configured to be more proactive or diligent in monitoring their performance relative to their SLA (e.g., execute iPerf more frequently) so as to more timely detect any transgressions thereof and address them with supplementation.

Such scoring or risk assessment may also be temporally correlated, such as based on data indicative of certain times of the day or certain days or the week or months of the year (or correlation with certain events such as sporting events, sunspots, military exercises, use of weather radar, etc.) when higher interference may be present, such that supplementation is more actively monitored/polled at such times. Note also that SLAs may be constructed to vary temporally and/or on an event-driven basis, and as such the present disclosure contemplates such variations being accounted for in the logic performance monitoring client (e.g., iPerf) such that the SLA is a “moving target” against which the performance is assessed based on a function of time/event.

Moreover, it will be recognized that the UL and DL aspects of performance may be weighted or treated heterogeneously if desired. For instance, “at risk” categorization of UL bandwidth performance may have a different score or proximity index than DL for a given CPE/FWA, since for example DL performance (or lack thereof) may be a more critical determinant of user service quality or experience (e.g., a slow file upload may be much less troublesome to a user than an intermittent or choppy video streaming experience). Note that this type of analysis may also be applied on a per-user/per-premises basis if desired. For example, the present disclosure contemplates scenarios where a given user may describe or specify various aspects of their SLA/performance which are most critical to them, and the scoring/monitoring/polling/supplementation aspects described above algorithmically adjusted based thereon such that the behavior of each CPE/FWA is “tuned” to that particular user or premises. For instance, where a premises uses very little UL capacity, its CPE/FWA behavior may be much more heavily weighted to the DL aspects of its SLA.FIG.3Billustrates the fixed wireless configuration with relaying functionality utilizing CBS frequency band ofFIG.3A, further showing the constituent components of each CPE/FWA303according to one embodiment of the present disclosure. As shown (and subsequently described in greater detail herein), each CPE/FWA303includes a performance monitoring client which enables in effect stand-alone assessment of its own performance relative to its particular SLA (which may not be the same for each of the CPE/houses shown, depending on contractual agreements, physical limitation of the installation, etc.). As such, each CPE/FWA in this embodiment can both assess itself relative to its own SLA, and “advertise itself” (whether actively, such as via request or advertisement messaging) as either needing supplementation from other CPE/FWA local to it, or being able to provide supplementation to other low-TP CPE/FWA devices.

As previously noted, one primary attribute of the disclosure relates to its ability to enhance coverage and data rates. Specifically, to increase the amount of signal power received by the “out-of-network” coverage CPE/FWA (and thereby enhance its data rate), the CPE/FWA may receive the signal from multiple in-coverage or supplementing CPE/FWA. It will be appreciated that depending on the type of antenna elements321used in each CPE/FWA (e.g., directional or omni-directional), even a high-TP CPE/FWA303a,303b(FIG.3A) may not be able to supplement a low-TP CPE/FWA303cif the antenna geometry of the supplementing (and receiving) devices does not support it, such as where highly directional antenna elements are utilized on one or both CPE/FWA and they are aligned to their serving xNB versus the other CPE/FWA.

Hence, in one implementation, the CPE/FWA may also have “smart” antenna capability that can steer the radiation pattern (e.g., lobes) toward the desired target CPE/FWA or serving base station301to maximize e.g., the received SINR. This steering may be accomplished via mechanical means (e.g., actually moving the antenna element or array in azimuth and/or elevation/tilt), and/or electronic steering means such as beamforming (e.g., as may be used in LTE) or so-called “massive MIMO” in 5G NR technology).

In one such implementation, a directional or steerable device such as the BLiNQ SC-300S dynamic device manufactured by BLiNQ Networks Corporation is used, which includes software-enabled targeting of specific areas to enable efficient coverage.

In another such implementation, each CPE/FWA employing multiple directional antenna element technology measures the received signal from its associated base station or another CPE/FWA in communication therewith (e.g., via D2D mechanisms such as ProSe described subsequently herein), and extracts multipath wireless channel information relating to phase and amplitude from the received signal. Such information is used to combine the output of the multiple antennas in such a way as to form a narrow sectorized beam towards the target base station or another CPE/FWA as appropriate, including as input to any mechanical steering mechanism (e.g., to change azimuth of the element/array). Various other similar approaches for optimizing SINR or other signal-strength related parameters will be recognized by those of ordinary skill when given the present disclosure.

Methodology—

Various methods and embodiments thereof for enhancing throughput and coverage area utilizing relaying or supplementation via quasi-licensed (e.g., CBRS GAA or PAL) spectrum according to the present disclosure are now described with respect toFIGS.4-5B.

FIG.4shows one exemplary embodiment of the method used by a CPE/FWA in obtaining supplementation of data bandwidth for itself, according to the present disclosure. As shown, the method400includes first monitoring performance using the performance monitoring process (e.g., iPerf317) operative to execute on the CPE/FWA303c(step402).

Next, per step404, the CPE/FWA detects inadequate performance of its backhaul (e.g., connection to its serving xNB301a). For instance, as described above, the measured or actual data rate over a prescribed period of time (e.g., averaged over n minutes) for UL and/or DL is assessed, and compared to the relevant SLA(s). When the prescribed criterion is not met, the method proceeds to step406, where the CPE/FWA (or a proxy therefore, such as the ProSe server described subsequently herein) identifies one or more other candidate (e.g., geographically local) CPE/FWA which can putatively supplement the bandwidth of the deficient CPE/FWA303c(step406).

At step408, the CPE/FWA303ctransmits directly (or via proxy process) a communication to the identified one or more CPE/FWA303a,303brequesting supplementation. As described elsewhere herein, in one approach, a D2D communication channel is established between the various requesting/responding CPE/FWAs so as to facilitate establishment of the ultimate D2D “relay” channel (e.g., a channel via the primary air interfaces of the device using CBRS SAS-allocated bandwidth).

At step410, after the requests have been received and spectrum is granted, the serving or high-TP CPE/FWA being supplementation of the requesting CPE/FWA303c, and per step412, the performance is again monitored by the recipient (served) CPE/FWA to assure that the necessary SLA goals or criterion are met.

Referring now toFIGS.4A-4B, one implementation of the generalized methodology400ofFIG.4is shown and described, in the exemplary context of a CBRS-based system with SAS, CBSD/xNBs and 4G/5G xNB, and in-coverage and out-of-coverage CPE/FWA devices as previously described.

Per step421of the method420, each CPE/FWA utilizes its indigenous iPerf agent to measure KPIs (key performance indicators) such as TP, latency, and jitter.

Next, per step423, the CPE/FWA each compares their measured data from step421with their respective SLAs, and if their data rates are higher than the SLA (or other relative criterion as discussed elsewhere herein), can act as relays or supplementation devices for other CPE.

Next per step425, any low-TP CPE/FWAs with data rate lower than their specified SLA are identified. For instance, in one approach, each CPE/FWA can monitor itself and when a given CPE/FWA falls below SLA or other criteria, it can either advertise itself to the “network” as being such, or directly contact other CPE/FWA within the network, via D2D side channel or other mechanism.

Next, per step427, the low-TP CPE303c(or their proxy process) identify one or more high-TP CPE, and establish a D2D connection to the high-TP CPEs at step429so as to support negotiation for authentication, supplementation requests, determination of supplementation capability of the serving CPE/FWA303a,303b, spectrum grant communication, etc.).

Next per step431, the iPerf agents on the low-TP CPE/FWA device(s) determine how much resource are needed from the supplementing high-TP CPE. As a brief aside, the exemplary iPerf client used in the various embodiments described herein is a tool for network performance measurement and tuning that can produce standardized performance measurements. iPerf can be configured with client and server functionality, and can create its own data streams to measure the throughput between the two “ends” of the connection in one or both directions. The data streams can be for example Transmission Control Protocol (TCP) or User Datagram Protocol (UDP), and various parameters are user configurable (in the present context, by MSO design or testing personnel, or even dynamically via remote control from a network process). IPerf is typically embodied as open-source software written in C, and runs on various platforms including Linux and Windows. Notwithstanding, the present disclosure contemplates use of other performance monitoring techniques (whether implemented by the DUT such as the CPE/FWA “self-assessing” itself, or from the other end of the connection, such as by a serving BS301).

At step433, the high-TP CPE303a,303bcalculate the amount of resources that can be allocate to the low-TP CPE (e.g., using their own iPerf client processes and respective SLAs). Note that in one embodiment, to avoid repeated request/grant/withdrawal cycles between two CPE/FWAs (i.e., supplementation “dither”), the iPerfs and monitoring algorithms can be configured to smooth (e.g., average) out the various parameters over time, and also anticipate changes in operating conditions or demand which may occur for the serving (or served) CPE/FWA. For instance, if a given serving CPE/FWA303a,303bhistorically is largely inactive between 2:00 AM and 5:00 AM local time, it can be safely presumed in most cases that any excess capacity over and above SLA will be stable and not subject to sudden retraction or withdrawal by the serving CPE/FWA, such as might be caused by a user streaming multiple videos as might occur during normal (waking) hours. Similarly, if a requesting CPE only transiently falls below one or more of its SLA criteria, the algorithms may be configured to ignore such transients, and only allow for supplementation requests that are more pervasive and continuous in nature. Likewise, if the requesting CPE/FWA303cis configured to anticipate that, even though performance is deficient or below requisite levels, that no salient demand will be forthcoming for say several hours (e.g., during the same late-night window as referenced above), it may selectively forestall issuing requests or advertisements for supplementation, since the lack of performance is a logical “don't care” state, and the supplementation would not be used anyway even if provided.

Next per step435, the high-TP CPEs register to the SAS as CBSDs and request spectrum grants. Per step437, the high-TP CPE receives the grant from the SAS, and per step439a data session between the requesting (served) CPE/FWA and the serving CPE/FWA is established using the granted spectrum. In one embodiment, normal 3GPP channel discovery and establishment procedures (including RACH, establishment of RRC Connected State, etc.) are performed as if between the CPE/FWA and a base station.

Next per step441, the low-TP CPE requests data service from the high-TP CPE(s) via normal 3GPP signaling, and data exchange between the various CPE/FWAs (served and serving) occurs to support service flows for the requesting CPE/FWA303cper step443.

Per step445, the data service support starts between the CPE to provide the requested supplementation. The data exchange process between the serving and served CPE is dynamic, and if the resources are not needed anymore, the SAS grant is relinquished by the serving CPE/FWA (e.g., via communication to the SAS) per step447, and D2D connection is terminated.

FIGS.5A-5Billustrate an embodiment of a generalized method of operation used by a serving CPE/FWA in providing data rate supplementation according to the present disclosure.

As shown, the method500includes the serving CPE/FWA receiving a request for data rate supplementation from a requesting or served CPE/FWA as described elsewhere herein (whether via polling/pull, active request “push” by the served CPE/FWA, via a proxy process, or other) per step502.

Per step504, the receiving CPE/FWA evaluates its own backhaul performance relative to its SLA.

Per step506, based on the evaluation of step504, the CPE/FWA identifies an amount of supplementation which it can provide, and compares this amount to the requested or requisite amount associated with the supplementation request (step508). If the available capacity is adequate to support the request (step510), then the serving CPE/FWA303a,303bnotifies the requesting CPE/FWA303cof the available supplementation (e.g., via D2D “side channel” messaging) per step512. At step514, the serving CPE/FWA obtains a spectrum grant via registration with the SAS, and establishes the supplementation channel with the served CPE/FWA303cas previously described (step516). The serving CPE then provides the supplementation of data services to the requesting CPE using the granted spectrum per step518.

It will also be appreciated that while a single served CPE/FWA303cis described in the context of the foregoing discussion, a given serving or supplementing CPE/FWA303a,303bmay in fact service multiple requesting CPE/FWA simultaneously. For example, a given CPE/FWA may receive a request for supplementation from a first CPE/FWA, and provide service to that device, and then subsequently receive a request from another “deficient” CPE/FWA, and assuming that its performance/capability are adequate, supplement that device as well. In one such approach, the two requesting CPE are served via two different spectrum grants (i.e., using two different carriers or bands), and one or more allocated direction antenna elements and corresponding formed beams (the two requesting CPE presumed to be disparate enough in azimuth or elevation such that simultaneous supplementation is possible without unacceptable levels of interference). In another approach, a time-share or TDM based scheme is used on the same carrier or set of sub-bands. Using OFDM-based 3GPP mechanisms, different time/frequency resource blocks can be allocated to each served CPE/FWA as well. Each CPE may also be fitted with two or more separate transceiver chains (front ends) and associated baseband processing such that each served CPE may have its own dedicated air interface with a serving CPE/FWA if desired. Numerous other approaches to simultaneous provision of service to two or more requesting CPE will be recognized by those of ordinary skill when given the present disclosure.

Device to Device (D2D) Communication Mechanisms—

In one exemplary embodiment of the disclosure, communication between the various CPE/FWA devices303within a given network area is provided using 3GPP-based Proximity Services (ProSe). This capability allows for, inter alia, the provision of the following parameters to the CPEs to enable relay/supplementation connectivity among themselves, and assignment of unique IDs to each of the CPE: (i) security parameters; (ii) group membership data and unicast/multicast addresses, (iii) radio resource parameters; and (iv) service request/response messaging.

As a brief aside, 3GPP TS 32.277 V14.0.0 (2016-09), “Technical Specification—3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Proximity-based Services (ProSe) charging (Release 14),” which is incorporated herein by reference, describes the exemplary ProSe functionality utilized in some embodiments of the present disclosure. First introduced in Release 12 of the 3GPP specifications, ProSe (Proximity Services) is a D2D (Device-to-Device) technology that allows 3GPP-compliant devices to detect on other, and to communicate directly as opposed to via the core functions. It uses new functional elements including a “sidelink” air interface for direct connectivity between devices. In comparison to existing D2D and proximity networking technologies, ProSe offers some benefits such as enhanced scalability and management, privacy, security and mobile device battery-efficiency.

FIG.6Ais a block diagram of a prior art non-roaming reference architecture for proximity services (ProSe) according to 3GPP Release 14.

FIG.6Bis a block diagram of a prior art inter-PLMN reference architecture for proximity services (ProSe) according to 3GPP Release 14.

FIG.6Cis a block diagram of a prior art roaming reference architecture for proximity services (ProSe) according to 3GPP Release 14.

As can be seen in each of the above Release 14 architectures, a client-server model is used wherein a ProSe application on a UE communicates logically with a ProSe application server via e.g., a ProSe network function within the PLMN (public land mobile network) associated with the UE. A PC5 inter-UE communication interface is utilized for D2D communication (i.e., UE to UE) as shown, and Uu interfaces are used from the UEs back to the E-UTRAN.

As shown inFIG.7, embodiments of the present disclosure leverage the foregoing ProSe architecture to enable, among other things, CPE/FWA to CPE/FWA communication in support of the relay and supplementation functions. In the architecture700ofFIG.7, the low-TP CPE303creceive/transmit from/to the E-UTRAN (including eNBs301) over the Uu interface. Also, the serving or high-TP CPEs303a,303breceive/transmit data from/to the low-TP CPE303cover the PC5 interface. This data is aggregated at transport layer as subsequently described herein with respect toFIGS.8and8A.

The Evolved Packet Core (EPC)703transfers the aggregated data packet from eNBs to e.g., the Internet715and then to the SAS717(via a DP, not shown). The EPC unit consists of Mobility Management Entity (MMS)711, Packet Data Gateway (P-GW)70, Evolved Packet Data Gateway (E-PDG), Serving Gateway (S-GW)712, Policy and Charging Rules Function (PCFR), and Home Subscriber Server (HSS)707. The ProSe application server705communicates directly with the EPC core703via the PC2 interface (or alternatively may be communicative with the EPC via the Internet715) to provide support of the ProSe “apps” operative on each CPE/FWA within the architecture, including via the illustrated PC1 interface713.

FIG.7Ashows another embodiment of the ProSe architecture730of the present disclosure, wherein 5G NR network entities are utilized (including gNBs301and NG-RAN, 5GC733, PCF739, UDM/HSS737, and AMF711), as well as the ProSe app to Server interface743.

As will be recognized, one major difference between the 5G Core (5GC) compared to the EPC is that 5GC's control plane (CP) functions interact in a Service-Based Architecture (SBA). The Network Repository Function (NRF) provides NF service registration and discovery, enabling NFs (network functions) to identify appropriate services within one another. These SBA principles apply to interfaces between CP functions within 5GC only, so interfaces towards the Radio Access Network (NG-RAN), CPE/FWA or user plane (UP) functions (N1, N2, N3, N4, N6 and N9) are excluded. 5GC also has functional separation of the Access and Mobility Functions (AMF) and Session Management Functions (SMF), and also includes the separation of UP (user plane) and CP (control plane) functions of the gateway, which is an evolution of the gateway CP/UP separation (CUPS) introduced in 3GPP Release 14 for the EPC. Other differences include a separate Authentication Server (AUSF), and several new functions, such as the Network Slice Selection Function (NSSF) and the Network Exposure Function (NEF), each of which can be leveraged by e.g., a network operator such as an MSO/MNO when provisioning services to the various CPE/FWA, including in support of ProSe functions.

It will be appreciated that while the various embodiments of the present disclosure are described in the context of D2D communication provided via the 3GPP ProSe standards and framework, the present disclosure is in no way so limited, and in fact other D2D or “pseudo-D2D” communication modalities (including those which must pass through at least a portion of the MSO/MNO infrastructure supporting the CPE/FWAs) may be used consistent with the disclosure to provide the necessary cross-CPE/FWA identification and communication functionality.

Packet Management—

In that packet streams for a given recipient (e.g., served low-TP) CPE/FWA303cmust at some level be split and carried across each of the serving bearers (other CPE/FWA303a,303b, and the base station301), some mechanism is needed to manage such packet stream splitting and recombination. In one exemplary approach, a transport layer function is used to manage packet allocations across the different bearers. This approach advantageously obviates any PHY or link-layer modifications, and also supports high-throughput so as to maintain QoS and SLA requirements for the target (served) CPE/FWA303c.

FIG.8shows an example of aggregation of multiple links at the application layer of the low-TP CPE/FWA303c. As shown, the Transmission Control Protocol (TCP) packets825a-cfrom the respective high TP-CPEs303a,303band the serving base station (eNB or gNB)301are aggregated in the application layer of the recipient low TP-CPE303cbased on use of an exemplary multiple path “transport layer” protocol such as Multi-path Transmission Control Protocol (MPTCP)823.

As a brief aside, MPTCP allows a Transmission Control Protocol (TCP) connection to use multiple paths to, inter alia, maximize resource usage and increase redundancy. These features enable inverse multiplexing of resources, and hence in theory increases TCP throughput to the aggregate of all available link-level channels (as opposed to a single one as required by non-MPTCP implementations based on standard TCP). Additionally, link-level channels may be added or dropped, such as where a given CPE/FWA begins or ceases supplementation of a served CPE/FWA in the present context, without disrupting the end-to-end TCP connection between e.g., the served CPE/FWA and a remote network server such as a content or web server. Link handover is handled by abstraction in the transport layer, without change to the network or link layers. Accordingly, link handover and instantiation/teardown can be implemented at the endpoints of the TCP session (e.g., the CPE/FWA) without requiring special functionality in the supporting sub-network infrastructure. Multipath TCP can balance a single TCP connection across multiple interfaces to achieve a desired throughput.

Hence, in the illustrated embodiment ofFIG.8, the application layer process829can utilize application-specific transports and endpoints and via MPTCP (including e.g., each of the data connections between the served CPE/FWA and the base station301, as well as the other serving CPE/FWA), support each of these via common transport layer functionality. Aggregation of these multiple links is applied using MPTCP at the backhaul (baseband) of the low-TP or served CPE/FWA303c, in effect allowing the served CPE/FWA to act as a transport layer aggregator of (and congestion control process for) multiple packet streams825, including those intended for the served CPE yet received via the different air interface channels.

FIG.8Ashows an example of splitting the aggregated packets to individual packet streams at the transport layer of the low-TP CPE. For example, in one embodiment, the streams from various CPE/FWA and network base-stations(s) are combined using MPTCP at the low-TP CPE. The reverse is carried out from the CPE towards other CPE/FWA and the serving base-station(s). Any duplication of packets is taken care of by the underlying PDCP (packet data convergence protocol) of LTE (i.e., TS 25.323 and related).

FIG.8Billustrates one exemplary generalized method850of packet management over multiple bearers according to the present disclosure. As shown, in step852, the low-TP CPE/FWA303creceives packets associated with one of its streams or flows (e.g., an application layer process829) from its serving base station (xNB). Per step854, it also receives packets from one or more serving or supplementing CPE/FWA303a,303b, via the air interface channels established with those devices.

At step856, the recipient low-TP CPE/FWA aggregates the packets from all sources at its backhaul transport layer (e.g., using the MPTCP protocol), and applies congestion and flow control per step858so as to optimize the backhaul as a “virtual unified” transport (e.g., via balancing of the individual link-layer constituents associated with the respective bearers).

Inter-Process Protocol—

FIG.9is a ladder diagram illustrating the communication flow for enhancing coverage area and throughput of quasi-licensed wireless service in accordance with the exemplary methods ofFIGS.4-5B.

In the embodiment illustrated inFIG.9, the communication protocol900includes the “in coverage” or serving (high-TP) CPE/FWAs303a,303b(seeFIG.3A) first performing initial attach procedures with the relevant E-UTRAN/EPC entities (including the P-GW packet gateway709) via their respective serving eNBs301(steps1aand1b).

Next, D2D discovery between the low-TP CPE/FWA303cand the CPE/FWA of the other houses303a,303bis performed, and supporting functions such as IP address discovery and device authentication/negotiation are performed, as shown inFIG.9(steps2a-5b). It will be appreciated that this D2D process may be “push” or “pull” from any node to any other, depending on how the protocol is configured (e.g., the low-TP CPE/FWA may periodically monitor itself and instigate the request for supplementation as inFIG.4previously described, or alternatively one of the high-TP CPE/FWA devices may periodically poll other CPE/FWA (including the low-TP CPE/FWA) to cause the latter to evaluate their TP (e.g., versus their relevant SLA) and report back to the polling device.

It will be appreciated that the D2D discovery and connection process of steps2a-5bmay also take several different forms, depending on the particular functionality desired. For instance, in one approach, discovery and connection with all available prospectively supplementing CPE/FWA is established irrespective of whether the low-TP CPE/FWA303cwill utilize them; the various connected CPE/FWA will evaluate their own ability to supplement (as previously described with respect to e.g.,FIGS.4A-5B), and either the requesting CPE/FWA303cor the supplementing CPE/FWA303a,303bwill decide which of the connected population are ultimately utilized.

Alternatively, in another approach, more serialized logic is utilized, such as where the connection and evaluation of each prospective supplementing CPE/FWA is conducted before any further D2D connections to other CPE are established. For instance, if the first “connected” CPE/FWA is capable of providing complete supplementation to the low-T CPE/FWA (e.g., up to its SLA), then no further communication is required with other CPE/FWA. This approach has the advantage of lower processing overhead and simultaneous radiated interference from the participating CPE (e.g., as opposed to a “broadcast” or other such model), yet may also introduce additional latency in reaching full SLA supplementation for the low-TP CPE/FWA.

In yet another approach, the low-TP CPE/FWA303cmay access historical or even predictive/speculative data regarding one or more known CPE/FWA (e.g., captured via prior sessions between the devices, or via a download of such data from one or more of the MSO or MNO core entities), and use this data to make an “educated guess” as to which CPE/FWA is likely to be the optimal choice for supplementation (e.g., which CPE/FWA or grouping thereof has historically provided, or is projected to provide, complete supplementation with the minimum of overhead. For example, if one nearby CPE/FWA has historically always been able to provide complete SLA supplementation to the low-TP CPE/FWA303cby itself, then this is an obvious first choice. As such, the present disclosure contemplates that each CPE/FWA may build its own (or be provided with) a hierarchy or “logic tree” to be applied to the D2D logic of steps2a-5binFIG.9. It will also be appreciated that the foregoing decisions/logic may be handed off to a network entity or process, such as logic within the P-GW709, or even another MNO or MSO entity including e.g., the ProSe server when so equipped.

Per steps6a-6bofFIG.9, the participating (supplementing) CPE/FWA303a,303bthen contact the cognizant spectrum allocation process (e.g., the SAS717for CBRS implementations), such as via an MSO-based or third-party domain proxy (DP)—not shown, to request a spectrum grant to enable bandwidth supplementation to the requesting low-TP CPE/FWA303c. Per CBRS protocol, the SAS registers the devices and returns the respective grant(s) to each requester303a,303b, thereby enabling establishment of wireless connection (e.g., RRC Connected state) via the primary air interface of each CPE/FWA (i.e., within the 3.550-3.70 GHz band using 3GPP LTE or NR protocols).

It is noted that the D2D discovery and connection protocols of steps2a-5bare in one embodiment conducted using a “sidelink” (e.g., as specified in Rel. 12/13), or another alternate channel which may be available for such purposes. In one embodiment, the system (granted) frequency utilized by the extant CPE/FWA (i.e., the high-TP CPE) is used for purposes of the D2D/sidelink communications, although it will be appreciated that other frequencies or bands may be used consistent with the present disclosure. The sidelink frequency can also be indicate in the grant. In one operational scenario, all of the participating CPE/FWA devices are already “in-network” and have established communication and SAS grants through the network, and hence at time of supplementation, a new grant is not needed for the initial “relay” or D2D communications. However, when the supplementing CPE/FWA(s) are required to transmit (akin to a base-station) to support the other (supplemented or low-TP) CPE/FWA, a new grant is requested from the SAS as shown onFIG.9. InFIG.9, the high-TP CPE/FWAs are requesting permission from the SAS for “xNB-like operation” to support the low-TP CPE.

Similarly, an “in-network” or established low-TP would not require a grant, as it already has a grant from the network prior to establishment of the D2D sidelinks with the other CPE/FWA(s).

CBRS FWA Apparatus—

FIG.10illustrates one exemplary embodiment of a CPE/FWA303(e.g., roof-mounted FWA with associated radio head and CPE electronics) configured according to the present disclosure. It will be appreciated that while described in the context of a CBRS-compliant FWA, the device ofFIG.10may be readily adapted to other spectra and/or technologies such as e.g., Multefire, DSA, LSA, or TVWS.

As shown inFIG.10, the CPE/FWA is a Relay Node Manager (RNM)- and ProSe-enabled device which includes, inter alia, a processor subsystem with CPU1042, a memory module1054, one or more radio frequency (RF) network interface front ends1048(e.g., adapted for operation in the 3.55-3.70 GHz band, C-Band, NR-U bands, etc.) and associated antenna elements1055, one or more backend interfaces (e.g., USB, GbE, etc.), a WLAN/BLE module1024with integrated WLAN router and antennae1056, power module1052(which may include the aforementioned PoE injector device), and an RF baseband processing module1056.

In one exemplary embodiment, the processor subsystem1042may include one or more of a digital signal processor (DSP), microprocessor (e.g., RISC core(s) such as ARM core), field-programmable gate array, GPU, or plurality of processing components mounted on one or more substrates (e.g., printed circuit board). The processor subsystem/CPU1042may also comprise an internal cache memory (e.g., L1/L2/L3 cache). The processor subsystem is in communication with a memory subsystem854, the latter including memory which may for example comprise 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 subsystem.

In this and various embodiments, the processor subsystem/CPU1042is configured to execute at least one computer program stored in program memory854(e.g., a non-transitory computer readable storage medium). A plurality of computer programs/firmware are used and are configured to perform various functions such as communication with relevant functional modules within the CPE/FWA303such as the radio head and WLAN/BLE module1024.

Various other functions useful for and typical in “radio head” electronics including baseband management (e.g., transmit and receive functions via the baseband processor1056and associated Tx and Rx chains of the RF front end1048. For example, in one embodiment, the Tx and Rx chains are part of an RF front end used for OFDM-based RF communication with CBSD devices (e.g., xNB301operating as CBRS base stations deployed by the MSO or a third party, so as to provide backhaul).

In the exemplary embodiment, the memory subsystem1054includes a Relay Node Manager (RNM) process or logic module1021configured to process relaying functionality and protocols such as those described according toFIGS.3A-5B. For instance, in one implementation, the RNM1021includes the necessary logic and functionality to (i) determine if the CPE/FWA TP is lower than a prescribed SLA; (ii) access data within e.g., memory1054or the mass storage device relating to known other CPE/FWA303; (iii) if no other CPE/FWA are known a priori to the low-TP CPE/FWA, initiate a search for the same; (iv) Establish a D2D connections to one or more of the other CPE/FWA; (v) request data/bandwidth supplementation from the other device(s); and (vi) act as a supplementation CPE/FWA or relay if the indigenous TP is higher than SLA. Since the physical channel dynamics for a given CPE/FWA may change over time (whether increase or decrease) such as due to new xNB install or extant xNB removal, growth of trees, introduction of other interferers, etc. over time, each CPE/FWA303installed is in the exemplary embodiment configured to enable acting as either a supplemented device (i.e., low-TP device) or a supplementation provider (i.e., high-TP device) at any given time.

As shown, the CPE/FWA303also includes the previously described ProSe logic module1023for D2D communication support, as well as MPTCP stack logic1027to implement e.g., the packet management and related functions as described with respect toFIGS.8A-8C.

Service Provider Network—

FIG.11illustrates one embodiment of a service provider network configuration useful with the relaying functionality and supporting 3GPP/CBRS-based wireless network(s) described herein. It will be appreciated that while described with respect to such network configuration, the methods and apparatus described herein may readily be used with other network types and topologies, whether wired or wireless, managed or unmanaged.

The exemplary service provider network1100is used in the embodiment ofFIG.11to provide backbone and Internet access from the service provider's wireless access nodes (e.g., CBSD/xNBs, Wi-Fi APs, FWA devices or base stations operated or maintained by the MSO), and one or more stand-alone or embedded cable modems (CMs)1133in data communication therewith.

The individual xNBs301are backhauled by the CMs1133to the MSO core via e.g., CMTS or CCAP MHAv2/RPD or other such architecture, and the MSO core1150includes at least some of the EPC/5GC core functions previously described, as well as the ProSe Application Server as shown. Each of the CPE/FWA303are communicative with their respective xNBs301, as well as other CPE/FWA as needed to support the relay functions previously described. Client devices1106such as tablets, smartphones, SmartTVs, etc. at each premises are served by respective WLAN routers323, the latter which are backhauled to the MSO core or backbone via their respective CPE/FWA.

Notably, in the embodiment ofFIG.11, all of the necessary components for support of the relay functionality are owned, maintained and/or operated by the common entity (e.g., cable MSO). The approach ofFIG.11has the advantage of, inter alia, giving the MSO complete control over the entire service provider chain, including control over the xNBs so as to optimize service to its specific customers (versus the non-MSO customer-specific service provided by an MNO), and the ability to construct its architecture to optimize incipient 5G NR functions such as network slicing, gNB DU/CU Option “splits”, etc.

In contrast, in the embodiment ofFIG.12, the architecture1200is divided among two or more entities, such as an MNO and an MSO. As shown, the MSO service domain extends only to the CPE/FWA and served premises and the MSO core functions, while other functions such as 3GPP EPC/E-UTRAN or 5GC and NG-RAN functionality is provided by one or more MNO networks1232operated by MNOs with which the MSO has a service agreement. In this approach, the ProSe Application server is still maintained and operated by the MSO (since the MSO maintains cognizance over the CPE/FWA which must communicate via ProSe), although this is not a requirement, and the present disclosure contemplates embodiments where the ProSe function is maintained by the MNO or even a third party. The approach ofFIG.12has the advantage of, inter alia, avoiding more CAPEX by the MSO, including duplication of infrastructure which may already service the area of interest, including reduced RF interference due to addition of extra (and ostensibly unnecessary) xNBs or other transceivers.

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).