Patent Description:
The scope of Rel-<NUM> MIMO enhancements stated in RP-<NUM> (Reference [<NUM>]) WID Enhancements on MIMO for NR (September <NUM>) includes the following objectives for multi-transmit receive point (TRP)/panel transmission including improved reliability and robustness with both ideal and non-ideal backhaul: Specify downlink control signaling enhancement(s) for efficient support of non-coherent joint transmission; Perform study and, if needed, specify enhancements on uplink control signaling and/or reference signal(s) for non-coherent joint transmission; and Include multi-TRP techniques for ultra-reliable low-latency communication (URLLC) requirements.

RAN1 has been working with two variants of this:.

3GPP RAN1 has sent the following LSs to 3GPP RAN2 on this WI:.

Based on the LSs received, the multiTRP operation may be supported with multiple PDCCHs (same or different cellID) or with one PDCCH (same cell ID). The LS in [<NUM>] treats only multi-PDCCH transmission and includes:
For multiple PDCCH based multi-TRP/panel transmission, the total number of code words (CWs) in scheduled PDSCHs, each of which is scheduled by one PDCCH, is up to <NUM> and also the total number of MIMO layers of scheduled PDSCHs is up to reported UE MIMO capability, if resource allocation of PDSCHs are overlapped.

To support multiple-PDCCH based multi-TRP/panel transmission with intra-cell (same cell ID) and inter-cell (different Cell IDs), RRC configuration can be used to link multiple PDCCH/PDSCH pairs with multiple TRPs. One CORESET in a "PDCCH-config" corresponds to one TRP.

Separate ACK/NACK payload/feedback for received PDSCHs is supported. For separate ACK/NACK payload/feedback for received PDSCHs where multiple DCIs are used, PUCCH resources conveying ACK/NACK feedback can be TDM with separated HARQ-ACK codebook.

The LS in Reference [<NUM>] includes RAN1 agreements across the MIMO WI and the multi-TRP related are discussed below.

On multiple PDCCH based multi-TRP/panel transmission, for multi-PDCCH based multi-TRP operation, increase the maximum number of CORESETs per "PDCCH-config" to <NUM>, according to UE capability.

For separate ACK/NACK feedback for PDSCHs received from different TRPs, the UE should be able to generate separate ACK/NACK codebooks identified by an index, if the index is configured and applied across all CCs. The index to be used to generate separated ACK/NACK codebook is a higher layer signalling index per CORESET. Note that the index may not be configured for scenarios if there is no ambiguity of codebook generation at the UE, e.g. slot based PUCCH resource allocation per TRP. This does not preclude configuring the index for other purposes.

At least for eMBB with M-DCI NCJT in order to generate different PDSCH scrambling sequences, support enhancing RRC configuration to configure multiple dataScramblingIdentityPDSCH.

For rate matching mechanism used for multi-DCI based multi-TRP/panel transmission and for LTE CRS, extending lte-CRS-ToMatchAround to be configured with multiple CRS patterns in a serving cell.

Beam management in Release <NUM> of NR was designed for a situation where multiple beams cover one cell. Due to the smaller coverage area of these narrow beams, it could be anticipated that a UE would change beam more frequently than it changes cells. To reduce the signaling load for the beam switches, it was decided that RRC signaling would not be required to facilitate such changes. Instead, a signaling solution based on Medium Access Control protocol (MAC) Control Element (CE) or DCI has been introduced for beam management / intra-cell mobility. <FIG> illustrates beam switching within the same cell, with intra-cell beam management, and with no RRC signalling involved for the switching.

Three examples of sub-functionality to support beam management are L1-RSRP reporting on SSB and CSI-RS; MAC CE based activation/deactivation updates of beam indications, so-called Quasi-Co-Location (QCL) source, explained in the following in more details); and beam failure recovery / radio link monitoring / beam failure detection.

As these functionalities were designed to handle mobility without RRC involvement, they were limited to intra-cell operation. Following is a description of some existing fundamental concepts in the <NUM> NR L1 specifications that are relevant for the present disclosure, namely, beam indications, Quasi-Co-Location (QCL) source and TCI states.

Beam indications, Quasi-Co-Location (QCL) source and TCI states are discussed below.

Several signals can be transmitted from the same base station antenna from different antenna ports. These signals can have the same large-scale properties, for instance in terms of Doppler shift/spread, average delay spread, or average delay, when measured at the receiver. These antenna ports are then said to be quasi co-located (QCL).

