Apparatus and method for multi-carrier unlicensed heterogeneous channel access

Abstract

Devices and methods for multi-carrier or multi-band utilization in unlicensed wireless networks. In one embodiment, the devices and methods provide enhanced wireless service that provides enhanced bandwidth capabilities to 5G NR-U entities, such as gNodeBs and UE devices, across two heterogeneous unlicensed bands with different media access mechanisms and protocols. In one variant, LBT (listen-before-talk) protocols are used to detect the presence or absence of users within the respective bands of interest. When two or more unoccupied carriers or bands are identified, aggregation operations are used to enhance the downlink / uplink (DL / UL) transmission bandwidth of the device.

Description

[0001] priority

[0002] This application claims priority to U.S. Patent Application No. 16 / 567,509, filed September 11, 2019, entitled “Apparatus and Methods for Multicarrier Unlicensed Heterogeneous Channel Access,” and International Application No. PCT / US2020 / 050512, filed September 11, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to the field of wireless devices and networks thereof, and specifically, in one exemplary aspect, provides a channel access mechanism for radio networks utilizing unlicensed spectrum. Background Technology

[0004] Numerous wireless network technologies, also known as radio access technologies (“RATs”), provide potential means of connecting radio-based communication networks to user facilities. Such RATs typically utilize licensed radio spectrum (i.e., spectrum allocated by the FCC according to the frequency allocation tables compiled under Section 2.106 of Commission Rules). Currently, only frequency bands between 9 kHz and 275 GHz are allocated (i.e., designated for use by one or more terrestrial or space radio communication services or radio astronomy services under specific conditions). For example, a typical cellular service provider might utilize spectrum for so-called “3G” (third generation) and “4G” (fourth generation) wireless communications, as shown in Table 1 below:

[0005] Table 1

[0006]

[0007] Alternatively, unlicensed spectrum may be used, such as spectrum within the so-called ISM band. The ISM band is defined by the ITU Radio Regulations (Article 5) in footnotes 5.138, 5.150, and 5.280. In the United States, the use of the ISM band is governed by Federal Communications Commission (FCC) Rule Part 18, while Part 15 contains rules regarding unlicensed communication devices, even those sharing ISM frequencies. Table 2 below shows typical ISM frequency allocations:

[0008] Table 2

[0009]

[0010] The ISM band is also shared with (non-ISM) license-free communication applications, such as wireless sensor networks in the 915MHz and 2.450GHz bands, and wireless LANs (e.g., Wi-Fi) and cordless phones in the 915MHz, 2.450GHz and 5.800GHz bands.

[0011] In addition, the 5GHz band has been allocated for use by, for example, WLAN equipment, as shown in Table 3:

[0012] Table 3

[0013] With name frequency band Required dynamic frequency selection UNII-1 5.15 to 5.25 GHz no UNII-2 5.25 to 5.35 GHz yes UNII-2 Extension 5.47 to 5.725 GHz yes UNII-3 5.725 to 5.825 GHz no

[0014] User client devices (e.g., smartphones, tablets, phablets, laptops, smartwatches, or other wireless-enabled devices, mobile devices, or others) typically support multiple RATs, enabling devices to interconnect or connect to networks (e.g., the Internet, intranets, or extranets), and typically include RATs associated with licensed and unlicensed spectrum. Specifically, wireless access to other networks by client devices is achieved through wireless technologies that utilize network hardware such as wireless access points (“WAPs” or “APs”), small cells, femtocells, or cell towers, provided by the back-end or backhaul portion of a service provider network (e.g., a cable network). Users typically access the network at nodes or “hotspots,” where they can gain access by connecting to modems, routers, APs, etc., within wireless range.

[0015] 5G New Radio (NR) and NG-RAN (Next Generation Radio Local Area Network)

[0016] NG-RAN, or "Next Generation Radio Local Area Network," is part of 3GPP's "5G" next-generation radio system. 3GPP is currently specifying Release 16 of NG-RAN, its components, and the interactions between related nodes, including the so-called "gNB" (Next Generation Node B or eNB). NG-RAN will provide high-bandwidth, low-latency wireless communication and, depending on the application, will efficiently utilize licensed and unlicensed spectrum of the types described above in a variety of deployment scenarios, including indoor "field" use, urban "macro" (large cell) coverage, rural coverage, in-vehicle use, and "smart" grids and infrastructure. NG-RAN will also integrate with 4G / 4.5G systems and infrastructure, and will further utilize new LTE entities (e.g., "evolved" LTE eNBs or "eLTE eNBs" supporting connections to the EPC (Evolved Packet Core) and NR "NGC" (Next Generation Core).

[0017] In some aspects, Release 16 NG-RAN utilizes the technologies and capabilities of existing LTE / LTE-A technologies (commonly known as 4G and 5G) as a foundation for further feature development and capabilities. For example, one of the notable features of LTE-A is the extension of LTE to the unlicensed spectrum of 5 GHz, including the spectrum between 5150 MHz and 5995 MHz. Additionally, the 5 GHz band is currently utilized by the latest WLAN technologies, referring to 802.1ln / ax / ax. The LTE-A Release 10 specification, 3GPP TR 36.808, introduced carrier aggregation (in other words, multi-carrier operation) to increase bandwidth and thus improve throughput. Because maintaining backward compatibility with Releases 8 and 9 is important, aggregation is based on Release 8 and 9 carriers; furthermore, see “3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Carrier Aggregation (Release 10)”, August 2010, the entire contents of which are incorporated herein by reference.

[0018] As described in 3GPP TR 36.808 and generally illustrated in Figure 1 of this document, LTE-A User Equipment (UE) 103 can be allocated across multiple carriers on downlink (DL) 105 and uplink (UL) 107. Each aggregated carrier is referred to as a component carrier (CC). Component carriers can have bandwidths of 1.4, 3, 5, 10, 15, or 20 MHz, and a maximum of five aggregated carriers can be supported between the UE and base station 101 (e.g., a 3GPPeNB or gNB). Therefore, the maximum aggregated bandwidth is 100 MHz. Individual component carriers may also have different bandwidths. See Figure 1 of this document.

[0019] 3GPP TS 36.212 defines the Random Access Channel (RACH) procedure for LTE and LTE-A. When a UE first connects, it begins searching for networks and available frequency bands. It is possible for a UE to connect to multiple frequency bands from different networks. Therefore, the UE synchronizes with the network through the established RACH protocol. Each UE sends a specific preamble to the network on the RACH. If two UEs use the same RACH simultaneously, a collision may occur. 3GPP TS 36.212 defines 64 different preamble patterns available to the UE, and the UE can decide which one to use randomly. If the UE successfully transmits, the eNB sends a "Random Access Response" to the UE on the DL-SCH (Downlink Shared Channel), granting the UE network access and allocating spectrum to the UE.

[0020] Similar to the RACH procedure described above, when a 5G NR / NG-RAN radio initially connects to the 5G NR / NG-RAN network, it uses a random access protocol. Specifically, in 5G NR / NG-RAN, initial access is generally similar to the standard procedure relied upon by traditional LTE. However, the specific implementation of initial access differs significantly between 5G NR / NG-RAN and traditional LTE. In traditional LTE implementations, synchronization signals are transmitted using an omnidirectional antenna, while 5G NR / NG-RAN and NR / NGgNB employ beam scanning and management when transmitting synchronization signals. At the start of the 5G random access procedure, neither the UE nor the gNB is aware of the appropriate beam direction; therefore, the initial synchronization signal can be transmitted using multi-beam scanning. After detecting the initial synchronization signal, the UE selects the optimal gNB beam for further DL acquisition. The gNB also utilizes multiple Rx beams because the UE's location is unknown. The gNB provides multiple RACH resources to the UE and applies one Rx beam for each RACH resource.

[0021] Unlicensed multicarrier operation and issues -

[0022] As discussed above, due to the carrier aggregation capabilities in LTE, carriers aim to extend the use of unlicensed spectrum by utilizing LTE technology. Unlicensed LTE technologies (e.g., LAA or MulteFire at 5 GHz) as well as IEEE 802.1ln / ac / ax (Wi-Fi at 2.4 GHz / 5 GHz) and IEEE 802.1lad / ay (60 GHz) all support multi-carrier operation in unlicensed spectrum. At a high level, each technology follows a specific multi-carrier channel access procedure relative to a set of DL or UL carriers targeted for transmission.

[0023] For example, in the case of the IEEE-Std.80211 technology mentioned above, a dual-energy detection plus preamble detection method is used on each carrier in multiple candidate carrier sets. Furthermore, 802.1lax APs can aggregate 5GHz and 2.4GHz bands, but each band uses the same channel access mechanism.

[0024] In the case of LAA and MulteFire, energy detection is used on each carrier.

[0025] However, in all cases, the multi-carrier channel access mechanism is homogeneous; that is, the channel access process on each carrier is essentially the same.

[0026] The entire contents of 3GPP TR 38.889 3GPP V16.0.0 (2018-12), entitled “Technical Report - 3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; Study on Unlicensed Spectrum Access Based on NR (Release 16),” are incorporated herein by reference, discussing the LBT mechanism and requirements for NR-U. It should be noted that in Release 16, 5G NR-U is considering the use of multi-carrier operation in unlicensed spectrum below 7 GHz. However, the aforementioned homogeneous channel access mechanism may be unsuitable when NR-U nodes aggregate carriers from unlicensed bands of 5 GHz and 6 GHz, and furthermore, due to the different regulatory requirements or coexistence criteria in these different bands. For example: (i) NR-U may need to implement the LBT (Listen Before Talk) protocol to access the physical medium for transmission according to TS 38.889 (or TS 37.213 for LTE-LAA); and (ii) the mechanisms for taking into account transmission failures and the implementation of the resulting exponential backoff mechanism may differ.

[0027] Therefore, no feasible multi-carrier channel utilization or aggregation mechanism exists in the unlicensed spectrum that can coordinate different channel access mechanisms that can be used for a subset of aggregated carriers. Accordingly, there is a need for improved devices and methods to provide multi-carrier channel access in such heterogeneous environments, in order to further achieve increased unlicensed bandwidth throughput through carrier aggregation or other multi-carrier utilization techniques. Summary of the Invention

[0028] This disclosure addresses the aforementioned needs, in particular, by providing apparatus and methods for enhanced multicarrier channel access mechanisms in unlicensed frequency bands.

[0029] In a first aspect, a method for operating a wireless network having at least one wireless access node is disclosed. In one embodiment, the method includes: using a first carrier in a first unlicensed frequency band for transmitting at least a first portion of user data between the at least one wireless access node and a wireless user equipment; and simultaneously using a second carrier in a second unlicensed frequency band for transmitting at least a second portion of the user data between the at least one wireless access node and the wireless user equipment.

[0030] In one variant, the first and second unlicensed frequency bands utilize a heterogeneous carrier access mechanism.

[0031] In another variant, the at least one wireless access node includes an NR (New Radio) compatible distributed unit (DU); and the simultaneous use includes the transmission of at least a first portion and a second portion of the user data coordinated with the wireless user equipment.

[0032] In a further variation, utilizing the first carrier while simultaneously using the second carrier includes scanning at least each of the first and second carriers using correspondingly different scanning mechanisms in the scanning mechanism.

[0033] In another variant, scanning at least each of the first and second carriers using a correspondingly different scanning mechanism comprises: scanning at least a first and a second frequency band containing the first and second carriers, and each band containing a plurality of other carriers; and selecting at least the first and second carriers for utilization from their respective plurality of other carriers. In one embodiment, selecting at least the first and second carriers for utilization from their respective plurality of other carriers comprises: selecting the first carrier and at least one other carrier within the first frequency band; selecting the second carrier and at least one other carrier within the second frequency band; aggregating (i) the first carrier and the at least one other carrier within the first frequency band with (ii) the second carrier and the at least one other carrier within the second frequency band; and utilizing the first carrier and utilizing the second carrier in the aggregation.

[0034] In yet another variation, utilizing the first carrier while simultaneously using the second carrier includes using correspondingly different access mechanisms in the access mechanism to access at least each of the first and second carriers. In one implementation, using correspondingly different access mechanisms in the access mechanism to access at least each of the first and second carriers includes using corresponding first and second LBT (Listen-Before-Speak) based processes.

[0035] In a further variation, the transmission of at least one of 3GPP PDCCH control data or PDSCH user plane data on each of the first and second carriers is carried out using the first carrier and simultaneously using the second carrier.

