Apparatuses for selecting communication beams based on normalized time of arrival (ToA) of reference signals

Apparatuses for selecting communication beams based on normalized times of arrival (ToA) of reference signals (RSs) are disclosed. An apparatus of a first cellular communication device includes a data storage device configured to store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by a second cellular communication device. The apparatus also includes one or more processors configured to process a received portion of the plurality of reference signals received from the second cellular communication device through at least a portion of the plurality of communication beams, normalize ToAs of one or more reference signals of the received portion of the plurality of reference signals to a time period unit; and identify which of the plurality of communication beams correspond to the one or more reference signals using the reference signal data.

BACKGROUND

Various embodiments generally may relate to the field of wireless communications, and more particularly, to using Time of Arrival (ToA) based positioning in new radio (NR).

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

In new radio (NR) systems, also known as Fifth Generation (5G) systems, including those using millimeter wave (mmWave) communications, multiple communication beams will be used for transmission and reception at both the next generation NodeB (gNB) side and the user equipment (UE) side. It is contemplated that any system consistent with embodiments herein may use five, eight, or any other number of communication beams. In some embodiments consistent with the present disclosure, a gNB may be a cellular base station in a cellular communications network. Also, embodiments of the disclosure extend to any communication systems where multiple beams are used for transmission, reception, or both transmission and reception. As a result, any reference to a particular communication node as a UE or gNB herein may be substituted with a more generic “communication device” to extend the disclosure to these systems. Furthermore, as the term “gNB” applies specifically to a radio access network (RAN) node serving as a cellular base station in NR or 5G systems, the term “cellular base station” could be used herein to replace the term “gNB” to appropriately extend the embodiments of the disclosure to other cellular systems such as Long Term Evolution (LTE) systems, Third Generation (3G) systems, Second Generation (2G) systems, and cellular communication systems that have not yet been contemplated (but that incorporate embodiments of the disclosure).

A time of arrival (ToA) based solution may be used as a positioning method in some wireless systems using multiple communication beams. In these systems, characteristics regarding the physical channel between the gNB and a UE or other device (including, but not limited to, distance, relative location, signal path of travel, and/or nature of interference sources) may be known or estimated based upon the traversal time of a reference signal (RS) from a gNB (or other device) to the UE (or other device), or based upon the traversal time of a signal from a UE (or other device) to a gNB (or other device).

The terms “beam” and “communication beam” are used interchangeably herein. A beam may include a Tx beam at a gNB for downlink, an Rx beam at a UE for downlink, a Tx beam at UE for uplink, or an Rx beam at a gNB for uplink.

NR scenarios involving multiple communication beams may take into account particular considerations for ToA based positioning. Specific RSs are associated with specific communication beams to enable differentiation between the different communication beams. In these scenarios, multiple RSs may be received at a device through different beams during a relevant time period. Timing information for these beams may be determined by normalizing ToAs for these beams. The receiving device may compare and/or report timing information for all or for fewer than all RSs (e.g., only one RS) received during that time period. In some embodiments, a UE may report, to a gNB, timing information for one or more RSs that arrived at the UE with earlier normalized ToAs than other RSs. By way of non-limiting example, the UE may report timing information for only the RS that has the earliest normalized ToA. In some embodiments, a UE may report timing information for one or more RSs received at the UE that did not necessarily have the earliest normalized ToAs, but had the best associated signal qualities of the received RSs. By way of non-limiting example, the UE may report timing information for only the RS that has the best signal quality of the received RSs. In some embodiments, a device will be configured to consider both timing information and signal quality of the received RSs when selecting one or more of the RSs for which to report timing information or selecting one or more beams for use in communication.

An RS in embodiments disclosed herein may be, but is not limited to, a Synchronization Signal Block (SSB), a Positioning Reference Signal (PRS), a Channel State Information Reference Signal (CSI-RS), a DeModulation Reference Signal for a Physical Broadcast Channel (DMRS for PBCH), a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Physical Random Access Channel (PRACH) signal, a Physical Uplink Control Channel (PUCCH) signal, or a Sounding Reference Signal (SRS). It is further contemplated that other signals or signal types may be used as an RS. By way of non-limiting example, a new signal or signal type may be created and designated for use as an RS.

FIG. 1is a simplified illustration of a wireless communication system100, according to some embodiments. The wireless communication system100includes a gNB102and a UE104in wireless communication (e.g., via a cellular data communication link). The gNB102broadcasts multiple transmit (“Tx”) beams106-114. The UE104can receive one or more reference signals on the different Tx beams106-114. Each beam106-114from the gNB102may be associated with a specific RS index, so the UE104may understand each beam as associated with a different index for an RS. For example, the first beam106may be associated with a first reference signal index, the second beam108may be associated with a second reference signal index, the third beam110may be associated with a third reference signal index, the fourth beam112may be associated with a fourth reference signal index, and the fifth beam114may be associated with a fifth beam index. The UE104may store information identifying the RSs in one or more data storage devices of the UE104to enable the UE to identify the RSs.

InFIG. 1, the first beam106travels from the gNB102to the UE104along a first path116. The second beam108travels from the gNB102to the UE104along a second path118. The second path118includes a reflection by an obstacle120, which obstructs the second path118. Different RSs may be sent by the gNB102in the first beam106and the second beam108along the first path116and the second path118, respectively.

