Patent Description:
Wireless communication networks, such as those provided based on standards promulgated by the 3rd Generation Partnership Project (3GPP), e.g., Long Term Evolution (LTE) and New Radio (NR) (NR is also referred to as <NUM>), support at least a network node, more than one wireless device (WD), and communication signals associated with the network node and the WDs. Generally, these communication signals may include THz signals and mmWave signals which suffer from issues associated with high propagation loss and sensitivity to blockage. To overcome these issues, directional communications, such as beamforming, may be utilized at a transmitter and a receiver by establishing highly directional transmission links. To support directional communications, a set of procedures, known as beam management (BM), are defined in the 3GPP specifications for mmWave communication. The set of procedures typically include three operations: (<NUM>) P1, i.e., beam establishment; (<NUM>) P2, i.e., network node beam refinement and tracking; and (<NUM>) P3, i.e., WD beam refinement and tracking.

For P2, the network node, e.g., an NR network node (gNodeB), should request aperiodic Channel State Information (CSI) reporting by using Download Control Information (DCI), specifically, using a non-fallback DCI format 0_1. Receiving aperiodic CSI reporting successfully is critical for BM. However, sometimes CSI feedback reports are not successfully received due to Discontinuous Transmission (DTX) or Uplink Control Information (UCI) Cyclic Redundancy Code (CRC) NOK, i.e., the CRC has not passed. Typically, there are no retransmission for these failed CSI reports.

In some cases, the period of time without receiving CSI reports could be sufficiently long to result in loss of communication between the network node and the WD. In order to maintain the communication between the network node and the WD, the User Plane Control (UPC) needs to move to a transition state, known as safe mode, and to handle Uplink/Downlink (UL/DL) scheduling during this period of loss of communication. For instance, safe mode handling is required during Radio Resource Control (RRC) reconfiguration for dynamic UL waveform switching between Cyclic Prefix - Orthogonal Frequency Division Multiplexing (CP-OFDM) and Discrete Fourier Transform Spread - Orthogonal Frequency Division Multiplexing (DFTS-OFDM). More particularly, DFTS-OFDM only uses a single-layer, so that DFTS-OFDM should be configured with single-antenna port and single-layer. Waveform switching is performed via RRC reconfiguration due to the need for DCI 0_1 field reconfiguration, e.g., antenna ports, precoding information, number of layers.

Further, there is a period of time in which the WD is configured for single port, but the network node is not aware of this information until the network node receives an RRC Reconfiguration Complete message. In this period of time, DCI 0_1 used for aperiodic CSI report for BM cannot be utilized due to a mismatch in DCI 0_1 format size. Other formats, such as DCI 0_0 format, cannot be used for aperiodic CSI report request which are critical for both BM and link adaptation (LA). Accordingly, the network node does not have information about when the WD performs or completes reconfiguration. Also, the network node does not have information about how much time has elapsed from RRC Reconfiguration to the completion of RRC reconfiguration.

A straightforward option for the network node to handle UL/DL scheduling during safe mode is to suspend UL/DL scheduling at least during safe mode. However, suspension of UL/DL scheduling negatively impacts the WD, at least by impacting the WD throughputs. Suspending UL/DL for an unresponsive WD may be still necessary for the network node, e.g., when the safe mode is long, to accommodate or schedule other WDs using resources that are released as a result of the UL/DL suspension. This way, the overall throughput associated of all WDs serviced by the network node is affected in a way that may be tolerated. Suspension of UL/DL scheduling has a high risk of WD dropping among other drawbacks.

Although continuing UL/DL without aperiodic CSI reports may be an alternative, the unavailability of CSI reports during safe mode, e.g., in cases of certain prolonged periods of time and/or occurrence of beam loss, continuing UL/DL transmissions without aperiodic CSI reports could cause undesired results. Some of the undesired results may include radio link failure (RLF), e.g., triggered by the network node, Radio Link Control (RLC) delivery failure, expiration of a time indicated by a timer. In either case, suspending or continuing UL/DL, WD throughput is negatively affected.

