Indication of the presence of a tracking reference signal

By using L1 signaling to indicate TRS presence or absence, the method addresses the inefficiencies in existing communication methods, achieving power savings and optimized resource use in idle mode UEs.

JP7717168B2Active Publication Date: 2025-08-01TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023542861
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-01-15
Filing Date
2022-01-14
Publication Date
2025-08-01
Estimated Expiration
2042-01-14

AI Technical Summary

Technical Problem

Existing communication methods in idle mode user equipment (UE) do not efficiently balance network and UE power consumption by providing flexible indication of tracking reference signals (TRS), leading to increased power consumption and inefficient resource usage.

Method used

Implementing a method for network nodes to indicate the presence, absence, or potential presence of TRS through Layer 1 (L1) signaling, allowing UEs to flexibly choose between blind detection and skipping TRS detection based on the indication, thereby optimizing power usage.

Benefits of technology

This approach enables UE power savings by allowing flexible TRS detection, reducing unnecessary network power consumption, and optimizing resource utilization without compromising communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007717168000003
    Figure 0007717168000003
  • Figure 0007717168000004
    Figure 0007717168000004
  • Figure 0007717168000005
    Figure 0007717168000005
Patent Text Reader

Abstract

A communications device (1000, 4110) in a communications network may receive (1320) an indication from a network node (1100, 4160) in the communications network indicating one of the following: a reference signal is present at the reference signal occasion, a reference signal may or may not be present at the reference signal occasion, or a reference signal is absent at the reference signal occasion. The communications device may decode (1370) a paging message at a paging occasion following the reference signal occasion.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to communications, and more particularly to communication methods and related devices and nodes for indicating the presence of tracking reference signals.

Background Art

[0002] FIG. 1 is a diagram of an example of a fifth generation (“5G”) network (also referred to as a new radio (“NR”) network) including a pair 110a - b of network nodes (e.g., 5G base stations (“gNBs”)) and a plurality of communication devices 120 (also referred to as user equipment (“UEs”)).

