Patent Description:
The addition of beamforming to mobile telephony offers the possibility of enhanced connectivity with high signal strength along with high directivity. The selection of an uplink and downlink beam, or beams to use between two points in a mobile setting can be challenging based on the frequencies and mobility of the units at both end-points. The disclosure herein introduces concepts for mobile telephony as well as solutions to problems occurring in beamforming at high (THz) frequencies with mobile units.

A method performed by a base station, the method comprising:.

Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs. ) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref. ") in the FIGs. indicate like elements, and wherein:.

In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to <FIG>, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

<FIG> is a system diagram illustrating an example communications system <NUM> in which one or more disclosed embodiments may be implemented. For example, the communications systems <NUM> may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

As shown in <FIG>, the communications system <NUM> may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) <NUM>/<NUM>, a core network (CN) <NUM>/<NUM>, a public switched telephone network (PSTN) <NUM>, the Internet <NUM>, and other networks <NUM>, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and/or a "STA", may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.

Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN <NUM>/<NUM>, the Internet <NUM>, and/or the networks <NUM>. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like.

Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell.

For example, the base station 114a in the RAN <NUM>/<NUM> and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface <NUM> using wideband CDMA (WCDMA).

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE <NUM> (i.e., Wireless Fidelity (Wi-Fi), IEEE <NUM> (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard <NUM> (IS-<NUM>), Interim Standard <NUM> (IS-<NUM>), Interim Standard <NUM> (IS-<NUM>), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

The base station 114b in <FIG> may be a wireless router, Home Node-B, Home eNode-B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE <NUM> to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. Thus, the base station 114b may not be required to access the Intemet <NUM> via the CN <NUM>/<NUM>.

For example, in addition to being connected to the RAN <NUM>/<NUM>, which may be utilizing an NR radio technology, the CN <NUM>/<NUM> may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA <NUM>, WiMAX, E-UTRA, or Wi-Fi radio technology.

The CN <NUM>/<NUM> may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN <NUM>, the Internet <NUM>, and/or other networks <NUM>.

As shown in <FIG>, the WTRU <NUM> may include a processor <NUM>, a transceiver <NUM>, a transmit/receive element <NUM>, a speaker/microphone <NUM>, a keypad <NUM>, a display/touchpad <NUM>, non-removable memory <NUM>, removable memory <NUM>, a power source <NUM>, a global positioning system (GPS) chipset <NUM>, and/or other elements/peripherals <NUM>, among others.

While <FIG> depicts the processor <NUM> and the transceiver <NUM> as separate components, it will be appreciated that the processor <NUM> and the transceiver <NUM> may be integrated together, e.g., in an electronic package or chip.

For example, in an embodiment, the transmit/receive element <NUM> may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element <NUM> may be configured to transmit and/or receive both RF and light signals.

For example, the WTRU <NUM> may employ MIMO technology. Thus, in an embodiment, the WTRU <NUM> may include two or more transmit/receive elements <NUM> (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface <NUM>.

The processor <NUM> may further be coupled to other elements/peripherals <NUM>, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals <NUM> may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and/or augmented reality (VR/AR) device, an activity tracker, and the like. The elements/peripherals <NUM> may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

The WTRU <NUM> may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. In an embodiment, the WTRU <NUM> may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

As noted above, the RAN <NUM> may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface <NUM>.

In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like.

While each of the foregoing elements are depicted as part of the CN <NUM>, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.

The MME <NUM> may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN <NUM> via an S1 interface and may serve as a control node.

The SGW <NUM> may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN <NUM> via the S1 interface. The SGW <NUM> may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. 11e DLS or an <NUM>.

In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in <NUM> systems.

High throughput (HT) STAs may use a <NUM> wide channel for communication, for example, via a combination of the primary <NUM> channel with an adjacent or nonadjacent <NUM> channel to form a <NUM> wide channel.

Very high throughput (VHT) STAs may support <NUM>, <NUM>, <NUM>, and/or <NUM> wide channels. Inverse fast Fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. At the receiver of the receiving STA, the above-described operation for the <NUM>+<NUM> configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc..

11af and <NUM>. 11af and <NUM>. 11n, and <NUM>. 11af supports <NUM>, <NUM> and <NUM> bandwidths in the TV white space (TVWS) spectrum, and <NUM>. 11ah may support meter type control/machine-type communications (MTC), such as MTC devices in a macro coverage area.

11n, <NUM>. 11ac, <NUM>. 11af, and <NUM>. Carrier sensing and/or network allocation vector (NAV) settings may depend on the status of the primary channel.

In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c.

For example, OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like.

The CN <NUM> shown in <FIG> may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b.

For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like. The AMF <NUM> may provide a control plane function for switching between the RAN <NUM> and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as Wi-Fi.

The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN <NUM> via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet <NUM>, e.g., to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

In view of <FIG>, and the corresponding description of <FIG>, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME <NUM>, SGW <NUM>, PGW <NUM>, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown). As explained herein, a wireless transmit/receive unit (WTRU) may be an example of a user equipment (UE). Hence the terms UE and WTRU and the notation WTRU/UE may be used with equal scope herein.

Due to high propagation losses at higher frequencies, i.e. millimeter Wave (mmW) or terahertz (THz) bands, a large number of closely-spaced antenna elements may be mounted at both a base station, such as a gNB, as well as at the UE, where the antenna processing can include analog domain beamforming. As illustrated in <FIG>, the best beam pair may not necessarily correspond to transmitter and receiver beams that are physically pointing directly towards each other, such as in line-of-sight (LOS) setting. For instance, due to scattering/reflections in the surrounding environment, such a LOS path between the transmitter and receiver may be blocked and a reflected path may provide better connectivity, as illustrated in the right-hand part of <FIG> This is even more critical for operation in higher-frequency bands due to their "around-the-corner" dispersion.

In this scenario, and in mmW/THz bands in general, having beam-management functionality which enables or retains a suitable beam pair at the transmitter/receiver becomes crucial. In majority of cases, once a suitable transmitter/receiver beam pair is found for, say, downlink transmission direction, it can also be a suitable beam pair for the uplink transmission direction and vice versa. In 3GPP this is referred to as (downlink/uplink) beam correspondence. Thus, in the case of beam correspondence, it is sufficient to explicitly determine a suitable beam pair in one of the transmission directions, while the same beam-pair can also be used also in the opposite transmission direction.

The concept of beam correspondence is also equally applicable for frequency division duplex (FDD) systems where the uplink and downlink spectrum pairs do not necessarily have the same carrier frequency. More explicitly, the beam correspondence holds even if uplink and downlink operate on different carrier frequencies in the paired spectrum.

Typically, the beam management consists of the following stages:.

Hereinbelow, the term gNB is used as a specific example of a base station. As expressed hereinabove, a base station (BS) may be a transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. One of skill in that will recognize that the example gNB used hereinbelow is just one example of a base station in a network and that the specific example of a gNB used hereinbelow represents just one example of a base station. In this disclosure, a focus is placed on the beam establishment as well as the beam adjustment stages of the beam management. Beam establishment includes the procedures and functions by which a beam pair is initially established in the downlink and uplink transmission directions, for example, when a connection is established. During the beam establishment/cell search, a UE (also known as a WTRU) can acquire a so-called synchronization signal block (SSB) transmitted by a base station, such as a gNB, in that specific cell. In NR, the gNB transmits a plurality of beamformed SSBs, each in different direction as shown in <FIG>, showing synchronization signal (SS) and synchronization blocks (SB)s. The number of SSBs is equal to the number of beams/directions which is dependent on the operating band, while the duration of SSBs is subcarrier spacing dependent. A typical SSB is shown in <FIG> showing primary synchronization signal (PSS), and secondary synchronization signal (SSS) subcarriers in relation to the physical broadcast channel (PBCH)s.

By acquiring each such SSB in different directions, the WTRU measures the L1 reference signal received power, abbreviated as L1-RSRP, and decides on the best SSB. Then subsequently the WTRU utilizes a corresponding random-access occasion e.g. a physical random-access channel (PRACH)) and preamble, where the uplink random-access transmission can be used by the network to identify the downlink beam acquired by the WTRU, thereby establishing an initial beam pair. The same beam pair can also be used for uplink transmission.

Once an initial beam pair is established, there is a requirement to regularly reevaluate/monitor the selection of transmitter-side and receiver-side beam directions due to movements and rotations of the mobile device. Furthermore, even for stationary devices, movements of other objects in the environment may block or unblock different beam pairs, implying a possible need to reevaluate the selected beam directions. This beam adjustment may also include refining the beam shape, for instance making the beam narrower compared to a relatively wider beam used for initial beam establishment.

Typically, beamforming involves beam pairs consisting of transmitter-side beamforming and receiver-side beamforming. The beam adjustment may include two stages:.

The following are example technical shortcomings and challenges that the state-of-the-art beam establishment and tracking procedures experience due to the rapid channel dynamics which are prevalent in particular in higher spectrum bands.

Detailed methods for beam establishment and beam tracking procedures that overcome the above-mentioned example technical shortcomings are proposed below.

The proposed techniques allow the base station (BS) and WTRU to identify the optimal beam pair, i.e. the beam pair having high L1-RSRP, with low latency by circumventing the exhaustive search. More explicitly, in this disclosure a data-driven based beam establishment and beam tracking procedures for THz frequencies are proposed. The solutions include (i) Data-driven beam establishment for THz systems, and (ii) Data-driven beam tracking/refinement procedures using CSI-RS in DL and SRS in UL.

A data-driven beam establishment for THz systems is proposed that exploits the spatial signatures of lower frequencies (e.g. mmWave/LTE) as well as WTRU's mobility information. This is achieved by exploiting the functional mapping between the spatial signatures such as CSI, location as well as mobility of lower frequencies and potential beam pairs at THz frequencies. In an option, the functional mapping can be obtained offline using training dataset, which may be obtained by simulation/real-time data samples. The functional mapping between the signatures of lower and higher frequencies could be achieved using different methods such as analytical tools that are used to identify correlation in between or by machine learning based solutions (e.g. deep reinforcement learning) that leverage these interdependencies. The method of exploiting the spatial signatures of lower frequency for beam alignment would reduce the latency for beam establishment.

More explicitly, in real time, the spatial signatures (e.g. CSI, mobility, location information) are acquired by the gNB in the UL, where WTRU transmits SRS for CSI estimation at the gNB and the mobility information (e.g. location, velocity) as data. The WTRU may receive signaling (e.g., L3 Radio Resource Control (L3/RRC), L2 Medium Access Control (L2/MAC) or L1 / Physical Downlink Control Channel (L1/PDCCH)) that configures and/or activates uplink transmissions of feedback that may include at least one of CSI, location and/or mobility information. However, employing this procedure in real time involves learning the function that maps the spatial signatures to beam pairs, which may be carried out offline. A flowchart of the steps involved in the proposed data-driven beam establishment design is shown in <FIG>.

In the method <NUM> of <FIG> at <NUM> Step <NUM>, the WTRU reports CSI (e.g. signal to noise (SNR) values, full channel matrix, channel quality information (CQI)), location (may include <NUM>-D position, different granularities) and mobility information (speed, may include <NUM>-D direction) to gNB (an example of a base station) over sub- <NUM> or mmWave. The information such as CSI, location and mobility (with speed) are used to exploit the spatial signatures of lower frequency to find the equivalent mapping in the higher frequency. The location information (may include <NUM>-D positioning information) is useful for gNB to select interference-free beam pair. The location information can be chosen based on the required granularity, while mobility (may include <NUM>-D direction and speed) can be used to combat the channel aging. More explicitly, the rationale for including location and mobility information in conjunction with CSI is that they can be used for predicting the beam that is free of interference from other users as well as the predicted beam is not outdated.

In <FIG> at <NUM> Step <NUM>, the gNB employs prediction, (e.g. optionally using artificial intelligence / machine learning (AI/ML) methods) with input features as CSI, location, mobility and predicts the beam directions as well as number of beams for THz. The gNB prediction includes beam pair prediction information. The beam pair prediction may be performed in a variety of ways. For example, beam pair prediction may optionally use an AI/ML method or may use another technique/method useful for prediction/calculation/estimation purposes. For example, a predictive method using a linear regression, logistic regression, a neural network, a decision tree, a naïve Bayes or other predictive methods may be used for beam pair prediction.

In <FIG> at <NUM> Step <NUM>, the gNB transmits SSBs in the direction (also the number of SSBs) as predicted.

Also in <FIG> at <NUM> Step <NUM>, the gNB configures the WTRU using sub-<NUM> or mmWave with the resource-set that includes the beam directions from a pre-determined codebook which is shared offline with both gNB and WTRU. The pair of gNB and WTRU employs a beam search over these potential beams. A codebook includes codewords, where each codeword is a set of candidate beam pairs. Each beam pair carries an SSB. An SSB index is a beam pair index. Indices may indicate multiple SSBs. The gNB also configures the WTRU with the time slot of occurrence of each SSB in the codeword (e.g. SSB index mapping in terms of time slots for the selected SSB beams). Each codeword of the codebook includes beams pertaining to a range of channel conditions. More explicitly, the gNB sends the codeword index/indices that include beams predicted by the gNB as well as the time of occurrence of the SSB indices.

In one example realization of a WTRU, some characteristic description can be as follows. In one example realization, WTRU may have an initial communication in a first frequency range (such as a sub-<NUM> or mmW range) and may determine at least one aspect of SSB configuration associated with a second frequency range (e.g., THz range) via a transmission in the first frequency range (e.g., <NUM> or mmW). In one solution, the determination may be implicit, for example based on property of transmission in the first frequency range. In another solution, the determination maybe explicit, for example based on indication/control message in the first frequency range. In some solutions, the WTRU may be configured with an association between SSB index and a codebook index. For example, the WTRU may determine the first symbol of candidate SSB on the second frequency range using a reference time instance (or an offset thereof) in a first frequency range. For example, the WTRU may be configured with a WTRU specific SSB burst set configuration (See <FIG>) possibly different from a common SSB burst set configuration. For example, WTRU may receive the WTRU specific SSB burst set configuration applicable for a second frequency range via a first frequency range. For example, the WTRU specific burst set configuration transmitted from the gNB to the WTRU on the first frequency range may include one or more of the following: the configuration of starting symbol for SSB burst, number of SSBs in a burst, number of SSB bursts, duration of SSB burst, SSB burst periodicity, subcarrier spacing, number of SSB bursts, repetition configuration etc. Possibly the WTRU specific configuration may be associated with a validity period or time window. The WTRU may assume the SSB transmission follows the WTRU specific configuration within that time window. When the WTRU specific SSB burst set time window overlaps with the common SSB burst set configuration, the WTRU may be configured to assume that the common SSB burst set overrides the WTRU specific configuration.

Then the WTRU measures L1-RSRP of each SSB and determines the best beam based on the RSRP threshold.

Returning to <FIG>, at <NUM> Step <NUM>, the WTRU measures the L1-RSRP of the best suitable beam and reports it to the gNB. If no beam is found, the WTRU sends a beam establishment failed flag with BDR to the gNB. Given the BDR feedback, the gNB changes beam directions and/or increases the number of beams. <FIG> at <NUM> Step <NUM>, the gNB, based on the feedback with BDR, may increase the beam directions or change the direction and also updates its predictions (i.e. MIL parameters or other prediction parameters). As an option in a worst-case scenario where an updated prediction may not be possible or useful, the gNB may employ exhaustive beam sweeping:.

The above principles of <FIG> may be used to advantage in the flowchart <NUM> of the proposed data-driven beam establishment for THz systems from the base station (BS) (e.g. a gNB) perspective as shown in <FIG>. As expressed above, a NR gNB designation may be used as an example, the gNB may equivalently be considered a BS to allow the method <NUM> to be utilized in other networks. At step <NUM>, the gNB (e.g. a BS) receives CSI, mobility information, and location information from the WTRU via the first frequency range. That is, via the sub <NUM> or mmWave frequency band. At <NUM>, the gNB makes or accesses beam pair prediction information using the step <NUM> information (CSI, mobility information, location information) to predict the potential beam pairs and beam directions to be used in the second frequency band (e.g. a THz band). A beam pair includes an indication of an angle of departure (transmit beam) and an indication of an angle of arrival (receive beam). A beam pair prediction includes indications of the angles of departure and arrival for the transmit and receive beam pairs. The beam pair prediction information may be accessed via a memory location, an index, or other means or may be calculated using the step <NUM> information. In one embodiment, AI/ML may be used to obtain the prediction. Beam pair prediction information may include the codeword index, which includes the predicted beam-pairs. The size of the codeword determines the number of beam pairs. Multiple codewords indices may also be sent to the WTRU, where each codeword has beam pairs. The WTRU searches for beam pairs that are indicated in these codewords.

At step <NUM>, the gNB may transmit, over the first frequency band (e.g. <NUM> or mm Wave band) beam configuration information to the WTRU. The beam configuration information may include one or more indications relating to beam pair information to allow the WTRU to use the second frequency band to communicate with the gNB. The gNB may transmit a codebook index or multiple codeword indexes where each codeword has beam pairs. The configuration information may also include time slot information for each beam pair provided. The configuration information sent to the WTRU indicates the beam pair prediction information including relevant beam parameters transmitted to the WTRU at the first frequency band to establish communication with the WTRU using the second frequency band.

At step <NUM>, the gNB transmits SSBs to the WTRU in the second frequency band in the direction of the WTRU. This transmission in the second frequency band is to allow the WTRU to receive the SSB transmissions at the second band and establish communication between the gNB and the WTRU using the information of the SSBs. The SSB information may include the number of SSBs according to the prediction of beam pair information made/predicted by the BS. The SSB information received by the WTRU may include the number of SSB directions and the SSBs direction information as well as the time slot indication for each SSB index received from the gNB.

It is noted that steps <NUM> and <NUM> may be reversed in order to establish a communication between the BS and the WTRU at the second frequency bands (e.g. THz band).

At step <NUM>, the BS receives feedback information/indication from the WTRU indicative of a beam establishment at the second frequency band. In one embodiment, a BDR may be received providing the indication of beam establishment. Beam establishment success or failure is tested at step <NUM>. If the beam establishment was successful, the step <NUM> may be performed and an acknowledge (ACK) may be sent and a random-access channel (RACH) communication may be initiated at the second frequency band. Thus, second frequency band communications may commence between the gNB and the WTRU. If the beam establishment at step <NUM> is not successful, the gNB at step <NUM> may perform an update of its beam pair prediction of which beams to select for a communication with the WTRU at the second frequency band. This update of beam pair prediction information (potential beams and beam directions) may be made using ML parameters or may be derived from a BDR received by the gNB. At step <NUM>, a retraining request may be sent to the WTRU based on the updated beam pair prediction information. Retraining generally may occur at the gNB. A retraining request may be sent to WTRU. After retraining is finished, the gNB may retry beam establishment using the updated AI/ML model parameters.

Using the principles of <FIG> and <FIG> above, an example flowchart <NUM> of the proposed data-driven beam establishment for THz systems from the WTRU perspective is shown in <FIG>. As above, the gNB is an example of a base station. At step <NUM>, the WTRU transmits the CSI, mobility information, and location information to the gNB in a first frequency range communication (e.g. sub <NUM> or mmWave communication). At step <NUM>, the WTRU receives configuration information in the first frequency range for set-up of the anticipated communication in the second frequency range. The configuration information, received over the first frequency band, may include information relating to beam pairs for communication in the second frequency band. The configuration information received by the WTRU may include the number of SSB directions and the SSBs direction information as well as the time slot mapping for each SSB index received from the gNB over the first frequency range.

Having received the beam configuration information from the gNB, the WTRU at step <NUM> searches for the beam with high L1-RSRP from the potential beams transmitted by the gNB in the second frequency range (e.g. THz range). At step <NUM>, the WTRU tests/identifies if the beam L1-RSRP is greater than a threshold. If yes, the example method <NUM> proceeds to step <NUM> where a confirmation of beam establishment is transmitted by the WTRU. In one embodiment, the confirmation is the WTRU transmitting to the gNB an indication of the established beam having the SSB index with a high L1-RSRP.

If at step <NUM>, the beam L1-RSRP does not meet the threshold for a successful beam establishment in the second frequency band, then the process <NUM> moves to step <NUM> and the WTRU may send a beam establishment failed indication (flag) and/or a BDR with at least one SSB index and corresponding L1-RSRP values. At step <NUM>, the WTRU may receive new beam pair prediction information from the gNB. The new beam pair prediction information may include a new SSB direction. In one alternative to sending a new SSB direction, the WTRU may conduct a beam scanning procedure to establish a connection in the second frequency range.

An example signaling diagram between a gNB <NUM> and a WTRU <NUM> is shown in <FIG>. The signaling in <FIG> comports with the aspects of <FIG>. At <NUM>, CSI, location information, and mobility information are transmitted from the WTRU to the gNB (an example of a base station). At <NUM>, the gNB accesses beam pair prediction information as previously described. For example, the gNB can perform beam pair prediction using an input of CSI, location, and mobility information to produce an output of SS burst beam directions, and size of burst information. Optionally, AI/ML may be used for beam-pair prediction. The beam pair prediction information may include synchronization signal burst beam directions and the size of the burst. At <NUM>, the gNB transmits, using the first frequency band, configuration information relating to beam pairs for communication in the second frequency band. Such configuration information may include a codebook index including SSB indices/beams, and time slot mappings for each SSB index. The WTRU searches for beam pairs in the codewords of the codebook index. At <NUM>, the gNB transmits SSB in the second frequency band to assist the WTRU in establishing communications between the gNB and the WTRU in the second frequency band.

At <NUM>, the WTRU uses the transmitted SSBs to attempt to establish a communication on the second communication band by measuring the L1-RSRP and determines a selected beam to use to establish that communication. In one embodiment, the selected beam is one having the highest L1-RSRP of the measured beams. Assuming a beam is found, and a connection is established at the second frequency band, then at <NUM>, the WTRU transmits feedback to the gNB. The feedback may include the SSB index of the selected beam.

Otherwise, if the beam establishment at the second frequency band was unsuccessful. The feedback from the WTRU to the gNB may include a beam establishment failed indication (flag) with a BDR. This failed indication is transmitted on the first frequency band communication link between the WTRU and gNB.

At this point, the gNB may take action at <NUM> to update the beam pair prediction information in a manner previously discussed. At <NUM>, the gNB may take the action of increasing the synchronization signal bursts and directions transmitted to the WTRU. In response, the WTRU at <NUM> measures the L1-RSRP of beams candidates at the second frequency band and identifies a selected beam for communication. At <NUM>, feedback to the gNB from the WTRU concerning beam establishment is communicated. Optionally, the feedback may be transmitted via the sub-<NUM>/mm Wave link.

Once the beam establishment is established, there may be a need for regularly tracking the beam or refining the beam pair. This is because of the rapid fluctuations arising due to movement of users/time-varying channel conditions. In this disclosure, a data-driven beam tracking technique relying on CSI statistics and location information from the WTRU is proposed. More explicitly, using data-driven predictions methods, e.g. such as the use of ML, the gNB predicts the time when the gNB and WTRU pair may be required to refine the beams, the number of CSI-RS and the direction of each CSI-RS required for tracking/refining the beam. In order to improve the robustness of the prediction, the gNB might use the past experience of beam tracking in its predictions.

A high-level description of the proposed data-driven beam tracking/refinement for THz systems is summarized in <FIG>.

In the <FIG> flowchart for the example method <NUM>, steps in the data-driven beam tracking/refinement for THz system are resented. In <FIG>, at <NUM> step <NUM>, the WTRU reports CSI statistics, location (i.e. mobility information, pattem information) to the gNB (an example of a base station) over sub-<NUM> or mmWave or THz links. CSI statistics such as variance, and mobility information can be used in configuring CSI-RS time slot as well as beam directions for tracking beam.

In <FIG> at <NUM> Step <NUM>, the gNB employs prediction using input features as CSI statistics, location, mobility and identifies/predicts the CSI-RS beam directions as well as time slot for beam adjustment/refinement at THz.

In <FIG> at <NUM> Step <NUM>, the gNB transmits CSI-RS in the time slot and direction in the second (e.g. higher frequency range, such as the THz frequency range) as predicted previously. To further improve the latency, the gNB can also determine the number of CSI-RS directions. In one option, the WTRU may also request the base station, (e.g. a network component, such as a gNB) for beam refinement depending on the observed quality of service (e.g. BER or rate) at the WTRU. rather than the gNB configuring WTRU with the time slot for beam refinement. This request may be made using the second frequency range, such as the higher THz frequency range.

In <FIG> at <NUM> Step <NUM>, the WTRU measures L1-RSRP of each CSI-RS in the configured timeslot and decides the best beam based on the pre-configured L1-RSRP threshold.

In <FIG> at <NUM> Step <NUM>, given the BRN report with a failure flag set, the gNB might increase the CSI-beam directions and/or change the CSI-RS beam directions in the second (e.g. THz) frequency range.

In accordance with <FIG>, an example data-driven beam tracking/refinement flow diagram <NUM> from a gNB perspective is shown in <FIG>. At step <NUM>, the gNB (an example of a base station) receives CSI, mobility, and location information from the WTRU via the first frequency range (e.g. <NUM> or mmWave range). At step <NUM>, the gNB obtains (calculates or accesses) a beam pair prediction is the CSI, mobility, and location information to predict the time slot for beam refinement as well as the number of CSI-RS beam directions. At step <NUM>, the gNB transmits the CSI-RS signals to the WTRU in the second frequency band at the predicted directions and the predicted times.

At step <NUM>, the gNB receives beam refinement feedback from the WTRU. This may be in the form of a beam refinement report (BRN). At step <NUM>, the BRN is tested and if the BRN indicates a successful beam refinement, then the example process <NUM> moves to step <NUM> where an ACK is sent from the gNB to the WTRU and use of the refined beam continues. If at step <NUM>, the BRN indicates a failed beam refinement, then step <NUM> may be undertaken where the beam pair prediction is updated. In one option, retraining may be undertaken, or a new beam pair prediction may be made using information from the BRN. In one option, at step <NUM>, the WTRU may be asked to retrain with information supplied by the gNB.

In accordance with <FIG> and <FIG>, an example data-driven beam tracking/refinement flow diagram <NUM> from a WTRU perspective is shown in <FIG>. At step <NUM>, the WTRU transmits the CSI, mobility, and location information to the gNB (an example of a base station) via the first frequency band (e.g. sub-<NUM> or mmWave) band). At step <NUM>, the WTRU receives from the gNB configuration information related to a beam refinement. This may include information concerning the number of CSI-RS directions and the CSI-RS direction information relating to the beam refinement. At step <NUM>, the WTRU searches for the beams at the second frequency band looking for beams with a selected L1-RSRP within the group of new potential beams identified by the gNB. The selected beam may be one with the highest L1-RSRP.