Under these conditions, it may be that of the sent RSs, the highest quality (e.g., strongest RS received at UE104may be the RS travelling along the first path116associated with the first beam106. The received RS associated with the second beam108may have a lower received power than that of the RS associated with the first beam106because the second beam108is reflected by the obstacle120, which could cause an RS signal travelling along the second path118to lose power before reaching the UE104. Another reason the received RS associated with the second beam108may have a lower received power than the received RS associated with the first beam106may be because the second path118is longer than the first path116. As a result, the RS traveling along the second path118suffers a greater propagation loss relative to an RS traveling along the first path116.

The first RS to arrive at the UE104may be the RS received through the first path116, which may be a straight line assuming a line of sight connection between the gNB102and the UE104. As a result, the first path116is shorter than the second path118, and the RS associated with the first beam106would have an earlier normalized ToA than that of an RS associated with the second beam108. In embodiments where the UE102has been configured to report timing information of the RS signal having the earliest normalized ToA, the UE102may report timing information of the RS signal that arrived through the first path116.

FIG. 2is a simplified illustration of a wireless communication system200, according to some embodiments. The wireless communication system200includes a gNB202and a UE204in wireless communication, similar to the gNB102and the UE104ofFIG. 1. Similar to the wireless communication system100ofFIG. 1, the gNB202broadcasts multiple Tx beams206-214. The UE204can receive one or more reference signals on the different Tx beams206-214. As described above in relation toFIG. 1, each beam from the gNB202may be associated with a specific RS index, so the UE204may understand each beam as associated with a different index for an RS.

FIG. 2illustrates a case where a highest quality (e.g., strongest) RS received at the UE204may not be the same as an RS having an earliest normalized ToA at the UE204. InFIG. 2, the first beam206travels from the gNB202to the UE204along a first path216. The second beam208travels from the gNB202to the UE204along a second path218. The first path216passes through a first obstacle220on its way to the UE204. The second beam208is reflected by an obstacle222, which is located along the second path218to the UE204. An RS may be sent by the gNB204along each of the first path216and the second path218. The RS traveling along the first path216may suffer a large penetration loss when passing through the first obstacle220in order to arrive at the UE204. Therefore, the RS traveling along the first path216might not be the highest quality RS received at the UE in terms of RSRP, RSRQ, SINR, or another measure of signal quality. The RS traveling along the second path218might instead be the highest quality received RS in terms of RSRP, RSRQ, SINR, or another measure of signal quality. This may be because the loss from reflection of the second RS signal traveling along the second path218as reflected by the obstacle222is less than the penetration loss associated with the first RS signal traveling along the first path216. However, the second RS may not have the earliest normalized ToA when it arrives at the UE204. This may be because the first RS traveling along the first path216takes a shorter path to reach the UE202than that of the second RS, and thus this first RS has an earlier normalized ToA. In this scenario, if the UE204has been configured to report timing information of the RS signal having the earliest normalized ToA, the UE202may report, to the network, timing information (e.g., estimated timing information) for the first RS traveling along the first path216, even though it was not the highest quality RS signal that was received. In some embodiments, if the UE202has been configured to report timing information on the highest quality RS signal to arrive, the UE202may instead report, to the network, timing information for the second RS traveling along the second path.

FIG. 3is a simplified timing diagram300illustrating an example of timing of transmitted RSs, according to some embodiments. This timing of the transmitted RSs may be known by a receiving device (e.g., the timing is predetermined or indicated by the transmitting device to the receiving device in a timing message). As the timing is known by the receiving device, the receiving device can use the timing information to normalize the time of arrival of each of the RSs to a common time reference. This allows the receiving device to determine which of the RSs arrived the fastest from transmission to reception, corresponding to an earliest normalized ToA.

In the example ofFIG. 3, multiple RSs including multiple SSBs308-316are transmitted across multiple time slots302-306. Each of the SSBs308-316are illustrated here with four OFDM symbols per SSB. An RS according to some embodiments may instead include two, seven, or any other number of OFDM signals. The embodiment ofFIG. 1may be used as an example to illustrate the example ofFIG. 3. Referring toFIGS. 1 and 3together, the UE104is receiving the SSBs308-316from the gNB102. The gNB102has five (or more) Tx beams106-114for the downlink. Each of the SSBs308-316corresponds to one of the Tx beams106-114. The SSBs308-316may each correspond to a different RS index reflecting the corresponding Tx beam106-114through which it arrived at the UE104.

In some embodiments, the SSBs308-316are transmitted by the gNB102at different time occasions in the time domain. In the example ofFIG. 3, each SSB308-316occupies four Orthogonal Frequency Division Multiplexing (OFDM) symbols (i.e., each SSB time occasion is equivalent to 4 OFDM symbols). As illustrated inFIG. 3, the gNB102may transmit at least five SSBs308-316on at least five different beams106-114(with the first SSB308, the second SSB310, the third SSB312, the fourth SSB314, and the fifth SSB316each transmitting through a different beam106-114). The ToA of each SSB308-316may be derived from, for example, an estimated first arrival path timing of the SSB308-316at the UE104. As illustrated inFIG. 3, the SSBs308-316are each transmitted at a different time occasion in the time domain, as can be seen with reference to the differing placements of each respective SSB308-316across time slots302-306. The UE104may be able to receive the five SSBs308-316through the five different beams106-114. The UE104may record measured or estimated ToAs of the SSBs308-316(these ToAs may be referred to herein equivalently as “measured ToAs,” “estimated ToAs,” or “recorded ToAs”). The UE104may also be able to use its knowledge of the timing illustrated inFIG. 3to normalize the ToAs of the SSBs308-316to a common time period (e.g., a common time period unit).

The ToAs of SSBs308-316may be normalized to a common time period unit in order to facilitate comparison of the total time that it took for each SSB308-316to travel from the gNB102to the UE104(i.e., the normalized ToA). In general terms, a time period unit used for normalization with systems or methods described herein may include a time slot, an OFDM symbol, a subframe, a system frame, or any other period of time that the system or method is capable of measuring.

In the embodiment ofFIG. 3, the selected time period unit is a time slot. As illustrated inFIG. 3, The first SSB308and the second SSB310are transmitted by the gNB102in the first time slot302, the third SSB312and the fourth SSB314are transmitted by the gNB102in the second time slot304, and the fifth SSB316is transmitted by the gNB in the third time slot306. Under these circumstances, the ToAs of the first SSB308and the second SSB310are normalized to the first time slot302, which is the time at a head318of the first time slot302. By way of non-limiting example, each of SSB308-316may include a PSS, a PBCH, an SSS and a PBCH.

To normalize the ToAs of the SSBs308-316, the UE104uses timing information that is known regarding how the gNB102transmits the SSBs308-316. For example, the UE104may store RS timing information received from the gNB102. This timing information may indicate points of reference for timing of the RSs relative to each other and relative to time slots. By way of non-limiting example, the RS timing information may indicate timing of the time slots302-306relative to the SSBs308-316and to each other, timing of the SSBs308-316relative to the time slots302-316and to each other, or combinations thereof. As a result, to the extent that the SSBs308-316are received according to a different timing than that set forth in the timing information, the UE104can attribute this variation in timing of the SSBs308-316to the channel between the UE104and the gNB102. The UE104can use the timing information to normalize the received SSBs308-316to a common time unit. In consequence, the UE104can determine which of the SSBs308-316had an earliest normalized ToA, which would correspond to a shortest total time of propagation between the gNB102and the UE104.

As a specific, non-limiting example, the UE104may use a head318of the first time slot302as a point of reference to normalize the first SSB308and the second SSB310. In this example, the normalization of the first SSB308to the first time slot302is calculated by determining (e.g., based on timing information provided by the gNB, as shown inFIG. 3) that there is a number X of OFDM symbols324(where X≥0) between the head318of the first time slot302to a head330of the first SSB308. An estimated ToA of the first time slot302may then be determined from the estimated ToA of the first SSB308(corresponding to the head330of the first SSB308) by subtracting the amount of time corresponding to x OFDM symbols (i.e., X OFDM symbol durations) from the ToA of SSB308. The normalized ToA of the first SSB308may then be computed as follows:
(Normalized ToA of the first SSB 308)=(estimated ToA of the first SSB 308)−X*(duration of a single OFDM symbol),where “−” is the subtraction operator and “*” is the multiplication operator.

The normalized ToA of the second SSB310may be derived in similar fashion. For example, if it is known that the first SSB308includes four OFDM symbols and the second SSB310is transmitted immediately following transmission of the first SSB308(as shown inFIG. 3), the ToA of the second SSB310may be normalized by simply accounting for the four extra OFDM symbols introduced by the first SSB308prior to the arrival of the second SSB310, as shown below:
(Normalized ToA of the second SSB 310)=(estimated ToA of the second SSB 310)−(X+4)*(duration of a single OFDM symbol),where “+” is the addition operator.

The third SSB312and the fourth SSB314were transmitted in the second time slot304rather than in the first time slot302, as illustrated inFIG. 3. The transmission of the third SSB312was preceded by a number Y of OFDM symbols326(where Y≥0) following a head332of the second time slot304. To normalize the ToAs of these SSBs to the head318of the first time slot302such that they are comparable to the normalized ToAs of the first SSB308and the second SSB310, the slot difference from the first time slot302to the second time slot304is considered as well as the amount of time corresponding to the collection of Y OFDM symbols326:
(Normalized ToA of the third SSB 312)=(estimated ToA of the third SSB 312)−Y*(duration of a single OFDM symbol)−(duration of a single time slot).

The normalized ToA of the fourth SSB314may be derived in similar fashion, while simply accounting for the four extra OFDM symbols introduced by the third SSB312prior to the transmission of the fourth SSB314. This calculation is as follows:
(Normalized ToA of the fourth SSB 314)=(estimated ToA of the fourth SSB 314)−(Y+4)*(duration of a single OFDM symbol)−(duration of a single time slot).

As illustrated inFIG. 3, the fifth SSB316was transmitted in the third time slot306rather than in the first time slot302or the second time slot304. The transmittal of the fifth SSB316was preceded by a number Z of OFDM symbols328(where Z≥0) following a head334of the third time slot306. To normalize the fifth SSB316to the head318of the first time slot302such that it is comparable to the normalized ToAs of the first, second, third and fourth SSBs308-314, the time difference from the first time slot302to the third time slot306is considered as well as the amount of time corresponding to the Z OFDM symbols328. This calculation is as follows:
(Normalized ToA of the fifth SSB 316)=(estimated ToA of the fifth SSB 316)−Z*(duration of a single OFDM symbol)−2*(duration of a single slot).

At this juncture, all the ToAs of the SSBs308-316have been normalized to a same reference slot timing and it is possible to compare these normalized ToA values in order to determine which of the SSBs308-316has the earliest normalized ToA.

FIG. 4is a simplified flowchart illustrating a method400of operating a wireless communication system, according to some embodiments. The method400may be used to communicate data from a first cellular communication device to a second communication device. The method400may be used to communicate timing information for one or more reference signals received at the first cellular communication device to the second cellular communication device. The first cellular communication device may include a data storage device which contains stored reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by the second cellular communication device.

The method400includes processing402a received portion of a plurality of reference signals transmitted by a second cellular communication device through at least a portion of a plurality of communication beams. It should be noted that, in some instances, not all of the communication beams used by the second communication device may reach the first communication device. For example, one or more of the communication beams may be obstructed, point in a direction that is away from the first communication device, or otherwise fail to reach the first communication device. As a result, the received portion of the plurality of references signals may include all of the reference signals corresponding to all the communication beams, only a portion of the reference signals, only one of the reference signals, or in some instances none of the reference signals.

The method400also includes normalizing404times of arrival of one or more reference signals of the received portion of the plurality of reference signals to a common time period unit. The normalizing404may include performing calculations similar to the normalization calculations discussed above. In some embodiments, the normalizing404may be performed on each reference signal of the received portion of the plurality of reference signals. In some embodiments, the normalizing404may be performed on fewer than all (or even a single) of the reference signals of the received portion of the plurality of reference signals. In some embodiments, the reference signals of the received portion of the plurality of reference signals that are selected for normalization may have been previously indicated (e.g., by the second communication device) to the first communication device. In some embodiments, the reference signals of the received portion of the plurality of reference signals that are selected for normalization may be selected based on other characteristics. For example, these other characteristics may include signal quality measurements such as RSRP, RSRQ, SINR, other measures of signal quality, or combinations thereof.

The method400further includes identifying406which of the plurality of communication beams correspond to the one or more reference signals using the reference signal data.

In some embodiments, the second communication device (e.g., a gNB), which is the transmitter of the reference signals, may be configured to select one of the plurality of communication beams for use in transmitting communications to the first communication device (e.g., a UE). In such embodiments, the method400includes the first communication device generating408a report signal to be transmitted to the second cellular communication device. The report signal indicates timing information (e.g., normalized ToAs) of one or more of the received portion of reference signals to enable the second cellular communication device to select one of the communication beams for future communications. By way of specific, non-limiting example, the report signal may be generated by a UE in order to report the timing information (e.g., normalized ToAs) of one or more RSs associated with one or more specific beams and/or one or more specific RS indices. This timing information may include one or more normalized ToAs for the one or more reference signals. Also by way of specific, non-limiting example, the report signal may include an indication of an ordinal position of of one or more RSs, the RSs having been ordered based on their respective normalized ToAs (e.g., the RS that has the earliest normalized ToA corresponding to the shortest propagation time of the RS may be first in the order and the RS that has the latest normalized ToA corresponding to the longest propagation time of the RS may be last in the order).

In some embodiments, the report signal may include timing information regarding each of the one or more reference signals. In some embodiments, the report signal may include timing information regarding fewer than all (or even a single one) of the one or more reference signals. In some embodiments, the report signal may include timing information regarding the one or more reference signals which were previously indicated to the first communication device. In some embodiments, the report signal may include timing information for reference signals with other specified characteristics. These other specified characteristics may include signal quality measurements such as RSRP, RSRQ, SINR, other measures of signal quality, or combinations thereof.

In some embodiments, the first communication device (e.g., a gNB), which is the receiver of the reference signals, may be configured to select one of the plurality of communication beams for use by the second communication device (e.g., a UE) in transmitting communications to the first communication device. In such embodiments, the method400includes the first communication device selecting and indicating410, to the second communication device, a communication beam of the plurality of communication beams to be used in subsequent communications.

The method400further includes the first communication device processing412communications received through the selected one of the plurality of communication beams.

In some embodiments, the first communication device includes a UE (e.g., the UE104,204ofFIGS. 1 and 2) and the second communication device includes a gNB (e.g., the gNB102,202ofFIGS. 1 and 2). In some such embodiments the UE may report the normalized timing information to the gNB to enable the gNB to select one of the communication beams to be used in subsequent communications (e.g., operation408). In some such embodiments the gNB may select and indicate410the communication beam for use in subsequent communications.

In some embodiments, the first communication device includes a gNB (e.g., the gNB102,202ofFIGS. 1 and 2) and the second communication device includes a UE (e.g., the UE104,204ofFIGS. 1 and 2). In some such embodiments the gNB may select and indicate410the communication beam for use in subsequent communications. In some such embodiments, the gNB may report the normalized timing information to the UE to enable the UE to select one of the communication beams to be used in subsequent communications (e.g., operation408).

Also, the method400ofFIG. 4is directed to selection of a transmit beam for use in subsequent communications. It will be apparent to one of ordinary skill that a similar method could be implemented to selection of a receive beam in addition to, or instead of, selection of a transmit beam. For example, rather than a list of normalized ToAs with an entry for each received RS that corresponds to a particular transmit beam, the normalized timing information may include a matrix of normalized ToAs of the RSs through the various combinations of the transmit beams and the receive beams. In this way, both a transmit beam and a receive beam may be selected.

If multiple RSs for positioning are transmitted or received via multiple Tx and/or Rx beams, the ToA of the earliest arrived RS may be used for positioning timing (e.g., as a reference for normalizing the other received RSs) regardless of the used Tx or Rx beam. In other words, the ToA may be estimated from the first arrival path of a specific RS. An example of Embodiment 1 was provided above in the discussion ofFIG. 3in which the SSBs308-316were normalized based on an estimated ToA of the first SSB308.

If multiple RSs for positioning are transmitted or received via multiple Tx and/or Rx beams, the network (e.g., a gNB) may indicate to a UE to estimate RS timing for a number N (where N is an integer) of RSs having the top/best signal quality (e.g., the top N strongest RSs with corresponding beams). By way of non-limiting example, the quality of an RS may be measured by the UE using RSRP, RSRQ, SINR, other measure of signal quality, or combinations thereof. The UE may estimate RS timings on these N beams (i.e., the corresponding RSs), and the UE may report, to the gNB, the timing information (e.g., the normalized ToAs) along with associated specific beam/RS index information of each of these RSs. In some instances, the UE may report the timing information (e.g., normalized ToA) and corresponding beam/RS index for only the RS with the earliest normalized ToA among these top N RSs/beams. The RS timing may be transmit timing or receive timing, and receive timing may be estimated from the first arrival path of a specific RS. Also, as previously discussed, the ToAs of RSs with different beams may be normalized to a same time period unit for comparison.

For example, a network (e.g., a gNB) may indicate to a UE to measure ToA of RSs on the top 8 (assuming that N=8) highest quality RSs/beams received at the UE. The UE will then measure the ToA of the top 8 highest quality (e.g., strongest) RSs with corresponding beams, and report the timing information (e.g., normalized ToA information) of these 8 RSs with their corresponding beams/RS indices. The UE may report the timing information (normalized ToA information and corresponding beam/RS index) for the RS with the earliest normalized ToA among these 8 highest quality RSs/beams.

If multiple RSs for positioning are transmitted or received via multiple Tx and/or Rx beams, a network (e.g., a gNB) may indicate to a UE to estimate timing of RSs whose RSRP/RSRQ/SINR are at or above a threshold. The UE may estimate RS timings on the RSs that exceed the given threshold, and the UE may report the timing information (e.g., normalized ToA information), along with associated specific beams/RS indices, of each of these RSs. In some instances, the UE may report the timing information (e.g., the normalized ToA information) and corresponding beam/RS index information for only the RS with the earliest normalized ToA among these RSs/beams that exceed the given threshold. The RS timing may be Tx timing or Rx timing, and Rx timing may be estimated from the first arrival path of a specific RS. As previously discussed, the ToAs of RSs with different beams may be normalized to a common time period unit for comparison.

For example, the network (e.g., the gNB) may indicate, to a UE, to measure ToA information of all received RSs with an RSRP, RSRQ or SINR greater than or equal to a signaled threshold. The UE will measure the ToA of RS above this threshold. The UE will then report the timing information (e.g., normalized ToA information) of these RSs along with their corresponding beams/RS indices. In some instances, the UE may report only the timing information (e.g., normalized ToA information) and corresponding beam/RS index information for only the RS with the earliest normalized ToA from among these RS that are above the threshold.

If multiple RSs for positioning are transmitted or received via multiple Tx and/or Rx beams, the network (e.g., the gNB) may indicate a bitmap of RSs/beams, indices of RSs/beams, or a pattern of RSs/beam to a UE to instruct the UE to measure the ToA information (e.g., the normalized ToA information) on those of the RSs/beams that are included in the bitmap/index/pattern. The UE may calculate RS timings (e.g., normalized ToAs) on these RSs/beams, and the UE may report the timing information (e.g., the normalized ToA information) and corresponding specific beam/RS indices information for each of these RSs. In some instances, the UE may report the timing information (e.g., the normalized ToA information) and the associated beam/RS index information only for the RS with the earliest normalized ToA among these RSs/beams. The RS timing may be Tx timing or Rx timing, and Rx timing may be estimated from the first arrival path of a specific RS. As previously discussed, the ToAs of RSs with different beams may be normalized to a same time period unit for comparison.

For example, inFIG. 3, the network may indicate a bitmap “11100” to a UE in a system with five communication beams. Each of the bits of the bitmap may correspond with a different one of the five communication beams. The bitmap may indicate to the UE that the UE should measure ToA information of the first, second, and third SSBs308,310, and312(i.e., corresponding to a first, second and third of the 5 communication beams). The UE will measure the ToAs of the first, second, and third SSBs308,310, and312on these communication beams, and then the UE will report the timing information (e.g., the normalized ToA information) of these SSBs308,310, and312along with their corresponding RS/beam index information. In some instances, the UE may report the timing information (e.g., the normalized ToA information) and the associated beam/RS index information only for the one of the SSBs308,310, and312with the earliest normalized ToA among the indicated RSs/beams.

FIG. 5is a simplified signal flow diagram of a wireless communication system500, according to some embodiments. The wireless communication system500includes a gNB502and a UE504. As used herein with reference toFIGS. 5 and 6, the term “transmission” refers to the wireless communication of one or more signals between a gNB502,604and a UE504,602across one or more beams.

The gNB502optionally sends an RS information transmission506to the UE504. The RS information transmission506may include reference signal information. The reference signal information may include some (including one or more information items) or all of the following information items, according to various embodiments of the disclosure. For example, this reference signal information may identify or define RS(s) that may be sent from the gNB502to the UE504, and correlate the RS(s) with the one or more beams to enable the UE504to identify the beams during an RS transmission508. The reference signal information may include information identifying one or more indexes associated with RSs that will be transmitted by the gNB502. The reference signal information may include information such as a bitmap or pattern identifying to the UE504which RSs/beams received at the UE504should be considered for normalized timing information reporting by the UE504. The reference signal information may include timing information of RSs that have been or will be transmitted to the UE504to enable the UE504to identify points of reference in time for normalizing ToAs of the RSs. In various embodiments according toFIG. 5, the first transmission506may not be sent in cases where the UE504is already aware of the reference signal information that could otherwise be transferred by the first transmission506(e.g., where the UE504is already aware of the information described above).

The gNB502then sends an RS transmission508to the UE504. This second transmission includes a plurality of reference signals to the UE504, which are sent on a plurality of communication beams.

Once the RS transmission508arrives at the UE504, the UE504calculates510a normalized ToA(s) of a selected RS that arrived in the second transmission508. In some embodiments, the UE504calculating the normalized ToA(s) of a selected RS comprises calculating the normalized ToAs of a plurality (e.g., some or all) of the RSs. The calculation of the normalized ToA value may be according to embodiments discussed herein.

The UE504also identifies512which of the plurality of communication beams connecting gNB502and UE504corresponds to the selected RS or RSs. Those of ordinary skill in the art will recognize that the calculating510and the identifying512may occur in any order.

The UE504then proceeds to transmit a report transmission514to the gNB502. The report transmission514is configured to indicate to the gNB502a normalized ToA of the selected RS. The report transmission514may also indicate identifying information regarding the communication beam upon which the selected RS arrived, such as the beam index corresponding to the selected RS or RSs, discussed relative to other embodiments herein. The information included in the report signal may allow the gNB502to determine which of the communication beams was identified512by the UE504(i.e., which of the communication beams corresponds to the selected reference signal or reference signals).

The gNB502may then select a communication beam for use in subsequent communications based on the information of the report signal. Communications between the UE504and the gNB502may be performed using the selected communication beam.

In some embodiments of the wireless communication system500, the communication beams used during RS transmission508may be one or more Tx beams used by the gNB502for transmission. In such embodiments a selected Tx beam is used by the gNB502in transmitting516subsequent communications to the UE504.

It will be apparent to one of ordinary skill in the art that that the UE504may also be using a plurality of Rx beams in order to receive the second transmission508on the plurality of Tx (communication) beams used by the gNB502. In such embodiments, the gNB502may also select an Rx beam for use during the transmission flow500. This Rx beam may be selected by the gNB502using embodiments discussed herein (e.g., Embodiments 1-4). The selected Rx beam may be selected from among a plurality of the Rx beams used by the UE504to receive the RS transmission508(e.g., the UE504would be capable of identifying which Rx beam received certain combinations of the RSs). In some embodiments, the Rx beam selected by the gNB502in this manner may be used in addition to the Tx beam that may have been selected by the gNB502.

FIG. 6is a simplified signal flow diagram of a wireless communication system600, according to some embodiments. The wireless communication system includes a UE602and a gNB604. The UE602optionally sends an RS information transmission606to the UE604. The first transmission606may include information similar to that of the RS information transmission506ofFIG. 5. For example, the RS information transmission may include reference signal information. This reference signal information may identify or define RS(s) which may be sent from the UE602to the gNB604. The reference signal information may include information identifying one or more indexes associated with RSs that will be transmitted by the UE602. The reference signal information may include information such as a bitmap or pattern identifying to the gNB604which RSs/beams received at the gNB604should be considered by the gNB604for selection to calculate610normalized ToA. The reference signal information may include timing information corresponding to one or more transmitted RSs that have been or will be transmitted to the gNB604to enable the gNB604to enable the gNB604identify points of reference in time for normalizing ToAs of the RSs. In various embodiments according toFIG. 6, the RS information transmission606may not be sent in cases where the gNB604is already aware of the reference signal information that could otherwise be included in the first transmission606(e.g., where the gNB604is already aware of the information described above).

The UE602then sends an RS transmission608to the gNB604. This RS transmission includes a plurality of reference signals on a plurality of communication beams.

Once the RS transmission608arrives at the gNB604, the gNB604calculates610a normalized ToA of a selected RS or RSs that arrived in the RS transmission508. The calculation of the normalized ToA value may be according to embodiments discussed herein.

The gNB604also identifies612which of the plurality of communication beams connecting UE602and gNB604corresponds to the selected RS or RSs. Persons with ordinary skill in the art will recognize that the calculating610and the identifying612may occur in any order.

The gNB604selects one of the communication beams based on the normalized ToAs of the RSs, and then optionally proceeds to send an instruction transmission614to the UE602. The instruction transmission614is configured to instruct the UE602to use a specified communication beam for future communications.

Communications between the UE602and the gNB604may then be transmitted616on the communication beam that was selected by the gNB604.

In some embodiments of the wireless communication system600, the communication beams used during the RS transmission608may be one or more Tx beams used by the UE602for transmission. In such embodiments, the gNB612selects a Tx beam to be used by the UE602in transmissions616of subsequent communications.

It will be apparent to one of ordinary skill in the art that in some embodiments the gNB604may use a plurality of Rx beams in order to receive the RS transmission608on the plurality of Tx (communication) beams used by the UE602. In such embodiments, the gNB604may also select an Rx beam for use in the transmissions616. This Rx beam may be selected by the gNB604by using normalization and selection processes disclosed herein (e.g., Embodiments 1-4). In some embodiments, the Rx beam identified by the gNB604in this manner may be used in addition to the Tx beam that may have been identified612in the transmission flow600in the transmissions616.

FIG. 7illustrates an architecture of a system700of a network in accordance with some embodiments. The system700is shown to include a user equipment (UE)701and a UE702. The UEs701and702are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

The UEs701and702may be configured to connect, e.g., communicatively couple, with a radio access network (RAN)710. The RAN710may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs701and702utilize connections703and704, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections703and704are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs701and702may further directly exchange communication data via a ProSe interface705. The ProSe interface705may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE702is shown to be configured to access an access point (AP)706via connection707. The connection707can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP706would comprise a wireless fidelity (WiFi®) router. In this example, the AP706may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

The RAN710can include one or more access nodes that enable the connections703and704. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN710may include one or more RAN nodes for providing macrocells, e.g., macro RAN node711, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node712.

Any of the RAN nodes711and712can terminate the air interface protocol and can be the first point of contact for the UEs701and702. In some embodiments, any of the RAN nodes711and712can fulfill various logical functions for the RAN710including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In accordance with some embodiments, the UEs701and702can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes711and712over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs701and702. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs701and702about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE702within a cell) may be performed at any of the RAN nodes711and712based on channel quality information fed back from any of the UEs701and702. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs701and702.

