Patent Description:
Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for communication link selection for non-reference signal received power (RSRP) based association in wireless industrial internet-of-things.

A wireless network may include a number of base stations (BSs) that can support communication for a number of user equipments (UEs).

As the demand for mobile broadband access continues to increase, further improvements in LTE,NR, and other radio access technologies remain useful.

Patent application <CIT> relates to a system including a plurality of wireless sensors that detect threats within a secured geographic area, a control panel that monitors the plurality of sensors for activation, a primary control unit that forms a primary wireless mesh network coupling the plurality of sensors with the control panel based upon relative link quality, where the primary mesh network is defined by a primary routing table and a redundant control unit that forms a secondary wireless mesh network coupling the plurality of sensors with the control panel based upon relative link quality, where the secondary mesh network including a parent or child.

<FIG> is a diagram illustrating an example of a wireless network <NUM> in accordance with various aspects of the present disclosure.

In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network <NUM> through various types of backhaul interfaces such as a direct physical connection or a virtual network, using any suitable transport network.

Wireless network <NUM> may be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, and/or the like.

<FIG> shows a diagram illustrating an example <NUM> of a base station <NUM> in communication with a UE <NUM> in a wireless network <NUM>, in accordance with various aspects of the present disclosure.

At base station <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the network node, and provide data symbols for all network nodes. Transmit processor <NUM> may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) and/or a secondary synchronization signal (SSS)).

A channel processor may determine reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ), a channel quality indicator (CQI), and/or the like.

On the uplink, at UE <NUM>, a transmit processor <NUM> may receive and process data from a data source <NUM> and control information (e.g., for reports that include RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor <NUM>.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with communication link selection for non-reference signal received power (RSRP) based association in wireless industrial internet-of-things (IIoT), as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, another UE, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, interpreting, and/or the like) by one or more processors of the base station <NUM> and/or the UE <NUM>, may cause the one or more processors, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, interpreting the instructions, and/or the like.

In some aspects, network node <NUM> may include means for receiving an indication of a first set of parameters that corresponds to a direct communication link between an IIoT device and a first controller, means for receiving an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device and the first controller through a second controller, means for scheduling a communication on at least one of the direct communication link or the indirect communication link based at least in part on the first set of parameters and the second set of parameters, and/or the like. In some aspects, such means may include one or more components of network node <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

<FIG> is a diagram illustrating an example <NUM> of sidelink communications, in accordance with various aspects of the present disclosure.

As shown in <FIG>, a first UE <NUM>-<NUM> may communicate with a second UE <NUM>-<NUM> (and one or more other UEs <NUM>) via one or more sidelink channels <NUM>. The UEs <NUM>-<NUM> and <NUM>-<NUM> may communicate using the one or more sidelink channels <NUM> for P2P communications, D2D communications, V2X communications (e.g., which may include V2V communications, V2I communications, V2P communications, and/or the like), mesh networking, and/or the like. In some aspects, the UEs <NUM> (e.g., UE <NUM>-<NUM> and/or UE <NUM>-<NUM>) may correspond to one or more other UEs described elsewhere herein, such as UE <NUM>. In some aspects, the one or more sidelink channels <NUM> may use a PC5 interface and/or may operate in a high frequency band (e.g., the <NUM> band). Additionally, or alternatively, the UEs <NUM> may synchronize timing of transmission time intervals (TTIs) (e.g., frames, subframes, slots, symbols, and/or the like) using global navigation satellite system (GNSS) timing.

As further shown in <FIG>, the one or more sidelink channels <NUM> may include a physical sidelink control channel (PSCCH) <NUM>, a physical sidelink shared channel (PSSCH) <NUM>, and/or a physical sidelink feedback channel (PSFCH) <NUM>. The PSCCH <NUM> may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and/or a physical uplink control channel (PUCCH) used for cellular communications with a base station <NUM> via an access link or an access channel. The PSSCH <NUM> may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and/or a physical uplink shared channel (PUSCH) used for cellular communications with a base station <NUM> via an access link or an access channel. For example, the PSCCH <NUM> may carry sidelink control information (SCI) <NUM>, which may indicate various control information used for sidelink communications, such as one or more resources (e.g., time resources, frequency resources, spatial resources, and/or the like) where a transport block (TB) <NUM> may be carried on the PSSCH <NUM>. The TB <NUM> may include data. The PSFCH <NUM> may be used to communicate sidelink feedback <NUM>, such as hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK/NACK) information), transmit power control (TPC), a scheduling request (SR), and/or the like.

