METHOD AND APPARATUS FOR SENSING TECHNICAL FIELD [001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for sensing. BACKGROUND [002] This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art. [003] Joint communication and sensing (JCAS) transmission has been widely recognized as an efficient approach to deal with the foreseeable coexistence between communication and radar sensing. JCAS transmissions allow effective cooperation between communication and radar sensing functionalities and have shown great potentials in improving both the performances of communication and radar sensing. [004] JCAS may not only allow for more efficient spectrum usage but also efficiently provide dual communication and sensing services for many applications, e.g., intelligent transportation, smart factories and the Internet of Things (IoT). This has made JCAS a promising candidate for networks such as fifth generation system (5GS) or sixth generation system (6GS) as defined by 3rd Generation Partnership Project (3GPP). SUMMARY [005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. [006] FIG.1a schematically shows an example of multi-static radio network based sensing according to an embodiment of the present disclosure. [007] As illustrated in FIG.1a, a possible JCAS solution is to use more than one transmission and receiving point (TRP) (e.g. Remote Radio Unit (RRU)) cooperatively to perform a joint sensing function. The number of the receivers may be any suitable number such as 1, 2, 3, 4, 5, etc. At this illustrated example, 2 receivers (RRU2 and RRU3) and 1 transmitter (RRU1) are employed. RRU1 transmits a signal. The signal is reflected by an object such as a car. RRU2
and RRU3 receive the reflected signal reflected by the object and detect the object based on the reflected signal. [008] A merit of multi-static sensing of FIG.1a as compared to the monostatic sensing is that the scheme does not require a full-duplexing operation at a TRP as having monostatic sensing. This sharply reduces the complexity in suppressing or removing the transmission crosstalk at a single TRP. Hence, this completely removes the cost in system design for crosstalk suppressions, simplifies substantially design of a TRP receiver. [009] However there may be some issues for the multi-static sensing. [010] The first issue is how to steer several beams in both the transmit (Tx) side and receive (Rx) side. [011] When TRPs are away each other in a long distance, the signal power reflected by a passive object (such as automated drone) is very week and demands a high gain beam in both Tx side and Rx side to detect the potential reflected signals. [012] Hence, one of common and necessary practice is to have beamforming at both sides of transmitter(s) and receiver(s) to get a desirable processing gain. It often needs to steer several beams to sweep a space/angle domain in the Tx side and Rx side in separate time slices. [013] In a sensing scenario, the Tx and Rx beams are usually not oriented toward each other in contrast of the case in data communication scenario where Tx and Rx beams are roughly pointing to each other in a general orientation even without a special beamforming effort. [014] For sensing, Tx and Rx beams are arranged toward a third direction where a potential object may appear. Therefore, regarding beamforming at sensing, especially at multi-static sensing cases, there are following facts and requirements: [015] For achieve the optimal beamforming gains, the Tx and Rx beams should be coordinated somehow so that they need “collide” in a certain space “spot” to focus on a possible object. Otherwise, the claimed beamforming gain will not be actualized and the reflected signals from a passive object will be very week, even below the sensitivity of the receiver. [016] For the Tx side, transmitting narrow "pencil" beams in different directions, within a steering range, is necessary for the Tx side to achieve a good balance between the detecting signal beam gain and broad steering range. FIG.1b shows an example of sweeping efficiency issue with a narrow beam. As illustrated in FIG.1b, narrow beam could bring a high gain, but, it needs more time (radio resource) to sweep a certain range. [017] It varies notably in different radio unit (RU) implementations on the Rx side, especially for different frequency band, such as frequency range 1 (FR1) or frequency range 2 (FR2). [018] Since an analog beamformer can only produce one pencil Rx beam at a time slice, an RU equipped with an analog receiving beamformer—which is extensively employed in
mm-wave and THz—must mandatorily steer various Rx analog beams in different directions at different time slices. Beam management with such Rx implementation characteristic shall work on one direction at a time slot instead of omni-directions. [019] RUs equipped with complete digital beamformers, which are often employed in sub-6 Hz, can receive multiple beams in digital domain simultaneously. But it still optionally needs steer(pre-processing) several sharp Rx beams in various directions at a separate time slice, to enhance the rate of false and miss detections in sensing while minimizing the overall computing costs or fitting tight computational latency limit. [020] The second issue is high resource requirement from multiple beams in both the Tx side and Rx side. [021] More grids of beams due to narrow beamwidth, however, results in a significant time/frequency domain resource usage, or a longer detection delay. [022] Every sensor node, for instance, has N Tx beams and M Rx beams. M and N may be any suitable integers. If the N or M is increased, the total combination of Tx-Rx beam-pair is large. For an example, most simple case of Bi-static sensing with 1 Tx TRP and 1 Rx TRP for example, the total number of Tx and Rx beam pairs is N*M, indicating N*M times of sensing resources. [023] It is evident that beam steering requires optimization, particularly for big N or large M, as it uses a lot of sensing time and frequency resources. [024] To overcome or mitigate at least one of above mentioned issues or other issues, the embodiments of the present disclosure propose a solution for sensing. [025] In a first aspect of the disclosure, there is provided a method performed by a transmitter. The method may comprise sending, to a first receiver, first information regarding a first beam to be transmitted by the transmitter for sensing. The method may comprise sending the first beam. [026] In an embodiment, the first information may be used to determine at least one first receiving beam direction of the first receiver. [027] In an embodiment, the at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [028] In an embodiment, the first information may comprise at least one of: [029] a direction of the first beam, [030] at least one target location of the first beam, [031] an antenna location of the transmitter, [032] time resource information of the first beam, or [033] frequency resource information of the first beam.
[034] In an embodiment, the method may comprise obtaining priority information of at least one receiver. [035] In an embodiment, obtaining priority information of at least one receiver may comprise receiving the priority information of at least one receiver configured by an operator. [036] In an embodiment, obtaining priority information of at least one receiver may comprise determining the priority information of the at least one receiver based on sensing reliability of the at least one receiver and/or a specific quality of service communication traffic load status of the at least one receiver. [037] In an embodiment, the method may comprise sending the priority information of the at least one receiver to the at least one receiver. [038] In an embodiment, the higher the sensing reliability of a receiver is, the higher priority of the receiver is given. [039] In an embodiment, the higher the specific quality of service communication traffic load status of a receiver is, the higher priority of the receiver is given. [040] In an embodiment, the method may comprise receiving a geographic location of the at least one receiver and/or an interference level of the at least one receiver from the at least one receiver. [041] In an embodiment, the sensing reliability of the at least one receiver may be determined based on the geographic location of the at least one receiver and/or the interference level of the at least one receiver. [042] In an embodiment, the method may comprise receiving the specific quality of service communication traffic load status of the at least one receiver from the at least one receiver. [043] In an embodiment, the first receiver is a receiver with a highest priority among the at least one receiver. [044] In a second aspect of the disclosure, there is provided a method performed by a first receiver. The method may comprise receiving, from a transmitter, first information regarding a first beam to be transmitted by the transmitter for sensing. The method may comprise determining at least one first receiving beam direction of the first receiver based on the first information. [045] In an embodiment, the at least one first receiving beam direction is used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [046] In an embodiment, the method may comprise, if the first receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, detecting and/or tracking the object.
[047] In an embodiment, the first information may comprise at least one of: [048] a direction of the first beam, [049] at least one target location of the first beam, [050] an antenna location of the transmitter, [051] time resource information of the first beam, or [052] frequency resource information of the first beam. [053] In an embodiment, the method may comprise obtaining priority information of at least one receiver. [054] In an embodiment, obtaining priority information of at least one receiver may comprise receiving the priority information of at least one receiver configured by an operator. [055] In an embodiment, obtaining priority information of at least one receiver may comprise receiving the priority information of the at least one receiver from the transmitter. [056] In an embodiment, the method may comprise sending at least one of a specific quality of service communication traffic load status of the first receiver, a geographic location of the first receiver and an interference level of the first receiver to the transmitter. [057] In an embodiment, the first receiver may be a receiver with a highest priority among the at least one receiver. [058] In an embodiment, the method may comprise sending, to a second receiver, second information regarding the at least one first receiving beam direction of the first receiver and a direction of the first beam. [059] In an embodiment, the second information may be used to determine at least one second receiving beam direction of the second receiver. [060] In an embodiment, the at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [061] In an embodiment, the second receiver may be a receiver with a second highest priority among the at least one receiver. [062] In an embodiment, the second information may comprise at least one of: [063] a direction of the first beam, [064] an antenna location of the transmitter, [065] an antenna location of the first receiver, [066] the at least one first receiving beam direction of the first receiver, [067] time resource information of the first beam, or [068] frequency resource information of the first beam.
[069] In a third aspect of the disclosure, there is provided a method performed by a second receiver. The method may comprise receiving, from a first receiver, second information regarding at least one first receiving beam direction of the first receiver and a direction of a first beam to be transmitted by a transmitter for sensing. The method may comprise determining at least one second receiving beam direction of the second receiver based on the second information. [070] In an embodiment, the at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [071] In an embodiment, the at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by the potential object in the direction of the first beam. [072] In an embodiment, the method may comprise, if the second receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, detecting and/or tracking the object. [073] In an embodiment, the second information may comprise at least one of: [074] the direction of the first beam, [075] an antenna location of the transmitter, [076] an antenna location of the first receiver, [077] the at least one first receiving beam direction of the first receiver, [078] time resource information of the first beam, or [079] frequency resource information of the first beam. [080] In an embodiment, the method may comprise obtaining priority information of at least one receiver. [081] In an embodiment, obtaining priority information of at least one receiver may comprise receiving the priority information of at least one receiver configured by an operator. [082] In an embodiment, obtaining priority information of at least one receiver may comprise receiving the priority information of the at least one receiver from the transmitter. [083] In an embodiment, the method may comprise sending at least one of a specific quality of service communication traffic load status of the second receiver, a geographic location of the second receiver and an interference level of the second receiver to the transmitter. [084] In an embodiment, the priority of the first receiver may be higher than the priority of the second receiver. [085] In an embodiment, the priority of the second receiver may be closest to the priority of the first receiver.
[086] In an embodiment, the method may comprise sending, to a third receiver, third information regarding the at least one second receiving beam direction of the second receiver and the direction of the first beam. [087] In an embodiment, the third information may be used to determine at least one third receiving beam direction of the third receiver. [088] In an embodiment, the at least one third receiving beam direction may be used by the third receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [089] In an embodiment, the priority of the second receiver may be higher than the priority of the third receiver. [090] In an embodiment, the priority of the third receiver may be closest to the priority of the second receiver. [091] In an embodiment, the third information may comprise at least one of: [092] a direction of the first beam, [093] an antenna location of the transmitter, [094] an antenna location of the second receiver, [095] the at least one second receiving beam direction of the second receiver, [096] time resource information of the first beam, or [097] frequency resource information of the first beam. [098] In a fourth aspect of the disclosure, there is provided a transmitter. The transmitter may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said transmitter is operative to send, to a first receiver, first information regarding a first beam to be transmitted by the transmitter for sensing. Said transmitter is operative to send the first beam. [099] In an embodiment, the transmitter is further operative to perform any of the methods according to the first aspect. [0100] In a fifth aspect of the disclosure, there is provided a first receiver. The first receiver may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said first receiver is operative to receive, from a transmitter, first information regarding a first beam to be transmitted by the transmitter for sensing. Said first receiver is operative to determine at least one first receiving beam direction of the first receiver based on the first information. The at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam.
[0101] In an embodiment, the first receiver is further operative to perform any of the methods according to the second aspect. [0102] In a sixth aspect of the disclosure, there is provided a second receiver. The second receiver may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said second receiver is operative to receive, from a first receiver, second information regarding at least one first receiving beam direction of the first receiver and a direction of a first beam to be transmitted by a transmitter for sensing. Said second receiver is operative to determine at least one second receiving beam direction of the second receiver based on the second information. The at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. The at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by the potential object in the direction of the first beam. [0103] In an embodiment, the second receiver is further operative to perform any of the methods according to the third aspect. [0104] In a seventh aspect of the disclosure, there is provided a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the methods according to any one of the first to third aspects. [0105] In an eighth aspect of the disclosure, there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the methods according to any one of the first to third aspects. [0106] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution allows the efficient and flexible optimal beam-management among TRPs in multi-static and bi-static sensing. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS [0107] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, by way of example, from the following detailed description with reference to the accompanying drawings, in which like reference numerals or letters are used to designate like or equivalent elements. The drawings are illustrated
for facilitating better understanding of the embodiments of the disclosure and not necessarily drawn to scale, in which: [0108] FIG.1a schematically shows an example of multi-static radio network based sensing according to an embodiment of the present disclosure; [0109] FIG.1b shows an example of sweeping efficiency issue with a narrow beam; [0110] FIG.2a schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure; [0111] FIG.2b schematically shows system architecture in a 4G network according to an embodiment of the present disclosure; [0112] FIG.3a-FIG.3d show flowcharts of methods according to embodiments of the present disclosure; [0113] FIG.4a-FIG.4e show flowcharts of methods according to embodiments of the present disclosure; [0114] FIG.5a-FIG.5e show flowcharts of methods according to embodiments of the present disclosure; [0115] FIG.6a shows an example of general mathematical modeling of the beamforming coordination issue; [0116] FIG.6b shows an example of beamforming (Tx and Rx) at different cooperative TRPs; [0117] FIG.6c shows an example of necessary beam sweep coordination on directions for best possible detection; [0118] FIG.6d shows an example of RX beam sweeping control while Tx beam keep a constant direction; [0119] FIG.6e shows an example of a case where TX TRP BF direction stays constant in a stage and RX TRP BF sweeps; [0120] FIG.6f shows an example of a sub-optimal chance in the sensing; [0121] FIG.6g shows an example of the best coordination of the proposed scheme; [0122] FIG.6h shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure; [0123] FIG.6i shows an example of dynamic sensing-reliability-based priority setting according to another embodiment of the present disclosure; [0124] FIG.6j shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure; [0125] FIG.6k shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure;
[0126] FIG.6l shows an example of information sharing and signaling among TRPs for BF coordination among TX TRP and RX TRPs according to another embodiment of the present disclosure; [0127] FIG.6m shows an example of stage transitions of BF sweeping and control unit procedure according to another embodiment of the present disclosure; [0128] FIG.7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure; [0129] FIG.8a is a block diagram showing a transmitter according to an embodiment of the disclosure; [0130] FIG.8b is a block diagram showing a first receiver according to an embodiment of the disclosure; [0131] FIG.8c is a block diagram showing a second receiver according to an embodiment of the disclosure; [0132] FIG.9 shows an example of a communication system according to an embodiment of the disclosure; [0133] FIG.10 shows a UE in accordance with some embodiments; [0134] FIG.11 shows a network node in accordance with some embodiments; [0135] FIG.12 is a block diagram of a host according to an embodiment of the disclosure; [0136] FIG.13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and [0137] FIG.14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection according to an embodiment of the disclosure. DETAILED DESCRIPTION [0138] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more
embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure. [0139] As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc. UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and/or any other protocols either currently known or to be developed in the future. [0140] The term “network device” or “network node” or “network function” refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure. For example, the 5G system (5GS) may comprise a plurality of NFs such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), radio access network (RAN), service communication proxy (SCP), network data analytics function (NWDAF), network slice Selection Function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), etc. In other embodiments, the network function may comprise different types of
NFs for example depending on a specific network. For example, the 4G system (such as Long Term Evolution (LTE)) may include Mobile Management Entity (MME), home subscriber server (HSS), PCRF (Policy and Charging Rules Function), PGW (Packet Data Network Gateway), PGW control plane (PGW-C), Serving gateway (SGW), SGW control plane (SGW-C), E-UTRAN Node B (eNB), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network. [0141] The network device may be an access network device with accessing function in a communication network via which a terminal device accesses to the network and receives services therefrom. The access network device may include a base station (BS), an access point (AP), a multi-cell/multicast coordination entity (MCE), a controller or any other suitable device in a wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), an Integrated Access and Backhaul (IAB) node, a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth. [0142] Yet further examples of the access network device comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, positioning nodes and/or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network. [0143] Virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a provider edge node and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). [0144] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more of hardware nodes. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the provider edge node or PE may be entirely virtualized.
[0145] The functions may be implemented by one or more applications (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications are run in virtualization environment which provides hardware comprising processing circuitry and memory. Memory contains instructions executable by processing circuitry whereby application is operative to provide one or more of the features, benefits, and/or functions disclosed herein. [0146] Virtualization environment, comprises general-purpose or special-purpose network hardware devices comprising a set of one or more processors or processing circuitry, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory which may be non-persistent memory for temporarily storing instructions or software executed by processing circuitry. Each hardware device may comprise one or more network interface controllers (NICs), also known as network interface cards, which include physical network interface. Each hardware device may also include non-transitory, persistent, machine-readable storage media - having stored therein software and/or instructions executable by processing circuitry. Software may include any type of software including software for instantiating one or more virtualization layers (also referred to as hypervisors), software to execute virtual machines as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein. [0147] Virtual machines, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer or hypervisor. Different embodiments of the instance of virtual appliance may be implemented on one or more of virtual machines, and the implementations may be made in different ways. [0148] During operation, processing circuitry executes software to instantiate the hypervisor or virtualization layer, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer may present a virtual operating platform that appears like networking hardware to virtual machine. [0149] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. The UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device,
a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device”, “terminal”, “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project), such as 3GPP LTE standard or NR standard. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and/or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user. [0150] As yet another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0151] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic
is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. [0152] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed terms. [0153] As used herein unless expressly stated to the contrary, the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean any of the following “only A, only B, or both A and B.” The phrase “A and/or B” should be understood to mean any of the following “only A, only B, or both A and B”. [0154] As used herein unless expressly stated to the contrary, the phrase “a plurality of” followed by a conjunctive list of enumerated items (e.g., “A and B”, “A, B, and C”) is intended to mean “multiple items, with each item selected from the list consisting of” the enumerated items. For example, “a plurality of A and B” is intended to mean any of the following: more than one A; more than one B; or at least one A and at least one B. [0155] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/ or combinations thereof. [0156] It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar/same meanings may also be used. [0157] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs. [0158] FIG.2a schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure. The architecture of FIG.2a may be similar to Figure 4.2.3-1 of 3GPP TS 23.501 V18.4.0, the disclosure of which is incorporated by reference herein in its entirety. The system architecture of FIG.2a may comprise a plurality of network functions
(NFs) such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), (radio) access network ((R)AN), service communication proxy (SCP), Network Slice Selection Function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), Edge Application Server Discovery Function (EASDF), NSACF (network slice Admission Control Function), NWDAF, etc. [0159] In accordance with an exemplary embodiment, the UE can establish a signaling connection with the AMF over the reference point N1, as illustrated in FIG.2a. This signaling connection may enable NAS (Non-access stratum) signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R)AN and the N2 connection for this UE between the (R)AN and the AMF. The (R)AN can communicate with the UPF over the reference point N3. The UE can establish a protocol data unit (PDU) session to the DN (data network, e.g. an operator network or Internet) through the UPF over the reference point N6. [0160] As further illustrated in FIG.2a, the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, Neasdf, Nnssf, Nnwdaf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF, the NSACF, the EASDF, the NSSF, the NWDAF and the SMF. In addition, FIG.2a also shows some reference points such as N1, N2, N3, N4, N6 and N9, which can support the interactions between NF services in the NFs. For example, these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure. [0161] Various NFs shown in FIG.2a may be responsible for functions such as session management, mobility management, authentication, security, etc. The AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF, NSSAAF, EASDF may include the functionality for example as defined in clause 6.2 of 3GPP TS 23.501 V18.4.0. [0162] FIG.2b schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-1a of 3GPP TS 23.682 V18.0.0, the disclosure of which is incorporated by reference herein in its entirety. The system architecture of FIG.2b may comprise some exemplary elements such as Services Capability Server (SCS), Application Server (AS), SCEF (Service Capability Exposure Function), HSS, UE, RAN(Radio Access Network), SGSN (Serving GPRS(General Packet Radio Service) Support
Node), MME, MSC(Mobile Switching Centre), S-GW(Serving Gateway), GGSN/P-GW(Gateway GPRS Support Node/PDN(Packet Data Network) Gateway), MTC-IWF(Machine Type Communications-InterWorking Function) CDF/CGF(Charging Data Function/Charging Gateway Function), MTC-AAA(Machine Type Communications-authentication, authorization and accounting), SMS-SC/GMSC/IWMSC(Short Message Service-Service Centre/Gateway MSC/InterWorking MSC) IP-SM-GW(Internet protocol Short Message Gateway). The network elements and interfaces as shown in FIG.2b may be same as the corresponding network elements and interfaces as described in 3GPP TS 23.682 V18.0.0. [0163] The system architecture shows the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data rates for GSM Evolution) Radio Access Network), etc.) via the Um/Uu/LTE-Uu interfaces. The system architecture also shows the 3GPP network service capability exposure to SCS and AS. [0164] As further illustrated in FIG.2b, the exemplary system architecture also contains various reference points. [0165] Tsms: Reference point used by an entity outside the 3GPP network to communicate with UEs used for MTC via SMS (Short Message Service). [0166] Tsp: Reference point used by a SCS to communicate with the MTC-IWF related control plane signaling. [0167] T4: Reference point used between MTC-IWF and the SMS-SC in the HPLMN (home Public Land Mobile Network). [0168] T6a: Reference point used between SCEF and serving MME. [0169] T6b: Reference point used between SCEF and serving SGSN. [0170] T8: Reference point used between the SCEF and the SCS/AS. [0171] S6m: Reference point used by MTC-IWF to interrogate HSS/HLR (Home Location Register). [0172] S6n: Reference point used by MTC-AAA to interrogate HSS/HLR. [0173] S6t: Reference point used between SCEF and HSS. [0174] SGs: Reference point used between MSC and MME. [0175] Gi/SGi: Reference point used between GGSN/P-GW and application server and between GGSN/P-GW and SCS. [0176] Rf/Ga: Reference point used between MTC-IWF and CDF/CGF. [0177] Gd: Reference point used between SMS-SC/GMSC/IWMSC and SGSN. [0178] SGd: Reference point used between SMS-SC/GMSC/IWMSC and MME.
[0179] E: Reference point used between SMS-SC/GMSC/IWMSC and MSC. [0180] A non-terrestrial network refers to a network, or segment of networks using RF resources on board a satellite (or Uncrewed Aerial System (UAS) platform). [0181] Methods according to embodiments of the present disclosure [0182] FIG.3a shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 300 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. [0183] At block 302, the transmitter may send, to a first receiver, first information regarding a first beam to be transmitted by the transmitter for sensing. [0184] The transmitter may be any suitable node, device, function, or entity that can provide the radio transmitter function. The transmitter may be a transmitter of any suitable network node of any suitable network, e.g. 4G system, 5GS, or sixth generation system (6GS) as defined by 3GPP. For example, the transmitter may be a radio access network node or a TRP. [0185] The first receiver may be any suitable node, device, function, or entity that can provide the radio receiver function. The first receiver may be a receiver of any suitable network node of any suitable network, e.g.4G system, 5GS, or a 6GS as defined by 3GPP. For example, the first receiver may be a radio access network node or a TRP. [0186] The first receiver may be selected by the transmitter in various ways. For example, if there is only one receiver, it may be selected as the first receiver. If there are multiple receivers, the first receiver may be selected by the transmitter from the multiple receivers for example based on receiver geographic location, receiver sensing reliability, specific quality of service communication traffic load of the receiver, etc. [0187] In an embodiment, the transmitter and the first receiver may be located in different static locations. For example, the transmitter may be RRU1 of FIG.1a and the first receiver may be RRU2 or RRU3 of FIG.1a. [0188] In an embodiment, the transmitter and the first receiver may belong to JCAS system. [0189] The first beam may be any suitable beam for sensing and the present disclosure has no limit on it. [0190] The first information regarding the first beam may comprise any suitable information which can be used to determine at least one first receiving beam direction of the first receiver. [0191] In an embodiment, the first information may comprise at least one of a direction of the first beam, at least one target location of the first beam, an antenna location of the transmitter, time resource information of the first beam, or frequency resource information of the first beam.
[0192] The direction of the first beam may be denoted in any suitable ways and the present disclosure has no limit on it. For example, the beam direction vector may be: [0193] Vt= [αt, βt , µt]=[ xo_i-xt_i, yo_i-yt_i, zo_i-zt_i], [0194] Where the antenna location of the transmitter is {xt_i, yt_i, zt_i}, and an intended target position is assumed to be {xo_i, yo_i, zo_i}. [0195] The at least one target location of the first beam may be denoted in any suitable ways and the present disclosure has no limit on it. For example, a target location of the first beam may be a target Cartesian coordinate of the first beam. [0196] The antenna location of the transmitter may be denoted in any suitable ways and the present disclosure has no limit on it. For example, an antenna location of the transmitter may be a Cartesian coordinate of the antenna of the transmitter. [0197] The time resource information of the first beam denotes the time resource used by the first beam. The time resource information may enable a receiver to know when to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. In addition, the time resource information may be used by a receiver to determine a location of a detected object. [0198] The frequency resource information of the first beam denotes the frequency resource used by the first beam. The frequency resource information may enable a receiver to know the frequency resource of a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [0199] In an embodiment, the first information may comprise modulation and coding scheme of the first beams. [0200] In an embodiment, the first information may be used to determine at least one first receiving beam direction of the first receiver. For example, based on the first information, the first receiver may determine at least one first receiving beam direction of the first receiver using various mathematical methods. [0201] In an embodiment, the at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [0202] The potential object may be any suitable object such as a terminal device, an Unmanned Aerial Vehicle (UAV), a drone, a vehicle, etc. [0203] At block 304, the transmitter may send the first beam. For example, the transmitter may send the first beam using beamforming.
[0204] This embodiment can achieve the optimal beamforming gains. The Tx and Rx beams can be coordinated. This embodiment can allow the efficient and flexible optimal beam-management among TRPs in multi-static and bi-static sensing. [0205] FIG.3b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 310 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0206] At block 312, the transmitter may obtain priority information of at least one receiver. [0207] Receiver priority may indicate whether the receiver has greater freedom when choosing the Rx beam. In the worst scenario, if the receiver is unable to meet the beamforming (BF) direction criterion, it will not be able to participate in the cycle of sensing. Failure to join does not imply a failure of sensing at a scenario of multiple receivers. Rather, it typically results in performance degradation to some extent (e.g., 1T2R degenerates to a 1T1R). [0208] In an embodiment, the first receiver may be a receiver with the highest priority among the at least one receiver. [0209] The priority information of at least one receiver may be obtained in various ways and the present disclosure has no limit on it. [0210] In an embodiment, the transmitter may receive the priority information of at least one receiver configured by an operator. For example, priority ordering may be manually configured by an operator, so that usually with a fixed priority setting. [0211] In an embodiment, the transmitter may determine the priority information of the at least one receiver based on sensing reliability of the at least one receiver and/or a specific quality of service communication traffic load status of the at least one receiver. [0212] In an embodiment, the priority information of at least one receiver may be determined using machine learning or artificial intelligence (AI). [0213] Higher sensing reliability may indicate that a sensing result is more trustable or with less error with a high quality of signal received and its detection. [0214] Different sensing reliability may be caused by the various factors and all of them may jointly contribute the final effect. For example, the various factors may comprise geographic location (a static factor) of a receiver. For instance, when the transmitter chooses a certain Tx beam, if a receiver always has a smaller path loss for a potential reflected signal of the Tx beam reflected by a potential object in a direction of the Tx beam than another receiver, this receiver is
more reliable in receiving the potential reflected signal statistically. Subsequently, this receiver may be given a greater priority. [0215] The various factors may comprise interference level (e.g. dynamic due to adjacent radio behavior). Different receivers may suffer different interference levels from time to time, hence different sensing Signal to Interference & Noise Ratios (SINRs). Lower interference level may normally result in more accurate sensing result so that it indicates a higher reliability. [0216] In an embodiment, the higher the sensing reliability of a receiver is, the higher priority of the receiver is given. For example, if the sensing reliability of receiver A is bigger than that of receiver B, the higher priority is given to the receiver A. The specific priority value can be determined in various ways and the present disclosure has no limit on it. [0217] The specific quality of service (QoS) communication traffic load may indicate whether the receiver has greater freedom when choosing the Rx beam. The specific QoS communication traffic may be timing critical communication traffic. [0218] In an embodiment, the higher the specific quality of service communication traffic load status of a receiver is, the higher priority of the receiver is given. For example, to have TRP's communications to be less or not interrupted by sensing, especially for TRP with more timing critical communication traffic (like Ultra-Reliable Low Latency Communication (URLLC)), the use of this TRP may be given a higher priority in this situation. As this TRP could have higher possibility to select a Rx beam without impacting its beam control in communications. [0219] In an embodiment, based the abovementioned several options, a weighted format of joint metric could be formulated. E.g., two options can be combined to accumulate priority of two options and use sum of priority. [0220] FIG.3c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 320 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0221] At block 322, the transmitter may determine the priority information of the at least one receiver based on sensing reliability of the at least one receiver and/or a specific quality of service communication traffic load status of the at least one receiver. [0222] At block 324, the transmitter may send the priority information of the at least one receiver to the at least one receiver.
[0223] FIG.3d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 330 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0224] At block 332, optionally, the transmitter may receive a geographic location of the at least one receiver and/or an interference level of the at least one receiver from the at least one receiver. [0225] In an embodiment, the sensing reliability of the at least one receiver may be determined based on the geographic location of the at least one receiver and/or the interference level of the at least one receiver. [0226] For example, the geographic location of a receiver may comprise the antenna geographic location (such as antenna Global Positioning System (GPS) coordinates, antenna tilt, antenna direction, etc.) of the receiver. The geographic location of the receiver may be not changed frequently. The interference level of the receiver may be changed frequently. [0227] At block 334, optionally, the transmitter may receive the specific quality of service communication traffic load status of the at least one receiver from the at least one receiver. [0228] In an embodiment, the transmitter may receive such information using a request-response mechanism or subscription-notification mechanism. For example, the transmitter may send a request for obtaining such information to a receiver and receive a response comprising such information from the receiver. The transmitter may subscribe to be notified of such information change notifications. If the geographic location of a receiver and/or the interference level of the receiver and/or the specific quality of service communication traffic load status are changed, the transmitter may receive the changed information from the receiver. [0229] FIG.4a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first receiver or communicatively coupled to the first receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 400 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0230] At block 402, the first receiver may receive, from a transmitter, first information regarding a first beam to be transmitted by the transmitter for sensing.
[0231] For example, the transmitter may send the first information to the first receiver at block 302 and then the first receiver may receive the first information from a transmitter. [0232] In an embodiment, the first information may comprise at least one of a direction of the first beam, at least one target location of the first beam, an antenna location of the transmitter, time resource information of the first beam, or frequency resource information of the first beam. [0233] At block 404, the first receiver may determine at least one first receiving beam direction of the first receiver based on the first information. [0234] For example, based on the first information, the first receiver may determine at least one first receiving beam direction of the first receiver using various mathematical methods. [0235] In an embodiment, the at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [0236] FIG.4b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first receiver or communicatively coupled to the first receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 410 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0237] At block 412, if the first receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, the first receiver may detect and/or track the object. [0238] For example, the first receiver may determine some parameters (such as position, velocity) of the detected object using various methods. By continuously observing the position, velocity, acceleration and other parameters of the detected object, the first receiver may analyze the behavior patterns of the detected object, such as movement trajectory, acceleration, etc. [0239] The parameters and the behavior patterns of the detected object may be transmitted to any suitable network node such as transmitter or receiver for various communication and/or sensing purposes. [0240] FIG.4c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 420 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.
For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0241] At block 422, the first receiver may obtain priority information of at least one receiver. [0242] In an embodiment, the first receiver is a receiver with a highest priority among the at least one receiver. [0243] The priority information of at least one receiver may be obtained in various ways and the present disclosure has no limit on it. [0244] In an embodiment, the first receiver may receive the priority information of at least one receiver configured by an operator. For example, priority ordering may be manually configured by an operator, so that usually with a fixed priority setting. [0245] In an embodiment, the transmitter may determine the priority information of the at least one receiver based on sensing reliability of the at least one receiver and/or a specific quality of service communication traffic load status of the at least one receiver. In this case, the first receiver may receive the priority information of the at least one receiver from the transmitter. [0246] FIG.4d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 430 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0247] At block 432, the first receiver may send at least one of a specific quality of service communication traffic load status of the first receiver, a geographic location of the first receiver and an interference level of the first receiver to the transmitter. [0248] As described above, this information may be used to determine the priority information of the first receiver. [0249] FIG.4e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a transmitter or communicatively coupled to the transmitter. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 440 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
[0250] At block 442, the first receiver may send, to a second receiver, second information regarding the at least one first receiving beam direction of the first receiver and a direction of the first beam. [0251] In an embodiment, the second information may be used to determine at least one second receiving beam direction of the second receiver. [0252] In an embodiment, the at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [0253] In an embodiment, the second receiver may be a receiver with a second highest priority among the at least one receiver. [0254] The second information may comprise any suitable information. In an embodiment, the second information comprises at least one of a direction of the first beam, an antenna location of the transmitter, an antenna location of the first receiver, the at least one first receiving beam direction of the first receiver, time resource information of the first beam, or frequency resource information of the first beam. [0255] FIG.5a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second receiver or communicatively coupled to the second receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 500 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0256] At block 502, the second receiver may receive, from a first receiver, second information regarding at least one first receiving beam direction of the first receiver and a direction of a first beam to be transmitted by a transmitter for sensing. [0257] In an embodiment, the at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [0258] In an embodiment, the second information may comprise at least one of the direction of the first beam, an antenna location of the transmitter, an antenna location of the first receiver, the at least one first receiving beam direction of the first receiver, time resource information of the first beam, or frequency resource information of the first beam. [0259] At block 504, the second receiver may determine at least one second receiving beam direction of the second receiver based on the second information.
[0260] For example, the second receiver may determine at least one second receiving beam direction of the second receiver based on the direction of the first beam and an antenna location of the transmitter or based on the direction of the first beam, an antenna location of the transmitter, an antenna location of the first receiver, and the at least one first receiving beam direction of the first receiver. [0261] In an embodiment, the at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by the potential object in the direction of the first beam. [0262] FIG.5b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second receiver or communicatively coupled to the second receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 510 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0263] At block 512, if the second receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, the second receiver may detect and/or track the object. [0264] For example, the second receiver may determine the parameters (such as position, velocity) of the detected object using various methods. By continuously observing the position, velocity and other parameters of the detected object, the second receiver may analyze the behavior patterns of the detected object, such as movement trajectory, acceleration, etc. [0265] The parameters and the behavior patterns of the detected object may be transmitted to any suitable network node such as transmitter or receiver for various communication and/or sensing purposes. [0266] FIG.5c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second receiver or communicatively coupled to the second receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 520 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0267] At block 522, the second receiver may obtain priority information of at least one receiver.
[0268] In an embodiment, the second receiver may receive the priority information of at least one receiver configured by an operator. [0269] In an embodiment, the second receiver may receive the priority information of the at least one receiver from the transmitter. [0270] In an embodiment, the priority of the first receiver may be higher than the priority of the second receiver. [0271] In an embodiment, the priority of the second receiver may be closest to the priority of the first receiver. [0272] For example, if the priority of the first receiver is the first highest among the at least one receiver, the priority of the second receiver is the second highest among the at least one receiver. If the priority of the first receiver is the second highest among the at least one receiver, the priority of the second receiver is the third highest among the at least one receiver. [0273] FIG.5d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second receiver or communicatively coupled to the second receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 530 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0274] At block 532, the second receiver may send at least one of a specific quality of service communication traffic load status of the second receiver, a geographic location of the second receiver and an interference level of the second receiver to the transmitter. [0275] As described above, this information may be used to determine the priority information of the second receiver. [0276] FIG.5e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second receiver or communicatively coupled to the second receiver. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 540 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. [0277] At block 542, the second receiver may send, to a third receiver, third information regarding the at least one second receiving beam direction of the second receiver and the direction of the first beam.
[0278] In an embodiment, the third information may comprise at least one of a direction of the first beam, an antenna location of the transmitter, an antenna location of the second receiver, the at least one second receiving beam direction of the second receiver, time resource information of the first beam, or frequency resource information of the first beam. [0279] In an embodiment, the third information may be used to determine at least one third receiving beam direction of the third receiver. [0280] In an embodiment, the at least one third receiving beam direction may be used by the third receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. [0281] In an embodiment, the priority of the second receiver may be higher than the priority of the third receiver. [0282] In an embodiment, the priority of the third receiver may be closest to the priority of the second receiver. [0283] For example, if the priority of the second receiver is the second highest among the at least one receiver, the priority of the third receiver is the third highest among the at least one receiver. If the priority of the second receiver is the third highest among the at least one receiver, the priority of the third receiver is the fourth highest among the at least one receiver. [0284] In an embodiment, it proposes a beam coordination mechanism (sequential beam coordination) for sensing. The Rx TRPs may be assigned with a priority. Using two Rx TRPs as an example, one will be chosen as the primary Rx TRP and the other one is chosen as the secondary primary Rx TRP. Tx TRP may set the BF direction first, then notify the primary Rx TRP with the Tx beam direction information (e.g. beamforming vectors). The primary Rx TRP may determine at least one Rx beam direction and communicate them to the secondary primary Rx TRP. A concrete BF direction vector calculation method may be proposed based on the known information. A procedure of BF coordination may be provided. The concrete roles and signaling of coordinator and TX, RX TRPs may be defined. [0285] In an embodiment, it provides a total solution for beam coordination among different TRPs (radio sectors/cells) to detect and track an object in multi-static or bi-static sensing. [0286] A beam coordination mechanism for sensing is as below. [0287] Problem modeling setup [0288] FIG.6a shows an example of general mathematical modeling of the beamforming coordination issue. [0289] As illustrated in FIG.6a, the purposes of sensing network are to search certain space (for example as illustrated as sphere). The transmitter and receiver TRPs work cooperatively to detect the potential object in such a space. The transmitter and receivers are in different
locations with different Cartesian coordinates. Mathematically, it is convenient to have a common Cartesian axis system to capture the beam directions in a three-dimensional space. [0290] As illustrated in FIG.6a, TX-TRP-0 is at {xt0, yt0, zt0}. RX-TRP-0 is at {xr0, yr0, zr0}. RX-TRP-1 is at {xr1, yr1, zr1}. The searching space (sphere) may be denoted as {{xs0, ys0, zs0}, ……, {xsk, ysk, zsk}}. Though only two RX-TRPs are shown in FIG.6a, there may be more or less RX-TRPs in other embodiments. [0291] TX-TRP beam sweeping [0292] Whenever the sensing signal transmitter and receiver(s) are working, their Tx beam and RX beams are changing their directions to sweep the space range targeted. This could be defined as a sensing service area (e.g. sphere). The sweep behaviors of Tx beam and RX beam(s) are coordinated to best have the reflected wave-strength to the receiver is maximized, so that the receiver could successfully detect the target. Hence, an optimal management of each beam-direction is crucial. [0293] FIG.6b shows an example of beamforming (Tx and Rx) at different cooperative TRPs. [0294] As shown in FIG.6b, the Tx and Rx beams are not coordinated. The Tx beam of TX-TRP-0 points to an object 0 at (xo0, yo0, zo0). However, the RX beams of RX-TRP-0 and RX-TRP-1 does not point to the object 0. Therefore the reflected wave may not be received by RX-TRP-0 and RX-TRP-1, and the RX-TRP-0 and RX-TRP-1 could not detect the object 0. [0295] It is proposed that a Tx beam direction guides RX beam in the coordination. First of all, the target service sphere may be split into many discrete sub-spaces with a center, {xs_i, ys_i, zs_i} and a radius rs_i and i=0, 1, …, K. If the K is large enough and rs_i becomes substantially small so that the beam width could cover all of the subspaces. [0296] Then, a continuous changing of the beam towards such neighboring subspace (sphere) would complete a sweeping of the beams over the service space (e.g. sphere), despite how the index i is arranged. [0297] FIG.6c shows an example of necessary beam sweep coordination on directions for best possible detection. [0298] In short the Tx beam may go sweeping from a sequence {i}, such as {0, 1, 2, 3, 4,…, K} and repeat it in one iteration. Or it may have different sequence of beam ID, when certain emphasis such as {0, 1, 2, 3, 3, 3, 4, 4…, K}. This may be defined as Tx beam sweeping ID sequence (pattern). [0299] The beamforming of TX with different sweeping pattern could be (1) changing of beam direction at different time slot or (2) at different frequency sub-band at the same time slot, or (3) time-frequency-selectively. [0300] The TX TRP beam direction vector is,
[0301] Vt= [αt, βt , µt]=[xo_i-xt_i, yo_i-yt_i, zo_i-zt_i], [0302] Where the TX TRP is located in {xt_i, yt_i, zt_i}, and intended target position is assumed to be {xo_i, yo_i, zo_i}. [0303] If the Tx beam has a sweeping pattern over one of above resources (time or frequency, etc.), a RX beam will have a following-up beam direction at the same radio resources. [0304] Option a: determination of RX TRP beam direction when information shared from TX TRP is at least one possible target coordinate. [0305] Once a Tx beam targets to a subspace with a center {xo_i, yo_i, zo_i}, then its Tx beam direction will be calculated as: [0306] Vt=[αt, βt , µt]=[xo_i-xt_i, yo_i-yt_i, zo_i-zt_i], and a RX beam direction should be [0307] Vr=[xo_i-xr_i, yo_i-yr_i, zo_i-zr_i], when a RX is informed of the intended coordinates are {xo_i, yo_i, zo_i}. [0308] However, usually, there is no information about whether the target is present or not, so, usually, the TX TRP is arranged to beamform and sweep an angular domain or azimuth and elevations. Vt=[αt, βt , µt] would each element value to be a grid point of a certain service range. [0309] Option b: Primary RX TRP beam direction sweeps when info-shared is TX TRP’s beam direction. [0310] If a TX TRP’s beam direction, Vt= [αt, βt , µt], is informed to a primary RX TRP. Then accordingly, the direction of beam is determined by the primary TRP, Vr_Primary=[αr, βr , µr], which only needs to preserve the constraint: [0311] Vt and Vr_Primary are aligned in a common plane, mathematically, [0312] Vr_Primary= λ(τ Vt +AT -Ar_Primary) [0313] where At =[xt, yt, zt], Ar_Primary =[xr, yr, zr], [0314] τ is in range of (0, d), and d is a limiting number to define the sweeping range and λ is a scaling factor, usually, it could be used to normalize the direction vector to be of norm value 1 for standard representation of a directional vector. [0315] FIG.6d shows an example of RX beam sweeping control while Tx beam keep a constant direction. [0316] FIG.6e shows an example of a case where TX TRP BF direction stays constant in a stage and RX TRP BF sweeps. [0317] With this proposed beam direction control method, the Tx and Rx beams are focusing on a targeted subspace (a potential target encountered while sweeping RX TRP beams while a TX TRP beam remains static), as illustrated in FIG.6d and FIG.6e when primary receiver TRP beam will sweep, and Tx beam keeps a same direction. [0318] FIG.6f shows an example of a sub-optimal chance in the sensing.
[0319] As shown in FIG.6f, only primary receiver TRP (RX-TRP-0) beam is coordinated while other receiver (follow-up ones, e.g. RX-TRP-1) is not coordinated. Primary receiver (RX-TRP-0) beam follow-up of Tx beam sweeping. Therefore, with the proposed beam direction control method, the Tx and Rx beams are focusing on a targeted subspace (a potential targeted encountered while sweeping beams). [0320] Second primary receiver beam behavior [0321] In order to achieve the best detection rate, all RX beams should be coordinated as well to achieve an optimal focusing of beams as illustrated in FIG.6f. [0322] If Vt=[αt, βt , µt], Vr_Primary=[αr, βr , µr], the beam direction of follow-up-TRP should have a unique beam direction in following calculation procedure: [0323] First, calculating the focus: [0324] [xr0+λαr, yr0 +λβr, zr0+λµr] =[xt0+ ταt, yt0+τβt, zt0+τµt ] [0325] Or use any pair of follows equations to get λ and τ. [0326] xr0+λαr=xt0+ ταt, [0327] yr0 +λβr=yt0+τβt [0328] zr0+λµr= zt0+τµt [0329] Then the follow-up TRP should have the following beam direction: [0330] Vrj=µ[xt0+ ταt- xrj, yt0+τβt- yrj, zt0+τµt- zrj], for j=1, 2, 3…J [0331] Where µ is a scaling factor, usually, it could be used to normalize the direction vector to be of norm value 1 for standard representation of a directional vector. [0332] FIG.6g shows an example of the best coordination of the proposed scheme. As shown in FIG.6g, all beams from Tx and Rx TRPs are managed to focus on certain subspace. [0333] Options and metrics for setting priority of RX TRPs [0334] Rx TRP priority determines whether a Rx TRP has greater freedom when choosing the Rx beam. In the worst scenario, if the Rx TRP is unable to meet the BF direction criterion, it will not be able to participate in the cycle of sensing. Failure to join does not imply a failure of sensing at a scenario of multiple Rx TRPs; rather, it typically results in performance degradation to some extent. (e.g., 1T2R degenerates to a 1T1R). [0335] Options of priority determination [0336] Option 1: priority ordering is manually configured, so that usually with a fixed priority setting. This option is simple, but not a recommendation due to lack of adaptiveness. [0337] FIG.6h shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure. [0338] Step 1. An operator manually configures the priority of Rx TRP when TRP is set up. An operator may assign priority for Rx TRP1 &2.
[0339] Step 2. The operator may inform priority to all Tx TRP and Rx TRPs. [0340] Option 2: dynamic sensing-reliability-based priority setting [0341] Reliability in this context means sensing result is more trustable or with less error with a high quality of signal received and its detection. [0342] Different reliability could be caused by the following factors and all of them jointly contribute the final effect. [0343] A factor may be geographic location (a static factor). [0344] FIG.6i shows an example of dynamic sensing-reliability-based priority setting according to another embodiment of the present disclosure. [0345] For instance, when Tx TRP chooses a certain Tx beam, say Tx beam 1 in FIG.6i, if TRP 1 always has a smaller path loss than TRP 2 since TRP1 is aimed toward beam 1, then, TRP1 is more reliable in receiving the signal statistically. Subsequently, TRP 1 may be given a greater priority for Transmission Beam 1. [0346] A factor may be interference level (dynamic due to adjacent radio behavior). Different Rx TRP may suffer different neighboring cell’s interference levels from time to time, hence different sensing SINRs. Lower interference level may normally result in more accurate sensing result so that it indicates a higher reliability. [0347] FIG.6j shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure. [0348] Step 1a. Rx TRP1 sends GPS position of TRP, antenna tilt/direction to Tx TRP. [0349] Step 1b. Rx TRP2 sends GPS position of TRP, antenna tilt/direction to Tx TRP. [0350] Step 2. Tx TRP calculates priority for path loss for different Tx beam for each Rx TRP, lower path loss means higher priority: Pri_pathloss (TRP, Txbeam). [0351] Step 3. Tx TRP informs priority to all Rx TRPs. [0352] Option 3: high-QoS-traffic-based priority setting [0353] To have TRP's communications to be less or not interrupted by sensing, especially for TRP with more timing critical communication traffic (like URLLC), the use of this TRP should be given a higher priority in this situation. As this TRP could have higher possibility to select a Rx beam without impacting its beam control in communications. [0354] FIG.6k shows a flowchart of setting priority of RX TRPs according to another embodiment of the present disclosure. [0355] Step 1a. Rx TRP1 sends high timing critical traffic load status to Tx TRP. [0356] Step 1b. Rx TRP2 sends High timing critical traffic load status to Tx TRP. [0357] Step 2. Tx TRP calculates priority for high QoS load for each Rx TRP. Higher load means higher priority: Pri_load (TRP).
[0358] Step 3. Tx TRP informs priority to all Rx TRPs [0359] Option 4: Joint and weighted metric based on the above options: [0360] Based the abovementioned several Options, a weighted format of joint metric could be formulated. E.g., combining option-2, and option-3, and accumulate priority of two options and use sum of priority to make a final decision. [0361] General beam coordination steps [0362] For all the beams coordinated by proposed method, they sweep in a coordinated manner and Tx TRP take the leadership to sweep a certain subspace, and pass Tx beam direction to the primary receiver TRP which will work out at least one Rx beam direction as mentioned to then pass Tx beam direction and the at least one Rx beam direction to follow-up receiver TRPs to further determine their beam directions. [0363] In such sequential beam direction information sharing from transmitter TRP to a primary Rx TRP, then to a follow-up TRP(s), the whole multiple-static sensing system may have a coordinated beam direction for each of the TRPs. All the beams dynamically cooperate to focus on a certain subspace. [0364] Additionally, the operation of Tx TRP and Rx TRPs could work with different period. For an instance, the Tx TRP could keep a constant beam direction for a period, where during this period, a primary Rx TRP could sweep with a constraint on the beam direction, and follow-up TRP beam will follow the beam behavior (beam direction info shared from primary TRP) to decide its own beam direction. [0365] FIG.6l shows an example of information sharing and signaling among TRPs for BF coordination among TX TRP and RX TRPs according to another embodiment of the present disclosure. [0366] As illustrated in FIG.6l, information sharing among TRPs for BF coordination among TX TRP and RX TRPs are conducted sequentially from TX TRP and Primary RX TRP and then the 2nd primary TRP, so on and so forth. [0367] In other words, the determination of TX BF direction is prior to the RX ones in this proposal, though, vice-versa it is also possible and has a same effect. Then after getting the TX TRP beam direction, the primary RX TRP will determine its own BF direction according to the calculation method mentioned above. Afterwards, the 2nd primary or later follow-up RX will get the BF direction info of TX BF and primary RX BF, and then accordingly determine its own BF direction vector. [0368] FIG.6m shows an example of stage transitions of BF sweeping and control unit procedure according to another embodiment of the present disclosure.
[0369] Such a control unit could be established in either TX TRP, or a gNB of which TX TRP and RX TRP are the remote units, or in a core-network node. At each of beam sweep stage, whole BF directions are pre-determined sequentially from TX TRP to primary RX TRP (RX0 TRP), to secondary RX TRP (RX_k TRP). [0370] At step 01. A control unit may determine TX TRP BF direction and time/frequency resources. [0371] At step 02. TX TRP may share TX BF info to RX TRPs. [0372] At step 03. RX0 TRP determines BF directions over TX time-slots. [0373] At step 04. RX0 TRP shares BF directions over TX time-slots to RX_k TRP(s). [0374] At step 05. RX_k TRP determines BF directions over TX time-slots according to shared info. [0375] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution allows the efficient and flexible optimal beam-management among TRPs in multi-static and bi-static sensing. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description. [0376] Apparatuses according to embodiments of the present disclosure [0377] FIG.7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure. For example, the transmitter, the second receiver or the first receiver described above may be implemented as or through the apparatus 700. [0378] The apparatus 700 comprises at least one processor 721, such as a digital processor (DP), and at least one memory (MEM) 722 coupled to the processor 721. The apparatus 700 may further comprise a transmitter Tx and receiver Rx 723 coupled to the processor 721. The MEM 722 stores a program (PROG) 724. The PROG 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 700 to operate in accordance with the embodiments of the present disclosure. A combination of the at least one processor 721 and the at least one MEM 722 may form processing means 725 adapted to implement various embodiments of the present disclosure. [0379] Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 721, software, firmware, hardware or in a combination thereof. [0380] The MEM 722 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based
memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples. [0381] The processor 721 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. [0382] In an embodiment where the apparatus is implemented as or at the transmitter, the memory 722 contains instructions executable by the processor 721, whereby the transmitter operates according to any of the methods performed by the transmitter as described above. [0383] In an embodiment where the apparatus is implemented as or at the first receiver, the memory 722 contains instructions executable by the processor 721, whereby the first receiver operates according to any of the methods performed by the first receiver as described above. [0384] In an embodiment where the apparatus is implemented as or at the second receiver, the memory 722 contains instructions executable by the processor 721, whereby the second receiver operates according to any of the methods performed by the second receiver as described above. [0385] FIG.8a is a block diagram showing a transmitter according to an embodiment of the disclosure. As shown, the transmitter 830 may comprise a first sending module 831 configured to send, to a first receiver, first information regarding a first beam to be transmitted by the transmitter for sensing. The transmitter 830 may further comprise a second sending module 832 configured to send the first beam. [0386] In an embodiment, the transmitter 830 may further comprise an obtaining module 833 configured to obtain priority information of at least one receiver. [0387] In an embodiment, the transmitter 830 may further comprise a third sending module 834 configured to send the priority information of the at least one receiver to the at least one receiver. [0388] In an embodiment, the transmitter 830 may further comprise a first receiving module 835 configured to receive a geographic location of the at least one receiver and/or an interference level of the at least one receiver from the at least one receiver. The sensing reliability of the at least one receiver may be determined based on the geographic location of the at least one receiver and/or the interference level of the at least one receiver. [0389] In an embodiment, the transmitter 830 may further comprise a second receiving module 836 configured to receive the specific quality of service communication traffic load status of the at least one receiver from the at least one receiver. [0390] FIG.8b is a block diagram showing a first receiver according to an embodiment of the disclosure. As shown, the first receiver 850 may comprise a first receiving module 851
configured to receive, from a transmitter, first information regarding a first beam to be transmitted by the transmitter for sensing. The first receiver 850 may comprise a determining module 852 configured to determine at least one first receiving beam direction of the first receiver based on the first information. The at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in a direction of the first beam. [0391] In an embodiment, the first receiver 850 may further comprise a detecting and/or tracking module 853 configured to, if the first receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, detect and/or track the object. [0392] In an embodiment, the first receiver 850 may further comprise an obtaining receiving module 854 configured to obtain priority information of at least one receiver. [0393] In an embodiment, the first receiver 850 may further comprise a first sending module 855 configured to send at least one of a specific quality of service communication traffic load status of the first receiver, a geographic location of the first receiver and an interference level of the first receiver to the transmitter. [0394] In an embodiment, the first receiver 850 may further comprise a second sending module 856 configured to send, to a second receiver, second information regarding the at least one first receiving beam direction of the first receiver and a direction of the first beam. [0395] FIG.8c is a block diagram showing a second receiver according to an embodiment of the disclosure. As shown, the second receiver 860 may comprise a first receiving module 861 configured to receive, from a first receiver, second information regarding at least one first receiving beam direction of the first receiver and a direction of a first beam to be transmitted by a transmitter for sensing. The second receiver 860 may comprise a determining module 862 configured to determine at least one second receiving beam direction of the second receiver based on the second information. The at least one first receiving beam direction may be used by the first receiver to receive a potential reflected signal of the first beam reflected by a potential object in the direction of the first beam. The at least one second receiving beam direction may be used by the second receiver to receive a potential reflected signal of the first beam reflected by the potential object in the direction of the first beam. [0396] In an embodiment, the second receiver 860 may further comprise a detecting and/or tracking module 863 configured to, if the second receiver receives a reflected signal of the first beam reflected by an object in the direction of the first beam, detect and/or track the object. [0397] In an embodiment, the second receiver 860 may further comprise an obtaining module 864 configured to obtain priority information of at least one receiver.
[0398] In an embodiment, the second receiver 860 may further comprise a first sending module 865 configured to, send at least one of a specific quality of service communication traffic load status of the second receiver, a geographic location of the second receiver and an interference level of the second receiver to the transmitter. [0399] In an embodiment, the second receiver 860 may further comprise a second sending module 866 configured to send, to a third receiver, third information regarding the at least one second receiving beam direction of the second receiver and the direction of the first beam. [0400] With function units, the transmitter, the second receiver or the first receiver may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the transmitter, the second receiver or the first receiver in the communication system. The introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network. [0401] Further, the exemplary overall commutation system including the terminal device and the network node (such as the transmitter, the first receiver or the second receiver) will be introduced as below. [0402] FIG.9 shows an example of a communication system 9100 in accordance with some embodiments. [0403] In the example, the communication system 9100 includes a telecommunication network 9102 that includes an access network 9104, such as a radio access network (RAN), and a core network 9106, which includes one or more core network nodes 9108. The access network 9104 includes one or more access network nodes, such as network nodes 9110a and 9110b (one or more of which may be generally referred to as network nodes 9110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 9102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 9102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 9102, including one or more network nodes 9110 and/or core network nodes 9108. [0404] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane
(O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application or a non-real time control application, or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 9110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 9111a, 9112, 9111c, and 9111d (one or more of which may be generally referred to as UEs 9112) to the core network 9106 over one or more wireless connections. [0405] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 9100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 9100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0406] The UEs 9112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 9110 and other communication devices. Similarly, the network nodes 9110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 9112 and/or with other network nodes or equipment in the telecommunication network 9102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 9102. [0407] In the depicted example, the core network 9106 connects the network nodes 9110 to one or more hosts, such as host 9116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 9106 includes one more core network nodes (e.g., core
network node 9108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 9108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0408] The host 9116 may be under the ownership or control of a service provider other than an operator or provider of the access network 9104 and/or the telecommunication network 9102, and may be operated by the service provider or on behalf of the service provider. The host 9116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0409] As a whole, the communication system 9100 of FIG.9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [0410] In some examples, the telecommunication network 9102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 9102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 9102. For example, the telecommunications network 9102 may provide Ultra Reliable Low Latency Communication (URLLC) services to
some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [0411] In some examples, the UEs 9112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 9104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 9104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). [0412] In the example, the hub 9114 communicates with the access network 9104 to facilitate indirect communication between one or more UEs (e.g., UE 9111c and/or 9111d) and network nodes (e.g., network node 9110b). In some examples, the hub 9114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 9114 may be a broadband router enabling access to the core network 9106 for the UEs. As another example, the hub 9114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 9110, or by executable code, script, process, or other instructions in the hub 9114. As another example, the hub 9114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 9114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 9114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 9114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 9114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. [0413] The hub 9114 may have a constant/persistent or intermittent connection to the network node 9110b. The hub 9114 may also allow for a different communication scheme and/or schedule between the hub 9114 and UEs (e.g., UE 9111c and/or 9111d), and between the hub 9114 and the core network 9106. In other examples, the hub 9114 is connected to the core network 9106 and/or one or more UEs via a wired connection. Moreover, the hub 9114 may be configured to connect to an M2M service provider over the access network 9104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 9110 while still connected via the hub 9114 via a wired or
wireless connection. In some embodiments, the hub 9114 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 9110b. In other embodiments, the hub 9114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 9110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0414] FIG.10 shows a UE 10200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0415] A UE may support device-to-device (D1d) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0416] The UE 10200 includes processing circuitry 10202 that is operatively coupled via a bus 10204 to an input/output interface 10206, a power source 10208, a memory 10210, a communication interface 10212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG.10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0417] The processing circuitry 10202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 10210. The processing circuitry 10202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 10202 may include multiple central processing units (CPUs). [0418] In the example, the input/output interface 10206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 10200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0419] In some embodiments, the power source 10208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 10208 may further include power circuitry for delivering power from the power source 10208 itself, and/or an external power source, to the various parts of the UE 10200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 10208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 10208 to make the power suitable for the respective components of the UE 10200 to which power is supplied. [0420] The memory 10210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable
read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 10210 includes one or more application programs 10214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 10216. The memory 10210 may store, for use by the UE 10200, any of a variety of various operating systems or combinations of operating systems. [0421] The memory 10210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 10210 may allow the UE 10200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 10210, which may be or comprise a device-readable storage medium. [0422] The processing circuitry 10202 may be configured to communicate with an access network or other network using the communication interface 10212. The communication interface 10212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 10222. The communication interface 10212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 10218 and/or a receiver 10220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 10218 and receiver 10220 may be coupled to one or more antennas (e.g., antenna 10222) and may share circuit components, software or firmware, or alternatively be implemented separately. [0423] In the illustrated embodiment, communication functions of the communication interface 10212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range
communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0424] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 10212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0425] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0426] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a
heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 10200 shown in FIG.10. [0427] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0428] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0429] FIG.11 shows a network node 11300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). [0430] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a
distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [0431] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0432] The network node 11300 includes a processing circuitry 11302, a memory 11304, a communication interface 11306, and a power source 11308. The network node 11300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 11300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 11300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 11304 for different RATs) and some components may be reused (e.g., a same antenna 11310 may be shared by different RATs). The network node 11300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 11300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 11300. [0433] The processing circuitry 11302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 11300 components, such as the memory 11304, to provide network node 11300 functionality. [0434] In some embodiments, the processing circuitry 11302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 11302 includes one or more of radio
frequency (RF) transceiver circuitry 11312 and baseband processing circuitry 11314. In some embodiments, the radio frequency (RF) transceiver circuitry 11312 and the baseband processing circuitry 11314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 11312 and baseband processing circuitry 11314 may be on the same chip or set of chips, boards, or units. [0435] The memory 11304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 11302. The memory 11304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 11302 and utilized by the network node 11300. The memory 11304 may be used to store any calculations made by the processing circuitry 11302 and/or any data received via the communication interface 11306. In some embodiments, the processing circuitry 11302 and memory 11304 is integrated. [0436] The communication interface 11306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 11306 comprises port(s)/terminal(s) 11316 to send and receive data, for example to and from a network over a wired connection. The communication interface 11306 also includes radio front-end circuitry 11318 that may be coupled to, or in certain embodiments a part of, the antenna 11310. Radio front-end circuitry 11318 comprises filters 11320 and amplifiers 11322. The radio front-end circuitry 11318 may be connected to an antenna 11310 and processing circuitry 11302. The radio front-end circuitry may be configured to condition signals communicated between antenna 11310 and processing circuitry 11302. The radio front-end circuitry 11318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 11318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 11320 and/or amplifiers 11322. The radio signal may then be transmitted via the antenna 11310. Similarly, when receiving data, the antenna 11310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 11318. The digital data may be passed to the processing circuitry 11302. In other embodiments, the
communication interface may comprise different components and/or different combinations of components. [0437] In certain alternative embodiments, the network node 11300 does not include separate radio front-end circuitry 11318, instead, the processing circuitry 11302 includes radio front-end circuitry and is connected to the antenna 11310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 11312 is part of the communication interface 11306. In still other embodiments, the communication interface 11306 includes one or more ports or terminals 11316, the radio front-end circuitry 11318, and the RF transceiver circuitry 11312, as part of a radio unit (not shown), and the communication interface 11306 communicates with the baseband processing circuitry 11314, which is part of a digital unit (not shown). [0438] The antenna 11310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 11310 may be coupled to the radio front-end circuitry 11318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 11310 is separate from the network node 11300 and connectable to the network node 11300 through an interface or port. [0439] The antenna 11310, communication interface 11306, and/or the processing circuitry 11302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 11310, the communication interface 11306, and/or the processing circuitry 11302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0440] The power source 11308 provides power to the various components of network node 11300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 11308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 11300 with power for performing the functionality described herein. For example, the network node 11300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 11308. As a further example, the power source 11308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0441] Embodiments of the network node 11300 may include additional components beyond those shown in FIG.11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 11300 may include user interface equipment to allow input of information into the network node 11300 and to allow output of information from the network node 11300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 11300. [0442] FIG.12 is a block diagram of a host 12400, which may be an embodiment of the host 9116 of FIG.9, in accordance with various aspects described herein. As used herein, the host 12400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 12400 may provide one or more services to one or more UEs. [0443] The host 12400 includes processing circuitry 12402 that is operatively coupled via a bus 12404 to an input/output interface 12406, a network interface 12408, a power source 12410, and a memory 12412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the terminal devices, such that the descriptions thereof are generally applicable to the corresponding components of host 12400. [0444] The memory 12412 may include one or more computer programs including one or more host application programs 12414 and data 12416, which may include user data, e.g., data generated by a UE for the host 12400 or data generated by the host 12400 for a UE. Embodiments of the host 12400 may utilize only a subset or all of the components shown. The host application programs 12414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 12414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 12400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 12414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0445] FIG.13 is a block diagram illustrating a virtualization environment 13500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 13500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 13500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. [0446] Applications 13502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0447] Hardware 13504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 13506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 13508A and 13508B (one or more of which may be generally referred to as VMs 13508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 13506 may present a virtual operating platform that appears like networking hardware to the VMs 13508. [0448] The VMs 13508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 13506. Different embodiments of the instance of a virtual appliance 13502 may be implemented on one or more of VMs 13508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume
server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0449] In the context of NFV, a VM 13508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 13508, and that part of hardware 13504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 13508 on top of the hardware 13504 and corresponds to the application 13502. [0450] Hardware 13504 may be implemented in a standalone network node with generic or specific components. Hardware 13504 may implement some functions via virtualization. Alternatively, hardware 13504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 13510, which, among others, oversees lifecycle management of applications 13502. In some embodiments, hardware 13504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 13512 which may alternatively be used for communication between hardware nodes and radio units. [0451] FIG.14 shows a communication diagram of a host 14602 communicating via a network node 14604 with a UE 14606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 9111a of FIG.9), network node (such as network node 9110a of FIG.9), and host (such as host 9116 of FIG.9 and/or host 12400 of FIG.12) discussed in the preceding paragraphs will now be described with reference to FIG.14. [0452] Like host 12400, embodiments of host 14602 include hardware, such as a communication interface, processing circuitry, and memory. The host 14602 also includes software, which is stored in or accessible by the host 14602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 14606 connecting via an over-the-top (OTT) connection 14650 extending between the UE 14606 and host 14602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 14650.
[0453] The network node 14604 includes hardware enabling it to communicate with the host 14602 and UE 14606. The connection 14660 may be direct or pass through a core network (like core network 9106 of FIG.9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0454] The UE 14606 includes hardware and software, which is stored in or accessible by UE 14606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 14606 with the support of the host 14602. In the host 14602, an executing host application may communicate with the executing client application via the OTT connection 14650 terminating at the UE 14606 and host 14602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 14650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 14650. [0455] The OTT connection 14650 may extend via a connection 14660 between the host 14602 and the network node 14604 and via a wireless connection 14670 between the network node 14604 and the UE 14606 to provide the connection between the host 14602 and the UE 14606. The connection 14660 and wireless connection 14670, over which the OTT connection 14650 may be provided, have been drawn abstractly to illustrate the communication between the host 14602 and the UE 14606 via the network node 14604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0456] As an example of transmitting data via the OTT connection 14650, in step 14608, the host 14602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 14606. In other embodiments, the user data is associated with a UE 14606 that shares data with the host 14602 without explicit human interaction. In step 14610, the host 14602 initiates a transmission carrying the user data towards the UE 14606. The host 14602 may initiate the transmission responsive to a request transmitted by the UE 14606. The request may be caused by human interaction with the UE 14606 or by operation of the client application executing on the UE 14606. The transmission may pass via the network node 14604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 14612, the network node 14604 transmits to the UE 14606 the user data that was carried in the transmission that the host 14602 initiated, in accordance with the teachings of the embodiments
described throughout this disclosure. In step 14614, the UE 14606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 14606 associated with the host application executed by the host 14602. [0457] In some examples, the UE 14606 executes a client application which provides user data to the host 14602. The user data may be provided in reaction or response to the data received from the host 14602. Accordingly, in step 14616, the UE 14606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 14606. Regardless of the specific manner in which the user data was provided, the UE 14606 initiates, in step 14618, transmission of the user data towards the host 14602 via the network node 14604. In step 14620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 14604 receives user data from the UE 14606 and initiates transmission of the received user data towards the host 14602. In step 14622, the host 14602 receives the user data carried in the transmission initiated by the UE 14606. [0458] One or more of the various embodiments improve the performance of OTT services provided to the UE 14606 using the OTT connection 14650, in which the wireless connection 14670 forms the last segment. More precisely, in some embodiments herein, the proposed solution allows the efficient and flexible optimal beam-management among TRPs in multi-static and bi-static sensing. [0459] In an example scenario, factory status information may be collected and analyzed by the host 14602. As another example, the host 14602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 14602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 14602 may store surveillance video uploaded by a UE. As another example, the host 14602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 14602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [0460] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 14650 between the host 14602 and UE 14606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT
connection may be implemented in software and hardware of the host 14602 and/or UE 14606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 14650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 14650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 14604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 14602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 14650 while monitoring propagation times, errors, etc. [0461] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0462] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory
computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally. [0463] The term unit or module may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. [0464] According to an aspect of the disclosure it is provided a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above. [0465] According to an aspect of the disclosure it is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above. [0466] In addition, the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. The computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like. [0467] The techniques described herein may be implemented by various means so that an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or
combinations thereof. For a firmware or software, implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein. [0468] Exemplary embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatuses. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. [0469] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. [0470] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any implementation or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular implementations. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination. [0471] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The above described embodiments are
given for describing rather than limiting the disclosure, and it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the disclosure as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the disclosure and the appended claims. The protection scope of the disclosure is defined by the accompanying claims.