The network can then signal to the UE that two antenna ports are QCL so that the UE interprets that signals from these will have some similar properties. If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g. Doppler spread), the UE can estimate that parameter based on a reference signal transmitted from one of the antenna ports and use that estimate when receiving another reference signal or physical channel from the other antenna port. Typically, the first antenna port is represented by a measurement reference signal such as a CSI-RS (known as source RS) and the second antenna port is a demodulation reference signal (DMRS) (known as target RS) for PDSCH or PDCCH reception.

For instance, if antenna ports A and B are QCL with respect to average delay, the UE can estimate the average delay from the signal received from antenna port A (known as the source reference signal (RS)) and assume that the signal received from antenna port B (target RS) has the same average delay. This is useful for demodulation since the UE can know beforehand the properties of the channel when trying to measure the channel utilizing the DMRS, which may help the UE in for instance selecting an appropriate channel estimation filter.

Information about what assumptions can be made regarding QCL is signaled to the UE from the network. In NR, four types of QCL relations between a transmitted source RS and transmitted target RS are defined:.

QCL type D was introduced to facilitate beam management with analog beamforming and is known as spatial QCL. There is currently no strict definition of spatial QCL, but the understanding is that if two transmitted antenna ports are spatially QCL, the UE can use the same Rx beam to receive them. This is helpful for a UE that uses analog beamforming to receive signals, since the UE needs to adjust its RX beam in some direction prior to receiving a certain signal. If the UE knows that the signal is spatially QCL with some other signal it has received earlier, then it can safely use the same RX beam to receive also this signal. Note that for beam management, the discussion mostly revolves around QCL Type D, but it may also be necessary to convey a Type A QCL relation for the RSs to the UE, so that it can estimate all the relevant large-scale parameters.

Typically, this is achieved by configuring the UE with a CSI-RS for tracking (TRS) for time/frequency offset estimation. To be able to use any QCL reference, the UE would have to receive it with a sufficiently good SINR. In many cases, this means that the TRS has to be transmitted in a suitable beam to a certain UE.

Together with the concept of QCL source is the concept of a transmission configuration information (TCI) state. Each of the M states in a list of TCI states can be interpreted as a list of M possible beams transmitted in the downlink from the network and/or a list of M possible TRPs used by the network to communicate with the UE. The M TCI states can also be interpreted as a combination of one or multiple beams transmitted from one or multiple TRPs.

Each TCI state contains the previously described QCL information, i.e. one or two source downlink reference signals (RS), where each source RS associated with a QCL type. For example, a TCI state contains a pair of reference signals, each associated with a QCL type, e.g. two different CSI-RSs {CSI-RS1, CSI-RS2} is configured in the TCI state as {qcl-Type1, qcl-Type2} = {Type A, Type D}. It means the UE can derive Doppler shift, Doppler spread, average delay, delay spread from CSI-RS1 and Spatial Rx parameter (i.e. the RX beam to use) from CSI-RS2. In terms of RRC signaling, a TCI state is represented by an IE called TCI-State as shown in Table <NUM> below.

The TCI-State IE may be included in an RRC message transmitted to the UE, such as an RRCReconfiguration message.

As it is shown above in the TCI-State IE definition, there is a field called cell. According to the definition in TS <NUM> (Reference [<NUM>]), the field called cell in the QCL-Info configuration (i.e. cell field of IE ServCellIndex) is the UE's serving cell in which the Reference Signal that is QCL source is being configured. If the field is absent, it applies to the serving cell in which the TCI-State is configured (i.e. the spCell of the cell group, not an indexed SCell). The RS can be located on a serving cell other than the serving cell in which the TCI-State is configured only if the qcl-Type is configured as type D (see TS <NUM>, Reference [<NUM>], section <NUM>.

Existing approaches, however, may not adequately address configuration of radio link monitoring, radio resource management, and/or spatial relations.

An <NPL>) describes how the beam management functionality standardized in Release-<NUM> can be used to improve handover (HO) robustness and to achieve <NUM> handover interruption.

A <NPL>) discusses beam-based solutions to improve HO/SCG change reliability and robustness and enhancements for mobility.

Aspects of the invention are set out in the independent claims appended hereto.