In some aspects, the one or more sidelink channels <NUM> may use resource pools. For example, a scheduling assignment (e.g., included in SCI <NUM>) may be transmitted in subchannels using specific resource blocks (RBs) across time. In some aspects, data transmissions (e.g., on the PSSCH <NUM>) associated with a scheduling assignment may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, a scheduling assignment and associated data transmissions are not transmitted on adjacent RBs.

In some aspects, a UE <NUM> may operate using a transmission mode where resource selection and/or scheduling is performed by the UE <NUM> (e.g., rather than a base station <NUM>). In some aspects, the UE <NUM> may perform resource selection and/or scheduling by sensing channel availability for transmissions. For example, the UE <NUM> may measure a received signal strength indicator (RSSI) parameter (e.g., a sidelink-RSSI (S-RSSI) parameter) associated with various sidelink channels, may measure a reference signal received power (RSRP) parameter (e.g., a PSSCH-RSRP parameter) associated with various sidelink channels, may measure a reference signal received quality (RSRQ) parameter (e.g., a PSSCH-RSRQ parameter) associated with various sidelink channels, and/or the like, and may select a channel for transmission of a sidelink communication based at least in part on the measurement(s).

Additionally, or alternatively, the UE <NUM> may perform resource selection and/or scheduling using SCI <NUM> received in the PSCCH <NUM>, which may indicate occupied resources, channel parameters, and/or the like. Additionally, or alternatively, the UE <NUM> may perform resource selection and/or scheduling by determining a channel busy rate (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE <NUM> can use for a particular set of subframes).

In the transmission mode where resource selection and/or scheduling is performed by a UE <NUM>, the UE <NUM> may generate sidelink grants, and may transmit the grants in SCI <NUM>. A sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks to be used for the upcoming sidelink transmission on the PSSCH <NUM> (e.g., for TBs <NUM>), one or more subframes to be used for the upcoming sidelink transmission, a modulation and coding scheme (MCS) to be used for the upcoming sidelink transmission, and/or the like. In some aspects, a UE <NUM> may generate a sidelink grant that indicates one or more parameters for semi-persistent scheduling (SPS), such as a periodicity of a sidelink transmission. Additionally, or alternatively, the UE <NUM> may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

<FIG> is a diagram illustrating an example <NUM> of sidelink communications and access link communications, in accordance with various aspects of the present disclosure.

As shown in <FIG>, a transmitter (Tx) UE <NUM> and a receiver (Rx) UE <NUM> may communicate with one another via a sidelink, as described above in connection with <FIG>. As further shown, in some sidelink modes, a base station <NUM> may communicate with the Tx UE <NUM> via a first access link. Additionally, or alternatively, in some sidelink modes, the base station <NUM> may communicate with the Rx UE <NUM> via a second access link. The Tx UE <NUM> and/or the Rx UE <NUM> may correspond to one or more UEs described elsewhere herein, such as the UE <NUM> of <FIG>. Thus, "sidelink" may refer to a direct link between UEs <NUM>, and "access link" may refer to a direct link between a base station <NUM> and a UE <NUM>. Sidelink communications may be transmitted via the sidelink, and access link communications may be transmitted via the access link. An access link communication may be either a downlink communication (from a base station <NUM> to a UE <NUM>) or an uplink communication (from a UE <NUM> to a base station <NUM>).

IIoT is a branch of cellular technology in which UEs and BSs may be used to carry control data, measurement data, and/or the like between various industrial systems. For example, IIoT may be used to control IIoT devices such as sensors and/or actuators, to exchange measurement information between other IIoT devices such as programmable logic controllers (PLCs) of a factory floor (for example, in a factory automation application), and/or the like. According to various aspects, IIoT devices discussed herein (e.g., sensors, actuators, PLCs, and/or the like) may be, include, or be included in, UEs such as UE <NUM> discussed above in connection with <FIG>. In some aspects, an IIoT device may function as a small cell (e.g., a pico cell), in which case the IIoT device may be, include, or be included in, a BS such as BS <NUM> discussed above in connection with <FIG>.

<FIG> is a diagram illustrating an example of an IIoT communications network <NUM>, in accordance with various aspects of the present disclosure.

As shown, the network <NUM> includes a PLC <NUM> (which is, itself, a type of IIoT device) that exchanges wireless communication <NUM> with IIoT devices <NUM> (shown as 506A, 506B, and 506C). The IIoT devices <NUM> may include sensors 506C, actuators 506A and 506B, and/or the like. In some aspects, the IIoT devices <NUM> may be associated with equipment <NUM> (shown as 508A and 508B). The network <NUM> may include a base station <NUM> that exchanges communication <NUM> with the PLC <NUM> and/or communication <NUM> with one or more of the other IIoT devices <NUM>.