[0003] An idle mode user equipment (UE) (also referred to as a communication device) can receive information about paging settings via higher layer signaling (e.g., system information signaling). For each discontinuous reception cycle (I-DRX cycle) in the idle mode, the UE can start processing (e.g., a wake-up operation) before its paging occasion (e.g., to receive one or more synchronization signal blocks (SSBs) for functions such as automatic gain control (AGC) and time-frequency synchronization). During a paging occasion, the UE can attempt to decode paging downlink control information (DCI) (e.g., DCI1-0 with a cyclic redundancy check (CRC) scrambled by a paging radio network temporary identifier (P-RNTI)). If paging DCI is detected, the UE also decodes the paging physical downlink shared channel (PDSCH) allocated by the paging DCI and can identify whether it is being paged (e.g., whether the paging message contains the UE's 5G serving temporary mobile subscriber identity information (5G-S-TMSI)). The paging DCI can include a modulation and coding scheme (MCS), resource allocation, a transport block (TB) scaling field, and a redundancy version associated with the scheduled PDSCH. The paging DCI can also be used to indicate a system information (SI) change, in which case the UE may not need to decode the corresponding PDSCH). SUMMARY OF THE INVENTION

[0004] According to some embodiments, a method of operating a communication device in a communication network is provided. The method can include receiving, from a network node within the communication network, an indication indicating one of the following: a reference signal is present during a reference signal occasion, a reference signal may or may not be present during a reference signal occasion, or a reference signal is absent during a reference signal occasion. The method can further include decoding a paging message during a paging occasion following the reference signal occasion.

[0005] According to other embodiments, a method of operating a network node in a communication network is provided. The method can include determining whether to transmit a reference signal during a reference signal occasion. The method can further include transmitting an indication to a communication device within the communication network. The indication indicates one of the following: a reference signal is present during a reference signal occasion, a reference signal may or may not be present during a reference signal occasion, or a reference signal is absent during a reference signal occasion.

[0006] According to other embodiments, a communication device, a network node, a computer program, and a computer program product can be provided for performing the above method.

[0007] The various embodiments described herein provide potential advantages that enable the NW to flexibly indicate via L1 signaling whether a TRS is present, absent, and / or may be present, which allows for a flexible UE implementation that can skip TRS detection or utilize blind TRS detection to save UE power.

[0008] Included to provide a further understanding of the present disclosure, incorporated in the present application and forming a part of the present application, the accompanying drawings illustrate some non-limiting embodiments of the inventive concept.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

DETAILED DESCRIPTION OF THE INVENTION

[0010] Next, the concepts of the present invention will be described in more detail below with reference to the accompanying drawings showing examples of embodiments of the concepts of the present invention. However, the concepts of the present invention can be embodied in many different forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the concepts of the present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment can be implicitly assumed to be present / used in another embodiment.

[0011] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as illustrative examples and should not be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted, or extended without departing from the scope of the described subject matter.

[0012] As described above, an idle-mode UE can receive information about paging settings via higher-layer signaling.

[0013] If additional reference signals such as a Tracking Reference Signal (TRS) are provided to an idle / inactive UE, the UE can reduce its wake-up time and further receive sufficient signals (e.g., SSB and TRS) prior to its paging occasion to decode the paging PDSCH, thereby reducing UE power consumption. However, sending additional TRS to an idle / inactive UE increases the network's power consumption. Therefore, by allowing an idle UE to utilize such TRS only when the TRS is being used for a connected-mode UE, opportunistic UE power savings can be achieved without significantly increasing the Network (NW) power consumption.

[0014] The Network (NW) can indicate configured potential TRS / Channel State Information Reference Signal (CSI-RS) occasions to idle / inactive UEs via system information signaling. Whether the Tracking Reference Signal (TRS) / CSI-RS is transmitted in a potential TRS / CSI-RS occasion is left to the NW implementation.

[0015] In some examples, the process may allow for an explicit / implicit indication of the availability of TRS / CSI-RS in a TRS / CSI-RS occasion, which may include informing the system information block (SIB) that TRS is always present in a TRS / CSI-RS occasion; using layer 1 (L1) to signal such paging downlink control information (DCI) to indicate that TRS / CSI-RS is available in a TRS / CSI-RS occasion; leaving it to the UE implementation to blindly detect whether TRS / CSI-RS is available in a TRS / CSI-RS occasion; or considering that TRS / CSI-RS is always present in a TRS / CSI-RS occasion if there is a corresponding paging message (paging physical downlink shared channel (PDSCH)) in a subsequent paging occasion (PO).

[0016] In a PO, the DCI format used to schedule the paging physical downlink control channel (PDCCH) is described below.

[0017] The following information is transmitted using DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a paging radio network temporary identifier (P-RNTI): · Short message indicator - 2 bits. · Short message - 8 bits. This bit field is reserved if only scaling information for paging is carried. · Frequency domain resource allocation - TIFF0007717168000001.tif7170 bits. This bit field is reserved if only a short message is carried. · TIFF0007717168000002.tif6170 is the size of control resource set (CORESET) 0 · Time domain resource allocation - 4 bits. This bit field is reserved when only short messages are carried. · Virtual resource block (「VRB」) to physical resource block (「PRB」) mapping - 1 bit. This bit field is reserved when only short messages are carried. · Modulation and coding scheme - 5 bits. This bit field is reserved when only short messages are carried. · TB scaling - 2 bits. This bit field is reserved when only short messages are carried. · Reserved bits - 8 bits for operation in cells with shared spectrum channel access, 6 bits otherwise.

[0018] The reserved bits in DCI can be used to incorporate new functionality, such as the L1-based availability of TRS / CSI-RS in a TRS / CSI-RS occasion without backward compatibility issues.

[0019] Some potential problems associated with the current example above are that they do not achieve a good balance between NW power consumption (e.g., having to transmit extra TRS / CSI-RS just to assist idle / inactive UEs) and UE power consumption (e.g., having to blindly detect whether TRS / CSI-RS exists in a TRS / CSI-RS occasion).

[0020] In a TRS / CSI-RS occasion, a signaling method is needed that simultaneously provides information to the UE so that the UE implementation form can flexibly choose whether to blindly detect whether TRS / CSI-RS exists in a TRS / CSI-RS occasion while enabling the gNB to flexibly turn TRS / CSI-RS transmission off / on accordingly.

[0021] In this specification, various embodiments define code points in L1 signaling (e.g., via DCI), where setting the first field to a first value indicates the presence of TRS / CSI-RS in one or more occasions. In additional or alternative embodiments, setting the first field to a second value indicates that TRS / CSI-RS may or may not be present in one or more occasions. In additional or alternative embodiments, setting the first field to a third value indicates the absence of TRS / CSI-RS in one or more occasions.

[0022] In additional or alternative embodiments, a flexible way is provided to indicate the location of a bit field that indicates TRS / CSI-RS availability in DCI.

[0023] In additional or alternative embodiments, the NW is permitted to transmit or omit the transmission of TRS / CSI-RS in TRS / CSI-RS occasions for idle / inactive mode UEs without degrading the NW's energy consumption, and further gives the UE side the flexibility to choose whether to use blind detection of TRS / CSI-RS or simply look for precise presence / absence signaling of TRS / CSI-RS. In additional or alternative embodiments, some aspects of the present invention enable the NW to transmit the same DCI to all UEs regardless of the UE's release, so that new release UEs (e.g., Rel17 that utilizes TRS in idle mode) receive the same DCI as previous releases and additional PDCCH transmissions can be reduced on the NW side.

[0024] FIG. 10 is a block diagram showing elements of a wireless device UE1000 (also referred to as a mobile terminal, mobile communication terminal, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment (“UE”), user equipment node / terminal / device, etc.) configured to provide wireless communication. (Wireless device 1000 can be provided, for example, as described below with respect to wireless device 4110 of FIG. 15, UE 4200 of FIG. 16, and UEs 4491, 4492 of FIG. 18.) As shown, wireless device UE includes an antenna 1007 (corresponding to, for example, antenna 4111 of FIG. 15) and a transceiver circuit 1001 (also called a transceiver) configured to provide uplink and downlink wireless communication with a base station (corresponding to, for example, network node 4160 of FIG. 15, also called a RAN node) of a wireless access network, corresponding to, for example, interface 4114 of FIG. 15, interfaces 4205, 4209, 4211, transmitter 4233 and receiver 4235 of FIG. 16. Wireless device UE can also include a processing circuit 1003 (also called a processor, corresponding to, for example, processing circuit 4120 of FIG. 15 and processor 4201 of FIG. 16) coupled to the transceiver circuit, and a memory circuit 1005 (also called a memory, corresponding to, for example, device-readable medium 4130 of FIG. 15) coupled to the processing circuit. Memory circuit 1005 can include computer-readable program code that, when executed by processing circuit 1003, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1003 can be defined to include memory such that a separate memory circuit is not required. Wireless device UE can also include an interface (such as a user interface) coupled to processing circuit 1003, and / or wireless device UE can be incorporated into a vehicle.

[0025] As described herein, the operation of the wireless device UE may be performed by the processing circuit 1003 and / or the transceiver circuit 1001. For example, the processing circuit 1003 may control the transceiver circuit 1001 to transmit communications over a radio interface to a radio access network node (also referred to as a base station) through the transceiver circuit 1001 and / or to receive communications from the RAN node over a radio interface through the transceiver circuit 1001. Additionally, modules may be stored in the memory circuit 1005, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 1003, the processing circuit 1003 performs respective operations (e.g., the operations described below with respect to exemplary embodiments related to the wireless device).

[0026] FIG. 11 is a block diagram showing elements of a radio access network RAN node 1100 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communication, according to an embodiment of the concepts of the present invention. (RAN node 1100 can be provided as described below with respect to, for example, network node 4160 of FIG. 15 and base stations 4412a - c of FIG. 18, and all of them, unless stated otherwise, are considered to be compatible in the examples and embodiments described herein and within the intended scope of the present disclosure.) As shown, the RAN node can include a transceiver circuit 1101 (also called a transceiver) configured to provide uplink and downlink radio communication with mobile terminals (corresponding to, for example, a portion of interface 4190 of FIG. 15). The RAN node can include a network interface circuit 1107 (also called a network interface, corresponding to, for example, a portion of interface 4190 of FIG. 15) configured to provide communication with other nodes of the RAN and / or the core network CN (e.g., with other base stations). The network node can also include a processing circuit 1103 (also called a processor, corresponding to, for example, processing circuit 4170 of FIG. 15) coupled to the transceiver circuit, and a memory circuit 1105 (also called a memory, corresponding to, for example, device - readable medium 4180 of FIG. 15) coupled to the processing circuit. The memory circuit 1105 can include computer - readable program code that, when executed by the processing circuit 1103, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1103 can be defined to include memory such that a separate memory circuit is not required.

[0027] As described herein, the operation of the RAN node may be performed by the processing circuit 1103, the network interface 1107, and / or the transceiver 1101. For example, the processing circuit 1103 may control the transceiver 1101 to transmit downlink communications to one or more mobile terminals or mobile UEs over a radio interface through the transceiver 1101 and / or receive uplink communications from one or more mobile terminals or mobile UEs over the radio interface through the transceiver 1101. Similarly, the processing circuit 1103 may control the network interface 1107 to transmit communications to one or more other network nodes through the network interface 1107 and / or receive communications from one or more other network nodes through the network interface. Additionally, modules may be stored in the memory 1105, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 1103, the processing circuit 1103 performs respective operations (e.g., the operations described below with respect to exemplary embodiments related to the RAN node).

[0028] According to some other embodiments, the network node may be implemented as a core network CN node without a transceiver. In such embodiments, the transmission to the wireless device UE may be initiated by the network node such that the transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or a RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating the transmission may include transmitting through the transceiver.

[0029] FIG. 12 is a block diagram showing elements of a core network CN node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to an embodiment of the inventive concept. As shown, the CN node may include a network interface circuit 1207 (also referred to as a network interface) configured to provide communication with other nodes of the core network and / or a radio access network RAN. The CN node may also include a processing circuit 1203 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 1205 (also referred to as a memory) coupled to the processing circuit. The memory circuit 1205 may include computer-readable program code that, when executed by the processing circuit 1203, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1203 may be defined to include memory such that a separate memory circuit is not required.

[0030] As described herein, the operations of the CN node may be performed by the processing circuit 1203 and / or the network interface circuit 1207. For example, the processing circuit 1203 may control the network interface circuit 1207 to transmit communications through the network interface circuit 1207 to one or more other network nodes and / or receive communications through the network interface circuit from one or more other network nodes. Additionally, modules may be stored in the memory 1205, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 1203, the processing circuit 1203 performs respective operations (e.g., the operations described below with respect to exemplary embodiments related to core network nodes).

[0031] In some embodiments described herein, the term idle refers to both the RRC_IDLE and RRC_INACTIVE states of the UE. Further, some embodiments described herein consider using CSI-RS for Tracking (TRS), but the same operations can be applied to any other CSI-RS where configuration information is provided to an idle UE.

[0032] In some embodiments, an idle mode UE camps on an NR cell. The UE can receive broadcast or dedicated system information or release a message (or other higher layer signaling) containing paging configuration information. The UE can also receive configuration information regarding a TRS occasion (or potential TRS occasion). The gNB may or may not transmit the TRS in a TRS occasion. If the UE determines that there is a TRS in a TRS occasion, the UE can process the signal to perform functions such as AGC and time / frequency tracking and use the signal in the processing of a paging occasion to detect a paging message.

[0033] In additional or alternative embodiments, the UE can receive at least one parameter indicating the location of a TRS presence / absence indicator field ("TIF") in a downlink control information (DCI) format via higher layer signaling. In some examples, when the DCI size is 60 bits, an explicit value from 0 to 59 can be used to indicate the location of the TIF. In other examples, when the value is set to 10, bit number 10 in the DCI format is used for the TIF. If the TIF is a multi-bit field (e.g., 2 bits), the explicit bit field length can also be received via higher layer signaling. This allows the NW to use a reserved bit field as the TIF in paging DCI and indicate the TRS presence / absence information to idle / inactive UEs that detect the paging DCI.

[0034] In additional or alternative embodiments, the location or length of the TIF can be pre-set, for example, as part of a standardized document. In some examples, the location of the TIF or how to find the location of the TIF is given in the specification. For example, one of the reserved bits in DCI format 1-0 associated with P-RNTI or system information radio network temporary identifier ("SI-RNTI") can be allocated to the TIF in the specification. Furthermore, the conditions for enabling the TIF can be pre-set. For example, when an idle UE receives configuration information related to a TRS occasion, the UE can know that the TIF is included in the paging DCI.

[0035] In additional or alternative embodiments, the UE can find the length of the bit field and its interpretation based on pre-configuration or a combination with higher layer signaling. In some examples, the NW may have options to indicate to the UE the options used to indicate the availability of the TRS in a TRS occasion. In additional or alternative examples, when the NW mentions both blind detection ("BD") of the TRS and L1 signaling as options, the UE can know, for example, that the length of the TIF is 2 bits or more. When the NW mentions only L1 signaling, the UE can know that the TIF is simply 1 bit. When the NW mentions only BD, the UE can know either that the TIF is not transmitted or that the TIF is simply 1 bit. The bits in this example can be used to let the UE know, for example, that the TRS may or may not exist within the next X ms, or otherwise may be reserved.

[0036] In additional or alternative embodiments, the location and length of the TIF can be based on a combination of higher layer signaling and pre-configuration. For example, the location of the TIF, or how the location of the TIF is determined, is included in the specification, but an indicator is included in the TRS occasion provisioning information from the higher layer signaling for the UE to know whether the TIF is included in the paging DCI, which can indicate to the UE whether the TIF is set. In addition, the length of the TIF may be explicitly provided as part of the higher layer signaling, or the UE may be able to infer the length of the TIF based on some pre-configured conditions.

[0037] In additional or alternative embodiments, the DCI format can be one of DCI format 1-0 used for paging messages (i.e., CRC scrambled with P-RNTI), DCI format 1-0 used for system information messages (i.e., CRC scrambled with SI-RNTI), or the DCI format used for paging early indication (i.e., with CRC scrambled by the RNTI indicated by the higher layer). The paging early indication is an indication that tells the UE whether a future paging occasion includes a paging message (e.g., paging PDSCH) intended for that UE.

[0038] In additional or alternative embodiments, the UE can receive, via higher layer signaling, a validity timer value indicating the duration during which the TRS exists (which can be in units of milliseconds, seconds, paging occasions, frames, SFN cycles, or DRX cycles, for example), or the duration during which the TRS does not exist when the corresponding indication is sent in a DCI format. In an alternative example, the validity timer can be preconfigured as part of the specification (e.g., can be set to 1.28 seconds), or can be inferred based on a mathematical formula. A possible mathematical formula can be based on a UE identifier (“ID”), e.g., an ID received by the UE from the NW and used by the UE to determine its PO, or can be based on a function or part of a DRX cycle (e.g., if the DRX cycle is 1.28 seconds, the validity timer is also 1.28 seconds, but if the DRX is longer than 10 seconds, the validity timer is, for example, 2.56 seconds, which is part of the DRX cycle). In some examples, a combination of higher layer signaling and preconfiguration can be used to infer the validity timer. For example, the UE can know a set of possible validity timer values based on preconfiguration, and the higher layer signaling indicates which of them is used for the TIF.

[0039] Figure 2 is a table showing an example of the TIF field in DCI. Of course, other code point specifications (order or subset) are possible. In the example shown in Figure 2, NW can send code 00 if the TRS is given at the next Y1ms, and can send 10 or 01 if the TRS turns off immediately but there is some remaining time shorter than Y1ms. A UE that has received a 00 indication first can continue to rely on the existence of the remaining part of its validity timer, while another UE that receives a 10 or 01 indication will function without further existence guarantee. NW can also turn off the TRS after Y1ms has elapsed since the last 00 indication was sent. A UE that has received a 00 indication first can continue to rely on the existence of the remaining part of its validity timer regardless of subsequent indications that may show conflicting (01) or consistent (10) indications during the duration that the validity timer continues.

[0040] Figure 3 is a table showing another example of the TIF field in DCI. In the example shown in Figure 3, the second code point can be defined to mean one of the following: 1) the TRS does not exist in the TRS occasion during the next Y1ms; 2) the TRS may or may not exist in the TRS occasion during the next Y1ms. Therefore, this code point can be used to inform the UE whether it can or cannot use blind detection of the TRS.

[0041] In some embodiments, a process is provided that includes the UE decoding a DCI that includes a TIF field. The process further includes the UE determining that the TIF field is set to a first value indicating the presence of the TRS in one or more occasions. The process further includes the UE receiving the TRS in one or more of the corresponding occasions and subsequently attempting to decode a paging message in a paging occasion.

[0042] Figure 4 illustrates an example of this process for a certain UE in two consecutive paging cycles. In Figure 4, the unshaded boxes (e.g., denoted as TRSo) indicate the absence of the corresponding signal. The shaded parts indicate the presence of the corresponding signal / channel. In the previous cycle, the UE processes three SSBs (darkly shaded boxes) and decodes the paging DCI (DCI-1) and the corresponding PDSCH. In this example, the UE only needs to wake up for the three SSBs before the PO. The DCI also indicates the presence of the TRS at the next Xms. Based on this information, the UE determines that the TRS will be present at future POs, processes a subset of the SSBs and the TRS occasions before the future PO, and attempts to decode the paging DCI and the corresponding PDSCH at the future PO. The overall processing of the UE in future cycles is indicated by the dotted box (e.g., the UE only needs to wake up for one SSB and one TRS before the PO).

