Communication link selection for non-RSRP-based association in wireless industrial IoT

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In certain aspects, a network node may receive an indication of a first parameter set corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device and a first controller; receive an indication of a second parameter set corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and schedule communications over at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 987,137, filed on March 9, 2020, entitled “COMMUNICATION LINK SELECTION FOR NON-RSRP BASED ASSOCIATION IN WIRELESS INDUSTRIAL INTERNET-OF-THINGS,” and U.S. Non-Provisional Patent Application No. 17 / 186,780, filed on February 26, 2021, entitled “COMMUNICATION LINK SELECTION FOR NON-RSRP BASED ASSOCIATION IN WIRELESS INDUSTRIAL INTERNET-OF-THINGS,” which are hereby expressly incorporated herein by reference.

[0003] public domain

[0004] Aspects of the present disclosure generally relate to wireless communications, and techniques and apparatuses for communication link selection in wireless Industrial Internet of Things that is not based on reference signal received power (RSRP) correlation.

[0005] background

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0007] A wireless network may include several base stations (BSs) capable of supporting communications for several user equipment (UEs). UEs may communicate with a BS via downlinks and uplinks. The downlink (or forward link) refers to the communication link from the BS to the UE, while the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in greater detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, 5G Node B, and so on.

[0008] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. NR (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful.

[0009] Overview

[0010] In some aspects, a network node for wireless communication includes: a memory; and one or more processors operably coupled to the memory, the memory and the one or more processors configured to: receive an indication of a first set of parameters corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device and a first controller; receive an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and schedule 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.

[0011] In certain aspects, a wireless communication method performed by a network node includes receiving an indication of a first parameter set corresponding to a direct communication link between an IIoT device and a first controller; receiving an indication of a second parameter set corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and scheduling communication on at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set.

[0012] In some aspects, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, causes the network node to: receive an indication of a first set of parameters corresponding to a direct communication link between an IIoT device and a first controller; receive an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and schedule 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.

[0013] In certain aspects, an apparatus for wireless communication includes means for receiving an indication of a first set of parameters corresponding to a direct communication link between an IIoT device and a first controller; means for receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and means for scheduling communications over 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.

[0014] Aspects generally include methods, apparatus (devices), systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated in the accompanying figures and description.

[0015] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The concepts and specific examples disclosed can be readily used as a basis for modifying or designing other structures for implementing the same purposes as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, as well as the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures is provided for illustration and description purposes and is not intended to define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to understand in detail the features of the present disclosure set forth above, a more particular description of the content briefly summarized above may be obtained with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure.

[0019] Figure 2 is a diagram illustrating an example of a base station and a UE in communication in a wireless network according to various aspects of the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of sidelink communication according to various aspects of the present disclosure.

[0021] Figure 4 is a diagram illustrating examples of side link communications and access link communications according to various aspects of the present disclosure.

[0022] Figure 5 is a diagram illustrating an example of an Industrial Internet of Things (IIoT) communication network according to various aspects of the present disclosure.

[0023] Figure 6 and 7 is a diagram illustrating an example of IIoT communication according to various aspects of the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of IIoT communication according to various aspects of the present disclosure.

[0025] Figure 9 and 10 is a diagram illustrating an example of non-reference signal received power (RSRP)-based associated communication link selection for wireless IIoT in accordance with aspects of the present disclosure.

[0026] Figure 11 is a diagram illustrating an example process, eg, performed by a network node, according to various aspects of the present disclosure.

[0027] Detailed description

[0028] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and they will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently of any other aspect of the present disclosure or implemented in combination. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using a supplement to the various aspects of the present disclosure set forth herein or other other structures, functionality, or structure and functionality. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

[0029] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] It should be noted that although various aspects may be described herein using terminology generally associated with 5G or NR radio access technologies (RATs), various aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs beyond 5G (e.g., 6G).

[0031] Figure 1 is a diagram illustrating an example of a wireless network 100 according to various aspects of the present disclosure. The wireless network 100 may be a 5G (NR) network and / or an LTE network, etc. or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, B node, gNB, 5G B node (NB), access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or a BS subsystem serving that coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in FIG, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "TRP," "AP," "Node B," "5G NB," and "cell" may be used interchangeably herein.

[0033] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0034] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in , relay BS 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, relay base station, relay, etc.

[0035] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0036] The network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. These BSs may also communicate with each other directly or indirectly via a wireless or wired backhaul.

[0037] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs may be considered machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and the like, which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as a processor component, a memory component, and the like. In some aspects, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, and the like.

[0039] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this scenario, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0041] Devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that may span 410 MHz to 7.125 GHz and / or may communicate using an operating band having a second frequency range (FR2), the first frequency range (FR1) may span 410 MHz to 7.125 GHz, and the second frequency range (FR2) may span 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz band." Similarly, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as a "millimeter wave" band. Thus, unless otherwise specifically stated, it should be understood that, if used herein, the term sub-6 GHz, etc., may broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically stated, it should be understood that, if used herein, the term "millimeter wave," etc., may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0042] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 Examples described.

[0043] Figure 2 A diagram illustrating an example 200 of a base station 110 and a UE 120 in communication in a wireless network 100 according to various aspects of the present disclosure is shown. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0044] At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the network node, and provide data symbols for all network nodes. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and / or secondary synchronization signal (SSS)). A transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0045] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signals to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0046] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0047] The antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, etc. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include coplanar sets of antenna elements and / or non-coplanar sets of antenna elements. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0048] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 comprises a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein, for example, as described with reference to Figure 9-11 described.

[0049] At base station 110, uplink signals from UE 120 and other UEs may be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include a scheduler 246 to schedule UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in a modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein, for example, as described with reference to Figure 9-11 described.

[0050] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, another UE, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 11 110 and / or operations of other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 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 compilation, conversion, interpretation, etc.) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Figure 11 In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, interpreting instructions, etc.

[0051] In some aspects, the network node 120 may include means for receiving an indication of a first parameter set corresponding to a direct communication link between an IIoT device and a first controller; means for receiving an indication of a second parameter set corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; means for scheduling communications over at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set, etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of the network node 120 are depicted, such as the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and the like.