The communication between the PLC <NUM> and IIoT devices <NUM> may include cyclic exchanges of information. The PLC <NUM> may provide commands in wireless signals to factory equipment <NUM>. Sensors 506C and actuators 506A, 506B may be separate from the factory equipment <NUM> and/or may be comprised in or positioned at a piece of factory equipment <NUM>. The PLC <NUM> may automate control of machines and control systems, e.g., of industrial electromechanical processes, such as control of machinery on factory assembly lines, amusement rides, light fixtures, etc. An IIoT network <NUM> may include any number of PLCs <NUM>, sensors 506C, actuators 506A, 506B, and/or the like.

<FIG> is a diagram illustrating an example <NUM> of IIoT communications, in accordance with various aspects of the present disclosure.

As shown, a PLC <NUM> and an IIoT device <NUM> may exchange periodic or cyclic traffic. The PLC <NUM> may transmit communication <NUM> such as a command or other communication to the IIoT device <NUM> during a period of time TD-DL, <NUM>. The communication <NUM> from the PLC <NUM> to the IIoT device <NUM> may be referred to as downlink communication. The IIoT device <NUM> may receive the communication <NUM>, and may take an action based on the command. Following the action, the IIoT device <NUM> may transmit communication <NUM> back to the PLC <NUM> during period of time TD-UL, <NUM>. There may be a processing time duration <NUM> (TAP) between receipt of the communication <NUM> from the PLC <NUM> and transmission of the communication <NUM> from the IIoT device <NUM>. During the processing time, the IIoT device <NUM> may be sensing, actuating, and/or the like.

In some aspects, the communication <NUM> may include sensed data from a sensor, a confirmation of actuation from an actuator, and/or the like. The communication <NUM> may include an application layer acknowledgement. The communication <NUM> that is transmitted from the IIoT device <NUM> to the PLC <NUM> may be referred to as uplink communication. Following the PLC's receipt of the communication <NUM> from the IIoT device <NUM>, there may be a processing duration <NUM> (TAP) during which the PLC <NUM> may process the received information and before the PLC <NUM> sends additional communication/commands to the IIoT device <NUM>. The combined cycle may have a duration <NUM> of length Tcycle. Following the duration <NUM> TAP, the cycle may repeat with the PLC <NUM> sending additional communication <NUM> to the IIoT device <NUM>.

The communication network may accommodate periodic, regular traffic between PLCs <NUM> and IIoT devices <NUM>. The communication between the PLC <NUM> and the IIoT device <NUM> may be associated with a low latency and high reliability. For example, the communication may be based on a latency of less than <NUM> or less than <NUM>. The communication may have a reliability requirement on the order of <NUM>-<NUM> or <NUM>-<NUM>, such as <NUM>% reliability. The latency and reliability may apply to data and control channels.

In some aspects, a PLC <NUM> may use a control channel, such as a physical downlink control channel (PDCCH), to grant resources to IIoT device <NUM> for use in transmitting the periodic uplink communication <NUM>. Factory automation may involve a high IIoT device <NUM> density (e.g., approximately <NUM> UE per m<NUM>). Therefore, a large number of IIoT devices <NUM> may communicate with the PLC <NUM>. Sending a dynamic grant (e.g., one downlink control information (DCI) per slot) to each of the large number of IIoT devices <NUM> may place a burden on PDCCH overhead. Semi-persistent scheduling (SPS) may be used to reduce the overhead requirements of PDCCH by enabling the IIoT devices <NUM> to be granted resources in a semi-persistent or periodic manner. SPS may also be used to schedule resources for receiving downlink communication. The SPS may be communicated to each IIoT device <NUM> using radio resource control (RRC) signaling and/or DCI. In some aspects, SPS may be used for a first transmission, and PDCCH may be used to schedule a possible retransmission if the first transmission is not accurately received.