[0043] In some examples, when the UE determines that the TIF field is set to a second field value indicating that the TRS may or may not be present in one or more occasions, the UE can choose either to perform blind detection of the TRS in the TRS occasion or to omit the TRS detection and attempt to detect paging in the paging occasion.

[0044] In additional or alternative examples, when the UE determines that the TIF field is set to a second field value indicating that "the TRS may or may not be present in one or more occasions" or "reserved", the UE attempts to blindly detect the presence of the TRS in one or more of the corresponding occasions. If the TRS is detected, the UE can then attempt to decode the paging message in the paging occasion.

[0045] In an additional or alternative example, the UE determines that the TIF field is set to a second field value indicating that a TRS may or may not be present on one or more occasions, and the UE skips blindly detecting the presence of a TRS in one or more of the corresponding occasions, and for example, instead of using the TRS, it can attempt to decode a paging message in a paging occasion using legacy receiver preparation procedures.

[0046] Figure 5 illustrates an example of the UE processing timeline in two consecutive paging cycles for a certain UE. Similar to Figure 4, in this figure, the unshaded boxes (e.g., denoted as TRSo) indicate the absence of the corresponding signal, and the shaded parts indicate the presence of the corresponding signal / channel. The dotted parts indicate that the signal may or may not be present. In the previous cycle, the UE processes three SSBs (darkly shaded boxes) and decodes the paging DCI (DCI-1) and the corresponding PDSCH. In this example, the UE only needs to wake up for the first three SSBs of the PO. The DCI also indicates that a TRS may or may not be present in the next X ms, and based on this information, the UE attempts to blindly detect the presence of a TRS before future POs. If the UE detects the presence of a TRS, it can skip some SSB processing and directly process the paging PDCCH / PDSCH. The overall processing of the UE in future cycles is indicated by the dotted boxes (e.g., the UE only needs to wake up for 1 SSB and 1 TRS before the PO, and the UE can skip some SSBs and TRSs).

[0047] In some examples, when the UE determines that the TIF field is set to a third field value indicating the absence of TRS in one or more occasions, the UE omits TRS detection in one or more occasions and attempts to detect paging in a paging occasion, for example, by using legacy receiver preparation procedures instead of using TRS.

[0048] Figure 6 illustrates an example of a UE processing timeline in two consecutive paging cycles for a UE. In this figure, unshaded boxes (e.g., denoted as TRSo) indicate the absence of the corresponding signal, and the shaded portions indicate the presence of the corresponding signal / channel. In the previous cycle, the UE processes three SSBs (darkly shaded boxes) and decodes paging DCI (DCI-1) and the corresponding PDSCH. In this example, the UE only needs to wake up for the three SSBs before the PO. The DCI also indicates that there is no TRS in the next X ms, and based on this information, the UE knows that there is no TRS before future POs. The UE processes only the SSBs before future POs and processes the paging PDCCH / PDSCH. The overall processing of the UE in future cycles is indicated by the dotted boxes (e.g., the UE needs to wake up for the three SSBs before the PO).

[0049] In some embodiments, through signaling, the NW can efficiently serve UEs that perform blind TRS detection as well as UEs that do not support blind TRS detection through an integrated signaling framework.

[0050] In additional or alternative embodiments, when a TIF is embedded in paging DCI, in a given PO, a situation may occur where paging DCI is not transmitted for a time exceeding the validity timer duration. In some examples, the NW may stop TRS transmission after the validity period, and after the validity timer expires, the UE should not assume the presence of the TRS. In additional or alternative examples, to automatically extend the validity timer until the next paging DCI transmitted in the PO so that the UE can continue to use the TRS, the NW may transmit paging DCI with a non-TRS TIF without performing the associated actual paging message transmission to forcibly end the TRS validity.

[0051] In additional or alternative embodiments, the UE decodes the paging DCI but does not receive the TIF (e.g., if the NW is not transmitting the TIF, or if the TIF is set only in the paging DCI related to a specific paging occasion), or the UE does not receive the paging DCI. In some examples, if the validity timer is still running from the last indication, the UE uses this timer for its TRS-related operations (e.g., to decide whether to use it before paging if the TRS is present or blindly detected). In additional or alternative examples, if the validity timer expires and the UE has not received a new TIF, the UE can assume either that the TRS may or may not be present, or that the TRS is not present, or can extend the TIF indication. The latter approach can be based on the UE implementation form, on the basis that the UE can be preconfigured regarding the assumptions in this case, on the basis of the configuration by the NW through higher-layer signaling, or on the basis that the UE knows what to assume regarding the presence of the TRS when the validity timer expires and no new TIF is received.

[0052] In additional or alternative embodiments, the UE receives a new TIF while the previous TIF indication validity timer has not expired. In some examples, the UE ignores the previous indication and updates with the new indication. In additional or alternative examples, as long as the previous TIF indication is still valid, the UE does not expect to receive a new TIF indication, so the new indication is considered an error case. The UE behavior in this example can be preconfigured or explicitly configured by the NW through higher layer signaling.

[0053] The reserved fields within the paging DCI (e.g., DCI1-0) can be used for the indication of TRS presence information. For example, in a paging DCI of size 65 bits, there are 6 available reserved bits (including a 24-bit CRC). There may be additional reserved bits in the short message, which can also be utilized from the perspective of the NW. In some examples, especially when additional functionality is added to the paging DCI in the future, the reserved bits may not be sufficient. Therefore, in some examples, it is preferable to give the NW the flexibility to use any bit within the paging DCI for the indication of TRS presence.

[0054] In some examples, if the NW intends to use only the fields corresponding to the reserved bits, the NW can use an explicit parameter indicating the bit index within the bits corresponding to only the reserved bits. For example, if there are only 6 reserved bits, the NW only needs a 3-bit indicator to indicate the position of the bit (within the 6 reserved bits) used for the TRS presence indication.

[0055] In an additional or alternative example, if the NW intends to use any field in the DCI for the TRS presence indication, the NW can use an explicit parameter indicating any bit index within the bits corresponding to the DCI. For example, if there are only 60 bits (including 24 CRC bits) in the DCI, the NW needs a 6-bit indicator to indicate the position of the bit (in the DCI) used for the TRS presence indication. Therefore, the NW may also overload the existing fields in the paging DCI to communicate the TRS presence indication.

[0056] In an additional or alternative example, the paging DCI includes a TB scaling field that is interpreted as follows. In this case, S represents the scaling factor used for determining the transport block size for the corresponding paging PDSCH. The NW can also set the first bit of the TB scaling field for serving as the TIF (for example, by indicating to the UE the bit number X (corresponding to the first bit of the TB scaling field) in the paging DCI as part of the TRS presence setting information). Alternatively, the NW can use the reserved index for TB scaling as the TIF. For example, if 11 is transmitted for TB scaling, it indicates that the TRS exists at the next Y ms, otherwise, the TRS may or may not exist. FIG. 8 is a table showing an example of the TB scaling field that can be included in the paging DCI.

[0057] FIG. 7 shows an exemplary DCI format for paging and an explicit tifPosWithinDCI (TIF position within DCI) parameter indicated via a higher layer that identifies the position of the TIF in the DCI. The UE acquires this higher layer parameter to detect the DCI and infers the presence of the TRS in one or more TRS occasions using the TIF in the detected DCI.

[0058] In some embodiments, the above examples can be extended to examples where the position of the TIF in the paging DCI is pre-set, for example, examples that can be inferred from a standardized document.

[0059] In additional or alternative embodiments, the NW can embed the TIF into the DCI-based PEI transmission. The TIF format and field interpretation may be the same as those described above. The validity timer (e.g., Y1ms) may start from the PEI transmission instance or from the time instance of the PO referenced by the permanent device identifier (“PEI”).

[0060] In some examples, a UE that uses the PEI to determine the need for PO monitoring receives the PEI for each periodic operation, determines the availability of the TRS, and can adapt the receiver operation (e.g., the selection of signals collected for loop convergence) based on whether the TRS is currently available (or has already been signaled as available and the validity timer has not expired). A UE that does not use the PEI for PO monitoring adaptation can receive the PEI at the rate of the validity timer length. That is, the receiver PEI re-checks the TRS availability immediately before the preceding validity timer expires. The UE can then adapt the receiver operation based on whether the TRS is currently available.

[0061] In additional or alternative embodiments, the NW can transmit the TIF in a PDCCH transmission separate from the paging PDCCH or the PEI PDCCH. The same signaling principle as described above can be used, and DCI format 1-0 or other formats may be used.

[0062] In additional or alternative embodiments, if the current TIF indicates that the TRS is not available, the UE reverts to legacy (non-TRS-assisted) operation but can re-check the TIF status occasionally or periodically. If the TIF is embedded in the paging DCI, the UE can re-check the TIF status during the process of each paging DCI.

[0063] In additional or alternative embodiments, the UE may be provided with a PEI setting, in which case the PEI is based on the TRS. That is, if the UE receives a TRS or a specific TRS with, for example, a specific scrambling code, it indicates that there is paging for one or more of the future POs. In some examples, the TIF indication cannot be applied to the specific TRS used as the PEI and is only applicable to other TRSs not used as the PEI. In additional or alternative embodiments, if the TIF indicates that there is a TRS within the next Y ms, the UE can interpret that the TRS is not used as the PEI and that it is necessary to monitor the PO.

[0064] In additional or alternative embodiments, the TIF indication may be associated with multiple TRS settings, for example, for TRSs associated with multiple beams. In some examples, the UE receives multiple settings of the TRS from higher-layer signaling as potential TRS occasions. The TRS settings differ in at least one parameter, for example, the associated beams are different. In additional or alternative examples, the TIF indication is valid for all TRS settings, for example, for all beams on which the TRS is transmitted. If the TIF indicates that there is a TRS within the next Y ms, all the TRSs for which the setting information is provided to the idle UE are transmitted.