[0052] although Figure 2The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented using a single hardware, software, or combined component or a combination of various components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0053] As indicated above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 Examples described.

[0054] Figure 3 is a diagram illustrating an example 300 of sidelink communications in accordance with various aspects of the present disclosure.

[0055] like Figure 3 As shown, a first UE 305-1 can communicate with a second UE 305-2 (and one or more other UEs 305) via one or more sidelink channels 310. UEs 305-1 and 305-2 can communicate using one or more sidelink channels 310 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication, V2P communication, etc.), mesh networking, and the like. In some aspects, UEs 305 (e.g., UE 305-1 and / or UE 305-2) can correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more sidelink channels 310 can use a PC5 interface and / or can operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, UEs 305 can use Global Navigation Satellite System (GNSS) timing to synchronize the timing of transmission time intervals (TTIs) (e.g., frames, subframes, time slots, symbols, etc.).

[0056] As in Figure 3As further shown in FIG, the one or more sidelink channels 310 may include a physical sidelink control channel (PSCCH) 315, a physical sidelink shared channel (PSSCH) 320, and / or a physical sidelink feedback channel (PSFCH) 325. The PSCCH 315 may be used to convey control information, similar to the physical downlink control channel (PDCCH) and / or physical uplink control channel (PUCCH) used for cellular communication with the base station 110 via an access link or access channel. The PSSCH 320 may be used to convey data, similar to the physical downlink shared channel (PDSCH) and / or physical uplink shared channel (PUSCH) used for cellular communication with the base station 110 via an access link or access channel. For example, the PSCCH 315 may carry sidelink control information (SCI) 330, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, spatial resources, etc.), wherein a transport block (TB) 335 may be carried on the PSSCH 320. The TB 335 may include data. The PSFCH 325 may be used to communicate sidelink feedback 340, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), scheduling request (SR), and the like.

[0057] In some aspects, one or more sidelink channels 310 may utilize a resource pool. For example, a scheduling assignment (e.g., included in SCI 330) may be transmitted in a subchannel using specific resource blocks (RBs) across time. In some aspects, a data transmission associated with the scheduling assignment (e.g., on PSSCH 320) may occupy contiguous RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not transmitted on contiguous RBs.

[0058] In some aspects, the UE 305 may operate using a transmission mode in which resource selection and / or scheduling is performed by the UE 305 (e.g., rather than the base station 110). In some aspects, the UE 305 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, the UE 305 may measure received signal strength indicator (RSSI) parameters associated with various sidelink channels (e.g., sidelink-RSSI (S-RSSI) parameters); may measure reference signal received power (RSRP) parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters); may measure reference signal received quality (RSRQ) parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), etc.; and may select a channel for transmission of sidelink communications based at least in part on the measurement(s).

[0059] Additionally or alternatively, the UE 305 may perform resource selection and / or scheduling using the SCI 330 (which may indicate occupied resources, channel parameters, etc.) received in the PSCCH 315. Additionally or alternatively, the UE 305 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 305 may use for a particular set of subframes).

[0060] In a transmission mode in which resource selection and / or scheduling is performed by the UE 305, the UE 305 may generate a sidelink grant and may transmit the grant in the SCI 330. The 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 320 (e.g., for TB 335), 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, etc. In some aspects, the UE 305 may generate a sidelink grant that indicates one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of the sidelink transmission. Additionally or alternatively, the UE 305 may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

[0061] As indicated above, Figure 3 are provided as examples. Other examples may differ from those described in Figure 3 Examples described.

[0062] Figure 4 is a diagram illustrating an example 400 of sidelink and access link communications in accordance with various aspects of the present disclosure.

[0063] like Figure 4 As shown, the transmitter (Tx) UE 405 and the receiver (Rx) UE 410 can communicate with each other via a side link, as described above in conjunction with Figure 3 As further shown, in some sidelink modes, the base station 110 may communicate with the Tx UE 405 via a first access link. Additionally or alternatively, in some sidelink modes, the base station 110 may communicate with the Rx UE 410 via a second access link. The Tx UE 405 and / or the Rx UE 410 may correspond to one or more UEs described elsewhere herein, such as Figure 1UE 120. Thus, a "sidelink" may refer to a direct link between UEs 120, and an "access link" may refer to a direct link between base station 110 and UE 120. Sidelink communications may be transmitted via the sidelink, and access link communications may be transmitted via the access link. Access link communications may be downlink communications (from base station 110 to UE 120) or uplink communications (from UE 120 to base station 110).

[0064] As indicated above, Figure 4 are provided as examples. Other examples may differ from those described in Figure 4 Examples described.

[0065] IIoT is a branch of cellular technology in which UEs and BSs can be used to carry control data, measurement data, etc. between various industrial systems. For example, IIoT can be used to control IIoT devices such as sensors and / or actuators, exchange measurement information between other IIoT devices such as programmable logic controllers (PLCs) in a factory (e.g., in factory automation applications), etc. According to various aspects, the IIoT devices discussed herein (e.g., sensors, actuators, PLCs, etc.) can be or include devices such as the above combined devices. Figure 1 In some aspects, the IIoT device may be used as a small cell (e.g., a pico cell), in which case the IIoT device may be or may include a device such as the one described above in combination with a micro cell. Figure 1 A BS such as the BS 110 in question may be included in the BS.

[0066] Figure 5 is a diagram illustrating an example of an IIoT communication network 500 according to various aspects of the present disclosure.

[0067] As shown, network 500 includes a PLC 502 (itself a type of IIoT device) exchanging wireless communications 504 with IIoT devices 506 (shown as 506A, 506B, and 506C). IIoT devices 506 may include sensors 506C, actuators 506A and 506B, and the like. In certain aspects, IIoT devices 506 may be associated with equipment 508 (shown as 508A and 508B). Network 500 may include a base station 510 that exchanges communications 512 with PLC 502 and / or exchanges communications 514 with one or more other IIoT devices 506.