At step <NUM>, the selected beam is tested to determine if the L1-RSRP is above a threshold value. Assuming the selected new beam is above the threshold L1-RSRP, then the method <NUM> moves to step <NUM> where the WTRU transmits, in the first frequency band, an indication of the CSI-RS index of the selected beam that has the acceptable L1 RSRP value indication. If however, the selected beam does not have an L1-RSRP value greater than a threshold at step <NUM>, then the method <NUM> moves to step <NUM>, where a failed BRN is transmitted to the gNB. The BRN may include one or more of the CSI-RS indexes and corresponding L1-RSRPs. After some processing by the gNB, the WTRU may, at step <NUM>, receive new CSI-RS directions or continue transmission on the beam pair that is already connected in the second frequency range.

A signaling diagram <NUM> of an example data-driven CSI-RS based beam tracking/refinement between a gNB <NUM> and a WTRU <NUM> is shown in <FIG>. The signaling in <FIG> comports with the aspects of <FIG>. At <NUM>, CSI, mobility information, and location information are provided by the WTRU to the gNB (an example of a base station). At <NUM>, the gNB processes the received CSI statistics and location information and obtains (calculates or accesses) new beam pair prediction information for continued operation of the gNB and WTRU in the second frequency band (e.g. THz band). The new beam pair prediction information is a refinement of the existing beam configuration information and may include CSI-RS direction and number of CSI-RS locations. At <NUM>, the gNB transmits beam configuration information to the WTRU that refines the existing beam used in the second frequency band for communication between the gNb and the WTRU. The new beam configuration information includes the time slot for the beam refinement and any updated CSI-RS beam information. This refined information is transmitted to the WTRU on the first frequency band. At <NUM>, the gNB transmits refined CSI-RS beams in the second frequency band using the refined direction and the refined time slot resulting from the beam prediction obtained by the gNB.