Document <CIT> discloses a method for reporting an aperiodic channel condition in a wireless communication system. The method is performed by a terminal. The method comprises the steps of: receiving, from a base station, setting for one or more channel state information, CSI, processes including a plurality of channel state information-reference signals, CSI-RS, resources, wherein preceding is applied to each of the plurality of CSI-RS resources; receiving an aperiodic CSI report request from the base station; and transmitting, to the base station, an aperiodic CSI for a CSI process indicated by the aperiodic CSI report request, wherein, if a certain time has not elapsed after a CSI-RS resource index for the CSI process indicated by the aperiodic CSI report request is reported, the transmitted aperiodic CSI may include a CSI-RS resource index for a CSI process which has not been updated.

<NPL> discloses an overview on beam management procedure according to the current <NUM> standardization progress.

<NPL> discusses how low-frequency communication (e.g., <NUM> DSRC), onboard sensors mounted at vehicles and infrastructures, and DSRC messages (e.g., vehicle position, speed, acceleration, and path prediction) can be utilized to facilitate mm-wave V2X beam management.

<NPL> discloses evaluations of sensor-assisted multi-level codebook-based beamforming with trace-driven simulations using real mobility traces.

According to aspects of the present disclosure, there are provided a method and a network node according to the independent claims. Developments are set forth in the dependent claims.

Some embodiments advantageously provide methods and apparatuses for handling of sensor-assisted modes of wireless communication.

According to an aspect of the present disclosure, a method for a network node is provided. The network node supports communication at least with a wireless device (WD) and a sensor that is configured to provide visual information. The method includes transmitting a first signal to the WD. The first signal includes a request for the WD to transmit a report. The method further includes determining whether the network node has received the report from the WD within a predetermined period of time. If the network node has not received the report from the WD within the predetermined period of time, an alternate mode of communication with the WD is entered. The alternate mode of communication includes obtaining the visual information from the sensor, determining a fallback format for transmission based at least in part on the obtained visual information, and
transmitting a second signal to the WD using the fallback format.

In some embodiments, the method further includes determining a beam index based in part on the visual information from the sensor and determining a beam forming based on the determined beam index. The beam forming is determined to transmit the second signal to the WD further using the determined beam forming. In some other embodiments, the transmitted first signal includes a Radio Resource Control (RRC) message, the request is a Channel State Information (CSI) report request, and the report is a CSI report. In one embodiment, the alternate mode includes a User Plane Control (UPC) alternate mode. In another embodiment, the first signal to the WD is transmitted further using a Downlink Control Information (DCI) format, where the DCI format is a DCI 0_1 format. In some embodiment, the determined fallback format is a format that omits at least one communication feature in order for the network node to be able to maintain communication with the WD after entering the alternate mode, and the fallback format is determinable based at least in part on the obtained the visual information.

In some other embodiments, the determined fallback format includes at least one of a DCI 0_0 format for Physical Uplink Shared Channel (PUSCH) scheduling and a DCI 1_0 for Physical Downlink Shared Channel (PDSCH) scheduling. In one embodiment, the report is a P2 report, which is requested for network node beam refinement and tracking. In another embodiment the method further including adjusting at least a modulation coding scheme (MCS) for link adaptation (LA) after entering the alternate mode of communication, where the LA is one of an uplink (UL) LA and a downlink (DL) LA.

In some embodiments, the method further includes, after entering the alternate mode of communication, determining a current mode of link adaptation (LA) outer loop adjustment and selecting a mode of LA outer loop adjustment different from the current mode of LA outer loop adjustment. In some other embodiments, the method further includes freezing current UL and DL filters after entering the alternate mode of communication. In another embodiment, the method further includes receiving a success indicator signal from the WD and exiting the alternate mode of communication between the network node and the WD after receiving the success indicator signal from the WD.

According to another aspect of the present disclosure, a network node is provided. The network node supports communication at least with a wireless device (WD) and a sensor that is configured to provide visual information. The network node includes processing circuit that is configured to cause a transmission of a first signal to the WD. The first signal includes a request for the WD to transmit a report. The processing circuitry is further configured to determine whether the network node has received the report from the WD within a predetermined period of time. In addition, the processing circuitry is configured to, if the network node has not received the report from the WD within the predetermined period of time, enter an alternate mode of communication with the WD. The alternate mode of communication including obtaining the visual information from the sensor, determining a fallback format for transmission based at least in part on the obtained visual information, and causing a transmission of a second signal to the WD using the fallback format.