[0068] Communication between PLC 502 and IIoT devices 506 may include a cyclical exchange of information. PLC 502 may provide commands to factory equipment 508 in wireless signals. Sensors 506C and actuators 506A, 506B may be separate from factory equipment 508 and / or may be included and / or located within a piece of factory equipment 508. PLC 502 may automate the control of machines and control systems, such as those on factory assembly lines, rides, lighting, and the like. IIoT network 500 may include any number of PLCs 502, sensors 506C, actuators 506A, 506B, and the like.

[0069] As indicated above, Figure 5 are provided as examples. Other examples may differ from those described in Figure 5 Examples described.

[0070] Figure 6 is a diagram illustrating an example 600 of IIoT communications in accordance with various aspects of the present disclosure.

[0071] As shown, the PLC 602 and the IIoT device 604 may exchange periodic or cyclic traffic. The PLC 602 may D-DL The communication 606 (such as a command or other communication) is transmitted to the IIoT device 604 during the period T. The communication 608 from the PLC 602 to the IIoT device 604 may be referred to as a downlink communication. The IIoT device 604 may receive the communication 608 and may take an action based on the command. After the action, the IIoT device 604 may D-UL 612 during which the communication 610 is transmitted back to the PLC 602. There may be a processing time duration 614 (T) between receiving the communication 606 from the PLC 602 and transmitting the communication 610 from the IIoT device 604. AP During this processing time, the IIoT device 604 may be sensing, actuating, etc.

[0072] In some aspects, the communication 610 may include sensed data from a sensor, confirmation of an actuation from an actuator, etc. The communication 610 may include an application layer acknowledgment. The communication 610 transmitted from the IIoT device 604 to the PLC 602 may be referred to as an uplink communication. After the PLC receives the communication 610 from the IIoT device 604, there may be a processing duration 616 (T AP ), during which processing duration 616 and before the PLC 602 sends additional communications / commands to the IIoT device 604, the PLC 602 may process the received information. The combined loop may have a length of T 循环 The duration is 618. The duration is 616T APThe cycle may then repeat by the PLC 602 sending additional communications 606 to the IIoT device 604 .

[0073] The communication network can accommodate periodic regular traffic between the PLC 602 and the IIoT devices 604. The communication between the PLC 602 and the IIoT devices 604 can be associated with low latency and high reliability. For example, the communication can be based on a latency of less than 2 ms or less than 1 ms. The communication can have a latency of 10 -5 or 10 -6 Reliability requirements of the order of 99.9999% are possible. Latency and reliability can apply to both data and control channels.

[0074] In some aspects, the PLC 602 may use a control channel (such as a physical downlink control channel (PDCCH)) to grant resources to the IIoT device 604 for transmitting periodic uplink communications 610. Factory automation may involve a high density of IIoT devices 604 (e.g., approximately 1 UE per square meter). Therefore, a large number of IIoT devices 604 may communicate with the PLC 602. Sending dynamic grants (e.g., one downlink control information (DCI) per time slot) to each of the large number of IIoT devices 604 may burden the PDCCH overhead. Semi-persistent scheduling (SPS) may be used to reduce the overhead requirements of the PDCCH by enabling the IIoT device 604 to be granted resources in a semi-persistent or periodic manner. SPS may also be used to schedule resources for receiving downlink communications. SPS may be conveyed to each IIoT device 604 using radio resource control (RRC) signaling and / or DCI. In some aspects, SPS may be used for a first transmission, and the PDCCH may be used to schedule possible retransmissions if the first transmission is not accurately received.

[0075] As indicated above, Figure 6 are provided as examples. Other examples may differ from those described in Figure 6 Examples described.

[0076] Figure 7 is a diagram illustrating an example 700 of IIoT communication according to various aspects of the present disclosure. Figure 7As shown, IIoT communication may include downlink transmissions from the PLC to sensor and / or actuator 1 (shown as "S / A 1"), sensor and / or actuator 2 (shown as "S / A 2") in time slot 1 based on SPS, and so on until a downlink transmission to sensor and / or actuator N (shown as "S / AN"). Acknowledgement / negative acknowledgement (ACK / NACK) feedback may be received from each sensor / actuator. Based on the feedback, the PLC may transmit a PDCCH to schedule resources for retransmitting the information to the sensor / actuator from which a NACK or an ACK was not received. For uplink communication, the PLC may receive uplink transmissions from sensor / actuator 1 (S / A 1), sensor / actuator 2 (S / A 2) ... sensor / actuator N (S / AN) in time slot 1 based on SPS. The PLC may provide ACK / NACK feedback to each sensor / actuator. The PLC may transmit a PDCCH to the sensor / actuator scheduling retransmissions of messages that were not correctly received by the PLC.

[0077] As indicated above, Figure 7 are provided as examples. Other examples may differ from those described in Figure 7 Examples described.

[0078] Figure 8 is a diagram illustrating an example 800 of IIoT communications in accordance with various aspects of the present disclosure.

[0079] As shown in the figure numeral 805, a first PLC (shown as "PLC 1") can be configured to communicate with a first IIoT device (shown as "s1") and a second IIoT device (shown as "s3"). PLC 1 can be associated with s1 and s3, which means that PLC 1 can control s1 and / or s3, be configured to receive and / or process data from s1 and / or s3, and so on. In some aspects, the association between PLC1 and s1 and s3 can be established at the application layer by an industrial application that controls the operation of the plant. Similarly, as shown, a second PLC (shown as "PLC 2") can be associated with a third IIoT device (shown as "s2") and a fourth IIoT device (shown as "s4"). In some aspects, the association between PLC2 and s2 and s4 can be established by an industrial application. The communication link between the PLC and the IIoT devices can be based on a PC5 interface, which can be used to implement side link communication.

[0080] A base station (BS) (e.g., a gNB, etc.) can communicate with PLC 1 and / or PLC 2. In some aspects, PLCs 1 and 2 can be located close to the machinery, while the BS can be mounted on a ceiling or at a greater distance from the equipment. The communication link between the BS and the PLC can be based on an uplink / downlink (Uu) interface, which can also be referred to as an access link. In some aspects, the PLC can function as a small cell, and one or more IIoT devices can communicate with the PLC based on the Uu interface (access link).