The RAN710is shown to be communicatively coupled to a core network (CN)720—via an S1 interface713. In embodiments, the CN720may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface713is split into two parts: the S1-U interface714, which carries traffic data between the RAN nodes711and712and a serving gateway (S-GW)722, and an S1-mobility management entity (MME) interface715, which is a signaling interface between the RAN nodes711and712and MMEs721.

In this embodiment, the CN720comprises the MMEs721, the S-GW722, a Packet Data Network (PDN) Gateway (P-GW)723, and a home subscriber server (HSS)724. The MMEs721may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs721may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS724may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN720may comprise one or several HSSs724, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS724can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

The S-GW722may terminate the S1 interface713towards the RAN710, and routes data packets between the RAN710and the CN720. In addition, the S-GW722may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The P-GW723may terminate an SGi interface toward a PDN. The P-GW723may route data packets between the CN720(e.g., an EPC network) and external networks such as a network including the application server730(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface725. Generally, an application server730may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW723is shown to be communicatively coupled to an application server730via an IP communications interface725. The application server730can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs701and702via the CN720.

The P-GW723may further be a node for policy enforcement and charging data collection. A Policy and Charging Enforcement Function (PCRF)726is the policy and charging control element of the CN720. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF726may be communicatively coupled to the application server730via the P-GW723. The application server730may signal the PCRF726to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF726may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server730.

FIG. 8illustrates an architecture of a system800of a network in accordance with some embodiments. The system800is shown to include a UE801, which may be the same or similar to UEs701and702discussed previously; a RAN node811, which may be the same or similar to RAN nodes711and712discussed previously; a User Plane Function (UPF)802; a Data network (DN)803, which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC or CN)820.