In some embodiments, the processing circuit is further configured to determine a beam index based in part on the visual information from the sensor and determine a beam forming based on the determined beam index. The beam forming is determined to transmit the second signal to the WD further using the determined beam forming. In some other embodiments, the transmitted first signal includes a Radio Resource Control (RRC) message, the request is a Channel State Information (CSI) report request, and the report is a CSI report. In one embodiment, the alternate mode includes a User Plane Control (UPC) alternate mode. In another embodiments, the first signal to the WD is transmitted further using a Downlink Control Information (DCI) format, the DCI format being a DCI 0_1 format. In some embodiments, the determined fallback format is a format that omits at least one communication feature in order for the network node to be able to maintain communication with the WD after entering the alternate mode, the fallback format being determinable based at least in part on the obtained the visual information.

In some other embodiments, the determined fallback format includes at least one of a DCI 0_0 format for Physical Uplink Shared Channel (PUSCH) scheduling and a DCI 1_0 for Physical Downlink Shared Channel (PDSCH) scheduling. In one embodiment, the report is a P2 report, the P2 report being requested for network node beam refinement and tracking. In another embodiment, the processing circuit is further configured to adjust at least a modulation coding scheme (MCS) for link adaptation (LA) after entering the alternate mode of communication, where the LA is one of an uplink (UL) LA and a downlink (DL) LA.

In some embodiments, the processing circuitry is further configured to, after entering the alternate mode of communication, determine a current mode of link adaptation (LA) outer loop adjustment and select a mode of LA outer loop adjustment different from the current mode of LA outer loop adjustment. In some other embodiments, the processing circuitry is further configured to freeze current UL and DL filters after entering the alternate mode of communication. In another embodiment, the processing circuitry being further configured to determine a success indicator signal has been received from the WD and exit the alternate mode of communication between the network node and the WD after the success indicator signal is determined to have been received from the WD.

In some embodiments, the network node performs UL/DL scheduling using DCI fallback formats, DCI 0_0 and DCI 1_0, rather than suspending UL/DL scheduling. Continuing scheduling with fallback formats allows to maintain predetermined UL/DL throughputs from a WD perspective, e.g., when the elapsed time for RRC Reconfiguration is less than a predetermined duration and/or when there is no beam loss due to WD mobility.

In some other embodiments, safe mode is handled by incorporating information, e.g., vision/visual information, obtained in part through a sensor, e.g., a camera, that is in communication with the network node and part of the network node or that may be in communication with the network node without being part of the network node. More particularly, UL/DL scheduling continues with a fallback DCI format during the safe mode. In cases of prolonged RRC reconfiguration, the information obtained from the sensor may be used for P2 tracking until receiving the first aperiodic CSI report for P2 tracking, e.g., after safe mode ends.

The safe mode handling described herein is effective at least for cases of prolonged RRC reconfiguration and allows UL/DL scheduling to continue, rather than being suspended. In addition, since BM may be based on information obtained from the sensor, WD throughput can be maintained to predetermined levels. In some embodiments, the amount of information available from a sensor or sensors, e.g., having line-of-sight information, increases when a corresponding cell size decreases. In some other embodiments, using the safe mode handling described herein allows to conserve resources that otherwise would be used in order to obtain the same information that the sensor provides or information that is similar to the information provided by the sensor.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to vision-assisted safe mode handling in wireless communication networks. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. Also, the network node may include at least one sensor, configured to detect/sense at least a condition/parameter.

The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc..

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first WD 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

In addition, it is contemplated that a network node <NUM> may be in simultaneous communication and/or configured to communicate with more than one WD <NUM> at the same time. Further, the communication system <NUM> may be configured so that any WD <NUM> may communicate with another WD <NUM> via the network node <NUM> or directly.

A network node <NUM> is configured to include a node mode unit <NUM> which is configured to provide a mode of communication that is used to communicate with at least with one WD based in part on information provided by a sensor as discussed in detail below. A wireless device <NUM> is configured to include a WD mode unit <NUM> which is configured to cause the WD <NUM> to communicate at least with the network node <NUM> using a mode of communication that is based in part on information provided by a sensor as discussed in detail below.