[0081] In some aspects, one or more PLCs may use the BS for inter-PLC coordination with other PLCs. Additionally or alternatively, the PLCs may communicate with each other over a direct communication link. The direct communication between PLC 1 and PLC 2 may be based on sidelink communication, which in some aspects may utilize the PC5 interface. In some aspects, one or more PLCs may use the BS for backhaul to a human-machine interface (HMI). In some aspects, one or more 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 IIoT devices, such as initial access to the network, mobility, and the like.

[0082] As shown above, an application can determine the association between a PLC and an IIoT device. In some aspects, this association can be based on industrial functions and processes rather than on the quality of the communication link (such as RSRP) between the PLC and its associated IIoT device. As shown, for example, PLC 1 can be associated with s3 even though it is farther away from s3 than PLC 2. Similarly, PLC 2 can be associated with s2 even though it is farther away from s2 than PLC 1. The direct communication link between PLC 1 and s3, as well as the direct communication link between PLC 2 and s2, may be weak, susceptible to cross-link interference, etc.

[0083] As shown in reference numeral 810, to alleviate some of the issues associated with direct communication links between PLCs and associated IIoT devices, a base station (BS) may communicate with one or more of IIoT devices s1, s2, s3, and / or s4. The links between the BS and the IIoT devices may be based on the Uu interface. BS transmission control may help improve reliability. This BS control may involve two hops to provide control to the IIoT—a first hop from the PLC to the base station and a second hop from the base station to the associated IIoT device. In some examples, a portion of the scheduling for the IIoT device may be provided by the BS, while another portion of the scheduling may be provided by PLC 1 and / or PLC 2. Providing certain control directly from the PLC may help reduce over-the-air signaling and improve latency. However, transmissions from the PLC may be blocked to specific IIoT devices. Blockage of the links between the PLC and various IIoT devices may last for varying amounts of time. Furthermore, using a BS for two-hop communication may be inefficient due to the potential introduction of increased latency.

[0084] Aspects of the techniques and devices disclosed herein can enable communication link selection between a direct communication link and a two-hop communication link for non-RSRP-based association in a wireless IIoT environment. The two-hop communication link can include a first hop between the IIoT device and a first controller and a second hop between the first controller and a second controller. In this way, two-hop communication can be utilized without utilizing a base station. In certain aspects, a direct or indirect communication link can be selected that has characteristics that meet one or more thresholds. The characteristics can be evaluated using parameters related to reliability, latency, signal quality, etc.

[0085] In some aspects, a network node (e.g., a PLC, an IIoT device, etc.) may act as a scheduling device and may receive an indication of parameters corresponding to a direct communication link between the IIoT device and a first controller (e.g., a PLC, etc.) and an indication of parameters corresponding to an indirect communication link between the IIoT device and the first controller, wherein the indirect communication link involves a second controller. The scheduling device may schedule communications over direct and / or indirect communication links based at least in part on these parameters. In this way, various aspects of the technology disclosed herein may enable improving network capacity when load balancing across PLCs based on a two-hop metric corresponding to these parameters. In some aspects, the technology described herein may facilitate multipath diversity, where a transmission and its retransmission are forwarded over different communication links. In some aspects, utilizing a controller for multi-hop communication may reduce the demand on BS capacity.

[0086] As indicated above, Figure 8 are provided as examples. Other examples may differ from those described in Figure 8 Examples described.

[0087] Figure 9 is a diagram illustrating an example 900 of communication link selection for non-RSRP based association in a wireless Industrial Internet of Things, in accordance with aspects of the present disclosure.

[0088] like Figure 9 As shown, IIoT device s3 may be a dispatch network node, in which case the direct communication link 905 between s3 and PLC 1 and / or the direct communication link 910 between s3 and PLC 2 may be based on a Mode 2 side link. Similarly, the direct communication link 915 between PLC 1 and PLC 2 may be based on a Mode 2 side link. In certain aspects, as described below in conjunction with Figure 10 As discussed, the scheduling network node may be a BS for Uu (access link)-based communications, Mode 1 sidelink communications, etc. In certain aspects, the scheduling network node may include PLC 1 and / or PLC 2 for small cell Uu communications, Mode 2 sidelink communications with UE-UE scheduling, Mode 1 sidelink communications, etc.

[0089] As shown at reference numeral 920, network node s3 can receive an indication of a first parameter set corresponding to a direct communication link 905 between the IIoT device and a first controller (shown as PLC1). In the illustrated aspects where the scheduling network node includes an IIoT device, at least a portion of the indication of the first parameter set can be received by the IIoT device s3 itself (e.g., by determining one or more parameters in the first parameter set, etc.). As shown, in some aspects, at least a portion of the indication of the first parameter set can be received from the first controller PLC1.

[0090] In some aspects, the first parameter set may indicate a communication link quality associated with the direct communication link between the IIoT device s3 and the first controller PLC1, a load associated with the first controller PLC1, a resource requirement associated with the direct communication link 905 between the IIoT device s3 and the first controller PLC1, etc. In some aspects, receiving the indication of the first parameter set may include receiving a unicast message from the first controller PLC1, receiving a multicast message from the first controller PLC1, receiving a broadcast message from the first controller PLC1, etc.

[0091] In some aspects, for example, the IIoT device s3 may receive a parameter indicative of link quality by determining a link quality associated with the direct communication link 905. In some aspects, the IIoT device s3 may determine the link quality based on a reference signal received from the first controller PLC 1. The link quality may include any number of different measures of communication quality, such as, for example, reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-noise ratio (SNR), signal-to-interference and noise ratio (SINR), and the like.

[0092] In some aspects, the first controller PLC 1 can transmit an indication of a parameter indicative of a load associated with the PLC 1. "Load" can refer to a communication and / or processing load associated with communicating with one or more devices. The one or more devices can include an IIoT device s3, another IIoT device (s1, s2, s4, etc.), another controller (e.g., PLC 2, etc.), etc. In some aspects, the indication of a parameter indicative of a resource requirement associated with the communication link 905 can be received from the first controller PLC 1 and / or the IIoT device s3.

