System and method for managing communication and beamforming towards ues using reconfigurable intelligent surfaces

Abstract

The present disclosure provides a system (202) and a method for managing communication and beamforming towards a plurality of User Equipments (UEs) (208) using a Reconfigurable Intelligent Surface (RIS) (206). The system (202) establishes a connection with a RIS controller unit (RCU) (204) and the UEs (208), and receives a plurality of parameters from each UE (208), and RIS-related information from the RCU (204). The system (202) determines that at least one UE (208-1) is within or approaching a RIS coverage area, and transmits a message indicating that the at least one UE (208-1) is within or approaching the RIS coverage area to the RCU (204). Further, the system (202) enables the RCU (204) to reserve antenna array elements to directly communicate with the UE (208-1), and configure the RIS (206) for managing beamforming towards the UE (208-1), based on the message.

Description

SYSTEM AND METHOD FOR MANAGING COMMUNICATION AND BEAMFORMING TOWARDS UEs USING RECONFIGURABEE INTELLIGENT SURFACESRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The embodiments of the present disclosure generally relate to a field of wireless communication systems. More particularly, the present disclosure relates to a system and a method for managing communication and beamforming towards user equipments (UEs) using Reconfigurable Intelligent Surfaces (RIS), thereby optimizing signal propagation, enhancing coverage, and improving communication performance in wireless networks.BACKGROUND

[0003] The fifth-generation (5G) wireless technology, developed by a 3rdGeneration Partnership Project (3GPP), is designed to deliver significantly higher multi-Gbps peak data speeds, ultra-low latency, enhanced reliability, massive network capacity, increased availability, and a more consistent user experience across diverse users. While 5G has introduced higher performance and efficiency, empowering new user experiences and enabling new industry use cases, several challenges remain. The challenges include accommodating vertical industries, supporting private networks, and enabling flexible network deployments. To address these limitations, a sixth-generation (6G) network architecture introduces innovative solutions to enhance flexibility and adaptability. The 6G architecture integrates advanced physical layer technologies such as Orthogonal Time Frequency Space (OTFS), full-duplex communication, and intelligent surfaces, alongside comprehensive upper-layer considerations, while incorporating network sensing as a core functionality.

[0004] The 5G network has already introduced revolutionary features compared to previous generations, enabling services like enhanced Mobile Broadband (eMBB) and UltraReliable Low Latency Communication (URLLC). However, as we transition toward beyond 5G (B5G) systems, there are fundamental issues to resolve, such as achieving higher system capacity, faster data rates, reduced latency, and improved Quality of Service (QoS). A 6G network is envisioned to fully leverage Artificial Intelligence (Al) and other emerging technologies to overcome these limitations and deliver unprecedented communication capabilities.

[0005] Despite the progress in 5G, many emerging technologies remain underutilized, such as terahertz communication, optical wireless technology, free-space optics, blockchain, 3-Dimensional (3D) networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer, dynamic network slicing, holographic beamforming, and big data analytics. The 6G network architecture seeks to address this gap by enabling the convergence and utilization of the advanced technologies, ensuring a holistic and innovative approach to future wireless networks.

[0006] The 6G network architecture aims to expand human experiences across the physical, biological, and digital realms while simultaneously supporting next-generation industrial operations. It will focus on performance dimensions such as precise positioning, sensing, ultra-reliability, energy efficiency, and real-time responsiveness. The architecture envisions radio and access frameworks that serve both communication and sensing purposes, Al-optimized wide-area networks, dynamic orchestration of personalized services, and extreme real-time operations. Energy efficiency will be a critical consideration, given its impact on network performance across architectural domains. Additionally, use cases such as uncompressed transmission of high-quality 360-degree video for immersive augmented reality experiences will demand ultra-high data rates of 100 Gbps or more, along with extreme reliability and low latency. In essence, the 6G network must support programmable, flexible, secure, and automated systems, driven by specific use cases and guided by policy and intent, to meet the diverse needs of users and industries alike.

[0007] The recently completed 5G new radio standard is a result of several cutting-edge technologies, including massive multiple-input multiple-output (MIMO), millimeter (mm)-Wave communication and network densification. However, these technologies face two main practical limitations, namely, lack of control over a wireless channel, and high-power consumption of a wireless interface.

[0008] There is, therefore, a need in the art to provide an improved system and a method to manage communication and beamforming towards a plurality of user equipments using a Reconfigurable Intelligent Surface (RIS) by overcoming the deficiencies of the prior art(s).OBJECTS OF THE PRESENT DISCLOSURE

[0009] It is an object of the present disclosure to provide a system and a method for managing communication and beamforming for a plurality of user equipments using a Reconfigurable Intelligent Surface (RIS).

[0010] It is an object of the present disclosure to provide a system and a method for reconfiguring wireless propagation environments using Intelligent Reflecting Surfaces (IRS) or the RIS.

[0011] It is an object of the present disclosure to provide a system and a method to perform RIS tilt management (mechanical and digital tilt) so that a plurality of users can be served by a deployed RIS.

[0012] Another object of the present disclosure is to provide a system and a method to discover and register the RIS to a base station using a link setup procedure, and exchange capability information between the RIS and the base station.

[0013] Yet another object of the present disclosure is to provide a system and a method to determine whether the user equipment is within or approaching a RIS coverage area based on a plurality of parameters.

[0014] Yet another object of the present disclosure is to provide a system and a method that transmits a message indicating that the user equipment is within or approaching the RIS coverage area to a RIS controller unit (RCU).

[0015] Yet another object of the present disclosure is to provide a system and a method that enables the RCU to reserve antenna array elements of the RCU to directly communicate with the UE, and configure the RIS for managing beamforming towards the UE, based on the message.SUMMARY

[0016] In an aspect, the present disclosure relates to a system of a base station for managing communication and beamforming towards a plurality of user equipments using a Reconfigurable Intelligent Surface (RIS). The system includes one or more processors, and a memory operatively coupled to the one or more processors. The memory includes processorexecutable instructions, which on execution, cause the one or more processors to establish aconnection with a RIS controller unit (RCU) and the plurality of user equipments, and receive a plurality of parameters from each of the plurality of user equipments, and RlS-related information from the RCU. The one or more processors determine that at least one user equipment of the plurality of user equipments is within or approaching a RIS coverage area based on the plurality of parameters and the RlS-related information. Based on the determination, the one or more processors transmit a message indicating that the at least one user equipment is within or approaching the RIS coverage area to the RCU. The one or more processors enable the RCU to reserve one or more antenna array elements of the RCU to directly communicate with the at least one UE, and configure the RIS for managing beamforming towards the at least one UE, based on the message.

[0017] In an embodiment, the one or more processors may be configured to dynamically decide whether to use same beam or different beams to serve the plurality of user equipments within the RIS coverage area.

[0018] In an embodiment, when the at least one user equipment is served only by the reflected beams, the one or more processors may be configured to track a movement of the at least one user equipment, and initiate an intra-cell inter-beam handover when the at least one user equipment crosses from the RIS coverage area into a normal cell coverage area.

[0019] In an embodiment, the plurality of parameters may include at least one of location information and mobility patterns of each of the plurality of user equipments, a direction of travel of each of the plurality of user equipments, and RIS coverage information.

[0020] In an embodiment, based on the determination that the at least one user equipment is within or approaching the RIS coverage area, the one or more processors may be configured to create and update an RIS-user equipment mapping table comprising the plurality of parameters.

[0021] In an embodiment, the one or more processors may be configured to establish the connection with the RCU via a first interface, and wherein the RCU establishes a connection with the RIS panel associated with the RIS via a second interface, to reflect actual data or signals between the system and each of the plurality of user equipments over a third interface.

[0022] In an embodiment, the first interface and the second interface may be implemented as at least one of wired channels or wireless channels.

[0023] In an embodiment, the one or more processors may establish and manage the first and second interfaces with the RIS panel through the RCU by being configured to receive an RCU link setup request message including an array of RIS panel identifiers (RIS HW IDs) and an associated array of RIS capabilities from the RCU. The one or more processors mayauthenticate the RIS HW IDs by verifying the RIS HW IDs against one or more identifiers stored in a database and determining a validity of the RIS HW IDs. Based on a successful authentication, the one or more processors may generate a new RIS identifier (new RIS ID) for the RIS panel, map the new RIS ID to the corresponding RIS HW ID, and store the new RIS ID, the corresponding RIS HW ID, and the associated array of RIS capabilities in an RCU RIS table. The one or more processors may transmit an RCU link setup accept message including the new RIS ID mapped to the corresponding RIS HW ID and the associated array of RIS capabilities, along with a validation timer to the RCU, where the RCU may decode and send the RCU link setup accept message to the RIS panel.

[0024] In an embodiment, based on an unsuccessful authentication, the one or more processors may be configured to send an RCU link setup reject message with the array of RIS HW IDs to the RCU, where the RCU may decode and send the RCU link setup reject message to the RIS panel.

[0025] In an embodiment, the one or more processors may enable the RCU to manage beamforming towards the at least one user equipment or the RIS panel by being configured to receive capability information from the RCU associated with the RIS panel in a serving area of the at least one user equipment, and trigger a configuration towards the RIS panel in the serving area of the at least one user equipment based on the capability information. Upon triggering the configuration towards the RIS panel, the one or more processors may transmit an RCU RIS resource control command with an array of configurations per RIS to the RCU. The RCU may decode the array of configurations and configure the RIS panel, send a RIS resource control command to the RIS panel, and receive a RIS resource control accept response from the RIS panel when the RIS panel adheres to the array of configurations. The one or more processors may receive an RCU RIS resource control accept response from the RCU, and initiate transmission of any or the combination of reflected beams and direct beams for managing beamforming towards the RIS panel or the at least one user equipment.

[0026] In an embodiment, the one or more processors may be configured to receive an RCU RIS resource control reject response from the RCU, when the RCU decodes the array of configurations and fails to adhere to the array of configurations.

[0027] In an embodiment, the one or more processors may be configured to receive an RCU RIS resource control reject response from the RCU, when the RCU decodes the array of configurations and configures the RIS panel, sends the RIS resource control command to the RIS panel, and receives a RIS resource control reject response from the RIS panel when the RIS panel fails to adhere to the array of configurations.

[0028] In an embodiment, the one or more processors may be configured to receive the RIS-related information from the RCU once the RIS panel shares the RIS-related information as a configuration message with the RCU via at least one of an Operations, Administration, and Maintenance (0AM) entity or an Application Server (AS).

[0029] In an embodiment, the one or more processors may be configured to update one or more capabilities of the RIS panel when an RCU DU configuration update message with an array of capabilities per RIS is received from the RCU, and send an RCU DU configuration update confirm message to the RCU, where the RCU sends an RIS RCU configuration update confirm message to the RIS panel.

[0030] In an embodiment, wherein when the system queries for specific RIS capabilities from the RIS, the one or more processors may be configured to send a RCU capability query request including an RIS ID and an array of specific RIS capabilities to the RCU, where the RCU may identify specific RIS panel by decoding the RCU capability query request, send a RIS capability query request to the RIS panel, and receive a RIS capability query response including the array of specific RIS capabilities from the RIS. Further, the one or more processors may receive an RCU capability query response including the array of specific RIS capabilities from the RCU once the RCU receives the RIS capability query response from the RIS.

[0031] In an embodiment, the one or more processors may be configured to trigger the configuration to the RCU and the RIS panel based on the RIS-related information, and configure keep alive timers to the RCU and the RIS panel in the RCU RIS resource control command and the RIS resource control command, respectively.

