CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application serial number 63/073,089, filed on 01-SEP-2020, and of U.S. Provisional Application serial number 63/187,506, filed on 12-MAY-2021, each of which is incorporated in its entirety by this reference.

TECHNICAL FIELD

[0002] This invention relates generally to the radio repeater field, and more specifically to a new and useful system and method for repeater time-division duplexing (TDD) synchronization in the radio repeater field.

BACKGROUND

[0003] Cellular repeaters can help improve signal quality for areas not well covered by cellular basestations. Many cellular networks use time-division duplexing (TDD) to split transmission times between base station to the user and user to the base station. For repeaters deployed in such networks, there can be many benefits to having the repeater synchronize to the TDD timing of the network, such as reduced hardware cost, better performance, and/or lower noise injection in the network.

[0004] Typical TDD synchronization requires either the use of an external control signal provided to a repeater (e.g., providing a synchronization signal), or implementation of real-time modem functionality at the repeater (e.g., enabling the repeater to determine synchronization information in the same manner as endpoints of the network). However, it may not be practical to provide an external control signal to some repeaters, and realtime model functionality will typically increase repeater costs, such as by requiring the use of expensive dedicated hardware. Thus, there is a need in the radio repeater field to create a new and useful system and method for repeater TDD synchronization. BRIEF DESCRIPTION OF THE FIGURES

[0005] FIGURES 1A-1B are schematic representations of a first and second embodiment, respectively, of a repeater system.

[0006] FIGURE 1C is a schematic representation of an embodiment of a communication network including the repeater system.

[0007] FIGURE 2 is a schematic representation of an embodiment of a method for repeater operation.

[0008] FIGURES 3A-3C are schematic representations of an example of operating in a downlink mode, an uplink mode, and a downlink receive-only mode, respectively.

[0009] FIGURE 4 is a schematic representation of an embodiment of determining synchronization information.

[0010] FIGURE 5A is a schematic representation of an example of a communication network transmission pattern.

[0011] FIGURE 5B is a schematic representation of an example of a synchronization signal block of a communication network.

[0012] FIGURE 6 is a schematic representation of an example of determining a repeater operation schedule.

[0013] FIGURES 7A-7B and 8A-8B are schematic representations of various examples of maintaining synchronization.

[0014] FIGURES 9A-9B are schematic representations of signals in the first and second embodiments, respectively, of the repeater system.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The following description of the preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.

1. Overview.

[0016] A repeater system 10 preferably includes one or more radio transceivers and a signal processor (e.g., as shown in FIGURES 1A-1B), or optionally multiple signal processors. In examples, the radio transceiver can be a 5G NR transceiver (e.g., configured to communicate with other elements of a 5G NR communication network, such as user equipment (UE) and/or base stations (gNBs), and/or otherwise configured to participate in 5G NR networking), such as a mmWave (e.g., 5G Frequency Range 2 (FR2)) and/or longer wavelength (e.g., Sub-6 GHz, such as 5G Frequency Range 1 (FRi)) transceiver, but can additionally or alternatively be any other suitable radio transceiver. In some examples, the radio transceiver can include a phased array of transmission elements (e.g., enabling beamforming), but can additionally or alternatively include a single transmission element, a plurality of transmission elements in any other suitable arrangement, and/ or include any other suitable elements. However, the system 10 can additionally or alternatively include any suitable transmitter(s) and/or receiver(s), and/or any other suitable elements. The signal processor (e.g., in cooperation with the radio transceiver and/or any other suitable elements of the system) is preferably configured to perform the method 20 described below, but can additionally or alternatively be any other suitable signal processor. The repeater system 10 is preferably configured to participate in a communication network, such as a network including one or more UEs and base stations (e.g., as shown in FIGURE 1C)

[0017] In a first embodiment (e.g., as shown in FIGURE 9A), in which the system 10 includes a single radio transceiver, the transceiver can receive and re-radiate uplink and/or downlink signals, can pass some or all downlink signals to the signal processor (e.g., which processes the digitized signals such as described below regarding the method 20), and/or can receive control signals (e.g., TDD control signals) from the signal processor, such as described in more detail below regarding the method 20.

