Patent Description:
Data communication services are now ubiquitous throughout user premises (e.g., home, office, and even vehicles). Such data communication services may be provided via a managed or unmanaged network. For instance, a typical home has services provided by one or more network service providers via a managed network such as a cable or satellite network. These services may include content delivery (e.g., linear television, on-demand content, personal or cloud DVR, "start over", etc.), as well as so-called "over the top" third party content. Similarly, Internet and telephony access is also typically provided, and may be bundled with the aforementioned content delivery functions into subscription packages, which are increasingly becoming more user- or premises-specific in their construction and content. Such services are also increasingly becoming more user- or premises-specific in their construction and content. Such services are also increasingly attempting to adopt the paradigm of "anywhere", anytime," so that users (subscribers) can access the desired services (e.g., watch a movie) via a number of different receiving and rendering platforms, such as in different rooms of their house, on their mobile device while traveling, etc..

Network operators deliver data services (e.g., broadband) and video products to customers using a variety of different devices, thereby enabling their users or subscribers to access data/content in a number of different contexts, both fixed (e.g., at their residence) and mobile (such as while traveling or away from home). <FIG> and <FIG> are a functional block diagrams illustrating a typical prior art managed (e.g., cable) content delivery network architecture used to provide such data services to its users and subscribers.

Data/content delivery may be specific to the network operator, such as where video content is ingested by the network operator or its proxy, and delivered to the network users or subscribers as a product or service of the network operator. For instance, a cable multiple systems operator (MSO) may ingest content from multiple different sources (e.g., national networks, content aggregators, etc.), process the ingested content, and deliver it to the MSO subscribers via e.g., a hybrid fiber coax (HFC) cable/fiber network, such as to the subscriber's set-top box or DOCSIS cable modem. Such ingested content is transcoded to the necessary format as required (e.g., MPEG-<NUM> or MPEG-<NUM>/AVC), framed and placed in the appropriate media container format ("packaged"), and transmitted via e.g., statistical multiplex into a multi-program transport stream (MPTS) on <NUM> radio frequency (RF) channels for receipt by the subscribers RF tuner, demultiplexed and decoded, and rendered on the user's rendering device (e.g., digital TV) according to the prescribed coding format.

Within the cable plant, VOD and so-called switched digital video (SDV) may also be used to provide content, and utilize a single-program transport stream (SPTS) delivery modality. cable systems for example, downstream RF channels used for transmission of television programs are <NUM> wide, and occupy a <NUM> spectral slot between <NUM> and <NUM>. Deployments of VOD services have to share this spectrum with already established analog and digital cable television services such as those described above. Within a given cable plant, all homes that are electrically connected to the same cable feed running through a neighborhood will receive the same downstream signal. For the purpose of managing e.g., VOD services, these homes are grouped into logical groups typically called Service Groups. Homes belonging to the same Service Group receive their VOD service on the same set of RF channels.

VOD service is typically offered over a given number (e.g., <NUM>) of RF channels from the available spectrum in cable. Thus, a VOD Service Group consists of homes receiving VOD signals over the same <NUM> RF channels.

In most cable networks, programs are transmitted using MPEG (e.g., MPEG-<NUM>) audio/video compression. Since cable signals are transmitted using Quadrature Amplitude Modulation (QAM) scheme, available payload bitrate for typical modulation rates (QAM-<NUM>) used on HFC systems is roughly <NUM> Mbps. For example, in many VOD deployments, a typical rate of <NUM> Mbps is used to send one video program at resolution and quality equivalent to NTSC broadcast signals. In digital television terminology, this is called Standard Definition (SD) television resolution. Therefore, use of MPEG-<NUM> and QAM modulation enables carriage of <NUM> SD sessions on one RF channel (<NUM> x <NUM> = <NUM> Mbps < <NUM> Mbps). Since a typical Service Group consists of <NUM> RF channels, <NUM> simultaneous SD VOD sessions can be accommodated within a Service Group.

Entertainment-quality transmission of HD (High Definition) signals requires about four times as much bandwidth as SD. For an exemplary MPEG-<NUM> Main Profile - High Level (MP@HL) video compression, each HD program requires around <NUM> Mbps bitrate.

Alternatively, so-called "over-the-top" or OTT delivery may be used for providing services within a network, wherein content from a third party source who may be unaffiliated with the network operator provides content directly to the requesting user or subscriber via the network operator's infrastructure (including the cable architecture described supra), e.g., via an IP-based transport; i.e., the content is packetized and routed for delivery to the requesting user based on the user's network or IP address, such as via the aforementioned high-speed DOCSIS cable modem, according to the well-known Internet Protocol network-layer protocol.

IP unicasts (point to point) or multicasts (point to multiple points) have traditionally been used as the mechanism by which the OTT content is distributed over the network, via the user accessing a prescribed URL and logging in with their credentials to gain access to the content. The IP content is then streamed via the unicast/multicast to the requesting user(s), and received and decoded by a media player application program ("app") on the user's PC, laptop, or other IP-enabled end-user device.

In order to gain operational and economic efficiencies, technology stacks within content delivery networks such as HFC-based cable networks have over time generally migrated towards the "cloud" or network side of the network (e.g., into regionalized data centers), and away from the end user (client) consuming devices. Hence, the client device's content presentation capabilities are dictated increasingly by these cloud-based functions (including network-side caching architecture), along with the on-board storage and processing power of the client device and its associated software stack.

For example, cloud-based EPGs (electronic program guides) are increasingly configured to provide a streamlined user experience, reduced device processing and storage footprint, and a consistent and simple mechanism for software upgrades across multiple different types of HW/SW platforms (e.g., different OEM devices). For instance, HTML <NUM>-based cloud apps are increasingly replacing native apps (i.e., those incorporated into the design of the device at time of manufacture) for implementing such functions. Implementations such as the cloud-based "Spectrum Guide" offered by the Assignee hereof is more labor intensive for the client, due largely to the need for client processes or functions to interface with network-side entities or processes.

In the foregoing example of cloud-delivered EPGs, all objects (from content poster art to the elements of the day/time grid, and most visual video content) is stitched and delivered as a single stream to the client device (e.g., DSTB), as opposed to being indigenously generated by the DSTB. Specifically, the program guide elements (e.g., graphics) are stitched together as a transport stream, while video content that is utilized within a window or other display element of this program guide on the user device comes from a different source, and any advertisements come from yet a third location, akin to the operation of a web browser. This approach can present several challenges in performance, specifically with respect to latency associated with video transitions from one program channel to another, from one type of content to another (such as VOD to DVR), as well as video content to advertising content (e.g., linear addressable content, described above) transitions. Even in the most basic channel tuning functions, such transitions can take several seconds, due to inter alia, the need to repopulate/generate EPG display elements based on the cloud data and service.

As a brief aside, subscribers or users characteristically make programming selection decisions in less than <NUM> second (based on anecdotal evidence of the Assignee hereof). Conversely, a typical user has difficulty perceiving delays less than several milliseconds. Hence, the aforementioned multi-second latency or delay is highly detrimental to user experience, including by failing to keep users engaged with particular content, and with the service provider brand in general.

Other sources of delay in content switching transactions may exist as well. For instance, where the (primary) video content is delivered encoded in one format (e.g., H. <NUM>) and the switched-to content (e.g., addressable advertisement) is encoded in a different format (e.g., MPEG-<NUM>), delays in processing the MPEG-<NUM> content may arise from, inter alia, processing to support the rendering of MPEG-<NUM> content (e.g., identification and utilization of an MPEG-<NUM> compatible decoder or player on the client device). Conversely, the motion compensation and other features associated with H. <NUM> and other advanced codecs (discussed in greater detail below) can require significant processing overhead, thereby adding to the computational burden on the DSTB (or other client device). Likewise, open-GOP (group of pictures) processing versus closed-GOP processing can consume additional time and resources.

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 <NUM> of the Commission's Rules). Currently only frequency bands between <NUM> and <NUM> 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 "<NUM>" (third generation) and "<NUM>" (fourth generation) wireless communications as shown in Table <NUM> 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 <NUM>) in footnotes <NUM>, <NUM>, and <NUM> of the Radio Regulations. In the United States, uses of the ISM bands are governed by Part <NUM> of the Federal Communications Commission (FCC) rules, while Part <NUM> contains the rules for unlicensed communication devices, even those that share ISM frequencies. Table <NUM> 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 <NUM> and <NUM> bands, as well as wireless LANs (e.g., Wi-Fi) and cordless phones in the <NUM>, <NUM>, and <NUM> bands.

Additionally, the <NUM> band has been allocated for use by, e.g., WLAN equipment, as shown in Table <NUM>:.

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 node or "hotspot," a physical location at which the user may obtain access by connecting to modems, routers, APs, etc. that are within wireless range.

One such technology that enables a user to engage in wireless communication (e.g., via services provided through the cable network operator) is Wi-Fi® (IEEE Std. <NUM>), which has become a ubiquitously accepted standard for wireless networking in consumer electronics. Wi-Fi allows client devices to gain convenient high-speed access to networks (e.g., wireless local area networks (WLANs)) via one or more access points.

Commercially, Wi-Fi is able to provide services to a group of users within a venue or premises such as within a trusted home or business environment, or outside, e.g., cafes, hotels, business centers, restaurants, and other public areas. A typical Wi-Fi network setup may include the user's client device in wireless communication with an AP (and/or a modem connected to the AP) that are in communication with the backend, where the client device must be within a certain range that allows the client device to detect the signal from the AP and conduct communication with the AP.

