Patent ID: 12213100

DETAILED DESCRIPTION

FIG.1illustrates an example NB-IoT system comprising a RAN node and a UE. The RAN node and the UE are configured to exchange radio signals. According to embodiments, the RAN node transmits signals received by the UE on a downlink and/or the UE transmits signals received by the RAN node on an uplink.

A UE that is an NB-IoT device generally needs to monitor the Narrowband Physical Downlink Control Channel (NPDCCH) to check whether a paging message is scheduled. However, when monitoring paging in the Rel-14 NB-IoT design on a non-anchor carrier, the NB-IoT device cannot assume that the Narrowband Reference Signal (NRS) is present. Such a design makes it difficult for an NB-IoT device to terminate NPDCCH decoding early when no paging message is being transmitted. This may increase UE power consumption in cells where the NPDCCH is configured with a large number of repetitions, as the UE has to monitor for a long time in order to determine whether the NPDCCH was sent by the network.

One way to address this problem is to allow a number of subframes to contain NRS prior to and/or within the NPDCCH search space of a paging occasion (PO). The purpose of such an approach may be to enable the UE to stop monitoring the NPDCCH search space of a given PO early, since the Downlink Control Information (DCI) would be monitored in such an approach such that the UE would know whether or not there is an upcoming paging message for that UE.

The particular number of subframes that should contain NRS prior to and/or within a PO may depend on a plurality of factors. In some embodiments, these factors include the number of consecutive subframes containing NRS before the PO (hereinafter referred to by the variable “M”) and the number of consecutive subframes containing NRS within the NPDCCH search space (hereinafter referred to by the variable “N”).

In determining appropriate values of M and N, it may be important to consider fulfilling certain principles when transmitting NRS in association with POs. It may also be important to consider certain principles when determining an appropriate decimation pattern. A decimation pattern is a pattern that determines which POs have subframes with NRS even when no NPDCCH is transmitted.

For example, in some embodiments, it may be advantageous for the decimation pattern to be fair across UEs, e.g., such that all UEs see the same (or similar) percentage of POs that include NRS. It may additionally or alternatively be advantageous for a UE belonging to a given group of UEs monitoring paging in the same PO are able to use the NRS belonging to a PO of a different group in addition to the NRS belonging to a PO of its own UE group. In some embodiments, it may be advantageous for the maximum gap between a PO with NRS and a PO that the UE monitors to not be larger than some threshold (e.g., to ensure that the UE can reliably estimate the signal-to-noise ratio (SNR) for NPDCCH early termination). In some embodiments, POs with NRS are quasi-uniformly or uniformly distributed from the UE perspective. Additionally or alternatively, in some embodiments, POs with NRS are quasi-uniformly or uniformly distributed from the network perspective. Moreover, in some embodiments, a subset of the POs have associated subframes which contain NRS even when no paging NPDCCH is transmitted.

Given the above, according to at least some embodiments, whether or not a decimation pattern applies and/or the particular decimation pattern itself, may be based on the number of POs in a discontinuous reception (DRX) cycle.

Consider an example in which the DRX cycle of a UE is referred to by the variable “T.” The default value of T is transmitted in the System Information Block 2 (SIB2). This default cannot be overwritten by a UE specific value. Particular example values of T that may be advantageous in particular embodiments are 128, 256, 512, and 1024 radio frames.

The number of POs in a DRX cycle (hereinafter referred to by the variable “nB”) can be expressed in terms of T and broadcast in the System Information Block (SIB). For example, values of nB may be 4T, 2T, T, ½T, ¼T, ⅛T, 1/16T, 1/32T, 1/64T, 1/128T, 1/256T, 1/512T, and 1/1024T.

Accordingly, the decimation pattern of particular embodiments may be based on nB as compared to some threshold (e.g., T/2). For example, when nB is less than a threshold, then all POs may have NRS (i.e., no decimation pattern is applied). When nB is greater than or equal to the threshold, then a decimation pattern is applied, which may depend on the particular value of nB. That is, each nB value at or above the threshold may have a specified decimation pattern. In either case, the particular values of M and/or N may be different for different numbers of POs within a DRX cycle. Alternatively, the values of M and N may be the same for all values of nB below the threshold.

Using a decimation pattern in some cases and not in others as discussed above may be appropriate depending on certain circumstances. For example, when the presence of POs is high (e.g., when nB>=T/2), POs may be close together or even adjacent. As such, it is likely that not all POs will have NRS, and a decimation pattern is appropriate. In contrast, when the presence of POs is sparse in time (e.g., when nB<T/2), then a decimation pattern may be unnecessary or disadvantageous, as all POs may have associated subframes containing NRS.

Given the above, the values of M and N may be specified in order to handle both sparse and non-sparse PO scenarios. For example, sparse PO scenarios may use values of M and N such that M+N=10. Correspondingly, non-sparse scenarios may use values of M and N, and a decimation pattern, that guarantee 10 subframes with NRS near every PO from the network perspective after the decimation pattern is applied. As discussed above, each value of nB may be associated with a corresponding decimation pattern and values of M and N.

Although many different arrangements of NRS may be used according to various embodiments, in general, it may be advantageous to avoid significant NRS gaps (e.g., regardless of whether or not POs are sparse).

UEs are generally permitted to enter into the system at any time. Accordingly, a reference timing for the decimation pattern on POs with associated NRS needs to be defined. To handle the non-sparse scenario (e.g., when nB>=T/2), one potential solution for applying a decimation pattern may include using an offset with respect to a UE's previous POs. This enables UEs monitoring different POs to have an almost equal chance to have NRS associated with its PO after decimation. Further, a UE can use the NRS associated with other UEs' POs also.

