Beam width control

The method and apparatus dynamically adjust millimeter-wave antenna beamwidth based on data rate and location to address the inefficiencies of static beam control in smart factories, improving connectivity and resource utilization.

JP2026539071APending Publication Date: 2026-11-19UNIVERSITY OF MELBOURNE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2026525280
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-10-27
Filing Date
2024-10-25
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Conventional beam control methods are static and insufficient for dynamic environments like smart factories, where robots and IoT devices require high bandwidth and data rates that change over time, leading to insufficient coverage and inefficiency in next-generation wireless communication systems.

Method used

A method and apparatus for controlling the beamwidth of a millimeter-wave antenna using a lens and actuation arrangement to dynamically adjust the beamwidth based on data rate, location, and task requirements, enabling flexible and dynamic beam control.

Benefits of technology

Dynamically adjusts beamwidth to meet varying data rate and connectivity needs, enhancing coverage and efficiency in smart industry environments by optimizing resource allocation and reducing power consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026539071000001_ABST
    Figure 2026539071000001_ABST
Patent Text Reader

Abstract

A device for controlling the beamwidth of a millimeter-wave (mmW) device, comprising a lens, an mmW antenna, and an actuation arrangement operably connected to the lens and the mmW antenna, wherein the actuation arrangement is configured to change the beamwidth of the mmW antenna based on a control signal.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to antenna beam control. More specifically, embodiments of the present disclosure relate to a method and apparatus for controlling the beamwidth of a millimeter wave antenna. BACKGROUND ART

[0002] Advances in autonomous systems have increased the need for next-generation industrial wireless communication systems. Such systems provide high bandwidth (>10 Gb / s) and / or data rates and / or connectivity for large-scale heterogeneous connections (>10,000) to alleviate wireless bottlenecks of current technologies and maximize productivity, provide ultra-fast response times for large-scale data collection, upload to real-time analysis systems, and decision making to minimize deadlocks and idle time, and / or provide enhanced privacy and security where data sovereignty and independent network management are essential.

[0003] Conventional beam control methods may use static lenses, phase shifting, aperture synthesis, frequency selective antennas, and the like.

[0004] In the newly and rapidly growing smart industry, vendors and network providers tend to use proven conventional approaches, such as large antenna arrays equipped with beamforming modules.

[0005] These methods are static solutions and are insufficient to address the dynamic requirements in smart industry operating environments (such as smart factories, smart warehouses, smart logistics, and smart processing) where robots may require high bandwidth and / or data rates in real time and / or on demand. For example, analog beamforming and beam steering only provide a focused beam at a specific angle. While this may be programmable, it does not solve the problem of insufficient coverage. In other words, a more flexible and dynamic solution is needed when both data rate utilization and the number of connected devices can change over time.

[0006] Currently available commercially available beam steering and beamforming systems and methods employ signal constructive techniques and phase shifters that use antenna arrays with expensive, power-hungry beam control chipsets. These systems and methods are power-hungry, costly to build, and unsuitable for use in end devices such as robots communicating with base stations in smart industry environments. Furthermore, these techniques result in static beams.

[0007] In addition, most current systems and methods focus on directional beam steering rather than beam focusing. Beam steering alone may be insufficient in applications that extend beyond conventional communication environments, such as next-generation smart industries where a large number of high-bandwidth / high-data-rate devices are connected to the network. In one example, thousands of autonomous robots, machines, and Internet of Things devices in a smart factory may transmit gigabytes of data for real-time analysis and decision-making to maximize productivity and safety. In another example, one or more robots, machines, or IoT devices may transmit gigabytes of data when performing complex tasks and / or tasks that require high data rates.

[0008] Furthermore, existing lens systems are primarily designed for radar, satellite applications, and fixed wireless communications, which differ from high-data-rate, dynamic mobile wireless applications such as smart industries where autonomous robots and machines require high data-rate and low-latency connectivity for collaborative production.

[0009] It is desirable to overcome or improve one or more of the aforementioned drawbacks, or at least provide a useful alternative. [Overview of the Initiative]

[0010] According to one embodiment, an apparatus is provided for controlling the beamwidth of a millimeter-wave (mmW) device, the apparatus comprising a lens, an mmW antenna, and an actuation arrangement operably connected to the lens and the mmW antenna, the actuation arrangement being configured to change the beamwidth of the mmW antenna based on a control signal.

[0011] In another embodiment, a method is provided for controlling the beamwidth of a millimeter-wave (mmW) antenna, the method comprising: at a base station receiving a connection request from an end device at a certain location; determining the beamwidth of the base station's mmW antenna and the data rate associated with the connection request from the end device; and changing one or both of the beamwidth of the base station's mmW antenna and the beamwidth of the end device's mmW antenna based on the determined data rate and location.

[0012] The beamwidth of a mmW antenna may be changed by increasing the beamwidth when the data rate is lower than a predetermined value.

[0013] The beamwidth of a mmW antenna may be changed by reducing the beamwidth when the data rate is higher than a predetermined value.

[0014] A connection request may be initiated or received when the first and second devices are in a common work zone. In some embodiments, a connection request may be initiated or received when the end device is activated in a work zone associated with a base station.

[0015] The data rate associated with the connection request may be the data rate required for a first or second device to perform a task in an automated factory.

[0016] The data rate associated with a connection request may be determined based on the base station's resource allocation. Resource allocation may include time-domain allocation and / or frequency-domain allocation.

[0017] In some embodiments, the beamwidth of the mmW antenna may be varied based on the priority of the task associated with the connection request.

[0018] In some embodiments, the beam width of the mmW antenna may be varied based on the distance of the end device from the boundary of the work zone.

[0019] In some embodiments, the beam width of the mmW antenna may be varied by changing the distance between the mmW antenna and the lens.

[0020] In some embodiments, the beamwidth of the mmW antenna may be varied based on a link power budget defined for the end device.

[0021] Preferred embodiments of the present disclosure are described below with reference to the accompanying drawings, with reference only to non-limiting embodiments. [Brief explanation of the drawing]