[0032] In an embodiment, the one or more processors may be configured to monitor keep alive messages from the RCU for every RCU keep alive timer expiry for a predetermined number of keep alive attempts, and trigger an RCU failure condition once the predetermined number of keep alive attempts are crossed.

[0033] In an embodiment, the one or more processors may be configured to receive the location information and the mobility patterns of each of the plurality of user equipments by sending a location update query request to each of the plurality of user equipments and receiving a location update query response including the location information and the mobility patterns from each of the plurality of user equipments.

[0034] In an embodiment, the one or more processors may initiate at least one of activation or deactivation of the RIS panel by being configured to send at least one of an RIS activation command or an RIS deactivation command to the RCU, where the RCU may decode the RIS activation command or the RIS deactivation command, send an RCU RIS activationcommand or an RCU RIS deactivation command to the RIS panel, and receive an RCU RIS activation accept command or an RCU RIS deactivation accept command from the RIS panel. Further, the one or more processors may receive at least one of an RIS activation accept command or an RIS deactivation accept command from the RCU once the RCU receives the RCU RIS activation accept command or the RCU RIS deactivation accept command from the RIS panel.

[0035] In an embodiment, the one or more processors may be configured to receive at least one of an RIS activation reject response or an RIS deactivation reject response from the RCU during a failure in at least one of the RCU or the RIS panel.

[0036] In an aspect, the present disclosure relates to a method for managing beamforming for a plurality of user equipments using a Reconfigurable Intelligent Surface (RIS). The method includes establishing, by one or more processors associated with a system, a connection with an RCU and the plurality of user equipments. Upon establishing the connection, the method includes receiving, by the one or more processors, a plurality of parameters from each of the plurality of user equipments, and RIS-related information from the RCU. The method includes determining, by the one or more processors, that at least one user equipment of the plurality of user equipments is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information. Based on the determination, the method includes transmitting, by the one or more processors, a message indicating that the at least one user equipment is within or approaching the RIS coverage area to the RCU. Further, the method includes enabling, by the one or more processors, the RCU to reserve one or more antenna array elements of the RCU to directly communicate with the at least one UE, and configure the RIS for managing beamforming towards the at least one UE, based on the message.

[0037] In an aspect, the present disclosure relates to a user equipment (UE) including a processor and a memory operatively coupled to the processor. The memory includes processorexecutable instructions, which on execution, cause the processor to send a report including a plurality of parameters to a system. The processor is communicatively coupled with the system, and the system is configured to establish a connection with an RCU and the UE. Upon establishing the connection, the system receives the plurality of parameters from the UE, and RIS-related information from the RCU, and determines that the UE is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information. Based on the determination, the system transmits a message indicating that the UE is within or approaching the RIS coverage area to the RCU. Further, the system enables the RCU to reserve one or more antenna array elements of the RCU to directly communicate with the at least oneUE, and configure the RIS for managing beamforming towards the at least one UE, based on the message.

[0038] In an aspect, the present disclosure relates to a non-transitory computer-readable medium comprising processor-executable instructions that cause a processor to establish a connection with an RCU and a plurality of user equipments. Upon establishing the connection, the processor receives a plurality of parameters from each of the plurality of user equipments, and RlS-related information from the RCU. The processor determines that at least one user equipment of the plurality of user equipments is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information. Based on the determination, the processor transmits a message indicating that the at least one user equipment is within or approaching the RIS coverage area to the RCU. Further, the processor enables the RCU to reserve one or more antenna array elements of the RCU to directly communicate with the at least one UE, and configure the RIS for managing beamforming towards the at least one UE, based on the message.BRIEF DESCRIPTION OF DRAWINGS

[0039] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0040] FIGs. 1A and IB illustrate schematic views (100A, 100B) depicting RIS deployment scenario.

[0041] FIG. 2 illustrates an exemplary Reconfigurable Intelligent Surface (RIS) integrated network architecture (200) for managing communication and beamforming towards the plurality of user equipments, in accordance with an embodiment of the present disclosure.

[0042] FIG. 3 illustrates an example schematic view (300) depicting a RIS coverage support, in accordance with an embodiment of the present disclosure.

[0043] FIG. 4 illustrate an example schematic view (400) depicting a RIS sharing scenario, in accordance with an embodiment of the present disclosure.

[0044] FIG. 5 illustrates an exemplary network architecture (500) for implementing a system for managing communication and beamforming towards a plurality of user equipments using the RIS, in accordance with an embodiment of the present disclosure.

[0045] FIG. 6 illustrates an exemplary block diagram (600) of a communication system architecture with RIS support, in accordance with embodiments of the present disclosure.

[0046] FIG. 7 illustrates an exemplary block diagram (700) of a protocol architecture of the communication system, in accordance with embodiments of the present disclosure.

[0047] FIG. 8 illustrates an exemplary block diagram (800) of a system for managing communication and beamforming towards the plurality of user equipments using the RIS, in accordance with embodiments of the present disclosure.

[0048] FIG. 9A illustrates a sequential diagram (900A) depicting a link setup success case during a link setup procedure, in accordance with embodiments of the present disclosure.

[0049] FIG. 9B illustrates a sequential diagram (900B) depicting a link setup failure case during the link setup procedure when an authentication fails against RIS HW ID, in accordance with embodiments of the present disclosure.

[0050] FIG. 9C illustrates a sequential diagram (900C) depicting a link setup failure case during the link setup procedure when an RCU rejects a link establishment procedure, in accordance with embodiments of the present disclosure.

[0051] FIG. 10A illustrates a sequential diagram (1000A) depicting a success case during a RIS resource control command procedure, in accordance with embodiments of the present disclosure.

[0052] FIG. 10B illustrates a sequential diagram (1000B) depicting a failure case when the RCU is unable to adhere to configurations shared by the system to the RCU, in accordance with embodiments of the present disclosure.

[0053] FIG. 10C illustrates a sequential diagram (1000C) depicting a failure case when the RIS is unable to adhere to the configurations shared by the system to the RCU and then from the RCU to the RIS, in accordance with embodiments of the present disclosure.

[0054] FIG. 11A illustrates a sequential diagram (1100A) depicting a capability exchange procedure, in accordance with embodiments of the present disclosure.

[0055] FIG. 11B illustrates a sequential diagram (1100B) depicting a configuration update procedure of the RIS, in accordance with embodiments of the present disclosure.

[0056] FIG. 11C illustrates a sequential diagram (1100C) depicting capability query and response procedures, in accordance with embodiments of the present disclosure.

[0057] FIG. 12 illustrates a sequential diagram (1200) depicting a keep alive procedure, in accordance with embodiments of the present disclosure.

[0058] FIG. 13 illustrates a sequential diagram (1300) depicting a system configuration update procedure, in accordance with embodiments of the present disclosure.

[0059] FIG. 14 illustrates a sequential diagram (1400) depicting a location query procedure, in accordance with embodiments of the present disclosure.

[0060] FIG. 15A illustrates a sequential diagram (1500A) depicting an activation / deactivation procedure of RIS from the system, in accordance with embodiments of the present disclosure.

[0061] FIG. 15B illustrates a sequential diagram (1500B) depicting an activation / deactivation failure procedure, in accordance with embodiments of the present disclosure.

[0062] FIG. 16 illustrates a sequential diagram (1600) depicting a failure indication procedure to EMS / OAM, in accordance with embodiments of the present disclosure.

[0063] FIG. 17 illustrates an exemplary computer system (1700) in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.

[0064] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0065] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0066] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that variouschanges may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0067] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.

[0068] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0069] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0070] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0071] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0072] FIGs. 1A and IB illustrate schematic views (100A, 100B) depicting Reconfigurable Intelligent Surfaces (RIS) deployment scenario.

[0073] With reference to FIG. 1 A, the RIS are fast emerging as a key wireless technology trend for beyond 5G systems. The RIS correspond to smart radio surfaces of many small antennas or reconfigurable metamaterial elements (unit cells), which enable controlling a propagation environment through tunable scatterings of electromagnetic waves. The RIS have reflection, refraction, and absorption properties, which are reconfigurable and adaptable to a radio channel environment, therefore enabling a go-beyond Snell's law of static reflection and refraction. The main peculiarities of the RIS include no power amplification, operation at a Radio Frequency (RF) level with no or limited digital signal processing (depending on the type of RIS - active, passive, or hybrid), and multi-functional reconfigurability.

[0074] Three use cases that are currently being explored for RIS are as follows:1. RIS used as smart nearly passive relays for coverage extension,2. RIS used as single-RF multi-stream transmitter for capacity improvements, and 3. RIS used for information aided transmission in the context of ambient backscattering and symbiotic radio.

[0075] The RISs enable control of radio signals between a transmitter and a receiver in a dynamic and goal -oriented way, thereby turning the wireless environment into a service. This ability in terms of reconfiguring the wireless channel has motivated a host of potential enhancements of various network Key Performance Indicators (KPIs) such as capacity, coverage, energy efficiency, positioning, and security, which is in addition to the support of new capabilities such as sensing and wireless power transfer.

[0076] With reference to FIG. IB, the RISs introduce a new system node turning the wireless environment from a passive to an intelligent actor, so the channel becomes programmable. This may challenge basic wireless system design paradigms, creating innovation opportunity which will progressively impact the evolution of wireless system architecture, access technologies, and networking protocols.

[0077] The RIS is expected to construct an intelligent and programmable radio environment in a controllable way. The RIS makes it possible to perform passive reflection, passive absorption, passive scattering, and push the physical environment to change towards intelligent and interactive. The RIS can change electromagnetic characteristics of the elements and generate phase shift independently on incident signals without using any RF signal processing. Also, the RIS technology has many technical features beyond current mainstream technology. Compared with massive Multiple Input Multiple Output (MIMO), RIS-aided wireless network hugely improves the system performance via optimizing the smart signal propagation.

[0078] As a key candidate technology, the RIS has many advantages. The RIS element is completely passive and it has low power consumption, making it environmentally friendly and sustainable green. No high cost components such as Analog-to-Digital Converter / Digital-to-Analog Converter (ADC / DAC) and power amplifier are needed, and a feasibility of large-area deployment can be improved. In addition, electromagnetic waves may be reconstructed at any point on its continuous surface, thus form any shape to adapt to different application scenarios and support higher spatial-resolution.

[0079] The RIS makes it possible to intelligently control the propagation environment, improve transmission reliability, and achieve higher spectrum efficiency. The RIS is applicable to the following typical scenarios: (i) Overcome Non-Line-of-Sight (NLoS) limitation and deal with a coverage hole problem in an environmentally friendly manner, (ii) Serve cell edge users, relief multi -cell co-channel interference, expand coverage, and implement dynamic mobile user tracking, (iii) Reduce electromagnetic pollution and solve the multi-path problem, (iv) RIS can be used for positioning, perception, holographic communication, and enhance reality, (v) To realize sensing-communication integration.

[0080] Future communication systems may face a more complex wireless environment and higher service quality requirements, which may bring greater challenges to the RIS. Firstly, reasonable electromagnetic model and channel model has to be established. The fundamental limitation and potential gains of RIS-aided communication systems has to be explored. Brand new method is required for channel estimation as no RF chain is configured in the RIS.Secondly, passive beamforming design and passive information transfer optimization are required. In addition, RIS deployment may bring a new network paradigm. Furthermore, research and development of new material is one of the bottlenecks in the development of the RIS technology. New control mechanism may be explored through electromagnetic modelling, control methods, and baseband characterization of meta surface. Finally, as the theoretical research on electromagnetic propagation and channel models continues to grow, it is necessary to consider data-driven and model-driven Artificial Intelligence (Al) optimization design to make full use of physical-layer features and improve algorithm efficiency.