Another wireless technology in widespread use is Long-Term Evolution standard (also colloquially referred to as "LTE," "<NUM>," "LTE Advanced," among others). An LTE network is powered by an Evolved Packet Core ("EPC"), an Internet Protocol (IP)-based network architecture and eNodeB - Evolved NodeB or E-UTRAN node which part of the Radio Access Network (RAN), capable of providing high-speed wireless data communication services to many wireless-enabled devices of users with a wide coverage area.

Currently, most consumer devices include multi-RAT capability; e.g.; the capability to access multiple different RATs, whether simultaneously, or in a "fail over" manner (such as via a wireless connection manager process running on the device). For example, a smartphone may be enabled for LTE data access, but when unavailable, utilize one or more Wi-Fi technologies (e.g., <NUM>/n/ac) for data communications.

The capabilities of different RATs (such as LTE and Wi-Fi) can be very different, including regarding establishment of wireless service to a given client device. For example, there is a disparity between the signal strength threshold for initializing a connection via Wi-Fi vs. LTE (including those technologies configured to operate in unlicensed bands such as LTE-U and LTE-LAA). As a brief aside, LTE-U enables data communication via LTE in an unlicensed spectrum (e.g., <NUM>) to provide additional radio spectrum for data transmission (e.g., to compensate for overflow traffic). LTE-LAA uses carrier aggregation to combine LTE in unlicensed spectrum (e.g., <NUM>) with the licensed band. Typical levels of signal strength required for LTE-U or LTE-LAA service are approximately -<NUM> to -<NUM> dBm. In comparison, Wi-Fi can be detected by a client device based on a signal strength of approximately -<NUM> to -<NUM> dBm, i.e., a higher (i.e., less sensitive) detection threshold.

Increasing numbers of users (whether users of wireless interfaces of the aforementioned standards, or others) invariably lead to "crowding" of the spectrum, including interference. Interference may also exist from non-user sources such as solar radiation, electrical equipment, military uses, etc. In effect, a given amount of spectrum has physical limitations on the amount of bandwidth it can provide, and as more users are added in parallel, each user potentially experiences more interference and degradation of performance.

Moreover, technologies such as Wi-Fi have limited range (due in part to the unlicensed spectral power mask imposed in those bands), and may suffer from spatial propagation variations (especially inside structures such as buildings) and deployment density issues. Wi-Fi has become so ubiquitous that, especially in high-density scenarios such as hospitality units (e.g., hotels), enterprises, crowded venues, and the like, the contention issues may be unmanageable, even with a plethora of Wi-Fi APs installed to compensate. Yet further, there is generally no coordination between such APs, each in effect contending for bandwidth on its backhaul with others.

Additionally, lack of integration with other services provided by e.g., a managed network operator, typically exists with unlicensed technology such as Wi-Fi. Wi-Fi typically acts as a "data pipe" opaquely carried by the network operator/service provider.

NG-RAN or "NextGen RAN (Radio Area Network)" is part of the 3GPP "<NUM>" next generation radio system. 3GPP is currently specifying Release <NUM> 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 <NUM> 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 <NUM>/<NUM> 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 <NUM> NG-RAN leverages technology and functions of extant LTE/LTE-A technologies (colloquially referred to as <NUM> or <NUM>), 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 <NUM> V14. entitled "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release <NUM>)" dated September <NUM>.

As a brief aside, and referring to <FIG>, the CU <NUM> (also known as gNB-CU) is a logical node within the NR architecture <NUM> that communicates with the NG Core <NUM>, and includes gNB functions such as transfer of user data, session management, mobility control, RAN sharing, and positioning; however, other functions are allocated exclusively to the DU(s) <NUM> (also known as gNB-DUs) per various "split" options described subsequently herein in greater detail. The CU <NUM> communicates user data and controls the operation of the DU(s) <NUM>, via corresponding front-haul (Fs) user plane and control plane interfaces <NUM>, <NUM>.

Accordingly, to implement the Fs interfaces <NUM>, <NUM>, the (standardized) F1 interface is employed. It provides a mechanism for interconnecting a gNB-CU <NUM> and a gNB-DU <NUM> of a gNB <NUM> within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. The F1 Application Protocol (F1AP) supports the functions of F1 interface by signaling procedures defined in 3GPP TS <NUM>. F1AP consists of so-called "elementary procedures" (EPs). An EP is a unit of interaction between gNB-CU and gNB-DU. These EPs are defined separately and are intended to be used to build up complete messaging sequences in a flexible manner. Generally, unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone procedures, which can be active in parallel.

Within such an architecture <NUM>, a gNB-DU <NUM> (or ngeNB-DU) is under the control of a single gNB-CU <NUM>. When a gNB-DU is initiated (including power-up), it executes the F1 SETUP procedure (which is generally modeled after the above-referenced S1 SETUP procedures of LTE) to inform the controlling gNB-CU of, inter alia, any number of parameters such as e.g., the number of cells (together with the identity of each particular cell) in the F <NUM> SETUP REQUEST message.

Even with the great advances in wireless data rate, robustness and coverage afforded by extant <NUM>/<NUM> (e.g. LTE/LTE-A) and WLAN (and other unlicensed) systems, and corresponding IoT solutions outlined above, significant disabilities still exist.

One such problem relates to the scenario where a broadband user migrates from an indoor use case to an outdoor use case. For instance, a user utilizing their premises Wi-Fi AP experiences a very limited range - perhaps <NUM> feet or so depending on premises construction and other factors - before they experience degradation and ultimately loss of signal. Moreover, there is no session continuity between shorter range technologies such as Wi-Fi and longer range broadband cellular systems such as LTE (i.e., a user must terminate their Wi-Fi session and continue using a new LTE (3GPP) session). Such "unlicensed to licensed" (and vice versa) spectral use also presents unique challenges, in that unlicensed systems are often not configured to integrate with MNO systems (e.g., WLAN APs are not configured to comply with 3GPP eUTRAN or other such standards as far as interoperability).

Moreover, the foregoing solutions are generally not integrated or logically unified, and may also require subscription to and use of multiple service provider technologies and infrastructure. For example, unlicensed WLAN APs within a user premises may be backhauled by a cable or fiber or satellite MSO, while cellular service is provided by a wholly separate MNO using licensed cellular infrastructure.

In cases where MNO or other radio access node or base stations are backhauled by another provider (e.g., a wireless network built around HFC/DOCSIS as backhaul between the radio and wireless core network elements), several disadvantages are encountered, including (i) separate CAPEX (capital expenditure) and OPEX (operating expenditure) "silos" for maintaining the two different networks; i.e., wired and wireless; and (ii) lower data throughput efficiency and higher latency due to the additional overhead of encapsulating wireless data packets through e.g., the DOCSIS (backhaul) protocols. In the context of the aforementioned ultra-low latency requirements of <NUM> (i.e., <NUM> or less round-trip between endpoint nodes), such infrastructure-induced latency can result in failing to meet these requirements, making this architecture potentially unsuitable for <NUM> applications.

Moreover, to achieve certain capacity targets (e.g., <NUM> Gbps) over such infrastructure, increased use of optical fiber is needed in certain parts of the infrastructure. Under current HFC network design, services are provided to users via a coaxial cable "drop" to their premises, and groups of such premises are served by common tap-off points or nodes within the larger architecture (see discussion of cable systems supra). Individual premises "tap off' the cabling or other infrastructure from each node and, depending on their geographic placement and other considerations, may require utilization of a number of different amplification units in order to maintain sufficient signal strength out to the most distant (topology-wise) premises in the system. For instance, a common description of how many amplifier stages are used between a source node and premises is "N+i", where i = the number of amplifier stages between the source node and the premises. For instance, N=<NUM> refers to the situation where no amplifiers are used, and N+<NUM> refers to use of three (<NUM>) amplifiers. In some extant cable/HFC systems in operation, values of i may be as high as seven (<NUM>); i.e., N+<NUM>, such as for service to rural areas.

As can be expected, use of such amplifier stages introduces some limitations on the data rates or bandwidth (both downstream; i.e., toward the client premises, and upstream, i.e., from the client premises) achievable by such systems. In effect, such systems are limited in maximum bandwidth/data rate, due in part to the design of the amplifiers; for example, they are typically designed to provide services primarily in the downstream direction (with much lower upstream bandwidth via so-called "OOB" or out-of band RF channels providing highly limited upstream communication. Cable modem or DOCSIS-compliant systems utilize DOCSIS QAMs (RF channels) for enhanced upstream bandwidth capability such as for Internet services, but even such technologies are significantly limited in capability, and moreover have limited flexibility in the allocation of downstream versus upstream bandwidth, especially dynamically.

Accordingly, as alluded to above, replacement of such amplifier stages (and supporting coaxial cabling) with higher bandwidth, low-loss mediums such as optical fiber is necessary to achieve very high target data rates (sometimes referred to as going "fiber deep"), including all the way back to an N+<NUM> configuration throughout the entire network to achieve the highest data rates. However, replacement of literally tens of thousands of amplifiers and thousands of miles of cabling with optical fiber or the like is prohibitively expensive, and can take years.

Additionally, the following art is acknowledged: (i) Crawford, et al. O Patent Application Publication No. <CIT>; hereinafter "Crawford"), which discloses transmitting signaling via wireline and wireless at approximately <NUM> in the downstream (i.e., premises) direction from the access point; and (ii) Malach, et al. (<CIT>; hereinafter "Malach"), which discloses a system and method for automating a deployment site served by a distributed antenna system (DAS).

Accordingly, improved apparatus and methods are needed to, inter alia, enable optimized delivery of ultra-high data rate services (both wired and wireless) and which leverage extant network infrastructure. Ideally, such improved apparatus and methods would also support seamless geographic and cross-platform mobility for users while providing such services, and support incipient applications and technologies such as IoT.