[0022] [Figure 1A]is a block diagram of a communication system in an automated factory. [Figure 1B] is a schematic diagram of a simplified exemplary configuration of an automated factory. [Figure 2] is a flowchart of a method for controlling a beam of a millimeter wave (mmW) antenna associated with a base station communicating with an end device in the automated factory of FIG. 1A and FIG. 1B. [Figure 3] is a schematic diagram of an exemplary configuration of a shop floor of an operating automated factory. [Figure 4] is a block diagram of an apparatus for controlling the beam width of a millimeter wave (mmW) device. [Figure 5] is a sketch of a perspective view of an exemplary arrangement of the mmW antenna and the lens of the apparatus of FIG. 4. [Figure 6] is a diagram of a polar coordinate radiation pattern as an example of a mmW lens when operating at a frequency of 27 GHz. [Figure 7] is a graph of 3 dB beam width (angle in degrees) versus the distance (in cm) between the lens and the mmW antenna when operating at 24 GHz. [Figure 8] is a graph of 3 dB beam width (angle in degrees) versus the distance (in cm) between the lens and the mmW antenna when operating at 26 GHz. [Figure 9] is a graph of 3 dB beam width (angle in degrees) versus the distance (in cm) between the lens and the mmW antenna when operating at 28 GHz. [Figure 10] is a graph of 3 dB beam width (angle in degrees) versus the distance (in cm) between the lens and the mmW antenna when operating at 30 GHz. [Figure 11] is a graph of 3 dB beam width (angle in degrees) versus the distance (in cm) between the lens and the mmW antenna when operating at 32 GHz. [Figure 12] is a block diagram of an exemplary radio frequency (RF) transmitter and receiver operating at 27 GHz. [Figure 13A]This graph shows the 3dB beamwidth (angle in degrees) for lens reconstruction settings when operating at frequencies of 25GHz, 26GHz, and 27GHz. [Figure 13B] This graph shows the 6dB beamwidth (angle in degrees) for lens reconstruction settings when operating at frequencies of 25GHz, 26GHz, and 27GHz. [Figure 14A] This graph shows the 3dB beamwidth (angle in degrees) for lens reconstruction settings when operating at frequencies of 28GHz, 29GHz, and 30GHz. [Figure 14B] This graph shows the 6dB beamwidth (angle in degrees) for lens reconstruction settings when operating at frequencies of 28GHz, 29GHz, and 30GHz. [Modes for carrying out the invention]

[0023] Figure 1A is a block diagram of a communication system 100A in an automated factory according to an embodiment of the present disclosure. The automated factory may be a logistics and warehousing facility or a manufacturing facility for large-scale production of goods, including but not limited to automotive, electrical and electronic, metal and machinery, chemical, food and beverage, pharmaceutical and cosmetic products. In a preferred embodiment, the automated factory is a smart factory with interconnected machinery, including robots, configured to share data and enhance automation and manufacturing flexibility. System 100A comprises a base station 102 and a plurality of end devices 106a, 106b. The base station 102 may be associated with one or more work zones 108 and may be configured to manage specific tasks in a particular work zone. In some embodiments, a shop floor may have a plurality of work zones. The base station 102 includes a millimeter-wave (mmW) antenna 104 configured to communicate with the end devices 106a, 106b. In various embodiments, it will be understood that system 100A may have one or more end devices 106 having different data rate requirements, such as having two end devices 106a and 106b within the work zone 108 as shown in Figure 1A. Furthermore, end devices 106a and 106b may require different data rates for different time periods based on the tasks assigned to the end devices.

[0024] In some embodiments, the end devices 106a, 106b may be stationary machines (e.g., assembly lines). In another embodiment, the end devices 106a, 106b may be mobile machines (e.g., transport machines that move one or more articles or parts from one point to another within a shop floor). In yet another embodiment, the end devices 106a, 106b may be stationary robots (e.g., robots that have a predetermined fixed position near an assembly line and are assigned the task of assembling parts of an article). In yet another embodiment, the end devices 106a, 106b may be mobile robots or cobots (i.e., collaborative robots mounted on autonomous mobile robots with machine vision that move around the shop floor and perform specific tasks, such as, but not limited to, custom assembly, machine tending, quality inspection, and moving tools or accessories between stationary machines and / or stationary robots using an articulated robotic arm). It will be understood that an automated factory may have any combination of the different types of end devices 106 described above, for example, working together for the intended factory application, as shown in Figure 3. In an exemplary embodiment, the automated factory may be a warehouse or logistics facility and may include autonomous mobile robots (AMRs) for locating, tracking, and moving inventory within it.

[0025] Figure 1B is a schematic diagram of a simplified exemplary configuration of the automated factory 100B of Figure 1A according to an embodiment of the present disclosure. The shop floor of factory 100B comprises a base station 102 including a mmW antenna 104, a base station 110 including a mmW antenna 112, and a plurality of end devices 106a, 106b, 106c, 106d, 106e, and 106f. The mmW antenna 104 is configured to communicate with the end devices 106a, 106b, and 106c. The mmW antenna 112 is configured to communicate with the end devices 106d, 106e, and 106f. The base stations 102, 110, and the plurality of end devices 106a, 106b, 106c, 106d, 106e, and 106f operate within a work zone 108 with different data rate requirements. In some embodiments, one or more of the end devices 106a, 106b, 106c, 106d, 106e, and 106f may require different data rates for different time periods based on the tasks assigned to the end device. In embodiments, the end devices 106a, 106d, 106e, and 106f may be stationary machines, while the end devices 106b and 106c may be mobile machines, robots, or cobots. Each end device comprises an mmW module containing a mmW antenna. In Figure 1B, the mmW antenna 104 of the base station 102 is configured to communicate with the mmW module 114a associated with end device 106a, the mmW module 114b associated with end device 106b, and the mmW module 114c associated with end device 106c. The mmW antenna 112 of base station 110 is configured to communicate with mmW module 114d associated with end device 106d, mmW module 114e associated with end device 106e, and mmW module 114f associated with end device 106f. Further details regarding the mmW modules (or mmW devices) are provided below with reference to Figure 4.

[0026] Figure 2 is a flowchart of a method 200 according to embodiments of the present disclosure for controlling the beamwidth of a millimeter-wave (mmW) antenna associated with a base station communicating with each end device in the automated factory of Figure 1B. Method 200 comprises the base station 102 receiving a connection request from an end device 106a located at a certain location (step 202). In embodiments, the connection request is initiated / received when the end device 106a is activated in a work zone 108 associated with the base station 102. In one embodiment, the end device 106a may be activated upon entry into the work zone 108. In another embodiment, the end device 106a may be activated by a user or a factory manufacturing execution module (details of which will be described later). In some embodiments, the end device 106a may be activated automatically or manually. The end device 106a may be activated when the device is required to perform a task in the factory. Thus, the connection requests received by the base station 102 may be based on tasks performed by the end device 106a. Method 200 further comprises determining the beamwidth of the millimeter-wave (mmW) antenna of base station 102 and the data rate associated with the connection request from end device 106a (step 204), and changing one or both of the beamwidth of the base station's mmW antenna and the end device's mmW antenna based on the determined data rate and location (step 206).