[0081] As one new fundamental technology, the RIS has the characteristics of low cost, low power consumption, and easy deployment, supports future green communication, and enables future sensing-communication integration. The RIS is around a comer to bring a new network paradigm and open a new era of future communication system.

[0082] Therefore, the present disclosure provides a system and a method for managing communication and beamforming towards a plurality of user equipments using the RIS. The system may be associated with a base station or interchangeably referred to as the base station throughout the disclosure. The RIS helps in enhancing desired signal power while nulling reflected interference. Alternatively, the RIS tunes the reflected interference to cancel direct interference, thereby improving cell -edge user’s Signal-to-Interference-plus-Noise Ratio (SINR) by creating a signal hotspot as well as interference-free zone in a vicinity of the RIS.

[0083] The system ensures that the base station is aware of the availability of the RIS and the RIS is controlled / configured considering a given user distribution in the vicinity of a deployed RIS panel. In one embodiment, the system may control and configure the RIS with various parameters. The parameters may include, but not limited to, spatial information including phase, amplitude, directivity, and other beamforming information, Uplink / Downlink (UL / DL) in Time Division Duplexing (TDD) configuration information for better interference management, timing advance information to adjust the timing related information caused due to the delays caused between the DU - RIS control unit (RCU) link and then between the RCU -RIS link, activation or deactivation of a specific RIS, a mode (reflection / refraction / etc.) in which the RIS operates, a feedback (measurement report, Channel State Information (CSI) report, etc), information or configuration on how the RIS shall be controlled, e.g., network controlled or network assisted, etc. All or few of the above parameters may be controlled via a newly introduced node called the RCU, which in turn is connected to the base station.

[0084] In one embodiment, the base station may be aware of the RIS either through prior knowledge encoded in a database or via a signaling mechanism between the RIS and the basestation. When the RIS comes up, the RIS may send a handshake signal to all connected RCUs and from RCU to the base stations via a physical connection available, where the following information is exchanged: RIS Identifier (ID), capabilities of the RIS etc. The connection between the RIS and the base station via the RCU may also be via an RF connection (Integrated Access and Backhaul (IAB), Microwave link, etc). The handshake signal schema may be proposed as following.

[0085] In one embodiment, we assume a mechanism of interface between the base station and a RIS panel as shown in FIG. IB. FIG. IB depicts an open architecture for a RIS-assisted communication system, wherein the base station hosting an RIS application layer connects to the RCU which in turn controls the RIS.

[0086] In one deployment option, a micro controller that is a part of the RIS may also be treated as the RIS controller unit called the RCU, and in other deployment option, the same RCU may be made as a separate logical entity sitting outside the RIS which shall control multiple RISs connected to the same.

[0087] Various embodiments of the present disclosure will be explained in detail with reference to FIGs. 2-17.

[0088] FIG. 2 illustrates an exemplary RIS integrated network architecture (200) for managing communication and beamforming towards a plurality of user equipments, in accordance with an embodiment of the present disclosure.

[0089] With reference to FIG. 2, in the RIS integrated network architecture (200), the RIS (206) comprises of a reflecting surface (RIS hardware) (206a), equipped with a control unit. It may be appreciated that the reflecting surface or the RIS hardware (206a) may be interchangeably referred to as a RIS panel throughout the disclosure.

[0090] A link between a base station (BS) (202) including a Distribution Unit (DU) (202a), a Centralized Unit (CU) (202b), and a RIS controller (202c), and a RIS control unit (RCU) (204) may be termed as a control link. A link between the BS (202) and the RIS hardware (206a) may be termed as a backhaul link, and a link between the RIS hardware (206a) and a user equipment (UE) (208) may be termed as an access link. The RIS hardware (206a) may reflect Radio Frequency (RF) signals incident on it to the UE (208).

[0091] The RCU (204) may perform signaling exchanges to and from the BS (202) using the control link. The signaling exchange may be for establishing synchronization between the BS (202) and the RIS (206), transmitting capability information from the RIS (206) to the BS (202) and receiving control information from the BS (202) to the RIS (206). The capability information of the RIS (206) may include parameters of the RIS (206) which may be known bythe network (214) and the BS (202) so that the RIS (206) may be configured properly. The capability information may be provided by the RCU / OAM to the BS (202). The capability information may include, but not limited to, an angle of incidence beam, an operating frequency and its range, a channel estimation capability, location information, a number of beams that may be handled simultaneously, configuration of meta-elements, number of phase shifts and amplitude levels, values of phase shifts and amplitude levels, coupling elements, codebook design capabilities, region of coverage of RIS (206), beamforming pattern at the RIS (206), the region covered by each beam at the RIS (206), RIS type, operation mode, and a control mode.

[0092] The control link may be either wired or wireless channel. In case of a wireless channel, either dedicated resources may be used for signaling exchanges, or the signals may be multiplexed with the resources used for exchanging control / data signals between the BS (202) and the UE (208). In case of a wired channel, the signaling exchanges between the BS (202) and the RIS (206) may remain the same, however, the signaling mechanism may differ depending on the interface.

[0093] A transport layer between the BS (202) and the RIS (206) may be wireless or wired. In case of wireless transport option, the transport layer may also be based on cellular radio-interface (i.e., IAB). In this case, the RCU (204) may consist of all LI, L2 and L3 layers like the UE (208). The RCU (204) may be also capable of performing UE like operations, e.g., initial access, capability reporting and receiving control information. For the BS (202) to operate with the RIS (206), certain capability information of the RIS (206) may be required at the BS (202).

[0094] The base station (202) including the CU (202b) and the DU (202a) may communicate to a target UE (208) over a Uu interface direction or via RIS reflectors again over the Uu interface. The base station (202) may include an application layer called the RIS controller (202c), which may communicate to the RCU (204) over the control link called R-l. The BS (202) may be terrestrial or non-terrestrial based network.

[0095] The RIS controller (202c) may be residing in the BS (202), which may send all controlling / configuration related information to the RCU (204). In cases of UE-controlled mode (where the RIS (206) is controlled by the UE (208)), the RIS controller (202c) may be residing inside the UE (208) as the application layer.

[0096] The RCU (204) may receive all the controlling / configuration related information from the RIS controller (202c) and then further control / configure the RIS hardware (206a). The RIS controller (202c) and the RCU (204) may communicate over the R-l interface, which may act as a control link between the BS (202) and the RCU (204). The RCU (204) and the RIShardware (206a) may communicate over a R-2 interface. The R-l and R-2 interfaces may be wired or wireless (any radio) interface. The RCU (204) may be collocated with the BS (202) or with the RIS hardware (206a) depending on the implementation or deployment decisions.

[0097] The RIS hardware (206a) may be an actual RIS panel which reflects the actual data / signals between the BS (202) and the UE (208) over the Uu interface. The RIS hardware or panel (206a) may include a micro-controller which may be used to communicate to the RCU (204), in case of active RIS (206) to receive the necessary configurations, or to receive preconfigured configurations via the wired interface in cases of passive or hybrid RIS.

[0098] FIG. 3 illustrates an example schematic view (300) depicting the RIS coverage support, in accordance with an embodiment of the present disclosure.

[0099] With reference to FIG. 3, considering certain areas like behind some big buildings, behind a small hill structure, or at cell edges, where there may be a definite chance for signal degradation from the BS (202). In these areas, the BS signals may be improved by deploying the RIS (206) in an appropriate location with appropriate dimensions. Based on the dimension of the RIS (206), a beam width may be adjusted either vertically or horizontally to support one or more UEs (208) affected by signal degradation. The beams may also be steered either vertically or horizontally. Based on the dimension of RIS antenna elements, maximum steering of a beam both vertically and horizontally may create a virtual spherical area, which may be called as a RIS coverage area. Therefore, any users suffering from signal degradation within this kind of spherical coverage area may get improved signals from the BS (202) by using the reflected / regenerated beams from the associated RIS (206).

[0100] With reference to FIG. 3, a RIS-1 (206-1) may be deployed in such a way that, it may receive direct signal from the BS (202) and reflect / regenerate another beam to provide improved BS signal to the area behind the big building. Based on a number of antenna array elements supported by the RIS-1 (206-1), the RIS-1 coverage may be created virtually. Any UEs (208) within this coverage may get benefitted from the RIS-1 (206-1). Similarly, a RIS-2 (206-2) may be deployed closer to a small hill to aid the UEs (208) suffering behind the hill.

[0101] In the RIS-3 (206-3) case, some cell edge UEs (208) were getting degraded signal from the serving BS (202) and often getting disconnected abruptly. In such scenarios, the RIS-3 (206-3) may aid those cell edge UEs (208) to get stable and improved signals from the BS (202) consistently, thereby enabling those UEs (208) to get away from unnecessary call drops. The RIS-3 deployment may improve a capacity of a serving cell by extending the coverage based on the dimensions of the deployed RIS-3 (206-3).

[0102] FIG. 4 illustrate an example schematic view (400) depicting a RIS sharing scenario, in accordance with an embodiment of the present disclosure.

[0103] Within the cell coverage, one or more RISs (206) may be deployed based on a nature of a geographical area of the cell coverage. The dimension of such RISs (206) may be same or different, based on the dimension of the BS signal obstructing object (210). Indirectly, like a coverage hole size created by the obstructing object.

[0104] With reference to FIG. 4, the obstructing objects (210) may be a tall building, a small hill, attenuation all along the signal path up to the cell edge. The deployment of the RIS (206) may be either static, where the possible coverage holes within the cell coverage is know in advance and more or less permanent due to structures like building, tunnels, bridges, hills, trees, etc., and also may be dynamic, where the possible coverage hole within the cell coverage is temporary, like due to natural calamities, public safety scenarios, public gatherings, etc., in which cases, the RIS (206) may be deployed via Unmanned Aerial Vehicle (UAV), air balloons, satellites, etc.

[0105] FIG. 4 illustrates a scenario where a single RIS (206) may be shared by one or more cells. Here, a UE1 (208-1) may be connected to a cell of BS-1 (e.g., gNodeB-1) (202-1) and a UE2 (208-2) may be connected to cell of BS-2 (e.g., gNodeB-2) (202-2), where they experience the degradation of the direct signals from the respective BS. Since these two UEs (208-1, 208-2) are under the coverage of the same RIS controller (202c), the resources of the RIS (206) may be shared either statically or dynamically with both the cells.

[0106] When the UE1 (208-1) and the UE2 (208-2) reports their location information to the CU (202b) of the respective BS, either BS-1 (202-1) or BS-2 (202-2), the CU (202b) of the respective BS may check its RIS-cell mapping table, where the CU (202b) of the respective BS may find that same RIS coverage is applicable for both the UEs (208-1, 208-2). Therefore, the CU (202b) of the respective BS may decide to share the common RIS resources between these two UEs (208-1, 208-2). The CU (202b) of the respective BS may use an internal Artificial Intelligence / Machine Learning (AI / ML) strategy and decide to reserve ‘X%’ of RIS antenna resource elements to the UE1 (208-1) and ‘Y%’ of RIS antenna resource elements to the UE2 (208-1). This reservation of RIS antenna element resources may be communicated to the DU (202a) of the respective BS via 6G-F1 interface procedures. The DU (202a) may additionally request the UEs (208-1, 208-2) to report the location information along with CSI information and dynamically take the decision whether to use the RIS (206) to enhance the UE experience.