[0018] In a second embodiment (e.g., as shown in FIGURE 9B), in which the system 10 includes two radio transceivers, the first transceiver can receive downlink signals and pass them to the signal processor (e.g., as digital signals), and the signal processor can pass these downlink signals on to the second transceiver to be re-radiated and/or can process the digitized signals (e.g., such as described below regarding the method 20). Similarly, the second transceiver can receive uplink signals and pass them to the first transceiver (e.g., passed via the signal processor, preferably as digital signals; passed directly to the first transceiver, preferably as analog signals; etc.) to be re-radiated. Further, in this embodiment, the signal processor preferably provides control signals (e.g., TDD control signals) to both transceivers (or alternatively, to only one of the transceivers), such as described in more detail below regarding the method 20.

[0019] However, the system 10 can additionally or alternatively be configured to implement the method 20 in any other suitable manner.

[0020] A method 20 for repeater operation preferably includes determining synchronization information S200, operating in a synchronized repeater mode S300, and maintaining synchronization S400 (e.g., as shown in FIGURE 2), and can optionally include operating in a fallback repeater mode Sioo. The method preferably functions to enable use of one or more repeaters in a communication network employing time-division duplexing (TDD), such as a 5G NR communication network which preferably includes one or more UEs and gNBs. However, the method can additionally or alternatively include any other suitable elements performed in any suitable manner. The method 20 is preferably performed using the repeater system 10 described herein, but can additionally or alternatively be performed using any other suitable systems.

[0021] Embodiments of the repeater system and/ or method for repeater operation can confer several potential benefits. For example, embodiments of the system and/ or method can achieve and maintain TDD synchronization within a communications network (e.g., 5G NR network), without the use of a modem. In some embodiments, the system and/or method can enable semi-offline processing (e.g., in embedded software) to achieve and/or maintain TDD synchronization, rather than relying on dedicated modem hardware, thereby reducing the cost and/or complexity of the system. However, the system and/ or method can additionally or alternatively confer any other suitable benefits.

2. Method.

2.1 Operating in a fallback repeater mode.

[0022] Operating in a fallback repeater mode Sioo can function to provide a subset of repeater functionality while synchronization (e.g., TDD synchronization) is unavailable (e.g., not yet achieved). [0023] While performing Sioo, the repeater preferably operates in one or more receive-only modes in which it can receive, but does not repeat, transmissions from a base station (e.g., gNB) and/or one or more UEs; more preferably operating in a downlink receive-only mode in which transmissions are received from the base station (and not the UEs) such as shown by way of example in FIGURE 3C, but additionally or alternatively operating in an uplink receive-only mode in which transmissions are received from one or more UEs (and not the base station), a universal receive-only mode in which transmissions can be received from any suitable entities (e.g., both the base station and one or more UEs), and/or any other suitable receive-only mode.

[0024] However, the repeater can additionally or alternatively operate in repeating mode while performing Sioo. In a first embodiment, the repeating mode is a downlink- only mode, in which the repeater receives transmissions from the base station and repeats the received transmissions (e.g., to one or more devices, such as user equipment), such as shown by way of example in FIGURE 3A. For example, the repeater can amplify and reradiate the received transmissions (e.g., re-radiate with beamforming, such as directed toward one or more UEs). In alternate embodiments, the repeating mode can be an uplink only mode (e.g., receiving transmissions from one or more UEs and repeating the received transmissions to the base station), or can switch between uplink and downlink modes in any suitable manner. However, the repeater can additionally or alternatively operate in any other suitable manner while performing Sioo.

[0025] Sioo is preferably performed before TDD synchronization is achieved (e.g., while determining or attempting to determine synchronization information, such as described below regarding S200), but can additionally or alternatively be performed after losing synchronization (e.g., while attempting to reestablish synchronization) and/or with any other suitable timing. However, Sioo can additionally or alternatively include performing any other suitable fallback functions in any suitable manner.

2.2 Determining synchronization information.

[0026] Determining synchronization information S200 preferably functions to determine timing of uplink and/ or downlink windows in use by a base station. [0027] The synchronization information is preferably determined as is typical for 5G modem operation, such as by receiving one or more transmissions S210 (e.g., from a base station), detecting one or more synchronization signal blocks (SSBs) S220, selecting one or more of the received SSBs S230, decoding SSB information S240, and/or determining a TDD pattern S250, such as shown by way of example in FIGURE 4.

[0028] S210 preferably includes receiving one or more transmissions via a communication network, such as transmissions received from a base station (e.g., gNB) of the communication network (e.g., transmissions received during one or more downlink windows of the network, such as shown by way of example in FIGURE 5A). Upon receipt of a transmission from a base station (and/ or at any other suitable time), the received transmission is preferably stored, more preferably stored along with a timestamp (e.g., internal timestamp from a local repeater clock) such as a receipt timestamp.