[0027] This disclosure may address one or both of the challenges of high data rates and a large number of connections, depending on the needs of end devices connected to a base station. An exemplary diagram of a smart factory shop floor configuration is depicted in Figure 1B. The shop floor may consist of both stationary and mobile robots and machines with varying data rate requirements. These robots and / or machines may require different data rates for different time periods based on the applications or tasks they are performing during industrial operation.

[0028] Figure 3 shows an exemplary configuration 300 of a shop floor in an operational automated factory. The automated factory comprises a manufacturing execution module 302 (or, in other words, a manufacturing execution system (MES) module), a network control module 304, a base station A306 communicably connected to a mmW antenna 306a, a base station B308 communicably connected to a mmW antenna 308a, a plurality of work zones 312, 314, 316, 318, 320, 322, and a plurality of end devices 310, 324, 326, 326, 330, 332, 334, 336, 338, 340, 342. It will be understood that each base station may have one or more work zones associated with it, and end devices within one or more work zones may be connected to their respective base stations. In some embodiments, each work zone may have a plurality of base stations. Each end device is equipped with an mmW module containing an mmW antenna for communicating with the mmW antenna 306a of the base station 306 (for example, end device 310 has an mmW module 310a). The mmW module may further include a lens and actuation arrangement, the details of which will be described later.

[0029] The manufacturing execution module 302 may perform one or more of the following: monitoring and controlling the production process on the shop floor; tracking and recording the conversion from raw materials to finished products in real time by controlling and monitoring end devices such as robots, machines, sensors, and operators; and providing real-time visibility into production operations.

[0030] The network control module 304 may be configured to run network management software to perform one or more of the following: tracking all devices connecting to the network via different base stations; orchestrating data rates in real time based on the requirements of end devices; and tracking where and / or tasks each end device is performing to ensure network consistency, continuity, and availability.

[0031] In one embodiment, the end device 310 may be activated in the work zone 312 of base station A306 at time t+0. In another embodiment, the end device 310 may be activated when it enters the work zone 312 at time t+0. In yet another embodiment, the end device 310 may be activated when it is assigned a task. The end device 310 may be assigned a first task by the factory's manufacturing execution module 302. When a task is assigned to the end device 310, one or more pieces of information, such as the ID of the end device 310, the destination coordinates and / or speed of the end device 310, and the data rate and computational requirements values ​​for the end device 310 to perform the task at its current location, while traveling to (in transit) to the destination, and at the destination, may be collected and stored in the network control module 304. The manufacturing execution module 302 controls the task assignment and reconfiguration of end devices in the factory. The network control module 304 stores the locations of all end devices in the factory. In one embodiment, the first task may require a first data rate with a moderate uplink data rate and a low downlink data rate.

[0032] To establish a connection between base station A306 and end device 310, the following actions may be performed. Establishing a connection between base station A306 and end device 310 may also refer to establishing a connection between the millimeter-wave antenna 306a of base station 306 and the mmW module 310a of the end device, where the mmW module 310a of the end device is understood to include an mmW antenna.

[0033] The end device 310 may listen for network control channel beacons and any network messages being broadcast to them. The end device 310 then sends a connection request to base station A306. In an embodiment, the connection request may include at least one or more of the following: data rate requirements, duration of connection, task information (e.g., task type, duration, priority), and the location of the end device 310 within the work zone 312.

[0034] Next, base station A306 determines the beamwidth of its mmW antenna 306a. Base station A306 determines the data rate associated with the connection request from end device 310. In some embodiments, end device 310 may notify base station A306 of the required data rate and the duration for which that data rate is required, corresponding to the task performed by end device 310. Network control module 304 may then notify this information when a connection request is received at base station A306. Over time, network control module 304 may have an updated table of information related to all individual tasks performed on the shop floor, such as task information or IDs with corresponding data rates and time periods. In some other embodiments, manufacturing execution module 302 may share task information / IDs and data rate requirements with network control module 304, and the task information may be validated against the information from manufacturing execution module 302 when a connection request is received from end device 310. The data rate may include the uplink data rate and downlink data rate required by the end device 310. In an embodiment, the data rate may include the uplink data rate and downlink data rate required by the end device 310 to perform the first task in the work zone 312. The base station A306 then changes the beamwidth of its mmW antenna based on the determined data rate and location.

[0035] In an exemplary embodiment, if the network control module 304 can support a bandwidth of 400 MHz and the end device 310 requires a bandwidth of 200 MHz to perform a high-bandwidth, high-data-rate task, the end device may initiate a connection request with the corresponding "high" data rate, for example, 1 Gb / s (QAM64 modulation scheme with standard coding (approximately 5.5 bits / Hz including standard overhead)). The exemplary high-bandwidth, high-data-rate task may be a real-time 3D machine vision application. Such a "high" data rate may correspond to a bandwidth of approximately 150 MHz with QAM256 modulation. If the end device 310 requires a moderate bandwidth of approximately 20 MHz to approximately 100 MHz (depending on application needs and communication link quality), for example, it may initiate a connection request with a "moderate" data rate of 20 Mbps to 500 Mbps. If the spectral efficiency is in the range of 1 to 5, a “moderate” data rate can range from 20 Mbps (e.g., 20 MHz at 1 bps / Hz) to 500 Mbps (e.g., 100 MHz at 5 bps / Hz). If the end device 310 requires a lower bandwidth of about 1 MHz to about 20 MHz, it may initiate a connection request with a “low” data rate of 1 Mbps to 100 Mbps, for example. If the spectral efficiency is in the range of 1 to 5, a “low” data rate can range from 1 Mbps (e.g., 1 MHz at 1 bps / Hz) to 100 Mbps (e.g., 20 MHz at 5 bps / Hz).

[0036] An example of a standard channel quality index table, including modulation scheme, code rate, and spectral efficiency, is shown below.

[0037] [Table 1]

[0038] Beam width change Varying the beamwidth of the mmW antenna 306a of base station A306 based on the determined data rate involves either increasing the beamwidth when the determined data rate is lower than the current support value, or decreasing the beamwidth when the determined data rate is higher than the current support value. The current support value will be explained in more detail later.

[0039] Base station A306 may determine a new beamwidth based on i) the determined number of connections, ii) the sum of all determined bandwidth requirements, and / or iii) the determined number of current tasks at time t and t+1.