Example implementations, in accordance with an embodiment, of the WD <NUM> and network node <NUM> discussed in the preceding paragraphs will now be described with reference to <FIG>.

The communication system <NUM> further includes a network node <NUM> provided in a communication system <NUM> and including hardware <NUM> enabling it to communicate with the WD <NUM>.

Further, hardware <NUM> of the network node <NUM> may further include sensor <NUM>. Sensor <NUM> may collectively refer to more than one sensor, such as sensors 60a, 60b, 60c, etc. In some embodiments, sensor <NUM> is part of the processing circuitry <NUM> and/or processor <NUM> but is not limited to being part of either one or both. In some other embodiments, sensor <NUM> is not within the network node <NUM> and may be at a location that is different from the location of the network node <NUM> and directly or indirectly in communication with the network node <NUM>. Also, although sensor <NUM> is shown as being within processor <NUM>, it is contemplated that sensor <NUM> may be implemented such that a portion of the sensor <NUM> is stored in a corresponding memory, such as memory <NUM>, within the processing circuitry <NUM>. In other words, sensor <NUM> may be implemented in hardware or in a combination of hardware and software within the processing circuitry <NUM>. In some embodiments, sensor <NUM> may be at least one sensor of any one of the following sensors: vision sensors, imaging sensors, optical sensors, infrared sensors, color sensors, temperature sensors, radiation sensors, proximity sensors, pressure sensors, velocity sensors, flow sensors, position sensors, location sensors, photoelectric sensor, chemical sensors, humidity sensors, or any combination thereof. For example, sensor <NUM> may be a camera providing visual/optical information. Sensor <NUM> may be a type of sensor that provides information usable for P2 tracking, usable for beam forming, and/or usable in order to maintain communication with WD <NUM>. However, sensor <NUM> is not limited to being any of the sensors described and may be any kind of sensor. Thus, sensor <NUM> is configured to sense any condition/parameter and provide the sensed condition/parameter and/or information associated with the sensed condition/parameter.

The network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include node mode unit <NUM> configured to provide a mode of communication that is used to communicate with at least with one WD based in part on information provided by the sensor <NUM>.

The processing circuitry <NUM> may include a processor <NUM>, memory <NUM>.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include a WD mode unit <NUM> configured to cause the WD <NUM> to communicate at least with the network node <NUM> using a mode of communication that is based in part on information provided by sensor <NUM>.

In some embodiments, the inner workings of the network node <NUM> and WD <NUM> may be as shown in <FIG> and independently, the surrounding network topology may be that of <FIG>.

In some embodiments, any of the WDs <NUM> may be configured to, and/or comprises a radio interface <NUM> and/or processing circuitry <NUM> configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node <NUM>, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node <NUM>.

Although <FIG> and <FIG> show various "units" such as node mode unit <NUM>, and WD mode unit <NUM> as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart of an example method in a network node <NUM> for handling at least a mode of communication based in part on information obtained from a sensor, e.g., providing an alternate-mode of communication at least with one WD <NUM> based in part on information provided by sensor <NUM>. One or more Blocks and/or functions performed by network node <NUM> may be performed by one or more elements of network node <NUM> such as by node mode unit <NUM> in processing circuitry <NUM>, processor <NUM>, sensor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. The example method includes transmitting (Block <NUM>), such as via one or more of processing circuitry <NUM>, processor <NUM>, node mode unit <NUM>, radio interface <NUM> and communication interface <NUM>, a first signal to the WD <NUM>, the first signal including a request for the WD <NUM> to transmit a report. The example method further includes determining (Block S102), such as via one or more of processing circuitry <NUM>, processor <NUM>, node mode unit <NUM>, radio interface <NUM> and communication interface <NUM>, whether the network node <NUM> has received the report from the WD <NUM> within a predetermined period of time. Further, the example method includes, if the network node <NUM> has not received the report from the WD <NUM> within the predetermined period of time, entering (Block S104), such as via one or more of processing circuitry <NUM>, processor <NUM>, node mode unit <NUM>, sensor <NUM>, radio interface <NUM> and communication interface <NUM>, an alternate mode of communication with the WD <NUM>. The alternate mode of communication includes obtaining the visual information from the sensor <NUM>, determining a fallback format for transmission based at least in part on the obtained visual information, and transmitting a second signal to the WD <NUM> using the fallback format.