<FIG> is a diagram illustrating an example <NUM> of IIoT communications, in accordance with various aspects of the present disclosure. As shown in <FIG>, IIoT communications may include downlink transmissions from a PLC to a sensor and/or actuator <NUM> (shown as "S/A <NUM>"), a sensor and/or actuator <NUM> (shown as "S/A <NUM>"), and so forth until the downlink transmission for a sensor and/or actuator N (shown as "S/A N") in a slot <NUM> based on SPS. Acknowledgement/negative acknowledgement (ACK/NACK) feedback may be received from each of the sensors/actuators. Based on the feedback, the PLC may transmit PDCCH to schedule resources for a retransmission of the information to the sensors/actuators from which a NACK is received or from which an ACK is not received. For uplink communication, the PLC may receive uplink transmissions from sensor/actuator <NUM> (S/A <NUM>), sensor/actuator <NUM> (S/A <NUM>),. , sensor/actuator N (S/A N) in a slot <NUM> based on SPS. The PLC may provide ACK/NACK feedback to each of the sensor/actuators. The PLC may transmit PDCCH to the sensors/actuators scheduling a retransmission for information that was not correctly received by the PLC.

<FIG> is a diagram illustrating examples <NUM> of IIoT communications, in accordance with various aspects of the present disclosure.

As shown by reference number <NUM>, a first PLC (shown as "PLC <NUM>") may be configured to communicate with a first IIoT device (shown as "s1") and a second IIoT device (shown as "s3"). The PLC <NUM> may be associated with s1 and s3, which means the PLC <NUM> may control s1 and/or s3, be configured to receive and/or process data from s1 and/or s3, and/or the like. In some aspects, the association between the PLC <NUM> and s1 and s3 may be established by an industrial application that controls factory operations at the application layer. Similarly, as shown, a second PLC (shown as "PLC <NUM>") may be associated with a third IIoT device (shown as "s2") and a fourth IIoT device (shown as "s4"). In some aspects, the association between the PLC <NUM> and s2 and s4 may be established by the industrial application. The communication links between the PLCs and the IIoT devices may be based on a PC5 interface, which may be used to implement sidelink communication.

A base station (BS) (e.g., a gNB, and/or the like) may communicate with PLC <NUM> and/or PLC <NUM>. In some aspects, PLCs <NUM> and <NUM> may be located close to machinery, whereas the BS may be ceiling mounted or at a greater distance from the equipment. The communication links between the BS and the PLCs may be based on an uplink/downlink (Uu) interface, which also may be referred to as an access link. In some aspects, a PLC may function as a small cell and one or more IIoT devices may communicate with the PLC based on an Uu interface (access link).

In some aspects, one or more of the PLCs may use the BS for inter-PLC coordination with other PLCs. Additionally, or alternatively, the PLCs may communicate over direct communication links with one another. Direct communication between PLC <NUM> and PLC <NUM> may be based on sidelink communications, which may utilize, in some aspects, the PC5 interface. In some aspects, one or more of the PLCs may use the BS for a backhaul to a human machine interface (HMI). In some aspects, one or more of the PLCs may use the BS as a system controller. The BS may perform interference management (IM) across multiple PLCs. The BS may handle other network functions for the IIoT devices, such as initial access with the network, mobility, and/or the like.

As indicated above, an application may determine association between a PLC and an IIoT device. In some aspects, this association may be determined based on industrial functions and processes, and not based on communication link quality such as RSRP between the PLC and its associated IIoT device. As shown, for example, PLC <NUM> may be associated with s3, even though it is farther away from s3 than PLC <NUM>. Similarly, PLC <NUM> may be associated with s2, even though it is farther away from s2 than PLC <NUM>. The direct communication link between PLC <NUM> and s3 and the direct communication link between PLC <NUM> and s2 may be weak, subject to cross-link interference, and/or the like.

As shown by reference number <NUM>, to mitigate some of the issues regarding the direct communication links between PLCs and associated IIoTs, the BS may communicate with one or more of the IIoT devices s1, s2, s3, and/or s4. The links between the BS and the IIoT devices may be based on a Uu interface. The transmission of control by the BS may help to improve reliability. Such control by the BS may involve two hops in order to provide the control to the IIoT - a first hop from a PLC to the base station and a second hop from the base station to the associated IIoT device. In some examples, a portion of scheduling for the IIoT devices may be provided by the BS, and another portion of the scheduling may be provided by the PLC <NUM> and/or PLC <NUM>. Providing some control directly from the PLC may help to reduce over-the-air signaling and may improve latency. However, transmissions from the PLC may be blocked for a particular IIoT device. Blocks of links between PLCs and various IIoTs may last for different amounts of time. Moreover, using the BS for two-hop communications may be inefficient as more latency may be introduced.

Various aspects of the techniques and apparatus disclosed herein may enable communication link selection between direct communication links and two-hop communication links for non-RSRP based association in wireless IIoT environments. The two-hop communication links may include a first hop between an IIoT device and a first controller and a second hop between the first controller and a second controller. In this manner, two-hop communications may be utilized without utilizing the BS. In some aspects, the direct or indirect communication link with characteristics that satisfy one or more thresholds may be selected. The characteristics may be evaluated using parameters that relate to reliability, latency, signal quality, and/or the like.