[0040] In one embodiment, base station A306 may determine its resource allocation by querying a resource map stored within the base station. The resource map is a time (n) × frequency (m) domain multiplexing matrix map, where "n" is the number of time domain slots and "m" is the number of frequency domain slots in a single transmission window. By querying the resource map, base station A306 may determine the number of time domain multiplexing blocks allocated to one or more end devices that are in an active communication state, and the number of frequency domain multiplexing blocks allocated to one or more end devices that are in an active communication state. When determining whether base station A306 has sufficient resources to process connection requests and allocate resources to end device 310, it may check the number of active devices connected within the work zone 312.

[0041] Updating the beam profile To change the beamwidth of the mmW antenna at base station A306, base station A may look up a pre-calculated table that references the beamwidth in degrees and the settings of the actuators connected to the mmW antenna and lens. The pre-calculated table may be based on test values ​​from, for example, Figures 7 to 11 and may contain information such as 3dB beamwidth, distance between the center of the lens and the near plane of the mmW antenna, modulation (e.g., 16QAM, 64QAM), and code rate.

[0042] Figure 4 is a block diagram of an apparatus 400 for controlling the beamwidth of a millimeter-wave (mmW) device according to an embodiment of the present disclosure. The apparatus 400 includes a lens 402, an mmW antenna 404, and an actuation arrangement 406 operably connected to the lens 402 and the mmW antenna 404. The actuation arrangement 406 is configured to change the beamwidth of the mmW antenna 404 based on a control signal 408. In embodiments, the mmW device may be communicably coupled to a first device (not shown), such as an end device 310 in Figure 3, which is configured to communicate with a second device (not shown), such as a base station A306 in Figure 3. The control signal 408 may be a connection request transmitted between the first device and the second device, for example, a connection request transmitted from the end device 310 to the base station A306. The control signal 408 may include a data rate associated with the connection request. The control signal 408 may further include locations for one or both of the first and second devices.

[0043] The actuation configuration 406 may be configured to change the beamwidth of the mmW antenna by increasing the beamwidth when the data rate is below a predetermined value (for example, when many end devices are connected to the base station but the data rate / bandwidth requirements per end device are low). The actuation configuration 406 may be configured to change the beamwidth of the mmW antenna by decreasing the beamwidth when the data rate is above a predetermined value (for example, when there are few end devices connected to the base station but the data rate / bandwidth requirements per end device are high).

[0044] A connection request may be initiated when the first and second devices are in a common work zone. Details of initiating a connection request are described above. In embodiments, the data rate associated with a connection request may be the data rate required for the first or second device to perform a task in an automated factory. For example, in a smart factory environment, a large amount of data may need to be generated from an end device, such as a robot, for a particular task and transmitted uplink to a base station. In another embodiment, the base station may want to transmit a large volume of data downlink to an end device for another task. The data rate associated with a connection request may be determined based on time-domain resource allocation and / or frequency-domain resource allocation, as described above.

[0045] The actuation configuration 406 may be configured to vary the beamwidth of the mmW antenna 404 based on task priority, for example, a high data-rate task requiring uplink data transmission from an end device to a base station may have a higher priority than a low data-rate task assigned to another end device or the base station's current task. In other embodiments, task priority may be based on one or more of the task duration, task type, and the location of the end device relative to the base station.

[0046] Varying the beamwidth may be based on the distance of the first and / or second devices from the boundary of a common work zone, as described above. Varying the beamwidth further comprises varying the distance between the mmW antenna 404 and the lens 402. Varying the beamwidth may further be based on a link power budget defined for the first and / or second devices, as described elsewhere in this disclosure.

[0047] Figure 5 is a perspective view of an exemplary arrangement of a mmW device (e.g., associated with a base station A306) comprising a mmW antenna 404, a lens 402, and an actuation arrangement 406 according to an embodiment of the present disclosure. The actuation arrangement 406 may include an actuator (e.g., linear, rotary) connecting the lens 402 to the mmW antenna 404. In various embodiments, the lens 402 is a convex lens. In some embodiments, the lens 402 is a mmW lens. In embodiments, the lens 402 may have dimensions of 80 mm × 28 mm × 76 mm. In some embodiments, the lens 402 may be made of high-density polyethylene. In various embodiments, the mmW antenna 404 is a patch antenna (e.g., a 2 × 2 patch antenna, a 4 × 4 patch antenna). A stepper motor or the like may then be triggered by the base station A306 to perform actuation of the actuator 406, thereby changing the distance between the mmW antenna 404 and the lens 402 to adjust the beam focus and thereby change the beam width. The distance between the mmW antenna 404 and the lens 402 may be increased to narrow the beamwidth or decreased to widen it. The distance between the mmW antenna 404 and the lens 402 may also be the distance between the near-plane of the mmW antenna 404 and the center of the lens 402. The transmit and receive power levels may be adjusted according to a link power budget table. The link power budget table may consist of standard radio frequency (RF) parameters such as transmitter power (dBm), gain by adjusting the beamwidth, carrier frequency, distance, propagation loss, receiver antenna gain, received power, bandwidth, noise figure, signal-to-noise ratio (SNR), and data rate.

[0048] Figure 6 shows an exemplary polar radiation pattern of a mmW lens operating at a frequency of 27 GHz. Figures 7–11 illustrate 3 dB beamwidth (angle in degrees) versus distance (in cm) between the lens and the mmW antenna, according to embodiments of the present disclosure, when operating at 24 GHz, 26 GHz, 28 GHz, 30 GHz, and 32 GHz, respectively. It will be understood that the distance between the lens and the mmW antenna refers to a measured on-axial distance from the near-plane of the mmW antenna to the center of the lens. It will be further understood that the curves shown in Figures 7–11 are merely examples and may vary based on one or more of the lens material and / or lens shape.

[0049] In the exemplary embodiment shown in Figure 9, when operating at 28 GHz, the currently supported value for the antenna may be 30 degrees (3 dB beamwidth), and the distance from the center of the lens to the near-plane of the antenna may be 8 cm. Due to increasing bandwidth or data rate requirements of the end device, the beamwidth may be dynamically changed to 20 degrees at 28 GHz, and the distance from the center of the lens to the near-plane of the antenna may be 15 cm.

[0050] Beam width ramping The system may linearly or exponentially ramp the beamwidth at a set rate to assist in re-establishing a high-capacity link and realigning the transmitter and receiver between base station 306 and end device 310. The system may ramp the beamwidth by iterating over the (previously described) pre-calculated table for slow (linear) and fast (exponential) scanning of the beamwidth. If the connection between base station A306 and end device 310 is re-established with a beamwidth value wider than the current beamwidth value, an unplanned failure event may be logged to the local storage of base station A306, the unplanned failure event may be advertised on an available route / channel (e.g., a multi-hop route via another base station or repeater using standard routing techniques), and the beamwidth ramp timer may be triggered. If the beamwidth ramp timer overflows, a message may be sent to the transmitter to negotiate the beam profile, i.e., base station A306 may check whether the beamwidth now has sufficient coverage, and if not, the beamwidth ramp timer may be triggered again to perform ramping until sufficient coverage is achieved.