However, this approach has some significant flaws. For example, under such an approach it is not clear how the offset can be derived by the UE when the UE is allowed to enter the cell at any arbitrary time. That is, it is unclear how the UE can determine the offset if the offset is defined with respect to previous POs. Indeed, such a solution, by itself, does not address how the UE can identify the first (or previous) PO, not to mention determining an offset relative to a previous PO.

To handle the sparse scenario (e.g., when nB<T/2), one solution is to merely designate a static, predefined value for M (e.g., M=8). However, this approach also has significant flaws. In particular, such an approach is quite inflexible, especially considering the NB-IoT in-band system likely will have to co-exist with other Long Term Evolution (LTE) services. A more flexible solution that improves the co-existence between NB-IoT and LTE would be beneficial.

Moreover, for both the sparse and non-sparse PO presence cases, the separate or joint usage of the variables “M” and “N” (which denote the presence of NRS prior and within the NPDCCH search space) may lead to a discontinuous presence (i.e., gap) of NRS.

By signaling the starting subframe of “M” (i.e., the start of the subframes containing NRS prior to the NPDCCH search space), embodiments of the present disclosure prevent a gap from disrupting the presence of NRS. Signaling the starting subframe of “M” to avoid a gap in the presence of NRS is applicable to both a sparse and a non-sparse presence of POs. Such a solution can be applied if “M” is used alone to provide the number of subframes containing NRS, or if both “M+N” are used to provide the number of subframes containing NRS.

Such a solution can further be used when a set of decimation patterns for POs with associated NRS built on subframe patterns are defined in advance, and the System Frame Number (SFN) is used as reference timing for determining when decimation applies and when decimation does not apply. Moreover, such a solution supports the PO always having in vicinity (i.e., earlier or later in time, depending on the usage of “M” and “N”) a configurable number of subframes containing NRS. The starting point of the decimation pattern can be cell-ID dependent or explicitly signaled by the RAN Node (e.g., the eNodeB). Accordingly, to avoid having gaps disrupting the presence of NRS, for both a sparse and a non-sparse presence of POs, embodiments of the present disclosure signal the starting subframe of “M”.

On the network side, a simple example embodiment may determine if a decimation pattern is to be used, and if so, provide a decimation pattern for NRS transmission based upon SFN, and provide the values of M and/or N. If not, then the network may provide the value of M and/or N such that M and N does not create a gap (i.e., a non-NRS containing subframe).

On the UE side, a simple example embodiment may determine, from the SIB, whether the UE is camped on a non-anchor carrier. Further, the UE may determine whether a decimation pattern applies from an nB value in the SIB. The UE may also obtain an SFN that contains NRS based by applying an SFN based formula, and obtain a subframe containing NRS based on M and/or N.

Advantageously, the decimation pattern on POs with associated NRS uses the SFN as reference timing as to known when (and in some embodiments, in which paging radio frame) the decimation applies and when it doesn't. A UE can enter into the system at any-time, and depending on the SFN and the decimation pattern the UE may either immediately have NRS subframes associated to its PO or a subsequent PO. The decimation pattern on POs with associated NRS may account for subframe patterns that defined in existing specifications, e.g., to allow for the presence of the POs per paging radio frame, which may be different depending on the number of UE groups. Further, by signaling the starting subframe of “M” (subframes containing NRS prior the NPDCCH search space), a gap disrupting the presence of NRS can be avoided. Indeed, signaling the starting subframe of “M” to avoid a gap in the presence of NRS may be applied when POs are sparse, when POs are not sparse, or both. Moreover, the solution can be applied if “M” is used alone to provide the number of subframes containing NRS, or if both “M+N” are used to provide the number of subframes containing NRS. Example embodiments will now be provided in which certain additional parameters will be used. According to such example, for sake of explanation and without limitation, the parameter UE_ID is a UE identifier determined by taking its International Mobile Subscriber Identity (IMSI) mod 4096. In addition, a Paging Frame (PF) is given by the equation SFN mod T=(T div N)*(UE_ID mod N), wherein N is the lesser of T and nB.

The PO subframe may be obtained using a table such as the one illustrated inFIG.2based on the values of Ns and i_s. For purposes of explanation and not limitation, Ns is the greater of 1 and nB/T, whereas i_s is given by floor (UE_ID/N) mod Ns.

In the table ofFIG.2, Ns refers to whether there is one, two, or four UE groups, whereas “i_s” (which can be equal to 0, 1, 2, or 3) refers to the actual UE groups. In the table, the value corresponding to the coordinates given by “Ns” and “i_s” indicates the subframe to which the PO is mapped. For example, when Ns=1 (i.e., there is only one UE group) and i_s=0 (i.e., the UE group is Group 0), then the PO is mapped to a paging radio frame in subframe number9.

According to embodiments of the present disclosure, when POs are sparse in time, a decimation pattern is not applied and ten consecutive subframes containing NRS are used. The values of M and N (as discussed above) may vary, provided that they add up to ten.

When both M and N are non-zero values, it may be important to know the starting point of M, which refers to the subframes containing NRS prior to the NPDCCH search space of a PO. The NB-IoT frame structures illustrated inFIGS.3A and3Bdistinguish between two different situations that depend upon the starting point of M.