[0065] In additional or alternative examples, the TIF indication is only valid for a subset of the TRS configurations. For example, the NW can provide a subset of the TRS configurations associated with the TIF through higher layer signaling. For example, the UE may have received configuration information regarding a first TRS, a second TRS, and a third TRS. The NW then indicates, as part of the TRS provisioning to the idle UE, that only the first and second TRSs are associated with the TIF. In this way, the UE decodes the TIF, and if the TIF indicates that a TRS exists within the next Yms, the UE knows that the first and second TRSs exist, but the third TRS may or may not exist. The indication of which TRSs are associated with the TIF can be shown, for example, through an indicator as part of the provisioning of the TRS configuration information to the idle UE. For example, this parameter can be called tifassociated(enable,disable), which means that when it is enabled, the TIF is associated with this particular TRS, and when it is disabled, the TIF is not associated with this TRS. Such a separation is also useful in cases where one or more TRSs are also used as PEIs, and thus the NW has the ability to exclude these TRSs from the association with the TIF.

[0066] In additional or alternative examples, the NW can set the TRS resources into different groups. For example, the first group includes the first and second TRS resources, and the second group includes the third TRS resource. The NW can additionally set the TIF such that, as part of the indication, the UE receives an indication of which group of TRS resources is indicated. For example, the TIF can include 3 bits. The following example depicts how the bits can be used to convey the TIF indication for two groups. The same principle can be used to extend to three or more groups.

[0067] In an additional or alternative example, if one or more groups of TRS resources are not associated with a TIF, the UE knows that the TRS resources may or may not exist. Therefore, if the UE wants to use them, blind detection must be applied. In this example, the first TIF bit is used as an indication that a group is associated, i.e., bit 0 indicates the first group and bit 1 indicates the second group. FIG. 9 is a table showing an example of the TIF field in DCI that includes bits indicating which group is associated. In this example, fields 011 and 111 are reserved. In one example, for instance, one of 011 can also be used to indicate that there are TRSs in the TRS occasions of the first and second groups respectively within, for example, the next Y1ms and Y2ms. For instance, the other 111 can be used to indicate that there may or may not be TRSs in the TRS occasions of the first and second groups respectively within, for example, the next Y1ms and Y2ms.

[0068] In an additional or alternative example, the reserved bits or other bits in the paging DCI can be used for TIF. In one example, the TIF bit field may not be continuous either. For example, the locations of the first, second, or third bits in FIG. 9 may be in different parts of the paging DCI and may not be continuous. In this case, any location can be pre-set or the NW can flexibly set the explicit bit locations respectively. In an additional or alternative example, the bit order follows the location numbers of each bit. For example, the first bit can exist at location 10, the second bit at location 15, and the third bit at location 21.

[0069] In some embodiments, a header field can be set to allow flexible use of reserved bits in DCI. A subset of the reserved bits can function as a header field, and this header field indicates to the UE how to interpret some / all of the other reserved bits. For example, if the header field indicates a pre-set value (e.g., a first value such as 01), the next X reserved bits (e.g., 2 reserved bits) in the DCI can indicate the presence / absence of TRS in the next time window (in slots, milliseconds, seconds, or SFN units).

[0070] In some examples, if the header field indicates a pre-set value (e.g., a second value such as 10), the next Y reserved bits (e.g., 2 reserved bits) in the DCI can inform about the PEI for some / all of the paging groups.

[0071] In additional or alternative examples, if the header field indicates a pre-set value (e.g., a third value such as 11), the next Z reserved bits (e.g., 3 reserved bits) in the DCI can indicate the minimum TB scaling value assumption for the reception of paging PDSCH in the next time window (in slots, milliseconds, seconds, or SFN units).

[0072] In additional or alternative examples, if the header field indicates a pre-set value (e.g., a third value such as 11), the remaining reserved bits can be treated as reserved.

[0073] Some embodiments herein are described using TRS and TRS occasions, but the same principles are applicable to TRS / CSI-RS and TRS / CSI-RS occasions.

[0074] Some embodiments described herein enable idle mode UE power savings by allowing the NW to flexibly indicate via L1 signaling whether a TRS "exists" and "may or may not exist" in one or more TRS occasions. In additional or alternative embodiments, the NW can indicate whether a TRS is absent in one or more TRS occasions. This signaling enables a flexible UE implementation that can skip TRS detection or utilize TRS blind detection, saving UE power.

[0075] Next, with reference to the flowchart of FIG. 13, the operation of a communication device (implemented using the structure of the block diagram of FIG. 10) according to some embodiments of the concepts of the present invention will be described. For example, modules may be stored in the memory 1005 of FIG. 10, and these modules may provide instructions such that when the instructions of the modules are executed by their respective communication device processing circuits 1003, the processing circuit 1003 performs each operation of the flowchart.

[0076] In block 1310, the processing circuit 1003 receives, via the transceiver 1001, a message including at least one of the length and location of an indicator.

[0077] In block 1320, the processing circuit 1003 receives, via the transceiver 1001, an indication indicating whether a reference signal exists during a subsequent reference signal occasion. In some embodiments, the indication is received during the communication device's awake period during a DRX cycle as part of being in an idle state. In additional or alternative embodiments, the reference signal is a tracking reference signal (TRS) or a channel state information reference signal (CSI-RS).

[0078] In additional or alternative embodiments, receiving an indication includes receiving an indication indicating one of the following: that a reference signal is present at reference signal occasion, that a reference signal may or may not be present at reference signal occasion, and that a reference signal is absent at reference signal occasion. In additional or alternative embodiments, receiving an indication includes receiving an indication indicating that a reference signal is present at reference signal occasion.

[0079] In additional or alternative embodiments, receiving an indication includes receiving downlink control information (DCI) including an indication indicating whether a reference signal is transmitted by a network node at reference signal occasion during a second DRX cycle during a first DRX cycle. In additional or alternative embodiments, the DCI is DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by at least one of the following radio network temporary identifiers (RNTIs): paging RNTI (P-RNTI), and system information (SI-RNTI).

[0080] In additional or alternative embodiments, receiving an indication includes receiving a synchronization signal block (SSB) including an indication indicating whether a reference signal is transmitted by a network node at reference signal occasion during a first DRX cycle during the first DRX cycle.

[0081] In block 1330, the processing circuit 1003 determines a validity timer indicating the duration for which a reference signal is present at reference signal occasion. In some embodiments, determining the validity timer includes receiving an indication of the validity timer from a network node. In additional or alternative embodiments, determining the validity timer includes determining the validity timer based on an identifier of the communication device.

[0082] In block 1340, the processing circuit 1003 monitors the number of SSBs based on an indication. In some embodiments, monitoring the number of SSBs transmitted by a network node includes monitoring only one SSB transmitted by the network node in response to receiving an indication that a reference signal is present. In additional or alternative embodiments, the number of SSBs to be monitored is determined based on whether a reference signal is received in response to attempting to detect the reference signal during a reference signal occasion.

[0083] In block 1350, the processing circuit 1003 determines whether to attempt blind detection of a reference signal. In some embodiments, the communication device only determines whether to attempt blind detection when an indication indicates that a reference signal may or may not be present during a reference signal occasion.

[0084] In block 1360, the processing circuit 1003 receives a reference signal via the transceiver 1001 during a reference signal occasion.

[0085] In block 1370, the processing circuit 1003 decodes a paging message during a paging occasion following a reference signal occasion. In some embodiments, the paging message is decoded using the monitored SSBs. In additional or alternative embodiments, decoding the paging message includes decoding the paging message based on a reference signal in response to receiving the reference signal during a reference signal occasion.

[0086] Various operations from the flowchart of FIG. 13 may be optional with respect to some embodiments of the communication device and related methods. For example, with respect to the following specific example 1, 1310 and 1330 - 1360 of FIG. 13 are optional.

[0087] Next, with reference to the flowchart of FIG. 14, the operation of a network node (implemented using the block diagram structure of FIG. 11) according to some embodiments of the concepts of the present invention will be described. For example, the modules may be stored in the memory 1105 of FIG. 11, and these modules may provide instructions such that when the instructions of the modules are executed by their respective RAN node processing circuits 1103, the processing circuit 1103 performs each operation of the flowchart. The operations of FIG. 14 are described below as being performed by the RAN node, but the operations can be performed by any suitable network node (e.g., the CN node 1200).

[0088] In block 1410, the processing circuit 1203 determines whether to transmit a reference signal upon a reference signal occasion. In some embodiments, the reference signal is a tracking reference signal (TRS) or a channel state information reference signal (CSI-RS). In additional or alternative embodiments, the communication device is a first communication device in an idle state, and determining whether to transmit a reference signal upon a reference signal occasion includes determining whether a second communication device is in an active state.

[0089] In block 1420, the processing circuit 1203 transmits a message including at least one of an indication of length and location via the transceiver 1201.

[0090] In block 1430, the processing circuit 1203 transmits an indication of a validity timer indicating the duration for which a reference signal exists upon a reference signal occasion via the transceiver 1201.

[0091] In block 1440, the processing circuit 1203 transmits, via the transceiver 1201, an indication indicating whether a reference signal is transmitted during a reference signal occasion. In some embodiments, transmitting the indication includes transmitting an indication indicating one of the following: the reference signal is present during a reference signal occasion, the reference signal may or may not be present during a reference signal occasion, and the reference signal is absent during a reference signal occasion. In additional or alternative embodiments, transmitting the indication includes transmitting an indication indicating that the reference signal is present during a reference signal occasion.

[0092] In additional or alternative embodiments, transmitting the indication includes transmitting downlink control information (DCI) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion during a second DRX cycle during a first DRX cycle of a communication device. In additional or alternative embodiments, the DCI is DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by at least one of the following radio network temporary identifiers (RNTIs): paging RNTI (P-RNTI), and system information (SI-RNTI).

[0093] In additional or alternative embodiments, transmitting the indication includes transmitting a synchronization signal block (SSB) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion during a first DRX cycle during the first DRX cycle.

[0094] In block 1450, the processing circuit 1203 transmits a reference signal via the transceiver 1201 during a reference signal occasion.

[0095] In block 1460, the processing circuit 1203 transmits a paging message via the transceiver 1201.

[0096] The various operations from the flowchart of FIG. 6 can be optional with respect to some embodiments of the communication device and related methods. For example, with respect to the following specific Example 16, blocks 1420-1430 and 1450-1460 of FIG. 14 are optional.

[0097] Specific examples are outlined below.

[0098] Example 1. A method of operating a communication device in a communication network, the method comprising receiving (1320) from a network node in the communication network an indication indicating one of the following: that a reference signal is present at reference signal occasion, that a reference signal may or may not be present at reference signal occasion, or that a reference signal is absent at reference signal occasion; and decoding (1370) a paging message at paging occasion following the reference signal occasion.

[0099] Example 2. The method according to Example 1, wherein decoding the paging message at paging occasion comprises decoding the paging message at paging occasion using a reference signal indicated by the indication.

[0100] Example 3. The method according to Example 1 or 2, wherein the reference signal is a tracking reference signal (TRS) or a channel state information reference signal (CSI-RS).