According to some embodiments, by providing the first and second IEs with the indication of the added SSB/PCI (where the second IE relates to at least one of CSI, RLM, UL power control, and/or UL spatial relations), improved support for inter-cell multi-TRP reception may be provided.

It has been argued in R1-<NUM> (Reference [<NUM>]) - Lower-layer mobility enhancements that the only thing that is needed for the UE to be able to start receiving data on the physical layer in the target cell is that the QCL source is updated. This would enable the UE to align to the target cell in an indicated direction to demodulate the bits and decode the data.

The RRC IE that carries the QCL source is called TCI-state, as shown in Table <NUM>.

The TCI-state IE contains pointers to reference signal(s). The reference signals are implicitly associated with a serving cell via a serving cell integer index. Hence, in Rel-<NUM>, it is only possible to change QCL source to reference signals transmitted within a serving cell (SpCell or associated SCell within that SpCell group). It is not possible to change the QCL source to a reference signal in a non-serving cell.

To be able to use this functionality, it has been proposed in R1-<NUM> - Lower-layer mobility enhancements to introduce an identifier of the non-serving cell in the QCL-info where as proposed, a natural choice for such an identifier is the physical cell identity (PCI).

If a PCI were introduced in the QCL-info, the network could update the QCL source to an RS in a non-serving cell. Once the indication command takes effect, the network can directly start transmitting data over PDSCH from the new cell. Since the procedure is synchronized, the network and the UE have the same understanding of when the updated configuration takes effect. Thus, the interruption in data communication can be eliminated.

However, there remains a problem as to how to configure functionality for the other TRPs, such as radio link monitoring, radio resource management, spatial relations, etc. One approach is to add a list of additional SSBs (including PCI) in ServingCellConfig and add a reference to one entry of that list in QCL-Info (only included when the reference is SSB). The ServingCellConfig IE is communicated to the UE by the network via an RRC message, such as RRCReconfiguration.

When QCL-Info is updated with PCI information, it essentially means that the SSB of which the PCI belongs to becomes signaled in serving cell configurations. Currently, each serving cell has one SSB(PCI) associated to it and CSI, radio link monitoring when configured separately, are based on the SSB(PCI) currently given in ServingCellConfigCommon.

If new SSB(PCI) are added to serving cell configuration, it is unclear how these will be used by the UE. For example, the UE might interpret the new SSB(PCI) as belonging to the serving cell rather than another TRP.

Some embodiments described herein provide a method for a UE to consider multiple sets of SSB, where each set has its independent PCI configured for the UE, in serving cell configuration. Some embodiments described herein provide details for the configuration of multiple sets of SSBs. Hence, under a serving cell, a unique SSB can be indicated by the pair {SSB index; PCI} in contrast to the approach in Rel-<NUM> where only SSB index was used to address a unique SSB. For the UE to use the SSB(PCI), it is desirable for the added SSB(PCI) to be included in other IEs in the RRCReconfiguration message. For example, some embodiments may allow further features to be enabled, as discussed below.

CSI reporting related to transmission from a TRP that has another SSB(PCI) associated to it. In order to report L1-RSRP based on SSB of the added SSB(PCI), the added SSB(PCI) needs to be indicated to the UE in CSI-SSB-ResourceSet in CSI-MeasConfig.

Radio link monitoring (RLM) configuration from a TRP that has another SSB(PCI) associated to it.

Radio Resource Management (RRM) from a TRP in has another SSB(PCI) associated to it.

UL power control associated to a TRP in has another SSB(PCI) associated to it.

Spatial relations association to a TRP in has another SSB(PCI) associated to it.

Determining MAC CE format taking added SSB(PCI) into account.

According to some embodiments, it may be possible to support inter-cell multi-TRP reception.

For purposes of the following discussion, it is assumed the ServingCellConfig IE includes in one of its IEs the list of added SSB(PCI)s. The additional SSBs are referred to herein as "added SSB(PCI)" and it is assumed that each of these is identified by an ID.

In one embodiment, each item of the "added SSB(PCI)" includes one or more of: an identifier (referred here as "addedSSB_Id"), PCI, SSB measurement timing configuration (SMTC), subcarrier spacing (SCS) and Absolute Radio-Frequency Channel Number (ARFCN). The PCI of addedSSB_Id can be different from the PCI used for the serving cell. The ARFCN tells where the SSB is located in frequency.