FIG.3Aillustrates an example in which M creates a gap. In this example, M starts from the leftmost subframe and both “M” and “N” are ≠0. Given that the NB-IoT frames each comprise ten subframes, these circumstances will always produce a gap between the M subframes and the N subframes. For illustration purposes, nB=T/4 in this example, whereas M and N are both set to 5 such that M+N=10 is fulfilled.

FIG.3Balso illustrates an example in which nB=T/4 and in which M and N are both set to 5 such that M+N=10 is fulfilled. However, in contrast toFIG.3A,FIG.3Billustrates an example in which M does not create a gap. In the example ofFIG.3B, M is flushed to the right such that one of its subframes is adjacent to the PO and both M and N are #0. When this occurs, there will always be a contiguous transmission of NRS with no gap between M and N.

Embodiments of the present disclosure ensure that M and N are adjacent to each other under sparse PO conditions, such that there is no gap (i.e., intervening subframe) between M and N. In some embodiments, M and N can respectively have the values ten and zero (or vice versa) to fulfill with the condition M+N=10, thereby producing no gap. Such an embodiment produces either ten subframes in a row containing NRS ending at the PO or 10 subframes in a row containing NRS starting at the PO within the NPDCCH search space.

In other embodiments, M and N are both non-zero, M is flushed to the right such that the M subframes are adjacent to the N subframes, and M and N may be any combination of values between one and nine such that the condition M+N=10 is fulfilled.

In yet other embodiments, M and N may be any combination of values between one and nine such that the condition M+N=10 is fulfilled, and the starting subframe of M is signaled such that M and N are adjacent to each other.

Other embodiments are directed to conditions in which POs are abundant (i.e., when POs are not sparse). In such embodiments, a decimation pattern is applied. Continuing with the example in which the threshold for determining whether POs are sparse or non-sparse is T/2, non-sparse scenarios may include nB=4T, 2T, T, and T/2, which encompasses the presence of four UE groups (when nB=4T), two UE groups (when nB=2T), and one UE group (when nB=T or nB=T/2). Each of these scenarios may require applying a different respective decimation pattern.

To avoid timing ambiguities between the UE and the RAN node, in some embodiments, the decimation pattern is determined based on a common timing reference (e.g., SFN) or a predetermined timing (e.g., an absolute starting time). Although SFN is used as example to describe embodiments using a common timing reference, the embodiments of this disclosure are not limited to this particular common timing reference. Indeed, the SFN can be replaced with any other timing reference that is commonly common determined, unambiguously, between a UE and a RAN node.

A set of decimation patterns for POs with associated NRS may be built on subframe patterns and use SFN as the reference timing. The general form of the SFN that contains NRS subframes that can be used by a UE at a PO may be described by the equation:

SFNN⁢R⁢S=(⌊(a-SFNb)-c⌋*d)+e(1)
and in some cases as:

SFNNRS=(f+⌊SFN-gh⌋*i)(2)
where a, b, c, d, e, f, g, h and i are integers. Also, if allowed, one or more of a, b c, d, e, f, g, h, and i can be set to 0. Moreover, the selection of one or more of the integer numbers in the above equations may depend on the cell-ID and/or one or more of the integer numbers in the above equations may be updated via higher layer signaling.

Example decimation patterns for two UE groups (e.g., when nB=2T) and one UE group (e.g., when nB=T or when nB=T/2) are described below. Note that the decimation pattern of a particular UE group may be different when there are different numbers of UE groups. For example, the decimation patterns of UE groups 0 and 1 when there are two UE groups may be different when there are four UE groups instead.

FIG.4illustrates an example decimation pattern for two UE groups (e.g., nB=2T) in which only two subframes containing NRS are associated with a given PO, if any. Although only two subframes are associated with each PO having subframes containing NRS associated, other embodiments may have a different number of subframes containing NRS associated (e.g., a configurable number of subframes containing NRS between 1 and 4).

In the example ofFIG.4, a four subframe pattern is illustrated. The four subframe pattern repeats as the SFN changes, such that no offset need be specified.

According to embodiments involving two UE groups, when SFN mod 4 is equal to 0 or 1, UE group 0 is active and UE group 1 has both M and N configured to zero. For UE group 0 at SFN mod 4=0, M is non-zero (e.g., configured to either 1, 2, 3, or 4) and N is zero for UE group 0. For UE group 0 at SFN mod 4=1, N is non-zero (e.g., configured to either 1, 2, 3, or 4) and M is zero.

Correspondingly, when SFN mod 4 is equal to 2 or 3, UE group 1 is active and UE group 0 has both M and N configured to zero. For UE group 1 at SFN mod 4=2, N is non-zero (e.g., configured to either 1, 2, 3, or 4) and M is zero. For UE group 1 at SFN mod 4=3, M is non-zero (e.g., configured to either 1, 2, 3, or 4) and N is zero.

Expressed differently, when

SFN=⌊❘"\[LeftBracketingBar]"(4-SFN4)-1❘"\[RightBracketingBar]"⌋*4,
then UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 while setting N=0, whereas UE group 1 sets both M and N to 0. When

SFN=(⌊❘"\[LeftBracketingBar]"(4-SFN4)-1❘"\[RightBracketingBar]"⌋*4)+1,
then UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0, whereas UE group 1 sets both “M” and “N” to 0. When

SFN=2+(⌊❘"\[LeftBracketingBar]"(6-SFN6)-1❘"\[RightBracketingBar]"⌋*4),
then UE group 1 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 while setting M=0, whereas UE group 0 sets both M and N to 0. When