[0107] Once the UE (208-1 or 208-2) moves out of the RIS coverage area, the CU (202b) of the respective BS may release the reserved RIS resources and intimate the same to the DU (202a) of the respective BS, to plan its scheduling accordingly.

[0108] FIG. 5 illustrates an exemplary network architecture (500) for implementing a system for managing communication and beamforming towards a plurality of user equipments using the RIS, in accordance with an embodiment of the present disclosure.

[0109] With reference to FIG. 5, by way of example and not by not limitation, the exemplary network architecture (500) may include a plurality of computing devices (208-1, 208-2...208-N), which may be individually referred as the computing device (208) and collectively referred as the computing devices (208). The computing device (208) may be smart devices operating in a smart environment, for example, Internet of Things (loT) devices. The computing devices (208) may be associated with a plurality of users (212-1, 212-2...212-N). The plurality of users (212-1, 212-2...212-N) may be individually referred as the user (212) and collectively referred as the users (212). It may be appreciated that the computing device (208) may be interchangeably referred to as the UE.

[0110] In an embodiment, the UEs (208) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. The UEs (208) may be, for example, but are not limited to, a set-up box, a smart television (TV), a streaming media player, a media centre personal computer (PC), and so on. In an embodiment, the UEs (208) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users and / or entities, or any combination thereof.[oni] A person of ordinary skill in the art will appreciate that the UEs (208) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0112] In an embodiment, the UEs (208) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a headmounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or any type of portable computer, a mediaplaying device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UEs (208) may include, but is not limited to, any electrical, electronic, electromechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device, wherein the UEs (208) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (212) or the entity such as a touch pad, a touch enabled screen, an electronic pen, and the like.

[0113] A person of ordinary skill in the art will appreciate that the UEs (208) may not be restricted to the mentioned devices and various other devices may be used.

[0114] In an embodiment, the UEs (208) may communicate with the system (i.e., BS) (202) through a network (214). It may be appreciated that the system may be associated with the BS (202) or interchangeably referred to as the BS (202). The network (214) may be, for example, a telecommunication network. The network (214) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes, that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (214) may include, by way of example but not limitation, one or more of: a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a public-switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combination thereof.

[0115] In an embodiment, the system (202) may be configured to establish a connection with the RCU (204) and the UEs (208), and receive a plurality of parameters from the UEs (208), and RIS-related information from the RCU (204). The plurality of parameters may include, but not limited to, location information and mobility patterns of each UE (208), a direction of travel of each UE (208), and RIS coverage information. The system (202) may determine that at least one UE (e.g., 208-1) of the UEs (208) is within or approaching the RIS coverage area based on the plurality of parameters and the RIS-related information. Based on the determination, the system (208) may transmit a message indicating that the at least one UE (e.g., 208-1) is within or approaching the RIS coverage area to the RCU (204). The system (202)may enable the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

[0116] Although FIG. 5 shows exemplary components of the network architecture (500), in other embodiments, the network architecture (500) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 5. Additionally, or alternatively, one or more components of the network architecture (500) may perform functions described as being performed by one or more other components of the network architecture (500).

[0117] FIG. 6 illustrates an exemplary block diagram of a communication system architecture (600) with RIS support, in accordance with embodiments of the present disclosure.

[0118] With reference to FIG. 6, the communication system (600) may include the BS (i.e., the system) (202), the RCU (204), and the RIS (206). The BS (202) may include the DU (202a), the CU (202b), and the RIS controller (202c). The DU (202a) and the CU (202b) may be connected to the EMS / Network Management System (NMS) (216). The BS (i.e., the system) (202), the RCU (204), and the RIS (206) may be connected via the network (214) and the Rl, R2, Fl, Ng, and Xn interfaces.

[0119] The DU (202a) may support multiple UEs (208), and each UE (208) may be connected to one or more RCU (204) via the Rl interface. Each RCU (204) may be connected to one or more RIS hardware / panels (206a) via the R2 interface. When the RIS (206) powers on or wakes up, the RIS (206) may itself register to the respective RCU (204) that it is connected. The RCU (204) may assign a RIS-ID, and update a RIS ID table within the RCU (204) which may be then later updated to the BS (DU / CU) (202) in the subsequent link setup procedures.

[0120] The CU (202b) may maintains an RIS-cell mapping table for each supported cell context. Whenever, the RIS (206) is deployed in a cell, an entry may be created in the RIS-Cell mapping table. The entry may include the RIS-ID, RIS capabilities like supported number of antenna elements, mechanical / electrical tilt support, active / passive support, geographical location like altitude, azimuth, elevation, coverage capabilities of the RIS (206), sharable or not sharable, deployed in the cell edge / cell mid / cell centre regions, etc. All the information may be obtained either from Element Management System / Operations, Administration, and Maintenance (EMS / OAM) entity or directly from the RIS controller (202c) via the Rl interface during the Rl -Application (AP) setup procedure.

[0121] The UE (208) may frequently update its physical location information to the BS (CU) (202) either using a L2 message. Whenever the reported UE location is falling or comingcloser to any deployed RIS coverages, then the CU (202b) may intimate the UE details, its location information, the associated RIS information to the DU (202a). Then, the DU (202a) may create an entry in its RIS-UE mapping table and request the UE (208) to start reporting the current location information, mobility speed, direction of travel, etc., while reporting periodic or aperiodic CSI reports.

[0122] When the UE (208) sends the additional information, the DU (202a) may verify whether the UE (208) has entered the RIS coverage area and if it is under specific RIS (206). The associated measurement reports may indicate that the UE (208) may be better served by the RIS (206) than the BS (202) itself. Further, the DU (202a) may start coordinating with the associated RIS controller (202c) and the RCU (204), and reserve a number of antenna array elements for reflecting the specific beam towards the UE (208). If multiple UEs (208) are existing in the RIS coverage area, then the DU (202a) may decide if the same beam or different beams needs to be created to serve those UEs (208). The DU (202a) may decide whether to have only reflected beam or both direct beam and the reflected beam for the UE (208). In case the UE (208) is served by both direct and the reflected beams, then there may be no issues when the UE (208) is crossing from the RIS coverage area into a normal cell coverage area. But, when the UE (208) is served by only reflected beam, then the DU (202a) may closely monitor movements of the UE (208) crossing from the RIS coverage area into the normal cell coverage area and trigger an intra-cell inter-beam handover at the appropriate instance.

[0123] The CU (202b) may either activate or deactivate the usage of the given RIS (206) via the DU (202a) by sending RIS activate or RIS deactivate message to the DU (202a) via the Fl interface. The CU (202b) may update the RIS details and usages to the EMS frequently, which may be used for additional billing / maintenance purposes if needed.

[0124] FIG. 7 illustrates an exemplary block diagram (700) of a protocol architecture of the communication system (600), in accordance with embodiments of the present disclosure.

[0125] With reference to FIG. 7, an interface stack may be formed to make the DU (202a), the RCU (204), and the RIS (206) work together to create an open interface and to make sure all the nodes are inter-operable.

[0126] Major functions of the RIS control plane over the R1 / R2 interfaces may include, but not limited to, configuring / controlling the RIS hardware or panel (206a) and selection of the RIS hardware (206a) when multiple RISs (206) are connected to multiple BSs (202). Selection of the RIS (206) may also be done based on if the RIS (206) is looked for UL or DL or UL and DL. The R1 / R2 interface may act as the control link between the RIS controller (202c) and the RCU (204), and then between the RCU (204) and the RIS hardware (206a), respectively.

[0127] FIG. 7 illustrates the above mentioned R1 / R2 (DU-RCU-RIS) interface protocol stack that may be used to communicate with other nodes connected via the given interfaces. The R1 / R2 interfaces may be wired or wireless interfaces. Depending on the interface, necessary stacks may be made available as a part of the respective R1 / R2-AP interfaces which may then facilitate the necessary discovery and link establishment / setup procedures between the DU (202a) and the RCU (206) and between the RCU (204) and the RIS (206). The interfaces may be as described below:i. Uu I / F - Radio interface between the BS (202) and the UE (208) or between the BS (202) and the RIS (206), and then between the RIS (206) and the UE (204) for reflected beam.ii. RIS App - Application layer to interface between Uu stack and R1AP or between R1AP and R2AP.iii. R1 AP - Application part of the interface stack between the DU (202a) and the RCU (204).iv. R2 AP - Application part of the interface stack between the RCU (204) and the RIS (206).

[0128] FIG. 8 illustrates an exemplary block diagram (800) of a system for managing communication and beamforming towards the plurality of UEs (208) using the RIS (206), in accordance with embodiments of the present disclosure.

[0129] With reference to FIG. 8, in an embodiment, and as shown in FIG. 8, the system may be the BS (202) or associated with the BS (202). The system (202) may include one or more processors (802). The one or more processors (802) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processors (802) may be configured to fetch and execute computer-readable instructions stored in a memory (804) of the system (202). The memory (804) may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory (804) may include any non-transitory storage device including, for example, a volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read-Only Memory (EPROM), a flash memory, and the like.

[0130] In an embodiment, the system (202) may also include an interface(s) (806). The interface(s) (806) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (806)may facilitate communication of the system (202) with various devices coupled to it. The interface(s) (806) may also provide a communication pathway for one or more components of the system (202). Examples of such components include, but are not limited to, processing engine(s) (808) and a database (810).

[0131] In an embodiment, the processing engine(s) (808) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (808). In examples, described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (808) may be processor-executable instructions stored on a non-transitory machine -readable storage medium and the hardware for the one or more processors (802) may include a processing resource, to execute such instructions. In the present examples, the machine -readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (808). In such examples, the system (202) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (202) and the processing resource. In other examples, the processing engine(s) (808) may be implemented by an electronic circuitry.

[0132] In an embodiment, the database (810) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processors (802) or the processing engine(s) (808) or the system (202). In an embodiment, the database (810) may store data received from the UEs (208).

[0133] In an exemplary embodiment, the processing engine(s) (808) may include one or more engines selected from any of a data ingestion engine (812) and other units / engines (814). The other units / engines (814) may include, but are not limited to, a monitoring engine, a determination engine, and the like.

[0134] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), establish a connection with the RCU (204) and the UEs (208). The one or more processors (802) may establish the connection with the RCU (204) via a first interface, i.e., R1 interface. The RCU (204) may establish a connection with the RIS panel (206a) associated with the RIS (206) via a second interface, i.e., R2 interface to reflect actual data or signals between the system (202) and each of the plurality of UEs (208) over a third interface, i.e., Uu interface. The first interface and the second interface may be implemented as wired channels or wireless channels.

[0135] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), establish and manage the first and second interfaces with the RIS panel (206a) through the RCU (204) by receiving an RCU link setup request message including an array of RIS panel identifiers (RIS HW IDs) and an associated array of RIS capabilities from the RCU (204). Further, the one or more processors (802) may authenticate the RIS HW IDs by verifying the RIS HW IDs against one or more identifiers stored in the database (810) and determining a validity of the RIS HW IDs. Based on a successful authentication, the one or more processors (802) may generate a new RIS identifier (new RIS ID) for the RIS panel (206a), and map the new RIS ID to the corresponding RIS HW ID. The one or more processors (802) may store the new RIS ID, the corresponding RIS HW ID, and the associated array of RIS capabilities in an RCU RIS table. Furthermore, the one or more processors (802) may transmit an RCU link setup accept message including the new RIS ID mapped to the corresponding RIS HW ID and the associated array of RIS capabilities, along with a validation timer to the RCU (204). The RCU (204) may decode and send the RCU link setup accept message to the RIS panel (206a).