In another embodiment, if SCS is not given, the UE may assume the SCS is the same as for the serving cell (both for SSB and PDSCH/PDCCH). In another embodiment, is SMTC is not given, the UE may assume the SMTC is the same as for the serving cell as given in ServingCellConfigCommon.

In one embodiment, the mTRP ID is associated to the added SSB(PCI).

Taking added SSB(PCI) into account in CSI is discussed below.

In one embodiment, the added SSB(PCI) may be taken into account in CSI. For example, in order to report L1-RSRP based on SSB of the added SSB(PCI), the added SSB(PCI) may be indicated to the UE in CSI-SSB-ResourceSet used in CSI-MeasConfig and in CSI-ReportConfig in some embodiments.

In some embodiments, the IE CSI-SSB-ResourceSet may be used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon. Alternatively, if "SSBPCI_mTRP" is configured, the SSB-Index refers to SS/PBCH in added SSB(PCI) given in ServingCellConfig as referred by "addedSSB_Id". The CSI-SSB-ResourceSet IE including addedSSB_Id is shown below in Table <NUM>.

The IE CSI-SSB-ResourceSet is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon. The CSI-SSB-ResourceSet information element is illustrated in Table <NUM> below.

By including "addedSSB_Id" in the CSI-SSB-ResourceSet IE, the UE can, for example, report CSI associated with the identified SSB(PCI).

Taking added SSB(PCI) into account in RadioLinkMonitoringConfig is discussed below.

In another embodiment, the added SSB(PCI) may be taken into account in RadioLinkMonitoringConfig for use in radio link monitoring by the UE. For example, in order to report L1-RSRP based on SSB of the added SSB(PCI), the added SSB(PCI) may be indicated to the UE in CSI-SSB-ResourceSet used in CSI-MeasConfig and in CSI-ReportConfig. The RadioLinkMonitoringConfig IE with "addedSSB_Id" included is shown below in Table <NUM>.

The IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also TS <NUM> (Reference [<NUM>]), clause <NUM>. The RadioLinkMonitoringConfig information element is illustrated in Table <NUM> below.

Table <NUM> below provides RadioLinkMonitoringConfig field descriptions for fields of the RadioLinkMonitoringConfig information element.

Table <NUM> below provides RadioLinkMonitoringRS field descriptions for fields of the RadioLinkMonitoringConfig information element.

By including "addedSSB_Id" in the RadioLinkMonitoringConfig, the UE can perform radio link monitoring on the added SSB(PCI).

Taking added SSB(PCI) into account in radio resource management (RRM) is discussed below.

In some embodiments, the added SSB(PCI) may be taken into account in radio resource management (RRM). For example, there may be a need for UE to take these added SSBs into account when measuring SSBs on a carrier.

In some embodiments, the UE may consider each SSB as a separate entity and derive cell quality for each SSB. In this case, in measurement object, these SSBs may be flagged as belonging to a TRP. In this case, when the UE reports, the UE may add the flag to the measurement result.

In another embodiment, the UE may be configured to combine the measurements from the two SSBs. Combining the measurements may include an average over the measurement quantity like RSRP or RSRQ, selection of the measurement quantity, reporting measurement quantity on both SSBs where second report may be relative to the first report.

Taking added SSB(PCI) into account UL power control is discussed below.

In other embodiments, the UE may take the added SSB(PCI) into account for UL power control. For example, in order to perform UL power control, the UE may be configured with a pathloss reference RS. In this case, the added SSB(PCI) may be indicated in the corresponding RRC configuration. An example of a PUCCH-PowerControl IE that takes the added SSB(PCI)) into account is shown below in Table <NUM>.

The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH. The PUCCH-PowerControl information element is illustrated in Table <NUM> below.

Table <NUM> below provides P0-PUCCH field descriptions for fields of the PUCCH-PowerControl information element.

Table <NUM> below provides PUCCH-PowerControl field descriptions for fields of the PUCCH-PowerControl information element.

The example above related to PUCCH power control, and similar extensions should be made for SRS power control (in the field pathlossReferenceRS inside the RRC IE SRS-ResourceSet) and PUSCH power control (in the RRC IE PUSCH-PathlossReferenceRS).

Taking added SSB(PCI) into account UL spatial relations is discussed below.

