RRM measurement limitations for CLI measurements

Abstract

The present invention relates to RRM measurement restrictions for CLI measurements. The present invention discloses methods, systems, apparatus, and computer programs for a coordination mechanism between a network and a user equipment (UE) configured to perform cross-link interference (CLI) measurements. In one aspect, a method includes generating a message indicating whether a user equipment (UE) supports a capability to simultaneously receive at least one signal associated with a cross-link interference (CLI) measurement and at least one signal associated with a serving cell or a neighboring cell of the UE. The method further includes transmitting the message to an access node (AN).

Description

[0001] This application is a divisional application of the PCT application entering the Chinese national phase, with an international filing date of June 12, 2020, national application number 202080056158.4, and invention name “RRM measurement restrictions for CLI measurements”.

[0002] Priority claim

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 861,064, filed on June 13, 2019, entitled “RRM MEASUREMENT RESTRICTION ONCLI MEASUREMENT,” which is incorporated herein by reference in its entirety. Background Art

[0004] User Equipment (UE) can transmit data wirelessly using a wireless communication network. To transmit data wirelessly, the UE connects to a node of a Radio Access Network (RAN) and synchronizes with the network. Summary of the Invention

[0005] The present disclosure relates to methods, systems, apparatuses, and computer programs, or a combination thereof, for a coordination mechanism between a network and a user equipment (UE) configured to perform cross-link interference (CLI) measurements.

[0006] According to one aspect of the present disclosure, a method includes generating a message indicating whether a user equipment (UE) supports simultaneous reception of at least one signal associated with a cross-link interference (CLI) measurement and at least one signal associated with a serving cell or a neighboring cell of the UE. The method further includes transmitting the message to an access node (AN).

[0007] Other versions include corresponding systems, apparatus, and computer programs for performing the actions of the method defined by the instructions encoded on a computer-readable storage device. These and other versions may optionally include one or more of the following features:

[0008] In some embodiments, the method further involves receiving one or more signals associated with CLI measurement during the CLI measurement window.

[0009] In some embodiments, the CLI measurement window is from X1 symbols before the CLI measurement related symbol to X2 symbols after the CLI measurement related symbol, and X1 and X2 are integers greater than or equal to 0, and wherein the CLI measurement related symbol includes at least one orthogonal frequency division multiplexing (OFDM) symbol of a sounding reference signal (SRS).

[0010] In some implementations, X1 and X2 are determined based on at least one of UE capabilities or subcarrier spacing (SCS).

[0011] In some embodiments, the UE capability indicates that the UE supports simultaneous reception of at least one signal associated with CLI measurement and at least one signal associated with the UE's serving cell or neighboring cell, and the method further includes: receiving one or more sounding reference signals (SRS) associated with CLI measurement during the CLI measurement window; performing one or more measurements relative to the one or more SRS during the CLI measurement window; and receiving one or more signals associated with the UE's serving cell or neighboring cell during the CLI measurement window.

[0012] In some embodiments, the one or more measurements include at least one of a reference signal received power (RSRP) measurement and a received signal strength indicator (RSSI) measurement relative to one or more SRSs.

[0013] In some embodiments, the one or more signals associated with the UE's serving cell or a neighboring cell is at least one radio resource management (RRM) signal.

[0014] In some implementations, the one or more signals associated with the UE's serving cell include at least one of a physical downlink shared channel (PDSCH) signal and a physical downlink control channel (PDCCH) signal.

[0015] In some embodiments, the UE capability indicates that the UE does not support simultaneous reception of at least one signal associated with CLI measurement and at least one signal associated with the UE's serving cell or neighboring cell, and the method further includes: receiving one or more sounding reference signals (SRS) associated with CLI measurement during the CLI measurement window; performing one or more measurements relative to the one or more SRS during the CLI measurement window; and ignoring one or more signals associated with the UE's serving cell or neighboring cell and transmitted to the UE during the CLI measurement window.

[0016] According to another aspect of the present disclosure, an apparatus of a user equipment (UE) includes: a processing circuit configured to determine a UE capability indicating whether the UE supports simultaneous cross-link interference (CLI) measurement and reception of at least one signal associated with a serving cell or a neighboring cell of the UE; and a baseband circuit systematically coupled to the processing circuit, the baseband circuit configured to generate a message indicating the UE capability.

[0017] In some embodiments, the processing circuit is further configured to perform the CLI measurement during a CLI measurement window.

[0018] In some embodiments, the CLI measurement window is from X1 symbols before the CLI measurement related symbol to X2 symbols after the CLI measurement related symbol, and X1 and X2 are integers greater than or equal to 0, and wherein the CLI measurement related symbol includes at least one orthogonal frequency division multiplexing (OFDM) symbol of a sounding reference signal (SRS).

[0019] In some embodiments, the UE capability indicates that the UE is capable of simultaneous CLI measurements and reception of at least one signal associated with the UE's serving cell or neighboring cell, and the baseband circuit is further configured to: perform one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement during the CLI measurement window; and receive one or more signals associated with the UE's serving cell or neighboring cell during the CLI measurement window.

[0020] In some embodiments, the UE capability indicates that the UE is incapable of simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell or neighboring cell, and the baseband circuit is further configured to: perform one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement during the CLI measurement window; and ignore one or more signals associated with the UE's serving cell or neighboring cell and transmitted to the UE during the CLI measurement window.

[0021] According to yet another aspect of the present disclosure, a method involves receiving a message from a user equipment (UE) indicating whether the UE supports simultaneous cross-link interference (CLI) measurement and reception of at least one signal associated with a serving cell of the UE. The method further involves determining whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with a serving cell of the UE based on the message.

[0022] In some embodiments, determining whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell based on the message includes determining that the UE does not support simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell, and the method further involves: determining that the UE will ignore one or more signals associated with the serving cell and transmitted to the UE.

[0023] In some embodiments, the method further involves receiving a report from the UE indicating one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement.

[0024] In some embodiments, determining whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell based on the message includes determining that the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell, and the method further includes receiving a report from the UE indicating: (i) one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement, and (ii) one or more measurements relative to one or more signals associated with the UE's serving cell.

[0025] In some embodiments, one or more measurements relative to one or more signals associated with a serving cell of the UE are at least one of synchronization signal block (SSB) based measurements or channel state information reference signal (CSI-RS) based measurements.

[0026] In some embodiments, the one or more measurements relative to one or more SRSs associated with the CLI measurement include at least one of a reference signal received power (RSRP) measurement and a received signal strength indicator (RSSI) measurement relative to the one or more SRSs. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 An exemplary architecture of a system of networks according to some embodiments of the present disclosure is shown.

[0028] Figure 2 An example of cross-link interference is shown according to some embodiments of the present disclosure.

[0029] Figure 3A 、 Figure 3B and Figure 3C Each shows a flow chart of an exemplary process according to some embodiments of the present disclosure.

[0030] Figure 4 An exemplary architecture of a system including a first CN according to some embodiments of the present disclosure is shown.

[0031] Figure 5A An exemplary radio frequency front end (RFFE) combining a millimeter wave (mmWave) RFFE and one or more sub-millimeter wave radio frequency integrated circuits (RFICs) according to some embodiments of the present disclosure is shown.

[0032] Figure 5B An alternative RFEM according to some embodiments of the present disclosure is shown.