[0093] As shown at reference numeral 925, the scheduling network node s3 may receive an indication of a second parameter set corresponding to an indirect communication link between the IIoT device s3 and the first controller PLC 1 via the second controller PLC 2. The indication of the second parameter set may be received from the first controller PLC 1 and / or the second controller PLC 2. In certain aspects, as Figure 9 As shown, the second parameter set may include at least one of the following: a first-hop parameter set corresponding to the direct communication link 910 between the IIoT device s3 and the second controller PLC 2 or a second-hop parameter set corresponding to the direct communication link 915 between the second controller PLC 2 and the first controller PLC 1.

[0094] In some aspects, the second parameter set may indicate a link quality associated with the direct communication link 910 between the IIoT device s3 and the second controller PLC 2, a load associated with the second controller PLC 2, a resource requirement associated with the direct communication link 910 between the IIoT device s3 and the second controller PLC 2, a link quality associated with the direct communication link 915 between the second controller PLC 2 and the first controller PLC 1, a load associated with the first controller PLC 1, a resource requirement associated with the direct communication link 915 between the second controller PLC 2 and the first controller PLC 1, and the like.

[0095] In some aspects, receiving an indication of the second parameter set may include receiving a unicast message from the first controller PLC 1, receiving a unicast message from the second controller PLC 2, receiving a multicast message from the first controller PLC 1, receiving a multicast message from the second controller PLC 2, receiving a broadcast message from the first controller PLC 1, receiving a broadcast message from the second controller PLC 2, or a combination thereof. In some aspects, the scheduling network node may be configured to periodically receive an indication of at least one of the first parameter set, the second parameter set, or a combination thereof.

[0096] As shown at reference numeral 930, the scheduling network node s3 can schedule communication over at least one of the direct communication link 905 or the indirect communication link between the IIoT device s3 and the first controller PLC 1 based at least in part on the first parameter set and the second parameter set. In certain aspects, scheduling the communication can include determining a direct communication link metric based on the first parameter set; determining an indirect communication link metric based on the second parameter set; comparing the direct communication link metric to 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 to the indirect communication link metric.

[0097] In some aspects, the direct communication link metrics indicate an estimated latency associated with the direct communication link 905 between the IIoT device s3 and the first controller PLC 1, an estimated reliability associated with the direct communication link between the IIoT device s3 and the first controller PLC 1, etc. In some aspects, the indirect communication link metrics may indicate an estimated latency associated with the direct communication link 910 between the IIoT device s3 and the second controller PLC 2, an estimated reliability associated with the direct communication link 910 between the IIoT device s3 and the second controller PLC 2, an estimated latency associated with the direct communication link 915 between the second controller PLC 2 and the first controller PLC 1, an estimated reliability associated with the direct communication link 915 between the second controller PLC 2 and the first controller PLC 1, etc.

[0098] In some aspects, scheduling communications over 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 1 and scheduling retransmissions between the IIoT device s3 and the first controller PLC 1. In some aspects, scheduling communications may include scheduling the primary transmission between the IIoT device s3 and the first controller PLC 1 by allocating a first set of resources corresponding to the direct communication link or the indirect communication link and scheduling retransmissions between the IIoT device s3 and the first controller PLC 1 by allocating a second set of resources corresponding to the direct communication link or the indirect communication link.

[0099] In certain aspects, scheduling communications on at least one of the direct communication link or the indirect communication link may include allocating a resource set corresponding to the direct communication link, the indirect communication link, or a combination thereof. In certain aspects, the resource set may include time resources, frequency resources, space resources, etc. The resource set may be associated with semi-persistently scheduled (SPS) communications, periodically scheduled communications, aperiodically scheduled communications, etc.

[0100] In some aspects, scheduling communications may include scheduling communications on the direct communication link by allocating a set of side link resources. In some aspects, the first controller PLC 1 may be configured as a small cell base station and scheduling communications may include scheduling communications on the direct communication link by allocating a set of access link resources.

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

[0102] The scheduling network node s3 may transmit an indication of a resource allocation (RA) corresponding to the scheduled communication, as indicated by reference numeral 935. The scheduling network node s3 may transmit the indication of the RA to the first controller PLC1, the second controller PLC2, the BS, and the like.

[0103] As indicated above, Figure 9 are provided as examples. Other examples may differ from those described in Figure 9 Examples described.

[0104] Figure 10 is a diagram illustrating an example 1000 of communication link selection for non-RSRP based association in a wireless Industrial Internet of Things, in accordance with aspects of the present disclosure.

[0105] like Figure 10As shown, the BS may be a dispatching network node, in which case the direct communication link between s3 and PLC1 and / or the direct communication link between s3 and PLC2 may be based on a Mode 1 side link. Similarly, the direct communication link between PLC1 and PLC2 may be based on a Mode 1 side link. The direct communication link between the BS and any of the controllers PLC1 or PLC2, IIoT devices s1-s4, etc. may be based on access link communication and may utilize a Uu interface.

[0106] As shown at reference numeral 1005, the first controller PLC1 may transmit, and the network node (shown as BS) may receive, an indication of a first set of parameters corresponding to a direct communication link between an IIoT device (shown as s3) and the first controller (shown as PLC1). In certain 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 PLC1, a load associated with the first controller PLC1, a resource requirement associated with the direct communication link between the IIoT device s3 and the first controller PLC1, and the like.

[0107] As indicated by reference numeral 1010, the second controller PLC 2 may transmit, and the BS may receive, an indication of a second parameter set corresponding to an indirect communication link between the IIoT device s3 and the first controller PLC 1 via the second controller PLC 2. In certain aspects, the second parameter set may include a first-hop parameter set corresponding to a direct communication link between the IIoT device s3 and the second controller PLC 2, a second-hop parameter set corresponding to a direct communication link between the second controller PLC 2 and the first controller PLC 1, and so on.

[0108] As indicated by reference numeral 1015, the BS may schedule communication over at least one of a direct communication link or an indirect communication link between the IIoT device s3 and the first controller PLC 1 based at least in part on the first parameter set and the second parameter set. In certain aspects, scheduling the communication may include determining a direct communication link metric based on the first parameter set; determining an indirect communication link metric based on the second parameter set; comparing the direct communication link metric to 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 to the indirect communication link metric.

[0109] As indicated by reference numeral 1020, the BS may transmit an indication of a resource allocation (RA) corresponding to the scheduled communication. The BS may transmit the indication of the RA to the first controller PLC1, the second controller PLC2, the BS, and so on.