SFN=(2+(⌊❘"\[LeftBracketingBar]"(6-SFN6)-1❘"\[RightBracketingBar]"⌋*4))+1,
then UE group 1 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 while setting N=0, whereas UE group 0 sets both M and N to 0.

Decimation patterns consistent with the above andFIG.4may guarantee that near every PO there will be either 1, 2, 3, or 4 subframes that contain NRS, depending on the configuration of M and N which alternate according to a pattern. In some embodiments, the configuration of M is consistent for odd radio frames and the configuration of N is consistent for even radio frames, or vice versa.

The decimation pattern of UE group 0 under single UE group scenarios (e.g., nB=T and nB=T/2) may be different than that which UE group 0 has in two and/or four UE group scenarios, for example.FIGS.5A and5Billustrate example decimation patterns for one UE group using four and eight subframes (respectively) that contain NRS associated to a given PO. As with other of the example scenarios above, the number of subframes containing NRS in this example are configurable to a value from 1 to 4. The pattern shown inFIG.5Amay be appropriate when nB=T, whereas the pattern inFIG.5Bmay be appropriate when nB=T/2.

According to embodiments involving one UE group, when SFN mod 4 is equal to 0, N is non-zero (e.g., configured to either 1, 2, 3, or 4) and M is zero. When SFN mod 4 is equal to 3, M is non-zero (e.g., configured to either 1, 2, 3, or 4) and N is zero. Otherwise, both M and N are zero.

Expressed differently, when

SFN=⌊❘"\[LeftBracketingBar]"(4-SFN4)-1❘"\[RightBracketingBar]"⌋*4,
then UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0. When

SFN=(2+(⌊❘"\[LeftBracketingBar]"(6-SFN6)-1❘"\[RightBracketingBar]"⌋*4))+1,
then UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 and N=0.

As with previous examples, in the example ofFIG.5A, the four subframe pattern repeats as the SFN changes, such that no offset need be specified. In some embodiments, the decimation pattern rotates within a DRX cycle the presence of NRS in odd and even radio frames, and guarantees that nearby every PO there will be either 1, 2, 3, or 4 subframes containing NRS. In some embodiments, the number of subframes will depend on the configuration of M and N in the odd and even radio frames respectively.

FIG.5Billustrates an example in which POs are at the limit of being considered a sparse case (e.g., when nB=T/2) and in which POs are limited to even radio frames. Thus, using odd and even radio frames to rotate the location of the subframes containing NRS is not possible. Thus, the decimation pattern applies on even radio frames only.

According to embodiments consistent withFIG.5B, when SFN mod 8 is equal to 2, M is non-zero (e.g., configured to either 1, 2, 3, or 4) and N is zero. When SFN mod 8 is equal to 4, N is non-zero (e.g., configured to either 1, 2, 3, or 4) and M is zero. Otherwise, both M and N are zero.

Expressed differently, when

SFN=(2+⌊SFN-28⌋*8),
then the UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 and setting N=0. When

SFN=(4+⌊SFN-48⌋*8)
then the UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0. Alternatively, M can be configured to be either 1, 2, 3, or 4 and N can be set to zero.

As with previous examples, no offset is required, since the SFN-based operations are used to alternate the presence of NRS.

According to embodiments, the Cell_ID can be used to alternate the starting point of the decimation pattern.FIGS.6A and6Billustrate example decimation patterns for One UE group when nB=T/2. The example ofFIG.6Areflects the decimation pattern when the Cell_ID is odd, whereas the example ofFIG.6Breflects the decimation pattern when the Cell_ID is even.

As shown inFIG.6A(i.e., the odd Cell_ID example), when SFN mod 8=2, M is set to either 1, 2, 3, or 4, and N is set to zero. When SFN mod 8=4, M is set to zero and N is set to either 1, 2, 3, or 4.

Expressed differently, when

SFN==(2+⌊SFN-28⌋*8),
then the UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 and setting N=0. When

SFN==(4+⌊SFN-48⌋*8),

then the UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0.

In contrast, as shown inFIG.6B(i.e., the even Cell_ID example), when SFN mod 8=0, N is set to either 1, 2, 3, or 4, and M is set to zero. When SFN mod 8=6, N is set to zero and M is set to either 1, 2, 3, or 4.

Expressed differently, when

SFN==(⌊SFN8⌋*8),
then the UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0. When

SFN==(6+⌊SFN-68⌋*8),
then the UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 and setting N=0.

Alternatively, a default configuration can specify that the values X=2 and Y=4 are to be applied such that when

SFN==(X+⌊SFN-X8⌋*8),
then the UE group 0 will have subframes containing NRS by configuring M to be either 1, 2, 3, or 4 and setting N=0, whereas when

SFN==(Y+⌊SFN-Y8⌋*8),

then the UE group 0 will have subframes containing NRS by configuring N to be either 1, 2, 3, or 4 and setting M=0. The values of X and Y may subsequently be changed by the network to shift the decimation pattern as desired. For example, if at some point the network wants to change the location of the NRS, it can broadcast X=0 and Y=6.

In view of all of the above, embodiments of the present disclosure include a method400implemented by a UE700(e.g., a wireless terminal), as shown inFIG.7. The method400comprises determining paging occasions that are associated with an NRS from a plurality of paging occasions based on a common timing reference between a RAN node600and the UE700(block410). In some embodiments, the method400further comprises monitoring consecutive subframes for the NRS based on a first value indicating how many of the consecutive subframes that precede the paging occasions associated with the NRS to monitor (block420).