[0101] Example 4. Monitoring the number of synchronization signal blocks (SSBs) transmitted by a network node prior to a paging occasion (1340), further including monitoring (1340) where the number of SSBs to be monitored is based on an indication, and decoding a paging message during the paging occasion includes decoding the paging message during the paging occasion using the monitored SSBs, the method according to any one of Examples 1 to 3.

[0102] Example 5. Monitoring the number of SSBs transmitted by a network node includes monitoring only one SSB transmitted by the network node in response to receiving an indication indicating the presence of a reference signal, the method according to Example 4.

[0103] Example 6. Determining whether to attempt blind detection includes determining to attempt blind detection, and monitoring the number of SSBs includes determining the number of SSBs to be monitored based on whether a reference signal has been received in response to attempting to detect the reference signal during a reference signal occasion, the method according to Example 4.

[0104] Example 7. Receiving an indication includes receiving an indication indicating the presence of a reference signal during a reference signal occasion, and the method further includes receiving (1360) the reference signal during the reference signal occasion in response to receiving an indication indicating the presence of the reference signal during the reference signal occasion, the method according to any one of Examples 1 to 4.

[0105] Example 8. Receiving an indication includes receiving an indication indicating that a reference signal may or may not be present during a reference signal occasion, and the method further includes determining (1350) whether to attempt blind detection of the reference signal during the reference signal occasion in response to receiving an indication indicating that the reference signal may or may not be present during the reference signal occasion, the method according to any one of Examples 1 to 4.

[0106] Example 9. Receiving an indication includes receiving downlink control information (DCI) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion during a second DRX cycle during a first DRX cycle, the method according to any one of Examples 1 to 8.

[0107] Example 10. The method according to Example 9, wherein the DCI is DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by at least one of the following radio network temporary identifiers (RNTIs): paging RNTI (P-RNTI), and system information (SI-RNTI).

[0108] Example 11. The method according to Example 9 or 10, further includes receiving (1310) a message including at least one of the length and location of an indication in the DCI.

[0109] Example 12. Receiving an indication includes receiving a synchronization signal block (SSB) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion during a first DRX cycle during the first DRX cycle, the method according to any one of Examples 1 to 9.

[0110] The method according to any one of Examples 1 to 12, further comprising determining (1330) a validity timer indicating a duration during which a reference signal exists during a reference signal occasion.

[0111] The method according to Example 13, wherein determining the validity timer includes receiving an indication of the validity timer from a network node.

[0112] The method according to Example 13, wherein determining the validity timer includes determining the validity timer based on an identifier of a communication device.

[0113] A method of operating a network node in a communication network, the method including determining (1410) whether to transmit a reference signal during a reference signal occasion and transmitting (1440) an indication to a communication device in the communication network indicating whether the reference signal is to be transmitted during the reference signal occasion.

[0114] The method according to Example 16, wherein the reference signal is a tracking reference signal (TRS) or a channel state information reference signal (CSI-RS).

[0115] The method according to Example 16 or 17, wherein transmitting the indication includes transmitting an indication indicating one of the following: the reference signal exists during the reference signal occasion, the reference signal may or may not exist during the reference signal occasion, and the reference signal is absent during the reference signal occasion.

[0116] The method according to Example 18, wherein transmitting the indication includes transmitting an indication indicating that the reference signal exists during the reference signal occasion, and the method further includes transmitting (1450) the reference signal during the reference signal occasion in response to transmitting the indication indicating that the reference signal exists during the reference signal occasion.

[0117] Example 20. The method according to any one of Examples 16 to 19, further comprising transmitting a paging message (1460) in response to transmitting an indication.

[0118] Example 21. The method according to any one of Examples 16 to 20, wherein transmitting an indication includes transmitting downlink control information (DCI) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion in a second DRX cycle during a first DRX cycle of a communication device.

[0119] Example 22. The method according to Example 21, wherein the DCI is DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by at least one of the following radio network temporary identifiers (RNTIs): paging RNTI (P-RNTI), and system information (SI-RNTI).

[0120] Example 23. The method according to Example 21 or 22, further comprising transmitting a message (1420) including at least one of a length and a location of an indication in the DCI.

[0121] Example 24. The method according to any one of Examples 16 to 20, wherein transmitting an indication includes transmitting a synchronization signal block (SSB) including an indication indicating whether a reference signal is transmitted by a network node during a reference signal occasion in a first DRX cycle during the first DRX cycle.

[0122] Example 25. The method according to any one of Examples 16 to 24, further comprising transmitting an indication of a validity timer indicating a duration during which a reference signal exists during a reference signal occasion (1430).

[0123] Example 26. The method according to any one of Examples 16 to 25, wherein the communication device is a first communication device in an idle state, and determining whether to transmit a reference signal during a reference signal occasion includes determining whether a second communication device is in an active state.

[0124] Example 27. A communication device (1000) within a communication network, the communication device comprising a processing circuit (1003) and a memory (1005) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the communication device to perform an operation including any one of the operations of Examples 1 to 15.

[0125] Example 28. A communication device (1000) within a communication network configured to perform any one of the operations of Examples 1 to 15.

[0126] Example 29. A computer program comprising program code executable by a processing circuit (1003) of a communication device (1000) within a communication network, whereby execution of the program code causes the communication device to perform an operation including any one of the operations of Examples 1 to 15.

[0127] Example 30. A computer program product comprising a non-transitory storage medium including program code executable by a processing circuit (1003) of a communication device (1000) within a communication network, whereby execution of the program code causes the communication device to perform an operation including any one of the operations of Examples 1 to 15.

[0128] Example 31. A network node (1100, 1200) in a communication network, the network node comprising a processing circuit (1103, 1203) and a memory (1105, 1205) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the network node to perform an operation including any one of the operations of Examples 16 to 26.

[0129] Example 32. A network node (1100, 1200) in a communication network configured to perform any one of the operations of Examples 16 to 26.

[0130] Example 33. A computer program comprising program code executed by a processing circuit (1103, 1203) of a network node (1100, 1200) in a communication network, whereby execution of the program code causes a communication device to perform an operation including any one of the operations of Examples 16 to 26.

[0131] Example 34. A computer program product comprising a non-transitory storage medium including program code executed by a processing circuit (1103, 1203) of a network node (1100, 1200) in a communication network, whereby execution of the program code causes the network node to perform an operation including any one of the operations of Examples 16 to 26.

[0132] Additional explanations are provided below.

[0133] In general, all terms used in this specification should be interpreted according to their ordinary meanings in the relevant technical fields, unless they have distinct meanings and / or are suggested by the context in which they are used. All references to elements, devices, components, means, steps, etc. should be open to interpretation as referring to at least one instance of the element, device, component, means, step, etc., unless otherwise explicitly stated. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as being next or prior to another step and / or unless it is implied that a step must be next or prior to another step. Any feature of any embodiment disclosed herein may, where appropriate, be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the embodiments of this specification will become apparent from the following description.

[0134] Hereinafter, some of the embodiments contemplated in this specification will be further described with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0135] FIG. 15 shows a wireless network according to some embodiments.

[0136] The subject matter described in this specification may be implemented in any suitable type of system using any suitable components, but the embodiments disclosed herein are described in the context of a wireless network, such as the example wireless network shown in FIG. 15. For simplicity, the wireless network of FIG. 15 only shows network 4106, network nodes 4160 and 4160b, and wireless devices 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device such as a landline phone, a service provider, or any other network node or end device. For the illustrated components, network node 4160 and wireless device 4110 are depicted in more detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0137] A wireless network may comprise and / or interface with any type of communication, communication, data, cellular, and / or wireless network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards such as the Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, wireless local area network (WLAN) standards such as the IEEE 802.11 standard, and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0138] The network 4106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0139] The network node 4160 and the wireless device 4110 include various components that will be described in more detail below. These components may cooperate to provide the functions of the network node and / or the wireless device, such as providing a wireless connection in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relays, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, regardless of whether the connection is wired or wireless.

[0140] As used herein, a network node refers to a device that is configured to communicate, arranged to communicate, and / or operable to communicate directly or indirectly with a wireless device and / or other network nodes, or a device that enables and / or provides wireless access to a wireless device and / or performs other functions (e.g., management) of a wireless network. Examples of network nodes include, without limitation, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). The base stations may be categorized based on the amount of coverage provided by the base station (or equivalently, the transmission power level of the base station), and thus may also be referred to as femto base stations, pico base stations, micro base stations, macro base stations. The base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed wireless base station, such as a centralized digital unit and / or a remote radio unit (RRU), also sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna integrated radio. The parts of the distributed wireless base station may also be referred to as nodes of a distributed antenna system (DAS). Further additional examples of network nodes include MSR devices such as multi-standard radio (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-SMLC), and / or MDTs. As another example, a network node may be a virtual network node as described in more detail later.However, more generally, a network node may represent any suitable device (or group of devices) that is configured, arranged, and / or operable to enable a wireless device to access a wireless network, and / or to provide access to a wireless network to a wireless device, or to provide some service to a wireless device accessing the wireless network.

[0141] In FIG. 15, network node 4160 includes a processing circuit 4170, a device-readable medium 4180, an interface 4190, auxiliary equipment 4184, a power source 4186, a power circuit 4187, and an antenna 4162. Network node 4160 shown in the exemplary wireless network of FIG. 15 may represent a device including the shown combination of hardware components, but other embodiments may include network nodes having different combinations of components. It should be understood that a network node may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. Further, the components of network node 4160 are shown as a single box located within a larger box, or as a single box nested within multiple boxes, but in reality, a network node may comprise multiple different physical components that make up a single shown component (e.g., device-readable medium 4180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0142] Similarly, network node 4160 may be assembled from a plurality of physically distinct components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In a particular scenario where network node 4160 comprises a plurality of distinct components (e.g., a BTS component and a BSC component), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique pair of Node B and RNC may, in some cases, be regarded as a single distinct network node. In some embodiments, network node 4160 may be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components may be replicated (e.g., separate device-readable media 4180 for different RATs), and some components may be reused (e.g., the same antenna 4162 may be shared by RATs). Network node 4160 may also include a plurality of sets of various illustrated components related to different radio technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth radio technology, integrated into network node 4160. These radio technologies may be integrated into the same or different chips or chip sets, and other components within network node 4160.

[0143] Processing circuitry 4170 is configured to perform any decision-making operation, computational operation, or similar operation (e.g., a particular acquisition operation) described herein as being implemented by a network node. These operations performed by processing circuitry 4170 may include processing the information obtained by processing circuitry 4170, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a decision as a result of the above processing.

[0144] The processing circuit 4170, either alone or in combination with other network node 4160 components such as the device-readable medium 4180, may comprise one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide the functionality of the network node 4160. For example, the processing circuit 4170 may execute instructions stored on the device-readable medium 4180 or in a memory within the processing circuit 4170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 4170 may include a system on chip (SOC).