[0136] Based on an unsuccessful authentication, the one or more processors (802) may be configured to send an RCU link setup reject message with the array of RIS HW IDs to the RCU (204). The RCU (204) may decode and send the RCU link setup reject message to the RIS panel (206a).

[0137] Upon establishing the connection, the one or more processors (802) may, via the data ingestion engine (812), receive a plurality of parameters from each UE (208), and RIS-related information from the RCU (204). The plurality of parameters may include, but not limited to, location information and mobility patterns of each of the plurality of UEs (208), a direction of travel of each of the plurality of UEs (208), and RIS coverage information. In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), receive the RIS-related information from the RCU (204) once the RIS panel (206a) shares the RIS-related information as a configuration message with the RCU (204) via at least one of an 0AM entity or an Application Server (AS).

[0138] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), determine that at least one UE (208-1) of the plurality of UEs (208) is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information. Based on the determination, the one or more processors (802) may, via the data ingestion engine (812), transmit a message indicating that the at least one UE (208-1) is within or approaching the RIS coverage area to the RCU (204).

[0139] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), enable the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

[0140] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), enable the RCU (204) to manage beamforming towards the at least one UE (208-1) or the RIS panel (206a) by receiving capability information from the RCU (204) associated with the RIS panel (206a) in a serving area of the at least one UE (208-1). The one or more processors (802) may trigger a configuration towards the RIS panel (206a) in the serving area of the at least one UE (208-1) based on the capability information. Upon triggering the configuration towards the RIS panel (206a), the one or more processors (802) may transmit an RCU RIS resource control command with an array of configurations per RIS to the RCU (204). The RCU (204) may decode the array of configurations and configure the RIS panel (206a), send a RIS resource control command to the RIS panel (206a), and receive a RIS resource control accept response from the RIS panel (206a) when the RIS panel (206a) adheres to the array of configurations. Further, the one or more processors (802) may receive an RCU_RIS resource control accept response (response is a parameter) from the RCU (204), and initiate transmission of any or the combination of reflected beams and direct beams for managing beamforming towards the RIS panel (206a) or the at least one UE (208-1).

[0141] Information Element (IE) sent in the resource control command message to configure the RIS (206) with specific configuration parameters may include, but not limited to, time resource, beam ID, elemental weights, an index from codebook, activate, RCU keep alive timer, RIS keep alive timer, RCU keep alive maximum number of attempts, and RIS keep alive maximum number of attempts.

[0142] The response parameter may be sent along with a confirmation or rejection to the configurations sent during the RIS resource control command procedure. The response may be sent as a part of the RIS Resource Control Response and RCU RIS Resource Control Response. Response here may be both positive and negative as in if the configuration is applied and not applied, and if not applied what may be the possible error cause. The response may be stated as below:Response :: {<0 - Applied> |<1 - Not_Applied> {Error_Cause :: {0 - Link Failure;1 - Connection Failure;2 - HW Failure; } };

[0143] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), receive an RCU_RIS resource control reject response from the RCU (204), when the RCU (204) decodes the array of configurations and fails to adhere to the array of configurations. In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), receive an RCU_RIS resource control reject response from the RCU (204), when the RCU (204) decodes the array of configurations and configures the RIS panel (206a), sends the RIS resource control command to the RIS panel (206a), and receives a RIS resource control reject response from the RIS panel (206a) when the RIS panel (206a) fails to adhere to the array of configurations.

[0144] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), dynamically decide whether to use same beam or different beams to serve the plurality of UEs (208) within the RIS coverage area. When the at least one UE (208-1) is served only by the reflected beams, the one or more processors (802) may track a movement of the at least one UE (208-1), and initiate an intra-cell inter-beam handover when the at least one UE (208-1) crosses from the RIS coverage area into the normal cell coverage area.

[0145] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), create and update an RIS-UE mapping table including the plurality of parameters, based on the determination that the at least one UE (208-1) is within or approaching the RIS coverage area.

[0146] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), update one or more capabilities of the RIS panel (206a) when an RCU DU configuration update message with an array of capabilities per RIS is received from the RCU (204). Further, the one or more processors (802) may send an RCU_DU configuration update confirm message to the RCU (204), where the RCU (204) sends an RIS_RCU configuration update confirm message to the RIS panel (206a).

[0147] In an embodiment, when the system (202) queries for specific RIS capabilities from the RIS (206), the one or more processors (802) may be configured to send an RCU capability query request including an RIS ID and an array of specific RIS capabilities to the RCU (204). The RCU (204) may identify specific RIS panel (206a) by decoding the RCU capability query request, send a RIS capability query request to the RIS panel (206a), and receive a RIS capability query response including the array of specific RIS capabilities from the RIS (206). Further, the one or more processors (802) may receive an RCU capability query responseincluding the array of specific RIS capabilities from the RCU (204) once the RCU (204) receives the RIS capability query response from the RIS (206).

[0148] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), trigger the configuration to the RCU (204) and the RIS panel (206a) based on the RIS-related information, and configure keep alive timers to the RCU (204) and the RIS panel (206a) in the RCU RIS resource control command and the RIS resource control command, respectively. In an embodiment, the one or more processors (802) may be configured to monitor keep alive messages from the RCU (204) for every RCU keep alive timer expiry for a predetermined number of keep alive attempts, and trigger an RCU failure condition once the predetermined number of keep alive attempts are crossed.

[0149] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), receive the location information and the mobility patterns of each of the plurality of UEs (208) by sending a location update query request to each of the plurality of UEs (208) and receiving a location update query response including the location information and the mobility patterns from each of the plurality of UEs (208).

[0150] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), initiate activation or deactivation of the RIS panel (206a) by sending an RIS activation command or an RIS deactivation command to the RCU (204). The RCU (204) may decode the RIS activation command or the RIS deactivation command, send an RCU RIS activation command or an RCU RIS deactivation command to the RIS panel (206a), and receive an RCU RIS activation accept command or an RCU RIS deactivation accept command from the RIS panel (206a). Further, the one or more processors (802) may receive an RIS activation accept command or an RIS deactivation accept command from the RCU (204) once the RCU (204) receives the RCU RIS activation accept command or the RCU RIS deactivation accept command from the RIS panel (206a).

[0151] In an embodiment, the one or more processors (802) may, via the data ingestion engine (812), receive an RIS activation reject response or an RIS deactivation reject response from the RCU (204) during a failure in at least one of the RCU (204) or the RIS panel (206a).

[0152] Although FIG. 8 shows exemplary components of the system (202), in other embodiments, the system (202) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 8. Additionally, or alternatively, one or more components of the system (202) may perform functions described as being performed by one or more other components of the system (202).

[0153] FIG. 9A illustrates a sequential diagram (900A) depicting a link setup success case during a link setup procedure, in accordance with embodiments of the present disclosure.

[0154] With reference to FIG. 9A, R1 / R2 link setup procedure may be initiated by the RCU (204) towards the DU (202a), to establish the R1 / R2 link, respectively. The RCU may share the RIS capabilities to the DU (202a) via the link setup request message. The DU (202a) may authenticate the RIS (206) and allocate a unique RIS ID, and issue an activate command to the RCU (204) by sending a setup response message.

[0155] At 902a, the RIS (206) may be powered up individually and try to connect with the RCU (204). The RIS (206) may establish the control link connection based on the interface selected. If the interface is a wireless interface, for example, Wireless-Fidelity (Wi-Fi) or 5G New Radio (NR), then respective control procedure and protocol structures may be used to make the connection.

[0156] At 904a, the RIS (206) may send a RIS UinkSetupRequest with a pre-coded RIS HW ID and its capabilities (RIS capabilities) to the RCU (204). The RIS HW ID may be defined as Ris_hw_id:: { <20 digit alphanumeric string>}.

[0157] At 906a, the RCU (204) may decode the RIS HW ID from all the RIS (206) that are connected to the RCU (204) and forward the same to DU (202a).

[0158] At 908a, the RCU (204) may send an RCU UinkSetupReq with the Array of RIS HW ID and associated Array of RIS Capabilities to the DU (202a).

[0159] At 910a, the DU (202a) may authenticate all the received HW ID against the IDs stored in the database (810). If the authentication succeeds, then either the DU (202a) may generate a new RIS ID or the CU (202b) may generate the new RIS ID and share the new RIS ID with the DU (202a) to be shared with the respective RIS. Finally, the DU (202a) may store the new RIS ID, HW ID and respective capabilities at the RCU RIS table. The RIS ID may be a unique identification of the RIS hardware (206a) as assigned by the network (CU or DU based on the implementation). The RIS ID may be defined as Ris id :: {<20 digit pseudo random generated unique ID>}.

[0160] At 912a, the DU (202a) may send an RCU_LinkSetupConfirm message with the array of RIS ID mapping to the RIS HW ID, RCU ID, the DU ID, and the array of activate command along with its corresponding validation period. The DU ID may be a unique identifier assigned to the DU (202a), so that the RCU (204) may recognize the commands received from the respective DU (202a) during any signalling exchange procedure. The RCU ID may be a pseudo random generated 20-digit unique identification number as assigned by the BS (202) (CU or DU) during the link setup or registration procedure.

[0161] At 914a, the RCU (204) may decode and send an RIS LinkSetupConfirm message to a given RIS (206) with its respective RIS ID along with the activate command and its validity timer.

[0162] At 916a, the DU (202a) may send CU_RIS_LinkSetupConfirm message with the array of RIS ID, so that the array of RIS ID may be stored in the CU (202b) under RCU RIS cell mapping table.

[0163] FIG. 9B illustrates a sequential diagram (900B) depicting a link setup failure case during the link setup procedure when an authentication fails against RIS HW ID, in accordance with embodiments of the present disclosure.

[0164] With reference to FIG. 9B, the link setup procedure may handle the failure case where a link setup failure happens as the authentication fails against the RIS HW ID.

[0165] At 902b, the RIS (206) may be powered up individually and try to connect with the RCU (204). The RIS (206) may establish the control link connection based on the interface selected. If the interface is the wireless interface, for example, Wi-Fi or 5G NR, then respective control procedure and protocol structures may be used to make the connection.

[0166] At 904b, the RIS (206) may send a RIS LinkSetupRequest with a pre-coded RIS HW ID and its capabilities (RIS Capabilities) to the RCU (204).

[0167] At 906b, the RCU (204) may decode the RIS HW ID from all the RIS (206) that are connected to the RCU (204) and forward the same to RCU (204).

[0168] At 908b, the RCU (204) may send a RCU LinkSetupReq with the Array of RIS ID and associated Array of RIS Capabilities to the DU (202a).

[0169] At 910b, the DU (202a) may authenticate the received HW ID against the stored HW ID.

[0170] At 912b, if the authentication fails, the DU (202a) may send an RCU LinkSetupReject with a list or Array of RIS HW ID to the RCU (204).

[0171] At 914b, the RCU (204) may send a RIS UinkSetupReject response to the respective RIS (206) along with the RIS HW ID.

[0172] Error cause may be sent as a part of the RIS UinkSetupReject when there is the link setup failure. The error cause may be as stated below:Error_Cuase :: {0 - Max Conn Reached; Max. number of RIS connections a given RCU can handle has already reached.1 - RCU Deactivated; RCU is deactivated by the DU (BS) and yet to be activated2 - Invalid RIS; RIS capabilities or Operation mode or control mode is not right for the given RCU to control the RIS.3 - Misc_Cause; For any other unknown reasons.}