The CN820may include an Authentication Server Function (AUSF)822; a Core Access and Mobility Management Function (AMF)821; a Session Management Function (SMF)824; a Network Exposure Function (NEF)823; a Policy Control Function (PCF)826; a Network Function (NF) Repository Function (NRF)825; a Unified Data Management (UDM)827; and an Application Function (AF)828. The CN820may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.

The UPF802may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN803, and a branching point to support multi-homed PDU session. The UPF802may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF802may include an uplink classifier to support routing traffic flows to a data network. The DN803may represent various network operator services, Internet access, or third party services. NY803may include, or be similar to application server730discussed previously.

The AUSF822may store data for authentication of UE801and handle authentication related functionality. The AUSF822may facilitate a common authentication framework for various access types.

The AMF821may be responsible for registration management (e.g., for registering UE801, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF821may provide transport for SM messages between and SMF824, and act as a transparent proxy for routing SM messages. AMF821may also provide transport for short message service (SMS) messages between UE801and an SMS function (SMSF) (not shown byFIG. 8). AMF821may act as Security Anchor Function (SEA), which may include interaction with the AUSF822and the UE801, receipt of an intermediate key that was established as a result of the UE801authentication process. Where USIM based authentication is used, the AMF821may retrieve the security material from the AUSF822. AMF821may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF821may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (NI) signaling, and perform NAS ciphering and integrity protection.

AMF821may also support NAS signaling with a UE801over an N3 interworking-function (IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signaling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS (NI) signaling between the UE801and AMF821, and relay uplink and downlink user-plane packets between the UE801and UPF802. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE801.

The SMF824may be responsible for session management (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session. The SMF824may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN.

The NEF823may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF828), edge computing or fog computing systems, etc. In such embodiments, the NEF823may authenticate, authorize, and/or throttle the AFs. NEF823may also translate information exchanged with the AF828and information exchanged with internal network functions. For example, the NEF823may translate between an AF-Service-Identifier and an internal 5GC information. NEF823may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF823as structured data, or at a data storage NF using a standardized interfaces. The stored information can then be re-exposed by the NEF823to other NFs and AFs, and/or used for other purposes such as analytics.

The NRF825may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF825also maintains information of available NF instances and their supported services.

The PCF826may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior. The PCF826may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of UDM827.

The UDM827may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE801. The UDM827may include two parts, an application FE and a User Data Repository (UDR). The UDM may include a UDM FE, which is in charge of processing of credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification handling; access authorization; registration/mobility management; and subscription management. The UDR may interact with PCF826. UDM827may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.

The AF828may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC and AF828to provide information to each other via NEF823, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE801access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF802close to the UE801and execute traffic steering from the UPF802to DN803via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF828. In this way, the AF828may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF828is considered to be a trusted entity, the network operator may permit AF828to interact directly with relevant NFs.

As discussed previously, the CN820may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE801to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF821and UDM827for notification procedure that the UE801is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM827when UE801is available for SMS).

The system800may include the following reference points: N1: Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3: Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network. There may be many more reference points and/or service-based interfaces between the NF services in the NFs, however, these interfaces and reference points have been omitted for clarity. For example, an NS reference point may be between the PCF and the AF; an N7 reference point may be between the PCF and the SMF; an N11 reference point between the AMF and SMF; etc. In some embodiments, the CN820may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME721) and the AMF821in order to enable interworking between CN820and CN720.