Other embodiments of the present disclosure include a method430implemented by a RAN node600(e.g., an NB-IoT base station) as shown inFIG.8. The method430comprises transmitting, to a UE700, an NRS on paging occasions based on a common timing reference between the RAN node600and the UE700(block440). In some embodiments, the method430further comprises transmitting, to the UE700, a first value indicating how many consecutive subframes preceding the paging occasions to monitor for the NRS (block435).

Other embodiments of the present disclosure include a UE700, as shown inFIG.9. The UE ofFIG.9comprises processing circuitry710and interface circuitry730. The processing circuitry710is communicatively coupled to the interface circuitry730, e.g., via one or more buses. In some embodiments, the proxy server700further comprises memory circuitry720that is communicatively coupled to the processing circuitry710, e.g., via one or more buses. According to particular embodiments, the processing circuitry710is configured to perform one or more of the methods described herein (e.g., the method400).

Other embodiments of the present disclosure include a RAN node600, as shown inFIG.10. The RAN node600ofFIG.10comprises processing circuitry610and interface circuitry630. The processing circuitry610is communicatively coupled to the interface circuitry630, e.g., via one or more buses. In some embodiments, the network node600further comprises memory circuitry620that is communicatively coupled to the processing circuitry610, e.g., via one or more buses. According to particular embodiments, the processing circuitry610is configured to perform one or more of the methods described herein (e.g., the method430).

The processing circuitry610,710of each device600,700may comprise one or more microprocessors, microcontrollers, hardware circuits, discrete logic circuits, hardware registers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or a combination thereof. For example, the processing circuitry610,710may be programmable hardware capable of executing software instructions of a respective computer program660,760stored in respective memory circuitry620,720whereby the corresponding processing circuitry610,710is configured. The memory circuitry620,720of the various embodiments may comprise any non-transitory machine-readable media known in the art or that may be developed, whether volatile or non-volatile, including but not limited to solid state media (e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, flash memory, solid state drive, etc.), removable storage devices (e.g., Secure Digital (SD) card, miniSD card, microSD card, memory stick, thumb-drive, USB flash drive, ROM cartridge, Universal Media Disc), fixed drive (e.g., magnetic hard disk drive), or the like, wholly or in any combination.

The interface circuitry630,730may be a controller hub configured to control the input and output (I/O) data paths of its respective device600,700. Such I/O data paths may include data paths for exchanging signals over a communications network, data paths for exchanging signals with a user, and/or data paths for exchanging data internally among components of the device600,700. For example, the interface circuitry630,730may comprise a transceiver configured to send and receive communication signals over one or more of a cellular network, Ethernet network, or optical network. The interface circuitry630,730may be implemented as a unitary physical component, or as a plurality of physical components that are contiguously or separately arranged, any of which may be communicatively coupled to any other, or may communicate with any other via the processing circuitry610,710. For example, the interface circuitry630,730may comprise transmitter circuitry640,740configured to send communication signals over a communications network and receiver circuitry650,750configured to receive communication signals over the communications network. Other embodiments may include other permutations and/or arrangements of the above and/or their equivalents.

According to embodiments of the UE700, the processing circuitry710is configured to determine paging occasions that are associated with an NRS from a plurality of paging occasions based on a common timing reference between a RAN node600and the UE700.

According to embodiments of the RAN node600, the processing circuitry610is configured to transmit, to a UE700, an NRS on paging occasions based on a common timing reference between the RAN node600and the UE700.

Other embodiments of the present disclosure include corresponding computer programs. In one such embodiment, the computer program comprises instructions which, when executed on processing circuitry of a RAN node600, cause the RAN node device600to carry out any of the processing described above with respect to a RAN node600. In another such embodiment, the computer program comprises instructions which, when executed on processing circuitry of a UE700, cause the UE700to carry out any of the processing described above with respect to a UE700. A computer program in either regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Additional embodiments will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG.11. For simplicity, the wireless network ofFIG.11only depicts network1106, network nodes1160and1160b, and WDs1110,1110b, and1110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node1160and wireless device (WD)1110are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-IoT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or Zig Bee standards.

Network1106may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node1160and WD1110comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

InFIG.11, network node1160includes processing circuitry1170, device readable medium1180, interface1190, auxiliary equipment1184, power source1186, power circuitry1187, and antenna1162. Although network node1160illustrated in the example wireless network ofFIG.11may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node1160are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium1180may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node1160may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node1160comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node1160may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium1180for the different RATs) and some components may be reused (e.g., the same antenna1162may be shared by the RATs). Network node1160may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node1160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node1160.

Processing circuitry1170is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry1170may include processing information obtained by processing circuitry1170by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry1170may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node1160components, such as device readable medium1180, network node1160functionality. For example, processing circuitry1170may execute instructions stored in device readable medium1180or in memory within processing circuitry1170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry1170may include a system on a chip (SOC).

In some embodiments, processing circuitry1170may include one or more of radio frequency (RF) transceiver circuitry1172and baseband processing circuitry1174. In some embodiments, radio frequency (RF) transceiver circuitry1172and baseband processing circuitry1174may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry1172and baseband processing circuitry1174may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry1170executing instructions stored on device readable medium1180or memory within processing circuitry1170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry1170without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry1170can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1170alone or to other components of network node1160, but are enjoyed by network node1160as a whole, and/or by end users and the wireless network generally.