In the invention, a network node (e.g., a PLC, an IIoT device, and/or the like) acts as a scheduling device and receives an indication of parameters that correspond to direct communication link between an IIoT device and a first controller (e.g., a PLC and/or the like) and an indication of parameters that correspond to an indirect communication link between the IIoT device and the first controller, where the indirect communication link involves a second controller. The scheduling device schedules communication on the direct and/or indirect communication link based at least in part on the parameters. In this way, aspects of the techniques disclosed herein may enable improved network capacity with load balancing across PLCs based on a two-hop metric that corresponds to the parameters. In some aspects, techniques described herein may facilitate multi-path diversity, in which a transmission and its retransmission are forwarded over different communication links. In some aspects, utilizing controllers for multiple hop communications may reduce the need for BS capacity.

<FIG> is a diagram illustrating an example <NUM> of communication link selection for non-RSRP based association in wireless industrial internet-of-things, in accordance with various aspects of the present disclosure.

As shown in <FIG>, the IIoT device s3 may be the scheduling network node, in which case, a direct communication link <NUM> between s3 and PLC <NUM> and/or a direct communication link <NUM> between s3 and PLC <NUM>, may be based on Mode <NUM> sidelink. Similarly, a direct communication link <NUM> between PLC <NUM> and PLC <NUM> may be based on Mode <NUM> sidelink. In some aspects, as discussed below in connection with <FIG>, the scheduling network node may be the BS for Uu (access link) based communications, Mode <NUM> sidelink communications, and/or the like. In some aspects, the scheduling network node may include the PLC <NUM> and/or PLC <NUM> for small cell Uu communications, Mode <NUM> sidelink communications with UE-UE scheduling, Mode <NUM> sidelink communications, and/or the like.

As shown by reference number <NUM>, the network node s3 receives an indication of a first set of parameters that corresponds to a direct communication link <NUM> between an IIoT device and a first controller (shown as PLC <NUM>). In the illustrated aspects, in which the scheduling network node includes the IIoT device, at least a portion of the indication of the first set of parameters may be received by the IIoT device s3 itself (e.g., by determining one or more of the first set of parameters, and/or the like). As shown, in some aspects, at least a portion of the indication of the first set of parameters may be received from the first controller PLC <NUM>.

In some aspects, the first set of parameters may indicate a communication link quality associated with the direct communication link between the IIoT device s3 and the first controller PLC <NUM>, a load associated with the first controller PLC <NUM>, a resource requirement associated with the direct communication link <NUM> between the IIoT device s3 and the first controller PLC <NUM>, and/or the like. In some aspects, receiving the indication of the first set of parameters may include receiving a unicast message from the first controller PLC <NUM>, receiving a multicast message from the first controller PLC <NUM>, receiving a broadcast message from the first controller PLC <NUM>, and/or the like.

In some aspects, for example, the IIoT device s3 may receive a parameter indicating the link quality associated with the direct communication link <NUM> by determining the link quality. In some aspects, the IIoT device s3 may determine the link quality based on a reference signal received from the first controller PLC <NUM>. The link quality may include any number of different measurements of communication quality such as, for example, a reference signal received power (RSRP), a reference signal received quality (RSRQ), a signal noise ratio (SNR), a signal to interference and noise ration (SINR), and/or the like.

In some aspects, the first controller PLC <NUM> may transmit an indication of a parameter indicating the load associated with the PLC <NUM>. "Load" may refer to a communication and/or processing load associated with communicating with one or more devices. The one or more devices may include the IIoT device s3, another IIoT device (s1, s2, s4, and/or the like), another controller (e.g., PLC <NUM>, and/or the like), and/or the like. In some aspects, an indication of a parameter indicating resource requirements associated with the communication link <NUM> may be received from the first controller PLC <NUM> and/or the IIoT device s3.

As shown by reference number <NUM>, the scheduling network node s3 receives an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device s3 and the first controller PLC <NUM> through a second controller PLC <NUM>. The indication of the second set of parameters is received from the first controller PLC <NUM> and/or the second controller PLC <NUM>. In some aspects, as shown in <FIG>, the second set of parameters may include at least one of a set of first hop parameters corresponding to the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM>, or a set of second hop parameters corresponding to the direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>.

In some aspects, the second set of parameters may indicate a link quality associated with the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM>, a load associated with the second controller PLC <NUM>, a resource requirement associated with the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM>, a link quality associated with the direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>, a load associated with the first controller PLC <NUM>, a resource requirement associated with the direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>, and/or the like.