[0051] If there is one or more end devices 310 in the work zone 312, or if there is one or more end devices 310 connected to base station A306, base station A may perform a transmitter multi-power event (described in more detail below in "Event 1 - Base Station Transmitter Multi-Power"). Base station A306 may perform transceiver scheduling (described in more detail below in "Event 2 - Transceiver Scheduling") to allocate time-domain and frequency-domain blocks to the end devices 310. The resource map and beamwidth table associated with base station A306 may be updated and transmitted to the network control module 304. The network control module 304 stores the updated resource map and beamwidth table of all base stations in the factory connected to the module. In an embodiment, the network control module 304 may update the resource map and beamwidth table of all base stations in accordance with any changes in the resource map and / or beamwidth table of any of the connected base stations, and may therefore be updated at an ad-hoc time or event-based time. In another embodiment, updates in the network control module 304 may be performed at a pre-selected / fixed time interval. The network control module 304 may send the updated information to the manufacturing execution module 302 for recording and verification.

[0052] Upon completion of the operations described above, the end device 310 connects to base station A306 with a moderate uplink data rate and a low downlink data rate (indicated by dashed links in Figure 3). When the connection request period expires, or when new data rate requirements are determined by the end device 310, a new connection request may be sent to base station A306, and the operations described above may be repeated.

[0053] Once the end device 310 completes a first task in work zone 312 (shown as the first production line in the embodiment of Figure 3), the manufacturing execution module 302 may assign the end device 310 a second task. The second task may need to be performed in another work zone 316 on the factory shop floor. As the end device 310 moves to the new work zone 316, the above-described operations may be triggered. However, assuming that the end device 310 is not performing any other tasks assigned to it while moving from work zone 312 to work zone 316 via work zone 314 at time t+1, periodic link status updates and handovers (e.g., in milliseconds) are required. With each link status update, based on either the location of the end device 310 reported to base station A306, or the link signal quality between the end device 310 and base station A306, base station A306 will determine that the end device 310 is moving away from it. Similarly, based on either the location of the end device 310 reported to base station B308, or the link signal quality between the end device 310 and base station B308, base station B308 will determine that the end device 310 is approaching it. During travel between work zones, scheduled transceiver failure events and unscheduled receiver failure events may occur (described in more detail below in "Event 3 - Scheduled Transceiver Failure (Deterministic / Predictable Event)" and "Event 4 - Unscheduled Receiver Failure (Unpredictable Event)"), and notification messages may be sent to all affected end devices in the factory.

[0054] The data rate of the end device 310 may be monitored in real time from the start to the end of a specific task, or from the start to the end of a connection, and may be analyzed based on predictive analysis for improved consistency and continuity.

[0055] In an embodiment, the beamwidth may be varied based on the priority of the task assigned to the end device 310. In an exemplary embodiment, the second task assigned to the end device 310 may be a critical or high-priority high-data-rate task requiring a high uplink data rate and a moderate downlink data rate. Thus, when the end device 310 arrives at the work zone 316 (e.g., the second production line) at time t+2, the end device 310 may send a connection request to the base station B308 and perform the operations described above to establish a connection between the end device 310 and the base station B308. Establishing a connection between the base station B308 and the end device 310 may also refer to establishing a connection between the millimeter-wave antenna 308a of the base station 308 and the mmW module 310a of the end device 310, where the mmW module 310a of the end device is understood to include a mmW antenna. Base station B308 will perform further priority scheduling events, as will be described in more detail later in "Event 5 - Priority Scheduling," and base station B308 and end device 310 may be connected via ultrafast connectivity, i.e., high uplink data rates and moderate downlink data rates (indicated by dashed-dotted links in Figure 3).

[0056] event One or more of the following events may dynamically trigger the rescheduling of resource allocation and beam width configuration.

[0057] Event 1 - Base station transmitter with multiple power outputs The transmit beamwidth of base station A306 may be reduced or increased to ensure that end device 310, along with any other end devices associated with base station A306, is covered by the specified (previously stated) link power budget per end device and based on the data rate requirements of end device 310. The variation in beamwidth may be limited by the maximum support distance across all active end devices in the work zone from which end device 310 transmits connection requests (seeking the minimum specified link power budget).

[0058] To find the optimal support distance, the distance of all end devices from the boundary of the work zone, defined as the maximum coverage area of ​​the base station, may be determined. In embodiments, such a determination may be made by base station A306 by one of the following methods: using a camera; a method based on location reported to base station A306 by the end device 310 (which may be more accurate than using a camera, and the network control module 304 may track location information from all connected devices); or a method by standard triangulation calculation based on the link power budget.

[0059] The minimum beamwidth span weighting may be calculated based on the distance of the end device closest to the boundary of each work zone (i.e., the base station coverage). In the embodiment, if the end device is located at the boundary of work zone 312, the minimum beamwidth span weighting = 1. If the furthest distance between any two end devices in a work zone is half the diameter of the work zone, the weighting = 0.5. Thus, the beamwidth may be varied by adjusting to a weighted beamwidth profile as follows: Weighted beamwidth profile = beamwidth × weight (1) Here, (beam width × weight > 0) and (link budget ≥ min|node link budget list|).

[0060] The "node link budget list" may be a predefined link budget that is application-dependent. Beam width updates may be notified to the affected nodes. The transmit beam may then be updated as described above.

[0061] Event 2 - Transceiver Scheduling Transceiver scheduling classifies transceivers into two classes: (1) reallocated and (2) unallocated. Base station A306 may search for time-domain reallocations in the schedule list based on the resource map, including details of currently connected end devices, data rate requirements, which time slots and frequency subcarriers are allocated within the resource map, and priority classes. If a full allocation is not available, base station A306 may search for a partial allocation with an equivalent or reduced bit rate resulting from an additional allocation in the frequency domain. If the partial allocation search is successful, the reallocation of time-domain and frequency-domain resources may be notified to end device 310 and other affected end devices. If a full allocation is available, the system marks the event as reallocated. The reallocation of time-domain resources may be notified to end device 310 and other affected end devices. However, if neither a full nor a partial allocation is available, the expected channel bitrate loss may be notified to end device 310 and other affected end devices, and the event may be marked as unallocated. The predicted channel bitrate loss may be a value provided to the end device 310 by base station A306 to indicate a time period (ms) during which transmission is not permitted. If the time period is 1 ms and the data rate requested by the end device 310 is 100 Mbps, the end device 310 will need to buffer 100 kbits until the next transmit slot. If an event is marked as unassigned, the end device 310 will not receive bandwidth for transmission for a certain period. Therefore, the end device 310 may have to rely on its onboard memory buffer to store the message until the next assigned transmit slot. Since the transmit cycle is within milliseconds, this may not result in packet loss. The end device 310 may acquire a slot within the same or the next few cycles.Event 5 should have been triggered if the task had a high priority and strict latency requirements. In extreme scenarios where total network bandwidth < total requested bandwidth, packet loss may occur, and priority transmission may be given to more end devices performing more critical tasks.