[0033] Figure 6 Examples of infrastructure equipment according to some embodiments of the present disclosure are shown.

[0034] Figure 7 Exemplary components of a baseband circuit and a radio front end module (RFEM) are shown according to some embodiments of the present disclosure.

[0035] Figure 8 Various protocol functions that may be implemented in a wireless communication device according to some embodiments of the present disclosure are illustrated.

[0036] Figure 9 A block diagram illustrating components according to some embodiments of the present disclosure is shown.

[0037] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0038] The present disclosure relates to a network coordination mechanism for coordinating between a network and a user equipment (UE) configured to perform cross-link interference (CLI) measurements. In one embodiment, the coordination mechanism includes enabling the UE to transmit to the network an indicator of the UE's capability to simultaneously receive at least one signal associated with the CLI measurement and at least one signal associated with the UE's serving cell or a neighboring cell. In another embodiment, the coordination mechanism includes enabling the UE to transmit to the network an indicator of the UE's capability to simultaneously perform CLI measurements and measurements of at least one signal associated with the UE's serving cell. In yet another embodiment, the coordination mechanism includes measurement restrictions that limit measurements performed by the UE at specific times to avoid conflicting measurements. Among other advantages, the disclosed coordination mechanism improves the UE's connection quality (e.g., by improving user throughput).

[0039] Figure 1 An exemplary architecture of a system 100 of a network according to various embodiments is shown. The following description is provided for an exemplary system 100 operating in conjunction with LTE system standards and / or 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard and may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G) systems), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0040] like Figure 1As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smartphone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a connected or "smart" appliance, a MTC device, an M2M device, an IoT device, etc.

[0041] In some embodiments, any of the UEs 101 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0042] UE 101 may be configured to connect, e.g., be communicatively coupled, to RAN 110. In an embodiment, RAN 110 may be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., may refer to the RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN," etc., may refer to the RAN 110 operating in an LTE or 4G system 100. Multiple UEs 101 utilize connections (or channels) 103 and 104, respectively, each connection comprising a physical communication interface or layer (discussed in further detail below).

[0043] In this example, connections 103 and 104 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 101 may directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as an SL interface 105 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0044] UE 101b is shown configured to access AP 106 (also referred to as "WLAN node 106," "WLAN 106," "WLAN terminal 106," "WT 106," etc.) via connection 107. Connection 107 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 would include Wireless Fidelity. router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 101b, RAN 110, and AP 106 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve RAN nodes 111a-111b configuring UE 101b in an RRC_CONNECTED state to utilize radio resources of LTE / NR and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0045] The RAN 110 includes one or more AN nodes or RAN nodes 111a and 111b (collectively, "RAN nodes 111") that enable connections 103 and 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to RAN nodes 111 (e.g., gNBs) operating in NR or 5G systems 100, while the terms "E-UTRAN node" and the like may refer to RAN nodes 111 (e.g., eNBs) operating in LTE or 4G systems 100. According to various embodiments, the RAN node 111 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell. According to various embodiments, the RAN node 111 may operate in a licensed and / or unlicensed spectrum. More specifically, NR in an unlicensed spectrum may be referred to as NR-U, and LTE in an unlicensed spectrum may be referred to as LTE-U, License Assisted Access (LAA) or MulteFire. Therefore, the RAN node 111 may operate using LTE, Long Term Evolution Advanced (LTE-A), LTE-A, LTE-U, 5G, NR and / or NR-U protocols.

[0046] In some embodiments, all or part of the RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 111; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of multiple RAN nodes 111 to execute other virtualized applications. In some embodiments, a separate RAN node 111 may represent a plurality of RAN nodes 111 connected to the RAN via individual F1 interfaces ( Figure 1In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 6 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 101 and is connected to the 5GC via an NG interface.

[0047] In a V2X scenario, one or more of the RAN nodes 111 may be or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 101 (vUEs 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0048] Any of the RAN nodes 111 may serve as the endpoint for the air interface protocol and may be the first point of contact for the UE 101. In some embodiments, any of the RAN nodes 111 may perform various logical functions of the RAN 110, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0049] In an embodiment, UEs 101 may be configured to communicate with each other or with any of RAN nodes 111 using OFDM communication signals over a multi-carrier communication channel according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0050] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while similar techniques can be used for uplink transmissions. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which represents the physical resources in the downlink in each time slot. This type of time-frequency plane representation is common for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0051] According to various embodiments, UE 101 and RAN node 111 communicate data (e.g., transmit data and receive data) over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0052] To operate in the unlicensed spectrum, the UE 101 and the RAN node 111 may operate using LAA, eLAA, and / or feLAA mechanisms. In these embodiments, the UE 101 and the RAN node 111 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0053] LBT is a mechanism by which equipment (e.g., UE 101, RAN node 111, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0054] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the case where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some embodiments, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a variable-length LAA contention window between X and Y ECCA slots, where X and Y are the minimum and maximum values of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0055] The LAA mechanism is built on the Carrier Adaptation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL and UL.

[0056] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0057] The PDSCH carries user data and higher layer signaling to multiple UEs 101. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It can also inform multiple UEs 101 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 101b within a cell) can be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 101.

[0058] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0059] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to a set of nine physical resource elements, called EREGs, including four physical resource elements. In some cases, an ECCE may have other numbers of EREGs.

[0060] RAN nodes 111 may be configured to communicate with each other via interface 112. In embodiments where system 100 is NR or a system involving NR (e.g., when CN 120 is Figure 4 In some embodiments, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C) for user packets transmitted over the X2 interface. The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface and may be used to convey information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 101 for user data; information about PDCP PDUs that were not delivered to the UE 101; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0061] In embodiments where system 100 is a 5G or NR system, interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to a 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to a 5GC 120, and / or between two eNBs connected to a 5GC 120. In some embodiments, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U interface may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C interface may provide management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 101 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 111. This mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be built on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other embodiments, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0062] RAN 110 is shown as being communicatively coupled to a core network—in this embodiment, to a core network (CN) 120. CN 120 may include multiple network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of multiple UEs 101) connected to CN 120 via RAN 110. Components of CN 120 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0063] Generally speaking, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 130 may also be configured to support one or more communication services for the UE 101 via the EPC 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0064] In an embodiment, CN 120 may be a 5GC (referred to as "5GC 120" or the like), and RAN 110 may be connected to CN 120 via an NG interface 113. In an embodiment, NG interface 113 may be divided into two parts: an NG user plane (NG-U) interface 114, which carries traffic data between RAN node 111 and UPF; and an S1 control plane (NG-C) interface 115, which is a signaling interface between RAN node 111 and AMF.

[0065] In an embodiment, CN 120 may be a 5G CN (referred to as "5GC 120," etc.), while in other embodiments, CN 120 may be an EPC. In the case where CN 120 is an EPC (referred to as "EPC 120," etc.), RAN 110 may be connected to CN 120 via an S1 interface 113. In an embodiment, S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and the S-GW; and an S1-MME interface 115, which is a signaling interface between RAN node 111 and the MME.