In some aspects, receiving the indication of the second set of parameters may include receiving a unicast message from the first controller PLC <NUM>, receiving a unicast message from the second controller PLC <NUM>, receiving a multicast message from the first controller PLC <NUM>, receiving a multicast message from the second controller PLC <NUM>, receiving a broadcast message from the first controller PLC <NUM>, receiving a broadcast message from the second controller PLC <NUM>, or a combination thereof. In some aspects, the scheduling network node may be configured to periodically receive indications of at least one of the first set of parameters, the second set of parameters, or a combination thereof.

As shown by reference number <NUM>, the scheduling network node s3, schedules a communication on at least one of the direct communication link <NUM> between the IIoT device s3 and the first controller PLC <NUM> or on the indirect communication link based at least in part on the first set of parameters and the second set of parameters. In some aspects, scheduling the communication may include determining a direct communication link metric based on the first set of parameters; determining an indirect communication link metric based on the second set of parameters; comparing the direct communication link metric with the indirect communication link metric; and selecting at least one of the direct communication link or the indirect communication link based at least in part on comparing the direct communication link metric with the indirect communication link metric.

In some aspects, the direct communication link metric indicates an estimated latency associated with the direct communication link <NUM> between the IIoT device s3 and the first controller PLC <NUM>, an estimated reliability associated with the direct communication link between the IIoT device s3 and the first controller PLC <NUM>, and/or the like. In some aspects, the indirect communication link metric may indicate an estimated latency associated with the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM>, an estimated reliability associated with the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM>, an estimated latency associated with a direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>, an estimated reliability associated with the direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>, and/or the like.

In some aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link may include scheduling a primary transmission between the IIoT device s3 and the first controller PLC <NUM> and scheduling a retransmission between the IIoT device s3 and the first controller PLC <NUM>. In some aspects, scheduling the communication may include scheduling the primary transmission between the IIoT device s3 and the first controller PLC <NUM> by allocating a first set of resources corresponding to the direct communication link or the indirect communication link and scheduling the retransmission between the IIoT device s3 and the first controller PLC <NUM> by allocating a second set of resources corresponding to the direct communication link or the indirect communication link.

In some aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link may include allocating a set of resources corresponding to the direct communication link, the indirect communication link, or a combination thereof. In some aspects, the set of resources may include time resources, frequency resources, spatial resources, and/or the like. The set of resources may be associated with a semi-persistent scheduling (SPS) communication, a periodic scheduling communication, an aperiodic scheduling communication, and/or the like.

In some aspects, scheduling the communication may include scheduling the communication on the direct communication link by allocating a set of sidelink resources. In some aspects, the first controller PLC <NUM> may be configured as a small cell base station and scheduling the communication may include scheduling the communication on the direct communication link by allocating a set of access link resources.

In some aspects, scheduling the communication may include scheduling the communication on the indirect communication link by allocating a first set of resources corresponding to the direct communication link <NUM> between the IIoT device s3 and the second controller PLC <NUM> and allocating a second set of resources corresponding to the direct communication link <NUM> between the second controller PLC <NUM> and the first controller PLC <NUM>. In some aspects, the first set of resources may include a set of sidelink resources, a set of access link resources, and/or the like. In some aspects, the second set of resources may include a set of sidelink resources. In some aspects, the set of sidelink resources may include at least one of a Mode <NUM> sidelink resource or a Mode <NUM> sidelink resource. The set of sidelink resources may be associated with a PC5 interface and the set of access link resources may be associated with an uplink/downlink (Uu) interface.

As shown by reference number <NUM>, the scheduling network node s3 transmits an indication of a resource allocation (RA) corresponding to the scheduled communication. The scheduling network node s3 transmits the indication of the RA to the first controller PLC <NUM>, the second controller PLC <NUM>, the BS, and/or the like.

As shown in <FIG>, the BS may be the scheduling network node, in which case a direct communication link between s3 and PLC <NUM> and/or a direct communication link between s3 and PLC <NUM> may be based on Mode <NUM> sidelink. Similarly, a direct communication link between PLC <NUM> and PLC <NUM> may be based on Mode <NUM> sidelink. Direct communication links between the BS and either of the controllers PLC <NUM> or PLC <NUM>, the IIoT devices s1-s4, and/or the like, may be based on access link communications and may utilize a Uu interface.