Device readable medium1180may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry1170. Device readable medium1180may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry1170and, utilized by network node1160. Device readable medium1180may be used to store any calculations made by processing circuitry1170and/or any data received via interface1190. In some embodiments, processing circuitry1170and device readable medium1180may be considered to be integrated.

Interface1190is used in the wired or wireless communication of signaling and/or data between network node1160, network1106, and/or WDs1110. As illustrated, interface1190comprises port(s)/terminal(s)1194to send and receive data, for example to and from network1106over a wired connection. Interface1190also includes radio front end circuitry1192that may be coupled to, or in certain embodiments a part of, antenna1162. Radio front end circuitry1192comprises filters1198and amplifiers1196. Radio front end circuitry1192may be connected to antenna1162and processing circuitry1170. Radio front end circuitry may be configured to condition signals communicated between antenna1162and processing circuitry1170. Radio front end circuitry1192may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1192may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1198and/or amplifiers1196. The radio signal may then be transmitted via antenna1162. Similarly, when receiving data, antenna1162may collect radio signals which are then converted into digital data by radio front end circuitry1192. The digital data may be passed to processing circuitry1170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node1160may not include separate radio front end circuitry1192, instead, processing circuitry1170may comprise radio front end circuitry and may be connected to antenna1162without separate radio front end circuitry1192. Similarly, in some embodiments, all or some of RF transceiver circuitry1172may be considered a part of interface1190. In still other embodiments, interface1190may include one or more ports or terminals1194, radio front end circuitry1192, and RF transceiver circuitry1172, as part of a radio unit (not shown), and interface1190may communicate with baseband processing circuitry1174, which is part of a digital unit (not shown).

Antenna1162may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna1162may be coupled to radio front end circuitry1190and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna1162may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna1162may be separate from network node1160and may be connectable to network node1160through an interface or port.

Antenna1162, interface1190, and/or processing circuitry1170may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna1162, interface1190, and/or processing circuitry1170may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry1187may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node1160with power for performing the functionality described herein. Power circuitry1187may receive power from power source1186. Power source1186and/or power circuitry1187may be configured to provide power to the various components of network node1160in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source1186may either be included in, or external to, power circuitry1187and/or network node1160. For example, network node1160may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry1187. As a further example, power source1186may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry1187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node1160may include additional components beyond those shown inFIG.11that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node1160may include user interface equipment to allow input of information into network node1160and to allow output of information from network node1160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node1160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device1110includes antenna1111, interface1114, processing circuitry1120, device readable medium1130, user interface equipment1132, auxiliary equipment1134, power source1136and power circuitry1137. WD1110may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD1110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD1110.

Antenna1111may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface1114. In certain alternative embodiments, antenna1111may be separate from WD1110and be connectable to WD1110through an interface or port. Antenna1111, interface1114, and/or processing circuitry1120may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna1111may be considered an interface.

As illustrated, interface1114comprises radio front end circuitry1112and antenna1111. Radio front end circuitry1112comprise one or more filters1118and amplifiers1116. Radio front end circuitry1114is connected to antenna1111and processing circuitry1120, and is configured to condition signals communicated between antenna1111and processing circuitry1120. Radio front end circuitry1112may be coupled to or a part of antenna1111. In some embodiments, WD1110may not include separate radio front end circuitry1112; rather, processing circuitry1120may comprise radio front end circuitry and may be connected to antenna1111. Similarly, in some embodiments, some or all of RF transceiver circuitry1122may be considered a part of interface1114. Radio front end circuitry1112may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1112may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1118and/or amplifiers1116. The radio signal may then be transmitted via antenna1111. Similarly, when receiving data, antenna1111may collect radio signals which are then converted into digital data by radio front end circuitry1112. The digital data may be passed to processing circuitry1120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry1120may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD1110components, such as device readable medium1130, WD1110functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry1120may execute instructions stored in device readable medium1130or in memory within processing circuitry1120to provide the functionality disclosed herein.

As illustrated, processing circuitry1120includes one or more of RF transceiver circuitry1122, baseband processing circuitry1124, and application processing circuitry1126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry1120of WD1110may comprise a SOC. In some embodiments, RF transceiver circuitry1122, baseband processing circuitry1124, and application processing circuitry1126may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry1124and application processing circuitry1126may be combined into one chip or set of chips, and RF transceiver circuitry1122may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry1122and baseband processing circuitry1124may be on the same chip or set of chips, and application processing circuitry1126may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry1122, baseband processing circuitry1124, and application processing circuitry1126may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry1122may be a part of interface1114. RF transceiver circuitry1122may condition RF signals for processing circuitry1120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry1120executing instructions stored on device readable medium1130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry1120without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry1120can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1120alone or to other components of WD1110, but are enjoyed by WD1110as a whole, and/or by end users and the wireless network generally.

Processing circuitry1120may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry1120, may include processing information obtained by processing circuitry1120by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD1110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium1130may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry1120. Device readable medium1130may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry1120. In some embodiments, processing circuitry1120and device readable medium1130may be considered to be integrated.

User interface equipment1132may provide components that allow for a human user to interact with WD1110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment1132may be operable to produce output to the user and to allow the user to provide input to WD1110. The type of interaction may vary depending on the type of user interface equipment1132installed in WD1110. For example, if WD1110is a smart phone, the interaction may be via a touch screen; if WD1110is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment1132may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment1132is configured to allow input of information into WD1110, and is connected to processing circuitry1120to allow processing circuitry1120to process the input information. User interface equipment1132may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment1132is also configured to allow output of information from WD1110, and to allow processing circuitry1120to output information from WD1110. User interface equipment1132may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment1132, WD1110may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment1134is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment1134may vary depending on the embodiment and/or scenario.