[0062] Event 3 - Scheduled transceiver failure (deterministic / predictable event) Predicted or known scheduled fault events may be triggered when an end device 310 intentionally enters an area of ​​no service, when a known entity interrupts the beam, or when a scheduled fault message is received from a base station. This is because the event is scheduled, and the network control module 304 may have information about all mobile robots throughout the factory, as previously mentioned. A known entity may be a known robot, worker, or automatic door that blocks the way (i.e., obstructs the line of sight between the mmW antenna and another robot) because there is no other alternative route to take. However, such faults may be temporary or, in the rare case, semi-permanent, when a robot (known entity) needs to interrupt or suspend other end devices to perform its assigned task. The fault may mean the disruption of an existing link configuration. For example, a transmit beam from base station A306 may be interrupted by another mobile end device moving in its path, thereby blocking part of the beam. Alternatively, the failure may mean that the end device 310 has moved to an area without service, or that fixtures such as walls, shelves, or other obstacles have blocked the beam.

[0063] Therefore, a scheduled failure is a planned or known interruption, meaning that a moving end device 330 traveling along a known and planned route may have no choice but to interrupt other machines / robots (or its own beam) due to the factory layout or when the end devices must pass each other.

[0064] Scheduled faults have two classes: (1) reallocated and (2) unallocated. Base station A306 may have a scheduler configured to optimize the movement of scheduled fault events from the unallocated class to the reallocated class in order to maintain the channel bitrate. This may be achieved by reallocating the transmission period to a fault-free period in the time-domain multiplexing sequence, or, if an equivalent bitrate allocation in the time domain is not available, by a series of time-domain and frequency-domain multiplexing slots. If additional frequency-domain slots are available in a shorter fault-free time period, this may result in no change or a reduced channel bitrate. If reallocation is not available, the event remains in the unallocated class, in which case the channel bitrate to end device 310 is reduced to 0 as expected during this period of the scheduled fault, and the scheduler of base station A306 is free to reallocate this time-domain multiplexing slot to another end device.

[0065] Overlapping or duplicate scheduled events will be triggered based on the last updated message, which will go through message integrity and message authentication and priority lookup in a scheduled fault access control list stored in the local storage of base station A306. The scheduled fault access control list may be used by the manufacturing execute module 302 to implement end device access and / or priority level assignment. The event includes the following steps: Base station A306 searches for time domain reallocation in the scheduled list based on the resource map. If a full allocation is not available, a search for a partial allocation with an equivalent or reduced bitrate resulting from an additional frequency domain allocation is performed, and if the search for a partial allocation is successful, the time domain and frequency domain resource reallocation is notified to the end devices. If a full allocation is available, the event is marked as reallocated class and the time domain reallocation is notified to the affected end devices. If neither full nor partial allocation is available, the event is marked as unallocated, the expected channel bitrate loss is notified to affected end devices, and the time-domain period of the failure is allocated from the affected end device node to the unaffected end device node.

[0066] Event 4 - Unexpected receiver failure (unpredictable event) An unexpected loss of link at the receiver (e.g., an end device) triggers this class of event. Detection may be determined when the interval between heartbeat messages exceeds a set threshold. In this embodiment, the interval between heartbeat messages may be set to every 10ms, and detection may be determined when three or five consecutive heartbeat messages are lost.

[0067] Such events are not planned and therefore may not be compensated for at the factory. These event types may also be recorded, even if they are due to link errors (which may remain unknown until the network control module 304 receives an update from a disconnected transmitter to confirm that an error actually occurred).

[0068] The event includes logging of link loss at base station A306 and network control module 304. Link loss may be notified via alternative route / channel. A beamwidth ramp routine may be initiated to re-establish the high-capacity link.

[0069] A link loss event may be notified via a high-capacity link if any one of the following events occurs, and a link re-establishment may be notified, which may include re-establishment of a high-capacity link, a link status update from an alternate route / channel, or exceeding the link failure alarm interval.

[0070] Event 5 - Prioritized Scheduling When an end device 310 enters the work zone 312 of base station A306 and submits a high-priority data rate request to the base station, the following actions may occur: Base station A306 may search for time domain reallocations in the schedule list based on the resource map. If a full allocation is available, the event is marked as reallocated, and the end device may be notified of the reallocation of time domain resources. If a full allocation is not available, a search is performed for a partial allocation with an equivalent or reduced bit rate resulting from an additional allocation in the frequency domain. If the search for a partial allocation is successful, the end device may be notified of the reallocation of time domain and frequency domain resources. If neither a full nor a partial allocation is available, base station A306 may refer to a list of connected end devices sorted by priority class. In this embodiment, all industrial operation tasks may be categorized into multiple priority classes, depending on the needs of the smart factory manager. The list of connected end devices may include a quality of service class identifier, resource requirement classes (guaranteed bitrate, unguaranteed bitrate), priority within each resource requirement class (e.g., 1, 2, 3, 4, ...), latency requirements, packet error rate requirements, and task definitions (e.g., machine vision).

[0071] Base station A306 may use network control module 304 to determine the end device with the lowest priority that should be temporarily changed to the unassigned class for a specific timestamp. Base station A306 may then redetermine the beamwidth for the work zone and / or end device and trigger a base station transmitter multi-power for event 1. This detail was previously described.

[0072] Next, base station A306 may notify the end device of the expected channel bitrate loss, and the event may be marked as a reallocated class.

[0073] Figure 12 is a block diagram of an exemplary radio frequency (RF) transmitter and receiver operating at 27 GHz. The transmitter may be the first or second device described with reference to Figure 4. Thus, the receiver may be the second or first device described with reference to Figure 4. Data may be transmitted from the DAC in "in-phase" (I) and "quadrature-phase" (Q) components. A local oscillator frequency of 13.5 GHz may be used, which, after passing through a multiplier, will increase the carrier frequency to 27 GHz. The data signals from the I and Q channels may then be mixed with the 27 GHz carrier frequency and amplified before being sent to the mmW antenna and lens. The distance from the center of the lens to the near plane of the antenna may be about 5 cm. In the receiver, the RF signal is detected and separated into I and Q components after passing through a low-noise amplifier (LNA). In embodiments, the same local oscillator (LO) and multiplier may be used on both the transmitter and receiver sides to perform clock recovery so that the phase of the received signal can be recovered. In this embodiment, the distance between the transmitter and receiver may be approximately 2.5 m, and a data rate of 3 Gbps may be achieved.