All figures © Copyright <NUM>-<NUM> Charter Communications Operating, LLC.

Reference is now made to the drawings wherein like numerals refer to like parts throughout.

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 "central unit" or "CU" refers without limitation to a centralized logical node within a wireless network infrastructure. For example, a CU might be embodied as a <NUM>/NR gNB Central Unit (gNB-CU), which is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs, and which terminates the F1 interface connected with one or more DUs (e.g., gNB-DUs) defined below.

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 "distributed unit" or "DU" refers without limitation to a distributed logical node within a wireless network infrastructure. For example, a DU might be embodied as a <NUM>/NR gNB Distributed Unit (gNB-DU), which is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU (referenced above). One gNB-DU supports one or multiple cells, yet a given cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU.

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 <NUM>, <NUM>, <NUM>, <NUM> and <NUM>.

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, or provides other services such as high-speed data delivery and backhaul.

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 "IoT device" refers without limitation to electronic devices having one or more primary functions and being configured to provide and/or receive data via one or more communication protocols. Examples of IoT devices include security or monitoring systems, appliances, consumer electronics, vehicles, infrastructure (e.g., traffic signaling systems), and medical devices, as well as receivers, hubs, proxy devices, or gateways used in association therewith.

As used herein, the term "IoT network" refers without limitation to any logical, physical, or topological connection or aggregation of two or more IoT devices (or one IoT device and one or more non-IoT devices). Examples of IoT networks include networks of one or more IoT devices arranged in a peer-to-peer (P2P), star, ring, tree, mesh, master-slave, and coordinator-device topology.

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), <NUM> LTE, WiMAX, VoLTE (Voice over LTE), and other wireless data standards.

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/<NUM> 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., <NUM>), or other network service provider having infrastructure required to deliver services including without limitation voice and data over those mediums. The term "MNO" as used herein is further intended to include MVNOs, MNVAs, and MVNEs.

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 technologies or networking protocols (e.g., SONET, DOCSIS, IEEE Std. <NUM>, ATM, X. <NUM>, Frame Relay, 3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP, RTP/RTCP, H. <NUM>, etc.).

As used herein the terms "<NUM>" and "New Radio (NR)" refer without limitation to apparatus, methods or systems compliant with 3GPP Release <NUM>, 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, <NUM>-QAM, <NUM>-QAM, <NUM>-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 "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. <NUM> or related standards including <NUM> a/b/g/n/s/v/ac/ax, <NUM>-<NUM>/<NUM> or <NUM>-<NUM>, as well as Wi-Fi Direct (including inter alia, the "Wi-Fi Peer-to-Peer (P2P) Specification").

The present invention aims to provide improved architectures and methods for providing enhanced ultra-high data rate services which, inter alia, leverage existing managed network (e.g., cable network) infrastructure. The architectures may enable a highly uniform user-experience regardless of the environment (e.g., indoor/outdoor/mobility), in which content is consumed and eliminates the need to distinguish between fixed-broadband and mobile-broadband, or the foregoing and IoT.

A Hybrid Fiber Coax (HFC) plant infrastructure and extant 3GPP LTE and <NUM> NR protocols may be used as bases for provision of standards-compliant ultra-low latency and high data rate services (e.g., <NUM> NR services) via a common service provider. In one variant, an expanded frequency band (approximately <NUM> in total bandwidth) is used over the coaxial portions of the HFC infrastructure, which is allocated to two or more sub-bands. Wideband amplifier apparatus are used to support delivery of the sub-bands to extant HFC network nodes (e.g., hubs or distribution points) within the network, and ultimately to premises devices. An OFDM and TDD-based access and modulation scheme is used to allow for maximal efficiency and flexibility in allocating bandwidth to UL and DL transmissions over the HFC infrastructure.

SG-enabled premises devices (e.g., CPE) are used within the foregoing architecture to provide the services to users at a given premises and thereabouts, using extant 3GPP protocols. In another variant, local area (e.g., "pole mounted") radio access nodes are used in concert with the SG-enabled CPE to provide supplemental RF coverage, including during mobility scenarios, as well as supplemental capacity to the CPE for indoor use cases (i.e., when the CPE requires additional bandwidth over what the HFC coaxial cable drop to the premises alone can provide), thereby enabling data rates on the order of <NUM> Gbps and above.

Advantageously, the foregoing enhanced high data rate, high mobility, low latency services are provided without (i) the need for any module or customized application software or protocols of the user device (e.g., mobile UE), and (ii) the need to expend CAPEX/OPEX relating to laying new fiber and/or maintaining two (e.g., MSO and MNO) network infrastructures in parallel.

Moreover, latency within the disclosed infrastructure is reduced by, inter alia, obviating encapsulation and other network/transport protocols normally necessitated through use of e.g., DOCSIS bearers and equipment (i.e., DOCSIS modems and CMTS apparatus within the MSO core.

Edge-heavy solutions (e.g., Fog models) are also supported via the use of the <NUM> protocols as well as high bandwidth and enhanced connectivity out at the edge of the MSO infrastructure.

Using 3GPP protocols through HFC also enables broadband service benefits stemming from the rich feature set, vendor diversity and operational reliability that 3GPP has already developed for the over <NUM> billion global subscribers of 3GPP <NUM> LTE.

The improved architecture also advantageously facilitates so-called "network slicing," including providing differentiated services (and QoS/QoE) for various target applications and use cases.

Apparatus and methods in accordance with the present invention are now described in detail. While these are described in the context of the previously mentioned wireless access nodes (e.g., gNBs) associated with or supported at least in part by a managed network of a service provider (e.g., MSO), other types of radio access technologies ("RATs"), other types of networks and architectures that are configured to deliver digital data (e.g., text, images, games, software applications, video and/or audio) may be used consistent with the present disclosure. 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 service area, venue, or other type of premises), the present disclosure may be readily adapted to other types of environments including, e.g., commercial/retail, or enterprise domain (e.g., businesses), or even governmental uses. Yet other applications are possible.

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.

Referring now to <FIG>, one embodiment of an enhanced service provider network architecture <NUM> is shown and described in detail.

As illustrated, the architecture <NUM> includes one or more hubs <NUM> within the MSO network (e.g., whether near edge portions of the network, or further towards the core), including a <NUM> NR core (5GC) <NUM>. The hub <NUM> includes a WLAN controller process <NUM>, and services one or more "enhanced" nodes <NUM>, which each include a gNB CUe <NUM> and an network radio node <NUM>, described in greater detail below. The nodes <NUM> utilize HFC infrastructure, including N-way taps <NUM> to deliver RF waveforms to the various served premises (including the enhanced CPE or CPEe) <NUM>.

Also serviced by the node <NUM> are one or more non-CUe enabled nodes <NUM> including <NUM>/<NUM> enabled network radio nodes <NUM>, which service additional premises as shown.

In the illustrated embodiment, the nodes <NUM>, <NUM> are backhauled by optical fiber, although this is merely illustrative, as other types of backhauls including e.g., high-bandwidth wireless may be used consistent with the present disclosure.

Similarly, one or more pole-mounted radio nodes 506a are backhauled to the MSO network via optical fiber (or other medium); these nodes 506a provide, inter alia, supplemental capacity/coverage for both indoor and outdoor (and mobility) scenarios as described in greater detail below.

A Wi-Fi router device <NUM> is also present in the served premises to provide WLAN coverage, in conjunction with the controller <NUM> at the hub <NUM>. The centralized Wi-Fi controller <NUM> is also utilized in the exemplary architecture <NUM> for tight-interworking and better mobility between the 3GPP and Wi-Fi access technologies where the Wi-Fi router is either integrated with the consumer premises equipment (e.g., enhanced CPE or CPEe) or connected to it. Then, mobility between the 3GPP and Wi-Fi channels for any user can be triggered for the best data throughput, such as based on (i) estimation of the RF quality of the Wi-Fi channel toward the user, and/or (ii) the degree of congestion of the Wi-Fi router, and not just the Wi-Fi received signal strength indicators (RSSI) measured at the mobile device, the latter which may not be representative of the service quality that can be obtained by the user.

In the exemplary configuration, the controller (e.g.,Wi-Fi Controller <NUM>) is configured to choose the best (optimal) wireless connection available to it based on performance (as opposed to coverage/coverage area alone). Typically today, a preferred method of access is predetermined based on its received signal strength and/or as a preferred means (e.g. Wi-Fi could be defined as the preferred method of access to off-load the mobile wireless network). However, this method suffers from the drawback of blind 'stickiness' to a technology, without considering the end user experience. Given that in exemplary embodiments of the architecture described herein, both Wi-Fi and licensed/unlicensed 3GPP access technologies are both controlled by the network operator (e.g.MSO), there is no need to prefer an access method, such as to purely to offload a user's traffic. The decision to offload or steer a user to a given access technology, can be based upon other criteria, such as e.g., a select set of Key Performance Indicators (KPIs) such as the user perceived latency, throughput, packet loss, jitter and bit/packet/frame error rates as measured in real-time at any given layer (e.g., L1, L2 or L3) by the network. For instance, in one implementation, once a target KPI threshold is triggered, the switching of the user can be triggered by either the AMF function (for 3GPP) or Wi-Fi Controller. This switching may then trigger a session establishment at the alternate access medium to transfer the user to that technology. This helps optimize QoE for connected users, since the controller will always be attempting to holistically optimize the connection versus merely making decisions based on coverage or signal strength alone.