[0066] In some scenarios, signal interference may occur between UEs (such as UE 101a, UE 101b). In one scenario, interference may occur when the wireless connections of the UE and its corresponding access node have different transmission directions. In this scenario, the uplink transmission of one UE may interfere with the downlink reception of another UE. For example, this scenario may occur when the UE is served by an access node that implements dynamic time division duplexing (TDD) and / or when the UEs are close to each other (for example, the distance between the UEs is less than a threshold distance). This UE-UE interference is also called cross-link interference (CLI). When neighboring UEs are using the same or sufficiently close frequencies to simultaneously transmit UL signals, the UE may experience CLI in the case of DL reception. In some other scenarios, if the frequencies used by the two UEs are close enough, CLI may occur in frequency division duplexing (FDD).

[0067] Figure 2 An example 200 of cross-link interference according to some embodiments is shown. In example 200, UE 202a, UE 202c are served by access node (AN) 204a via connections 206a, 206c, respectively. And UE 202b is served by access node 204b via connection 206b. UE 202a, UE 202b, UE 202c (collectively referred to as "UE 202") may communicate with Figure 1 AN 204a, AN 204b (collectively referred to as "AN 204") may be identical or substantially similar to UE 101. Figure 1 The RAN nodes 111 of the RAN 204a and 204b are the same or substantially similar. More specifically, the AN 204a and AN 204b may each be a base station (BS), an evolved Node B (eNB), a next-generation Node B (gNB), a roadside unit (RSU), a transmission reception point (TRxP or TR), etc., and may include a ground station (e.g., a terrestrial access point) or a satellite station, which provides coverage within a geographical area (e.g., a cell).

[0068] In example 200, CLI may occur between two or more of UEs 202. Figure 2 As shown, UE 202a is located near UE 202b and UE 202c. Therefore, CLI may occur between UE 202a and UE 202b and / or between UE 202a and UE 202c. In one example, CLI may occur when the wireless connections of the UEs (e.g., UE 202a and UE 202b) have different transmission directions. The CLI between UE 202a and UE 202b is represented by dashed line 210, and the CLI between UE 202a and UE 202c is represented by dashed line 208. Among other issues, CLI between UEs 202 may also affect user throughput.

[0069] To improve connection quality (e.g., by improving user throughput), the network may attempt to mitigate CLI between UEs. CLI mitigation techniques include coordinated scheduling / beamforming, power control, link adaptation, hybrid dynamic / static UL / DL resource allocation, and other examples. To use CLI mitigation techniques to mitigate CLI affecting a UE, the network may first obtain interference information for the UE.

[0070] In one approach, the network obtains interference information by instructing a UE (referred to as a "measuring UE") to perform CLI measurements and report the measurements to the network. CLI measurements were introduced in 3GPP Release 16. According to the current design, CLI measurements are based on one or more uplink signals received by the measuring UE from one or more interfering UEs (also referred to as "aggressive UEs"). The one or more uplink signals are, for example, sounding reference signals (SRS). The CLI measurements of the one or more uplink signals may include reference signal received power (CLI-RSRP) and / or received signal strength indicator (CLI-RSSI).

[0071] When performing CLI measurements, the measuring UE may assume fixed arrival timing of uplink signals (e.g., to reduce UE complexity), even though propagation delays from different interfering UEs may vary. Because uplink signals received from interfering UEs may be configured by different ANs, these signals may arrive simultaneously or nearly simultaneously with signals associated with the UE's serving cell (e.g., received from an access node serving the UE) or signals associated with a neighboring cell of the UE. If the signals arrive simultaneously or nearly simultaneously and the UE does not have the capability to receive (or measure) the signals simultaneously, reception of (or measurement of) at least one of the signals may fail.

[0072] To illustrate this scenario, consider a measuring UE attempting to perform CLI measurements on an SRS signal received from an interfering UE. Simultaneously or nearly simultaneously with the UE performing the CLI measurements, the UE may also receive one or more signals from the measuring UE's network for radio resource management (RRM) measurements. RRM measurements may be measurements based on synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RS) for radio link monitoring, beam failure detection, candidate beam detection, layer 1-RSRP, and / or layer 3-RSRP (RLM / BFD / CBD / L1-RSRP / L3-RSRP). If the measuring UE does not have the capability to perform CLI and RRM measurements simultaneously (or receive signals associated with the measurements simultaneously), the CLI and / or RRM measurements may fail.

[0073] In order to avoid the failure of one or both of these measurements, the present invention discloses UE capabilities that enable the UE to indicate whether the UE can perform certain actions concurrently with the CLI measurement or reception of signals associated with the CLI measurement. These UE capabilities can be provided by the UE to the network and can be used by the network as a coordination mechanism between the signal from the network and the CLI measurement at the UE. In one embodiment, the UE capability indicates whether the UE can support simultaneous CLI measurement and RRM measurement. The RRM measurement can be an SSB and / or CSI-RS based measurement for RLM / BFD / CBD / L1-RSRP / L3-RSRP. In another embodiment, the UE capability indicates whether the UE can support simultaneous CLI measurement and physical downlink shared channel (PDSCH) and / or physical downlink control channel (PDCCH) reception. A UE with this capability can not only support CLI measurement and RRM measurement concurrently, but also support concurrent PDSCH / PDCCH reception.

[0074] In one embodiment, the UE may indicate the UE capabilities to the network via an information element (IE). Table 1 includes two exemplary IEs that may be used to indicate UE capabilities. As shown in Table 1, the IE simultaneousRxDataAndMeasCLI indicates whether the UE supports concurrent CLI measurements from non-serving cells and reception of PDCCH or PDSCH from the serving cell. In addition, the IE simultaneousMeasRRMAndMeasCLI indicates whether the UE supports concurrent CLI measurements from non-serving cells and SSB or CSI-RS measurements from the serving cell. Note that the identifiers of the IEs in Table 1 are examples only, and IEs indicating the same information may have different identifiers.

[0075] Table 1

[0076]

[0077] In one embodiment, after receiving an IE indicating UE capabilities, the network may determine the UE capabilities associated with the received IE. In one example, if the UE capabilities indicate that the UE can perform certain actions concurrently with CLI measurements or reception of signals associated with CLI measurements, the network may determine not to restrict UE processes (e.g., measurements and / or signal reception). Thus, depending on the UE capabilities, the UE may concurrently perform CLI measurements (or reception of associated signals), RRM measurements (or reception of associated signals), and / or PDSCH / PDCCH reception. However, if the UE capabilities indicate that the UE does not support performing certain actions concurrently with CLI measurements or reception of signals associated with CLI measurements, the network may, in response, take remedial measures to avoid signal collisions or measurement failures.

[0078] In one embodiment, the network may impose measurement restrictions on the UE in response to determining that the UE does not support a particular capability (e.g., the UE does not support performing certain actions concurrently with CLI measurements or reception of signals associated with CLI measurements). Under the measurement restrictions, the network may not expect the UE to perform certain measurements. In one example, under one measurement restriction, the UE is not expected to perform SSB-based or CSI-RS-based RRM measurements for RLM / BFD / CBD / L1-RSRP / L3-RSRP during the CLI measurement window. In another example, under another measurement restriction, the UE is not expected to perform CLI measurements if SSBs or CSI-RS configured for RLM / BFD / CBD / L1-RSRP / L3-RSRP are present within the CLI measurement window. If measurement restrictions are imposed, a longer evaluation of the CLI or RRM measurements may be expected, or the UE may simply discard or ignore the CLI or RRM measurements.