Power source1136may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD1110may further comprise power circuitry1137for delivering power from power source1136to the various parts of WD1110which need power from power source1136to carry out any functionality described or indicated herein. Power circuitry1137may in certain embodiments comprise power management circuitry. Power circuitry1137may additionally or alternatively be operable to receive power from an external power source; in which case WD1110may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry1137may also in certain embodiments be operable to deliver power from an external power source to power source1136. This may be, for example, for the charging of power source1136. Power circuitry1137may perform any formatting, converting, or other modification to the power from power source1136to make the power suitable for the respective components of WD1110to which power is supplied.

FIG.12illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE1200may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE1200, as illustrated inFIG.12, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, althoughFIG.12is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

InFIG.12, UE1200includes processing circuitry1201that is operatively coupled to input/output interface1205, radio frequency (RF) interface1209, network connection interface1211, memory1215including random access memory (RAM)1217, read-only memory (ROM)1219, and storage medium1221or the like, communication subsystem1231, power source1233, and/or any other component, or any combination thereof. Storage medium1221includes operating system1223, application program1225, and data1227. In other embodiments, storage medium1221may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.12, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.12, processing circuitry1201may be configured to process computer instructions and data. Processing circuitry1201may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry1201may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface1205may be configured to provide a communication interface to an input device, output device, or input and output device. UE1200may be configured to use an output device via input/output interface1205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE1200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE1200may be configured to use an input device via input/output interface1205to allow a user to capture information into UE1200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

InFIG.12, RF interface1209may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface1211may be configured to provide a communication interface to network1243a. Network1243amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network1243amay comprise a Wi-Fi network. Network connection interface1211may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface1211may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM1217may be configured to interface via bus1202to processing circuitry1201to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM1219may be configured to provide computer instructions or data to processing circuitry1201. For example, ROM1219may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium1221may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium1221may be configured to include operating system1223, application program1225such as a web browser application, a widget or gadget engine or another application, and data file1227. Storage medium1221may store, for use by UE1200, any of a variety of various operating systems or combinations of operating systems.

Storage medium1221may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium1221may allow UE1200to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium1221, which may comprise a device readable medium.

InFIG.12, processing circuitry1201may be configured to communicate with network1243busing communication subsystem1231. Network1243aand network1243bmay be the same network or networks or different network or networks. Communication subsystem1231may be configured to include one or more transceivers used to communicate with network1243b. For example, communication subsystem1231may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.12, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter1233and/or receiver1235to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter1233and receiver1235of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem1231may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem1231may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network1243bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network1243bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source1213may be configured to provide alternating current (AC) or direct current (DC) power to components of UE1200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE1200or partitioned across multiple components of UE1200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem1231may be configured to include any of the components described herein. Further, processing circuitry1201may be configured to communicate with any of such components over bus1202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry1201perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry1201and communication subsystem1231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG.13is a schematic block diagram illustrating a virtualization environment1300in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments1300hosted by one or more of hardware nodes1330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications1320(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications1320are run in virtualization environment1300which provides hardware1330comprising processing circuitry1360and memory1390. Memory1390contains instructions1395executable by processing circuitry1360whereby application1320is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment1300, comprises general-purpose or special-purpose network hardware devices1330comprising a set of one or more processors or processing circuitry1360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory1390-1which may be non-persistent memory for temporarily storing instructions1395or software executed by processing circuitry1360. Each hardware device may comprise one or more network interface controllers (NICs)1370, also known as network interface cards, which include physical network interface1380. Each hardware device may also include non-transitory, persistent, machine-readable storage media1390-2having stored therein software1395and/or instructions executable by processing circuitry1360. Software1395may include any type of software including software for instantiating one or more virtualization layers1350(also referred to as hypervisors), software to execute virtual machines1340as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines1340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer1350or hypervisor. Different embodiments of the instance of virtual appliance1320may be implemented on one or more of virtual machines1340, and the implementations may be made in different ways.

During operation, processing circuitry1360executes software1395to instantiate the hypervisor or virtualization layer1350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer1350may present a virtual operating platform that appears like networking hardware to virtual machine1340.

As shown inFIG.13, hardware1330may be a standalone network node with generic or specific components. Hardware1330may comprise antenna13225and may implement some functions via virtualization. Alternatively, hardware1330may be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)13100, which, among others, oversees lifecycle management of applications1320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine1340may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines1340, and that part of hardware1330that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines1340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines1340on top of hardware networking infrastructure1330and corresponds to application1320inFIG.13.

In some embodiments, one or more radio units13200that each include one or more transmitters13220and one or more receivers13210may be coupled to one or more antennas13225. Radio units13200may communicate directly with hardware nodes1330via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system13230which may alternatively be used for communication between the hardware nodes1330and radio units13200.

FIG.14illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference toFIG.14, in accordance with an embodiment, a communication system includes telecommunication network1410, such as a 3GPP-type cellular network, which comprises access network1411, such as a radio access network, and core network1414. Access network1411comprises a plurality of base stations1412a,1412b,1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area1413a,1413b,1413c. Each base station1412a,1412b,1412cis connectable to core network1414over a wired or wireless connection1415. A first UE1491located in coverage area1413cis configured to wirelessly connect to, or be paged by, the corresponding base station1412c. A second UE1492in coverage area1413ais wirelessly connectable to the corresponding base station1412a. While a plurality of UEs1491,1492are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station1412.