[0145] In some embodiments, the processing circuit 4170 may include one or more of a radio frequency (RF) transceiver circuit 4172 and a baseband processing circuit 4174. In some embodiments, the radio frequency (RF) transceiver circuit 4172 and the baseband processing circuit 4174 may be on separate chips (or chip sets), boards, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 4172 and the baseband processing circuit 4174 may be on the same chip or chip set, board, or unit.

[0146] In certain embodiments, some or all of the functionality described herein as provided by a network node, base station, eNB, or other such network device may be implemented by processing circuitry 4170 executing instructions stored in a device-readable medium 4180 or memory within the processing circuitry 4170. In an alternative embodiment, some or all of the functionality may be provided by the processing circuitry 4170 without executing instructions stored in a separate or discrete device-readable medium, such as in a hardwired manner. In any of these embodiments, whether or not executing instructions stored in a device-readable medium, the processing circuitry 4170 is configurable to perform the above functionality. The benefits resulting from such functionality are not limited to the processing circuitry 4170 alone or other components of the network node 4160, but are enjoyed by the network node 4160 as a whole and / or generally by end users and wireless networks.

[0147] The device-readable medium 4180 may include, without limitation, any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 4170. The device-readable medium 4180 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that are executable by the processing circuit 4170 and utilized by the network node 4160. The device-readable medium 4180 may be used to store any calculations performed by the processing circuit 4170 and / or any data received via the interface 4190. In some embodiments, the processing circuit 4170 and the device-readable medium 4180 may be considered integrated.

[0148] Interface 4190 is used in the wired or wireless communication of signaling and / or data between network node 4160, network 4106, and / or wireless device 4110. As shown in the figure, interface 4190 includes ports / terminals 4194 for data transmission to and data reception from network 4106, for example, via a wired connection. Interface 4190 also includes a radio front-end circuit 4192 that may be coupled to antenna 4162 or, in certain embodiments, may be part of antenna 4162. The radio front-end circuit 4192 includes a filter 4198 and an amplifier 4196. The radio front-end circuit 4192 may be connected to antenna 4162 and processing circuit 4170. The radio front-end circuit may be configured to condition signals communicated between antenna 4162 and processing circuit 4170. The radio front-end circuit 4192 may receive digital data that is to be transmitted to other network nodes or wireless devices via a wireless connection. The radio front-end circuit 4192 may convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of filter 4198 and / or amplifier 4196. The wireless signal may then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 may collect a wireless signal, and the wireless signal may then be converted into digital data by radio front-end circuit 4192. The digital data may be passed to processing circuit 4170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0149] In certain alternative embodiments, network node 4160 may not include a separate radio front-end circuit 4192. Instead, processing circuit 4170 may comprise a radio front-end circuit and may be connected to antenna 4162 without a separate radio front-end circuit 4192. Similarly, in some embodiments, all or part of RF transceiver circuit 4172 may be regarded as part of interface 4190. In still other embodiments, interface 4190 may, as part of a wireless unit (not shown), include one or more ports or terminals 4194, a radio front-end circuit 4192, and RF transceiver circuit 4172, and interface 4190 may communicate with baseband processing circuit 4174, which is part of a digital unit (not shown).

[0150] Antenna 4162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 4162 may be coupled to radio front-end circuit 4192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 4162 may comprise one or more omnidirectional, sector, or panel antennas operable to transmit / receive wireless signals, for example, in the 2 GHz to 66 GHz range. Omnidirectional antennas may be used to transmit / receive wireless signals in any direction, sector antennas may be used to transmit / receive wireless signals from devices within a particular area, and panel antennas may be line-of-sight antennas used to transmit / receive wireless signals in a relatively straight line. In some cases, the use of two or more antennas may be referred to as MIMO. In certain embodiments, antenna 4162 may be separate from network node 4160 and may be connectable to network node 4160 through an interface or port.

[0151] Antenna 4162, interface 4190, and / or processing circuit 4170 may be configured to perform any receiving operation and / or specific acquisition operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 4162, interface 4190, and / or processing circuit 4170 may be configured to perform any transmission operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0152] Power circuit 4187 may comprise a power management circuit or be coupled to a power management circuit and is configured to supply power for implementing the functionality described herein to the components of network node 4160. Power circuit 4187 may receive power from power source 4186. Power source 4186 and / or power circuit 4187 may be configured to provide power to the various components of network node 4160 in a form suitable for each component (e.g., at the voltage and current levels required by each component respectively). Power source 4186 may be either included in power circuit 4187 and / or network node 4160 or external thereto. For example, network node 4160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to power circuit 4187. As a further example, power source 4186 may comprise a battery or a power source in the form of a battery pack connected to or integrated with power circuit 4187. The battery may provide backup power in the event of a failure of the external power source. Other types of power sources, such as solar cell devices, may also be used.

[0153] An alternative embodiment of network node 4160 may be responsible for providing a particular aspect of the functionality of a network node, including either the functionality described herein, and / or any functionality necessary to support the subject matter described herein, and may include additional components other than those shown in FIG. 15. For example, network node 4160 may include a user interface device that enables the input of information to network node 4160 and also enables the output of information from network node 4160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions on network node 4160.

[0154] As used herein, a wireless device refers to a device that is capable of wirelessly communicating with a network node and / or another wireless device, configured, constructed, and / or operable to do so. Unless otherwise specified, the term wireless device may be used interchangeably with user equipment (UE) herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information in the air. In some embodiments, the wireless device may be configured to transmit and / or receive information without direct human interaction. For example, the wireless device may be designed to transmit information to the network at a predetermined schedule when triggered by an internal or external event, or in response to a request from the network. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), in-vehicle wireless terminal devices, etc. The wireless device can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, the wireless device may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another wireless device and / or network node.In this case, the wireless device may also be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As one specific example, the wireless device may be a UE implementing the 3GPP NB-IoT (narrow band internet of things) standard. Specific examples of such machines or devices include sensors, metering devices such as power meters, industrial machinery, or household or personal electrical appliances (e.g., refrigerators, televisions, etc.), and personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the wireless device may represent a vehicle or other equipment having the ability to monitor and / or report its operating status or other functions related to its operation. The wireless device as described above can represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the wireless device as described above may be a mobile entity, in which case it may be referred to as a mobile device or a mobile terminal.

[0155] As shown in the figure, the wireless device 4110 includes an antenna 4111, an interface 4114, a processing circuit 4120, a device-readable medium 4130, a user interface device 4132, an auxiliary device 4134, a power source 4136, and a power circuit 4137. The wireless device 4110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the wireless device 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or sets of chips as other components within the wireless device 4110.

[0156] Antenna 4111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 4114. In certain alternative embodiments, antenna 4111 may be separate from wireless device 4110 and may be connectable to wireless device 4110 via an interface or port. Antenna 4111, interface 4114, and / or processing circuit 4120 may be configured to perform any of the receiving or transmitting operations described herein as being performed by the wireless device. Any information, data, and / or signals may be received from a network node and / or another wireless device. In some embodiments, the wireless front-end circuit and / or antenna 4111 may be regarded as an interface.

[0157] As shown in the figure, interface 4114 includes a radio frequency front-end circuit 4112 and an antenna 4111. The radio frequency front-end circuit 4112 includes one or more filters 4118 and an amplifier 4116. The radio frequency front-end circuit 4112 is connected to the antenna 4111 and the processing circuit 4120, and is configured to adjust signals communicated between the antenna 4111 and the processing circuit 4120. The radio frequency front-end circuit 4112 may be coupled to the antenna 4111 or may be part of the antenna 4111. In some embodiments, the wireless device 4110 may not include a separate radio frequency front-end circuit 4112. Instead, the processing circuit 4120 may include a radio frequency front-end circuit and may be connected to the antenna 4111. Similarly, in some embodiments, some or all of the RF transceiver circuit 4122 may be regarded as part of the interface 4114. The radio frequency front-end circuit 4112 may receive digital data that is to be sent to other network nodes or wireless devices via a wireless connection. The radio frequency front-end circuit 4112 may convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of the filters 4118 and / or the amplifier 4116. The wireless signal may then be transmitted via the antenna 4111. Similarly, when receiving data, the antenna 4111 may collect a wireless signal, and the wireless signal may then be converted into digital data by the radio frequency front-end circuit 4112. The digital data may be passed to the processing circuit 4120. In other embodiments, the interface may include different components and / or different combinations of components.

[0158] The processing circuit 4120 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide the wireless device 4110 functionality, either alone or in conjunction with other wireless device 4110 components such as the device readable medium 4130. Such functionality may include providing any of the various wireless features or benefits contemplated herein. For example, the processing circuit 4120 may execute instructions stored on the device readable medium 4130 or in memory within the processing circuit 4120 to provide the functionality disclosed herein.

[0159] As shown, processing circuit 4120 includes one or more of RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In certain embodiments, the processing circuit 4120 of wireless device 4110 may comprise a system-on-a-chip (SOC). In some embodiments, RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be on separate chips or chip sets. In an alternative embodiment, some or all of baseband processing circuit 4124 and application processing circuit 4126 may be combined into one chip or chip set, and RF transceiver circuit 4122 may be on a separate chip or chip set. In a further alternative embodiment, some or all of RF transceiver circuit 4122 and baseband processing circuit 4124 may be on the same chip or chip set, and application processing circuit 4126 may be on a separate chip or chip set. In yet another alternative embodiment, some or all of RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be combined within the same chip or chip set. In some embodiments, RF transceiver circuit 4122 may be part of interface 4114. RF transceiver circuit 4122 may condition RF signals for processing circuit 4120.

[0160] In some embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 4120 that executes instructions stored on a device-readable medium 4130, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4120 without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of these particular embodiments, whether or not executing instructions stored on a device-readable medium, processing circuitry 4120 is configurable to perform the above functionality. The benefits provided by such functionality are not limited to processing circuitry 4120 alone or to other components of wireless device 4110, but are enjoyed by wireless device 4110 as a whole and / or generally by an end user and a wireless network.

[0161] Processing circuitry 4120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 4120, may include, for example, processing information obtained by processing circuitry 4120 by converting the obtained information to other information, comparing the obtained or converted information to information stored by wireless device 4110, and / or performing one or more operations based on the obtained or converted information, and making a determination as a result of the processing.

[0162] The device-readable medium 4130 may be operative to store a computer program, software, an application (including one or more of logic, rules, code, tables, etc.), and / or other instructions that are executable by the processing circuit 4120. The device-readable medium 4130 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disc (CD) or a digital video disc (DVD)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that may store information, data, and / or instructions used by the processing circuit 4120. In some embodiments, the processing circuit 4120 and the device-readable medium 4130 may be considered integrated.