[0029] In 5G NR networks, an SSB typically occupies a small subset of carriers (e.g., occupying 240 carriers out of more than 800 carriers per channel), thus mapping to a small frequency footprint, such as shown by way of example in FIGURE 5B. Further, S200 can typically be performed using any one carrier’s SSB in a carrier-aggregated signal. Accordingly, receiving the transmission S210 can include receiving and/or storing a subset of carriers (or alternatively, can include receiving and/or storing all carriers). For example, for 400MHz bandwidth with 4 carriers (e.g., four 100MHz channels), the SSB from only one of the channels is needed, which would occupy between 30.72MHz to 61.44MHz (a small fraction of the total 400MHz signal bandwidth). Thus, in this example, S210 can include capturing a downconverted and/or downsampled waveform (e.g., with 30.72MHz sampling rate for the 120kHz SSB or 61.44MHz sampling rate for the 240kHz SSB), preferably along with a timestamp (e.g., internal timestamp). In a second example, for 100MHz bandwidth with 5 carriers (e.g., five 20MHz channels), the SSB from only one of the channels is needed, which would occupy between 3.84MHz to 7.68MHz (a small fraction of the total 100MHz signal bandwidth). A person of skill in the art will recognize that SSBs may be transmitted in various different patterns, depending on parameters such as subcarrier spacing, frequency range, and the like; the particular carrier subset sampled may differ accordingly, but will preferably occupy only a small fraction of the total signal bandwidth, regardless of the overall signal bandwidth and/ or carrier aggregation. However, the sampled carrier subset can additionally or alternatively occupy any other suitable bandwidth and/ or any other suitable portion of the total signal bandwidth.

[0030] However, S210 can additionally or alternatively include receiving any suitable transmission(s) in any suitable manner.

[0031] Detecting one or more SSBs S220 can function to locate the SSB(s) within the received transmission. S220 may not include detecting all SSBs in a frame, as some SSBs may not be discernable at the repeater (e.g., due to beamforming). However, S220 can alternatively include detecting all SSBs of a frame and/or detecting any other suitable number of SSBs.

[0032] Selecting one or more of the received SSBs S230 preferably functions to select an SSB (or multiple SSBs) for timing analysis. S230 preferably includes selecting a single SSB, such as the SSB that was received with the highest signal strength, but can alternatively include selecting multiple SSBs (e.g., all discernable SSBs, all SSBs received with signal strength greater than a threshold value, etc.). However, S230 can additionally or alternatively include selecting any other suitable SSB(s) in any suitable manner.

[0033] Decoding SSB information S240 preferably functions to determine a start time (and/or any other suitable reference time, such as a time associated with any other suitable reference event within the frame) for the frame (e.g., relative to the SSB timing). Based on the decoded SSB information, a timing offset between the frame start time (or other reference time) and the SSB time can be determined. S240 preferably includes using one or more internal repeater timestamps (e.g., SSB receipt time) and the determined timing offset(s) to determine the start time of the frame (referred to the internal repeater clock). However, S240 can additionally or alternatively include determining any other suitable information based on the SSB.

[0034] Determining the TDD pattern S250 preferably functions to determine the timing of uplink and/or downlink windows relative to the frame start time (and/or relative to any other reference time within the frame, such as an SSB time). The pattern can be determined from a control message (e.g., control message received from the base station, such as a control message within the transmission received in S210), based on user input (e.g., repeater configuration, information received from another network device, etc.), determined based on any other suitable information indicative of the TDD pattern (e.g., information received from the communication network, information received separate from the communication network, etc.), and/or determined in any other suitable manner.

[0035] However, the synchronization information (e.g., frame start time and/or other frame reference time, frame period, TDD schedule such as an uplink/downlink pattern, and/or any other suitable information associated with uplink or downlink window timing) can additionally or alternatively be determined in any other suitable manner.

[0036] S200 is preferably performed while synchronization information is unavailable, such as in response to (e.g., immediately or substantially immediately in response to) repeater startup, acquisition of a base station signal, change of synchronization information, and/or any other suitable loss of synchronization. However, S200 can additionally or alternatively be performed with any other suitable timing. S200 is preferably performed concurrently with S100, but the method can additionally or alternatively include operating the repeater in any other suitable modes (and/or not operating the repeater) while performing S200.