[0036] In another aspect, a computerized network device for use in a wireless infrastructure is disclosed. In one embodiment, the computerized network device includes: a digital processing device; at least one data network interface for data communication with the digital processing device; and a storage device for data communication with the digital processing device, the storage device including a storage medium having at least one computer program.

[0037] In one variant, the at least one computer program is configured to, when executed on the digital processing device, cause the computerized network device to: determine the availability of a first unlicensed frequency band using a first media access protocol; determine the availability of a second unlicensed frequency band using a second media access protocol, the second unlicensed frequency band having access requirements different from the first unlicensed frequency band; and, based on the determination of the availability of the first unlicensed frequency band and the determination of the availability of the second unlicensed frequency band, cause both bands to be used simultaneously in the aggregation.

[0038] In another variant, the aggregation simultaneously utilizes two bands to include data transactions with public user devices using the first unlicensed band, independent of the use of the second unlicensed band.

[0039] In a further variant, the computerized network device includes a gNodeB supporting 5G NR-U, and the first and second unlicensed frequency bands include the 5GHz band and the 6GHz band, respectively.

[0040] In a further variant, the first media access protocol includes an energy detection protocol, and the second access protocol includes a preamble detection protocol.

[0041] In another aspect, a method for operating a wireless network node is disclosed. In one embodiment, the method includes: determining the need for multi-band operation; at least based on the determination, accessing a cognitive network entity to allocate one or more carriers in a first of the multiple bands; performing an LBT-based media access protocol on at least a second of the multiple bands to identify at least one carrier that can be used therein; and transacting data with a wireless client device using at least the allocated one or more carriers in the first band and the identified at least one carrier in the second band.

[0042] In one variant, the method further includes performing an LBT-based media access protocol on at least one or more of the allocated carriers to verify its availability prior to the utilization. In one embodiment, performing the LBT-based media access protocol on at least one or more of the allocated carriers to verify its availability includes an LBT-based protocol different from the LBT-based media access protocol performed on at least the second band.

[0043] In a further aspect, a method for providing multi-carrier utilization in an unlicensed frequency band is disclosed. In one embodiment, the method includes: measuring a first set of channel sensing parameters; measuring a second set of channel sensing parameters; comparing the first set of channel sensing parameters with a first set of thresholds; comparing the second set of channel sensing parameters with a second set of thresholds; determining the availability of the first frequency band based on the measurements of the first set; determining the availability of the second frequency band based on the measurements of the second set; and transmitting a communication message in at least one of the first and second frequency bands.

[0044] In one variant, an unlicensed 5G NR-U device (e.g., gNB and / or UE) operating across an unlicensed frequency band is utilized. In one implementation, the 5G NR-U device performs a Listen-After-Talk (LBT) process to determine the availability of the two frequency bands mentioned above.

[0045] In another aspect of this disclosure, a 3GPP xNB (e.g., 4.5G and / or 5G) is disclosed. In one embodiment, the gNB includes: a receiver module, a transmitter module, a first channel access module (LBT A), a second channel access module (LBT B), and a channel sensing module. In a variant, the gNB may further include: a processor device; a wireless modem chipset that communicates with the processor device; a program memory that communicates with the processor device; an RF front-end module; a local database; and a network interface module for communicating with a core network. In a further embodiment, the program memory includes at least one program configured to, when executed on the processor device, cause communication signals to be transmitted on a first and / or second frequency band.

[0046] In another aspect of this disclosure, a 3GPP UE (e.g., 4.5G and / or 5G) is disclosed. In one embodiment, the UE includes: a receiver module, a transmitter module, a first channel access module (LBT A), a second channel access module (LBTB), and a channel sensing module. In a variant, the UE may further include: a processor device; a wireless modem chipset that communicates with the processor device; a program memory that communicates with the processor device; a mass storage device; and an RF front-end module. In a further embodiment, the program memory includes at least one program configured to, when executed on the processor device, cause communication signals to be transmitted on a first and / or second frequency band.

[0047] In another aspect of this disclosure, a computer-readable device is disclosed. In one embodiment, the device includes a storage medium configured to store one or more computer programs. In another embodiment, the device includes program memory, an HDD, or an SDD on a computerized controller device (e.g., an MSO controller). In yet another embodiment, the device includes program memory, an HDD, or an SDD on a computerized access node (e.g., a gNB or UE).

[0048] These and other aspects should become obvious when considering the publicly available information provided herein. Attached Figure Description

[0049] Figure 1 is a graphical illustration of an exemplary prior art method of carrier aggregation used, for example, in a licensed LTE wireless system.

[0050] Figure 2 This is a graphical illustration of an exemplary embodiment of multi-carrier utilization according to the present disclosure.

[0051] Figure 3 It is a graphical representation illustrating an exemplary allocation of 3GPP frames to two frequency bands.

[0052] Figure 4 It is a graphical representation illustrating an example of 3GPP frames using two frequency bands and the transmission of control data.

[0053] Figure 5A This is a conceptual block diagram illustrating an embodiment of the general xNB architecture according to the present disclosure.

[0054] Figure 5B This is an explanation Figure 5A A conceptual block diagram of an implementation scheme for the xNB architecture, showing one configuration of its LBT module.

[0055] Figure 6A This is a functional block diagram illustrating an embodiment of the UE architecture according to the present disclosure.

[0056] Figure 6B This is a functional block diagram illustrating an implementation scheme of the UE architecture according to this disclosure.

[0057] Figures 6C to 6D This is a functional block diagram illustrating an implementation scheme of the channel access mechanism in gNb or UE according to this disclosure.

[0058] Figure 6E This is a functional block diagram illustrating the implementation scheme of the channel access mechanism in the gNB and UE according to this disclosure.

[0059] Figure 7This is a logic flowchart illustrating an exemplary method for unlicensed channel access in a gNB.

[0060] Figure 7A This is an explanation Figure 7 A logical flowchart of an exemplary implementation of the LBT process.

[0061] Figure 7B This is an explanation Figure 7 A logic flowchart of a further exemplary implementation of the LBT process.

[0062] Figure 7C This is an explanation Figure 7A A logical flowchart of an exemplary implementation of a multi-band LBT process.

[0063] Figure 8 This is an explanation Figure 7C A logical flowchart of an implementation scheme for the LBT process.

[0064] Figure 9 This is an explanation Figure 7C A logic flowchart of another implementation of the LBT process.

[0065] Figure 10 It is shown Figure 7C A logical flowchart of another implementation scheme of the LBT process.

[0066] Figure 11 This is a logic flowchart illustrating an exemplary method for channel access in an unlicensed band used in a UE.

[0067] Figure 11A This is an explanation Figure 11 A logical flowchart of an exemplary implementation of the LBT process.

[0068] Figure 12 This is an explanation Figure 11A A logical flowchart of an implementation scheme for the LBT process.

[0069] Figure 13 This is an explanation Figure 11A A logic flowchart of another implementation of the LBT process.

[0070] Figure 14 This is an explanation Figure 11A The logic flowchart of another LBT process.

[0071] Figure 14 A to 14B are ladder diagrams illustrating the channel access procedure requested by the gNB according to this disclosure.

[0072] Figure 14C is a ladder diagram illustrating the channel access procedure requested by the UE according to this disclosure.

[0073] Figure 15 This is a functional block diagram illustrating an exemplary packet-based network architecture useful in the backhaul and support operation of the enhanced device (e.g., gNBe) disclosed herein.

[0074] Figure 15 A is a functional block diagram illustrating an exemplary embodiment of a prior art gNB architecture that includes a CU and multiple DUs.

[0075] Figure 15B This is a functional block illustrating an exemplary embodiment of a gNB architecture including a CUe and multiple DUs according to this disclosure.

[0076] Figure 15C This is a functional block diagram illustrating another exemplary embodiment of a gNB architecture comprising a plurality of CUes and corresponding plurality of DUes according to the present disclosure.

[0077] Figure 15D This is a functional block diagram illustrating another exemplary embodiment of a gNB architecture according to the present disclosure, which includes multiple CUe devices that are logically cross-connected to multiple different cores.

[0078] Figure 16 This is a functional block diagram of one embodiment of the 3GPP gNBe Due (Enhanced Distributed Unit) configured according to this disclosure.

[0079] Figure 17 This is a functional block diagram of one embodiment of a 3GPP-enhanced UE configured according to this disclosure.

[0080] All numbers Copyright 2019-2022 Charter Communications Operating LLC. All rights reserved. Detailed Implementation

[0081] Now refer to the accompanying drawings, where similar numbers throughout the text refer to similar parts.

[0082] As used herein, the term "application" (or "app") generally refers to (but is not limited to) an executable software unit that implements a specific function or subject. The subjects of applications vary widely across multiple disciplines and functions (e.g., on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculators, etc.), and an application may have more than one subject. Units of executable software typically run in a pre-defined environment; for example, a unit may contain a downloadable Java Xlet. TMIt runs in the JavaTV environment TM .

[0083] As used herein, the term “CBRS” refers to (but is not limited to) the architecture and protocols described in the following document: Signaling protocols and procedures for the Citizens Broadband Radio Service (CBRS): Spectrum Access System (SAS) - Citizens Broadband Radio Service Device (CBSD) Interface Technical Specification - Document WINNF-TS-0016, Version VI.2.1.3, January 2018, the entire contents of which, and any related documents or subsequent versions thereof, are incorporated herein by reference.

[0084] As used herein, the term "central unit" or "CU" refers to (but is not limited to) a centralized logical node within a wireless network infrastructure. For example, a CU may be embodied as a 5G / NR gNB central unit (gNB-CU), which is a logical node carrying the RRC, SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the gNB, controlling the operation of one or more gNB-DUs, and terminating the FI interface connected to one or more DUs (e.g., gNB-DUs) as defined below.

[0085] As used herein, the terms “client device” or “user device” or “UE” include (but are not limited to) set-top boxes (e.g., DSTB), gateways, modems, personal computers (PCs) and minicomputers (whether desktop, laptop or otherwise), and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablet computers, “phablets”, smartphones, and vehicle infotainment systems or portions thereof.

[0086] As used herein, the terms "computer program" or "software" refer to any sequence or human- or machine-recognizable steps that contain the ability to perform functions. Such programs can be presented 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 object-oriented environments such as the Common Object Request Broker Architecture (CORBA) and Java. TM (Including J2ME, JavaBean, etc.)

[0087] As used herein, the term "distributed unit" or "DU" refers to (but is not limited to) a distributed logical node within a wireless network infrastructure. For example, a DU can be embodied as a 5G / NR gNB distributed unit (gNB-DU), which is a logical node carrying the RLC, MAC, and PHY layers of a gNB or en-gNB, and whose operation is partially controlled by a gNB-CU (see above). A gNB-DU supports one or more cells, while a given cell is supported by only one gNB-DU. The gNB-DU terminates its FI interface connection to the gNB-CU.

[0088] As used herein, the term “DOCSIS” refers to any existing or planned variant of the wired data service interface specification, including, for example, DOCSIS versions 1.0, 1.1, 2.0, 3.0, and 3.1.

[0089] As used herein, the terms “headend” or “backend” generally refer to a network system controlled by an operator (e.g., an MSO) that uses client devices to distribute programming to MSO customers or provide other services such as high-speed data transmission and backhaul.

[0090] As used herein, the term “Internet (Internet and internet)” is used interchangeably to refer to an interconnected network that includes (but is not limited to) the Internet. Other common examples include (but are not limited to): networks of external servers, “cloud” entities (such as storage devices that are not local to the device, storage devices that are typically accessible at any time via a network connection), service nodes, access points, controller devices, client devices, etc.

[0091] As used herein, the term “LTE” refers to (but is not limited to and, where applicable) any variant or version 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), 4G LTE, WiMAX, VoLTE (LTE Voice) and other wireless data standards.

[0092] As used herein, the term "memory" includes any type of integrated circuit or other storage device suitable for storing digital data, including (but not limited to) ROM, PROM, EEPROM, DRAM, SDRAM, DDR / 2 SDRAM, EDO / FPMS, RLDRAM, SRAM, flash memory (e.g., NAND / NOR), 3D memory, and PSRAM.