[0163] The user interface device 4132 may provide components that enable a human user to interact with the wireless device 4110. Such interactions can be in many forms, such as visual, auditory, tactile, etc. The user interface device 4132 may be operable to produce an output to the user and to enable the user to provide an input to the wireless device 4110. The type of interaction may vary depending on the type of user interface device 4132 installed on the wireless device 4110. For example, if the wireless device 4110 is a smartphone, the interaction may be via a touch screen, and if the wireless device 4110 is a smart meter, the interaction may be via a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an alarm sound (e.g., when smoke is detected). The user interface device 4132 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 4132 is configured to enable the input of information to the wireless device 4110 and is connected to the processing circuit 4120 to enable the processing circuit 4120 to process the input information. The user interface device 4132 may include, for example, a microphone, a proximity or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 4132 is also configured to enable the output of information from the wireless device 4110 and to enable the processing circuit 4120 to output information from the wireless device 4110. The user interface device 4132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuits. Using one or more of the input and output interfaces, devices, and circuits of the user interface device 4132, the wireless device 4110 may communicate with an end user and / or a wireless network and may enable them to benefit from the functionality described herein.

[0164] Auxiliary device 4134 is operable to provide more specific functionality that may not generally be performed by a wireless device. This may include specialized sensors for performing measurements for various purposes, interfaces for additional types of communication such as wired communication, and the like. The inclusion of components of auxiliary device 4134, and the types of components of auxiliary device 4134, may vary depending on the embodiment and / or scenario.

[0165] Power source 4136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. Wireless device 4110 may further include a power circuit 4137 for delivering power from power source 4136 to various parts of wireless device 4110 that require power to perform any of the functionality described or shown herein. Power circuit 4137 may, in certain embodiments, include a power management circuit. Power circuit 4137 may additionally or alternatively be operable to receive power from an external power source, in which case wireless device 4110 may be connectable to an external power source (such as an electrical outlet) via an interface such as an input circuit or an electrical power cable. Power circuit 4137 may also, in certain embodiments, be operable to deliver power from an external power source to power source 4136. This may be, for example, for charging power source 4136. Power circuit 4137 can perform any formatting, conversion, or other modification to the power from power source 4136 to make the power suitable for each component of wireless device 4110 to which the power is supplied.

[0166] FIG. 16 shows an exemplary embodiment of a UE according to 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 associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to, or operation by, a human user but may not be associated with, or initially associated with, a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to, or operation by, an end user but may be associated with a user or operated for the benefit of a user. UE 4200 may be any UE identified by the Third Generation Partnership Project (3GPP), including a narrowband Internet of Things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As shown in FIG. 16, UE 4200 is an example of a wireless device configured for communication according to one or more communication standards promulgated by 3GPP, such as the GSM, UMTS, LTE, and / or 5G standards of the Third Generation Partnership Project (3GPP). As noted above, the terms wireless device and UE may be used synonymously. Thus, while FIG. 16 shows a UE, the components considered herein are equally applicable to a wireless device, and vice versa.

[0167] In FIG. 16, the UE 4200 includes a processing circuit 4201 operably coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, a memory 4215 (including a random access memory (RAM) 4217, a read-only memory (ROM) 4219, and a storage medium 4221, etc.), a communication subsystem 4231, a power supply 4213, and / or other components, or any combination thereof. The storage medium 4221 includes an operating system 4223, an application program 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. A particular UE may utilize all or only a subset of the components shown in FIG. 16. The level of integration between components may vary from UE to UE. Further, a particular UE may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0168] In FIG. 16, the processing circuit 4201 may be configured to process computer instructions and data. The processing circuit 4201 may be any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more program-embedded general-purpose processors such as a microprocessor or a digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 4201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0169] In the illustrated embodiment, the input / output interface 4205 may be configured to provide a communication interface to an input device, an output device, or an input / output device. The UE 4200 may be configured to use an output device via the input / output interface 4205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 4200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 4200 may be configured to enable a user to capture information to the UE 4200 using an input device via the input / output interface 4205. 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 track pad, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor that senses input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0170] In FIG. 16, the RF interface 4209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 4211 may be configured to provide a communication interface to the network 4243a. The network 4243a may include wired and / or wireless networks such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 4243a may comprise a Wi-Fi network. The network connection interface 4211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices through a communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 4211 may implement receiver and transmitter functionality suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or may be implemented separately.

[0171] The RAM 4217 may be configured to interface connect to the processing circuit 4201 via the bus 4202 to store or cache data or computer instructions during the execution of software programs such as an operating system, application programs, and device drivers. The ROM 4219 may be configured to provide computer instructions or data to the processing circuit 4201. For example, the ROM 4219 may be configured to store invariant low-level system code or data related to basic system functions such as basic input / output (I / O), startup, or reception of keystrokes from a keyboard, stored in a non-volatile memory. The storage medium 4221 may be configured to include a memory such as a RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 4221 may be configured to include an operating system 4223, an application program 4225 such as a web browser application, widget, or gadget engine, or another application, and a data file 4227. The storage medium 4221 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 4200.

[0172] The memory medium 4221 may be configured to include a number of physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-definition digital versatile disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a subscriber identity module or removable user identity information (SIM / RUIM) module such as a smart card memory, other memories, or any combination thereof. The memory medium 4221 may enable the UE4200 to access computer-executable instructions, application programs, etc. stored in a temporary or non-temporary memory medium, offload data, or upload data. A manufactured product, such as a manufactured product using a communication system, may be tangibly embodied in the memory medium 4221, which may include a device-readable medium.

[0173] In FIG. 16, the processing circuit 4201 can be set to communicate with the network 4243b using the communication subsystem 4231. The network 4243a and the network 4243b can be the same one or more networks, or different one or more networks. The communication subsystem 4231 can be set to include one or more transceivers used to communicate with the network 4243b. For example, the communication subsystem 4231 can communicate with one or more remote transceivers of another wireless device capable of wireless communication, such as another wireless device of a radio access network (RAN), a UE, or a base station, according to one or more communication protocols such as IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc., and can be set to include one or more transceivers. Each transceiver may include a transmitter 4233 and / or a receiver 4235 that respectively implement the functionality of a transmitter or a receiver suitable for a RAN link (e.g., frequency allocation, etc.). Further, the transmitter 4233 and the receiver 4235 of each transceiver may share circuit components, software, or firmware, or may be implemented separately.

[0174] In an exemplary embodiment, the communication functions of the communication subsystem 4231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) to determine location, other similar communication functions, or any combination thereof. For example, the communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 4243b may include wired and / or wireless networks such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, other similar networks, or any combination thereof. For example, the network 4243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 4213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 4200.

[0175] The features, benefits, and / or functions described herein may be implemented in one of the components of the UE 4200 or may be divided across multiple components of the UE 4200. Further, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 4231 may be configured to include any of the components described herein. Further, the processing circuit 4201 may be configured to communicate with any of such components through the bus 4202. In another example, any of such components may be represented by program instructions stored in a memory that, when executed by the processing circuit 4201, implement the corresponding functions described herein. In another example, the functionality of any of such components may be divided between the processing circuit 4201 and the communication subsystem 4231. In another example, the non-computation-intensive functions of any of such components may be implemented in software or firmware, and the computation-intensive functions may be implemented in hardware.

[0176] FIG. 17 is a schematic block diagram showing a virtualized environment 4300 in which functions implemented according to some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing a hardware platform, a memory device, and networking resources. As used herein, virtualization is applicable 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 its components, and is related to an implementation in which at least a part of a function is executed as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0177] 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 environments 4300 hosted by one or more of the hardware nodes 4330. Further, in embodiments where the virtual node is not a radio access node or does not require wireless connectivity (e.g., a core network node), the network node may be fully virtualized.