As shown by reference number <NUM>, the first controller PLC <NUM> may transmit, and the network node (shown as the BS) may receive, an indication of a first set of parameters that corresponds to a direct communication link between an IIoT device (shown as s3) and a first controller (shown as PLC <NUM>). In some aspects, the first set of parameters may indicate a link quality associated with the direct communication link between the IIoT device s3 and the first controller PLC <NUM>, a load associated with the first controller PLC <NUM>, a resource requirement associated with the direct communication link between the IIoT device s3 and the first controller PLC <NUM>, and/or the like.

As shown by reference number <NUM>, the second controller PLC <NUM> may transmit, and the BS may receive, an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device s3 and the first controller PLC <NUM> through the second controller PLC <NUM>. In some aspects, the second set of parameters may include a set of first hop parameters corresponding to the direct communication link between the IIoT device s3 and the second controller PLC <NUM>, a set of second hop parameters corresponding to the direct communication link between the second controller PLC <NUM> and the first controller PLC <NUM>, and/or the like.

As shown by reference number <NUM>, the BS may schedule a communication on at least one of the direct communication link between the IIoT device s3 and the first controller PLC <NUM> or on the indirect communication link based at least in part on the first set of parameters and the second set of parameters. In some aspects, scheduling the communication may include determining a direct communication link metric based on the first set of parameters; determining an indirect communication link metric based on the second set of parameters; comparing the direct communication link metric with the indirect communication link metric; and selecting at least one of the direct communication link or the indirect communication link based at least in part on comparing the direct communication link metric with the indirect communication link metric.

As shown by reference number <NUM>, the BS transmits an indication of a resource allocation (RA) corresponding to the scheduled communication. The BS transmits the indication of the RA to the first controller PLC <NUM>, the second controller PLC <NUM>, the BS, and/or the like.

In some aspects, the scheduling network node (shown as the BS) may utilize multi-path diversity to improve reliability. For example, as shown by reference number <NUM>, scheduling the communication may include scheduling a primary transmission (shown as "Primary Tx") between the IIoT device and the first controller PLC <NUM> by allocating a first set of resources corresponding to the direct communication link. As shown by reference number <NUM>, the BS may schedule a retransmission (shown as "Re-Tx") between the IIoT device and the first controller PLC <NUM> by allocating a second set of resources corresponding to the indirect communication link. In some aspects, the retransmission may be sent upon receiving a negative acknowledgment (NACK) from the IIoT device s3. In some aspects, the primary transmission may be scheduled using resources corresponding to the indirect communication link and the retransmission may be scheduled using resources corresponding to the direct communication link.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a network node, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the network node (e.g., BS <NUM>, UE <NUM>, s1, s2, s3, s4, PLC <NUM>, PLC <NUM>, and/or the like) performs operations associated with communication link selection for non-RSRP based association in wireless industrial internet-of-things.