Telecommunication network1410is itself connected to host computer1430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, and a distributed server or as processing resources in a server farm. Host computer1430may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections1421and1422between telecommunication network1410and host computer1430may extend directly from core network1414to host computer1430or may go via an optional intermediate network1420. Intermediate network1420may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network1420, if any, may be a backbone network or the Internet; in particular, intermediate network1420may comprise two or more sub-networks (not shown).

The communication system ofFIG.14as a whole enables connectivity between the connected UEs1491,1492and host computer1430. The connectivity may be described as an over-the-top (OTT) connection1450. Host computer1430and the connected UEs1491,1492are configured to communicate data and/or signaling via OTT connection1450, using access network1411, core network1414, any intermediate network1420and possible further infrastructure (not shown) as intermediaries. OTT connection1450may be transparent in the sense that the participating communication devices through which OTT connection1450passes are unaware of routing of uplink and downlink communications. For example, base station1412may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer1430to be forwarded (e.g., handed over) to a connected UE1491. Similarly, base station1412need not be aware of the future routing of an outgoing uplink communication originating from the UE1491towards the host computer1430.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.15.FIG.15illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system1500, host computer1510comprises hardware1515including communication interface1516configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1500. Host computer1510further comprises processing circuitry1518, which may have storage and/or processing capabilities. In particular, processing circuitry1518may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer1510further comprises software1511, which is stored in or accessible by host computer1510and executable by processing circuitry1518. Software1511includes host application1512. Host application1512may be operable to provide a service to a remote user, such as UE1530connecting via OTT connection1550terminating at UE1530and host computer1510. In providing the service to the remote user, host application1512may provide user data which is transmitted using OTT connection1550.

Communication system1500further includes base station1520provided in a telecommunication system and comprising hardware1525enabling it to communicate with host computer1510and with UE1530. Hardware1525may include communication interface1526for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1500, as well as radio interface1527for setting up and maintaining at least wireless connection1570with UE1530located in a coverage area (not shown inFIG.15) served by base station1520. Communication interface1526may be configured to facilitate connection1560to host computer1510. Connection1560may be direct or it may pass through a core network (not shown inFIG.15) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1525of base station1520further includes processing circuitry1528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station1520further has software1521stored internally or accessible via an external connection.

Communication system1500further includes UE1530already referred to. Its hardware1535may include radio interface1537configured to set up and maintain wireless connection1570with a base station serving a coverage area in which UE1530is currently located. Hardware1535of UE1530further includes processing circuitry1538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE1530further comprises software1531, which is stored in or accessible by UE1530and executable by processing circuitry1538. Software1531includes client application1532. Client application1532may be operable to provide a service to a human or non-human user via UE1530, with the support of host computer1510. In host computer1510, an executing host application1512may communicate with the executing client application1532via OTT connection1550terminating at UE1530and host computer1510. In providing the service to the user, client application1532may receive request data from host application1512and provide user data in response to the request data. OTT connection1550may transfer both the request data and the user data. Client application1532may interact with the user to generate the user data that it provides.

It is noted that host computer1510, base station1520and UE1530illustrated inFIG.15may be similar or identical to host computer1430, one of base stations1412a,1412b,1412cand one of UEs1491,1492ofFIG.14, respectively. This is to say, the inner workings of these entities may be as shown inFIG.15and independently, the surrounding network topology may be that ofFIG.14.

InFIG.15, OTT connection1550has been drawn abstractly to illustrate the communication between host computer1510and UE1530via base station1520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE1530or from the service provider operating host computer1510, or both. While OTT connection1550is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection1570between UE1530and base station1520is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE1530using OTT connection1550, in which wireless connection1570forms the last segment. More precisely, the teachings of these embodiments may enhance UE mobility between RAN nodes and thereby provide benefits such as reduced UE power consumption and/or more efficient detection of NRS, among other things.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection1550between host computer1510and UE1530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1550may be implemented in software1511and hardware1515of host computer1510or in software1531and hardware1535of UE1530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection1550passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software1511,1531may compute or estimate the monitored quantities. The reconfiguring of OTT connection1550may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1520, and it may be unknown or imperceptible to base station1520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer1510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software1511and1531causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1550while it monitors propagation times, errors etc.

FIG.16is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIG.14andFIG.15. For simplicity of the present disclosure, only drawing references toFIG.16will be included in this section. In step1610, the host computer provides user data. In substep1611(which may be optional) of step1610, the host computer provides the user data by executing a host application. In step1620, the host computer initiates a transmission carrying the user data to the UE. In step1630(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1640(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.17is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIG.14andFIG.15. For simplicity of the present disclosure, only drawing references toFIG.17will be included in this section. In step1710of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step1720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step1730(which may be optional), the UE receives the user data carried in the transmission.

FIG.18is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIG.14andFIG.15. For simplicity of the present disclosure, only drawing references toFIG.18will be included in this section. In step1810(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step1820, the UE provides user data. In substep1821(which may be optional) of step1820, the UE provides the user data by executing a client application. In substep1811(which may be optional) of step1810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep1830(which may be optional), transmission of the user data to the host computer. In step1840of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG.19is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIG.14andFIG.15. For simplicity of the present disclosure, only drawing references toFIG.19will be included in this section. In step1910(which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step1920(which may be optional), the base station initiates transmission of the received user data to the host computer. In step1930(which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.