At <NUM>, the WTRU receives the updated beam configuration information and measures L1-RSRP to determine a selected beam. The selected beam may be based on a threshold value for a successful beam update or refinement. Assuming that a successful refinement of the second frequency range beam is determined, then at step <NUM>, the WTRU transmits feedback to the gNB indicating a successful update of the communication on the second frequency band. Such an indication may be in indication of the selected CSI-RS index. However, if the attempt to update the existing communication using the second frequency band failed, then the WTRU may send to the gNB a BRN with a fail indication at <NUM>. Upon reception of the failed BRN report with a failure indication, the gNB at <NUM> updates the beam pair prediction using procedures such as AI/ML and/or a derivation from the BDR. At <NUM>, the gNB may take action based on the failure indication in the BRN. That action may include increasing the number of CSI-RS beams and or scheduling of a new time slot.

At <NUM>, the WTRU may receive updated configuration information and undertake measurements of each CSI-RS and identify a selected (best) beam that has an acceptable L1-RSRP. At <NUM>, the WTRU may transmit feedback to the gNB that may include the CSI-RS index of the selected beam for continued communication on the second frequency range.

Features of the disclosure herein include but are not limited to a base station (BS) apparatus and an example method performed by the BS. The example method includes receiving, from a wireless transmit receive unit (WTRU) via a communication in a first frequency band, channel state information (CSI) location information, and mobility information. The BS determines beam pair prediction information including one or more beam pair information to establish a communication in a second frequency band between the base station and the WTRU based on the CSI, location information, and mobility information. The communication in the second frequency band occurs at a higher frequency band than the communication in the first frequency band. The BS transmits, to the WTRU in the first frequency band, configuration information relating to the beam pair prediction information for communication in the second frequency band, wherein the configuration information includes a codeword index and time slot information for each beam pair. The BS transmits, in the second frequency band, at least one synchronization signal block according to the beam pair prediction information. The BS receives feedback from the WTRU, and the BS performs one of transmitting an acknowledge to the WTRU or updates the beam pair prediction information based on the feedback.