As shown in <FIG>, in some aspects, process <NUM> may include receiving an indication of a first set of parameters that corresponds to a direct communication link between an IIoT device and a first controller (block <NUM>). For example, the network node (e.g., using a receive processor, processor, memory, and/or the like) may receive an indication of a first set of parameters that corresponds to a direct communication link between an IIoT device and a first controller, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device and the first controller through a second controller (block <NUM>). For example, the network node (e.g., using controller/processor <NUM>, memory <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like) may receive an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device and the first controller through a second controller, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include scheduling a communication on at least one of the direct communication link or the indirect communication link based at least in part on the first set of parameters and the second set of parameters (block <NUM>). For example, the network node (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may schedule a communication on at least one of the direct communication link or the indirect communication link based at least in part on the first set of parameters and the second set of parameters, as described above.

In a first aspect, the first set of parameters indicates at least one of: a link quality associated with the direct communication link between the IIoT device and the first controller, a load associated with the first controller, a resource requirement associated with the direct communication link between the IIoT device and the first controller, or a combination thereof.

In a second aspect, alone or in combination with the first aspect, the second set of parameters comprises at least one of a set of first hop parameters corresponding to a direct communication link between the IIoT device and the second controller, and a set of second hop parameters corresponding to a direct communication link between the second controller and the first controller.

In a third aspect, alone or in combination with one or more of the first and second aspects, the second set of parameters indicates at least one of: a link quality associated with a direct communication link between the IIoT device and the second controller, a load associated with the second controller, a resource requirement associated with the direct communication link between the IIoT device and the second controller, a link quality associated with a direct communication link between the second controller and the first controller, a load associated with the first controller, a resource requirement associated with the direct communication link between the second controller and the first controller, or a combination thereof.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, scheduling the communication comprises: determining a direct communication link metric based on the first set of parameters; determining an indirect communication link metric based on the second set of parameters; comparing the direct communication link metric with the indirect communication link metric, and selecting at least one of the direct communication link or the indirect communication link based at least in part on comparing the direct communication link metric with the indirect communication link metric.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the direct communication link metric indicates at least one of: an estimated latency associated with the direct communication link between the IIoT device and the first controller, an estimated reliability associated with the direct communication link between the IIoT device and the first controller, or a combination thereof.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indirect communication link metric indicates at least one of: an estimated latency associated with a direct communication link between the IIoT device and the second controller, an estimated reliability associated with the direct communication link between the IIoT device and the second controller, an estimated latency associated with a direct communication link between the second controller and the first controller, an estimated reliability associated with the direct communication link between the second controller and the first controller, or a combination thereof.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link comprises: scheduling a primary transmission between the IIoT device and the first controller, and scheduling a retransmission between the IIoT device and the first controller.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, scheduling the communication comprises: scheduling the primary transmission between the IIoT device and the first controller by allocating a first set of resources corresponding to one of the direct communication link or the indirect communication link, and scheduling the retransmission between the IIoT device and the first controller by allocating a second set of resources corresponding to the other one of the direct communication link or the indirect communication link.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, scheduling the communication comprises: scheduling the primary transmission between the IIoT device and the first controller by allocating a first set of resources corresponding to the direct communication link or the indirect communication link, and scheduling the retransmission between the IIoT device and the first controller by allocating a second set of resources corresponding to the direct communication link or the indirect communication link.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link comprises allocating a set of resources corresponding to the direct communication link, the indirect communication link, or a combination thereof.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the set of resources comprises at least one of time resources, frequency resources, or spatial resources associated with at least one of: a semi-persistent scheduling communication, a periodic scheduling communication, an aperiodic scheduling communication, or a combination thereof.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link comprises scheduling the communication on the direct communication link by allocating a set of sidelink resources.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the first controller is configured as a small cell base station, and scheduling the communication on at least one of the direct communication link or the indirect communication link comprises scheduling the communication on the direct communication link by allocating a set of access link resources.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, scheduling the communication on at least one of the direct communication link or the indirect communication link comprises scheduling the communication on the indirect communication link by: allocating a first set of resources corresponding to a direct communication link between the IIoT device and the second controller, and allocating a second set of resources corresponding to a direct communication link between the second controller and the first controller.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the first set of resources comprises at least one of a set of sidelink resources or a set of access link resources.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the second set of resources comprises a set of sidelink resources.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the set of sidelink resources comprises at least one of a Mode <NUM> sidelink resource or a Mode <NUM> sidelink resource.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the set of sidelink resources are associated with a PC5 interface.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the set of access link resources are associated with an uplink/downlink (Uu) interface.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, receiving the indication of the first set of parameters comprises at least one of: receiving a unicast message from the IIoT device, receiving a unicast message from the first controller, receiving a multicast message from the IIoT device, receiving a multicast message from the first controller, receiving a broadcast message from the IIoT device, receiving a broadcast message from the first controller, or a combination thereof.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, receiving the indication of the second set of parameters comprises at least one of: receiving a unicast message from the IIoT device, receiving a unicast message from the first controller, receiving a unicast message from the second controller, receiving a multicast message from the IIoT device, receiving a multicast message from the first controller, receiving a multicast message from the second controller, receiving a broadcast message from the IIoT device, receiving a broadcast message from the first controller, receiving a broadcast message from the second controller, or a combination thereof.

In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the network node is to periodically receive indications of at least one of the first set of parameters, the second set of parameters, or a combination thereof.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the network node comprises at least one of the IIoT device, the first controller, the second controller, a third controller, a base station, or a combination thereof.

In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the IIoT device comprises a sensor or an actuator.

As used herein, the term "component" is intended to be broadly construed as hardware, and/or a combination of hardware and software.

Claim 1:
A network node for wireless communication, comprising:
a memory; and
one or more processors coupled to the memory, the one or more processors configured to:
receive an indication of a first set of parameters that corresponds to a direct communication link between an industrial internet-of-things, IIoT, device included in the network node and a first controller;
receive an indication of a second set of parameters that corresponds to an indirect communication link between the IIoT device and the first controller through a second controller;
schedule a communication on at least one of the direct communication link or the indirect communication link based at least in part on the first set of parameters and the second set of parameters; and
transmit an indication of a resource allocation corresponding to the scheduled communication to at least one of the first controller or the second controller based at least in part on scheduling the communication on the at least one of the direct communication link or the indirect communication link.