[0074] Figures 13A and 13B are graphs of beam widths (angles in degrees) of 3 dB and 6 dB for different distances (lens reconstruction settings) in centimeters, when operating at frequencies of 25 GHz, 26 GHz, and 27 GHz, respectively, according to embodiments of the present disclosure.

[0075] Figures 14A and 14B are graphs of beam widths (angles in degrees) of 3 dB and 6 dB for different distances (lens reconstruction settings) in centimeters, when operating at frequencies of 28 GHz, 29 GHz, and 30 GHz, respectively, according to embodiments of the present disclosure.

[0076] The beamwidth and distance data shown in Figures 13A, 13B, 14A, and 14B may be derived from physically modeled numerical electromagnetic simulations of a subset of the described lens designs under different reconstruction settings. Far-field projections and beamwidths of 3 dB and 6 dB may also be calculated. Thus, the plotted results may detail excitation by an ideal broadband radiation source. Therefore, variations in the final application with various non-ideal and directional radiation sources may be possible during the physical operation of the device.

[0077] Evaluations at different frequencies may indicate the range of supported operating frequencies for a given application and use with different wireless systems. Figures 13A, 13B, 14A, and 14B may further illustrate the expected impact on operation with broadband links over a range of bandwidths, which may be configured over a wider range of operating frequencies. Because evaluations over a wider frequency range may be possible, such data should not be used to infer an absolute limitation on operating frequencies based on the operating principle.

[0078] The described lens reconstruction settings may be digitally controlled and reconfigured via a network using protocols described elsewhere in this book. The settings may also be physically controlled by the position of actuators, representing a range of non-exclusive embodiments.

[0079] Assets Each base station within the factory may maintain a list of the following asset information associated with each end device: Heartbeat interval in milliseconds Heartbeat_threshold_milliseconds Link failure alarm interval Schedule List Resource map Window length (i.e., transmission window length in microseconds)

[0080] The link between base station A306 and end device 310 may include one or more of the following pieces of information: data rate Modulation format Power Budget Beam Profile Priority level

[0081] A scheduled fault access control list may include the following: Sender ID Priority level

[0082] Beam profile negotiation The default beam profile may be assigned by a pre-calculated table (described above) that references the link power budget allocation for each transceiver node with a defined beam width (in degrees or radians). The “Negotiate Beam Profile” message may be used in certain situations, for example, when a receiver requests a new beam profile from base station A306 that does not match the default allocation table, or when an unexpected event occurs at a transceiver device node, or in connection with other dynamic link updates that cause end device 310 to request a change in beam width.

[0083] Base station A306 may reject the request for any of the following reasons: a violation of the access control rule set, a conflict with a request of a higher priority level, or a conflict with the current service assignment (in which case a change in the beam profile would interrupt service to other nodes with the same beam profile and antenna assignment).

[0084] An example beam profile negotiation message may take the following form: Transmitter response Result: 0 Rejected 1 approval Error code: -1 Unknown error 0 No errors 1. Undisclosed error 2. Access violation 3. Priority Conflict 4. Service competition Timeout milliseconds: The timeout in milliseconds until renegotiation is approved. receiver request Beam profile request Reason code: -1 Unknown cause 0 Rescheduled actions 1. Link lost 2. Unexpected obstacles

[0085] Heartbeat messages used in the communication of information between a base station and one or more end devices may include the following: Parameter: Interval (milliseconds) Event List

[0086] It should be understood that the content of these messages may not be limited to what is provided here. As shop floor reconfigurations become more complex, for example, involving a larger number of diverse tasks and / or machines / robots, the information that needs to be included in these messages may become more complex. For example, machines with different quality 3D vision cameras that require different data rates to perform tasks of different granularity, or robots that move at different speeds and / or perform tasks at different speeds, thereby requiring different data rates, or the same data rate but different time intervals.

[0087] Scheduled fault messages may include the following: Failure start time: POSIX floating-point date. Failure termination time: POSIX floating-point date. Priority level Cause of the failure: -1 Unknown 0 Scheduled link downtime 1. Entering an area where service is unavailable. 2. Beam blocking 3. Alternative route unavailable. Diversity: bit -1 Reallocation unavailable (bitrate = 0 for the scheduled period) Time domain multiplexing reallocation available (bitrate guaranteed) 1. Time and frequency domain multiplexing reallocation available (bitrate guaranteed) Time and frequency domain multiplexing reallocation available (bitrate reduction) Resource Map TDM Assignment Resource Map FDM Assignment Result ID: Base station service area ID, or end device node ID, or null.

[0088] One or more embodiments of the present disclosure may provide a method for controlling millimeter-wave beamwidth within the FR2 5G band (K / Ka band boundary, i.e., 24.25–27.5 GHz) and throughout the entire Ka band (26.5–40 GHz). In one or more embodiments, the coverage of the base station's mmW antenna may be increased from about 60° to about 120°, and a gain of 11 dB may be achieved.

[0089] Compared to conventional wireless systems that optimize resource map allocation by focusing on task prioritization and frequency and time domain allocation, one or more embodiments of the Disclosure may provide a dynamic variable focus beamwidth control method. By optimally minimizing the beamwidth at the base station, the transceiver gain can be increased, and therefore higher modulation formats and codings can be used to improve the data rate of end devices. This results in more efficient use of time and frequency domain resource blocks, as the same amount of data can be transmitted using fewer blocks, ultimately maximizing the overall throughput of the system within a smart factory. One or more embodiments of the Disclosure may provide a narrow-focus high-data-rate beam for a small set of end devices running high-data-rate applications, and may reconfigure the beamwidth to provide a wider-focus beam as the number of end devices in the work zone increases. One or more embodiments of the Disclosure may provide accurate, reliable, and low-cost beamwidth control for the growing 5G market, particularly as applications extend beyond conventional communication environments into next-generation smart industries.

[0090] In one embodiment, one or two robots (end devices) may be performing ultrasonic inspections requiring high data rates (and therefore narrow-focus beams) in a specific / designated work zone of a factory, while real-time analysis is being performed simultaneously. After the inspection, multiple robots (end devices) may enter the designated area to deliver / drop off tools and components and perform assembly, thereby requiring increased beam width, but only requiring medium to low data rates.