In some embodiments, the added SSB(PCI) may be taken into account for UL spatial relations. For example, the UE can be configured to use a spatial relation to an RS in another cell. This means that the added SSB(PCI) may be indicated in the corresponding RRC configuration. The PUCCH-SpatialRelationInfo IE with "addedSSB_Id" is shown the table below.

The IE PUCCH-SpatialRelationInfo is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see TS <NUM>, (Reference [<NUM>]), clause <NUM>. The PUCCH-SpatialRelationInfo Information Element is illustrated in Table <NUM> below.

Table <NUM> below provides PUCCH-SpatialRelationInfo field descriptions for fields of the PUCCH-SpatialRelationInfo Information Element.

The spatial relation must be updated also for SRS, in the RRC IE SRS-SpatialRelationInfo.

Taking added SSB(PCI) into account determining MAC CE format is discussed below.

In some embodiments, the added SSB(PCI) may be taken into account for determining a MAC CE format. Adding SSB(PCI) to MAC CEs will create double the number of MAC CEs. Since each MAC CE requires an LCID, this may be an expensive solution. It may be better to reuse the existing LCID. Accordingly, some embodiments introduce an additional format for each MAC CE which includes the SSB(PCI) field. When the UE determines the format of the MAC CE, it will perform the following operations:.

In one embodiment this parameter is the SSB(PCI) parameter and the presence of the parameter indicates that the UE determines the MAC CE format to be a format which includes the SSB(PCI) field.

In one embodiment this parameter is the SSB(PCI) parameter and the presence of the parameter indicates that the UE determines the MAC CE format to be a format different from existing formats not taking into account SSB(PCI).

In another embodiment the UE can use the SSB(PCI) configured over RRC to determine the MAC CE format. If the UE is configured with the SSB(PCI) it determines the MAC CE format to be a MAC CE format which includes an SSB(PCI) field. If the UE is not configured with the SSB(PCI) field it determines the MAC CE format to be a MAC CE format without the SSB(PCI) field.

In yet another embodiment, instead of explicit SSB(PCI) field, there is another SSB(PCI) related way of interpreting the MAC CE.

<FIG> is a block diagram illustrating elements of a network node <NUM> of a communication system. The network node <NUM> may implement a RAN node in the communication system. For example, the network node <NUM> may implement a gNodeB or eNodeB.

As shown, the network node may include a network interface circuit <NUM> (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations, RAN nodes and/or core network nodes) of the communication network. The network node <NUM> may also include a wireless transceiver circuit <NUM> for providing a wireless communication interface with UEs. The network node <NUM> may also include a processor circuit <NUM> (also referred to as a processor) coupled to the transceiver circuit <NUM> and the network interface <NUM>, and a memory circuit <NUM> (also referred to as memory) coupled to the processor circuit. The memory circuit <NUM> may include computer readable program code that when executed by the processor circuit <NUM> causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit <NUM> may be defined to include memory so that a separate memory circuit is not required.

As discussed herein, operations of the network node may be performed by processor <NUM>, the wireless transceiver circuit <NUM> and/or the network interface <NUM>. For example, the processor <NUM> may control the network interface <NUM> to transmit communications through network interface <NUM> to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory <NUM>, and these modules may provide instructions so that when instructions of a module are executed by processor <NUM>, processor <NUM> performs respective operations (e.g., operations discussed herein with respect to Example Embodiments).

<FIG> is a block diagram illustrating elements of a UE <NUM> of a communication system. As shown, the UE may include a wireless transceiver circuit <NUM> for providing a wireless communication interface with a network. The UE <NUM> may also include a processor circuit <NUM> (also referred to as a processor) coupled to the transceiver circuit <NUM> and the wireless transceiver circuit <NUM>, and a memory circuit <NUM> (also referred to as memory) coupled to the processor circuit. The memory circuit <NUM> may include computer readable program code that when executed by the processor circuit <NUM> causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit <NUM> may be defined to include memory so that a separate memory circuit is not required.

As discussed herein, operations of the UE may be performed by processor <NUM> and/or the wireless transceiver circuit <NUM>. For example, the processor <NUM> may control the wireless transceiver circuit <NUM> to transmit communications to a network node <NUM>. Moreover, modules may be stored in memory <NUM>, and these modules may provide instructions so that when instructions of a module are executed by processor <NUM>, processor <NUM> performs respective operations (e.g., operations discussed herein with respect to Example Embodiments).