[0173] FIG. 9C illustrates a sequential diagram (900C) depicting a link setup failure case during the link setup procedure when an RCU rejects a link establishment procedure, in accordance with embodiments of the present disclosure.

[0174] With reference to FIG. 9C, the link setup procedure may handle a link setup reject procedure when the RCU (204) itself rejects the link establishment procedure.

[0175] At 902c, the RIS (206) may be powered up individually and try to connect with the RCU (204). The RIS (206) may establish the control link connection based on the interface selected. If the interface is the wireless interface, for example Wi-Fi or 5G NR, then respective control procedure and protocol structures may be used to make the connection.

[0176] At 904c, the RIS (206) may send a RIS LinkSetupRequest with a pre-coded RIS HW ID and its capabilities (RIS Capabilities) to the RCU (204).

[0177] At 906c, the RCU (204) may decode the RIS HW ID from all the RIS (206) that are connected to the RCU (204) and reject the establishment for various error causes, like - • Max Conn Reached - Max. number of RIS connections a given RCU can handle has already reached.• RCU_Deactivated - the RCU (204) is deactivated by the DU (202a) and yet to be activated.• Invalid RIS - RIS capabilities or operation mode or control mode is not right for the given RCU (204) to control the RIS (206).• Misc_Cause - For any other unknown reasons.

[0178] At 908c, the RCU (204) may send the RIS LinkSetupReject response with the respective RIS HW ID to the RIS (206).

[0179] FIG. 10A illustrates a sequential diagram (1000A) depicting a success case during a RIS resource control command procedure, in accordance with embodiments of the present disclosure.

[0180] The RIS resource control command procedure may be initiated by the DU (202a) towards the RCU (204), to command the reservation of antenna array elements for communication with the DU (202a) and to communicate with the UE (208) directly. One set of antenna array may be reserved for communications with the DU (202a) for a particular UE (208) and another set of antenna array may be reserved for communications with the UE (208) directly.Further, the DU (202a) may share the details like horizontal and vertical beam width, horizontal and vertical beam steering position, and altitude of the UE (208) to point the beam towards the UE (208), etc.

[0181] In the RIS resource control command procedure, the DU (202a), via the RCU (204), may configure the RIS (206) successfully with all the necessary configurations so that the DU (202a) may start transmitting the control / data signals / beams to the RIS (206) and the RIS (206) may reflect the same towards the target UE (208).

[0182] With reference to FIG. 10A, at 1002a, the DU (202a) after decoding the capabilities of the given RIS (206) may trigger certain configuration towards the RIS (206) serving in an area where the target UE (208) is located. At times, the trigger may be also from the CU side based on a measurement report received from the UEs (208) so that the DU (202a) may configure the RIS (206) further accordingly.

[0183] At 1004a, the DU (202) may send a RCU RIS Resource Control Command with an array of configurations per RIS to the RCU (204). The DU (202a) or the BS (202) may update the beamforming matrix at the RIS (206) using the control information. For example, the RIS (206) may perform a total of n different reflected beams at different time instances. The BS (202) may be aware of the total number of different beams (n) from the capability reporting step. The RIS (206) may form 3 beams in total, as shown in below figure. Each beam may be identified by a unique beam identifier (Beam ID: Beam 1, Beam 2 and Beam 3). The BS (202) may send the Beam ID along with its time of activation (tl, t2 and t3) as a control message to the RCU (204).

[0184] Example set of configurations may be defined in Table 1.Information Element Status DescriptionIdentity Information M RIS IDConfigurations M RIS configurations are transmitter position, desired receive angle,desired number of beams, frequencyof operation, and desired mode ofoperation.Table 1

[0185] At 1006a, the RCU (204) may decode the configurations and configure the respective RIS (206) based on the configurations received from the DU (202a).

[0186] At 1008a, the RCU (204) may send a RIS Resource Control Command with the configurations meant for the given RIS (206) to the RIS panel (206a).

[0187] At 1010a, the RIS (206), upon confirming the configurations, may send a RIS Resource Control Response with an appropriate response as a parameter.

[0188] At 1012a, the RCU (204) may send an RCU RIS Resource Control Response with the array of responses from different RIS as available to the DU (202a) or the BS (202). As the DU (202a) or the BS (202) receives the RCU_RIS_Resource_Control_Response, the DU (202a) or the BS (202) may start transmitting the beam towards the RIS (206), and may or may not continue direct transmission to the target UE (208). The RIS (206) may start receiving the beam and reflects it towards the target UE (208) post necessary processing.

[0189] FIG. 10B illustrates a sequential diagram (1000B) depicting a failure case when the RCU (204) is unable to adhere to configurations shared by the system (202) to the RCU (204), in accordance with embodiments of the present disclosure.

[0190] With reference to FIG. 10B, the RIS resource control command procedure may handle a failure scenario when the RCU (204) is unable to adhere to the configurations shared by the DU (202a) to the RCU (204).

[0191] At 1002b, the DU (202a), after decoding the capabilities of the given RIS (206) and receiving certain feedback information from the UE (208), may trigger certain configuration towards the RIS (206) serving in the area where the target UE (208) is located.

[0192] At 1004b, the DU (202a) may send an RCU RIS Resource Control Command with an array of configurations per RIS to the RCU (204).

[0193] At 1006b, the RCU (204) may decode the configurations but is unable to adhere to apply the said configurations, and may reject the RCU RIS Resource Control Command.

[0194] At 1008b, the RCU (204) may send an RCU RIS Resource Control Response with an appropriate response to the DU (202a).

[0195] FIG. 10C illustrates a sequential diagram (1000C) depicting a failure case when the RIS (206) is unable to adhere to the configurations shared by the system (202) to the RCU(204) and then from the RCU (204) to the RIS (206), in accordance with embodiments of the present disclosure.

[0196] With reference to FIG. 10C, RIS resource control command procedure may handle a negative scenario when the RIS (206) is unable to adhere to the configurations shared by the DU (202a) to the RCU (204) and then from the RCU (204) to the RIS (206).

[0197] At 1002c, the DU (202a), after decoding the capabilities of the given RIS (206) and receiving certain feedback information from the UE (208), may trigger certain configuration towards the RIS (206) serving in the area where the target UE (208) is located.

[0198] At 1004c, the DU (202a) may send a RCU RIS Resource Control Command with an array of configurations per RIS to the RCU (204).

[0199] At 1006c, the RCU (204) may decode the configurations and configure the respective RIS (206) based on the configurations received from the DU (202).

[0200] At 1008c, the RCU (204) may send a RIS Resource Control Command with the configurations meant for the given RIS (206). When the RIS (206) is unable to adhere to applying the said configurations, the RIS (206) may respond back with a negative response.

[0201] At 1010c, the RIS (206) may send a RIS Resource Control Response to the RCU (204) with an appropriate response.

[0202] At 1012c, the RCU (204) may send a RIS Resource Control Response with an appropriate response to the DU (202).

[0203] FIG. 11A illustrates a sequential diagram (1100A) depicting a capability exchange procedure, in accordance with embodiments of the present disclosure.

[0204] All the RIS capability related information may be initially shared by the RIS (206) to the RCU (204), and from the RCU (204) to the DU (202a) or the BS (202) during the link setup procedure. Same capability may also be sent as a configuration message via the 0AM entity or via the AS. At 1102a, the 0AM entity and the AS when updated with the latest capabilities of the RIS (206) may update its capabilities to the RCU (204) via the DU (202a) using the RIS Capability Configuration message.

[0205] FIG. 11B illustrates a sequential diagram (1100B) depicting a configuration update procedure of the RIS (206), in accordance with embodiments of the present disclosure.

[0206] The configuration update procedure of the RIS (206) may handle a case where any change in the capabilities at the RIS side may be updated to the RCU (204) using the configuration update message and likewise to the DU (202a).

[0207] With reference to FIG. 1 IB, at 1102b, any change in the capabilities of the RIS (204) may be intimated to the RCU (204) via a RIS_RCU_ConfigurationUpdate message.

[0208] At 1104b, the RCU (204) may store the updated capabilities inside its RIS table.

[0209] At 1106b, the RCU (204) may update the same to the DU (202a) by sending an RCU DU ConfiguraitonUpdate message with an array of capabilities per RIS.

[0210] At 1108b, the DU (202a) may update its RIS table with the updated configuration / capabilities per RIS.

[0211] At 1110b, the DU (202a) may send confirmation on updating the RIS capabilities in its database / table by sending an RCU_DUConfigurationUpdateConfirm message to the RCU (204).

[0212] At 1112b, the RCU (204) may send an RIS RCU ConfiguraitonUpdateConfirm message to the RIS (206).

[0213] FIG. 11C illustrates a sequential diagram (1100C) depicting capability query and response procedures, in accordance with embodiments of the present disclosure.

[0214] In certain circumstance, the RCU (204) may need to know certain capability related information about the RIS (206). In such cases, the RCU (204) may send a request to the RIS hardware (206a) to send the capability information, and the RIS hardware (206a) may respond with the requested capability information. To understand capabilities available in the RIS (206), a set of capability queries may be required to be sent and the RIS (206) may respond with a capability response message adding the capabilities that were queried.

[0215] With reference to FIG. 11C, at 1102c, the DU (202a) may query for specific RIS capabilities on need basis (Query Information) for a specific set of RIS identified via a set of RIS ID using RCU Capability Query.

[0216] At 1104c, the RCU (204) may further identify the specific RIS (206) by decoding the RIS ID sent by the DU (202a) and query for its specific capabilities via RIS Capability Query request.

[0217] At 1106c, the RIS (206) may respond with the capability of specific items (response information) using RIS CapabilityRsp message.

[0218] At 1108c, the RCU (204) may aggregate the RIS information and share with the DU (202a) using RCU CapabilityRsp message with all the RIS’s response information as a set / array.

[0219] Examples of query - response cases are presented below for reference:• Capability Query 1 - RIS position and orientation, incident angle range (degree), supported frequency of operation, range of received signal strength, beam splitting information are required.• Capability Response 1 - The RIS (206) may send a response in the similar sequence i.e. RIS position coordinates (r, 0, cp) and orientation (V / H), a range of incident angle supported (degree), a supported frequency of operation, a range of received signal strength, beam splitting possibility information may be sent to the RIS controller (202c).• In query 2, the range of receive angle (degrees) mode of operation are inquired. Mode of operation may be incremental or absolute. In incremental mode, the beam angle may be adjusted based on the earlier beam angle. In absolute mode, the beam angle may be directly set.• Capability Query 2 - Based on the capability response 1, the RIS controller (202c) may now send the capability query 2 where the range of receiver angle (degree), the mode of operation may be asked.• Capability Response 2 - In the corresponding response, the range of receiver angle and supported mode of operation may be intimated by the RIS controller (202c).

[0220] FIG. 12 illustrates a sequential diagram (1200) depicting a keep alive procedure, in accordance with embodiments of the present disclosure.

[0221] In case of any failures due to which the given RIS (206) or the RCU (204) shuts down or stops working, then the same needs to be known to the network (214). To achieve the same, the RIS (206) and / or the RCU (204) may send the keep alive messages that are sent periodically over R1 and R2 interfaces. The periodicity may be as set by the DU (202a) during the initial control command procedure.

[0222] At 1202, the DU (202a) may trigger the configuration to the RIS (206) and the RCU (204) based on the capabilities received so far and configure keep alive timers to the RCU (204) and the RIS (206) as a part of the resource control command procedure.