[0091] Conventional phased array beamforming methods actively transmit phase-shifted signals to generate a beamform. The sum of the power of each element is the coupled array signal power required to form the transmit beam, and is continuous over the duration of a constant beam configuration. The additional power required to form the beam is proportional to the number of array elements. In contrast, one or more embodiments of the present disclosure may require additional power only when the beam is reconfigured. When the beam configuration is constant, the present disclosure may not require additional power to maintain the beam profile. Other possible advantages of the present disclosure may include lower computing resources, lower installation and maintenance costs, lower integration complexity, higher uplink data rates, higher uplink continuity, higher uplink consistency, improved reconfigurability, lower complexity, better security, and improved reliability and adaptability.

[0092] Further possible advantages of this disclosure may include: simpler designs using patch antennas with lenses and actuators (mechanical or MEMS) as described in this disclosure; smaller / more compact lens antenna structures that can be reconfigured in real time; lower cost and / or complexity; ease of implementation; lower power consumption; deployment in base stations and / or end devices (e.g., machines, robots); real-time adjustable beamwidth reconfiguration; use in the design of base stations, end devices, and / or repeaters; the reconfigurable lens devices and / or methods described can be used with various radiation source types; and the ability to control beam steering and / or beamwidth reconfiguration using feedback mechanisms as described elsewhere in this disclosure.

[0093] This disclosure may find applications in smart factory environments using wireless communications, where robots and / or machines may be more deterministic in terms of motion, data rate (task-based), and / or signal quality, and therefore may provide more optimized, simplified, and customized protocols suitable for such environments. Beamwidth may be controllable and / or reconfigurable in real time based on one or more of location, data rate requirements, and / or link budgets (collected, for example, from a manufacturing execution system (MES) module of a central controller in the manufacturing environment). One or more embodiments of this disclosure may provide more effective control of wireless signals in a closed space (i.e., a factory), as well as real-time optimization of protocol and / or beamwidth selection to maximize effective throughput when robots and / or machines (end devices) are performing different applications and tasks that require different packet sizes, spacing, and / or latency.

[0094] Implementation of the Examples In the example, the message contained the following data format: a. Message UID 64-bit b. Sender node ID (64 bits) c. Recipient node ID (64 bits) d. Channel ID (64 bits) e-Message authentication code (256 or 512 bits) f. Sender's public key length, Sender's public key g. Encryption type h. Cryptographic parameters 1 i. Cryptographic parameters 2 j. Cryptographic parameter 3 k.FEC encoding, FEC payload l. Message integrity code 64 / 128 bits m. Payload length n. Payload

Claims

1. A device for controlling the beam width of a millimeter-wave (mmW) device, a. Lens and, b. mmW antenna and, c. An apparatus comprising a lens and an actuation arrangement operably connected to the mmW antenna, wherein the actuation arrangement is configured to change the beam width of the mmW antenna based on a control signal.

2. The apparatus according to claim 1, wherein the mmW device is communicatively coupled to a first device, and the first device is configured to communicate with a second device.

3. The apparatus according to claim 2, wherein the control signal is a connection request transmitted between the first device and the second device.

4. The apparatus according to claim 3, wherein the control signal comprises a data rate associated with the connection request.

5. The apparatus according to claim 4, wherein the control signal further comprises the location of one or both of the first device and the second device.

6. The apparatus according to claim 3 or 4, wherein the actuation arrangement is configured to change the beam width of the mmW antenna by increasing the beam width when the data rate is lower than a predetermined value.

7. The apparatus according to claim 3 or 4, wherein the actuation arrangement is configured to change the beam width of the mmW antenna by reducing the beam width when the data rate is higher than a predetermined value.

8. The apparatus according to any one of claims 2 to 7, wherein the connection request is initiated when the first device and the second device are in a common work zone.

9. The apparatus according to any one of claims 4 to 8, wherein the data rate associated with the connection request is the data rate required for the first device or the second device to perform a task in an automated factory.

10. The apparatus according to claim 9, wherein the actuation arrangement is configured to further change the beam width of the mmW antenna based on the priority of the tasks.

11. The apparatus according to claim 8, wherein the beam width is varied based on the distance of the first device and / or the second device from the boundary of the common work zone.

12. The apparatus according to any one of claims 4 to 11, wherein the data rate associated with the connection request is determined based on time-domain resource allocation and / or frequency-domain resource allocation.

13. The apparatus according to any one of claims 1 to 12, further comprising changing the beam width by changing the distance between the mmW antenna and the lens.

14. The apparatus according to any one of claims 2 to 13, wherein the beam width is further based on a link power budget defined for the first device and / or the second device.

15. A method for controlling the beamwidth of a millimeter-wave (mmW) antenna, a. At a base station, receiving connection requests from end devices located at a certain location, b. Determining the beamwidth of the mmW antenna of the base station and the data rate associated with the connection request from the end device, c. A method comprising changing one or both of the beamwidth of the mmW antenna of the base station and the beamwidth of the mmW antenna of the end device based on the determined data rate and the location.

16. The method according to claim 15, wherein changing the beam width of the mmW antenna is further characterized by increasing the beam width when the determined data rate is lower than a predetermined value.

17. The method according to claim 15, wherein changing the beam width of the mmW antenna is further characterized by reducing the beam width when the determined data rate is higher than a predetermined value.

18. The method according to any one of claims 15 to 17, wherein the beam width is further based on the priority of the task associated with the connection request.

19. The method according to any one of claims 15 to 18, wherein the connection request is received when the end device is activated in a work zone associated with the base station.

20. The method according to any one of claims 15 to 19, wherein the data rate associated with the connection request is the data rate required to perform a task in an automated factory.

21. The method according to claim 19, wherein the beam width is varied based on the distance of the end device from the boundary of the work zone.

22. The method according to any one of claims 15 to 21, further comprising determining the data rate associated with the connection request, which in turn involves determining the resource allocation of the base station.

23. The method according to claim 22, wherein the resource allocation further comprises a time domain allocation.

24. The method according to claim 22 or 23, wherein the resource allocation further comprises a frequency domain allocation.

25. The method according to any one of claims 15 to 24, further comprising changing the beam width of the mmW antenna of the base station by changing the distance between the mmW antenna and the lens of the base station.

26. The method according to any one of claims 15 to 25, further comprising changing the beam width of the mmW antenna of the end device by changing the distance between the mmW antenna and the lens of the end device.

27. The method according to any one of claims 15 to 26, wherein the beam width is further based on a defined link power budget for the end device.