[0079] The CLI measurement window may be determined by the UE based on the assumption of fixed arrival timing of the uplink signal (as described above). In one example, the CLI measurement window may start from X1 symbols before the CLI measurement related symbol (e.g., one orthogonal frequency division multiplexing (OFDM) symbol of the reference signal) to X2 symbols after the CLI measurement related symbol, where X1 and X2 are integers equal to or greater than 0. The values of X1 and X2 may depend on the UE capabilities, subcarrier spacing (SCS) and / or frequency band (e.g., frequency range 1 (FR1) and frequency range 2 (FR2)). In NR, FR1 overlaps and extends 4G LTE frequencies, including various frequency bands from 450 MHz to 6,000 MHz, which are also referred to as NR sub-6 GHz. FR2 also covers from 24,250 MHz to 52,600 MHz, which is commonly referred to as millimeter wave, even though strictly speaking millimeter wave frequencies may start at 30 GHz.

[0080] For example, for UEs that do not support simultaneous CLI and RRM measurements, the UE may be restricted from receiving PDCCH / PDSCH / CSI-RS within the CLI measurement window (e.g., the OFDM symbol on which the UE performs SRS-RSRP measurement). The CLI measurement window may include one data symbol before the OFDM symbol used for SRS-RSRP measurement at 15 kilohertz (kHz) and 30 kHz subcarrier spacing, and may include two data symbols before the OFDM symbol used for SRS-RSRP measurement at 60 kHz subcarrier spacing.