2.3 Operating in a synchronized repeater mode.

[0037] Operating in a synchronized repeater mode S300 preferably functions to provide bi-directional repeater functionality. S300 is preferably performed once synchronization is achieved (e.g., after determining synchronization information S200), more preferably while synchronization is maintained or substantially maintained, but can additionally or alternatively be performed with any other suitable timing.

[0038] S300 preferably includes determining a repeater operation schedule based on the synchronization information (e.g., based on the frame start time and uplink/ downlink pattern determined in S200). For example, this can include determining a schedule table referenced to the internal repeater clock (e.g., as shown in FIGURE 6). In this example, determining the schedule table can include determining the internal repeater timestamp for the start of a frame and determining additional timestamps for switching between uplink and downlink modes based on the determined uplink/ downlink pattern (e.g., adding a first scheduled window duration to the frame start timestamp to generate a second timestamp, adding an Mh scheduled window duration to the Mh timestamp to generate an N + 1th timestamp, etc.). However, S300 can additionally or alternatively include determining the schedule (e.g., schedule table) in any other suitable manner.

[0039] S300 preferably includes operating the repeater based on the determined schedule, such as operating the repeater in the appropriate mode (e.g., uplink mode or downlink mode) at appropriate times as indicated by the schedule. For example, this can include switching the repeater from uplink mode to downlink mode (and/ or vice versa) at the scheduled switching times.

[0040] Operating in the downlink mode is preferably performed as described above regarding S100, wherein the repeater receives a transmission from the base station and re-radiates it to user equipment (e.g., as shown in FIGURE 3A). Operating the repeater in the uplink mode preferably includes receiving transmissions from user equipment and re-radiating the transmissions to the base station (e.g., operating in the reverse relay direction from the downlink mode), such as shown by way of example in FIGURE 3B. However, S300 can additionally or alternatively include operating the repeater in any other suitable manner.

2.4 Maintaining synchronization.

[0041] Maintaining synchronization S400 preferably functions to prevent desynchronization from the communication network TDD schedule (e.g., due to clock drift). S400 preferably includes monitoring periodic signal timing S410 and adjusting operation timing S420 (e.g., as shown in FIGURES 7A, 7B, 8A, and/or 8B).

[0042] S410 preferably includes monitoring the timing of one or more periodic signals. S410 can include receiving a transmission within a known timing window. The known timing window is preferably selected based on an expectation that it will contain a known signal (e.g., known repeating signal, such as repeating with periodicity equal to the frame duration and/or SSB transmission cycle duration, which can be equal or substantially equal to 10 ms in some examples but can additionally or alternatively be any other suitable duration). For example, the known repeating signal can be a synchronization signal, such as the primary synchronization signal (PSS) and/or secondary synchronization signal (SSS) of an SSB. The synchronization signal used is preferably a synchronization signal from the SSB selected in S200, but can additionally or alternatively include a synchronization signal from any other suitable SSB, and/ or any other suitable synchronization signal. Based on the synchronization information (e.g., frame duration and/or SSB transmission cycle duration), the expected timing of the repeating signal is known (e.g., known within a limited tolerance range, such as approximately 50, 100, 200, 400, 20-50, 50-100, 100-200, 200-500, and/or 500- 1000 samples, etc.). Accordingly, S410 can include looking for the repeating signal only within a limited temporal range (e.g., within the expected timing tolerance, such as within a 200-sample window).

[0043] S410 preferably includes determining the received signal timing (of the known repeating signal) relative to its expected timing. For example, this can be achieved by determining a cross-correlation of the received transmission with the expected signal, wherein the peak of the cross-correlation will typically correspond to the offset from the expected timing (e.g., a cross-correlation peak at zero indicates that the signal occurred at the expected time, a cross-correlation peak at -10 samples indicates that the signal was received 10 samples earlier than expected, etc.). However, the received signal timing can be determined based on the received information in any other suitable manner.

[0044] Additionally or alternatively, S410 can include performing symbol timing detection, such as cyclic prefix detection. Such approaches may require averaging over multiple symbols (e.g., due to increased noise), and so may be less performant under certain circumstances.