Referring to <FIG>, a method of operating a network node includes providing (<NUM>) a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and transmitting (<NUM>) a control message including the first IE to a user equipment, UE, to enable the UE to perform a radio link monitoring function on the radio link.

The first information element may be a serving cell configuration IE. The control message may include a radio resource control, RRC, message. The RRC message may include an RRCReconfiguration message.

The added SSB/PCI may be associated with a transmit/receive point, TRP, other than a serving cell.

The added SSB/PCI may include one or more of an identifier of the added SSB/PCI, a physical cell identity, an SSB measurement timing configuration, SMTC, a subcarrier spacing, SCS, and an Absolute Radio-Frequency Channel Number, ARFCN.

The added SSB/PCI may identify a PCI that is different from a PCI used for a serving cell.

The method may further include including the added SSB/PCI in a second IE relating to channel state information, CSI; and including the second IE in the message to enable the UE to perform CSI measurements on the radio link. The second IE may include a CSI-MeasConfig IE. The second IE may include a CSI-SSB-ResourceSet IE.

The method may further include including the added SSB/PCI in a third IE relating to radio link monitoring; and including the third IE in the message to enable the UE to perform radio link monitoring on the radio link. The third IE may include a RadioLinkMonitoringConfig IE.

The method may further include including the added SSB/PCI in a fourth IE relating to uplink power control; and including the fourth IE in the message to enable the UE to perform uplink power control on the radio link. The fourth IE may include a PUCCH-PowerControl IE.

The method may further include including the added SSB/PCI in a fifth IE relating to uplink spatial relations; and including the fifth IE in the message to enable the UE to configure spatial relations on the radio link. The fifth IE may include a PUCCH-SpatialRelationInfo IE.

The method may further include including the added SSB/PCI in a medium access control, MAC, control element, CE; and including the MAC CE in the message to enable the UE to determine a MAC CE format of the radio link. The MAC CE may include an SSB/PCI field.

Referring to <FIG> and <FIG>, a network node (<NUM>) according to some embodiments is configured to perform operations of providing (<NUM>) a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and transmitting (<NUM>) a control message including the first IE to a user equipment, UE, to enable the UE to perform a radio link monitoring function on the radio link.

Referring to <FIG> and <FIG>, a network node (<NUM>) according to some embodiments includes a processing circuit (<NUM>), a transceiver (<NUM>) coupled to the processing circuit, and a memory (<NUM>) coupled to the processing circuit. The memory includes computer-readable program instructions that, when executed by the processing circuit, cause the processing circuit to perform operations of providing (<NUM>) a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and transmitting (<NUM>) a control message including the first IE to a user equipment, UE, to enable the UE to perform a radio link monitoring function on the radio link.

Referring to <FIG>, a method of operating a user equipment includes receiving (<NUM>) a control message from a network node, the message including a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and performing (<NUM>) a radio link monitoring function on the radio link based on the added SSB/PCI.

The method may further include receiving a second IE in the control message relating to channel state information, CSI, the second IE identifying the added SSB/PCI; and performing a CSI measurement on the radio link based on the added SSB/PCI. The second IE may include a CSI-MeasConfig IE. The second IE may include a CSI-SSB-ResourceSet IE.

The method may further include receiving a third IE relating to radio link monitoring, the third IE identifying the added SSB/PCI; and performing radio link monitoring on the radio link based on the added SSB/PCI. The third IE may include a RadioLinkMonitoringConfig IE.

The method may further include receiving a fourth IE relating to uplink power control, the fourth IE identifying the added SSB/PCI; and performing uplink power control on the radio link based on the added SSB/PCI. The fourth IE may include a PUCCH-PowerControl IE.

The method may further include receiving a fifth IE relating to uplink spatial relations, the fifth IE identifying the added SSB/PCI; and configuring spatial relations on the radio link based on the added SSB/PCI. The fifth IE may include a PUCCH-SpatialRelationInfo IE.

The method may further include receiving a medium access control, MAC, control element, CE, the MAC CE identifying the added SSB/PCI; and determining a MAC CE format based on the added SSB/PCI. The MAC CE may include an SSB/PCI field.

Referring to <FIG> and <FIG>, a UE (<NUM>) according to some embodiments is configured to perform operations of receiving (<NUM>) a control message from a network node, the message including a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and performing (<NUM>) a radio link monitoring function on the radio link based on the added SSB/PCI.