In some embodiments, the method further includes determining a beam index based in part on the visual information from the sensor <NUM> and determining a beam forming based on the determined beam index. The beam forming is determined to transmit the second signal to the WD <NUM> further using the determined beam forming. In some other embodiments, the transmitted first signal includes a Radio Resource Control (RRC) message, the request is a Channel State Information (CSI) report request, and the report is a CSI report. In one embodiment, the alternate mode includes a User Plane Control (UPC) alternate mode. In another embodiment, the first signal to the WD is transmitted further using a Downlink Control Information (DCI) format, where the DCI format is a DCI 0_1 format. In some embodiment, the determined fallback format is a format that omits at least one communication feature in order for the network node <NUM> to be able to maintain communication with the WD <NUM> after entering the alternate mode, and the fallback format is determinable based at least in part on the obtained the visual information.

In some embodiments, the method further includes, after entering the alternate mode of communication, determining a current mode of link adaptation (LA) outer loop adjustment and selecting a mode of LA outer loop adjustment different from the current mode of LA outer loop adjustment. In some other embodiments, the method further includes freezing current UL and DL filters after entering the alternate mode of communication. In another embodiment, the method further includes receiving a success indicator signal from the WD <NUM> and exiting the alternate mode of communication between the network node <NUM> and the WD <NUM> after receiving the success indicator signal from the WD <NUM>.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for vision-assisted safe mode handling in wireless communication networks, which may be implemented by the network node <NUM> and/or WD <NUM>.

In some embodiments, UL/DL scheduling is handled based in part on when the UPC enters a mode of communication. Some nonlimiting examples of the mode of communication include a safe mode, a normal state, or an alternate mode of communication. However, the mode of communication is not limited to the safe mode, the normal state, or the alternate mode of operation and may be any mode of communication. In some embodiments, the alternate mode may be a safe mode. Thus, although discussion below refers to the "safe mode", it is understood that embodiments are not limited to "safe mode" and can be other alternate modes of communication.

The network node <NUM> may move into the alternate, e.g., safe mode, upon sending a modification signal, e.g., an RRC message, to the WD <NUM>. Once the network node <NUM> is in safe mode, the network node <NUM> may perform any one of the following actions:.

The network node <NUM>, e.g., via the UPC protocol, may move into the normal state, after receiving a success indicator signal. When in the normal state, the network node <NUM> may perform any one of the following actions:.

In some embodiments, the network node <NUM> may move into or enter the alternate mode of communication. The alternate mode of communication may be a mode of communication that allows the network node <NUM> and the WD <NUM> to maintain communication without suspending UL/DL and/or by using information obtained at least from sensor <NUM>. The alternate mode may be a mode of communication that is based on a User Plane Control (UPC) protocol. In some other embodiments, the alternate mode of communication is a mode of communication that is based in part on the safe mode and/or the normal state. In a nonlimiting example, the network node <NUM> may enter the alternate mode of communication with the WD <NUM> after entering safe mode, and the network node <NUM> may perform any of one the steps described above for each of the safe mode and the normal state. However, the network node <NUM> is not limited to entering the alternate mode of communication after entering the safe mode and may enter the alternate mode at any time. Further, the network node <NUM> is not limited to performing the steps described for each of the safe mode and the normal state and may perform other steps.

Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them.

Claim 1:
A method for a network node (<NUM>) supporting communication at least with a wireless device, WD, (<NUM>) and a sensor (<NUM>) configured to provide visual information, the method comprising:
transmitting (S100) a first signal to the WD (<NUM>), the first signal including a request for the WD (<NUM>) to transmit a report;
determining (S102) whether the network node (<NUM>) has received the report from the WD (<NUM>) within a predetermined period of time; and
if the network node (<NUM>) has not received the report from the WD (<NUM>) within the predetermined period of time, entering (S104) an alternate mode of communication with the WD (<NUM>), the alternate mode of communication including:
obtaining the visual information from the sensor (<NUM>);
determining a fallback format for transmission based at least in part on the obtained visual information; and
transmitting a second signal to the WD (<NUM>) using the fallback format.