Receiving the CSI, location information, and mobility information from the WTRU includes receiving a spatial signature of the WTRU operating in the first frequency band. Determining beam pair prediction information includes determining beam direction and a number of beam pairs for the communication in the second frequency band. In one embodiment, determining beam pair prediction information includes performing a prediction of beam pair information using a machine learning technique.

The communication in the first frequency band occurs in a sub-<NUM> frequency band and the communication in the second frequency band occurs in a THz frequency band. The action of transmitting, to the WTRU in the first frequency band, configuration information relating to beam pairs for communication in the second frequency band includes the BS transmitting configuration information including at least one codeword index having at least one codeword where a codeword indicates a beam pair.

The BS receives feedback from the WTRU may include the base station transmitting to the WTRU a request for a beam data report (BDR) and receiving the BDR from the WTRU. Receiving feedback from the WTRU may include receiving a SSB index of a beam supporting the communication in the second frequency band. Receiving feedback from the WTRU may include the BS receiving from the WTRU an indication of beam establishment failure that is received in the first frequency band.

The features also include a computer-readable storage medium comprising instructions which when executed by a computer cause the computer to carry out any of the methods described herein.

Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. Although the solutions described herein consider New Radio (NR), <NUM> or LTE, LTE-A specific, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims. It is to be understood that this disclosure is not limited to particular methods or systems.

The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to <FIG>. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed.

One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality.

It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. " Further, the terms "any of" followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of" the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having <NUM>-<NUM> cells refers to groups having <NUM>, <NUM>, or <NUM> cells. Similarly, a group having <NUM>-<NUM> cells refers to groups having <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> cells, and so forth.

Claim 1:
A method performed by a base station, the method comprising:
receiving, from a wireless transmit receive unit, WTRU, via a communication in a first frequency band, channel state information, CSI, location information, and mobility information;
determining beam pair prediction information including one or more beam pair information to establish a communication in a second frequency band between the base station and the WTRU based on the received information, wherein the communication in the second frequency band occurs at a higher frequency band than the communication in the first frequency band;
transmitting, to the WTRU in the first frequency band, configuration information relating to the beam pair prediction information for communication in the second frequency band;
transmitting, in the second frequency band, at least one synchronization signal block according to the beam pair prediction information;
receiving feedback from the WTRU; and
performing one of transmitting an acknowledge to the WTRU or updating the beam pair prediction information based on the feedback.