[0223] At 1204, the RCU (204) and the RIS (206) may apply the keep alive timer as per the above step 1202. The RIS (206) may send the keep alive message to the RCU (204).

[0224] At 1206, when the keep alive timer of the RCU (204) expires, the RCU (204) may send the keep alive message to the DU (202a).

[0225] At 1208, the keep alive timer of the RIS (206) may be expired and step 1204 may be repeated.

[0226] At 1210, the keep alive timer of the RCU (204) may be expired and step 1206 may be repeated.

[0227] FIG. 13 illustrates a sequential diagram (1300) depicting a system configuration update procedure, in accordance with embodiments of the present disclosure.

[0228] The DU configuration update procedure may be initiated by the DU (202a) towards the CU (202b), indicating the latest set of RIS’s deployed and sharing their details. The CU (202b) may create the entries for those RIS’s which are new and allocate a new RIS ID for each RIS (206), and update the details of other RIS’s, which are already existing in the RIS-Cell mapping table. The CU (202b) may respond with the DU configuration update confirm message with all the list of newly allocated RIS-IDs associated with newly established RIS’s.

[0229] With reference to FIG. 13, at 1302, the DU (202a) may send updated capabilities of the given RIS (206) or of a set of RISs (206) to the CU (202b) via DU_configurationUpdate message. In the same message there may be updates on the new RIS entries also.

[0230] At 1304, the CU (202b) may create entries for new RIS ID in its mapping table and update the table for an existing one.

[0231] At 1306, if the update is done successfully, then the CU (202b) may send a confirmation to the DU (202a) using DU_ConfiguraitonUpdate_Confirm message with the array of RIS ID as reference.

[0232] At 1308, the RIS table at the DU (202a) may be updated either before step 1302 or at step 1308.

[0233] FIG. 14 illustrates a sequential diagram (1400) depicting a location query procedure, in accordance with embodiments of the present disclosure.

[0234] The location query procedure may be initiated by the CU (202b) towards the DU (202a). Whenever one or more UEs (208) are detected in the proximity of the specific RIS coverages, the CU (202b) may initiate the coordination with specific RISs, with respect to the identified target UEs (208).

[0235] With reference to FIG. 14, at 1402, the CU (202b) may detect that the one more UEs (208) are in the range of the given RIS (206) via regular triangulation methods based on received measurement report. This may not have larger accuracy in terms of UEs specific location but may give an approximate range if the UE (208) is in the range of RIS (206) or not.

[0236] At 1404, with the trigger, the CU (202b) may send location query message for the set of UEs (208) and for associated RIS ID. The UEs (208) may send the location information (in the order of Global Positioning System (GPS) based latitude / longitude and then Observed Time Difference of Arrival (OTDOA), eCelllD based and Cell ID based information when GPS is not supported by the given UE (208)) to the CU (202b). This may be done by sending the location query message.

[0237] At 1406, the UE (208) may start adding the location information in the measurement report.

[0238] At 1408, the UE (208) may respond with the location information by adding the same in the measurement report message.

[0239] At 1410, based on the location information received as a part of the measurement report message, the CU (202b) may continuously monitor the same against the RIS location information stored in its database. If the UE location matches that of the RIS range based on its location, then the CU (202b) may trigger the configuration message to the DU (202a) to further configure the respective RIS (206).

[0240] At 1412, subsequently, the CU (202b) may trigger the configuration of the RIS (206) to the DU (202a) by sending CU_Resource_ControlCommand message which further triggers the RCU RIS RadioResourceCntrol Command.

[0241] FIG. 15A illustrates a sequential diagram (1500A) depicting an activation / deactivation procedure of the RIS (206) from the system (202), in accordance with embodiments of the present disclosure.

[0242] The activation / deactivation procedure may be initiated by the CU (202b) towards the DU (202a), to activate or deactivate the given RIS (206). The activation / deactivation procedure may be predominantly used during energy saving scenarios and during maintenance scenarios. During the link detection procedure, the CU (202b) / DU (202a) may have already indicate the activate or deactivation status of the given RIS (206) along with its validity timer. The link detection procedure may help in subsequent activation or deactivation procedure.

[0243] At 1502a, the CU (202b) may send a CU_RIS_Activation_command to the DU (202a) with activate command (activate_cmd) and its validity timer for the set of RIS (206) to the respective DUs (202a) which is controlling the said RISs (206). The activate_cmd may be a parameter sent either during the link setup procedure or during a dedicated activate / deactivate procedure, i.e., Active_Cmd :: { 0 - Deactivate | 1 - Activate}. The validity timer may indicate for how long the RIS (206) may be in active or enable state before it deactivates or disables by itself. Deactivate may be different from power off. Here, the RIS functionalities may be disabled for the period as indicated by the BS (202), but the interface link may still be present to receive further commands to get enabled or activated again. That is, Active_Validity_timer :: {<0123456789 in ms>}.

[0244] At 1504a, the DU (202a) may initiate the activation / deactivation procedure to the respective RIS (206).

[0245] At 1506a, the DU (202a) may send a DU RIS Activation Command to the RCU (204) with all the activate command and its validity timer for a set of RIS (206) connected to the respective RCUs (204) as per the stored table.

[0246] At 1508a, the RCU (204) may accordingly decode the message and send an RCU RIS Activation cmd to the respective RISs (206) with the activate command and its validity timer.

[0247] At 1510a, the RIS (206) may send an RCU RIS Activation CommandAccept response to the RCU (204) upon successful execution of the command.

[0248] Likewise, at 1512a, the RCU (204) may send an DU_RIS_Activation_CommandAccept response to the DU (202a) upon successful execution of the command.

[0249] Likewise, at 1514a, the DU (202a) may send a CU_RIS_Activation_CommandAccept response to the CU (202b) upon successful execution of the command.

[0250] FIG. 15B illustrates a sequential diagram (1500B) depicting an activation / deactivation failure procedure, in accordance with embodiments of the present disclosure.

[0251] In the activation / deactivation failure procedure, when the activation command is not successfully executed at different stages of the above nodes (as in at the DU (202a), the RCU (204), or at the RIS (206) level), respective nodes may send RIS_Activation_CommandReject message as seen below:

[0252] At 1502b, the CU (202b) may send an CU RIS Activation command to the DU (202a) with activate command and its validity timer for the set of RIS (206) to the respective DUs (202a) which is controlling the said RISs (206).

[0253] At 1504b, the DU (202a) may initiate the activation / deactivation procedure to the respective RIS (206).

[0254] At 1506b- 1 : Failure at DU (202a) - For any failure at the DU side, the DU (202a) may send an CU RIS Activation CommandRej response with appropriate reject reason to the CU (202b).

[0255] At 1506b-2: Failure at RCU (204) - the DU (202a) may send the DU RIS Activation Command to the RCU (204) with all the activate command and its validity timer for the set of RIS (206) connected to the respective RCUs (204) as per the stored table.

[0256] At 1508b-2, the RCU (204) may accordingly decode the message and in case of any failure, sends a DU RIS Activation commandRej response to the DU (202a) with appropriate set of rejection cause if failure happened at multiple RCUs (204).

[0257] At 151 Ob-2, the DU (202a) may send the CU RIS Activation CommandRej response to the CU (202b) with appropriate set of rejection cause as an array if the failure happened at multiple RCUs (204).

[0258] At 1506b-3, Failure at RIS (206) - the DU (202a) may send the DU RIS Activation Command to the RCU (204) with all the activate command and its validity timer for the set of RIS (206) connected to the respective RCUs (204) as per the stored table.

[0259] At 1508b-3, the RCU (204) may accordingly decode the message and send the RCU RIS Activation cmd to the respective RISs (206) with the activate command and its validity timer.

[0260] At 1510b-3, the RIS (206) may send the RCU RIS Activation CommandRej response to the RCU (204) in case of any failure with appropriate rejection cause.

[0261] At 1512b-3, accordingly, the RCU (204) may send the DU_RIS_Activation_commandRej response to the DU (202a) with appropriate set of rejection cause if failure happened at multiple RCUs (204).

[0262] At 1514b-3, accordingly, the DU (202a) may send a CU_RIS_Activation_CommandRej response to the CU (202b) with appropriate set of rejection cause if the failure happened at multiple RCUs / RIS’s.

[0263] The rejection cause or the reject cause may be a parameter sent as a part of the activation reject message. Rejection may be due to failure or activation of the RIS (206) at the DU (202a), the RCU (204), and at the RIS (206) level. Depending on the failure, at what level, the Rej Cause may be different and same is finally updated to the OAM / EMS. The Rej Cause may be as stated below:RejCasue :: {0 - Failure at RIS {0-RIS_Not_A vailable;1-RIS HW Failure OR RIS Not Responding;2-Other Reasons; } |1 -Failure at RCU {0-RCU_Not_A vailable;1-RCU HW Failure OR RCU Not Responding;2-Other Reasons; } |2-Failure at DU {0-DU_Not_A vailable ;l-DU HW Failure OR DU Not Responding;2-Other Reasons; }};

[0264] FIG. 16 illustrates a sequential diagram (1600) depicting a failure indication procedure to EMS / OAM, in accordance with embodiments of the present disclosure.

[0265] If any fault indication at the RIS (206) / RCU (204) needs to be informed at the EMS / OAM level, then the same may be notified by the DU (202a) or the CU (202b) at the BS (202) to the OAM / EMS using the predefined interface using Simple Network Management Protocol (SNMP) or Technical Report 069 (TR069), etc.

[0266] At 1602, the DU (202a) may trigger configuration of the RIS (206) based on capabilities received so far and configure the keep alive timers along with the other configurations using RIS Resource Control Command procedures.

[0267] At 1604-1, Failure at RIS side: the RCU (204) may monitor the keep alive messages from the RIS (206) for every RIS keep alive timer expiry for a maximum number of keep alive attempts. Once the maximum number of attempts are crossed, the RCU (204) may trigger a RIS failure condition. At 1606-1, the RCU (204) may send a RIS Failure lnd to the DU (202a). Accordingly, at 1608-1, the DU (202a) may send a RIS_failure_ind for the set of RIS IDs to the CU (202b). Similarly, at 1610-1, the CU (202b) may send RIS failure ind to the 0AM entity with the set of RIS IDs.

[0268] At 1604-2, Alt: Failure at RIS side: the DU (202a) may monitor for RCU keep alive messages from the RCU (204) for every RCU keep alive timer expiry for a maximum number of keep alive attempts. Once the maximum number of attempts are crossed, the DU (202a) may trigger an RCU failure condition. At 1606-2, the DU (202a) may send the RCU_Failure_Ind to the CU (202b). Similarly, at 1608-2, the CU (202b) may send RCU Failure ind to the 0AM entity with the set of RCU IDs.

[0269] FIG. 17 illustrates an exemplary computer system (1700) in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.

[0270] As shown in FIG. 17, the computer system (1700) may include an external storage device (1710), abus (1720), amain memory (1730), a read-only memory (1740), amass storage device (1750), a communication port(s) (1760), and a processor (1770). A person skilled in the art will appreciate that the computer system (1700) may include more than one processor (1770) and communication ports (1760). The processor (1770) may include various modules associated with embodiments of the present disclosure. The communication port(s) (1760) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernetport, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (1760) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (1700) connects.

[0271] In an embodiment, the main memory (1730) may be a Random-Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (1740) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (1770). The mass storage device (1750) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0272] In an embodiment, the bus (1720) may communicatively couple the processor(s) (1770) with the othermemory, storage, and communication blocks. The bus (1720) maybe, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (1770) to the computer system (1700).