[0178] The functionality may be implemented by one or more applications 4320 (which may sometimes be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that are operable to implement some of the features, functionality, and / or benefits of the embodiments disclosed herein. The application 4320 is executed in a virtualization environment 4300 that provides hardware 4330 including a processing circuit 4360 and a memory 4390. The memory 4390 includes instructions 4395 that, when executed by the processing circuit 4360, enable the application 4320 to operate to provide one or more of the features, benefits, and / or functionality disclosed herein.

[0179] The virtualized environment 4300 comprises a general-purpose or dedicated network hardware device 4330 comprising a set of one or more processors or processing circuitry 4360, which may be a commercial off-the-shelf (COTS) processor, a dedicated application-specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may comprise a memory 4390-1, which may be a non-persistent memory for temporarily storing instructions 4395 or software executed by the processing circuitry 4360. Each hardware device may comprise one or more network interface controllers (NICs) 4370, also known as network interface cards, including a physical network interface 4380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 4390-2 storing software 4395 and / or instructions executable by the processing circuitry 4360. The software 4395 may include any type of software including software for instantiating one or more virtualization layers (also referred to as hypervisors) 4350, software for executing virtual machines 4340, and software enabling the software to perform the functions, features, and / or benefits described in some embodiments described herein.

[0180] The virtual machine 4340 comprises virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be operated by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of the virtual appliance 4320 may be implemented in one or more of the virtual machines 4340, and the implementation may be performed in different ways.

[0181] During operation, the processing circuit 4360 executes software 4395 to instantiate a hypervisor or virtualization layer 4350, sometimes referred to as a virtual machine monitor (VMM). The virtualization layer 4350 may present a virtual operating platform to the virtual machines 4340 that appears as networking hardware.

[0182] As shown in FIG. 17, the hardware 4330 may be a stand-alone network node with general or specific components. The hardware 4330 may include an antenna 43225 and may implement some functions through virtualization. Alternatively, the hardware 4330 may be part of a larger class of hardware (such as in the case of a data center or customer premise equipment (CPE)) that is managed through a management and orchestration (MANO) 43100 where multiple hardware nodes work together, especially overseeing the lifecycle management of the application 4320.

[0183] In some contexts, the virtualization of hardware is 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 areas that can be placed in a data center, as well as on customer premise equipment.

[0184] In the context of NFV, the virtual machine 4340 may be a software implementation of a physical machine that runs a program as if it were running on a physical, non-virtualized machine. The virtual machine 4340 and the portion of the hardware 4330 that executes the virtual machine constitute a separate virtual network element (VNE) when the virtual machine has dedicated hardware and / or when the virtual machine shares hardware with other virtual machines 4340.

[0185] Furthermore, in the context of NFV, a virtual network function (VNF) is responsible for processing specific network functions that operate in one or more virtual machines 4340 on the hardware network infrastructure 4330 and corresponds to the application 4320 of FIG. 17.

[0186] In some embodiments, one or more radio units 43200, each including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio unit 43200 may communicate directly with the hardware node 4330 via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node having radio capabilities, such as a radio access node or a base station.

[0187] In some embodiments, some signaling can be achieved using a control system 43230 that may alternatively be used for communication between the hardware node 4330 and the radio unit 43200.

[0188] FIG. 18 shows a communication network connected to a host computer via an intermediate network according to some embodiments.

[0189] Referring to FIG. 18, according to one embodiment, a communication system includes a communication network 4410 such as a 3GPP-type cellular network including an access network 4411 such as a radio access network and a core network 4414. The access network 4411 includes a plurality of base stations 4412a, 4412b, 4412c, such as NB, eNB, gNB, or other types of radio access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to the core network 4414 over a wired or wireless connection 4415. A first UE 4491 located within the coverage area 4413c is configured to wirelessly connect to the corresponding base station 4412c or be paged by the corresponding base station 4412c. A second UE 4492 in the coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. In this example, a plurality of UEs 4491, 4492 are shown, but the disclosed embodiments are equally applicable to a situation where one UE is present in a coverage area or a situation where one UE connects to the corresponding base station 4412.

[0190] The communication network 4410 itself is connected to a host computer 4430, which can be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, or a distributed server, or as processing resources in a server farm. The host computer 4430 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 4421 and 4422 between the communication network 4410 and the host computer 4430 can extend directly from the core network 4414 to the host computer 4430, or can extend via an optional intermediate network 4420. The intermediate network 4420 can be one of a public network, a private network, or a host-type network, or a combination of two or more thereof, and the intermediate network 4420, if present, can be a backbone network or the Internet, and in particular, the intermediate network 4420 can comprise two or more sub-networks (not shown).

[0191] The communication system of FIG. 18 enables connectivity overall between the connected UEs 4491, 4492 and the host computer 4430. The connectivity can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491, 4492 are configured to communicate data and / or signaling via the OTT connection 4450 using, as intermediaries, the access network 4411, the core network 4414, any intermediate network 4420, and possibly additional infrastructure (not shown). The OTT connection 4450 can be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes do not recognize the routing of uplink and downlink communications. For example, when data originating from the host computer 4430 is transferred (e.g., handed over) to the connected UE 4491, the base station 4412 may not be informed of, or need to be informed of, the past routing of the incoming downlink communication. Similarly, the base station 4412 need not be aware of the future routing of the outgoing uplink communication originating from the UE 4491 and going towards the host computer 4430.

[0192] In the foregoing description of various embodiments of the inventive concept, it should be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the inventive concept. Unless otherwise defined, all terms (including technical and scientific terms) used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concept pertains. Terms such as those defined in commonly used dictionaries shall be interpreted as having a meaning that conforms to their meaning in the context of the present specification and the relevant art, and shall not be interpreted in an idealized or overly formal sense unless expressly so defined herein. When an element is said to be "connected to", "coupled to", "responsive to", or a variation thereof, with respect to another element, the element can be directly connected to, coupled to, or responsive to the other element, or intervening elements may be present. In contrast, when an element is said to be "directly connected to", "directly coupled to", "directly responsive to", or a variation thereof, with respect to another element, no intervening elements are present. Like numbers refer to like elements throughout. Further, as used herein, "coupled to", "connected to", "responsive to", or variations thereof can include wirelessly coupled to, wirelessly connected to, or wirelessly responsive to. As used herein, the singular forms "a", "an" and "the" include the plural forms as well, unless the context clearly indicates otherwise. For brevity and / or clarity, well-known functions or constructions may not be described in detail. The term "and / or" (abbreviated " / ") includes any and all combinations of one or more of the associated listed items.

[0193] To describe various elements / acts, the terms first, second, third, etc. may be used herein, but it should be understood that these elements / acts are not to be limited by these terms. These terms are only used to distinguish one element / act from another. Thus, a first element / act in some embodiments may, without departing from the teachings of the inventive concept, be referred to as a second element / act in other embodiments. The same reference numeral or the same reference sign indicates the same or like elements throughout this specification.

[0194] As used herein, the terms "comprise," "comprising," "comprises," "include," "including," "includes," "have," "has," "having," or variations thereof are open-ended and include one or more recited features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Further, as used herein, the common abbreviation "e.g.", which is derived from the Latin phrase "exempli gratia," may be used to introduce or specifically mention one or more general examples of the foregoing items and is not limiting of such items. The common abbreviation "i.e.", which is derived from the Latin phrase "id est," may be used to specifically mention a particular item from a more general recitation.

[0195] Exemplary embodiments are described herein with reference to block diagrams and / or flowchart diagrams of a computer-implemented method, apparatus (system and / or device) and / or computer program product. It should be understood that the blocks of the block diagrams and / or flowchart diagrams, as well as combinations of blocks in the block diagrams and / or flowchart diagrams, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to the processor circuits of a general-purpose computer circuit, a special-purpose computer circuit, and / or other programmable data processing circuits to create a machine, whereby the instructions executed via the processor of the computer and / or other programmable data processing device implement the functions / acts specified in one or more blocks of the block diagram and / or flowchart, and thereby, to transform and control transistors, values stored in memory locations, and other hardware components within such circuits to create means (functions) and / or structures for implementing the functions / acts specified in the blocks of the block diagram and / or flowchart.

[0196] These computer program instructions can also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing device to function in a particular manner, whereby the instructions stored in the computer-readable medium produce a manufacture including instructions for implementing the functions / acts specified in one or more blocks of the block diagram and / or flowchart. Accordingly, embodiments of the inventive concept can be embodied in hardware and / or software (including firmware, resident software, microcode, etc.) running on a processor such as a digital signal processor, which may sometimes be generically referred to as a "circuit", "module" or variations thereof.

[0197] Also, note that in some alternative implementations, the functions / acts recited in a block may occur out of the order recited in the flowchart. For example, two blocks shown in succession may in fact be executed substantially in parallel depending on the related functions / acts, or the blocks may sometimes be executed in reverse order. Additionally, the functionality of a given block in a flowchart and / or block diagram may be split into multiple blocks, and / or the functionality of two or more blocks in a flowchart and / or block diagram may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks shown, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Also, understand that although some of the figures include arrows on communication paths to indicate a primary direction of communication, communication may occur in the direction opposite to that shown by the arrows.

[0198] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be regarded as illustrative and not restrictive, and the examples of embodiments are intended to cover all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Accordingly, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including examples of embodiments and their equivalents, and should not be limited or restricted by the foregoing detailed description.

Claims

1. A method for operating a communication device in a communication network, the method comprising: receiving (1320) an indication from a network node within the communication network, the indication indicating one of: the presence of a tracking reference signal (TRS) at a reference signal occasion; the possibility that the TRS may or may not be present at the reference signal occasion; or the absence of the TRS at the reference signal occasion; the indication including an indication of a validity timer, the validity timer indicating a duration for which the TRS is present at the reference signal occasion; A method comprising the above.

2. decoding (1370) a paging message using the TRS indicated by the indication at a paging occasion following the reference signal occasion; The method according to claim 1, further comprising the above.

3. monitoring system information, the system information including configuration information related to a TRS occasion and / or a potential TRS occasion; The method according to claim 1 or 2, further comprising the above.

4. The method according to any one of claims 1 to 3, wherein receiving the indication includes receiving at least one parameter indicating a location of a TRS presence / absence indicator field ("TIF") in a downlink control information (DCI) format.

5. receiving the indication includes receiving the indication indicating the presence of the TRS at the reference signal occasion; the method comprising: receiving (1360) the TRS at the reference signal occasion in response to receiving the indication indicating the presence of the TRS at the reference signal occasion; The method according to any one of claims 1 to 4, further comprising the above.

6. receiving the indication includes receiving the indication indicating that the TRS may or may not be present at the reference signal occasion; the method comprising: In response to receiving the indication indicating that the TRS may or may not exist at the time of the reference signal occasion, determining whether to attempt blind detection of the TRS at the time of the reference signal occasion (1350) The method according to any one of claims 1 to 4, further comprising. **Claim 7** A method of operating a network node in a communication network, the method comprising Determining whether to transmit a tracking reference signal (TRS) at the time of a reference signal occasion (1410); Transmitting an indication to a communication device within the communication network (1440), the indication including transmitting an indication indicating one of the presence of a reference signal at the time of a reference signal occasion, the possibility of the presence or absence of a reference signal at the time of a reference signal occasion, or the absence of the reference signal at the time of the reference signal occasion; The indication includes an indication of a validity timer, and the validity timer indicates a duration for which the TRS exists at the time of a reference signal occasion, including an indication of a validity timer. A method comprising. **Claim 8** Transmitting the indication includes transmitting the indication indicating the presence of the reference signal at the time of the reference signal occasion; The method comprises In response to transmitting the indication indicating the presence of the reference signal at the time of the reference signal occasion, transmitting the reference signal at the time of the reference signal occasion (1450) The method according to claim 7, further comprising. **Claim 9** Subsequent to transmitting the indication, transmitting a paging message (1460) The method according to claim 7 or 8, further comprising. **Claim 10** Transmitting the indication includes transmitting downlink control information (DCI) including the indication, the DCI being one of paging DCI and paging early indication DCI, transmitting DCI; Including, the method comprising Transmitting a message including at least one of the length and location of the indication in the DCI (1420) The method according to any one of claims 7 to 9, further comprising.

11. Transmitting system information, wherein the system information includes configuration information related to a TRS occasion and / or a potential TRS occasion The method according to any one of claims 7 to 10, further comprising:

12. Transmitting the indication includes transmitting at least one parameter indicating a location of a TRS presence / absence indicator field ("TIF") in a downlink control information (DCI) format. The method according to any one of claims 7 to 11.

13. A communication device (1000, 4110) in a communication network, the communication device comprising: A processing circuit (1003, 4120); A memory (1005, 4130) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the communication device to perform an operation including any one of the operations of claims 1 to 6. A communication device (1000, 4110) in a communication network, comprising:

14. A network node (1100, 4160) in a communication network, the network node comprising: A processing circuit (1103, 4170); A memory (1105, 4180) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the network node to perform an operation including any one of the operations of claims 7 to 12. A network node (1100, 4160) in a communication network, comprising:

15. A computer program comprising program code executed by a processing circuit (1003, 4120, 1103, 4170) to perform an operation including any one of the operations of claims 1 to 12.

16. A non-transitory storage medium including program code executed by a processing circuit (1003, 4120, 1103, 4170) to perform an operation including any one of the operations of claims 1 to 12.

Citation Information

Patent Citations

  • Terminal, base station, and paging method

    WO2022074748A1