Although not shown byFIG. 8, system800may include multiple RAN nodes811wherein an Xn interface is defined between two or more RAN nodes811(e.g., gNBs and the like) that connecting to 5GC820, between a RAN node811(e.g., gNB) connecting to 5GC820and an eNB (e.g., a RAN node711ofFIG. 7), and/or between two eNBs connecting to 5GC820.

In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE801in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes811. The mobility support may include context transfer from an old (source) serving RAN node811to new (target) serving RAN node811; and control of user plane tunnels between old (source) serving RAN node811to new (target) serving RAN node811.

A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer. The SCTP layer may be on top of an IP layer. The SCTP layer provides the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

FIG. 9illustrates example components of a device900in accordance with some embodiments. In some embodiments, the device900may include application circuitry902, baseband circuitry904, Radio Frequency (RF) circuitry906, front-end module (FEM) circuitry908, one or more antennas910, and power management circuitry (PMC)912coupled together at least as shown. The components of the illustrated device900may be included in a UE or a RAN node. In some embodiments, the device900may include fewer elements (e.g., a RAN node may not utilize application circuitry902, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device900may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The application circuitry902may include one or more application processors. For example, the application circuitry902may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device900. In some embodiments, processors of application circuitry902may process IP data packets received from an EPC.

The baseband circuitry904may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry904may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry906and to generate baseband signals for a transmit signal path of the RF circuitry906. Baseband processing circuitry904may interface with the application circuitry902for generation and processing of the baseband signals and for controlling operations of the RF circuitry906. For example, in some embodiments, the baseband circuitry904may include a third generation (3G) baseband processor904A, a fourth generation (4G) baseband processor904B, a fifth generation (5G) baseband processor904C, or other baseband processor(s)904D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry904(e.g., one or more of baseband processors904A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry906. In other embodiments, some or all of the functionality of baseband processors904A-D may be included in modules stored in the memory904G and executed via a Central Processing Unit (CPU)904E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry904may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry904may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry904may include one or more audio digital signal processor(s) (DSP)904F. The audio DSP(s)904F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry904and the application circuitry902may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the mixer circuitry906A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry906D to generate RF output signals for the FEM circuitry908. The baseband signals may be provided by the baseband circuitry904and may be filtered by the filter circuitry906C.

The synthesizer circuitry906D may be configured to synthesize an output frequency for use by the mixer circuitry906A of the RF circuitry906based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry906D may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry904or the application circuitry902(such as an applications processor) depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry902.

FEM circuitry908may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas910, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry906for further processing. The FEM circuitry908may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry906for transmission by one or more of the one or more antennas910. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry906, solely in the FEM circuitry908, or in both the RF circuitry906and the FEM circuitry908.

In some embodiments, the PMC912may manage power provided to the baseband circuitry904. In particular, the PMC912may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC912may often be included when the device900is capable of being powered by a battery, for example, when the device900is included in a UE. The PMC912may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

FIG. 9shows the PMC912coupled only with the baseband circuitry904. However, in other embodiments, the PMC912may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry902, the RF circuitry906, or the FEM circuitry908.

In some embodiments, the PMC912may control, or otherwise be part of, various power saving mechanisms of the device900. For example, if the device900is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device900may power down for brief intervals of time and thus save power.

FIG. 10illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry904ofFIG. 9may comprise processors904A-904E and a memory904G utilized by said processors. Each of the processors904A-904E may include a memory interface,1004A-1004E, respectively, to send/receive data to/from the memory904G.

The baseband circuitry904may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface1012(e.g., an interface to send/receive data to/from memory external to the baseband circuitry904), an application circuitry interface1014(e.g., an interface to send/receive data to/from the application circuitry902ofFIG. 9), an RF circuitry interface1016(e.g., an interface to send/receive data to/from RF circuitry906ofFIG. 9), a wireless hardware connectivity interface1018(e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface1020(e.g., an interface to send/receive power or control signals to/from the PMC912.

FIG. 11is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG. 11shows a diagrammatic representation of hardware resources1100including one or more processors (or processor cores)1110, one or more memory/storage devices1120, and one or more communication resources1130, each of which may be communicatively coupled via a bus1140. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor1102may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources1100.

The communication resources1130may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices1104or one or more databases1106via a network1108. For example, the communication resources1130may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

Instructions1150may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors1110to perform any one or more of the methodologies discussed herein. The instructions1150may reside, completely or partially, within at least one of the processors1110(e.g., within the processor's cache memory), the memory/storage devices1120, or any suitable combination thereof. Furthermore, any portion of the instructions1150may be transferred to the hardware resources1100from any combination of the peripheral devices1104or the databases1106. Accordingly, the memory of processors1110, the memory/storage devices1120, the peripheral devices1104, and the databases1106are examples of computer-readable and machine-readable media.

EXAMPLES

The following is a non-exhaustive list of example embodiments that fall within the scope of the disclosure. In order to avoid complexity in providing the disclosure, not all of the examples listed below are separately and explicitly disclosed as having been contemplated herein as combinable with all of the others of the examples listed below and other embodiments disclosed hereinabove. Unless one of ordinary skill in the art would understand that these examples listed below, and the above disclosed embodiments, are not combinable, it is contemplated within the scope of the disclosure that such examples and embodiments are combinable.

Example 1 may include if RS for positioning are transmitted or received via multiple Tx or Rx beams, the ToA of the earliest arrived RS may be used for positioning timing regardless of the used Tx or Rx beamThe beams may include Tx beam at gNB for downlink, or, Rx beam at UE for downlink, or Tx beam at UE for uplink, or Rx beam at gNB for uplink.The RS for positioning may include but not limit to:SSB(synchronization sequence block), orPRS(positioning reference signal), orCSI-RS, orDMRS for PBCH, orPSS and/or SSS, orPRACH, orPUCCH, orSRS (sounding reference signal)The ToA may be estimated from the first arrival path of a specific RSThe ToAs of RS with different beams may be normalized to a same time period unit for comparison, the time period unit may include but not limit to:Time slot, orOFDM symbol, orSubframe, orSystem frameUE may report the timing information associated with specific beam/RS index

Example 2 may include if RS for positioning are transmitted or received via multiple Tx or Rx beams, network may indicate UE to estimate RS timing for top/best n beams (e.g. top n strongest RS with corresponding beams, n is an integer), UE may estimate RS timings on these n beams, and UE may report the timing information associated with specific beam/RS index, or UE may report the timing information for the earliest ToA among these RS/beams.The beams may include Tx beam at gNB for downlink, or, Rx beam at UE for downlink, or Tx beam at UE for uplink, or Rx beam at gNB for uplink.The RS for positioning may include but not limit to:SSB(synchronization sequence block), orPRS(positioning reference signal), orCSI-RS, orDMRS for PBCH, orPSS and/or SSS, orPRACH, orPUCCH, orSRS (sounding reference signal)The RS timing may be Tx timing or Rx timing, and Rx timing may be estimated from the first arrival path of a specific RSThe ToAs of RS with different beams may be normalized to a same time period unit for comparison, the time period unit may include but not limit to:Time slot, orOFDM symbol, orSubframe, orSystem frame

Example 3 may include if RS for positioning are transmitted or received via multiple Tx or Rx beams, network may indicate UE to estimate timing of RS whose RSRP/RSRQ/SINR are above a threshold, UE may estimate RS timings on these n beams, and UE may report the timing information associated with specific beam/RS index, or UE may report the timing information for the earliest ToA among these RS/beams.The beams may include Tx beam at gNB for downlink, or, Rx beam at UE for downlink, or Tx beam at UE for uplink, or Rx beam at gNB for uplink.The RS for positioning may include but not limit to:SSB(synchronization sequence block), orPRS(positioning reference signal), orCSI-RS, orDMRS for PBCH, orPSS and/or SSS, orPRACH, orPUCCH, orSRS (sounding reference signal)The RS timing may be Tx timing or Rx timing, and Rx timing may be estimated from the first arrival path of a specific RSThe ToAs of RS with different beams may be normalized to a same time period unit for comparison, the time period unit may include but not limit to:Time slot, orOFDM symbol, orSubframe, orSystem frame

Example 4 may include if RS for positioning are transmitted or received via multiple Tx or Rx beams, network may indicate a bitmap of RS/beam or index of RS/beam or pattern of RS/beam or RS/beam to UE to require UE measure the ToA on those RS/beam which are included in the bitmap/index/pattern, UE may estimate RS timings on these n beams, and UE may report the timing information associated with specific beam/RS index, or UE may report the timing information for the earliest ToA among these RS/beams.The beams may include Tx beam at gNB for downlink, or, Rx beam at UE for downlink, or Tx beam at UE for uplink, or Rx beam at gNB for uplink.The RS for positioning may include but not limit to:SSB(synchronization sequence block), orPRS(positioning reference signal), orCSI-RS, orDMRS for PBCH, orPSS and/or SSS, orPRACH, orPUCCH, orSRS (sounding reference signal)The RS timing may be Tx timing or Rx timing, and Rx timing may be estimated from the first arrival path of a specific RSThe ToAs of RS with different beams may be normalized to a same time period unit for comparison, the time period unit may include but not limit to:Time slot, orOFDM symbol, orSubframe, orSystem frame

Example 5: An apparatus of a first cellular communication device, comprising: a data storage device configured to store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by a second cellular communication device; and one or more processors configured to: process a received portion of the plurality of reference signals received from the second cellular communication device through at least a portion of the plurality of communication beams; normalize times of arrival (ToAs) of one or more reference signals of the received portion of the plurality of reference signals to a time period unit; and identify which of the plurality of communication beams correspond to the one or more reference signals using the reference signal data.

Example 6: The apparatus of Example 5, wherein the one or more processors are further configured to generate a report signal to be transmitted to the second cellular communication device, the report signal configured to indicate a normalized ToA of at least one of the one or more reference signals.

Example 7: The apparatus of Example 6, wherein a report signal indicates only the normalized ToA of the one or more reference signals of the received portion of the plurality of reference signals that has a earliest normalized ToA.

Example 8: The apparatus of Example 5, wherein the one or more reference signals include each reference signal of the received portion of the plurality of reference signals.

Example 9: The apparatus of Example 5, wherein the one or more reference signals include a subset of the received portion of the plurality of reference signals, the subset determined based on a signal quality of each reference signal of the received portion of the plurality of reference signals.

Example 10: The apparatus of Example 9, wherein the one or more processors are further configured to generate a report signal to be transmitted to the second cellular communication device, the report signal configured to indicate only a normalized ToA of a reference signal in the subset with an earliest normalized ToA.

Example 11: The apparatus of Example 9, wherein the one or more processors are further configured to generate a report signal to be transmitted to the second cellular communication device, the report signal configured to indicate only a normalized ToA of a reference signal in the subset with the strongest signal quality.

Example 12: The apparatus of Example 9, wherein the one or more processors are further configured to generate a report signal to be transmitted to the second cellular communication device, the report signal configured to indicate a normalized ToA of each reference signal in the subset.

Example 13: The apparatus of Example 9, wherein the subset includes a pre-determined number of the reference signals of the received portion of the plurality of reference signals with a highest signal quality.

Example 14: The apparatus of Example 9, wherein the subset includes any reference signals of the received portion of the plurality of reference signals with a signal quality above a pre-determined threshold.

Example 15: The apparatus of Example 9, wherein the signal quality of each of the plurality of reference signals in the received portion of the plurality of reference signals is determined using one or more measurements selected from the group consisting of Reference Signal Receive Power (RSRP), Reference Signal Receive Quality (RSRQ), and Signal to Interference and Noise Ratio (SINR).

Example 16: The apparatus of Example 5, wherein the data storage device is further configured to store a bitmap received from the second cellular communication device, the bitmap configured to indicate a subset of the plurality of reference signals that are allowed to be included in the one or more reference signals.

Example 17: The apparatus of Example 16, wherein the bitmap is configured to indicate the reference signals themselves, the communication beams corresponding to the reference signals, indexes of the reference signals or communication beams, patterns of the reference signals or beams, or combinations thereof corresponding to the subset of the plurality of reference signals.

Example 18: The apparatus of Example 5, wherein the one or more processors are configured to generate other reference signals to be sent to the second cellular communication device to enable the second cellular communication device to determine normalized ToAs of the other reference signals.

Example 19: The apparatus of Example 5, wherein the plurality of reference signals comprise Synchronization Signal Blocks (SSBs), Positioning Reference Signals (PRSs), Channel State Information Reference Signals (CSI-RSs), DeModulation Reference Signals for one or more Physical Broadcast Channels (DMRSs for PBCH), Primary Synchronization Signals (PSSs), Secondary Synchronization Signals (SSSs), Physical Random Access Channel (PRACH) signals, Physical Uplink Control Channel (PUCCH) signals, Sounding Reference Signals (SRSs), or combinations thereof.

Example 20: The apparatus of Example 5, wherein the time period unit comprises a time slot, an Orthogonal Frequency Division Multiplexing (ODFM) symbol, a subframe, or a system frame.

Example 21: An apparatus of a User Equipment (UE), comprising: a data storage device configured to store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by a cellular base station; and one or more processors configured to: process a received portion of the plurality of reference signals received from the cellular base station through at least a portion of the plurality of communication beams; normalize times of arrival (ToAs) of one or more reference signals of the received portion of the plurality of reference signals to a time period unit; identify which of the plurality of communication beams correspond to the one or more reference signals using the reference signal data; and generate a report signal to be transmitted to the cellular base station, the report signal configured to indicate an earliest normalized ToA of an earliest reference signal of the one or more reference signals.

Example 22: The apparatus of Example 21, wherein the report signal further includes a reference signal index identifying the earliest reference signal.

Example 23: An apparatus of a cellular base station, comprising: a data storage device configured to store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by an apparatus of a User Equipment (UE); and one or more processors configured to: process a received portion of the plurality of reference signals received from the UE through at least a portion of the plurality of communication beams; normalize times of arrival (ToAs) of one or more reference signals of the received portion of the plurality of reference signals to a time period unit; identify which of the plurality of communication beams correspond to the one or more reference signals using the reference signal data; determine an earliest normalized ToA of an earliest reference signal of the one or more reference signals; and select a communication beam of the portion of the plurality of communication beams for subsequent communication, the selected communication beam corresponding to the earliest normalized ToA.

Example 24: The apparatus of Example 23, wherein the one or more processors are further configured to generate an instruction signal to be transmitted to the UE, the instruction signal configured to instruct the UE to use the selected communication beam.

Example 25: The apparatus of Example 23, wherein the plurality of reference signals received from the UE comprise at least one Sounding Reference Signal (SRS).

Example 26: An apparatus of a User Equipment (UE), comprising: a data storage device configured to: store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams used by a cellular base station; and one or more processors configured to: process an indication received from the cellular base station, the indication indicating one or more reference signals of interest; process a received portion of the plurality of reference signals received from the cellular base station through at least a portion of the plurality of communication beams; identify a subset of the reference signals of the received portion of the plurality of reference signals that correspond to the one or more reference signals of interest; normalize times of arrival (ToAs) of the subset of the received reference signals of interest; and generate a report signal to be transmitted to the cellular base station, the report signal configured to indicate at least one normalized ToA corresponding to at least one of the received reference signals of interest.

Example 27: The apparatus of Example 26, wherein the report signal is configured to indicate a normalized ToA and a corresponding communication beam of the received reference signal of interest with an earliest normalized ToA.

Example 28: An apparatus of a cellular base station, comprising: a data storage device configured to: store reference signal data identifying a plurality of reference signals corresponding to a plurality of communication beams received from a User Equipment (UE); and store information indicating reference signals of interest; and one or more processors configured to: process a received portion of the plurality of reference signals received from the UE through at least a portion of the plurality of communication beams; identify a subset of the reference signals of the received portion of the plurality of reference signals that correspond to the one or more reference signals of interest; normalize times of arrival (ToAs) of the reference signals in the subset; and identify which of the plurality of communication beams correspond to the reference signals in the subset.

Example 29: The apparatus of Example 28, wherein the one or more processors are further configured to generate an instruction signal to be transmitted to the UE, the instruction signal configured to instruct the UE to use a specified communication beam.

Example 30: The apparatus of Example 28, wherein the reference signals of interest comprise Sounding Reference Signals (SRSs).

Example 31 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of Examples 1-30, or any other method or process described herein.

Example 34 may include a method, technique, or process as described in or related to any of Examples 1-30, or portions or parts thereof.

Example 36 may include a signal as described in or related to any of Examples 1-30, or portions or parts thereof.

Example 37 may include a signal in a wireless network as shown and described herein.

Example 39 may include a system for providing wireless communication as shown and described herein.

Example 40 may include a device for providing wireless communication as shown and described herein.

It will be apparent to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the disclosure. The scope of the present disclosure should, therefore, be determined only by the following claims.