[0110] In some aspects, the scheduling network node (shown as BS) can utilize multipath diversity to improve reliability. For example, as shown in the reference numeral 1025, scheduling communications may include scheduling a main transmission (shown as "Main Tx") between the IIoT device and the first controller PLC 1 by allocating a first set of resources corresponding to a direct communication link. As shown in the reference numeral 1030, the BS can schedule retransmissions (shown as "Re-Tx") between the IIoT device and the first controller PLC 1 by allocating a second set of resources corresponding to an indirect communication link. In some aspects, the retransmission can be sent upon receiving a negative acknowledgment (NACK) from the IIoT device s3. In some aspects, the main transmission can be scheduled using resources corresponding to the indirect communication link, and the retransmission can be scheduled using resources corresponding to the direct communication link.

[0111] As indicated above, Figure 10 are provided as examples. Other examples may differ from those described in Figure 10 Examples described.

[0112] Figure 11 1 is a diagram illustrating an example process 1100, for example, performed by a network node, in accordance with various aspects of the present disclosure. Example process 1100 is an example of operations in which a network node (e.g., BS 110, UE 120, s1, s2, s3, s4, PLC 1, PLC 2, etc.) performs communication link selection for non-RSRP-based association in a wireless Industrial Internet of Things.

[0113] like Figure 11 As shown, in certain aspects, process 1100 may include receiving an indication of a first set of parameters corresponding to a direct communication link between an IIoT device and a first controller (block 1110). For example, a network node (e.g., using a receiving processor, a processor, a memory, etc.) may receive an indication of a first set of parameters corresponding to a direct communication link between an IIoT device and a first controller, as described above.

[0114] like Figure 11 As further shown, in certain aspects, process 1100 may include receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via the second controller (block 1120). For example, the network node (e.g., using controller / processor 280, memory 282, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.) may receive an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via the second controller, as described above.

[0115] like Figure 11As further illustrated, in certain aspects, process 1100 may include scheduling communications over at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set (block 1130). For example, the network node (e.g., using controller / processor 280, memory 282, etc.) may schedule communications over at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set, as described above.

[0116] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0117] In a first aspect, the first parameter set indicates at least one of: a link quality associated with a 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.

[0118] In a second aspect, alone or in combination with the first aspect, the second parameter set includes at least one of the following: a first-hop parameter set corresponding to a direct communication link between the IIoT device and the second controller and a second-hop parameter set corresponding to a direct communication link between the second controller and the first controller.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, the second parameter set indicates at least one of: a link quality associated with the 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 the 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.

[0120] In a fourth aspect, alone or in combination with one or more of aspects 1 to 3, scheduling communications comprises determining a direct communication link metric based on a first set of parameters; determining an indirect communication link metric based on a second set of parameters; comparing the direct communication link metric to 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 to the indirect communication link metric.

[0121] In a fifth aspect, either alone or in combination with one or more of aspects one to four, 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.

[0122] In a sixth aspect, either alone or in combination with one or more of aspects one to five, the indirect communication link metric indicates at least one of: an estimated wait time associated with a direct communication link between the IIoT device and the second controller, an estimated reliability associated with a direct communication link between the IIoT device and the second controller, an estimated wait time associated with a direct communication link between the second controller and the first controller, an estimated reliability associated with a direct communication link between the second controller and the first controller, or a combination thereof.

[0123] In a seventh aspect, alone or in combination with one or more of aspects one to six, scheduling communications on at least one of a direct communication link or an indirect communication link includes scheduling a main transmission between the IIoT device and the first controller and scheduling a retransmission between the IIoT device and the first controller.

[0124] In an eighth aspect, alone or in combination with one or more of aspects one to seven, scheduling communications includes scheduling main transmissions 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 retransmissions between the IIoT device and the first controller by allocating a second set of resources corresponding to the other of the direct communication link or the indirect communication link.

[0125] In a ninth aspect, alone or in combination with one or more of aspects one to eight, scheduling communications includes scheduling main transmissions between the IIoT device and the first controller by allocating a first set of resources corresponding to a direct communication link or an indirect communication link, and scheduling retransmissions 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.

[0126] In a tenth aspect, alone or in combination with one or more of aspects one to nine, scheduling communications on at least one of a direct communication link or an indirect communication link includes allocating a set of resources corresponding to the direct communication link, the indirect communication link, or a combination thereof.

[0127] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the resource set includes at least one of time resources, frequency resources, or space resources associated with at least one of: semi-persistent scheduled communication, periodic scheduled communication, non-periodic scheduled communication, or a combination thereof.

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

[0129] In a thirteenth aspect, alone or in combination with one or more of aspects one to twelfth, the first controller is configured as a small cell base station, and scheduling communications on at least one of a direct communication link or an indirect communication link includes scheduling communications on the direct communication link by allocating an access link resource set.

[0130] In a fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, scheduling communications on at least one of a direct communication link or an indirect communication link includes scheduling communications on the indirect communication link by allocating a first set of resources corresponding to the direct communication link between the IIoT device and the second controller and allocating a second set of resources corresponding to the direct communication link between the second controller and the first controller.

[0131] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the first resource set includes at least one of a side link resource set or an access link resource set.

[0132] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the second resource set comprises a sidelink resource set.

[0133] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the sidelink resource set includes at least one of a mode 1 sidelink resource or a mode 2 sidelink resource.

[0134] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the sidelink resource set is associated with a PC5 interface.

[0135] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the access link resource set is associated with an uplink / downlink (Uu) interface.

[0136] In the twentieth aspect, alone or in combination with one or more of aspects one to nineteen, receiving an indication of the first parameter set includes 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.

[0137] In aspect 21, either alone or in combination with one or more of aspects 1 to 20, receiving an indication of a second set of parameters comprises at least one of: receiving a unicast message from an IIoT device, receiving a unicast message from a first controller, receiving a unicast message from a second controller, receiving a multicast message from an IIoT device, receiving a multicast message from a first controller, receiving a multicast message from a second controller, receiving a broadcast message from an IIoT device, receiving a broadcast message from a first controller, receiving a broadcast message from a second controller, or a combination thereof.