[0045] However, S410 can additionally or alternatively include monitoring periodic signal timing in any other suitable manner. [0046] Adjusting repeater operation timing S420 preferably functions to compensate for clock drift (e.g., drift between the base station clock and repeater clock). S420 is preferably performed based on the periodic signal (e.g., based on the periodic signal timing determined in S410). If an offset from the expected timing is detected in S410, then S420 can include adjusting the timing of repeater operation (e.g., adjusting the schedule used for operating in the synchronized repeater mode, such as described above regarding S300).

[0047] S420 preferably includes adjusting the repeater operation timing to compensate for the clock drift detected in S410. For example, S420 can include shifting the scheduled switching times of the schedule table, preferably by an amount equal (or substantially equal) to the detected offset (e.g., if the signal arrives 4 ps early, shifting all scheduled times 4 ps earlier; if the signal arrives 3 ps late, shifting all scheduled times 3 ps later; etc.). For example, an updated frame reference time t/ can be determined based on the equation t . = t _r — t _d + nx, wherein t _r is a prior frame reference time, t _d is the detected offset, r is the expected frame duration, and n is a positive integer; in this example, each scheduled switching time of the schedule table can be taken to be a different frame reference time, and the appropriate updated value t/ can be determined based on its prior value t _r and the detected offset.

[0048] In some examples, a trend in timing drift maybe detected (and/ or otherwise determined to exist). For example, a timing drift trend may be detected based on a substantially constant offset from the expected timing is regularly detected (e.g., if the signal is always offset by a substantially constant amount, such as shown in FIGURE 8B). Additionally or alternatively, a timing drift trend if the average offset from expected timing is substantially non-zero (e.g., substantially greater than zero or substantially less than zero), possibly wherein the absolute value of the average is greater (or substantially greater) than a threshold (e.g., fixed threshold amount, such as an absolute time or an amount of time relative to the period; dynamic threshold, such as a threshold based on the variance of the timing drift; etc.). In such examples, S420 preferably includes adjusting the expected signal periodicity accordingly to compensate, in response to determining the timing drift trend. In a first such example, if the signal consistently arrives substantially 3 ps early (and/or arrives an average of 3 ps early), the repeater operation period (e.g., frame duration, SSB transmission cycle length, etc.) can be reduced by 3 ps to compensate. In a second such example, if the signal consistently arrives substantially 2 ps late (and/or arrives an average of 2 ps late), the repeater operation period (e.g., frame duration, SSB transmission cycle length, etc.) can be increased by 2 ps to compensate.

[0049] However, S400 can additionally or alternatively include maintaining synchronization in any other suitable manner.

[0050] S400 is preferably performed while operating in the synchronized repeater mode (e.g., as described above regarding S300). S400 can be performed every signal period (e.g., frame duration, SSB transmission cycle length, etc.), can be performed with any other suitable periodicity (e.g., for a period equal to an integer multiple of the signal period or TDD schedule period), can be performed sporadically, can be performed in response to trigger events (e.g., detection of possible de-synchronization, such as detection of low or no radio traffic in the expected direction near the beginning or end of one or more TDD uplink or downlink windows, detection of an internal repeater clock error, etc.), and/or can be performed with any other suitable timing.

[0051] Although referred to herein as a frame (e.g., having a duration such as 10 ms or any other suitable duration), a person of skill in the art will recognize that, in some circumstances, the method may additionally or alternatively be performed based on any other suitable periodic aspect(s) of the communication network, such as the SSB transmission cycle (e.g., cycle length for which SSB transmission is repeated, such as 5, 10, 20, 40, 80, or 160 ms, etc.). Further, although reference is made to operations of 5G NR communications networks, a person of skill in the art will recognize that the invention can analogously be applied in any other suitable TDD communications network including one or more substantially periodic signals.

[0052] However, the method for repeater operation 20 can additionally or alternatively include any other suitable elements performed in any suitable manner.

[0053] Although omitted for conciseness, the preferred embodiments include every combination and permutation of the various system components and the various method processes. Furthermore, various processes of the preferred method can be embodied and/or implemented at least in part as a machine configured to receive a computer- readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the system. The computer-readable medium can be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processing subsystem, but any suitable dedicated hardware device or hardware/firmware combination device can additionally or alternatively execute the instructions.

[0054] The FIGURES illustrate the architecture, functionality and operation of possible implementations of systems, methods and computer program products according to preferred embodiments, example configurations, and variations thereof. In this regard, each block in the flowchart or block diagrams may represent a module, segment, step, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block can occur out of the order noted in the FIGURES. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0055] As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.