[0081] Figure 3A 、 Figure 3B and Figure 3C Each shows a flow chart of an exemplary process according to some embodiments. For clarity of presentation, the following description generally describes the process in the context of other figures in this specification. As an example, the flow charts 300, 310 may be executed by a UE (e.g., Figure 1 or Figure 2 ) and flowchart 320 may be executed by an access node (e.g., as Figure 2 However, it should be understood that these processes can be performed, for example, by any suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware. In some embodiments, the steps of the process can be run in parallel, in combination, in a loop, or in any order.

[0082] Figure 3A FIG3 is a flow diagram of an exemplary process 300 for indicating UE capabilities from the perspective of a UE, according to various embodiments. The UE may be the same as or substantially similar to UE 101 and / or UE 202. At step 302, process 300 involves generating a message indicating whether a user equipment (UE) supports simultaneous reception of at least one signal associated with cross-link interference (CLI) measurement and at least one signal associated with a serving cell or a neighboring cell of the UE. At step 304, process 300 involves transmitting the message to an access node (AN).

[0083] In some embodiments, the method further involves receiving one or more signals associated with CLI measurement during the CLI measurement window.

[0084] In some embodiments, the CLI measurement window is from X1 symbols before the CLI measurement related symbol to X2 symbols after the CLI measurement related symbol, and X1 and X2 are integers greater than or equal to 0, and wherein the CLI measurement related symbol includes at least one orthogonal frequency division multiplexing (OFDM) symbol of a sounding reference signal (SRS).

[0085] In some embodiments, the CLI measurement is a reference signal received power (RSRP) measurement or a received signal strength indicator (RSSI) measurement relative to a reference signal (RS). Such a reference RS may be a sounding RS (SRS) and / or other similar RS.

[0086] In some implementations, X1 and X2 are determined based on at least one of UE capabilities or subcarrier spacing (SCS).

[0087] In some embodiments, the UE capability indicates that the UE supports simultaneous reception of at least one signal associated with CLI measurement and at least one signal associated with the UE's serving cell or neighboring cell, and the method further includes: receiving one or more sounding reference signals (SRS) associated with CLI measurement during the CLI measurement window; performing one or more measurements relative to the one or more SRS during the CLI measurement window; and receiving one or more signals associated with the UE's serving cell or neighboring cell during the CLI measurement window.

[0088] In some embodiments, the one or more measurements include at least one of a reference signal received power (RSRP) measurement and a received signal strength indicator (RSSI) measurement relative to one or more SRSs.

[0089] In some embodiments, the one or more signals associated with the UE's serving cell or a neighboring cell is at least one radio resource management (RRM) signal.

[0090] In some implementations, the one or more signals associated with the UE's serving cell include at least one of a physical downlink shared channel (PDSCH) signal and a physical downlink control channel (PDCCH) signal.

[0091] In some embodiments, the UE capability indicates that the UE does not support simultaneous reception of at least one signal associated with CLI measurement and at least one signal associated with the UE's serving cell or neighboring cell, and the method further includes: receiving one or more sounding reference signals (SRS) associated with CLI measurement during the CLI measurement window; performing one or more measurements relative to the one or more SRS during the CLI measurement window; and ignoring one or more signals associated with the UE's serving cell or neighboring cell and transmitted to the UE during the CLI measurement window.

[0092] Figure 3B3 is a flow chart of an exemplary process 310 for indicating UE capabilities from the perspective of the UE. At step 312, process 310 involves indicating whether the UE supports simultaneous cross-link interference (CLI) measurement and reception of at least one signal associated with the UE's serving cell or a neighboring cell. In one example, step 312 may be performed by processing circuitry of the UE. At step 314, process 310 involves generating a message indicating the UE capabilities. In one example, step 314 may be performed by baseband circuitry of the UE.

[0093] In some embodiments, process 310 further involves performing CLI measurements during a CLI measurement window.

[0094] In some embodiments, the CLI measurement window is from X1 symbols before the CLI measurement related symbol to X2 symbols after the CLI measurement related symbol, and X1 and X2 are integers greater than or equal to 0, and wherein the CLI measurement related symbol includes at least one orthogonal frequency division multiplexing (OFDM) symbol of a sounding reference signal (SRS).

[0095] In some embodiments, the UE capability indicates that the UE is capable of performing simultaneous CLI measurements and reception of at least one signal associated with the UE's serving cell or neighboring cell, and the process further involves: performing one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement during the CLI measurement window; and receiving one or more signals associated with the UE's serving cell or neighboring cell during the CLI measurement window.

[0096] In some embodiments, the UE capability indicates that the UE is incapable of simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell or neighboring cell, and the process further involves: performing one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement during the CLI measurement window; and ignoring one or more signals associated with the UE's serving cell or neighboring cell and transmitted to the UE during the CLI measurement window.

[0097] Figure 3C 3 is a flow diagram of an example process 320 for generating a message indicating capabilities of a UE. At step 322, process 320 involves receiving a message from a user equipment (UE) indicating whether the UE supports capabilities for reception of at least one signal associated with a serving cell of the UE. At step 324, process 320 involves determining, based on the message, whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with a serving cell of the UE.

[0098] In some embodiments, determining whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell based on the message includes determining that the UE does not support simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell, and the method further involves: determining that the UE will ignore one or more signals associated with the serving cell and transmitted to the UE.

[0099] In some embodiments, the method further involves receiving a report from the UE indicating one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement.

[0100] In some embodiments, determining whether the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell based on the message includes determining that the UE supports simultaneous CLI measurement and reception of at least one signal associated with the UE's serving cell, and the method further includes receiving a report from the UE indicating: (i) one or more measurements relative to one or more sounding reference signals (SRS) associated with the CLI measurement, and (ii) one or more measurements relative to one or more signals associated with the UE's serving cell.

[0101] In some embodiments, one or more measurements relative to one or more signals associated with a serving cell of the UE are at least one of synchronization signal block (SSB) based measurements or channel state information reference signal (CSI-RS) based measurements.

[0102] In some embodiments, the one or more measurements relative to one or more SRSs associated with the CLI measurement include at least one of a reference signal received power (RSRP) measurement and a received signal strength indicator (RSSI) measurement relative to the one or more SRSs.

[0103] Figure 3A 、 Figure 3B and Figure 3C The exemplary processes shown may be modified or reconfigured to include additional, fewer, or different steps (not shown), which may be performed in the order shown or in a different order.

[0104] Figure 4 FIG. 4 shows an exemplary architecture of a system 400 including a first CN 420 according to various embodiments. In this example, the system 400 may implement the LTE standard, wherein the CN 420 is a Figure 1 In addition, UE 401 can communicate with the EPC 420 corresponding to the CN 120. Figure 1 The UE 101 is the same as or similar to the UE 101, and the E-UTRAN 410 may be the same as Figure 1The CN 420 may be a RAN that is the same as or similar to the RAN 110 of the mobile network, and may include the RAN node 111 discussed previously. The CN 420 may include an MME 421 , an S-GW 422 , a P-GW 423 , an HSS 424 , and an SGSN 425 .

[0105] MME 421 can be functionally similar to the control plane of a traditional SGSN and can implement MM functionality to keep track of the current location of UE 401. MME 421 can perform various MM procedures to manage mobility aspects of access, such as gateway selection and tracking area list management. MM (also known as "EPS MM" or "EMM" in E-UTRAN systems) can refer to all applicable procedures, methods, data stores, etc. used to maintain knowledge of the current location of UE 401, provide user identity confidentiality to users / subscribers, and / or perform other similar services. Each UE 401 and MME 421 can include an MM or EMM sublayer, and upon successful completion of the attach procedure, an MM context can be established in both UE 401 and MME 421. An MM context can be a data structure or database object that stores MM-related information for UE 401. MME 421 can be coupled to HSS 424 via the S6a reference point, to SGSN 425 via the S3 reference point, and to S-GW 422 via the S11 reference point.

[0106] SGSN 425 may be a node that serves UE 401 by tracking the location of individual UE 401 and performing security functions. Furthermore, SGSN 425 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 421; handling of UE 401 time zone capabilities as specified by MME 421; and MME selection for handover to E-UTRAN 3GPP access networks. The S3 reference point between MME 421 and SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and / or active states.

[0107] HSS 424 may include a database for network users, including subscription-related information used to support network entities handling communication sessions. EPC 420 may include one or more HSSs 424, depending on the number of mobile subscribers, device capacity, network organization, and the like. For example, HSS 424 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, and the like. The S6a reference point between HSS 424 and MME 421 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access EPC 420 between HSS 424 and MME 421.

[0108] The S-GW 422 may terminate the S1 interface 113 towards the RAN 410 ( Figure 4 The S-GW 422 is a RAN-based mobile gateway ("S1-U" in

[15] ) and routes data packets between the RAN 410 and the EPC 420. Additionally, the S-GW 422 can be the local mobility anchor for inter-RAN node handovers and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcing certain policies. The S11 reference point between the S-GW 422 and the MME 421 can provide a control plane between the MME 421 and the S-GW 422. The S-GW 422 can be coupled to the P-GW 423 via the S5 reference point.

[0109] The P-GW 423 may terminate the SGi interface towards the PDN 430. The P-GW 423 may communicate with the PDN 430 via the IP interface 125 (see, e.g., Figure 1 ) routes data packets between EPC 420 and external networks such as a network including application server 130 (alternatively referred to as "AF"). In an embodiment, P-GW 423 can communicate via IP communication interface 125 (see, e.g., Figure 1 ) is communicatively coupled to an application server ( Figure 1 Application server 130 or Figure 4430). The S5 reference point between the P-GW 423 and the S-GW 422 can provide user plane tunneling and tunnel management between the P-GW 423 and the S-GW 422. Due to the mobility of the UE 401 and whether the S-GW 422 needs to connect to a non-collocated P-GW 423 for the required PDN connectivity, the S5 reference point can also be used for S-GW 422 relocation. The P-GW 423 can also include nodes for policy enforcement and charging data collection (e.g., PCEF (not shown)). In addition, the SGi reference point between the P-GW 423 and the packet data network (PDN) 430 can be an operator-external public, private PDN, or an intra-operator packet data network, for example, to provide IMS services. The P-GW 423 can be coupled to the PCRF 426 via the Gx reference point.

[0110] PCRF 426 is the policy and charging control element of EPC 420. In a non-roaming scenario, a single PCRF 426 may exist in the Home Public Land Mobile Network (HPLMN) associated with UE 401's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, two PCRFs may be associated with UE 401's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 426 may be communicatively coupled to application server 430 via P-GW 423. Application server 430 may signal PCRF 426 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 426 may configure the rules to a PCEF (not shown) with the appropriate TFT and QCI, which initiates QoS and charging as specified by application server 430. The Gx reference point between PCRF 426 and P-GW 423 may allow for the transfer of QoS policies and charging rules from PCRF 426 to PCEF in P-GW 423. The Rx reference point may reside between PDN 430 (or "AF 430") and PCRF 426.

[0111] Figure 5A An exemplary radio frequency front end (RFFE) combining a millimeter wave (mmWave) RFFE and one or more sub-millimeter wave radio frequency integrated circuits (RFICs) is shown. Figure 5AAn embodiment of an RF front end 500 is shown that combines a mmWave RFFE 505 and one or more sub-6 GHz radio frequency integrated circuits (RFICs) 510. The mmWave RFFE 505 can be used for UE 101 when operating in FR2 or mmWave; the RFIC 510 can be used for UE 101 when operating in FR1, sub-6 GHz, or LTE bands. In this embodiment, the one or more RFICs 510 can be physically separate from the mmWave RFFE 505. The RFIC 510 can include connections to one or more antennas 520. The RFFE 505 can be coupled to multiple antennas 515, which can form one or more antenna panels.

[0112] Figure 5B An alternative embodiment of the RFFE 525 is shown. In this aspect, both mmWave and sub-6 GHz radio functionality can be implemented in the same physical RFFE 530. The RFFE 530 can incorporate both a mmWave antenna 535 and a sub-6 GHz antenna 540.

[0113] Figure 5A and Figure 5B Various RFFE architecture implementations for the UE 202 or AN 204 are shown.

[0114] In communications involving NR, an AN associated with a cell may utilize beamforming techniques to form transmission beams when transmitting signals to facilitate directional transmission to a UE at a specific location. This may be particularly useful when operating at millimeter wave frequencies. A transmission beam in a certain direction relative to the cell may provide a stronger signal to a UE at a specific location than to other UEs at other locations. This may enable better wireless connectivity between the UE and the AN associated with the cell. Multiple transmission beams from a cell may be formed by the antenna panels of the AN associated with the cell. For example, up to 64 transmission beams may be formed by different transmission beam configurations from one cell. Such transmission beam configurations may utilize beamforming techniques implemented by one or more antenna panels. The transmission beams may then be received and measured by the UE. In some embodiments, the UE may further form one or more receive beams upon reception. Therefore, non-data measurements for cell search and measurement rely on beams.

[0115] Figure 6 An example of infrastructure equipment 600 according to various embodiments is shown. Infrastructure equipment 600 (or "system 600") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 111 and / or AP 106 shown and described previously), an application server 130, and / or any other element / device discussed herein. In other examples, system 600 can be implemented in or by a UE.

[0116] System 600 includes application circuitry 605, baseband circuitry 610, one or more radio front-end modules (RFEMs) 615, memory circuitry 620, a power management integrated circuit (PMIC) 625, a power tee circuit 630, a network controller circuit 635, a network interface connector 640, satellite positioning circuitry 645, and a user interface 650. In some embodiments, device 600 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be separately included in more than one device for a CRAN, vBBU, or other similar embodiments.

[0117] The application circuit 605 may include circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, a real-time clock (RTC), a timer (including an interval timer and a watchdog timer), general-purpose input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 605 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 600. In some embodiments, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0118] The processor of the application circuit 605 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating in accordance with various embodiments herein. As an example, the processor of the application circuit 605 may include one or more Apple A series processors, Intel or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM Holdings, Ltd. licensed ARM-based processors, such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 600 may not utilize application circuitry 605 and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0119] In some embodiments, application circuit 605 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) and high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuit 605 may include logic blocks or logic structures, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuitry of application circuit 605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse), and the like) for storing logic blocks, logic structures, data, and the like in lookup tables (LUTs) and the like.