[0138] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the network node periodically receives an indication of at least one of the first parameter set, the second parameter set, or a combination thereof.

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

[0140] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the IIoT device includes a sensor or an actuator.

[0141] although Figure 11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Figure 11 1100. Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0142] The following provides an overview of some aspects of the disclosure:

[0143] Aspect 1: A wireless communication method performed by a network node, comprising: receiving an indication of a first parameter set corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device and a first controller; receiving an indication of a second parameter set corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; and scheduling communication on at least one of the direct communication link or the indirect communication link based at least in part on the first parameter set and the second parameter set.

[0144] Aspect 2: A method as described in Aspect 1, wherein the first parameter set indicates at least one of the following: link quality associated with the direct communication link between the IIoT device and the first controller, load associated with the first controller, resource requirements associated with the direct communication link between the IIoT device and the first controller, or a combination thereof.

[0145] Aspect 3: A method as described in any of Aspects 1 or 2, wherein the second parameter set includes at least one of the following: a first-hop parameter set corresponding to a direct communication link between the IIoT device and the second controller and a second-hop parameter set corresponding to a direct communication link between the second controller and the first controller.

[0146] Aspect 4: A method as described in any of Aspects 1-3, wherein the second parameter set indicates at least one of the following: a link quality associated with the 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 the 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.

[0147] Aspect 5: A method as described in any of Aspects 1-3, wherein scheduling the communication includes: determining a direct communication link metric based on the first parameter set; determining an indirect communication link metric based on the second parameter set; 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.

[0148] Aspect 6: A method as described in Aspect 5, wherein the direct communication link metric indicates at least one of: an estimated waiting time 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.

[0149] Aspect 7: A method as described in any of Aspects 5 or 6, wherein the indirect communication link metric indicates at least one of: an estimated waiting time associated with the 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 waiting time associated with the 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.

[0150] Aspect 8: A method as described in any of Aspects 1-7, wherein scheduling the communication on at least one of the direct communication link or the indirect communication link includes: scheduling a main transmission between the IIoT device and the first controller; and scheduling a retransmission between the IIoT device and the first controller.

[0151] Aspect 9: A method as described in Aspect 8, wherein scheduling the communication includes: scheduling the main 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 of the direct communication link or the indirect communication link.

[0152] Aspect 10: A method as described in Aspect 8, wherein scheduling the communication includes: scheduling the main 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.

[0153] Aspect 11: The method of any of Aspects 1-10, wherein 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.

[0154] Aspect 12: The method of aspect 11, wherein the resource set comprises at least one of time resources, frequency resources, or space resources associated with at least one of: semi-persistently scheduled communication, periodically scheduled communication, aperiodically scheduled communication, or a combination thereof.

[0155] Aspect 13: The method of any one of aspects 1-12, wherein 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.

[0156] Aspect 14: A method as described in any of Aspects 1-13, wherein the first controller is configured as a small cell base station, and wherein scheduling the communication on at least one of the direct communication link or the indirect communication link includes scheduling the communication on the direct communication link by allocating an access link resource set.

[0157] Aspect 15: A method as described in any of Aspects 1-15, wherein scheduling the communication on at least one of the direct communication link or the indirect communication link includes scheduling the communication on the indirect communication link by: allocating a first set of resources corresponding to the direct communication link between the IIoT device and the second controller; and allocating a second set of resources corresponding to the direct communication link between the second controller and the first controller.

[0158] Aspect 16: The method of aspect 15, wherein the first resource set comprises at least one of a side link resource set or an access link resource set.

[0159] Aspect 17: The method according to any one of aspects 15 or 16, wherein the second resource set comprises a sidelink resource set.

[0160] Aspect 18: The method of aspect 17, wherein the set of sidelink resources comprises at least one of mode 1 sidelink resources or mode 2 sidelink resources.

[0161] Aspect 19: The method according to any one of aspects 17 or 18, wherein the sidelink resource set is associated with a PC5 interface.

[0162] Aspect 20: The method according to any one of aspects 15-19, wherein the access link resource set is associated with an uplink / downlink (Uu) interface.

[0163] Aspect 21: A method as described in any of Aspects 1-20, wherein receiving an indication of the first parameter set includes at least one of the following: receiving a unicast message from the IIoT device, receiving a unicast message from the first controller, receiving multicast information from the IIoT device, receiving multicast information from the first controller, receiving a broadcast message from the IIoT device, receiving a broadcast message from the first controller, or a combination thereof.

[0164] Aspect 22: A method as described in any of Aspects 1-21, wherein receiving an indication of the second parameter set includes at least one of the following: 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.

[0165] Aspect 23: The method according to any one of aspects 1-22, wherein the network node periodically receives an indication of at least one of the first parameter set, the second parameter set, or a combination thereof.

[0166] Aspect 24: The method of any one of Aspects 1-23, wherein 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.

[0167] Aspect 25: The method of any one of Aspects 1-24, wherein the IIoT device comprises a sensor or an actuator.

[0168] Aspect 26: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in one or more of Aspects 1-25.

[0169] Aspect 27: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method as described in one or more of aspects 1-25.

[0170] Aspect 28: An apparatus for wireless communication, comprising at least one means for performing the method as recited in one or more of Aspects 1-25.

[0171] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-25.

[0172] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-25.

[0173] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0174] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. "Software" should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a processor is implemented using hardware and / or a combination of hardware and software.

[0175] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0176] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Thus, the operation and behavior of these systems and / or methods are described herein without reference to specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods based, at least in part, on the description herein.

[0177] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0178] Although specific feature combinations are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. As used herein, the phrase quoting "at least one of" a column of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to encompass: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other sorting of a, b and c).

[0179] The elements, actions or instructions used herein should not be interpreted as key or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more projects and can be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more projects cited in conjunction with the article "the" and can be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "group" are intended to include one or more projects (e.g., related items, non-related items, a combination of related and non-related items, etc.) and can be used interchangeably with "one or more". In cases where it is intended to have only one project, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "having", "containing", "comprising" etc. are intended to be open terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a sequence is intended to be inclusive and can be used interchangeably with and " / or" unless expressly stated otherwise (e.g., when used in conjunction with "either of" or "only one of").