This architecture also obviates the problematic transition between premises Wi-Fi and cellular, thereby enabling content consumption while the user is mobile, with no reduction in QoE or interruptions due to e.g., new session establishment in the cellular network. This is accomplished by, inter alia, communication between the Wi-Fi controller <NUM> and the CUe <NUM>, such that the CUe can remain cognizant of both Wi-Fi and 3GPP channel status, performance and availability. Advantageously, in exemplary embodiments, the foregoing enhanced mobility is provided without the need for any module or customized application software or protocols of the user device (e.g., mobile UE), since all communication sessions (whether between the CPEe and the UE, or the supplemental radio access node and the UE) are both (i) controlled by a common system, and (ii) utilize extant 3GPP (e.g., <NUM>/<NUM>/<NUM>) protocols and architectural elements. In one variant a GPRS Tunneling Protocol (GTP) is utilized for maintenance of session continuity between the heterogeneous RAN technologies (e.g., 3GPP and IEEE Std. In another variant, a PMIP (Proxy Mobile IP) based approach is utilized for session maintenance/handover. In yet a further variant, techniques described in 3GPP TS <NUM> v13. <NUM>, "3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release <NUM>)" (aka "I-WLAN") based approach is utilized for these purposes. As will be appreciated by those of ordinary skill given the present disclosure, combinations of the foregoing mechanisms may be utilized as well, depending on the particular application (including the two heterogeneous technologies that are party to the session maintenance/handoff).

The MSO network architecture <NUM> of <FIG> is particularly useful for the delivery of packetized content (e.g., encoded digital content carried within a packet or frame structure or protocol) consistent with the various aspects of the present disclosure. In addition to on-demand and broadcast content (e.g., live video programming), the system of <FIG> may deliver Internet data and OTT (over-the-top) services to the end users (including those of the DUe's <NUM>) via the Internet protocol (IP) and TCP (i.e., over the <NUM> radio bearer), although other protocols and transport mechanisms of the type well known in the digital communication art may be substituted.

The architecture <NUM> of <FIG> further provides a consistent and seamless user experience with IPTV over both wireline and wireless interfaces. Additionally, in the IP paradigm, dynamic switching between unicast delivery and multicast/broadcast is used based on e.g., local demand. For instance, where a single user (device) is requesting content, an IP unicast can be utilized. For multiple devices (i.e., with multiple different IP addresses, such as e.g., different premises), multicast can be utilized. This approach provides for efficient and responsive switching of delivery and obviates other more equipment/CAPEX-intensive approaches.

Moreover, the architecture can be used for both broadband data delivery as well as "content" (e.g., movie channels) simultaneously, and obviates much of the prior separate infrastructure for "in band" and DOCSIS (and OOB) transport. Specifically, with DOCSIS (even FDX DOCSIS), bandwidth is often allocated for video QAMs, and a "split" is hard-coded for downstream and upstream data traffic. This hard split is typically implemented across all network elements - even amplifiers. In contrast, under the exemplary configuration of the architecture disclosed herein, effectively all traffic traversing the architecture is IP-based, and hence in many cases there is no need to allocate QAMs and frequency splits for different program or data streams. This "all-IP" approach enables flexible use of the available bandwidth on the transmission medium for all applications dynamically, based on for instance the demand of each such application at any given period or point in time.

In certain embodiments, the service provider network <NUM> also advantageously permits the aggregation and/or analysis of subscriber- or account-specific data (including inter alia, correlation of particular CUe or DUe or E-UTRAN eNB/femtocell 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., gNB ID, Global gNB Identifier, NCGI, MAC address or the like) can be cross-correlated to MSO subscriber data maintained at e.g., the network head end(s) <NUM> so as to permit or at least facilitate, among other things, (i) user/device authentication to the MSO network; (ii) correlation of aspects of the area, premises or venue where service is provided to particular subscriber capabilities, demographics, or equipment locations, such as for delivery of location-specific or targeted content or advertising or <NUM> "slicing" configuration or delivery; and (iii) determination of subscription level, and hence subscriber privileges and access to certain services as applicable.

Moreover, device profiles for particular devices (e.g., 3GPP <NUM> NR and WLAN-enabled UE, or the CPEe <NUM> and any associated antenna <NUM>, etc.) can be maintained by the MSO, such that the MSO (or its automated proxy processes) can model the device for wireless or other capabilities. For instance, one (non-supplemented) CPEe <NUM> may be modeled as having bandwidth capability of X Gbps, while another premises' supplemented CPEe may be modeled as having bandwidth capability of X+Y Gbps, and hence the latter may be eligible for services or "slices" that are not available to the former.

As a brief aside, the <NUM> technology defines a number of network functions (NFs), which include the following:.

Within the <NUM> NR architecture, the control plane (CP) and user plane (UP) functionality is divided within the core network or NGC (Next Generation Core). For instance, the <NUM> UPF discussed above supports UP data processing, while other nodes support CP functions. This divided approach advantageously allows for, inter alia, independent scaling of CP and UP functions. Additionally, network slices can be tailored to support different services, such as for instance those described herein with respect to session handover between e.g., WLAN and 3GPP NR, and supplemental links to the CPEe.

In addition to the NFs described above, a number of different identifiers are used in the NG-RAN architecture, including those of UE's and for other network entities, and may be assigned to various entities described herein. Specifically:.

Hence, depending on what data is useful to the MSO or its customers, various portions of the foregoing can be associated and stored to particular gNB "clients" or their components being backhauled by the MSO network.

In the context of <FIG>, the DUe's described herein may assume any number of forms and functions relative to the enhanced CPE (CPEe) <NUM> and the radio node 506a (e.g., pole mounted external device). Recognizing that generally speaking, "DU" and "CU" refer to 3GPP standardized features and functions, these features and functions can, so long as supported in the architecture <NUM> of <FIG>, be implemented in any myriad number of ways and/or locations. Moreover, enhancements and/or extensions to these components (herein referred to as CUe and DUe) and their functions provided by the present disclosure may likewise be distributed at various nodes and locations throughout the architecture <NUM>, the illustrated locations and dispositions being merely exemplary.

Accordingly, referring now to <FIG>, various embodiments of the distributed (CUe/DUe) gNB architecture are described. As shown in <FIG>, a first architecture <NUM> includes a gNB <NUM> having an enhanced CU (CUe) <NUM> and a plurality of enhanced DUs (DUe) <NUM>. As described in greater detail subsequently herein, these enhanced entities are enabled to permit inter-process signaling and high data rate, low latency services, whether autonomously or under control of another logical entity (such as the NG Core <NUM> with which the gNB communicates, or components thereof), as well as unified mobility and IoT services.

The individual DUe's <NUM> in <FIG> communicate data and messaging with the CUe <NUM> via interposed physical communication interfaces <NUM> and logical interfaces <NUM>. As previously described, such interfaces may include a user plane and control plane, and be embodied in prescribed protocols such as F1AP. Operation of each DUe and CUe are described in greater detail subsequently herein; however, it will be noted that in this embodiment, one CUe <NUM> is associated with one or more DUe's <NUM>, yet a given DUe is only associated with a single CUe. Likewise, the single CUe <NUM> is communicative with a single NG Core <NUM>, such as that operated by an MSO. Each NG Core <NUM> may have multiple gNBs <NUM> associated therewith (e.g., of the type <NUM> shown in <FIG>).

In the architecture <NUM> of <FIG>, two or more gNBs 522a-n are communicative with one another via e.g., an Xn interface <NUM>, and accordingly can conduct at least CUe to CUe data transfer and communication. Separate NG Cores 523a-n are used for control and user plane (and other) functions of the network.

In the architecture <NUM> of <FIG>, two or more gNBs 522a-n are communicative with one another via e.g., the Xn interface <NUM>, and accordingly can conduct at least CUe to CUe data transfer and communication. Moreover, the separate NG Cores 523a-n are logically "cross-connected" to the gNBs <NUM> of one or more other NG Cores, such that one core can utilize/control the infrastructure of another, and vice versa. This may be in "daisy chain" fashion (i.e., one gNB is communicative one other NG Core other than its own, and that NG Core is communicate with yet one additional gNB <NUM> other than its own, and so forth), or the gNBs <NUM> and NG Cores <NUM> may form a "mesh" topology where multiple Cores <NUM> are in communication with multiple gNBs or multiple different entities (e.g., service providers). Yet other topologies will be recognized by those of ordinary skill given the present disclosure. This cross-connection approach advantageously allows for, inter alia, sharing of infrastructure between two MSOs, or between MNO and MSO, which is especially useful in e.g., dense deployment environments which may not be able to support multiple sets of RAN infrastructure, such as for different service providers.

It will also be appreciated that while described primarily with respect to a unitary gNB-CUe entity or device <NUM>, <NUM> as shown in <FIG>, the present disclosure is in no way limited to such architectures. For example, the techniques described herein may be implemented as part of a distributed or dis-aggregated or distributed CUe entity (e.g., one wherein the user plane and control plane functions of the CUe are dis-aggregated or distributed across two or more entities such as a CUe-C (control) and CUe-U (user)), and/or other functional divisions are employed.

It is also noted that heterogeneous architectures of eNBs or femtocells (i.e., E-UTRAN LTE/LTE-A Node B's or base stations) and gNBs may be utilized consistent with the architectures of <FIG>. For instance, a given DUe may (in addition to supporting node operations as discussed in greater detail with respect to <FIG> below), act (i) solely as a DUe (i.e., <NUM> NR PHY node) and operate outside of an E-UTRAN macrocell, or (ii) be physically co-located with an eNB or femtocell and provide NR coverage within a portion of the eNB macrocell coverage area, or (iii) be physically non-colocated with the eNB or femtocell, but still provide NR coverage within the macrocell coverage area.

In accordance with the <NUM> NR model, the DUe(s) <NUM> comprise logical nodes that each may include varying subsets of the gNB functions, depending on the functional split option. DUe operation is controlled by the CUe <NUM> (and ultimately for some functions by the NG Core <NUM>). Split options between the DUe and CUe in the present disclosure may include for example:.

Under Option <NUM> (RRC/PDCP split), the RRC (radio resource control) is in the CUe <NUM> while PDCP (packet data convergence protocol), RLC (radio link control), MAC, physical layer (PHY) and RF are kept in the DUe, thereby maintaining the entire user plane in the distributed unit.

Under Option <NUM> (PDCP/RLC split), there are two possible variants: (i) RRC, PDCP maintained in the CUe, while RLC, MAC, physical layer and RF are in the DU(s) <NUM>; and (ii) RRC, PDCP in the CUe (with split user plane and control plane stacks), and RLC, MAC, physical layer and RF in the DUe's <NUM>.

Under Option <NUM> (Intra RLC Split), two splits are possible: (i) split based on ARQ; and (ii) split based on TX RLC and RX RLC.

Under Option <NUM> (RLC-MAC split), RRC, PDCP, and RLC are maintained in the CUe <NUM>, while MAC, physical layer, and RF are maintained in the DUe's.

Under Option <NUM> (Intra-MAC split), RF, physical layer and lower part of the MAC layer (Low-MAC) are in the DUe's <NUM>, while the higher part of the MAC layer (High-MAC), RLC and PDCP are in the CUe <NUM>.

Under Option <NUM> (MAC-PHY split), the MAC and upper layers are in the CUe, while the PHY layer and RF are in the DUe's <NUM>. The interface between the CUe and DUe's carries data, configuration, and scheduling-related information (e.g. Modulation and Coding Scheme or MCS, layer mapping, beamforming and antenna configuration, radio and resource block allocation, etc.) as well as measurements.

Under Option <NUM> (Intra-PHY split), different sub-options for UL (uplink) and DL downlink) may occur independently. For example, in the UL, FFT (Fast Fourier Transform) and CP removal may reside in the DUe's <NUM>, while remaining functions reside in the CUe <NUM>. In the DL, iFFT and CP addition may reside in the DUe <NUM>, while the remainder of the PHY resides in the CUe <NUM>.

Finally, under Option <NUM> (PHY-RF split), the RF and the PHY layer may be separated to, inter alia, permit the centralization of processes at all protocol layer levels, resulting in a high degree of coordination of the RAN. This allows optimized support of functions such as CoMP, MIMO, load balancing, and mobility.

Generally speaking, the foregoing split options are intended to enable flexible hardware implementations which allow scalable cost-effective solutions, as well as coordination for e.g., performance features, load management, and real-time performance optimization. Moreover configurable functional splits enable dynamic adaptation to various use cases and operational scenarios. Factors considered in determining how/when to implement such options can include: (i) QoS requirements for offered services (e.g. low latency to support <NUM> RAN requirements, high throughput); (ii) support of requirements for user density and load demand per given geographical area (which may affect RAN coordination); (iii) availability of transport and backhaul networks with different performance levels; (iv) application type (e.g. real-time or non-real time); (v) feature requirements at the Radio Network level (e.g. Carrier Aggregation).

It is also noted that the "DU" functionality referenced in the various split options above can itself be split across the DUe and its downstream components, such as the RF stages of the node <NUM> (see <FIG> and <FIG>) and/or the CPEe <NUM>. As such, the present disclosure contemplates embodiments where some of the functionality typically found within the DUe may be distributed to the node/CPEe.

It will further be recognized that user-plane data/traffic may also be routed and delivered apart from the CUe. In one implementation (described above), the CUe hosts both the RRC (control-plane) and PDCP (user-plane); however, as but one alternate embodiment, a so-called " dis-aggregated" CUe may be utilized, wherein a CUe-CP entity (i.e., CUe - control plane) hosts only the RRC related functions, and a CUe-UP (CUe - user plane) which is configured to host only PDCP/SDAP (user-plane) functions. The CUe-CP and CUe-UP entities can, in one variant, interface data and inter-process communications via an E1 data interface, although other approaches for communication may be used.

It will also be appreciated that the CUe-CP and CUe-UP may be controlled and/or operated by different entities, such as where one service provider or network operator maintains cognizance/control over the CUe-UP, and another over the CUe-CP, and the operations of the two coordinated according to one or more prescribed operational or service policies or rules.

Referring again to <FIG>, the exemplary embodiment of the DUe <NUM> is a strand-mounted or buried DUe (along with the downstream radio chain(s), the latter which may include one or more partial or complete RRH's (remote radio heads) which include at least portions of the PHY functionality of the node (e.g., analog front end, DAC/ADCs, etc.). As can be appreciated, the location and configuration of each DUe/node may be altered to suit operational requirements such as population density, available electrical power service (e.g., in rural areas), presence of other closely located or co-located radio equipment, geographic features, etc..

As discussed with respect to <FIG> below, the nodes <NUM> in the embodiment of <FIG> include multiple OFDM-based transmitter-receiver chains of <NUM> nominal bandwidth, although this configuration is merely exemplary. In operation, the node generates waveforms that are transmitted in the allocated band (e.g., up to approximately <NUM>), but it will be appreciated that if desired, the OFDM signals may in effect be operated in parallel with signals carried in the below-<NUM> band, such as for normal cable system operations.

As shown in <FIG>, in one implementation, each node (and hence DUe) is in communication with its serving CUe via an F1 interface, and may be either co-located or not co-located with the CUe. For example, a node/DUe may be positioned within the MSO HFC infrastructure proximate a distribution node within the extant HFC topology, such as before the N-way tap point <NUM>, such that a plurality of premises (e.g., the shown residential customers) can be served by the node/DUe via the aforementioned OFDM waveforms and extant HFC plant. In certain embodiments, each node/DUe <NUM>, <NUM> is located closer to the edge of the network, so as to service one or more venues or residences (e.g., a building, room, or plaza for commercial, corporate, academic purposes, and/or any other space suitable for wireless access). For instance, in the context of <FIG>, a node might even comprise a CPEe or external access node (each discussed elsewhere herein). Each radio node 506a is configured to provide wireless network coverage within its coverage or connectivity range for its RAT (e.g., <NUM> and/or <NUM> NR). For example, a venue may have a wireless NR modem (radio node) installed within the entrance thereof for prospective customers to connect to, including those in the parking lot via inter alia, their NR or LTE-enabled vehicles or personal devices of operators thereof.

Notably, different classes of DUe/node <NUM>, <NUM> may be utilized. For instance, a putative "Class A" LTE eNB may transmit up X dbm, while a "Class-B" LTE eNBs can transmit up to Y dbm (Y>X), so the average area can vary widely. In practical terms, a Class-A device may have a working range on the order of hundreds of feet, while a Class 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. Similarly, different types of NR-enabled nodes/DUe <NUM>, <NUM> can be used depending on these factors, whether alone or with other wireless PHYs such as WLAN, etc..

<FIG> and <FIG> illustrate exemplary downstream (DS) and upstream (US) data throughputs or rates as a function of distance within the HFC cable plant of <FIG>. As illustrated, a total (DS and US combined) bandwidth on the order of <NUM> Gbps is achievable (based on computerized simulation conducted by the Assignee hereof), at Node+<NUM> at <NUM> ft (<NUM>), and at Node+<NUM> at <NUM> ft (<NUM>). One exemplary split of the aforementioned <NUM> Gbps is asymmetric; e.g., <NUM> Gbps DL/<NUM> Gbps UL, although this may be dynamically varied using e.g., TDD variation as described elsewhere herein.

Notably, the portions of the extant HFC architecture described above (see e.g., <FIG> and <FIG>) utilized by the architecture <NUM> of <FIG> are not inherently limited by their medium and architecture (i.e., optical fiber transport ring, with coaxial cable toward the edges); coaxial cable can operate at frequencies significantly higher than the sub-<NUM> typically used in cable systems, but at a price of significantly increased attenuation. As is known, the formula for theoretical calculation of attenuation (A) in a typical coaxial cable includes the attenuation due to conductors plus attenuation due to the dielectric medium: <MAT> where:.

Rt  = Total line resistance ohms per <NUM> ft. Rt <MAT>  (for single copper line)
p  = Power factor of dielectric
F  = Frequency in megahertz (MHz).

As such, attenuation increases with increasing frequency, and hence there are practical restraints on the upper frequency limit of the operating band. However, these restraints are not prohibitive in ranges up to for example <NUM>, where with suitable cable and amplifier manufacturing and design, such coaxial cables can suitably carry RF signals without undue attenuation. Notably, a doubling of the roughly <NUM>-wide typical cable RF band (i.e., to <NUM> width) is very possible without suffering undue attenuation at the higher frequencies.

It will also be appreciated that the attenuation described above is a function of, inter alia, coaxial conductor length, and hence higher levels of "per-MHz" attenuation may be acceptable for shorter runs of cable. Stated differently, nodes serviced by shorter runs of cable may be able to better utilize the higher-end portions of the RF spectrum (e.g., on the high end of the aforementioned exemplary <NUM> band) as compared to those more distant, the latter requiring greater or disproportionate amplification. As such, the present disclosure contemplates use of selective mapping of frequency spectrum usage as a function of total cable medium run length or similar.

Another factor of transmission medium performance is the velocity factor (VF), also known as wave propagation speed or velocity of propagation (VoP), defined as the ratio of the speed at which a wavefront (of an electromagnetic or radio frequency signal, a light pulse in an optical fiber or a change of the electrical voltage on a copper wire) propagates over the transmission medium, to the speed of light (c, approximately 3E08 m/s) in a vacuum. For optical signals, the velocity factor is the reciprocal of the refractive index. The speed of radio frequency signals in a vacuum is the speed of light, and so the velocity factor of a radio wave in a vacuum is <NUM>, or <NUM>%. In electrical cables, the velocity factor mainly depends on the material used for insulating the current-carrying conductor(s). Velocity factor is an important characteristic of communication media such as coaxial, CAT-<NUM>/<NUM> cables, and optical fiber. Data cable and fiber typically has a VF between roughly <NUM> and <NUM> (<NUM>% to <NUM>% of the speed of light in a vacuum).

Achievable round-trip latencies in LTE (UL/DL) are on the order of <NUM> (for "fast" UL access, which eliminates need for scheduling requests and individual scheduling grants, thereby minimizing latency, and shorter TTI, per Release <NUM>), while those for <NUM> NR are one the order of <NUM> or less, depending on transmission time interval frequency (e.g., <NUM>).

Notably, a significant portion of <NUM>/<NUM> transport latency relates to network core and transport (i.e., non-edge) portions of the supporting infrastructure.

Hence, assuming a nominal <NUM> VF and a one (<NUM>) ms roundtrip latency requirement, putative service distances on the order of <NUM> are possible, assuming no other processing or transport latency: <MAT>.

<FIG> and <FIG> illustrate exemplary configurations of a network radio frequency node apparatus <NUM> according to the present disclosure. As referenced above, these nodes <NUM> can take any number of form factors, including (i) co-located with other MSO equipment, such as in a physically secured space of the MSO, (ii) "strand" or pole mounted, (iii) surface mounted, and (iv) buried, so as to inter alia, facilitate most efficient integration with the extant HFC (and optical) infrastructure, as well as other <NUM>/<NUM> components such as the CUe <NUM>.

As shown, in <FIG>, the exemplary node <NUM> in one embodiment generally includes an optical interface <NUM> to the HFC network DWDM system (see <FIG>), as well as a "Southbound" RF interface <NUM> to the HFC distribution network (i.e., coax). The optical interface <NUM> communicates with an SFP connector cage <NUM> for receiving the DWDM signals via the interposed optical fiber. A <NUM> NR DUe <NUM> is also included to provide <NUM> DU functionality as previously described, based on the selected option split. The MIMO/radio unit (RU) stages <NUM> operate at baseband, prior to upconversion of the transmitted waveforms by the IF (intermediate frequency) stages <NUM> as shown. As discussed below, multiple parallel stages are used in the exemplary embodiment to capitalize on the multiple parallel data streams afforded by the MIMO technology within the 3GPP technology. A tilt stage <NUM> is also utilized prior to the diplexer stage <NUM> and impedance matching stage <NUM>. Specifically, in one implementation, this "tilt" stage is used to compensate for non-linearity across different frequencies carried by the medium (e.g., coaxial cable). For instance, higher frequencies may have a higher loss per unit distance when travelling on the medium as compared to lower frequencies travelling the same distance on the same medium. When a high bandwidth signal (e.g. <NUM>-<NUM>) is transmitted on a coax line, its loss across the entire frequency bandwidth will not be linear, and may include shape artifacts such as a slope (or "tilt"), and/or bends or "knees" in the attenuation curve (e.g., akin to a low-pass filter). Such non-linear losses may be compensated for to achieve optimal performance on the medium, by the use of one or more tilt compensation apparatus <NUM> on the RF stage of the node device.

A synchronization signal generator <NUM> is also used in some embodiments as discussed in greater detail below with respect to <FIG>.

In the exemplary implementation of <FIG>, both <NUM> and <NUM> gNB DUe <NUM>, <NUM> are also included to support the RF chains for <NUM> and <NUM> communication respectively. As described in greater detail below, the <NUM> portion of the spectrum is divided into two bands (upper and lower), while the <NUM> portion is divided into upper and lower bands within a different frequency range. In the exemplary implementation, OFDM modulation is applied to generate a plurality of carriers in the time domain. See, e.g., co-owned and co-pending <CIT> and entitled "Digital domain content processing and distribution apparatus and methods," and <CIT> also entitled "Digital domain content processing and distribution apparatus and methods," for inter alia, exemplary reprogrammable OFDM-based spectrum generation apparatus useful with various embodiments of the node <NUM> described herein.

In the exemplary embodiment, the <NUM> and LTE OFDM carriers produced by the node <NUM> utilize <NUM> of the available HFC bearer bandwidth, and this bandwidth is partitioned into two or more sub-bands depending on e.g., operational conditions, ratio of "N+<NUM>" subscribers served versus "N+i" subscribers served, and other parameters. In one variant, each node utilizes RF power from its upstream nodes to derive electrical power, and further propagate the RF signal (whether at the same of different frequency) to downstream nodes and devices including the wideband amplifiers.

While the present embodiments are described primarily in the context of an OFDM-based PHY (e.g., one using IFFT and FFT processes with multiple carriers in the time domain) along with TDD (time division duplex) temporal multiplexing, it will be appreciated that other PHY/multiple access schemes may be utilized consistent with the various aspects of the present disclosure, including for example and without limitation FDD (frequency division duplexing), direct sequence or other spread spectrum, and FDMA (e.g., SC-FDMA or NB FDMA).

As a brief aside, to achieve high throughput using a single receiver chipset in the consumer premises equipment (CPEe) <NUM> and 3GPP <NUM> NR waveforms over a single coaxial feeder, such as the coaxial cable that MSOs bring to their subscriber's premises or the single coaxial cable that is installed for lower-cost single input single output (SISO) distributed antenna systems (DAS), the total carrier bandwidth that can be aggregated by the chipset is limited to a value, e.g. <NUM>, which is insufficient for reaching high throughputs such as <NUM> Gbit/s using one data stream alone given the spectral efficiencies supported by the 3GPP <NUM> NR standard.

Since the 3GPP <NUM> NR standard supports the transmission of multiple independent parallel data streams as part of a multiple input multiple output (MIMO) channel for the same RF bandwidth to leverage the spatial diversity that wireless channels afford when multiple antenna elements are used, the very first generation of 3GPP <NUM> chipsets will support such parallel MIMO data streams. However, attempts to transmit these parallel streams over a single cable would generally be counterproductive, as all the streams would occupy the same RF bandwidth and would interfere with each other for lack of spatial diversity between them.

Accordingly, the various embodiments disclosed herein (<FIG> and <FIG>) leverage the parallel MIMO data streams supported by 3GPP <NUM> NR, which are shifted in frequency in a transceiver node before being injected into the single coaxial feeder so that frequency diversity (instead of spatial diversity; spatial diversity may be utilized at the CPEe and/or supplemental pole-mounted radio access node if desired) is leveraged to achieve the maximum total carrier bandwidth that 3GPP <NUM> NR chipsets will support with parallel data streams.

Also, since higher frequencies attenuate much more over the coaxial transmission media than lower frequencies, in one variant the Intermediate Frequencies (IF) are transmitted over the media, and block-conversion to RF carrier frequency is employed subsequently in the consumer premises equipment (CPEe) <NUM> for 3GPP band-compliant interoperability with the 3GPP <NUM> NR chipset in the CPEe. In this fashion, attenuation that would otherwise be experienced by conversion earlier in the topology is advantageously avoided.

The IF carriers injected by the transceiver node into the coaxial feeder <NUM> can be received by multiple CPEe <NUM> that share the feeder as a common bus using directional couplers and power dividers or taps. Point-to-Multipoint (PtMP) downstream transmissions from the node <NUM> to the CPEe <NUM> can be achieved by, for instance, scheduling payload for different CPEe on different 3GPP <NUM> NR physical resource blocks (PRB) which are separated in frequency.

In the exemplary embodiment, the vast majority of bandwidth in the coaxial cable bearer is used in Time Division Duplex (TDD) fashion to switch between downstream (DS) and upstream (US) <NUM> NR communications. Upstream communications from the multiple CPEe <NUM> to the transceiver node can also/alternatively occur simultaneously over separate PRBs (frequency separation).

In one variant (see <FIG>), a minor portion of the lower spectrum (since lower frequencies attenuate less on the cable) is allocated to a 3GPP <NUM> LTE MIMO carrier with up to two parallel streams of <NUM> bandwidth for a total of <NUM>. This is performed since 3GPP Release <NUM> only supports <NUM> NR in Non-Standalone (NSA) mode, whereby it must operate in tandem with a <NUM> LTE carrier. Just as with the parallel <NUM> streams, the two parallel LTE MIMO streams are to be offset in frequency so as to not interfere with each other and are configured in the exemplary embodiment to operate in TDD mode.

As an aside, <NUM> NR supports adaptive TDD duty cycles, whereby the proportion of time allocated for downstream and upstream transmissions can be adapted to the net demand for traffic from the total set of transmitting network elements, viz. the node and all the CPEe <NUM> sharing the coaxial bus with the node. <NUM> LTE does not support such adaptive duty cycles. To prevent receiver blocking in the likely scenario that the <NUM> and <NUM> duty cycles differ, high-rejection filter combiners <NUM> are used in all active network elements, viz. transceiver nodes, inline amplifiers and CPEe <NUM> for the <NUM> and <NUM> carriers to not interfere with each other or cause receiver blocking. In the exemplary diplexer of <FIG>, both <NUM> and <NUM> are addressed via a high-rejection filter to allow for different duty cycles.

In one variant, another minor portion of the lower spectrum on the coaxial cable employs one-way communication in the downstream for the transmission of two digital synchronization channels, one for <NUM> and one for <NUM>, which are I-Q multiplexed onto one QPSK analog synchronization channel within the aforementioned "minor portion" from the signal generator <NUM> of the transceiver node <NUM> to the multiple inline amplifiers and CPEe <NUM> that may be sharing the coaxial bus. These synchronization channels aid coherent reception of the PRBs, and in one variant command the network elements to switch between downstream and upstream communication modes according to the TDD duty cycle set by the transceiver node <NUM>. In the exemplary configuration, two digital synchronization channels are required since the <NUM> and <NUM> streams may have different upstream-downstream ratios or duty-cycles. Since lower frequencies attenuate less on the cable, the synchronization channel is in one implementation transmitted over a lower portion of the spectrum on the cable so that it reaches every downstream network element and CPEe. In one variant, an analog signal is modulated with two bits, where one bit switches according to the duty cycle for the <NUM> signal, and the other bit switches according to the duty cycle of the <NUM> signal, although other approaches may be utilized.

The connectivity between the transceiver node <NUM> and the northbound network element is achieved with a fiber optic link <NUM> to the MSO DWDM plant. To minimize the number of fiber channels required to feed the transceiver node <NUM>, and to restrict it to a pair of fiber strands, in one embodiment the 3GPP <NUM> NR F1 interface (described supra) is realized over the fiber pair to leverage the low overhead of the F1 interface. The 3GPP <NUM> NR Distribution Unit (DUe) functionality is incorporated into the transceiver node <NUM> as previously described, since the F1 interface is defined between the Central Unit (CU/CUe) and DU/DUe where, in the illustrated embodiment, the CUe and DUe together constitute a 3GPP <NUM> NR base station or gNB (see <FIG>).

An Ethernet switch <NUM> is also provided at the optical interface in the embodiment of <FIG> to divide the backhaul into the <NUM> and <NUM> data paths (e.g., the received upstream <NUM> and <NUM> signals are respectively routed differently based on the switch <NUM>).

The exemplary node <NUM> also includes a power converter <NUM> to adapt for internal use of quasi-square wave low voltage power supply technology over HFC used by DOCSIS network elements as of the date of this disclosure. The node <NUM> in one variant is further configured to pass the quasi-square wave low voltage power received on the input port <NUM> through to the HFC output port <NUM> to other active network elements such as e.g., amplifiers, which may be installed downstream of the node on the HFC infrastructure.

It is noted that as compared to some extant solutions, the illustrated embodiment of <FIG> and <FIG> uses HFC versus twisted pair to feed the CPEe <NUM>; HFC advantageously provides lower loss and wider bandwidths than twisted pair, which is exploited to provide <NUM> throughputs to farther distances, and to leverage the large existing base of installed coaxial cable. Moreover, the foregoing architecture in one implementation is configured to serve multiple CPEe <NUM> using directional couplers and power dividers or taps to attach to a common coaxial bus which connects to a single interface at the transceiver node. The aforementioned Ethernet services (necessary to service an external Wi-Fi access-point and an integrated Wi-Fi router) are further added in other implementations to provide expanded capability, in contrast to the existing solutions.

<FIG> illustrates an exemplary configuration of a CPEe apparatus <NUM> according to the present disclosure. As shown, the CPEe <NUM> generally an RF input interface <NUM> to the HFC distribution network (i.e., coax drop at the premises). A transmitter/receiver architecture generally symmetrical to the transmitter/receiver of the node <NUM> discussed previously is used; i.e., impedance matching circuitry, diplexer, synchronization circuit, tilt, etc. are used as part of the CPEe RF front end. Block converters <NUM> are used to convert to and from the coaxial cable domain bands (here, <NUM>-<NUM> and <NUM>-<NUM>) to the premises domain, discussed in greater detail below.

The exemplary CPEe <NUM> also includes a <NUM> UE process <NUM> to implement 3GPP functionality of the UE within the CPEe, and 3GPP (e.g., <NUM>/LTE) repeater module <NUM> which includes one or more antennae elements <NUM> for indoor/premises coverage within the user RF band(s). As such, the CPEe <NUM> shown can in effect function as a base station for user devices within the premises operating within the user band(s).

A 10GbE WLAN port <NUM> is also included, which interfaces between the UE module <NUM> and the (optional) WLAN router <NUM> with internal 10GbE switch <NUM>) to support data interchange with premises WLAN infrastructure such as a Wi-Fi AP.

Also shown in the configuration of <FIG> are several external ports <NUM>, <NUM> for external antenna <NUM> connection (e.g., roof-top antenna element(s) used for provision of the supplemental data link as previously described with respect to <FIG>), wireless high-bandwidth backhaul, or other functions.

In the exemplary implementation of <FIG>, both <NUM> and <NUM> gNB block converters <NUM>, <NUM> are included to support the RF chains for <NUM> and <NUM> communication respectively (i.e., for conversion of the IF-band signals received to the relevant RF frequencies of the <NUM>/<NUM> interfaces and modems within the CPEe, such as in the <NUM> band. The block converters also enable upstream communication with the distribution node <NUM> via the relevant IF bands via the coaxial input <NUM> as previously described.

Notably, the CPEe <NUM> applies block-conversion between the IF and RF carrier frequency for the <NUM> and <NUM> carrier separately since they may be on different frequency bands. The CPEe includes in one implementation a <NUM> NR and <NUM> LTE-capable user equipment (UE) chipset <NUM>. The two technologies are supported in this embodiment, since the first release of 3GPP <NUM> NR requires <NUM> and <NUM> to operate in tandem as part of the non-standalone (NSA) configuration.

It is noted that in the exemplary configuration of <FIG> (showing the lower frequencies in <NUM> combined with <NUM>), a filter combiner is used (in contrast to the more generalized approach of <FIG>).

It is also noted that the specific implementation of <FIG> utilizes "tilt" compensation as previously described on only one of the RF-IF block converters <NUM>. This is due to the fact that the need for such compensation arises, in certain cases such as coaxial cable operated in the frequency band noted) disproportionately at the higher frequencies (i.e., up to <NUM> in this embodiment). It will be appreciated however that depending on the particular application, different compensation configurations may be used consistent with the present disclosure. For example, in one variant, the upper-band block converters <NUM> may be allocated against more granular frequency bands, and hence tilt/compensation applied only in narrow regions of the utilized frequency band (e.g., on one or two of four %G RF-IF block converters). Similarly, different types of tilt/compensation may be applied to each block converter (or a subset thereof) in heterogeneous fashion. Various different combinations of the foregoing will also be appreciated by those of ordinary skill given the present disclosure.

Block conversion to the RF frequency makes the signals 3GPP band-compliant and interoperable with the UE chipset in the CPEe <NUM>. The RF carriers are also then amenable for amplification through the included repeater <NUM> for <NUM> and <NUM> which can radiate the RF carriers, typically indoors, through detachable external antennas <NUM> connected to the CPEe. Mobile devices such as smartphones, tablets with cellular modems and IoT devices can then serve off of the radiated signal for <NUM> and <NUM> service (see discussion of <FIG> and <FIG> below).

The UE chipset <NUM> and the repeater <NUM> receive separate digital I/Q synchronization signals, one for <NUM> and one for <NUM>, for switching between the downstream and upstream modes of the respective TDD carriers, since they are likely to have different downstream-to-upstream ratios or duty cycle. These two digital synchronization signals are received from an I-Q modulated analog QPSK signal received from lower-end spectrum on the coaxial cable that feeds the CPEe <NUM> via the port <NUM>.

As noted, in the exemplary implementation, OFDM modulation is applied to generate a plurality of carriers in the time domain at the distribution node <NUM>; accordingly, demodulation (via inter alia, FFT) is used in the CPEe to demodulate the IF signals. See, e.g., co-owned and co-pending <CIT> and entitled "Digital domain content processing and distribution apparatus and methods," and <CIT> also entitled "Digital domain content processing and distribution apparatus and methods," for inter alia, exemplary reprogrammable OFDM-based receiver/demodulation apparatus useful with various embodiments of the CPEe <NUM> described herein.

Similar to the embodiment of <FIG>, a <NUM> Gbe Ethernet port is also provided to support operation of the WLAN router <NUM> in the device of <FIG>, including for LAN use within the served premises.

Further, to boost the broadband capacity beyond the capacity available through the primary coaxial cable link and to add a redundant connection for higher reliability (which could be important for small businesses, enterprises, educational institutions, etc.), two additional RF interfaces on the CPEe of <FIG> are included for connecting the CPEe to a <NUM>-port external antenna <NUM> which is installed outdoors, e.g., on the roof of the small business, multi-dwelling unit (MDU) or multi-story enterprise (see <FIG>). This external antenna can be used to receive supplemental signals from outdoor radios installed in the vicinity of the consumer premises. It will be appreciated that the outdoor radios may have a primary purpose of providing coverage for outdoor mobility, but signals from them can also/alternatively be used in a fixed-wireless manner to supplement the capacity from the primary coaxial link and to add redundancy, as described elsewhere herein.

In a further embodiment of the architecture <NUM>, a supplemental or complementary data link <NUM> is utilized to provide additional data capacity (and redundancy to the primary link in the event of an equipment or other failure), as shown in <FIG>. In this configuration, data rates on the order of <NUM> Gbps can be achieved based on computer modeling by the Assignee hereof; e.g., <NUM> Gbps DS and <NUM> Gbps US. The supplemental link in one variant includes a <NUM> NR wireless interface between a pole-mounted or other external radio access node 506a, and the premises transceiver (which in one embodiment includes the CPEe <NUM> with added antenna capability <NUM>. As used in the present context, the terms "pole-mounted" and "external" refer without limitation to any mounting placement or location which can establish a connection or data connectivity with e.g., the supplemental antenna <NUM> (e.g., roof-top or outdoor antenna) of the CPEe. Such mounting may be outdoor or within a large structure (e.g., a sports stadium, large building complex, and may be only temporary or semi-permanent in some implementations.

<FIG> illustrates an exemplary embodiment of a network architecture <NUM> according to the present disclosure, including use of a supplemental link <NUM> in support of "seamless" mobility of a mobile user device.

Advantageously, as shown in <FIG>, the use of common waveforms and protocols over HFC and wireless in exemplary embodiments of the architecture <NUM> allow the use of common network elements such as centralized authentication, authorization, and accounting (AAA) functions, packet gateway and mobility controller (MME) and a common base station for indoor and outdoor areas within a service area, provided the base station is split into a central unit (CUe) and distribution unit (DUe) as described elsewhere herein. It is expected that such a split base station architecture can be ported back to 3GPP <NUM>/<NUM> LTE/A as well.

As illustrated in <FIG>, the commonality of network elements advantageously enables seamless mobility experience between indoor and outdoor spaces of the served premises, in part because macro network-grade network elements with high signaling capacity and data throughput capacity control both spaces. Mobility between these spaces by devices such as phones and IoT modems trigger the least amount of signaling toward "northbound" network elements because, in many cases, mobility is constrained between distribution units (DUe <NUM>) connected to a common Central Unit (CUe <NUM>) as illustrated by the dashed lines in <FIG>, and generally in <FIG>.

Moreover, as previously described, data throughput performance-triggered mobility between 3GPP and Wi-Fi is provided using a centralized Wi-Fi controller connected to a 3GPP mobility controller which services both indoor and outdoor spaces and with Wi-Fi access points cooperating with the Wi-Fi controller <NUM>.

In another embodiment, one or more external (exterior) mobility node devices are utilized to provide outdoor mobility to users/subscribers, including in-vehicle use scenarios. As shown in <FIG>, the "combined" cell coverage is large due to the unified common architecture of the system; no MSO-to-MNO (or vice versa) handovers are required while the vehicle remains in the combined cell coverage area served by the MSO, whether under WLAN APs or the <NUM>/<NUM> external access nodes (which in one embodiment, may include the pole-mounted devices 506a shown in <FIG>, and/or other devices such as those co-located at cellular base station sites). Specifically, by virtue of the common operator (e.g., MSO) and infrastructure, multiple mobility access nodes can be combined to form a single cell for both higher throughput (e.g., at the cell edge) and greater coverage, thereby further reducing handovers.

In one variant, the mobility access nodes are ruggedized versions of the CPEe <NUM>, having generally comparable capabilities. For instance, in one implementation, the external access nodes include both a backhaul (fiber or HFC) to the MSO network, as well as a supplemental link antenna such that the access node can communicate with the pole-mounted devices 506a for additional capacity as needed.

In another implementation, the mobility access nodes use the pole-mounted devices as their backhaul (alone).

WLAN nodes may also be backhauled through the mobility access nodes, including with provision of QoS.

It will also be appreciated that the common MSO core and RAN architecture shown allows for the MSO to selectively supplement coverage using a pole-mounted or other configuration DUe. For example, where a new home or neighborhood is built, the MSO can simply add one or more such DUe devices at locations determined to provide the desired level of coverage; this is in contrast to MNO-based cellular coverage, wherein installation of a new base station (i) can't be directly controlled by the MSO or integrated with other MSO services, (ii) is much more labor and capital intensive.

Yet other combinations and modifications will be appreciated by those of ordinary skill given the present disclosure.

In another aspect of the disclosure, an architecture for providing high data rate, low latency and high mobility unified coverage to e.g., large indoor spaces such as office buildings, enterprises, universities, etc. is disclosed. As shown in <FIG>, one implementation of this architecture utilizes the foregoing hub <NUM> and CUe node <NUM> (including access node <NUM> and CUe <NUM>, as shown in <FIG>) to supply one or more CPEe <NUM> within the enterprise, etc. via HFC infrastructure. The CPEe are then connected to e.g., an indoor (or indoor/outdoor) DAS <NUM> which provides coverage within the structure as shown. The CPEe <NUM> may also utilize the supplemental antenna capability previously described to supplement bandwidth provided to the structure/enterprise as well as indoor/outdoor mobility, such as via local pole-mounted access node with <NUM>//<NUM> capability.

Referring now to <FIG>, methods of operating the network infrastructure of, e.g., <FIG> herein are shown and described.

<FIG> is a logical flow diagram illustrating one embodiment of a generalized method <NUM> of utilizing an existing network (e.g., HFC) for high-bandwidth data communication. As shown, the method includes first identifying content (e.g., digitally rendered media or other data, etc.) to be transmitted to the recipient device or node (e.g., a requesting CPEe <NUM> or UE in communication therewith) per step <NUM>.

Next, per step <NUM>, the transmission node <NUM> generates waveforms "containing" the identified content data. As described below, in one embodiment, this includes generation of OFDM waveforms and scheduling of time-frequency resources to carry the content data (e.g., PRBs).

Per step <NUM>, the waveforms are transmitted via the network infrastructure (e.g., coaxial cable and/or DWDM optical medium) to one or more recipient nodes. It will be appreciated that such transmission may include relay or transmission via one or more intermediary nodes, including for instance one or more N-way taps (<FIG>), optical nodes, repeaters, etc.).

Per step <NUM>, the transmitted waveforms are received at the recipient node (e.g., CPEe <NUM> in one instance).

The waveforms are then upconverted in frequency (e.g., to the specified user frequency band per step <NUM>, and transmitted per step <NUM> via the local (e.g., premises RAN or distribution medium) for use by, e.g., consuming or requesting UE.

<FIG> is a logical flow diagram illustrating one particular implementation of content processing and transmission methods <NUM> according to the generalized method of <FIG>. Specifically, as shown, the method <NUM> includes first performing a serial-to-parallel conversion of the content data per step <NUM>. Next, the parallelized data is mapped to its resources (step <NUM>), and an IFFT or other such transformation operation performed to convert the frequency-domain signals to the time domain (step <NUM>). The transformed (time domain) data is then re-serialized (step <NUM>) and converted to the analog domain (step <NUM>) for transmission over e.g., the RF interface such as a coaxial cable plant. In the exemplary embodiment, an upper band on the plant (e.g., <NUM>-<NUM>) is used, although it will be appreciated that other frequency bands (and in fact multiple different frequency bands in various portions of the spectrum) may be used for this purpose.

<FIG> is a logical flow diagram illustrating one particular implementation of content reception and digital processing methods <NUM> by a CPEe according to the generalized method of <FIG>. In this method <NUM>, the CPEe <NUM> receives the transmitted waveforms (see step <NUM> of the method <NUM>), and performs analog-domain upconversion to the target frequency (e.g., user band) per step <NUM>.

Per step <NUM>, the upconverted signals are synchronized via the recovered I/Q signals via the synchronization circuit of the CPEe, and the upconverted signals are converted to the digital domain for use by, e.g., the chipset <NUM> of the CPEe <NUM> (see <FIG>). Within the chipset, the digital domain signals are processed including inter alia serial-to-parallel conversion, FFT transformation of the data back to the frequency domain (step <NUM>), de-mapping of the physical resources (step <NUM>), parallel-to-serial conversion (step <NUM>), and ultimately distribution of the digital (baseband) data to e.g., the 10GbE switch, Wi-Fi router, etc. (step <NUM>).

<FIG> is a logical flow diagram illustrating one particular implementation of content reception and transmission within a premises by a CPEe according to the generalized method of <FIG>. Specifically, as shown in <FIG>, the method <NUM> includes upconversion to the user band (step <NUM>) as in the method <NUM> described above, but rather than conversion to the digital domain as in the method <NUM>, the upconverted analog domain signals are synchronized (step <NUM>) and provided to one or more repeater ports for transmission of the upconverted waveforms via the antenna(e) of the repeater module (see <FIG>).

In exemplary implementations, supplemental link addition may be conducted according to any number of schemes, including without limitation: (i) 3GPP-based CA (carrier aggregation), or (ii) use of an additional MIMO (spatial diversity) layer.

Claim 1:
A method of operating a radio frequency network comprising a hybrid fiber coax infrastructure initially designed to operate at a first normal frequency band, the method enabling the hybrid fiber coax infrastructure to be used to deliver integrated wireless data services, the method comprising:
transmitting, from a distribution node (<NUM>), orthogonal frequency division multiplexing "OFDM" waveforms over at least a portion of the hybrid fiber coax infrastructure using at least a frequency band wider in frequency than a normal operating band of the hybrid fiber coax infrastructure (<NUM>), the frequency band being lower in frequency than a user frequency band used by at least one wireless user device (<NUM>) of the hybrid fiber coax infrastructure;
receiving, via at least one computerized premises device (<NUM>, <NUM>), the transmitted OFDM waveforms, the receiving of the transmitted OFDM waveforms comprising receiving the transmitted OFDM waveforms from the distribution node (<NUM>) disposed upstream from the at least one computerized premises device in the hybrid fiber coax infrastructure;
upconverting, at the at least one computerized premises device, the received OFDM waveforms to the user frequency band to form upconverted waveforms (<NUM>); and
wirelessly transmitting, at the at least one computerized premises device, the upconverted waveforms to the at least one wireless user device (<NUM>).