[0273] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (1720) to support direct operator interaction with the computer system (1700). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (1760). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (1700) limit the scope of the present disclosure.

[0274] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0275] The present disclosure manages communication and beamforming towards a plurality of user equipments using a Reconfigurable Intelligent Surface (RIS).

[0276] The present disclosure reconfigures wireless propagation environments using Intelligent Reflecting Surfaces (IRS) or the RIS.

[0277] The present disclosure performs RIS tilt management (mechanical and digital tilt) so that a plurality of users can be served by a deployed RIS.

[0278] The present disclosure discovers and registers the RIS to a base station using a link setup procedure, and exchanges capability information between the RIS and the base station.

[0279] The present disclosure determines whether the user equipment is within or approaching a RIS coverage area based on a plurality of parameters.

[0280] The present disclosure transmits a message indicating that the user equipment is within or approaching the RIS coverage area to a RIS controller unit (RCU).

[0281] The present disclosure enables the RCU to reserve antenna array elements of the RCU to directly communicate with the UE, and configure the RIS for managing beamforming towards the UE, based on the message.

Claims

We Claim:

1. A system (202) for managing communication and beamforming towards a plurality of User Equipments (UEs) (208) using a Reconfigurable Intelligent Surface (RIS) (206), the system (202) comprising:one or more processors (802); anda memory (804) operatively coupled to the one or more processors (802), wherein the memory (804) comprises processor-executable instructions, which on execution, cause the one or more processors (802) to:establish a connection with a RIS controller unit (RCU) (204) and the plurality of UEs (208);upon establishing the connection, receive a plurality of parameters from each of the plurality of UEs (208), and RIS-related information from the RCU (204);determine that at least one UE (208-1) of the plurality of UEs (208) is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information;based on the determination, transmit a message indicating that the at least one UE (208-1) is within or approaching the RIS coverage area to the RCU (204); andenable the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

2. The system (202) as claimed in claim 1, wherein the one or more processors (802) are configured to dynamically decide whether to use same beam or different beams to serve the plurality of UEs (208) within the RIS coverage area.

3. The system (202) as claimed in claim 1, wherein when the at least one UE (208-1) is served only by reflected beams, the one or more processors (802) are configured to monitor a movement of the at least one UE (208-1), and initiate an intra-cell inter-beam handover when the at least one UE (208-1) crosses from the RIS coverage area into a normal cell coverage area.

4. The system (202) as claimed in claim 1, wherein the plurality of parameters comprises at least one of: location information and mobility patterns of each of the plurality of UEs (208), a direction of travel of each of the plurality of UEs (208), and RIS coverage information.

5. The system (202) as claimed in claim 1, wherein based on the determination that the at least one UE (208-1) is within or approaching the RIS coverage area, the one or more processors (802) are configured to create and update an RIS-UE mapping table comprising the plurality of parameters.

6. The system (202) as claimed in claim 1, wherein the one or more processors (802) are configured to establish the connection with the RCU (204) via a first interface, and wherein the RCU (204) establishes a connection with a RIS panel (206a) associated with the RIS (206) via a second interface, to reflect actual data or signals between the system (202) and each of the plurality of UEs (208) over a third interface.

7. The system (202) as claimed in claim 6, wherein the first interface and the second interface are implemented as at least one of wired channels or wireless channels.

8. The system (202) as claimed in claim 6, wherein the one or more processors (802) are to establish and manage the connection of the first and second interfaces with the RIS panel (206a) through the RCU (204) by being configured to:receive an RCU link setup request message comprising an array of RIS panel identifiers (RIS HW IDs) and an associated array of RIS capabilities from the RCU (204);authenticate the RIS HW IDs by verifying the RIS HW IDs against one or more identifiers stored in a database and determining a validity of the RIS HW IDs;based on a successful authentication, generate anew RIS identifier (new RIS ID) for the RIS panel (206a);map the new RIS ID to the corresponding RIS HW ID, and store the new RIS ID, the corresponding RIS HW ID, and the associated array of RIS capabilities in an RCU RIS table; andtransmit an RCU link setup accept message comprising the new RIS ID mapped to the corresponding RIS HW ID and the associated array of RIS capabilities, along with a validation timer to the RCU (204), wherein the RCU (204) decodes and sends the RCU link setup accept message to the RIS panel (206a).

9. The system (202) as claimed in claim 8, wherein based on an unsuccessful authentication, the one or more processors (802) are configured to send an RCU link setup reject message with the array of RIS HW IDs to the RCU (204), and wherein the RCU (204) decodes and sends the RCU link setup reject message to the RIS panel (206a).

10. The system (202) as claimed in claim 1, wherein the one or more processors (802) are to enable the RCU (204) to manage beamforming towards the at least one UE (208-1) by being configured to:receive capability information from the RCU (204) associated with the RIS panel (206a) in a serving area of the at least one UE (208-1);trigger a configuration towards the RIS panel (206a) in the serving area of the at least one UE (208-1) based on the capability information;upon triggering the configuration towards the RIS panel (206a), transmit an RCU RIS resource control command with an array of configurations per RIS to the RCU (204), wherein the RCU (204) decodes the array of configurations and configures the RIS panel (206a), sends a RIS resource control command to the RIS panel (206a), and receives a RIS resource control accept response from the RIS panel (206a) when the RIS panel (206a) adheres to the array of configurations;receive an RCU_RIS resource control accept response from the RCU (204); and initiate transmission of any or combination of reflected beams and direct beams for managing beamforming towards the RIS panel (206a) or the at least one UE (208-1).

11. The system (202) as claimed in claim 10, wherein the one or more processors (802) are configured to receive an RCU_RIS resource control reject response from the RCU (204), when the RCU (204) decodes the array of configurations and fails to adhere to the array of configurations.

12. The system (202) as claimed in claim 10, wherein the one or more processors (802) are configured to receive an RCU_RIS resource control reject response from the RCU (204), when the RCU (204) decodes the array of configurations and configures the RIS panel (206a), sends the RIS resource control command to the RIS panel (206a), and receives a RIS resource control reject response from the RIS panel (206a) when the RIS panel (206a) fails to adhere to the array of configurations.

13. The system (202) as claimed in claim 1, wherein the one or more processors (802) are configured to receive the RIS-related information from the RCU (204) once the RIS panel (206a) shares the RIS-related information as a configuration message with the RCU (204) via at least one of an Operations, Administration, and Maintenance (0AM) entity or an Application Server (AS).

14. The system (202) as claimed in claim 1, wherein the one or more processors (802) are configured to update one or more capabilities of the RIS panel (206a) when an RCU DU configuration update message with an array of capabilities per RIS is received from the RCU(204), and sends an RCU_DU configuration update confirm message to the RCU (204), and wherein the RCU (204) sends an RIS RCU configuration update confirm message to the RIS panel (206a).

15. The system (202) as claimed in claim 1, wherein when the system (202) queries for specific RIS capabilities from the RIS (206), the one or more processors (802) are configured to:send an RCU capability query request comprising an RIS ID and an array of specific RIS capabilities to the RCU (204), wherein the RCU (204) identifies specific RIS panel (206a) by decoding the RCU capability query request, sends a RIS capability query request to the RIS panel (206a), and receives a RIS capability query response comprising the array of specific RIS capabilities from the RIS (206); andreceive an RCU capability query response comprising the array of specific RIS capabilities from the RCU (204) once the RCU (204) receives the RIS capability query response from the RIS (206).

16. The system (202) as claimed in claim 10, wherein the one or more processors (802) are configured to trigger the configuration to the RCU (204) and the RIS panel (206a) based on the RIS-related information, and configure keep alive timers to the RCU (204) and the RIS panel (206a) in the RCU RIS resource control command and the RIS resource control command, respectively.

17. The system (202) as claimed in claim 16, wherein the one or more processors (802) are configured to monitor keep alive messages from the RCU (204) for every RCU keep alive timer expiry for a predetermined number of keep alive attempts, and trigger an RCU failure condition once the predetermined number of keep alive attempts are crossed.

18. The system (202) as claimed in claim 4, wherein the one or more processors (802) are configured to receive the location information and the mobility patterns of each of the plurality of UEs (208) by sending a location update query request to each of the plurality of UEs (208) and receiving a location update query response comprising the location information and the mobility patterns from each of the plurality of UEs (208).

19. The system (202) as claimed in claim 1, wherein the one or more processors (802) are to initiate at least one of: activation or deactivation of the RIS panel (206a) by being configured to:send at least one of: an RIS activation command or an RIS deactivation command to the RCU (204), wherein the RCU (204) decodes the RIS activation command or the RIS deactivation command, sends an RCU RIS activation command or an RCU RISdeactivation command to the RIS panel (206a), and receives an RCU RIS activation accept command or an RCU RIS deactivation accept command from the RIS panel (206a); andreceive at least one of: an RIS activation accept command or an RIS deactivation accept command from the RCU (204) once the RCU (204) receives the RCU_RIS activation accept command or the RCU RIS deactivation accept command from the RIS panel (206a).

20. The system (202) as claimed in claim 18, wherein the one or more processors (802) are configured to receive at least one of: an RIS activation reject response or an RIS deactivation reject response from the RCU (204) during a failure in at least one of the RCU (204) or the RIS panel (206a).

21. A method for managing communication and beamforming towards a plurality of UEs (208) using a Reconfigurable Intelligent Surface (RIS), the method comprising:establishing, by one or more processors (802) associated with a system (202), a connection with a RIS controller unit (RCU (204)) and the plurality of UEs (208); upon establishing the connection, receiving, by the one or more processors (802), a plurality of parameters from each of the plurality of UEs (208), and RIS-related information from the RCU (204);determining, by the one or more processors (802), that at least one UE (208-1) of the plurality of UEs (208) is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information;based on the determination, transmitting, by the one or more processors (802), a message indicating that the at least one UE (208-1) is within or approaching the RIS coverage area to the RCU (204); andenabling, by the one or more processors (802), the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

22. A User Equipment (UE) (208) comprising:a processor; anda memory operatively coupled to the processor, wherein the memory comprises processor-executable instructions, which on execution, cause the processor to:send a report comprising a plurality of parameters to a system (202),wherein the processor is communicatively coupled with the system (202), and wherein the system (202) is configured to:establish a connection with a RIS controller unit (RCU) (204) and the UE (208);upon establishing the connection, receive the plurality of parameters from the UE (208), and RIS-related information from the RCU (204); determine that the UE (208) is within or approaching a RIS coverage area based on the plurality of parameters and the RIS-related information;based on the determination, transmit a message indicating that the UE (208) is within or approaching the RIS coverage area to the RCU (204); and enable the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

23. A non-transitory computer-readable medium comprising processor-executable instructions that cause a processor to:establish a connection with a RIS controller unit (RCU) (204) and a plurality of UEs (208);upon establishing the connection, receive a plurality of parameters from each of the plurality of UEs (208), and RIS-related information from the RCU (204);determine that at least one UE (208-1) of the plurality of UEs (208) is within or approaching a RIS coverage area based on the plurality of parameters and the RIS- related information;based on the determination, transmit a message indicating that the at least one UE (208-1) is within or approaching the RIS coverage area to the RCU (204); and enable the RCU (204) to reserve one or more antenna array elements of the RCU (204) to directly communicate with the at least one UE (208-1), and configure the RIS (206) for managing beamforming towards the at least one UE (208-1), based on the message.

Images