[0120] The baseband circuit 610 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 7 The various hardware electronic components of baseband circuit 610 are discussed.

[0121] The user interface circuitry 650 may include one or more user interfaces designed to enable a user to interact with the system 600 or a peripheral component interface designed to enable a peripheral component to interact with the system 600. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.

[0122] The radio front end module (RFEM) 615 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-mmWave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 7The antenna array 711 is a RFEM that can be connected to multiple antennas. In an alternative embodiment, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 615 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0123] The memory circuit 620 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 620 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0124] The PMIC 625 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 630 may provide power drawn from the network cable to provide both power and data connectivity for the infrastructure equipment 600 using a single cable.

[0125] The network controller circuit 635 can provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity can be provided to / from the infrastructure equipment 600 via the network interface connector 640 using a physical connection, which can be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 635 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some embodiments, the network controller circuit 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0126] The positioning circuit 645 includes circuits for receiving and decoding signals transmitted / broadcasted by the positioning network of the global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc.). The positioning circuit 645 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 645 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 645 may also be part of or interact with the baseband circuit 610 and / or RFEM 615 to communicate with nodes and components of the positioning network. The positioning circuit 645 may also provide location data and / or time data to the application circuit 605, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 111, etc.).

[0127] Figure 6 The components shown can communicate with each other using interface circuitry that can include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0128] Figure 7 Exemplary components of a baseband circuit 710 and a radio front end module (RFEM) 715 are shown according to various embodiments. The baseband circuit 710 corresponds to Figure 6 Baseband circuit 610. RFEM 715 corresponds to Figure 6 RFEM 615. As shown, RFEM 715 may include radio frequency (RF) circuitry 706, front end module (FEM) circuitry 708, and at least an antenna array 711 coupled together as shown.

[0129] The baseband circuitry 710 includes circuitry and / or control logic components configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuitry 706. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 710 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 710 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other embodiments. The baseband circuitry 710 is configured to process baseband signals received from the receive signal path of the RF circuitry 706 and to generate baseband signals for the transmit signal path of the RF circuitry 706. The baseband circuitry 710 is configured to communicate with the application circuitry 605 (see Figure 6 ) to generate and process baseband signals and control the operation of RF circuit 706. Baseband circuit 710 can handle various radio control functions.

[0130] The aforementioned circuits and / or control logic components of the baseband circuitry 710 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 704A, a 4G / LTE baseband processor 704B, a 5G / NR baseband processor 704C, or some other baseband processor 704D for other existing, developing, or future generations (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functionality of the baseband processors 704A-704D may be included in modules stored in the memory 704G and executed via the central processing unit (CPU) 704E. In other embodiments, some or all of the functionality of the baseband processors 704A-704D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 704G may store program code for a real-time OS (RTOS) that, when executed by the CPU 704E (or other baseband processor), enables the CPU 704E (or other baseband processor) to manage resources of the baseband circuit 710, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) The baseband circuit 710 may include one or more audio digital signal processors (DSPs) 704F. The audio DSPs 704F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0131] In some embodiments, each of processors 704A-704E includes a corresponding memory interface to send data to / receive data from memory 704G. Baseband circuit 710 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 710; an interface for sending data to / receiving data from a memory external to baseband circuit 710; Figures 6 and 7 Application circuit interface for sending data to / receiving data from the application circuit 605; Figure 7 RF circuit 706 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC.

[0132] In an alternative embodiment (which may be combined with the above embodiment), the baseband circuit 710 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connection, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 710 may include a protocol processing circuit having one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 715).

[0133] although Figure 7 Although not shown, in some embodiments, the baseband circuitry 710 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuitry 710 and / or the RF circuitry 706 are part of millimeter wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuitry 710 and / or the RF circuitry 706 are part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In the second example, the protocol processing circuitry will operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 704G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 710 may also support radio communications for more than one wireless protocol.

[0134] The various hardware elements of the baseband circuit 710 discussed herein may be implemented as, for example, a solder-in substrate comprising one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In one example, the components of the baseband circuit 710 may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In another example, some or all of the components of the baseband circuit 710 and the RF circuit 706 may be implemented together, such as, for example, a system on a chip (SOC) or a system-in-package (SiP). In another example, some or all of the components of the baseband circuit 710 may be implemented as a separate SoC communicatively coupled to the RF circuit 706 (or multiple instances of the RF circuit 706). In yet another example, some or all of the components of the baseband circuit 710 and the application circuit 605 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0135] In some embodiments, the baseband circuit 710 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 710 can support communications with E-UTRAN or other WMANs, WLANs, or WPANs. Embodiments in which the baseband circuit 710 is configured to support radio communications using more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0136] The RF circuitry 706 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 706 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 706 can include a receive signal path that can include circuitry for down-converting RF signals received from the FEM circuitry 708 and providing baseband signals to the baseband circuitry 710. The RF circuitry 706 can also include a transmit signal path that can include circuitry for up-converting baseband signals provided by the baseband circuitry 710 and providing an RF output signal to the FEM circuitry 708 for transmission.

[0137] In some embodiments, the receive signal path of RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b, and filter circuitry 706c. In some embodiments, the transmit signal path of RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing frequencies used by mixer circuitry 706a in the receive and transmit signal paths. In some embodiments, mixer circuitry 706a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d. Amplifier circuitry 706b may be configured to amplify the downconverted signal, and filter circuitry 706c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 710 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 706a of the receive signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0138] In some embodiments, mixer circuit 706a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 706d to generate an RF output signal for FEM circuit 708. The baseband signal can be provided by baseband circuit 710 and can be filtered by filter circuit 706c.

[0139] In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for quadrature down conversion and quadrature up conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be arranged for direct down conversion and direct up conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be configured for superheterodyne operation.

[0140] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 710 may include a digital baseband interface to communicate with RF circuitry 706.

[0141] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0142] In some embodiments, synthesizer circuit 706 d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 706 d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0143] Synthesizer circuit 706d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 706a of RF circuit 706. In some embodiments, synthesizer circuit 706d can be a fractional-N / N+1 synthesizer.

[0144] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 710 or application circuitry 605 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 605.