Claims

1. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving an indication of a first set of parameters corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device comprising the network node and a first controller; receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; scheduling communications over 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 well as An indication of a resource allocation corresponding to the scheduled communication is transmitted to at least one of the first controller or the second controller based at least in part on scheduling the communication on at least one of the direct communication link or the indirect communication link.

2. The network node of claim 1 , wherein the first parameter set 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, resource requirements associated with the direct communication link between the IIoT device and the first controller, or Its combination.

3. The network node of claim 1 , wherein the second parameter set comprises at least one of: a first-hop parameter set corresponding to a direct communication link between the IIoT device and the second controller, and a second-hop parameter set corresponding to a direct communication link between the second controller and the first controller.

4. The network node of claim 1 , wherein the second parameter set 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, resource requirements 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, resource requirements associated with the direct communication link between the second controller and the first controller, or Its combination.

5. The network node of claim 1 , wherein the one or more processors, when scheduling the communication: 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 to the indirect communication link metric; as well as At least one of the direct communication link or the indirect communication link is selected based at least in part on comparing the direct communication link metric to the indirect communication link metric.

6. The network node of claim 5, wherein 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 Its combination.

7. The network node of claim 5, wherein 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 Its combination.

8. The network node of claim 1 , wherein the one or more processors are configured to, when scheduling the communication over at least one of the direct communication link or the indirect communication link: scheduling a 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 Retransmissions between the IIoT device and the first controller are scheduled by allocating a second set of resources corresponding to the direct communication link or the indirect communication link.

9. The network node of claim 1 , wherein the one or more processors are configured to, when scheduling the communication on at least one of the direct communication link or the indirect communication link, allocate a resource set corresponding to the direct communication link, the indirect communication link, or a combination thereof, and wherein the resource set comprises at least one of time resources, frequency resources, or spatial resources associated with at least one of: Semi-persistent scheduled communication, Periodically scheduled communications, Aperiodically scheduled communication, or Its combination.

10. The network node of claim 1 , wherein the one or more processors are configured to, when scheduling the communication on at least one of the direct communication link or the indirect communication link, schedule the communication on the direct communication link by allocating a set of sidelink resources.

11. The network node of claim 1 , wherein the first controller is configured as a small cell base station, and wherein the one or more processors are configured to, when scheduling the communication on at least one of the direct communication link or the indirect communication link, schedule the communication on the direct communication link by allocating an access link resource set.

12. The network node of claim 1 , wherein the one or more processors are configured to, when scheduling the communication on at least one of the direct communication link or the indirect communication link, schedule 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 A second set of resources corresponding to a direct communication link between the second controller and the first controller is allocated.

13. The network node of claim 12, wherein the first resource set comprises at least one of a side link resource set or an access link resource set.

14. The network node of claim 12, wherein the second set of resources comprises a sidelink resource set.

15. The network node of claim 1 , wherein the one or more processors, upon receiving an indication of the first set of parameters: determining the first parameter set, receiving a unicast message from the first controller, receiving a multicast message from said first controller, receiving a broadcast message from the first controller, or Its combination.

16. The network node of claim 1 , wherein the one or more processors, upon receiving an indication of the second set of parameters: receiving a unicast message from the first controller, receiving a unicast message from the second controller, receiving a multicast message from said first controller, receiving a multicast message from the second controller, receiving a broadcast message from the first controller, receiving a broadcast message from the second controller, or Its combination.

17. A wireless communication method performed by a network node, comprising: receiving an indication of a first set of parameters corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device comprising the network node and a first controller; receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; scheduling communications over 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 well as An indication of a resource allocation corresponding to the scheduled communication is transmitted to at least one of the first controller or the second controller based at least in part on scheduling the communication on at least one of the direct communication link or the indirect communication link.

18. The method of claim 17, wherein the first parameter set 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, resource requirements associated with the direct communication link between the IIoT device and the first controller, or Its combination.

19. The method of claim 17, wherein the second parameter set comprises at least one of: a first-hop parameter set corresponding to a direct communication link between the IIoT device and the second controller and a second-hop parameter set corresponding to a direct communication link between the second controller and the first controller.

20. The method of claim 17, wherein the second parameter set 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, resource requirements 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, resource requirements associated with the direct communication link between the second controller and the first controller, or Its combination.

21. The method of claim 17, wherein 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 to the indirect communication link metric; as well as At least one of the direct communication link or the indirect communication link is selected based at least in part on comparing the direct communication link metric to the indirect communication link metric.

22. The method of claim 21 , wherein 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 Its combination.

23. The method of claim 21 , wherein 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 Its combination.

24. The method of claim 17, wherein scheduling the communication over 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; as well as Scheduling retransmissions between the IIoT device and the first controller.

25. The method of claim 24, wherein 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 The retransmission between the IIoT device and the first controller is scheduled by allocating a second set of resources corresponding to the other of the direct communication link or the indirect communication link.

26. The method of claim 17, wherein 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 at least one of a sidelink resource set or an access link resource set.

27. The method of claim 17, further comprising periodically receiving an indication of at least one of the first parameter set, the second parameter set, or a combination thereof.

28. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a network node, cause the network node to: receiving an indication of a first set of parameters corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device comprising the network node and a first controller; receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; scheduling communications over 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 well as An indication of a resource allocation corresponding to the scheduled communication is transmitted to at least one of the first controller or the second controller based at least in part on scheduling the communication on at least one of the direct communication link or the indirect communication link.

29. A device for wireless communication, comprising: means for receiving an indication of a first set of parameters corresponding to a direct communication link between an Industrial Internet of Things (IIoT) device including the device and a first controller; means for receiving an indication of a second set of parameters corresponding to an indirect communication link between the IIoT device and the first controller via a second controller; means for scheduling communications over 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 well as Means for transmitting, based at least in part on scheduling communications over at least one of the direct communication link or the indirect communication link, to at least one of the first controller or the second controller an indication of a resource allocation corresponding to the scheduled communications.

30. The apparatus of claim 29, further comprising means for performing the method of any one of claims 18-27.

Images