Referring to <FIG> and <FIG>, a UE (<NUM>) according to some embodiments includes a processing circuit (<NUM>), a transceiver (<NUM>) coupled to the processing circuit, and a memory (<NUM>) coupled to the processing circuit. The memory includes computer-readable program instructions that, when executed by the processing circuit, cause the processing circuit to perform operations of receiving (<NUM>) a control message from a network node, the message including a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link; and performing (<NUM>) a radio link monitoring function on the radio link based on the added SSB/PCI.

Operations of a network node <NUM> (implemented using the structure of <FIG>, which may be implemented as a RAN node) will now be discussed with reference to the flow chart of <FIG> according to some embodiments of inventive concepts. For example, modules may be stored in memory <NUM> of <FIG>, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry <NUM>, processing circuitry <NUM> performs respective operations of the flow chart.

According to some embodiments at block <NUM>, processing circuit <NUM> provides a first information element IE including an indication of an added synchronization signal block/physical cell identity SSB/PCI wherein the indication of the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link. According to some embodiments, the first information element may be a serving cell configuration IE. According to some embodiments, the indication of the added SSB/PCI may include one or more of an identifier of the added SSB/PCI, a physical cell identity PCI, an SSB measurement timing configuration SMTC, a subcarrier spacing SCS, and an Absolute Radio-Frequency Channel Number ARFCN. For example, the indication of the added SSB/PCI may identify a PCI that is different from a PCI used for a serving cell.

According to some embodiments at block <NUM>, processing circuit <NUM> provides a second IE including the indication of the added SSB/PCI, wherein the second IE relates to uplink power control.

According to some embodiments at block <NUM>, processing circuit <NUM> transmits (through transceiver circuit <NUM>) a control message including the first IE and the second IE to a user equipment UE to enable the UE to perform a radio link monitoring function on the radio link. The second IE is included in the control message to enable the UE to perform uplink power control on the radio link.

According to some embodiments, the second IE may relate to channel state information CSI, and the second IE may be included in the control message to enable the UE to perform CSI measurements on the radio link. For example, the second IE may be a CSI-MeasConfig IE, or the second IE may be a CSI-SSB-ResourceSet IE.

According to some embodiments, the second IE may relate to radio link monitoring, and the second IE may be included in the control message to enable the UE to perform radio link monitoring on the radio link. For example, the second IE may be a RadioLinkMonitoringConfig IE.

The second IE relates to uplink power control, and the second IE is included in the control message to enable the UE to perform uplink power control on the radio link. For example, the second IE may be a PUCCH-PowerControl IE.

According to some embodiments, the second IE may relate to uplink spatial relations, and the second IE may be included in the control message to enable the UE to configure spatial relations on the radio link. For example, the second IE may be a PUCCH-SpatialRelationInfo IE.

Various operations from the flow chart of <FIG> may be optional with respect to some embodiments of network nodes and related methods.

Operations of a network node <NUM> (implemented using the structure of <FIG>, which may be implemented as a RAN node) will now be discussed with reference to the flow chart of <FIG> according to some embodiments of inventive concepts. For example, modules may be stored in memory <NUM> of <FIG>, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry <NUM>, processing circuitry <NUM> performs respective operations of the flow chart.

According to some embodiments at block <NUM>, processing circuit <NUM> provides a media access control MAC control element CE including the indication of the added SSB/PCI. In such embodiments, the MAC CE may be included in a MAC control message to enable the UE to determine a MAC CE format of the radio link.

Various operations from the flow chart of <FIG> may be optional with respect to some embodiments of network nodes and related methods. Regarding methods of example embodiment <NUM> (set forth below), for example, operations of block <NUM> of <FIG> may be optional.

Operations of the communication device UE <NUM> (implemented using the structure of the block diagram of <FIG>) will now be discussed with reference to the flow charts of <FIG> according to some embodiments of inventive concepts. For example, modules may be stored in memory <NUM> of <FIG>, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry <NUM>, processing circuitry <NUM> performs respective operations of the flow chart.

According to some embodiments at block <NUM>, processor circuit <NUM> receives (through transceiver circuit <NUM>) a control message from a network node. The control message includes a first information element IE including an indication of an added synchronization signal block/physical cell identity SSB/PCI, and the control message includes a second IE including the indication of the added SSB/PCI. The indication of the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link, and the second IE relates to uplink power control.