[0145] The synthesizer circuit 706d of the RF circuit 706 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-modulus frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0146] In some embodiments, the synthesizer circuit 706d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 706 can include an IQ / polarity converter.

[0147] The FEM circuitry 708 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 711, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 706 for further processing. The FEM circuitry 708 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more antenna elements in the antenna array 711. In various embodiments, amplification by the transmit or receive signal paths may be performed only in the RF circuitry 706, only in the FEM circuitry 708, or in both the RF circuitry 706 and the FEM circuitry 708.

[0148] In some embodiments, the FEM circuitry 708 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 708 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 708 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 706). The transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuitry 706), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 711.

[0149] Antenna array 711 includes one or more antenna elements, each configured to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals. For example, a digital baseband signal provided by baseband circuitry 710 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 711, which includes one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can be formed into various arrangements as known and / or discussed herein. Antenna array 711 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 711 can be formed as patches of metal foil of various shapes (e.g., patch antennas) and can be coupled to RF circuitry 706 and / or FEM circuitry 708 using metal transmission lines, etc.

[0150] The processor of the application circuitry 605 and the processor of the baseband circuitry 710 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 710 can be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuitry 605 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which is described in further detail below. As mentioned herein, layer 2 may include the MAC layer, the RLC layer, and the PDCP layer, which are described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which is described in further detail below.

[0151] Figure 8 Various protocol functions that can be implemented in wireless communication devices according to various embodiments are shown. Specifically, Figure 8 The present invention includes an arrangement 800 showing the interconnection between various protocol layers / entities. The present invention provides various protocol layers / entities for operating in conjunction with the 5G / NR system standard and / or the LTE system standard. Figure 8 The following description, but Figure 8 Some or all aspects of the present invention may also be applicable to other wireless communication network systems.

[0152] In addition to other higher layer functionality not shown, the protocol layers of arrangement 800 may include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857. These protocol layers may include one or more service access points (e.g., Figure 8 Items 859, 856, 850, 849, 845, 835, 825, and 815).

[0153] PHY 810 can transmit and receive physical layer signals 805, which can be received from or transmitted to one or more other communication devices. Physical layer signals 805 may include one or more physical channels, such as those discussed herein. PHY 810 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes) and other measurement items used by higher layers (e.g., RRC 855). PHY 810 may also further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In an embodiment, an instance of PHY 810 may process a request from an instance of MAC 820 via one or more PHY-SAP 815 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 815 may include one or more transport channels.

[0154] An instance of MAC 820 may process requests from an instance of RLC 830 and provide instructions thereto via one or more MAC-SAPs 825. These requests and instructions transmitted via MAC-SAP 825 may include one or more logical channels. MAC 820 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 810 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 810 via transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0155] An instance of RLC 830 can process requests from an instance of PDCP 840 and provide instructions thereto via one or more Radio Link Control Service Access Points (RLC-SAPs) 835. These requests and instructions transmitted via RLC-SAPs 835 can include one or more logical channels. RLC 830 can operate in multiple operating modes, including transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 830 can perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 830 can also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0156] An instance of PDCP 840 may process requests from an instance of RRC 855 and / or an instance of SDAP 847 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAPs) 845 and provide instructions thereto. These requests and instructions conveyed via PDCP-SAP 845 may include one or more radio bearers. PDCP 840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), enforce in-sequence delivery of upper layer PDUs upon lower layer reestablishment, eliminate lower layer duplication upon reestablishment of lower layer SDUs for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0157] An instance of SDAP 847 can process requests from one or more higher layer protocol entities and provide instructions to them via one or more SDAP-SAPs 849. These requests and instructions transmitted via SDAP-SAP 849 may include one or more QoS flows. SDAP 847 can map QoS flows to DRBs and vice versa, and can also mark the QFI in DL packets and UL packets. A single SDAP entity 847 can be configured for a separate PDU session. In the UL direction, NG-RAN 110 can control the mapping of QoS flows to DRBs in two different ways: reflective mapping or explicit mapping. For reflective mapping, SDAP 847 of UE 101 can monitor the QFI of DL packets for each DRB and apply the same mapping to packets flowing in the UL direction. For a DRB, SDAP 847 of UE 101 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflective mapping, the NG-RAN 510 may tag DL packets with a QoS flow ID over the Uu interface. Explicit mapping may involve RRC 855 configuring SDAP 847 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by SDAP 847. In an embodiment, SDAP 847 may only be used in NR implementations and may not be used in LTE implementations.

[0158] The RRC 855 may configure aspects of one or more protocol layers, which may include one or more instances of the PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847, via one or more Management Service Access Points (M-SAPs). In an embodiment, instances of the RRC 855 may process requests from and provide instructions to one or more NAS entities 857 via one or more RRC-SAPs 856. Primary services and functions of the RRC 855 may include broadcasting of system information (e.g., included in a MIB or SIB related to the NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of the RRC connection between the UE 101 and the RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0159] NAS 857 may form the highest layer of the control plane between UE 101 and AMF 521. NAS 857 may support mobility and session management procedures of UE 101 to establish and maintain an IP connection between UE 101 and P-GW in the LTE system.

[0160] According to various embodiments, one or more protocol entities of arrangement 800 may be implemented in UE 101, RAN node 111, AMF 521 in NR implementations, MME 421 in LTE implementations, UPF 502 in NR implementations, S-GW 422 and P-GW 423 in LTE implementations, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 521, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 111 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of gNB 111 may each host the RLC 830, MAC 820, and PHY 810 of gNB 111.

[0161] In a first example, the control plane protocol stack may include, in order from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may be built on top of NAS 857, including an IP layer 861, SCTP 862, and an application layer signaling protocol (AP) 863.

[0162] In an NR implementation, the AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 521, or the AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 defined between two or more RAN nodes 111.

[0163] The NG-AP 863 may support the functionality of the NG interface 113 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 111 and the AMF 521. NG-AP 863 services may include two groups: UE-associated services (e.g., services related to the UE 101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 111 and the AMF 521). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 111 involved in a specific paging area; a UE context management function for allowing the AMF 521 to establish, modify and / or release the UE context in the AMF 521 and the NG-RAN node 111; a mobility function for the UE 101 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 101 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 101; an NG interface management function for setting up the NG interface and monitoring errors over the NG interface; a warning message sending function for providing a means to transfer a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 101 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 101; a ... 120 Configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 111; and / or other similar functions.

[0164] The XnAP 863 may support the functionality of the Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 111 (or E-UTRAN 410), such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. The XnAP global procedures may include procedures unrelated to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, and cell activation procedures.

[0165] In an LTE embodiment, the AP 863 may be an S1 application protocol layer (S1-AP) 863 for the S1 interface 113 defined between the E-UTRAN node 111 and the MME, or the AP 863 may be an X2 application protocol layer (X2AP or X2-AP) 863 for the X2 interface 112 defined between two or more E-UTRAN nodes 111.

[0166] The S1 application protocol layer (S1-AP) 863 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be the interaction unit between the E-UTRAN node 111 and the MME 421 within the LTE CN 120. S1-AP 863 services may include two groups: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to, E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling, RAN Information Management (RIM), and configuration transfer.

[0167] The X2AP 863 may support the functions of the X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures for handling UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. The X2AP global procedures may include procedures unrelated to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, and cell activation procedures.