[0093] As used herein, the terms “microprocessor” and “processor” or “digital processor” generally refer to all types of digital processing devices, including (but not limited to) digital signal processors (DSPs), reduced instruction set computers (RISCs), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computer architectures (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single IC die or distributed across multiple components.

[0094] As used herein, the term “MSO” or “multi-system operator” refers to a cable, satellite, or terrestrial network provider that has the infrastructure required to provide services containing programming and data through these media.

[0095] As used herein, the term "MNO" or "mobile network operator" refers to a cellular, satellite, WMAN (e.g., 802.16) or other network service provider that has the infrastructure necessary to provide services through these media, including (but not limited to) voice and data. The term "MNO" as used herein is further intended to include MVNO, MNVA, and MVNE.

[0096] As used herein, the terms “network” and “bearer network” generally refer to any type of telecommunications or data network, including (but not limited to) hybrid fiber-coaxial (HFC) networks, satellite networks, telecommunications networks, and data networks (including MAN, WAN, LAN, WLAN, the Internet, 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 communication technologies or network protocols (e.g., SONET, DOCSIS, IEEE 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, LTE / LTE-A / LTE-U / LTE-LAA, 5G NR, WAP, SIP, UDP, FTP, RTP / RTCP, H.323, etc.).

[0097] As used herein, the terms “5G” and “New Radio (NR)” mean (but are not limited to) devices, methods or systems conforming to 3GPP Release 15, and any modifications, subsequent versions or amendments or supplements to new radio technologies, whether licensed or unlicensed.

[0098] As used herein, the term "QAM" refers to a modulation scheme used to transmit signals over, for example, cables or other networks. Depending on the network details, such modulation schemes can use any constellation level (e.g., QPSK, 16-QAM, 64-QAM, 256-QAM, etc.). QAM can also refer to the physical channel modulated according to the scheme.

[0099] As used herein, the term “SAS (Spectrum Access System)” means (but is not limited to) one or more SAS entities that may comply with and be certified for this purpose under FCC Part 96, including (i) federal SAS (FSAS), (ii) commercial SAS (e.g., SAS operated by a private company or entity), and (iii) other forms of SAS.

[0100] As used herein, the term "server" means any computerized component, system, or entity, regardless of its form, adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network.

[0101] As used herein, the term “storage device” means (but is not limited to) a computer hard disk drive, a DVR device, a memory, a RAID device or array, optical media (such as CD-ROM, laser disc, Blu-ray, etc.) or any other device or media capable of storing content or other information.

[0102] As used herein, the terms “unlicensed” and “unlicensed spectrum” refer to (but are not limited to) radio spectrum (e.g., from the sub-GHz range to 100 GHz) that is generally accessible, at least for part of the time, to users who do not have explicit licenses, such as the ISM band, 2.4 GHz band, 5 GHz band, 6 GHz band, quasi-licensed spectrum such as CBRS, 60 GHz (V-band), and other spectrum closely related to the geographic area of ​​operation (whether within or outside the United States) that will be known to those skilled in the art in this disclosure.

[0103] As used herein, the term “Wi-Fi” means (but is not limited to) any variation of the applicable IEEE standard 802.11 or related standards, including 802.11a / b / g / n / s / v / ac / ax, 802.11-2012 / 2013 or 802.11-2016, and Wi-Fi Direct (in particular including the “Wi-Fi Peer-to-Peer (P2P) Specification”, which is incorporated herein by reference).

[0104] As used herein, the term “xNB” refers to any 3GPP compliant node, including (but not limited to) eNB (eUTRAN) and gNB (5G NR).

[0105] Overview

[0106] In one exemplary aspect, this disclosure provides improved architectures, methods, and apparatus for providing enhanced wireless services, particularly utilizing multi-carrier channel access mechanisms for unlicensed spectrum, wherein different (heterogeneous) channel access mechanisms associated with different carriers (or carrier groups) can be adapted. Therefore, in addition, the exemplary embodiments described herein enable the simultaneous use of spectrum in different operating bands with originally incompatible access mechanisms and requirements to provide enhanced bandwidth between access nodes (e.g., 5g NR-U gNB) and user equipment (e.g., UE).

[0107] In one embodiment, an NR-U system is described where two operating frequency bands are used, without necessarily listing or including specific data related to the operating frequency bands. In a variant, the NR-U access node device (gNBe) of the present invention includes logic within its CU and / or DU that causes multiple (e.g., two) simultaneous LBT processes to be performed on each band, resulting in their simultaneous use. In one embodiment, the LBT process includes sensing one or more channel parameters for each band (which may include one or more individual carriers) to determine whether an unlicensed carrier is available. The LBT process across two (or more) carriers / bands may be heterogeneous, including sensing parameters, protocols, and / or backoff mechanisms applied to each carrier / band, consistent with the primary access mechanisms applicable to these bands.

[0108] In other variants, an enhanced UE (UEe) is described, which is configured to perform an LBT procedure to identify the band on which an NR-U device can operate.

[0109] In other variants, both UEe and gNBe can perform LBT procedures on each carrier to check the availability of the operating band.

[0110] Detailed description of exemplary embodiments

[0111] Exemplary embodiments of the devices and methods of this disclosure will now be described in detail. While these exemplary embodiments are described in the context of previously mentioned radio access nodes (e.g., GNBs) associated with or at least partially supported by a service provider's managed network (e.g., MSO and / or MNO networks), other types of radio access technologies (“RATs”), other types of networks and architectures configured to deliver digital data (e.g., text, images, games, software applications, video, and / or audio) may be used consistent with this disclosure. Such other networks or architectures may be broadband, narrowband, or other forms, and are therefore only exemplary in nature.

[0112] It will also be understood that while this disclosure is generally described in the context of a network providing services to customers or consumers or end users or subscribers (i.e., within a defined service area, location, or other type of location), this disclosure is readily applicable to other types of environments, including, for example, outdoor, commercial / retail, or enterprise sectors (e.g., corporate), and even government applications. Other applications are also possible.

[0113] Other features and advantages of this disclosure will be readily apparent to those skilled in the art upon reference to the accompanying drawings and the detailed description of the exemplary embodiments given below.

[0114] Multi-carrier heterogeneous access

[0115] Figure 2 An example of multi-carrier aggregation for LTE / LTE-A in an unlicensed band is shown in a wireless communication 200 according to an embodiment of the present disclosure. In this example, an enhanced gNB 201 (which will be referenced herein) Figures 3 to 16 (The figures in the diagrams are discussed in more detail.) UE 203 transmits OFDMA signals to UE 203 via DL channel 205. UE 203 transmits SC-FDMA UL signals to gNB 201 via UL channel 205. Link 205 is associated with frequency FI (band A) in the unlicensed spectrum. gNB 201 can also transmit OFDMA signals to UE 203 via DL link 207. Link 205 is also associated with frequency F2 (band B) in the unlicensed spectrum. UE 203 can also transmit SC-FDMA signals to gNB 201 via UL link 207. It is worth noting that the two segments (A and B) may utilize heterogeneous access mechanisms depending on the selected band and its corresponding regulations, standards, and specific implementations. For example, examples of such heterogeneity may exist in NR-U aggregation of unlicensed bands in 5 GHz and 6 GHz. For example, in the 5 GHz band, a centralized LBT process is sufficient for coexistence. In the 6GHz band, a centralized coordination entity known as the Automatic Frequency Coordination (AFC) entity can also specify which subsets of the band are available for unlicensed LBT-based access to protect existing users from interference or achieve other objectives.

[0116] As described in more detail below, data and control signals can be transmitted between gNB 201 and UE 205 via various links (i.e., link 205 and / or link 207). Depending on the configuration and application, there may be situations where one or both of links 205 and 207 can be used. gNB 201 can communicate with one or more NG cores 209, such as NG cores operated by MNO or MSO. Each NG core 209 may have multiple gNBs 201 associated with it. See below for more information. Figure 15A detailed discussion of exemplary gNB and 5GC core configurations from A to 15E.

[0117] Figure 2 This scenario can occur in situations where any MSO or mobile network operator (MNO) or a combination thereof (e.g., through MSO / MNO cooperation or infrastructure sharing agreements) is able to operate in unlicensed spectrum.

[0118] Figure 3 This section illustrates an example of frames used for DL / UL transmission in an unlicensed 3GPP network. Each frame, 301a-c and 303a-c, contains data and control signals for DL / UL. The first frame, 301a-c, is associated with spectrum FI (band A), and the second frame, 303a-c, is allocated to spectrum F2 (band B). Frames 301a-c and 303a-c are 10 ms long. In some examples, the boundary of the first frame, 301a-c, is synchronized with the boundary of the second frame, 303a-c. In other examples, the frame boundaries may not be synchronized with the boundaries of other frames. It will be understood that while cross-band frame synchronization may or may not be present, data can be transmitted using normally synchronized (simultaneous) bands. In one variation, spatial diversity (e.g., MIMO) channels are allocated to each of the different bands, although this is not required.

[0119] Figure 4 Examples of 3GPP frame structures in unlicensed frequency bands A and B are shown. Frame 401 is an example of a frame associated with frequency band A in periodic 3GPP (e.g., NR) radio frame transmissions, and frame 409 is associated with frequency band B in periodic NR radio frame transmissions. Radio frames 401 and 409 are 10 ms long and consist of 10 time slots. Each time slot is 1 ms long and may be used for DL ​​or UL. Control signals for frame 401 are transmitted via Physical Dedicated Control Channel (PDCCH) 405. Data signals for frame 401 are transmitted via Physical Dedicated Shared Channel (PDSCH) 407. LBT procedure 403 is used to request LBT access on unlicensed frequency band A. Control signals for frame 409 are transmitted via Physical Dedicated Control Channel (PDCCH) 413. Data signals for frame 409 are transmitted via Physical Dedicated Shared Channel (PDSCH) 415. LBT procedure 411 is used to request LBT access on unlicensed frequency band B.

[0120] refer to Figure 5A This document illustrates and describes an embodiment of a wireless device 500 for constructing a 5G unlicensed wireless communication system. In one example, device 500 may be a 5G gNB base station, such as... Figure 2 gNBe 201. In Figure 5AWithin a general architecture, device 500 includes receiver module 501, unlicensed LBT module 503, and transmitter module 505. These components communicate with each other, for example, in a transceiver configured with LBT module logic to interact with (see...). Figure 16 ).

[0121] The components of device 500 may be implemented individually or in part in software, firmware, or hardware. Receiver module 501 may be included in a radio frequency (RF) receiver operating in unlicensed spectrum. (Reference) Figure 3 and 4 The receiver module 501 can be used with frame structures 300 and 400 via wireless communication links 205 and / or 207. Figure 2 Transmitter module 505 receives data and control signals. It may include a radio frequency (RF) receiver operating in unlicensed spectrum and may be integrated with receiver module 501. (Reference) Figure 3 and 4 The transmitter module 505 can be used to transmit data and control signals via wireless communication links 205 and / or 207 using frame structures 300 and 400.

[0122] Figure 5B illustrate Figure 5A One embodiment of a general-purpose wireless device 500. In this embodiment, device 550 is configured for use in a 5G unlicensed wireless (e.g., 5G NR-U) communication system. Device 550 may include a receiver module 553, an LBT module 555, and a transmitter module 563. The components of the illustrated device 550 may be implemented individually or in part in software, firmware, or hardware. Receiver module 553 may include a radio frequency (RF) receiver operating in unlicensed spectrum (e.g., NR-U band or others). Reference Figure 3 and 4 Receiver module 553 can be used to receive data and control signals via wireless communication links 205 and / or 207 using frame structures 300 and 400. Transmitter module 563 can be included in a radio frequency (RF) receiver operating in unlicensed spectrum. Reference Figure 3 and 4 The transmitter module 563 can be used to transmit data and control signals on wireless communication links 205 and / or 207 using, for example, frame structures 300 and 400. Figure 5A With the same configuration, the receiver and transmitter modules can be aggregated into a transceiver.

[0123] The LBT module 555 in this configuration includes an LBT “A” module 557, an LBT “B” module 559, and a channel sensing module 561. The LBT A module executes an LBT protocol to determine the availability of unlicensed spectrum (e.g., one or more carriers) in band A. The LBT B module executes a similar LBT protocol to determine the availability of unlicensed spectrum in band B. The channel sensing module 561 is configured to measure N different parameters {a1, a2, ..., aN} and {b1, b2, ..., bN} in bands A and B, respectively. The channel sensing module 561 compares the measured parameters {a1, a2, ..., aN} and {b1, b2, ..., bN} with, for example, predetermined thresholds {t1, t2, ..., t2N} and {tb1, tb2, ..., tbN}, and determines whether any other device (e.g., a UE or gNB) is transmitting in either band A or B. If the channel sensing module 561 determines that either frequency band A or B is available, then the transmitter module 563 may initiate transmission (or not initiate transmission) depending on the application’s utilization logic (e.g., whether two or more carriers must be available before transmission can begin).

[0124] Figure 6A This description illustrates a general configuration of a device 600 for use in a 5G UEe according to this disclosure. The UEe device 600 includes a receiver module 601, an unlicensed LBT module 603, and a transmitter module 605.

[0125] and Figure 5A Similar to gNBe, components of the UEe device 600 can be implemented individually or in part in software, firmware, or hardware. Receiver module 601 includes a radio frequency (RF) receiver configured to operate in unlicensed spectrum. (Reference) Figure 3 and 4 The receiver module 601 can be used with frame structures 300 and 400 via wireless communication links 205 and / or 207. Figure 2 It receives data and control signals. Transmitter module 605 includes a radio frequency (RF) receiver configured to operate in unlicensed spectrum. (Reference) Figure 3 and 4 The transmitter module 605 can be used to transmit data and control signals via wireless communication links 205 and / or 207 using, for example, frame structures 300 and 400.

[0126] refer to Figure 6B ,based on Figure 6AThis document illustrates a general configuration of a UEe device 653 used in an unlicensed 5G wireless communication system. The UEe device 653 includes a receiver module 653, an LBT module 655, and a transmitter module 663. As described above, the components of the UEe device 653 may be implemented individually or in part in software, firmware, or hardware. The receiver module 653 includes a radio frequency (RF) receiver configured to operate within unlicensed spectrum. (Reference) Figure 3 and 4 Receiver module 653 can be used to receive data and control signals via wireless communication links 205 and / or 207 using frame structures 300 and 400. Transmitter module 663 includes a radio frequency (RF) receiver configured to operate in unlicensed spectrum. Reference Figure 3 and 4 The transmitter module 663 can be used to transmit data and control signals via wireless communication links 205 and / or 207 using, for example, frame structures 300 and 400.

[0127] The LBT module 655 of the illustrated UEe 650 includes an LBT A module 657, an LBT B module 659, and a channel sensing module 661. The LBT A module executes the LBT protocol as described elsewhere herein to determine the availability of one or more carriers in unlicensed spectrum within band A. Similarly, the LBT B module executes the LBT protocol to determine the availability of unlicensed spectrum in band B. The channel sensing module 661 measures N different parameters {a1, a2, ..., aN} and {b1, b2, ..., bN} for bands A and B, respectively. Module 655 compares the measured parameters {a1, a2, ..., aN} and {b1, b2, ..., bN} with predetermined thresholds {t1, t2, ..., tN} and {tb1, tb2, ..., tbN}, respectively, and determines whether any other device is transmitting on bands A and B. If the channel sensing module determines that either frequency band A or B is available, then the transmitter module 663 can then initiate transmission according to its utilization logic.

[0128] Figures 6C to 6E Various embodiments of the disclosed gNB UE architecture in a wireless 5G wireless network according to this disclosure are described. In these various illustrated architectures, one or both of the gNB and UE may be "enhanced" (i.e., include the LBT carrier utilization logic described herein) depending on the desired configuration.

[0129] As shown, gNBs 601c to 601e can transmit control and data signals to UEs 609c to 609e via DL channels 605c to 605e and / or 607c to 607E. UEs 609c to 609e can also transmit control and data signals to gNBs 601c to 601e via UL channels 605c to 605e and / or 607c to 607E. gNBs 601c to 601e can also receive control and data signals from UEs via UL channels 605c to 605e and / or 607c to 607E. UEs 609d to 609e can also receive control and data signals from gNBs via UL channels 605c to 605e and / or 607c to 607E. The gNB may or may not be the same channel, depending on the configuration.

[0130] The following text is about Figures 15B to 15D In more detail, the LBT logic module of gNBe 5033 can be implemented in gNBe's CUe and / or DUE. Figure 6C In the architecture, the LBT module 503 is only implemented in 5G gNBe (not UE).

[0131] exist Figure 6D In this architecture, the LBT module 603 is implemented in the 5G UEe. Figure 6E In the architecture, the LBT module is implemented in 5GgNBe and UEe.

[0132] refer to Figures 6C to 6D Suppose that, according to one scheme of utilization logic, transmission on both band A and band B begins as soon as either of the two bands is available (e.g., at least one heterogeneous carrier is available). For example, if LBT A 557 ( Figure 5B Once the availability of band A is determined, gNBe can begin transmitting data and control signals on band A.

[0133] However, in other utilization schemes, simultaneous transmission in two frequency bands can be regarded as a gating criterion; for example, two or more carriers must be available for "heterogeneous aggregation" before transmission begins.

[0134] However, given this disclosure, those skilled in the art will understand other approaches, such as those that simplify RF hardware complexity. For example, if LBT A has completed its carrier availability assessment before LBT B, then LBT A can transmit an initial signal (e.g., a preamble or others) to occupy band A until LBT B has completed its assessment, and vice versa. Once both LBT A and LBT B have completed their assessments and both bands are available, data and control signals can be transmitted simultaneously on both bands in a heterogeneous aggregation manner.

[0135] It will also be understood that, although the foregoing embodiments describe the evaluation and utilization of two (2) heterogeneous carriers (e.g., bands A and B) (including aggregation in some scenarios), the principles of this disclosure can be readily extended to: (i) carrier blocks; for example, where bands A and B comprise multiple individual carriers or subcarriers, which can be regarded as a whole by one of the LBT A / B logic blocks described above (e.g., evaluating the entire block or range of in-band carriers / subcarriers, for example by wideband scanning or evaluating a 100MHz wide NR band comprising five 20MHz LTE bands); and (ii) single carriers with multiple bands or more than two (e.g., bands A, B…N).

[0136] method

[0137] Figure 7 This is a flowchart illustrating an exemplary embodiment of a general method 700 for unlicensed channel access according to this disclosure. This method is described in the exemplary context of the unlicensed channel access process referenced herein, although it will be understood that, in light of this disclosure, it is applicable to other processes and applications skilled in the art. Method 700 Reference Figure 2 The exemplary gNBe 201 is described, although it may be practiced by other entities (e.g., LBT processes based on 5GC or MSO cores).

[0138] Incidentally, the previously cited existing 5G NR / NG-RAN RACH procedure (i.e., the procedure performed by the UE when the call is connected) includes the following four steps:

[0139] 1. Based on synchronization information from the gNB, the UE selects the RACH preamble sequence (MSG1) and transmits it at the most recent RACH time (occurring every 10, 20, 40, 80, or 160 ms). Due to reciprocity, the UE can use the Tx beam corresponding to the optimal Rx beam determined during synchronization.

[0140] 2. The gNB uses a selected beam to detect the preamble in the PDSCH using the Random Access Response (RAR) UL Authorization (MSG2) response. Afterwards, the UE and gNB establish a coarse beam alignment that can be used in subsequent steps.

[0141] 3. Upon receiving MSG2, the UE responds using resources scheduled by the gNB. Therefore, the gNB is aware of where to detect MSG3 and which gNB Rx beam should be used.

[0142] 4. gNB confirms the above situation by transmitting MSG4 in PDSCH using the gNB Tx beam determined in the previous step.

[0143] If two or more UEs select the same preamble, it can be decoded into a single preamble at the gNB, and then the gNB transmits its RAR for one UE. In this case, a preamble collision occurs in step three above. The UE transmits using its default power or the power recommended by the gNB. In the event of a transmission failure, the UE follows a power ramp procedure.

[0144] like Figure 7 As shown, method 700 of this disclosure uses an LBT-based process to determine unlicensed spectrum availability, included within heterogeneous bands. Depending on the configuration, one or both of the gNB and the UE can use these methods. For example, in one variant, the proposed LBT method can be used if the UE wants to perform simultaneous RACH transmissions on multiple bands. Otherwise, UL data transmission is the default use case.

[0145] According to step 702, determine, for example, the bandwidth requirements of pending requests or multiple requests.

[0146] According to step 704, the bandwidth requirement determined from step 702 is compared with the bandwidth available for gNBe (e.g., using a single carrier, or other existing methods, such as carrier aggregation within a common (non-heterogeneous) band).

[0147] According to step 706, if the bandwidth requirement exceeds the available bandwidth, then according to step 708, a multi-band (e.g., LBT-based) operation is invoked.

[0148] In a variant ( Figure 7A In step 708, step 714 first identifies the number of carriers (N) required for the bandwidth requested by the service. Next, according to step 716, two or more heterogeneous bands are identified that are ostensibly capable of serving the request (i.e., have sufficient bandwidth if available).

[0149] Finally, according to step 718, the multi-band LBT procedure is invoked on the identified band to identify at least N carriers / bands required to support the request.

[0150] In another variant ( Figure 7B In step 708, step 724 first identifies the number of carriers (N) required to serve the bandwidth requested. Next, according to step 726, two or more heterogeneous bands are identified that appear capable of serving the request (i.e., have sufficient bandwidth if available).

[0151] According to step 728, a multi-band procedure (which may or may not include LBTs for individual carriers / bands, as will be discussed) is invoked on the identified bands to identify at least N carriers / bands required to support the request. Specifically, at step 730, a carrier / band allocation is requested from the cognitive network entity relative to the specified band (e.g., for an AFC system for 6 GHz, or for a SAS / domain agent for CBRS). Incidentally, Automatic Frequency Coordination (AFC) technologies and systems are described, for example, in “Notification of Proposed Rulemaking for Unlicensed Use of the 6 GHz Band”, ET Dossier No. 18-295; GN Dossier No. 17-183, October 2, 2018 (available on [date missing]). https: / / docs.fcc.gov / public / attachments / DOC-354364Al.pdf The acquisition of frequency allocations that do not interfere with (or mitigate interference with) microwave transmitters, the entire contents of which are incorporated herein by reference. Similarly, SAS entities are used in CBRS systems to allocate quasi-licensed spectrum, such as GAA and PAL, to avoid interfering with / preempting existing users, such as DoD assets.

[0152] Therefore, current variants of the method utilize these entities to directly obtain “unimpeded” spectrum allocations without (necessarily) invoking LBTs and other protocols for channel access. In one implementation, the allocation received from the SAS / AFC (step 732) is used “blindly” without first verifying availability; that is, gNBe simply assumes the SAS / AFC is correct. Alternatively, a confirmatory LBT focused on allocation (or a wider bandwidth including allocation) is performed to verify the absence of obstruction from another user / device.

[0153] According to step 734, the LBT process, as described elsewhere in this document, scans to identify another (unassigned) band that may be used to determine the availability of one or more carriers.

[0154] Once the scan in step 734 is complete, gNBe can utilize two or more “mixed” resources (e.g., allocated spectrum and spectrum obtained by LBT) to serve the request as needed.

[0155] Regarding the LBT process, such as Figure 7C As shown in the image, Figure 7A One embodiment of step 718 of method 700 includes performing an LBT process at the gNB (e.g., gNBe 201) relative to a specified frequency band (e.g., band A and / or band B) according to step 743. For example, in one variant, a carrier-sensing, energy-detection, or correlation-based LBT mechanism (e.g., using a CAZAC sequence such as Zadoff-Chu to deterministically detect channel usage by an LTE-LAA / U device (e.g., via a P-SS synchronization signal)) or other mechanisms may be used. Preambles or other known patterns may also be used for detection.

[0156] Non-limiting examples of the scope (with A, with B) useful to exemplary embodiments of the methods described herein are:

[0157] -(5 to 5.9 GHz, 6.1 to 7.125 GHz)

[0158] -(5 to 5.9 GHz, 37 GHz)

[0159] -(5 to 5.9 GHz, 3.7 GHz)

[0160] -(5 to 5.9 GHz, 0.9 GHz)

[0161] However, it will be understood that, as discussed in more detail elsewhere herein, in accordance with this disclosure, other unlicensed bands or even “quasi-licensed” bands (e.g., CBRS bands in the 3.55 to 3.70 GHz range) may be used, containing one or all of the multi-band / carriers used for evaluation as part of the LBT process described herein.

[0162] Return again Figure 7C At step 745, the availability of frequency band A or B is determined based on the results of the LBT process. For example, if significant energy is detected in the band (e.g., compared to a specified threshold), then it can be assumed that the band is occupied.

[0163] At step 747, when the designated band is available, the gNB can transmit data and control signals on the band (or zone).

[0164] Note that the aforementioned process can be applied within the constraints of existing LBT / backoff mechanisms, applicable to the band being evaluated. As previously mentioned, these mechanisms may be heterogeneous across the two (or more) bands being evaluated, and thus, the device described herein may utilize its own specific mechanism for each different band, depending on its location within the RF spectrum (e.g., one mechanism for above 5 GHz and another for below 5 GHz; or one for 3GPP / 5G NR-U and one for CBR; or one for LTE-LAA and one for NR-U; or one for Multefire and one for NR-U, etc.). These processes may also be applied iteratively or non-iteratively (i.e., once a given carrier or band fails due to occupancy, the gNBe utilization logic may result in the evaluation of a new band (band C) to replace band A, or alternatively, band A may be re-evaluated multiple times or for a specified period before another anticipated candidate band is "abandoned").

[0165] Alternatively, as previously described, multiple carriers / bands can be evaluated in parallel via a common or single wideband scan, using a simpler single-layer approach; for example, scanning 25 carriers simultaneously, and assuming, based on, for example, historical or anecdotal usage or occupancy statistics, that at least a minimum number (N) will be “shifted” for utilization. Similarly, if the minimum N is not met, the entire wideband scan can simply be repeated, for example, after a backoff interval, until N is met (as opposed to moving to a new candidate band via the more layered approach described above).

[0166] It will also be understood that, in another embodiment, a “COTS” consistent with the enhanced gNB or a non-enhanced UE can be used, whereby the gNB effectively performs the LBT-based method described herein on behalf of the UE, and then signals are sent to the unmodified UE to share channel occupancy data (i.e., data indicating the two or more carriers or bands to be used by the UE when communicating data with the gNB), for example, via broadcast or signaling through a control channel. In one variant, the UE receives the channel occupancy data and immediately begins channel utilization. In another variant, the UE performs a simple “one-off” UL CCA (Clear Channel Assessment) for each of the bands prior to UL transmission to verify the availability of the signal carriers.

[0167] refer to Figure 8 Show and describe Figure 7 This is a specific embodiment of a general method for unlicensed channel access as described herein. Method 800 Reference Figure 2 The description in gNBe 201 is one of the descriptions, although it may be applied to other components or processes.

[0168] like Figure 8 As shown, method 800 includes performing an LBT process at step 803 first at a gNB (e.g., gNBe 201) in band A and / or band B. As described in more detail below, this step may include single, sequential, or simultaneous LBT processes for different bands of interest, including the use of heterogeneous LBT mechanisms depending on the specific properties of the band being evaluated.

[0169] At step 805, the channel parameters {a1, a2, a3, ..., aN} with band A are measured.

[0170] At step 807, gNBe compares {a1, a2, a3, ..., aN} with the threshold {ta1, ta2, ta3, ..., taN}.

[0171] At step 809, it is determined whether frequency band A is available.

[0172] At step 811, the gNB may transmit data and control signals at step 813, or return to step 805 to measure the channel parameters of the next frame.

[0173] At step 815, the channel parameters {b1, b2, b3, ..., bN} of band B are measured. At step 817, gNB compares {ta1, ta2, ta3, ..., taN} with the threshold {tbl, tb2, bt3, ..., tbN}.

[0174] At step 819, it is determined whether frequency band B is available.

[0175] At step 821, the gNB may transmit data and control signals at step 823, or return to step 815 to measure the channel parameters of the next frame.

[0176] Note that the logic of steps 805 to 813 and 815 to 823 can be executed in parallel rather than in series, as described above. Furthermore, as previously mentioned, the transmission on band A (step 813) can be paused until the results of the band B evaluation are completed at step 821.

[0177] Figure 9 yes Figure 7 Another exemplary implementation of the general method described herein. For example... Figure 9 As shown, method 900 includes first performing an LBT process relative to band A and / or band B at gNBe 201.

[0178] At step 905, for the A-band measurement, one or more of the following channel parameters are included: energy detection, channel sensing time slot, maximum backoff counter size, minimum backoff counter size, delay period, and receive beam direction. At step 907, gNBe compares these parameters with the corresponding thresholds t1l, t12, t13, t14, and t16.

[0179] In step 911, it is determined whether frequency band A is available.

[0180] At step 911, gNBe may transmit data and control signals at step 913, or return to step 905 and measure the channel parameters of the next frame.

[0181] At step 915, the Band B measurement includes one or more of the channel parameters mentioned above, such as energy detection, channel sensing time slot, backoff counter maximum size, backoff counter minimum size, delay period, and receive beam direction. As mentioned above, depending on the Band B access mechanism in place, this set of parameters (and the relative thresholds / comparisons below) may be the same as or different from the set of parameters used for Band A.

[0182] At step 917, gNBe compares these measurement parameters with the corresponding thresholds t21, t22, t23, t24, t25 and t26.

[0183] At step 919, it is determined whether frequency band B is available.

[0184] At step 919, gNBe may transmit data and control signals at step 921, or return to step 915 to measure the channel parameters of the next frame.

[0185] and Figure 8 Similarly, the logic of steps 905 to 913 and 915 to 921 can be executed in parallel and in series as described above. In addition, as previously mentioned, the transmission on band A (step 913) can be paused until the result of the band B evaluation is completed at step 919.

[0186] Figure 10 yes Figure 7 Another exemplary implementation of the general method described herein. For example... Figure 10 As shown, method 1000 includes first performing an LBT procedure on band A and / or band B at gNBe.

[0187] At step 1005, for the A-band measurement, one or more of the following channel parameters are included: energy detection, channel sensing time slot, maximum backoff counter size, minimum backoff counter size, delay period, and receive beam direction. At step 1007, gNBe compares these parameters with thresholds t11, t12, t13, t14, and t16.

[0188] At step 1009, it is determined whether frequency band A is available.

[0189] At step 1011, the gNB may transmit data and control signals at step 1011, or return to step 1005 and measure the channel parameters of the next frame.

[0190] At step 1015, one or more of the following are measured: a coordination signal, channel sensing time slot occurrence, delay period, and receive beam direction. In one embodiment, the coordination signal is broadcast by a node (e.g., a centralized network node) that dynamically allocates device-specific channel sensing and / or channel access data. The coordination signal may, for example, be used in place of or as a substitute for the asynchronous method used for band A in this embodiment, relative to band B LBT; band B will actually be predefined by the network infrastructure rather than performing energy detection, etc. For example, in one variant, the coordination signal may include a public preamble with a specific signature or pattern that unauthorized devices attempt to detect, as opposed to “normal” energy detection, similar to the preamble used in the IEEE 802.11 standard protocol.

[0191] Next, at step 1017, gNBe compares these measurement parameters with thresholds t21, t22, t23, and t24. At step 1019, it is determined whether frequency band B is available.

[0192] At step 1019, the gNB may transmit data and control signals at step 1021, or return to step 1015 to measure the channel parameters of the next frame.

[0193] and Figure 8 and 9 Similarly, the logic of steps 1005 to 1011 and 1015 to 1021 can be executed in parallel and series as described above. Furthermore, as previously mentioned, transmission on band A (step 1011) can be paused until the results of the "coordination" evaluation of band B are completed at step 1019. Additionally, the coordination signal can be used to further aggregate bands A and B, for example, for synchronization purposes. Furthermore, the coordination signal can be used by two entities (e.g., gNBe and UEe) to coordinate UL / DL transmission scheduling.

[0194] Will understand, although Figure 10 Method 1000 uses a first type of heterogeneity between band A and band B detection (e.g., a first type of LBT protocol for band A, followed by a “coordinated” LBT protocol for band B), but this disclosure considers other types of heterogeneity arrangements. For example, in one variant (not shown), the band A / B protocols may differ in their frequency range sensing / detection range (e.g., one may be wideband while the other is narrower). In another variant, the detection measurement sets and / or sequences may differ between the two (or more) bands.

[0195] For example, as a non-limiting example, the following heterogeneous "arrays" of detection parameters are used for band A and band B, respectively:

[0196] 1. LBT A: {Energy detection threshold 1 (dBm), Channel sensing time slot duration 1 (μs), Backoff counter maximum size 1 (in time slots), Backoff counter minimum size 1 (in time slots), Delay period 1 (μs), Receive beam direction 1}

[0197] 2. LBT B: {Initial signal or preamble detection threshold (dBm), energy detection threshold 2 (dBm), channel sensing time slot duration 2 (μs), backoff counter maximum size 2 (in time slots), backoff counter minimum size 2 (in time slots), delay period 2 (μs), receive beam direction 2}.

[0198] In yet another variant, the iteration or type of the backoff parameter may differ in two (or more) bands; for example, consistent with the existing mechanisms in each of the different unpermissioned bands. For instance, one band may utilize a random number-based backoff mechanism, while another may not have a backoff mechanism and instead rely on collision detection (CD) and retry-only.

[0199] Figure 11 This is an explanation of its application to the UE (e.g., as will be discussed later in this document relative to...). Figure 17 The flowchart describes an example of a general method 1100 for unlicensed channel access (i.e., an exemplary enhanced UE 203), although the method may be applied to other entities or processes, as will be recognized by one of ordinary skill in the art to which this disclosure pertains.

[0200] As shown, Figure 11 Method 1100 includes first initializing UEe 203 (e.g., when powered on), such as in the case of a completely powered-off UE and not connected to any wireless network (step 1102). According to step 1104, UEe utilizes its 5G NR-U stack or LTE stack and existing setup to “RACH” to the network (i.e., its gNBe 201). This use of existing protocols enables the UE to establish a communication channel (including a control channel) with the network, through which it can receive data and guide its further utilization of the LBT-based heterogeneous unlicensed band process described herein. Note that the initial RACK can also connect to a licensed network (e.g., the user's cellular service provider).

[0201] Next, according to step 1106, the UEe receives unlicensed LBT process parameters from the gNBe (e.g., via dedicated or broadcast RRC configuration), guiding it to switch to unlicensed heterogeneous band service. For example, the gNBe may have pending service requests to deliver data to the UEe, which has been dormant for some time and wants / prefers to do so via NR-U multiband spectrum.

[0202] Finally, according to step 1108, the UEe invokes a multi-band procedure to initiate LBT-based operation according to gNBe instructions. Specifically, in one variant, the UEe begins a multi-band LBT scan (e.g., guided by band allocation provided by gNBe on the PDCCH) to determine the availability of two or more carriers through which the UEe can establish UL / DL channels 205, 207, as previously described herein. Figure 2 As shown in the image.

[0203] like Figure 11A As shown in the example, in one variant, Figure 11The method of step 1108 includes performing an LBT procedure relative to band A and / or band B at the UE (e.g., UEe 203) according to step 1113.

[0204] At step 1115, determine whether frequency band A or B is available.

[0205] At step 1117, UEe may transmit data and control signals on frequency band A and / or B.

[0206] Figure 12 This is a flowchart illustrating another example of method 1200 for unlicensed channel access. (See reference) Figure 2 , 6A Method 1200 is described by one of UEs 203, 602 and / or 653 as described in 6B.

[0207] like Figure 12 As shown, method 1200 includes first performing an LBT procedure for frequency band A and / or B at the UE (e.g., UE 203).

[0208] At step 1205, one or more of the channel parameters {a1, a2, a3, ..., aN} are measured. At step 1207, the UE compares {a1, a2, a3, ..., aN} with the corresponding thresholds {ta1, ta2, ta3, ..., taN}.

[0209] At step 1209, it is determined whether frequency band A is available.

[0210] At step 1211, UEe may transmit data and control signals at step 1213, or return to step 1205 to measure the channel parameters of the next frame.

[0211] At step 1215, the channel parameters {b1, b2, b3, ..., bN} of band B are measured. At step 1217, the UE compares {ta1, ta2, ta3...taN} with the corresponding thresholds {tbl, tb2, bt3, ..., tbN}.

[0212] At step 1219, it is determined whether frequency band A is available.

[0213] At step 1221, UEe may transmit data and control signals at step 1223, or return to step 1215 to measure the channel parameters of the next frame.

[0214] refer to Figure 13 ,exhibit Figure 12 A specific implementation of the general method described herein.

[0215] like Figure 13As shown, method 1300 includes first performing an LBT procedure at UEe (e.g., UEe 203) for band A and / or band B.

[0216] At step 1305, for the A-band measurement, one or more of the following channel parameters are included: energy detection, channel sensing time slot, backoff counter maximum size, backoff counter minimum size, delay period, and receive beam direction. At step 1307, the UE compares these parameters with the corresponding thresholds t11, t12, t13, t14, and t16.

[0217] At step 1309, it is determined whether frequency band A is available.

[0218] At step 1311, the UE may transmit data and control signals at step 1311, or return to step 1405 to measure the channel parameters of the next frame.

[0219] At step 1315, the B-band measurement includes one or more of the following channel parameters: energy detection, channel sensing time slot, maximum backoff counter size, minimum backoff counter size, delay period, and receive beam direction. At step 1317, the UE compares these measurement parameters with the corresponding thresholds t21, t22, t23, t24, t25, and t26.

[0220] At step 1319, it is determined whether frequency band B is available.

[0221] At step 1319, the UE determines the transmission data and control signals at step 1321, or returns to step 1315 to measure the channel parameters of the next frame.

[0222] Figure 14 yes Figure 7 Another implementation scheme of the general method described herein. For example... Figure 14 As shown, method 1400 includes first performing an LBT procedure at the UEe for band A and / or band B. At step 145, for band A, the measurement includes one or more of the following channel parameters: energy detection, channel sensing time slot, maximum backoff counter size, minimum backoff counter size, delay period, and receive beam direction. At step 1407, the UEe compares these parameters with corresponding thresholds t11, t12, t13, t14, and t16.

[0223] At step 1409, it is determined whether frequency band A is available.

[0224] At step 1411, the gNB may transmit data and control signals at step 1411, or return to step 1405 and measure the channel parameters of the next frame.

[0225] At step 1415, the UEe measures one or more of the following: a coordination signal, channel sensing time slot occurrence, delay period, and receive beam direction. In one embodiment, the coordination signal is broadcast by a node (e.g., a centralized network node) that dynamically allocates device-specific channel sensing and / or channel access data. The coordination signal may, for example, be used in place of or as a substitute for the asynchronous method used for band A in this embodiment relative to band BLBT; band B will actually be predefined by the network infrastructure rather than performing energy detection, etc.

[0226] At step 1417, UEe compares the parameters of these measurements with the corresponding thresholds t21, t22, t23, and t24.

[0227] At step 1419, it is determined whether frequency band B is available.

[0228] At step 1419, UEe may transmit data and control signals at step 1421, or return to step 1415 to measure the channel parameters of the next frame.

[0229] It will become clear that, in one variant, the above discussion... Figures 12 to 14 In various embodiments, the channel access parameters referenced can be assumed by the UE (e.g., set to predefined default values ​​for initial access). Once the RRC (Radio Resource Control) connection is complete, the UE can then use the network to indicate which carrier it uses; that is, the aforementioned parameters can be configured via higher-level signaling.

[0230] Figure 14 A through 14C are ladder diagrams illustrating examples of LBT signaling procedures for DL / UL (in this case, applicable to this disclosure based on existing LBT protocols; see RAN WG1 Meeting No. 79, San Francisco, USA, April 17–21, 2014, the entire contents of which are incorporated herein by reference).

[0231] This article describes one of the gNBe devices 201. Figure 14 A and 14B. Figure 14 A describes unlicensed channel access by DL. At step 1407a of method 1400a, gNBe refers to... Figure 8 , 9 Steps 805, 815, 905, 915, 1005, and / or 1015 of method 10 perform carrier sensing. (Refer to...) Figure 8 , 9If steps 811, 821, 911, 919, 1009, and / or 1019 of method 10 are performed, and the channel is assessed to be idle at step 1409a, then the gNB schedules the UE on the PDCCH channel at step 1411a. According to step 1413a, the gNB can begin transmitting data and control signals on the PDSH channel. As may be understood, Figure 14 A represents only a portion of the process for a given band or carrier; similar logic applies to band B and other bands (if used).

[0232] UL's unlicensed channel access Figure 14 As described in B. At step 1407b of method 1400b, gNBe reference. Figure 8 , 9 Steps 805, 815, 905, 915, 1005, and / or 1015 of method 10 perform carrier sensing. (Refer to...) Figure 8 , 9 If steps 811, 821, 911, 919, 1009, and / or 1019 of method 10 assess channel idleness at step 1409b, then gNBe schedules the UE (or UEe) on the PDCCH channel at step 1411a. According to step 1413b, the UE / UEe can begin transmitting data and control signals on the PUSCH channel.

[0233] Description relative to UEe device 203 Figure 14 C, for unlicensed channel access by the UL. At step 1407c of method 1400c, the gNB schedules the UEe on the PDCCH. At step 1409c, the UEe performs carrier sensing. If the channel is assessed as idle at step 1411c, the UE may begin transmitting data and control signals on the PUSCH channel.

[0234] Service Provider Network

[0235] Figure 15 This describes a typical service provider network configuration useful for illustrating the features of the enhanced cell activation devices and methods described herein. In one embodiment of this disclosure, this service provider network 1500 is used to provide backbone and backhaul from the service provider's service nodes (e.g., HFC cables or FTTC / FTTH splitters) to different locations or venues / residences. For example, one or more standalone or embedded DOCSIS cable modems (CMs) 1512 communicate with various NR architecture components; for example, an enhanced gNB 201 comprising one or more enhanced CU (CUe) devices and / or one or more enhanced DU (DUe) devices, which include the features described above relative to... Figures 2 to 14 The multi-carrier NR-U capability described in C, as follows, is relative to... Figure 15A to 15d are described in more detail to provide bidirectional data communication to the served component. The following section also shows a more detailed description relative to... Figure 17 The types of enhanced UEs (UEe) discussed may include the multi-carrier NR-U functionality described herein in some embodiments.

[0236] In some embodiments, the service provider network 1500 also advantageously allows the aggregation and / or analysis of subscriber- or account-specific data (particularly including specific CUe or DUe or E-UTRAN eNB / femtocellular devices associated with such subscribers or accounts) as part of providing services to users according to the exemplary delivery model described herein. As just one example, device-specific IDs (e.g., gNB ID, global gNB identifier, NCGI, MAC address, etc.) may be cross-referenced with MSO subscriber data maintained, for example, at the network headend 1507, to allow or at least facilitate, in addition to, (i) user / device authentication for the MSO network; (ii) the relevance of regional, location, or place aspects of providing services to specific subscriber capabilities, demographics, or device locations, such as delivering specific location or targeted content or advertising; and (iii) determining subscription levels, and thus subscription rights and access rights to specific services (if applicable). Furthermore, the MSO may maintain device profiles for specific devices, enabling the MSO (or its automated agent processes) to model devices for wireless or other functionalities.

[0237] In short, the NG-RAN architecture uses many different identifiers, including identifiers for the UE and other network entities. Specifically:

[0238] - The AMF identifier (AMF ID) is used to identify the AMF (Access and Mobility Management Function);

[0239] - The NR Cell Global Identifier (NCGI) is used to globally identify NR cells and consists of the PLMN identity to which the cell belongs and the NR Cell Identity (NCI) of the cell;

[0240] - The gNB identifier (gNB ID) is used to identify the gNB in ​​the PLMN and is contained in its cell's NCI;

[0241] - Global gNB ID, which is used to globally identify gNBs, and consists of the PLMN identity to which the gNB belongs and the gNB ID;

[0242] - Tracking Area Identity (TAI), used to identify the tracking area, and consists of the PLMN identity to which the tracking area belongs and the TAC (Tracking Area Code) of the tracking area; and

[0243] - Single Network Slice Selection Auxiliary Information (S-NSSAI), which is used to identify network slices.

[0244] Therefore, depending on which data is useful to the MSO or its customers, the various portions of the aforementioned data can be associated with and stored in a specific gNB "client" or its components backhauled from the MSO network.

[0245] Figure 15 The MSO network architecture 1500 is particularly useful for delivering packetized content (e.g., coded digital content carried in packet or frame structures or protocols) consistent with various aspects of this disclosure. In addition to on-demand and broadcast content (e.g., live video programming), Figure 15 The system can also provide internet data and OTT (cloud-based) services to end users (including DU / DUe 1506 users) via Internet Protocol (IP) and TCP (i.e., via 5G radio bearer), although other protocols and delivery mechanisms of the types known in digital communication technologies can be replaced.

[0246] Figure 15 The network architecture 1500 typically includes one or more headends 1507 that communicate with at least one center 1517 via a ring 1537. The distribution center 1517 is capable of providing content to various "client" devices and gateway devices 1560 (if applicable) via a plug-in network infrastructure 1545. Figure 15 The inspection will reveal that each of the various gNB components (including DU / DUe and CUe) can act as a "client" device for the network. For example, in many installations, the CUe 1504 of a given gNB is physically different from or removed from the location of its component DU 1506, and therefore requires a plug-in (e.g., wired, wireless, optical) PHY bearer to transmit data between the DUe and CUe of a given gNB. In such an architecture, the CUe may be further positioned towards the core of the MSO distributed network, while the various component DUes are positioned at the edge. Alternatively, both devices can serve as backhaul services near the edge (e.g., via edge QAM or RF carrier 1540, such as...). Figure 15 (As shown in the diagram). In both cases, the MSO infrastructure can be used to backhaul data from each device and to transmit it to other components via the MSO infrastructure, just as two geographically different customers of a given MSO can transmit data within their respective locations via their respective DOCSIS modems. Each component has an IP address in the network and is therefore accessible to other components.

[0247] Alternatively, the CU / CUe device 1504 (which actually aggregates traffic from the individual components DU to the NG core 209) can have a dedicated high-bandwidth “drop”.

[0248] In addition, such as Figure 15 As illustrated by unit 201, a given CU / CUe and DU / DUe can be co-located as desired. This can also be "hybridized," for example, a component DU / DUe co-located with CU / CUe (and possibly physically integrated), while the remaining DU / DUes of the CU / CUe are geographically and physically distributed.

[0249] exist Figure 15 In the MSO network 1500, various content sources 1503, 1503a are used to provide content to content servers 1504, 1505 and source server 1521. For example, content can be received from local, regional, or network content libraries, as discussed in commonly owned U.S. Patent No. 8,997,136, entitled “Apparatus and Methods for Packetized Content Delivery Over a Bandwidth-Efficient Network,” the entire contents of which are incorporated herein by reference. Alternatively, content can be received from linear analog or digital feeds and third-party content sources. Internet content source 1503a (e.g., a web server) provides Internet content to packetized content source server 1521. Other IP content, such as Voice over IP (VoIP) and / or IPTV content, can also be received at source server 1521. Content can also be received from subscriber and non-subscriber devices (e.g., PCs or user-generated videos originating from smartphones).

[0250] Figure 15 The network architecture 1500 may further include a conventional multiplexer / encryptor / modulator (MEM; not shown). In this context, content server 1504 and packet-switched content server 1521 may be coupled via LAN to headend switching device 1522, such as an 802.3z Gigabit Ethernet (or "10G") device. For downstream delivery via MSO infrastructure (i.e., QAM), video and audio content is multiplexed at headend 1507 and transmitted via loop 1537 to edge switching device 1538 (which may also include an 802.3z Gigabit Ethernet device).

[0251] In an exemplary content delivery paradigm, MPEG-based video content (e.g., MPEG-2, H.264 / AVC, or H.265 / HEVC) can be delivered to a user IP-based client device via associated physical transport (e.g., a DOCSIS channel for a corresponding DU / DUe 1506 and a 5G NR bearer); this is MPEG-over-IP-over-MPEG. Specifically, higher-level MPEG or other encoded content can be encapsulated using IP network layer protocols, which then utilize MPEG packetization / container formats of types well-known in the art for delivery via RF channels or other transports (e.g., via multiplexed delivery streams (MPTS)). Delivery in such packetization modes can be unicast, multicast, or broadcast.

[0252] For example Figure 15 Individual devices of the cable modem 1512 and associated gNB device 201 in the implementation scheme can be configured to monitor specifically allocated RF channels (e.g., via port or socket ID / address, or other such mechanisms) for IP packets of the gNB / user location / address used for their services. IP packets associated with Internet services are received by an edge switch and forwarded to the cable modem terminal system (CMTS) 1539. The CMTS inspects the packets and forwards packets for the local network to the edge switch. Other packets are dropped or routed to another component in one variant.

[0253] The edge switch forwards packets received from the CMTS to the QAM modulator, which then transmits the packets to the "client" gNB device via one or more physical (QAM modulated RF) channels. IP packets are typically transmitted on RF channels that are different from the "in-band" RF channels used for broadcasting video and audio programs.

[0254] In one implementation scheme Figure 15 The CM 1512 shown in the document serves venues or locations such as conference centers, apartment buildings, corporate or hotel structures (e.g., hotels), which include one or more DU / DUe nodes for providing 5G NR services, and may also serve WLAN (e.g., 802.11-2016 compliant Wi-Fi) nodes for WLAN access (e.g., within the 2.4GHz ISM band), or even E-UTRAN femtocells, CBRS (Citizens Broadband Radio Service) nodes or other such devices.

[0255] In parallel (or alternatively) to the aforementioned delivery mechanism, the MSO backbone 1531 and other network components can be used to deliver packetized content to “client” gNB devices via non-MSO networks. For example, so-called “OTT” content (whether tightly coupled or otherwise) can be received, stored in the MSO’s network infrastructure, and delivered via a plug-in service provider network (which may include the public Internet) 1511 to the gNB CU / CUe 1504. (For example, in a local coffee shop, by connecting to the coffee shop service provider’s DU / DUe via a modem, the user’s IP-enabled end-user device uses an Internet browser or an MSO / third-party application to stream the content via the MSO backbone 1531 to the third-party network, the service provider’s modem (or optical demodulator), and the DU / DUe using an HTTP-based method, and then streams the content to the user device via the DU / DUe NR wireless interface.)

[0256] It will be further recognized that user plane data / services can also be routed and delivered outside of the CU / CUe. In one implementation (described above), the CU / CUe carries both RRC (Control Plane) and PDCP (User Plane); however, as an alternative embodiment, a so-called "de-converged" CU / CUe can be utilized, where the CU / CUeCP entity (i.e., the CU / CUe-Control Plane) carries only RRC-related functions, and the CU / CUe UP (CU / CUe-User Plane) is configured to carry only PDCP / SDAP (User Plane) functions. In a variant, the CU / CUe-CP and CU / CUe-UP entities can connect data and inter-process communication via an E1 data interface, but other communication methods may also be used. It will also be understood that the CU / CUe-CP and CU / CUe-UP can be controlled and / or operated by different entities; for example, one service provider or network operator maintains awareness / control of the CU / CUe-UP, and another maintains awareness / control of the CU / CUe-CP, and the operation of both is coordinated according to one or more prescribed operational or service policies or rules.

[0257] In some embodiments, each DU / DUe is located and / or serves one or more areas within one or more venues or residences (e.g., buildings, rooms, or plazas for commercial, business, or academic purposes, and / or any other space suitable for wireless access). Each DU / DUe is configured to provide wireless network coverage for its RAT (e.g., 5G NR) within its coverage or connectivity range. For example, a venue may install a wireless NR modem (DU / DUe) at its entrance for potential customers to connect, including those in the parking lot, particularly via its NR or LTE-enabled vehicles or their operator's personal devices. Notably, different categories of DU / DUe 1506 can be used.

[0258] gNB architecture

[0259] Now for reference Figure 15 A through 15D describe various embodiments of the distributed (CU / DU)gNB architecture according to this disclosure.

[0260] In short, and refer to Figure 15 A. The existing gNB shown (see Figure 1 discussed above) includes a CU 104 (also referred to as gNB CU), which is a logical node within the NR architecture that communicates with the NG core 109 and includes gNB functions such as user data delivery, session management, mobility control, RAN sharing, and location; however, according to various "partitioning" options described in more detail below, other functions are specifically assigned to DU 106 (also referred to as gNB-DU). CU 104 transmits user data and controls the operation of DU 106 via corresponding front-end (Fs) user plane and control plane interfaces 108, 110.

[0261] Fs interfaces 108 and 110 contain the (standardized) F1 interface. The F1 interface provides a mechanism for interconnecting gNB-CU 104 and gNB-DU 106 of gNB 101 within the NG-RAN, or for interconnecting gNB-CU and gNB-DU of en-gNB within the E-UTRAN. The F1 Application Protocol (F1AP) supports the functionality of the F1 interface through signaling procedures defined in 3GPP TS 38.473. F1AP consists of so-called “Essential Procedures” (EPs). EPs are the units of interaction between gNB-CUs and gNB-DUs. These EPs are individually defined and designed to establish complete message sequences in a flexible manner. Generally, unless otherwise stated, EPs can be invoked independently as independent procedures, and these independent procedures can be activated in parallel.

[0262] In this architecture, the gNB-DU 106 (or ngeNB-DU) is under the control of a single gNB-CU 104. When the gNB-DU starts up (including power-on), it executes the F1 SETUP procedure (typically modeled after the LTE S1 SETUP procedure) to specifically inform the gNB-CU controlling the number of cells in the F1 SETUP REQUEST message (and the identity of each particular cell). The gNB-CU can independently choose to activate some or all of the cells supported by the gNB-DU, and even change certain operating parameters associated with them, as indicated in the F1 SETUP RESPONSE message. The identity of each cell to be activated is also included in the F1 SETUP RESPONSE.

[0263] Against this backdrop, an exemplary configuration of the NR-U gNB 201 of this disclosure, as previously described, is presented and discussed in detail. For example... Figure 15B As shown, the first architecture includes a gNB201 with an enhanced CU (CUe) 1504 and multiple enhanced DU (DUe) 1506. These enhanced entities include corresponding software or firmware components (i.e., LBTs respectively). CU and LBT DU Modules 503a and 503b) and are capable of allowing multi-carrier utilization (including, for example, aggregation), either autonomously or under the control of another logical entity (e.g., the NG core 209 or its components with which the gNB communicates).

[0264] Figure 15B Individual DUe 1506 communicates data and transmits messages with CUe 1504 via a plug-in physical communication interface 1508 and a logical interface 1510. As previously described, such interfaces may include a user plane and a control plane and are embodied in a defined protocol (e.g., FIAP). Note that in this embodiment, one CUe 1504 is associated with one or more DUe 1506, and a given DUe is associated with only a single CUe. Similarly, a single CUe 1504 communicates with a single NG core 209, such as an NG core 209 operated by an MNO or MSO. Each NG core 209 may have multiple gNBs 201 associated with it.

[0265] exist Figure 15C In this architecture, two or more gNBs 201a to n communicate with each other via, for example, the Xn interface 1507, and accordingly, at least CUe-to-CUe data transfer and communication are possible. Separate NG cores 209a to n are used for network control and user plane (and other) functions. Note that two gNBs in their LBT / NR-U enhanced configurations may be heterogeneous, as shown; for example, in one gNB, only the CUe contains the LBT software / firmware upgrade 503, while in another gNB, both the CUe and DUe components contain the LBT software / firmware 503 (and they communicate with each other).

[0266] exist Figure 15DIn this architecture, two or more gNBs 201a to n communicate with each other via, for example, an Xn interface 1507, and accordingly, at least CUe-to-CUe data transfer and communication are possible. Furthermore, individual NG cores 209a to n are logically “cross-connected” to one or more other NG cores of gNBs 201, allowing one core to utilize / control the infrastructure of another, and vice versa. This can be in a “daisy-chain” manner (i.e., one gNB communicates with another NG core other than itself, and an NG core communicates with another gNB 201 other than itself, etc.), or gNBs 201 and NG cores 209 can form a “mesh” topology, where multiple cores 209 communicate with multiple gNBs or multiple different entities (e.g., service providers). However, other topologies will be recognized by those skilled in the art in light of this disclosure. This cross-connection method is particularly advantageous in allowing infrastructure sharing between two MNOs / MSOs, which is especially useful in, for example, densely deployed environments where multiple sets of RAN infrastructure may not be supported.

[0267] like Figure 15D As shown, a 5GC 209 contains an LBT NR-U software procedure 503c, which logically communicates with the LBT procedure on the corresponding gNB CUe. It can also communicate with the aforementioned external entities, such as AFC and / or CBRSDP / SAS 1560 (if present) (and is relevant to the band of interest).

[0268] It will also be understood that, although mainly relative to, Figures 15B to 15D The single gNB-CU entity or device 201 shown herein is described, but this disclosure is not limited to such an architecture. For example, the techniques described herein may be implemented as part of a distributed or de-aggregated or distributed CU entity (e.g., one in which the user plane and control plane functions of the CU are de-aggregated or distributed across two or more entities, such as CU-C (control) and CU-U (user)), and / or employ other functional partitioning.

[0269] It should also be noted that the heterogeneous architecture of eNB or femtocells (i.e., E-UTRAN LTE / LTE-A node B or base station) and gNB can be combined with... Figures 15B to 15D The architecture is consistently utilized. For example, a given DUE can act as (i) a standalone Due (i.e., a 5G 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) not be physically co-located with an eNB or femtocell but still provide NR coverage within the macrocell coverage area.

[0270] In the 5G NR model, DU 1506 includes logical nodes, each of which may contain a different subset of gNB functions, depending on the function splitting options. DU operation is controlled by CU 1504 (and ultimately by NG core 209 for certain functions). The splitting options between DUe and CUe in this disclosure may include, for example:

[0271] Option 1 (RRC / PCDP split)

[0272] Option 2 (PDCP / RLC split)

[0273] Option 3 (Split within RLC)

[0274] Option 4 (RLC-MAC split)

[0275] Option 5 (Intra-MAC Splitting)

[0276] Option 6 (MAC-PHY split)

[0277] Option 7 (PHY internal split)

[0278] Option 8 (PHY-RF splitting)

[0279] According to Option 1 (RRC / PDCP split), RRC (Radio Resource Control) is in CUe 204, while PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC, physical layer (PHY) and RF remain in DUe, thus maintaining the entire user plane in the distributed unit.

[0280] According to option 2 (PDCP / RLC split), there are two possible variations: (i) RRC and PDCP remain in CUE, while RLC, MAC, physical layer and RF are in DUe 1506; and (ii) RRC and PDCP are in CUE (with split user plane and control plane stack), while RLC, MAC, physical layer and RF are in DUe 1506.

[0281] According to option 3 (split within RLC), two splits are possible: (i) ARQ-based split; and (ii) split based on TXRLC and RX RLC.

[0282] According to option 4 (RLC-MAC split), RRC, PDCP, and RLC remain in CUe 1504, while MAC, physical layer, and RF remain in DUE.

[0283] According to option 5 (MAC splitting), the lower part of the RF, physical layer and MAC layer (low MAC) is in DUe 1506, while the higher part of the MAC layer (high MAC), RLC and PDCP are in CUe 1504.

[0284] According to option 6 (MAC-PHY split), the MAC and upper layers reside in the CUE, while the PHY layer and RF reside in the DUE 1506. The interface between the CUE and DUE carries data, configuration and scheduling-related information (such as modulation and coding schemes or MCS, layer mapping, beamforming and antenna configuration, radio and resource block allocation, etc.) and measurements.

[0285] Depending on option 7 (PHY Intra-Splitting), different sub-options for UL (Uplink) and DL (Downlink) may appear independently. For example, in UL, FFT (Fast Fourier Transform) and CP removal may reside in DUE 1506, while the remaining functionality resides in CUe 1504. In DL, iFFT and CP addition may reside in DUE 1506, while the rest of the PHY resides in CUe 1504.

[0286] Finally, according to option 8 (PHY-RF split), the RF and PHY layers can be separated to allow for centralized processing at all protocol layer levels, thereby enabling a high degree of RAN coordination. This allows for optimized support for features such as CoMP, MIMO, load balancing, and mobility.

[0287] The aforementioned splitting options are designed to enable flexible hardware implementations, allowing for scalable and cost-effective solutions, as well as coordination in performance characteristics, load management, and real-time performance optimization. Furthermore, configurable functional splitting can dynamically adapt to various use cases and operational scenarios. Factors to consider when determining how / when to implement such options may include: (i) the QoS requirements of the services provided (e.g., low latency, high throughput); (ii) the user density and load requirements for supporting specific geographic areas (which may affect RAN coordination); (iii) the availability of transport and backhaul networks with different performance levels; (iv) the application type (e.g., real-time or non-real-time); and (v) the functional requirements at the radio network layer (e.g., carrier aggregation).

[0288] gNBe devices -

[0289] Figure 16 A block diagram illustrating an exemplary embodiment of an NR-U-enabled gNB-DU (i.e., DUe 1506) device useful for operation according to this disclosure.

[0290] In one exemplary embodiment, as shown, gNB DUe (which may, for example, employ...) Figures 15B to 15DAny form shown herein, including integrated CU / CUe 1504 and DUe 1506, distributed CU / DU, etc., particularly includes a processor device or subsystem 1611, a program memory module 1607, logic 1609 (implemented herein as software or firmware executable on processor 1611), a local database 1613, and a wireless interface 1603 for communicating with the associated UE or UEe (e.g., 4G / 4.5G E-UTRAN and 5G-NR RAN, respectively).

[0291] The 5G RF interface 1603 can be configured to conform to the relevant PHY according to the relevant 3GPP NR standard it supports (e.g., NR-U). The radio antenna 1619 of the gNB can include multiple spatially distinct individual elements in, for example, a MIMO or MISO type configuration, enabling spatial diversity of the received signal. Furthermore, a phased array or similar arrangement can be used for spatial resolution within the environment, for example based on the time delay associated with the signal received by the respective elements.

[0292] In one embodiment, processor device 1611 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or processing components mounted on one or more substrates. Processor device 1611 may also include internal cache memory and modem 1615. Additionally, DUe includes those previously mentioned herein relative to... Figures 5A to 5B The LBT module 503 is of the type described. In one instance, the LBT module can be used in any DUe1506 (and / or Figures 15B to 15D The implementation in the CUe is as software or firmware stored on the storage device and executed on the processor 1611.

[0293] Processing subsystem 1611 communicates with a program memory module or subsystem 1607, the latter of which may include memory, such as SRAM, flash memory, and / or SDRAM (e.g., GDDR5 or GDDR6) components. Memory module 1607 may implement one or more of direct memory access (DMA) type hardware to facilitate data access well known in the art. The memory module of an exemplary embodiment contains one or more computer-executable instructions executable by processor device 1611. Mass storage devices (e.g., HDDs or SSDs, or NAND / NOR flash memory, etc.) are also provided, as shown.

[0294] Processor device 1611 is configured to execute at least one computer program stored in memory 1607 (e.g., according to this document). Figures 7 to 10 The method involves the logic of the LBT module (in the form of software or firmware that implements various functions). Other embodiments may implement such functionality within dedicated hardware, logic, and / or a dedicated coprocessor (not shown).

[0295] In some embodiments, logic 1609 also utilizes memory 1607 or other storage device 1613, which is configured to temporarily and / or locally store data related to various associations with the various UEs / UEe 203 serving under the NR-U standard. In other embodiments, application programming interfaces (APIs) may also reside in an internal cache or other memory 1607. Such APIs may contain public network protocols or programming languages ​​configured to support communication with other network entities (e.g., via API “calls” to or from NG core 209).

[0296] UEe devices -

[0297] Figure 17 A block diagram illustrating an exemplary embodiment of an enhanced UE (UEe) device 203 useful for operation according to this disclosure.

[0298] In one exemplary embodiment, as shown, UEe 203 specifically includes a processor device or subsystem 1711, a program memory module 1707, UE LBT logic 503 (implemented herein as software or firmware executable on processor 1702), and a radio interface 1703 for communicating with an associated RAN (e.g., 5G-NR RAN). Each of the RF interfaces 1703 is configured to conform to the associated PHY standard it supports. The antenna 1719 of the UEe radio may include multiple spatially distinct individual elements in, for example, a MIMO or MISO type configuration, allowing spatial diversity of the received signal to be utilized. Furthermore, a phased array or similar arrangement may be used for spatial resolution within the environment, for example based on the time delay associated with the signal received by the respective element.

[0299] In one embodiment, processor device 1711 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or processing components mounted on one or more substrates. Processor device 1711 may also include internal cache memory and modem 1715. As indicated, UEe includes an LBT module 503 on program memory communicating with the processing subsystem, wherein the former may include memory, which may include, for example, SRAM, flash memory, and / or SDRAM components. Memory module 1707 may implement one or more of direct memory access (DMA) type hardware to facilitate data access well known in the art. The memory module of the exemplary embodiment contains one or more computer-executable instructions executable by processor device 1711. Mass storage devices (e.g., HDDs or SSDs, or NAND / NOR flash memory, etc., e.g., via eMCC) are also provided, as shown.

[0300] Other embodiments may implement LBT functionality within dedicated hardware, logic, and / or a dedicated coprocessor (not shown).

[0301] As mentioned, UE 203 may include LBT module 503, which is configured to determine the availability of unlicensed frequency bands A and B. In one embodiment, the LBT module measures channel parameters in the unlicensed spectrum to determine the availability of the unlicensed frequency band. The LBT logic communicates with modem 1715 (via its execution on a processor) regarding the availability of the unlicensed spectrum. Modem 1715 processes baseband control and data signals for transmission and reception in RF front-end module 1703.

[0302] In some embodiments, the UEe also utilizes memory 1707 or other storage device 1721, configured to temporarily store data associated with various networks and for use in various services / applications (e.g., voice, etc.) to implement the various functions described herein. In other embodiments, application programming interfaces (APIs), such as those included in applications provided by the MSO or those natively available in use, may also reside in an internal cache or other memory 1707. Such APIs may contain public network protocols or programming languages ​​configured to interact with the UE. e 203 and other network entity communications (e.g., via API "calls" to the UE by the MSO network process responsible for NR-U carrier management). e )

[0303] Incidentally, the downloadable application or "app" may be available to subscribers of the MSO or cable network (and / or the general public, including MSO "partner" MNO subscribers), wherein the app allows users to configure their UE via a UI. e This is to implement enhanced functionality, including data collection and reporting to the MSO core network, in order to address roaming, congestion, or other issues discussed above. Figures 11 to 14 The C approach may be useful for other attributes, particularly enabling NR-U carrier availability. The application programming interface (API) can be included in applications provided by the MSO, installed along with other proprietary software pre-packaged by the UE. Alternatively, the relevant MNO can provide its subscribers with the aforementioned functionality (e.g., as a distributed UE). e Preloaded applications on the device (or downloaded later), or as a preloaded application for the UE. e Stacked OTA firmware updates.

[0304] It will be appreciated that while certain aspects of this disclosure are described with respect to a specific sequence of steps of the method, these descriptions are merely illustrative of the broader method of this disclosure and may be modified to suit the requirements of a particular application. In some cases, certain steps may become unnecessary or optional. Furthermore, certain steps or functionality may be added to the disclosed embodiments, or the order of execution of two or more steps may be interchanged. All such changes are considered to be covered by the disclosure and claims herein.

[0305] While the foregoing detailed description has shown, described, and pointed out novel features of this disclosure applicable to various embodiments, it will be understood that those skilled in the art may make various omissions, substitutions, and changes to the form and details of the described apparatus or process without departing from this disclosure. This description is not intended to be limiting, but should be regarded as an illustration of the general principles of this disclosure. The scope of this disclosure should be determined with reference to the claims.

[0306] It will be further understood that while some steps and aspects of the various methods and apparatuses described herein can be performed by humans, the disclosed aspects and individual methods and apparatuses are typically computerized / computer-implemented. Computerized apparatuses and methods are necessary for the full implementation of these aspects for a variety of reasons, including (but not limited to) commercial viability, practicality, and even feasibility (i.e., certain steps / processes simply cannot be performed by humans in any feasible manner).

Claims

1. A method for operating a wireless network having at least one wireless access node, the method comprising: Using a first carrier within a first unlicensed frequency band, for transmitting at least a first portion of user data between the at least one wireless access node and a wireless user equipment; and Simultaneously, a second carrier within a second unlicensed frequency band is used to transmit at least a second portion of the user data between the at least one wireless access node and the wireless user equipment; in: The first and second unlicensed frequency bands utilize heterogeneous carrier access mechanisms; Using the first carrier and simultaneously using the second carrier includes using different mechanisms in the heterogeneous carrier access mechanism to access at least each of the first and second carriers. Using the corresponding different mechanisms in the heterogeneous carrier access mechanism to access at least each of the first and second carriers includes using correspondingly different first and second listen-before-speak (LBT) processes on the first and second carriers; and At least one of the first and second LBT-based processes includes utilizing a plurality of channel sensing parameters, which are predefined default values ​​for initial access.

2. The method according to claim 1, wherein: The at least one wireless access node includes an NR (New Radio) compatible distributed unit (DU); and The simultaneous use of transmissions including at least a first portion and a second portion of the user data coordinated with the wireless user device.

3. The method of claim 1, wherein using the first carrier and simultaneously using the second carrier comprises scanning at least each of the first and second carriers using correspondingly different scanning mechanisms from a plurality of scanning mechanisms; The step of scanning at least one of the first and second carriers using the respective different scanning mechanisms of the plurality of scanning mechanisms includes: (i) Scan at least the first and second frequency bands including the first and second carriers, and each band including a plurality of other carriers; and (ii) Select at least the first and second carriers from a plurality of other carriers corresponding to the first and second carriers for the use.

4. The method of claim 3, wherein selecting at least the first and second carriers from a plurality of other carriers corresponding to the first and second carriers for the utilization comprises: (i) Select the first carrier and at least one other carrier within the first frequency band; (ii) Select the second carrier and at least one other carrier within the second frequency band; (iii) Aggregate (a) the first carrier and the at least one other carrier in the first frequency band with (b) the second carrier and the at least one other carrier in the second frequency band; and The use of the first carrier and the use of the second carrier include the use of the aggregation.

5. The method of claim 1, wherein using the first carrier while simultaneously using the second carrier comprises transmitting at least one of 3GPP Physical Downlink Control Channel (PDCCH) control data or Physical Downlink Shared Channel (PDSCH) user plane data on each of the first carrier and the second carrier.

6. A wireless access node for use in a wireless infrastructure, said at least one wireless access node comprising: Digital processing equipment; At least one data network interface for data communication with the digital processing device; and A storage device that communicates with the digital processing device, the storage device including a storage medium having at least one computer program configured to, when executed on the digital processing device, cause the at least one wireless access node to: Using a first carrier within a first unlicensed frequency band to transmit at least a first portion of user data between at least one wireless access node and a wireless user equipment; and Simultaneously, a second carrier within a second unlicensed frequency band is used to transmit at least a second portion of the user data between the at least one wireless access node and the wireless user equipment; in: The first and second unlicensed frequency bands utilize heterogeneous carrier access mechanisms; Simultaneous use of the first carrier and the second carrier includes accessing at least each of the first and second carriers by using corresponding different mechanisms in the heterogeneous carrier access mechanism; Accessing at least each of the first and second carriers through the respective different mechanisms in the heterogeneous carrier access mechanism includes using correspondingly different first and second listen-before-speak (LBT) processes on the first and second carriers; and At least one of the first and second LBT-based processes includes utilizing a plurality of channel sensing parameters, which are predefined default values ​​for initial access.

7. The at least one wireless access node of claim 6, wherein using the first carrier and the second carrier simultaneously includes using both the first and second unlicensed frequency bands simultaneously, and using both the first and second unlicensed frequency bands simultaneously includes using the first unlicensed frequency band independently of using the second unlicensed frequency band to transact data with public user facilities.

8. The at least one wireless access node according to claim 6, wherein the at least one wireless access node includes a gNodeB supporting 5G NR-U (Unlicensed New Radio), and the first and second unlicensed frequency bands respectively include the 5GHz band and the 6GHz band.

9. The at least one wireless access node according to claim 6, wherein the different mechanisms using the heterogeneous carrier access mechanism include using a first media access protocol including an energy detection protocol and a second media access protocol including a preamble detection protocol.

10. At least one wireless access node according to claim 9, wherein the preamble detection protocol affects the second unlicensed frequency band through a predefined managed network infrastructure.

11. The at least one wireless access node of claim 9, wherein the utilization of the second media access protocol includes the use of a coordination signal, the coordination signal including a common preamble having a signature or pattern configured to be detected by means of unlicensed spectrum.

12. The at least one wireless access node according to claim 11, wherein the coordination signal is broadcast by a network node device.

13. The at least one wireless access node according to claim 11, wherein the coordination signal is broadcast by a node that dynamically allocates at least one of (i) device-specific channel sensing or (ii) channel access data.

14. The at least one wireless access node according to claim 9, wherein: The use of the second media access protocol includes the use of coordination signals allocated by a network that does not require power detection; and The coordination signal, distributed via the network, is used to synchronize the second unlicensed frequency band with the first unlicensed frequency band.

Images