According to some embodiments, the first information element may be a serving cell configuration IE.

According to some embodiments, the indication of the added SSB/PCI includes one or more of an identifier of the added SSB/PCI, a physical cell identity, an SSB measurement timing configuration, SMTC, a subcarrier spacing, SCS, and an Absolute Radio-Frequency Channel Number, ARFCN. For example, the indication of the added SSB/PCI may identify a PCI that is different from a PCI used for a serving cell.

According to some embodiments at block <NUM>, processor circuit <NUM> performs a radio link monitoring function on the radio link based on the indication of the added SSB/PCI.

According to some embodiments at block <NUM>, processor circuit <NUM> manages the radio link based on the added SSB/PCI. Operations of block <NUM> may be performed, for example, as discussed below with respect to operation <NUM>-<NUM> of <FIG>, operation <NUM>-<NUM> of <FIG>, operation <NUM>-<NUM> of <FIG>, and/or operation <NUM>-<NUM> of <FIG>.

According to some embodiment, the second IE in the control message relates to channel state information CSI. In such embodiments at block <NUM>-<NUM> of <FIG>, processor circuit <NUM> may perform a CSI measurement on the radio link based on the indication of the added SSB/PCI. For example, the second IE may be a CSI-MeasConfig IE, and/or the second IE may be a CSI-SSB-ResourceSet IE.

According to some embodiments, the second IE may relate to radio link monitoring. In such embodiments at block <NUM>-<NUM> of <FIG>, processor circuit <NUM> may perform radio link monitoring on the radio link based on the indication of the added SSB/PCI. For example, the second IE may be a RadioLinkMonitoringConfig IE.

The second IE relates to uplink power control. At block <NUM>-<NUM> of <FIG>, processor circuit <NUM> performs uplink power control on the radio link based on the indication of the added SSB/PCI. For example, the second IE may be a PUCCH-PowerControl IE.

According to some embodiments, the second IE may relate to uplink spatial relations. In such embodiments at block <NUM>-<NUM> of <FIG>, processor circuit <NUM> may configure spatial relations on the radio link based on the indication of the added SSB/PCI. For example, the second IE may be a PUCCH-SpatialRelationInfo IE.

Various operations from the flow charts of <FIG> may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment <NUM> (set forth below), for example, operations of blocks <NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and/or <NUM>-<NUM> of <FIG>, and/or 8E may be optional.

According to some embodiments, the second IE may relate to uplink spatial relations. In such embodiments at block <NUM>-<NUM>, of <FIG> processor circuit <NUM> may configure spatial relations on the radio link based on the indication of the added SSB/PCI. For example, the second IE may be a PUCCH-SpatialRelationInfo IE.

According to some embodiments at block <NUM>, processor circuit <NUM> receives (through transceiver circuit <NUM>) a MAC control message including a medium access control MAC control element CE, with the MAC CE including the indication of the added SSB/PCI.

Various operations from the flow charts of <FIG> may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment <NUM> (set forth below), for example, operations of blocks <NUM>, <NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and/or <NUM>-<NUM> of <FIG>, and/or 9E may be optional.

Explanations are provided below for abbreviations that are mentioned in the present disclosure.

Citations are provided below for references that are mentioned in the present disclosure.

Additional explanation is provided below.

<FIG>: A wireless network in accordance with some embodiments.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

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

Network node QQ160 and WD QQ110 comprise various components described in more detail below.

Yet further examples of network nodes include multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

In <FIG>, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of <FIG> may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

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

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

Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

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

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

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

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, <NUM> and <NUM>. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187.

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

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

As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.

Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

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

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

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

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

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

Claim 1:
A method of operating a network node, comprising:
providing (<NUM>, <NUM>) a first information element, IE, including an indication of an added synchronization signal block/physical cell identity, SSB/PCI, wherein the indication of the added SSB/PCI indicates an SSB and associated PCI that are associated with a radio link;
providing (<NUM>, <NUM>) a second IE including the indication of the added SSB/PCI, wherein the second IE relates to uplink power control; and
transmitting (<NUM>, <NUM>) a control message including the first IE and the second IE to a user equipment, UE, to enable the UE to perform radio link monitoring function and uplink power control on the radio link based on the added SSB/PCI.