[0168] The SCTP layer (alternatively referred to as the SCTP / IP layer) 862 can provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). SCTP 862 can ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 521 / MME 421, based in part on the IP protocol supported by IP 861. The Internet Protocol layer (IP) 861 can be used to perform packet addressing and routing functions. In some embodiments, the IP layer 861 can use point-to-point transport to deliver and transmit PDUs. In this regard, the RAN node 111 can include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0169] In a second example, the user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810. The user plane protocol stack may be used for communication between UE 101, RAN node 111, and UPF 502 in an NR implementation, or between S-GW 422 and P-GW 423 in an LTE implementation. In this example, upper layers 851 may be built on top of SDAP 847 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 852, a general packet radio service (GPRS) tunneling protocol layer (GTP-U) for the user plane 853, and a user plane PDU layer (UP PDU) 863.

[0170] The transport network layer 854 (also known as the "transport layer") can be built on top of the IP transport, and GTP-U 853 can be used on top of the UDP / IP layer 852 (including the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also known as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.

[0171] GTP-U 853 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 852 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 111 and the S-GW 422 may utilize an S1-U interface to exchange user plane data via a protocol stack comprising the L1 layer (e.g., PHY 810), the L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and / or SDAP 847), the UDP / IP layer 852, and GTP-U 853. The S-GW 422 and the P-GW 423 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack comprising the L1 layer, the L2 layer, the UDP / IP layer 852, and GTP-U 853. As previously discussed, the NAS protocol may support mobility of UE 101 and session management procedures to establish and maintain an IP connection between UE 101 and P-GW 423 .

[0172] In addition, despite Figure 8Not shown, but an application layer may exist above the AP 863 and / or transport network layer 854. The application layer may be the layer where a user of the UE 101, RAN node 111, or other network element interacts with, for example, software applications executed by the application circuitry 605. The application layer may also provide one or more interfaces for the software applications to interact with the communication system of the UE 101 or RAN node 111, such as the baseband circuitry 710. In some embodiments, the IP layer and / or the application layer may provide functionality that is the same as or similar to layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0173] Figure 9 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 9 A schematic diagram of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 900.

[0174] Processor 910 may include, for example, processor 912 and processor 914. Processor 910 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0175] The memory / storage device 920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 920 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0176] The communication resources 930 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 906 via the network 908. For example, the communication resources 930 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0177] The instructions 950 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 910 to perform any one or more of the methods discussed herein. The instructions 950 may reside entirely or partially within at least one of the processors 910 (e.g., within a cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. In addition, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the database 906. Thus, the memory of the processor 910, the memory / storage device 920, the peripheral devices 904, and the database 906 are examples of computer-readable media and machine-readable media.

[0178] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following Examples section. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following Examples. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0179] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

Claims

1. A method for cross-link interference (CLI) measurement, the method comprising: generating a signal indicating that the UE has an ability to simultaneously perform cross-link interference (CLI) measurement and receive at least one of a physical downlink shared channel (PDSCH) signal or a physical downlink control channel (PDCCH) signal from a serving cell of the UE; as well as The signal is transmitted to an access node (AN) of the serving cell. 2 . The method according to claim 1 , wherein the at least one of the PDSCH signal or the PDCCH signal is received from a serving cell of the UE, and the CLI is measured from a cell other than the serving cell of the UE.

3. The method of claim 1 , wherein the CLI measurement is associated with one or more uplink signals from another UE. The method of claim 3 , wherein the one or more uplink signals comprise a sounding reference signal (SRS). The method according to claim 1 , wherein the CLI measurement is performed differently for a first frequency range and for a second frequency range.

6. The method of claim 3, wherein the CLI measurement comprises at least one of: a measurement of Reference Signal Received Power (RSRP) of the one or more uplink signals, or Measurement of a received signal strength indicator (RSSI) of the one or more uplink signals.

7. A user equipment (UE), comprising: a processor that generates a signal indicating that the UE has an ability to simultaneously perform cross-link interference (CLI) measurements and receive at least one of a physical downlink shared channel (PDSCH) signal or a physical downlink control channel (PDCCH) signal from a serving cell of the UE; as well as A transmitter transmits the signal to an access node (AN) of the serving cell. 8 . The UE according to claim 7 , wherein the at least one of the PDSCH signal or the PDCCH signal is received from a serving cell of the UE, and the CLI is measured from a cell other than the serving cell of the UE.

9. The UE of claim 7, wherein the CLI measurement is associated with one or more uplink signals from another UE.

10. The UE of claim 9, wherein the one or more uplink signals comprise a sounding reference signal (SRS). 11 . The UE according to claim 7 , wherein the CLI measurement is performed differently for a first frequency range and for a second frequency range.

12. The UE according to claim 9, wherein the CLI measurement comprises at least one of: a measurement of Reference Signal Received Power (RSRP) of the one or more uplink signals, or Measurement of a received signal strength indicator (RSSI) of the one or more uplink signals.

13. One or more processors comprising circuitry that executes instructions to cause a user equipment (UE) to perform operations comprising: generating a signal indicating that the UE has the capability of simultaneously performing cross-link interference (CLI) measurement and receiving at least one of a physical downlink shared channel (PDSCH) signal or a physical downlink control channel (PDCCH) signal from a serving cell of the UE; and The signal is transmitted to an access node (AN) of the serving cell.

14. The one or more processors of claim 13, wherein the at least one of a PDSCH signal or a PDCCH signal is received from a serving cell of the UE, and the CLI is measured from a cell other than the serving cell of the UE.

15. The one or more processors of claim 13, wherein the CLI measurement is associated with one or more uplink signals from another UE.

16. The one or more processors of claim 15, wherein the one or more uplink signals comprise a sounding reference signal (SRS).

17. The one or more processors of claim 13, wherein the CLI measurements are performed differently for a first frequency range than for a second frequency range.

18. The one or more processors of claim 15, wherein the CLI measurement comprises at least one of: a measurement of Reference Signal Received Power (RSRP) of the one or more uplink signals, or Measurement of a received signal strength indicator (RSSI) of the one or more uplink signals.

19. A method for cross-link interference (CLI) measurement, the method comprising: receiving, by an access node (AN), a signal from a user equipment (UE), the signal indicating that the UE has a capability of simultaneously performing cross-link interference (CLI) measurements and receiving at least one of a physical downlink shared channel (PDSCH) signal or a physical downlink control channel (PDCCH) signal from a serving cell of the UE; and At least one of a PDSCH signal or a PDCCH signal is generated.

20. The method according to claim 19, further comprising: At least one of a PDSHC signal or a PDCCH signal is transmitted by the AN to the UE. 21 . The method of claim 20 , wherein the at least one of the PDSCH signal or the PDCCH signal is transmitted via a serving cell of the UE, and the CLI is measured from a cell other than the serving cell of the UE.

22. The method of claim 19, wherein the CLI measurement is associated with one or more uplink signals from another UE.

23. The method of claim 22, wherein the one or more uplink signals comprise a sounding reference signal (SRS).

24. The method of claim 22, wherein the CLI measurement comprises at least one of: a measurement of Reference Signal Received Power (RSRP) of the one or more uplink signals, or Measurement of a received signal strength indicator (RSSI) of the one or more uplink signals.

25. The method of claim 19, wherein the CLI measurement is performed differently for a first frequency range and for a second frequency range.

Images