Inter-cell beam management scheduling constraints and reporting

Abstract

An apparatus and system are described for scheduling constraints on inter-cell Layer 1 reference signal received power (L1-RSRP) measurements when synchronization signal blocks (SSBs) and data are scheduled within the same symbol. The scheduling constraints include that a UE is not expected to receive downlink data or control signals on symbols corresponding to SSB indices configured for L1-RSRP measurements, where the data / control signals are transmitted by different cells, have the same subcarrier spacing (SCS), or have different SCSs, and the UE supports simultaneousRxDataSSB-DiffNumerology. The cells include the UE's serving cell and another cell with a different physical cell identifier (PCI). If the SCSs are different and the UE does not support simultaneousRxDataSSB-DiffNumerology, the UE is not expected to receive downlink data / control signals or channel state information reference signals, or transmit uplink data / control signals or sounding reference signals, on symbols corresponding to SSB indices configured for L1-RSRP measurements.

Description

[Technical Field]

[0001] [Priority Claim] This application claims priority to U.S. Provisional Patent Application No. 63 / 396,871, filed August 10, 2022, which is incorporated herein by reference in its entirety.

[0002] [Technical field] FIELD Embodiments relate to next generation wireless communications. In particular, some embodiments relate to scheduling constraints and user equipment (UE) reporting for inter-cell beam management. [Background technology]

[0003] The use and complexity of NG systems, including 5G networks and especially emerging sixth-generation (6G) networks, is increasing due to both the proliferation of user equipment (UE) devices using network resources and the volume of data and bandwidth used by various applications, such as video streaming, running on these UEs. With the significant increase in the number and diversity of communication devices, the corresponding network environment is becoming increasingly complex. As expected, the emergence of new technologies presents many challenges, including complexities associated with multi-cell beam management. [Brief explanation of the drawings]

[0004] The figures are not necessarily drawn to scale, and like reference numbers may represent like components in different figures. Like reference numbers with different letter suffixes may represent different instances of like components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.

[0005] [Figure 1A] 1 illustrates a network architecture, according to some aspects.

[0006] [Figure 1B]1 illustrates a non-roaming 5G system architecture, according to some aspects.

[0007] [Figure 1C] 1 illustrates a non-roaming 5G system architecture, according to some aspects.

[0008] [Figure 2] 1 illustrates a block diagram of a communication device according to some embodiments.

[0009] [Figure 3] 1 illustrates cell overlap according to some embodiments.

[0010] [Figure 4] 1 illustrates cell overlap according to some embodiments.

[0011] [Figure 5] 1 illustrates a process for identifying signal overlap according to some embodiments.

[0012] [Figure 6] 10 illustrates a process for transmitting a signal to a UE according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following description and drawings sufficiently describe particular embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, processing, and other changes. Portions and features of some embodiments may be included in or substituted for portions and features of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0014] 1A illustrates a network architecture according to some aspects. Network 140A includes 3GPP® LTE / 4G and NG network functions that are extensible to 6G functionality. Thus, while referring to 5G, this should be understood as extensible to 6G structures, systems, and functions. Network functions can be implemented as individual network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on a suitable platform, such as dedicated hardware or a cloud infrastructure.

[0015] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0016] Any of the wireless links described herein (e.g., used in network 140A or other illustrated networks) may operate according to any exemplary wireless communication technology and / or standard. Any spectrum management scheme may be used, including, for example, dedicated licensed spectrum, unlicensed spectrum, or (licensed) shared spectrum (e.g., Licensed Shared Access (LSA) at 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and Spectrum Access System (SAS) at 3.55-3.7 GHz and other frequencies). Different single-carrier or orthogonal frequency-domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter-bank-based multicarrier (FBMC), OFDM, etc.), and 3GPP NR in particular, may be used by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0017] In some aspects, both UEs 101 and 102 may comprise Internet of Things (IoT) UEs or cellular IoT (CIoT) UEs, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, both UEs 101 and 102 may comprise narrowband (NB) IoT UEs (e.g., enhanced NB-IoT (eNB-IoT) UEs and Further Enhanced (FeNB-IoT) UEs, etc.). IoT UEs may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over a public land mobile network (PLMN), proximity-based service (ProSe), or device-to-device (D2D) communications, sensor network, or IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. IoT networks include the ability to interconnect IoTUEs, including uniquely identifiable embedded computing devices (within the Internet infrastructure), over short-term connections. IoTUEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate IoT network connectivity. In some aspects, both UEs 101 and 102 may comprise enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0018] The UEs 101 and 102 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 110. The RAN 110 may be, e.g., an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGenRAN (NGRAN), or another type of RAN.

[0019] UEs 101 and 102 utilize connections 103 and 104, respectively, each including a physical communication interface or layer (described in more detail below). In this example, connections 103 and 104 are illustrated as air interfaces for enabling communication coupling and may be compatible with cellular communication protocols such as Global System for Mobile Communications (GSM) protocols, Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, PTT over Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, 6G protocols, etc.

[0020] In one aspect, the UEs 101 and 102 can further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 is also referred to as a sidelink (SL) interface, which includes one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0021] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may constitute a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, according to which AP 106 may constitute a wireless fidelity (WiFi) router. In this example, AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

[0022] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and can include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic region (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmission / reception points (TRPs). When the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeB. The RAN 110 can include one or more RAN nodes for providing a macrocell, e.g., a macro RAN node 111, and one or more RAN nodes for providing a femtocell or picocell (e.g., a cell with a smaller coverage area, lower user capacity, or larger bandwidth compared to a macrocell), e.g., a low-power (LP) RAN node 112.

[0023] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for the UEs 101 and 102. In some aspects, either of the RAN nodes 111 and 112 may perform various logical functions of the RAN 110, including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In one example, either of the nodes 111 and / or 112 may be a gNB, eNB, or another type of RAN node.

[0024] The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or other type of CN (e.g., as illustrated with reference to FIGS. 1B, 1C ). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1 mobility management entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and an MME 121.

[0025] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MME 121 is functionally similar to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 124 can include a database for network users, including subscription-related information to support network entity processing of communication sessions. The CN 120 can include one or more HSSs 124, depending on the number of mobile subscribers, device capabilities, network configuration, etc. For example, the HSS 124 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0026] The S-GW 122 terminates the S1 interface 113 towards the RAN 110 and can route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 include lawful interception, charging, and some policy enforcement.

[0027] The P-GW 123 can terminate the SGi interface toward the PDN. The P-GW 123 can route data packets between the CN 120 and external networks, such as a network including an application server 184 (also referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element that provides applications that use IP bearer resources in a core network (e.g., a UMTS packet service (PS) domain, an LTE PS data service, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., a Voice-over-Internet Protocol (VoIP) session, a PTT session, a group communication session, a social networking service, etc.) for the UEs 101 and 102 via the CN 120.

[0028] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE'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). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0029] In some aspects, the communications network 140A may be an IoT network or a 5G or 6G network, including a 5G New Radio network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One current enabler of IoT is narrowband IoT (NB-IoT). Operation in unlicensed spectrum may include dual connectivity (DC) operation and standalone LTE systems in unlicensed spectrum, whereby LTE-based technologies operate exclusively in unlicensed spectrum without using an "anchor" in licensed spectrum (MultiFire). Further enhanced operation of LTE systems in licensed and unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for sidelink resource allocation and UE processing operations for NR sidelink V2X communications.

[0030] The NG system architecture (or 6G system architecture) may include a RAN 110 and a 5G Core Network (5GC) 120. The NG-RAN 110 may include multiple nodes such as a gNB and an NG-eNB. The CN 120 (e.g., 5G Core Network / 5GC) may include an Access and Mobility Function (AMF) and / or a User Plane Function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0031] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each gNB and NG-eNB can be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some aspects, the gNB can be a primary node (MN) and the NG-eNB can be a secondary node (SN) in the 5G architecture.

[0032] FIG. 1B illustrates a non-roaming 5G system architecture according to some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in a reference point representation, which can be extended to a 6G system architecture. More specifically, a UE 102 can communicate with a RAN 110, as well as one or more other 5G network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146.

[0033] The UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include a network slice selection function. The AMF 132 can provide UE-based authentication, authorization, mobility management, etc., and can be access technology independent. The SMF 136 can be configured to set up and manage various sessions according to network policies. Thus, the SMF 136 can be responsible for session management and IP address assignment to the UE. The SMF 136 can also select and control the UPF 134 for data transfer. The SMF 136 can be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 can have multiple 5G sessions. A different SMF can be assigned to each session. Using different SMFs allows each session to be managed separately. As a result, the functionality of each session is independent of each other.

[0034] The UPF 134 can be deployed in one or more configurations according to the desired service type and can connect to a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0035] The AF 150 can provide information about the packet flow to the PCF 148, which is responsible for policy control, to support the desired QoS. The PCF 148 can configure mobility and session management policies for the UE 101. To this end, the PCF 148 can use the packet flow information to determine appropriate policies for the appropriate operation of the AMF 132 and SMF 136. The AUSF 144 can store data for UE authentication.

[0036] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as a call session control function (CSCF), as well as an IP multimedia subsystem (IMS) 168B. More specifically, the IMS 168B includes a CSCF capable of operating as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B is configurable as the UE 102's first point of contact within the IM subsystem (IMS) 168B. The S-CSCF 164B is configurable to handle session state within the network, and the E-CSCF is configurable to handle specific aspects of the emergency session, such as routing the emergency request to the appropriate emergency center or PSAP. The I-CSCF 166B can be configured to serve as the contact point within the network of the network operator for all IMS connections destined for subscribers of that network operator or roaming subscribers currently located within the network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0037] In some aspects, the UDM / HSS 146 can be coupled to an application server 184, which can include a telephony application server (TAS) or another application server (AS) 160B. The AS 160B can be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0038] The reference point representation indicates that interactions can exist between corresponding NF services. For example, Figure 1B shows the following reference points: N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150 (not shown)), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148 (not shown)), N8 (between UDM 146 and AMF 132 (not shown)), N9 (between two UPFs 134 (not shown)), N10 (between UDM 146 and SMF 136 (not shown)), and N11 (between SMF 136 and PCF 148 (not shown)). 1B )), N11 (between the AMF 132 and the SMF 136 (not shown)), N12 (between the AUSF 144 and the AMF 132 (not shown)), N13 (between the AUSF 144 and the UDM 146 (not shown)), N14 (between two AMFs 132 (not shown)), N15 (between the PCF 148 and the AMF 132 in the case of a non-roaming scenario, or between the PCF 148, the visited network, and the AMF 132 in the case of a roaming scenario (not shown)), N16 (between two SMFs (not shown)), and N22 (between the AMF 132 and the NSSF 142 (not shown)). Other reference point representations not shown in FIG. 1B can also be used.

[0039] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in FIG. 1B, the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented as corresponding point-to-point reference points Ni or service-based interfaces.

[0040] 1C , a service-based representation may be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface indicated by the AMF 132), Nsmf 158I (service-based interface indicated by the SMF 136), Nnef 158B (service-based interface indicated by the NEF 154), Npcf 158D (service-based interface indicated by the PCF 148), Nudm 158E (service-based interface indicated by the UDM 146), Naf 158F (service-based interface indicated by the AF 150), Nnrf 158C (service-based interface indicated by the NRF 156), Nnssf 158A (service-based interface indicated by the NSSF 142), Nausf 158G (service-based interface indicated by the AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, Nudsf) may also be used.

[0041] The NR-V2X architecture can support highly reliable, low-latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0042] FIG. 2 illustrates a block diagram of a communications device according to some embodiments. Communications device 200 may be a dedicated computer, a personal or laptop computer (PC), a UE such as a tablet PC or smartphone, dedicated network equipment such as an eNB, a server running software that configures the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be performed by the machine. For example, communications device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded for reception by a receiving entity (e.g., gNB, UE) prior to transmission by the transmitting entity (e.g., UE, gNB) and decoded after receipt by the receiving entity.

[0043] Examples such as those described herein may include or operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a particular way. In examples, circuits may be arranged modularly (e.g., internally or with respect to external entities such as other circuits) in a particular way. In examples, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured with firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In examples, software may reside on a machine-readable medium. In examples, software, when executed by the underlying hardware of a module, causes the hardware to perform the specified operations.

[0044] Thus, the term "module" (and "component") is understood to encompass a tangible entity that is physically configured, specifically configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a particular manner or to perform some or all of any of the operations described herein. Consider examples in which the modules are temporarily configured, where each of the modules need not be instantiated at any one moment. For example, if the modules include a general-purpose hardware processor that is configured using software, the general-purpose hardware processor may be configured as each different module at different times. The software may thus configure the hardware processor, for example, to configure a particular module at one time and a different module at a different time.

[0045] The communication device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an internal link (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable, volatile, or non-volatile storage. The communication device 200 may further include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, the input device 212, and the UI navigation device 214 may be touchscreen displays. The communication device 200 may further include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The communication device 200 may further include an output control, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.)) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0046] Storage device 216 may include non-transitory machine-readable medium 222 (hereinafter simply referred to as machine-readable medium). Machine-readable medium 222 stores one or more data structures or sets of instructions 224 (e.g., software) that implement or are utilized by any one or more of the techniques or functions described herein. Instructions 224 may reside, completely or at least partially, within main memory 204, static memory 206, and / or within hardware processor 202 during execution by communications device 200. Although machine-readable medium 222 is depicted as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.

[0047] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions, or data structures used by or associated with such instructions, for execution by communication device 200 that cause communication device 200 to perform any one or more of the techniques of this disclosure. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory and flash memory devices, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)), magnetic disks, such as internal hard disks and removable disks, magneto-optical disks, random access memory (RAM), and CD-ROM and DVD-ROM disks.

[0048] The instructions 224 may further be transmitted or received over a communications network using a transmission medium via the network interface device 220526 utilizing any one of a number of wireless local area network (WLAN) transport protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Exemplary communications networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may be based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, the IEEE 802.16 family of standards known as WiMax, the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, Universal Mobile Telecommunications (UMTS), and other standards. The network interface device 220 may include one or more different protocols, such as the IEEE 802.11b / g (IEEE 802.11b) family of standards, peer-to-peer (P2P) networks, next-generation (NG) / fifth-generation (5G) standards, etc. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the transmission medium 226.

[0049] It should be noted that the term “circuitry” as used herein refers to, is a part of, or includes hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-volume PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide a described functionality. In some embodiments, a circuitry can execute one or more software or firmware programs to provide at least a portion of the described functionality. The term “circuitry” can also refer to a combination of one or more hardware elements (or combinations of circuitry used in an electrical or electronic system) and program code used to perform the functions of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0050] As used herein, the term "circuitry" or "processor" means, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term "processor circuitry" or "processor" can refer to one or more or multiple baseband processors, physical central processing units (CPUs), single or multi-core processors, and / or other devices capable of executing or otherwise manipulating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0051] The wireless links described herein may operate according to any one or more of the following wireless communication technologies and / or standards, including, but not limited to, Global System for Mobile Communications (GSM) wireless communication technology, General Packet Radio Service (GPRS) wireless communication technology, Enhanced Data Rates for GSM Evolution (EDGE) wireless communication technology, and / or Third Generation Partnership Project (3GPP) wireless communication technologies, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LTE Advanced (Long Term Evolution Advanced), 2000 CDMA2000 (Code division multiple access 2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed ​​Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation), and the like. Generation)), W-CDMA(UMTS)(Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA(High Speed ​​Packet Access), HSDPA(High-Speed ​​Downlink Packet Access), HSUPA(High-Speed ​​Uplink Packet Access), HSPA+(High Speed ​​Packet Access Plus), UMTS-TDD(Universal Mobile Telecommunications System-Time-Division Duplex), TD-CDMA(TimeDivision-Code Division Multiple Access), 3GPP Rel.8 (Pre-4G) (3rd Generation Partnership Project Release8 (Pre-4th Generation)), 3GPP Rel.9 (3rd Generation Partnership Project Release9), 3GPP Rel.10 (3rd Generation Partnership Project Release10), 3GPP Rel.11 (3rd Generation Partnership Project Release11), 3GPP Rel.12 (3rd Generation Partnership Project Release12), 3GPP Rel.13 (3rd Generation Partnership Project Release13), 3GPP Rel.14 (3rd Generation Partnership Project Release14), 3GPP Rel.15 (3rd Generation Partnership Project Release15), 3GPP Rel.16 (3rd Generation Partnership Project Release16), 3GPP Rel.17 (3rd Generation Partnership Project Release17) and later releases (3GPP Rel.18, 3GPP Rel.19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial Radio Access), LTEAdvanced (4G) (Long Term Evolution Advanced), cdmaOne (2G), CDMA2000 (3G) (Code division multiple access 2000 (Thirdgeneration), EV-DO (Evolution-Data Optimized or Evolution-Data Only), AMPS(1G) (Advanced Mobile Phone System (1st Generation)), TACS / ETACS (Total Access Communication System / Extended Total Access Communication System), D-AMPS(2G) (Digital AMPS (2nd Generation)), PTT (Push-to-Talk), MTS (Mobile Telephone System), IMTS (Improved Mobile Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian: Offentlig Land mobil Telefoni, Public Land Mobile Telephony), MTD (Swedish: Mobil telefoni system D, or an abbreviation for Mobile Telephony System D), Autotel / PALM (Public Automated Land Mobile), ARP (Finnish: Auto radio puhelin, "car radio phone"), NMT (Nordic Mobile Telephony), Hicap (NTT (Nippon Telegraph and High-capacity version of Telephone), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handy-Phone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, LAA (Unlicensed Mobile Access), 3GPP Generic AccessNetwork, or GAN standard), Zigbee, Bluetooth (registered trademark), WiGig (Wireless Gigabit Alliance) standard, mmWave standards in general (wireless systems operating in the 10-300 GHz band or higher, such as WiGig, IEEE802.11ad, IEEE802.11ay, etc.), technologies operating in the 300 GHz and THz bands or higher, (3GPP / LTE-based or IEEE802.11p or IEEE802.11bd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP Cellular V2X, DSRC (Dedicated Short Range Computing) such as Intelligent-Transport Systems Communications systems (typically operating in the frequency range of 5850 MHz to 5925 MHz or higher (typically up to 5935 MHz according to the proposed changes in CEPT Report 71)), European ITS-G5 systems (i.e., European variants of IEEE 802.11p-based DSRC, including ITS-G5A (i.e., operation of ITS-G5 in the European ITS frequency bands dedicated to ITS for safety-related applications in the frequency range of 5875 GHz to 5905 GHz), ITS-G5B (i.e., operation in the European ITS frequency bands dedicated to ITS non-safety applications in the frequency range of 5855 GHz to 5875 GHz), and ITS-G5C (i.e., operation of ITS applications in the frequency range of 5470 GHz to 5725 GHz)), 700 MHz-band DSRC in Japan (including 715 MHz to 725 MHz), and IEEE 802.11bd-based systems).

[0052] The aspects described herein can be used in the context of any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, license-exempt spectrum, (licensed) shared spectrum (e.g., LSA=Licensed Shared Access for 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies, SAS=Spectrum Access System / CBRS=Citizen Broadband Radio System for 3.55-3.7 GHz and further frequencies, etc.).Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum, and other types of spectrum / bands, such as bands with national allocations (450-470 MHz, 902-928 MHz (Note: allocated in e.g. the US (FCC Part 15)), 863-868.6 MHz (Note: allocated in e.g. the European Union (ETSI EN 300)). 220), 915.9-929.7MHz (Note: Allocated in Japan, for example), 917-923.5MHz (Note: Allocated in Korea, for example), 755-779MHz and 779-787MHz (Note: Allocated in China, for example), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: ISM band available worldwide, also used by the Wi-Fi family of technologies (11b / g / n / ax) and Bluetooth), 2500-2690MHz, 698-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: Allocated in the US, for example, by Citizen Broadband Radio The following bands are currently in use: 5.15-5.25 GHz, 5.25-5.35 GHz, 5.47-5.725 GHz, and 5.725-5.85 GHz (Note: allocated, for example, in the US (FCC part 15), consisting of four U-NII bands, totaling 500 MHz of spectrum); 5.725-5.875 GHz (Note: allocated, for example, in the EU (ETSI EN 301 893)); 5.47-5.65 GHz (Note: allocated, for example, in South Korea); 5925-7125 MHz, and 5925-6425 MHz (Note: allocated, for example, in the US and EU, respectively). Note that next-generation Wi-Fi systems are expected to operate in the 6 GHz spectrum, but as of December 2017, Wi-Fi systems are not yet permitted in this band. Coordination is expected to be completed in the 2019-2020 timeframe.), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800-4200 MHz, the 3.5 GHz band, the 700 MHz band, bands in the 24.25-86 GHz range, etc.), spectrum made available by the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHz, and 92-94 GHz, etc.), the Intelligent Transport Systems (ITS) bands 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, and bands currently allocated to WiGig, such as the WiGig Band WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57-64 / 66 GHz (Note: This band has a near-global designation for Multi-Gigabit Wireless Systems (MGWS) / WiGig. The US (FCC part 15) allocates a total of 14 GHz of spectrum, and the EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates a total of 9 GHz of spectrum), the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated for autonomous radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the system can be used secondary in bands such as TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being particularly promising candidates. In addition to cellular applications, vertical market specific applications can address PMSE (Program Making and Special Events), medical, health, surgery, automotive, low latency, drones, etc.

[0053] As mentioned above, inter-cell beam management is for forming, controlling, and detecting beams from a specific cell. In 5G NR Rel-15 / Rel-16, synchronization signals are included in the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block (SSB) and are transmitted periodically. SSBs can be used for beam management purposes. Inter-cell beam management may be based on SSBs with different cell IDs. In particular, Layer 1 Reference Signal Received Power (L1-RSRP) measurements can be used for beam detection.

[0054] In some situations, physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH) transmissions may overlap with SSBs. However, there are no scheduling constraints if the PDCCH / PDSCH overlaps with an SSB configured for L1-RSRP on the same resource element (RE) for inter-cell beam management. This can lead to beam management issues. Therefore, such overlap can increase complexity and degrade performance for the UE.

[0055] In RAN4, scheduling constraints arise for inter-cell L1-RSRP when SSB and data are scheduled in the same Orthogonal Frequency Division Multiplexing (OFDM) symbol. In particular, when the subcarrier spacing (SCS) between SSB and data is different and the UE does not support simultaneousRxDataSSB-DiffNumerology, scheduling constraints exist to avoid overlap of SSB and data within the same symbol. There are no other constraints for other scenarios. The specifications are as follows:

[0056] 9.13.6.1 Scheduling availability for UEs performing L1-RSRP measurements in Frequency Range 1 (FR1) with the same subcarrier spacing as PDSCH / PDCCH

[0057] On the serving cell of FR1 and on cells with a PCI different from that of the serving cell, there are no scheduling constraints due to L1-RSRP measurements performed on SSBs, as with the RS for L1-RSRP measurements with the same SCS as the PDSCH / PDCCH.

[0058] 9.13.6.2 Scheduling availability for UEs performing L1-RSRP measurements with different subcarrier spacing than PDSCH / PDCCH in FR1

[0059] For UEs that support simultaneousRxDataSSB-DiffNumerology, there are no constraints on scheduling availability due to L1-RSRP measurements based on SSBs, as with RSs for L1-RSRP measurements. For UEs that do not support simultaneousRxDataSSB-DiffNumerology, the following constraints due to L1-RSRP measurements based on SSBs configured for L1-RSRP measurements apply:

[0060] The UE is not expected to transmit the Physical Uplink Control Channel (PUCCH) / Physical Uplink Shared Channel (PUSCH) / Sounding Reference Signal (SRS) or receive the PDCCH / PDSCH / Channel State Information Reference Signal (CSI-RS) for Tracking / CSI-RS for Channel Quality Information (CQI) on symbols corresponding to SSB indices configured for L1-RSRP measurement, where the PUCCH / PUSCH / SRS transmission and PDCCH / PDSCH / CSI-RS for Tracking / CSI-RS for CQI reception may be on the serving cell and a cell with a different PCI than the serving cell.

[0061] The scheduling constraints are not exhaustive, as there are other scenarios where a scheduling constraint is desirable. In RAN4, inter-cell beam management requirements are defined for known cell conditions, so the known conditions are:

[0062] A cell with a different physical cell identity (PCI) than the serving cell is considered known in this requirement if the following conditions are met:

[0063] SSBs from cells with different PCIs are either completely contained in the active bandwidth portion (BWP) or are associated with the UE's initial downlink BWP.

[0064] An SSB from a cell with a different PCI than the serving cell has the same SCS, sfn-SSB-Offset, and center frequency as the serving cell's SSB.

[0065] The timing difference of arrival at the UE between the SSB of the serving cell and the SSB of a cell with a different PCI is less than the cyclic prefix (CP) length of the corresponding SCS.

[0066] The UE has sent a valid L3 measurement report in the last 5 seconds.

[0067] SSBs from cells with different PCIs remain detectable according to the cell identification requirements specified in Section 9.2.

[0068] It can be seen that the SSB offsets are the same for the two cells. However, due to the different periodicity of SSBs from cells with different PCIs than the serving cell, PDCCH / PDSCH reception from one cell may overlap with SSBs for L1-RSRP measurement from another cell on the same RE within the same symbol.

[0069] Figure 3 illustrates cell overlap according to some embodiments. Figure 4 illustrates cell overlap according to some embodiments. In Figure 3, the serving cell's data overlaps with SSBs from another cell on the same RE within the same symbol, as indicated by the oval. In Figure 4, the serving cell's SSB overlaps with data from another cell on the same RE within the same symbol, as indicated by the oval.

[0070] Overlap on the same RE may cause performance degradation and may add complexity to the UE if it performs measurements and data reception simultaneously. Therefore, additional scheduling constraints may be introduced to avoid overlap. These constraints can be defined as follows:

[0071] Case 1: Scheduling availability for UEs performing L1-RSRP measurements at the same subcarrier spacing as PDSCH / PDCCH in FR1: If at least one RE of PDCCH / PDSCH overlaps with at least one RE of SSBs configured for L1-RSRP measurements from a cell with a different PCI, the UE is not expected to receive PDCCH / PDSCH on the symbols corresponding to the SSB index configured for L1-RSRP measurements. In this case, PDCCH / PDSCH reception may occur in the serving cell and in cells with a different PCI from the serving cell.

[0072] Case 2: Scheduling availability for UEs performing L1-RSRP measurements at a subcarrier spacing different from that of the PDSCH / PDCCH in FR1: For UEs that support simultaneousRxDataSSB-DiffNumerology, if at least one RE of the PDCCH / PDSCH overlaps with at least one RE of an SSB configured for L1-RSRP measurements from a cell with a different PCI, the UE does not expect to receive the PDCCH / PDSCH on the symbol corresponding to the SSB index configured for L1-RSRP measurements. In this case, PDCCH / PDSCH reception may occur in the serving cell and in cells with a different PCI from the serving cell.

[0073] For a UE that does not support simultaneousRxDataSSB-DiffNumerology, the UE does not intend to transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI on symbols corresponding to SSB indices configured for L1-RSRP measurement. In this case, transmission of PUCCH / PUSCH / SRS and reception of PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI may occur in the serving cell and in a cell with a PCI different from that of the serving cell.

[0074] The scheduling constraints for L3 measurements may be updated as well.

[0075] UE reporting behavior

[0076] In the current specification, the UE is required to report L1-RSRP results only in known cell conditions.

[0077] 9.13.3 Measurement Reporting Requirements

[0078] The UE reports only for the configured reporting settings for the active BWP (for cells with a different PCI than the serving cell in known cell conditions) (in other cases the UE does not send an L1-RSRP report).

[0079] The current definition for a known cell is:

[0080] A cell with a different PCI than the serving cell is considered known if the following conditions are met:

[0081] SSBs from cells with different PCIs may be completely included in an active BWP or may be associated with the UE's initial downlink BWP.

[0082] An SSB from a cell with a different PCI than the serving cell has the same SCS, sfn-SSB-Offset, and center frequency as the serving cell's SSB.

[0083] The timing difference of arrival at the UE between the SSB of the serving cell and the SSB of a cell with a different PCI is less than the CP length of the corresponding SCS.

[0084] The UE has sent a valid L3 measurement report in the last 5 seconds.

[0085] SSBs from cells with different PCIs remain detectable according to the cell identification requirements specified in Section 9.2.

[0086] Otherwise, the cell is unknown.

[0087] One special condition relates to the timing offset, which may vary over time, and requires extra effort from the UE to calculate the timing offset and compare it with the CP length. Therefore, it may be more desirable not to restrict the UE's reporting behavior.

[0088] If the timing difference of arrival at the UE between the SSB of the serving cell and the SSB of a cell with a different PCI is greater than the CP length, the UE does not need to report L1-RSRP measurements. If the UE reports L1-RSRP measurements, the UE may not meet the L1-RSRP measurement reporting requirements based on the accuracy requirements when the timing offset is below a threshold.

[0089] In some embodiments, if the round trip delay between the serving cell and the neighboring cell is within the CP, the legacy measurement and scheduling constraints used for non-serving cells may be applied to intra-frequency L1-RSRP measurements on the neighboring cell.

[0090] In some embodiments, the electronic devices, networks, systems, chips, or components of the above figures, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein. One such process that may be performed by a UE, one or more elements of a UE, and / or one or more electronic devices including or implementing one or more elements of a UE is illustrated in FIG. 5. FIG. 5 illustrates a process for identifying signal overlap, according to some embodiments. Process 500 may include, at operation 502, identifying that a data transmission overlaps with an SSB associated with an L1 RSRP of another cell, and, at operation 504, identifying the received data transmission based on the identification.

[0091] One such process that may be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include or implement one or more elements of a base station is shown in Figure 6. Figure 6 illustrates a process for transmitting a signal to a UE according to some embodiments. Process 600 may include, at operation 602, identifying that a data transmission overlaps with an SSB associated with an L1 RSRP of another cell, and, at operation 604, transmitting the data transmission to the UE based on the identification.

[0092] example

[0093] (Example 1) An apparatus for a next generation (NG) network element, the apparatus comprising: A processing circuit, determining a scheduling constraint for a user equipment (UE) that avoids overlap between a synchronization signal block (SSB) for Layer 1 reference signal received power (L1-RSRP) measurement and at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH); determining whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings; a processing circuit that, in response to determining that the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing, applies the scheduling constraint, wherein application of the scheduling constraint depends on whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing; a memory configured to store the scheduling constraints; Equipment including.

[0094] (Example 2) The device described in Example 1, wherein at least one of the PDCCH or PDSCH is from a serving cell and the SSB is from a cell having a physical cell identifier (PCI) different from the serving cell.

[0095] (Example 3) An apparatus as described in Examples 1 to 2, wherein the SSB is from a serving cell and at least one of the PDCCH or PDSCH is from a cell having a physical cell identifier (PCI) different from the serving cell.

[0096] (Example 4) The device according to Examples 1 to 3, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in frequency range 1 (FR1).

[0097] (Example 5) The device of Examples 1 to 4, wherein the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing and are transmitted in frequency range 1 (FR1).

[0098] (Example 6) The processing circuit determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; applying the scheduling constraint in response to determining that the UE supports simultaneousRxDataSSB-DiffNumerology. 6. The device of Example 5, configured to:

[0099] (Example 7) The processing circuit determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; In response to determining that the UE does not support simultaneousRxDataSSB-DiffNumerology, on symbols corresponding to SSB indices configured for L1-RSRP measurements, Transmitting any one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS); or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); Deciding not to assume The device according to Examples 5 to 6, configured as follows:

[0100] (Example 8) The device described in Examples 1 to 7, wherein the processing circuitry is configured to determine a reporting constraint for the UE, the reporting constraint including limiting transmission by the UE of an L1-RSRP report including the L1-RSRP measurement to a serving cell of the UE to a reporting configuration configured for an active bandwidth portion (BWP).

[0101] (Example 9) The device described in Example 8, further indicating that the reporting constraint can avoid the UE from transmitting the L1-RSRP report for a timing difference of arrival at the UE between an SSB of the serving cell and an SSB of a cell having a different physical cell identifier (PCI) than the serving cell's cyclic prefix (CP) length of the corresponding subcarrier spacing (SCS).

[0102] (Example 10) The device described in Example 9, wherein the reporting constraint further indicates that for timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements.

[0103] (Example 11) A device of a user equipment (UE), the device comprising: A processing circuit for configuring the UE to: receiving a synchronization signal block (SSB) from one of the serving cell or another cell, the other cell having a different physical cell identifier (PCI) from the serving cell; receiving at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) from the other of the serving cell or the other cell, wherein the SSB and the at least one of the PDCCH or PDSCH are subject to a scheduling constraint to avoid overlap between the SSB and the at least one of the PDCCH or PDSCH, the scheduling constraint depending on whether the SSB and the at least one of the PDCCH or PDSCH have different subcarrier spacings; performing a Layer 1 Reference Signal Received Power (L1-RSRP) measurement based on the SSB; sending an L1-RSRP report to the serving cell depending on a reporting constraint, the L1-RSRP report including the L1-RSRP measurements; a processing circuit configured as follows: a memory configured to store the scheduling constraints; Equipment including.

[0104] (Example 12) The device described in Example 11, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in frequency range 1 (FR1), and the scheduling constraint is applied to the SSB and at least one of the PDCCH or PDSCH having the same subcarrier spacing.

[0105] (Example 13) The device described in Examples 11 to 12, wherein the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing and are transmitted in frequency range 1 (FR1), and the scheduling constraint is applied in response to the UE supporting simultaneousRxDataSSB-DiffNumerology.

[0106] (Example 14) The SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); In response to the UE not supporting simultaneousRxDataSSB-DiffNumerology, On the symbol corresponding to the SSB index configured for L1-RSRP measurement, the UE: Transmitting any one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS); or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); The device described in Examples 11 to 13, which determines that the above does not apply.

[0107] (Example 15) The processing circuitry is configured such that the report constraint is: Limiting the sending of L1-RSRP reports to the report configuration configured for the active bandwidth portion (BWP); avoiding transmission of the L1-RSRP report for timing differences of arrival at the UE between an SSB of a serving cell and an SSB of another cell that are greater than a cyclic prefix (CP) length of a corresponding subcarrier spacing (SCS); For timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements; The device of Examples 11-14, configured to determine that the device includes:

[0108] Example 16. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a next generation (NG) network element, the one or more processors, when executed, performing: determining a scheduling constraint for a user equipment (UE) that avoids overlap between a synchronization signal block (SSB) for Layer 1 reference signal received power (L1-RSRP) measurement and at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH); determining whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings; In response to determining that the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing, applying the scheduling constraint, wherein application of the scheduling constraint depends on whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing.

[0109] (Example 17) The medium of Example 16, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in frequency range 1 (FR1).

[0110] (Example 18) The SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); The instructions, when executed by the one or more processors, cause the one or more processors to: determining whether the UE supports symetiousRxDataSSB-DiffNumerology; applying the scheduling constraint in response to determining that the UE supports symetiousRxDataSSB-DiffNumerology. The medium according to Examples 16-17, further comprising:

[0111] (Example 19) The SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); The instructions, when executed by the one or more processors, cause the one or more processors to: determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; In response to determining that the UE does not support simultaneousRxDataSSB-DiffNumerology, On the symbol corresponding to the SSB index configured for L1-RSRP measurement, the UE: Transmitting any one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS); or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); Deciding not to assume The medium according to Examples 16 to 18, further comprising:

[0112] (Example 20) When executed by the one or more processors, further configuring the one or more processors to receive from the UE an L1-RSRP report including the L1-RSRP measurement depending on a reporting constraint; The report constraints are: Limiting the sending of L1-RSRP reports to the report configuration configured for the active bandwidth portion (BWP); avoiding transmission of the L1-RSRP report for timing differences of arrival at the UE between an SSB of a serving cell and an SSB of another cell that are greater than a cyclic prefix (CP) length of a corresponding subcarrier spacing (SCS); For timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements; The medium according to Examples 16 to 19, comprising:

[0113] (Example 21) At least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of Examples 1-20.

[0114] (Example 22) An apparatus including means for carrying out any of Examples 1 to 20.

[0115] (Example 23) A system for implementing any of Examples 1 to 20.

[0116] Example 24: A method for carrying out any of Examples 1 to 20.

[0117] While the embodiments have been described with reference to specific exemplary embodiments, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broad scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative and not a restrictive sense. The accompanying drawings, which form a part of this specification, show, by way of example, and not by way of limitation, specific embodiments in which the subject matter may be practiced. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the techniques disclosed herein. Other embodiments may be utilized and derived therefrom, and accordingly, structural, logical, and electrical changes may be made without departing from the scope of the present disclosure. This detailed description is therefore not to be taken in a limiting sense, and the scope of various embodiments is defined solely by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0118] Subject matter may be referred to herein by the term "embodiment," individually and / or collectively, for convenience only, and where in fact multiple inventions are disclosed, without any intention to limit the scope of the application to any single inventive concept. Thus, although specific embodiments have been shown and described herein, it should be understood that any configuration calculated to achieve the same purpose may be substituted for the specific embodiment shown. The present disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above-described embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art upon reference to the foregoing description.

[0119] As used herein, the terms "a" or "an" are used, as is common in patent documents, to indicate one or more than one, independently of any other instance or use of "at least one" or "one or more." The term "or" is used herein to indicate non-exclusion. Thus, "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise specified. The terms "including" and "in which" are used herein as the plain-English equivalents of the terms "comprising" and "wherein," respectively. Also, in the following claims, the terms "including" and "comprising" are intended to be non-limiting, meaning that systems, UEs, articles, compositions, formulas, or processes that include elements in addition to those recited in the claims following such terms are still considered to be within the scope of those claims. Furthermore, in the following claims, the terms "first," "second," "third," etc. are used merely as labels and are not intended to impose numerical requirements on their objects. As indicated herein, although the term "a" is used herein, one or more of the associated elements may be used in different embodiments. For example, the term "processor" configured to perform certain operations includes both a single processor configured to perform all operations and multiple processors individually configured to perform some or all operations, such that a combination of processors performs all operations. Furthermore, the term "comprising" should be interpreted as "including at least" the following elements:

[0120] It is understood that this Abstract of the Disclosure will not be used to interpret or limit the scope or meaning of the claims. Moreover, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

1. 1. An apparatus for a next generation (NG) network element, the apparatus comprising: A processing circuit, determining a scheduling constraint for a user equipment (UE) that avoids overlap between a synchronization signal block (SSB) for Layer 1 reference signal received power (L1-RSRP) measurement and at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH); determining whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings; a processing circuit that, in response to determining that the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing, applies the scheduling constraint, the application of the scheduling constraint depending on whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing; a memory configured to store the scheduling constraints; Equipment including.

2. 2. The device of claim 1, wherein at least one of the PDCCH or PDSCH is from a serving cell and the SSB is from a cell having a different physical cell identifier (PCI) than the serving cell.

3. 2. The device of claim 1, wherein the SSB is from a serving cell and at least one of the PDCCH or PDSCH is from a cell having a different physical cell identifier (PCI) than the serving cell.

4. The device of any one of claims 1 to 3, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in frequency range 1 (FR1).

5. The device of any one of claims 1 to 3, wherein the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1).

6. The processing circuitry determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; applying the scheduling constraint in response to determining that the UE supports simultaneousRxDataSSB-DiffNumerology.

6. The device of claim 5, configured to:

7. The processing circuitry determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; In response to determining that the UE does not support simultaneousRxDataSSB-DiffNumerology, on symbols corresponding to SSB indices configured for L1-RSRP measurements, the UE: Transmitting any one of a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and a Sounding Reference Signal (SRS), or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); Deciding not to assume 6. The device of claim 5, configured to:

8. 4. The device of claim 1, wherein the processing circuitry is configured to determine a reporting constraint for the UE, the reporting constraint comprising limiting transmission by the UE of an L1-RSRP report including the L1-RSRP measurement to a serving cell of the UE to a reporting configuration configured for an active bandwidth portion (BWP).

9. 10. The device of claim 8, wherein the reporting constraint further indicates that the UE may avoid transmitting the L1-RSRP report for a timing difference of arrival at the UE between an SSB of the serving cell and an SSB of a cell having a different physical cell identifier (PCI) than the serving cell's cyclic prefix (CP) length of a corresponding subcarrier spacing (SCS).

10. 10. The device of claim 9, wherein the reporting constraint further indicates that for timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements.

11. A device of a user equipment (UE), the device comprising: A processing circuit for configuring the UE to: receiving a synchronization signal block (SSB) from one of a serving cell or another cell, the other cell having a different physical cell identifier (PCI) than the serving cell; receiving at least one of a Physical Downlink Control Channel (PDCCH) or a Physical Downlink Shared Channel (PDSCH) from the other of the serving cell or the other cell, wherein the SSB and the at least one of the PDCCH or PDSCH are subject to a scheduling constraint to avoid overlap between the SSB and the at least one of the PDCCH or PDSCH, the scheduling constraint depending on whether the SSB and the at least one of the PDCCH or PDSCH have different subcarrier spacings; performing a Layer 1 Reference Signal Received Power (L1-RSRP) measurement based on the SSB; sending an L1-RSRP report to the serving cell depending on a reporting constraint, the L1-RSRP report including the L1-RSRP measurements; a processing circuit configured as follows: a memory configured to store the scheduling constraints; Equipment including.

12. 12. The device of claim 11, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in Frequency Range 1 (FR1), and the scheduling constraint applies to the SSB and at least one of the PDCCH or PDSCH having the same subcarrier spacing.

13. 12. The device of claim 11, wherein the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing and are transmitted in Frequency Range 1 (FR1), and the scheduling constraint is applied in response to the UE supporting simultaneousRxDataSSB-DiffNumerology.

14. the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); In response to the UE not supporting simultaneousRxDataSSB-DiffNumerology, On the symbol corresponding to the SSB index configured for L1-RSRP measurement, the UE: Transmitting any one of a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and a Sounding Reference Signal (SRS), or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); The device of claim 11, wherein the device determines that the

15. The processing circuitry may be configured to: Limiting the sending of L1-RSRP reports to the report configuration configured for the Active Bandwidth Portion (BWP); avoiding transmission of the L1-RSRP report for timing differences of arrival at the UE between an SSB of a serving cell and an SSB of another cell that are greater than a cyclic prefix (CP) length of a corresponding subcarrier spacing (SCS); For timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements; 15. The apparatus of claim 11, configured to determine that the signal comprises:

16. 1. A computer-readable storage medium storing instructions for execution by one or more processors of a next generation (NG) network element, the instructions causing the one or more processors to: determining a scheduling constraint for a user equipment (UE) that avoids overlap between a synchronization signal block (SSB) for Layer 1 reference signal received power (L1-RSRP) measurement and at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH); determining whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings; In response to determining that the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing, applying the scheduling constraint, wherein application of the scheduling constraint depends on whether the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacing.

17. 17. The medium of claim 16, wherein the SSB and at least one of the PDCCH or PDSCH have the same subcarrier spacing and are transmitted in Frequency Range 1 (FR1).

18. The SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); The instructions, when executed by the one or more processors, cause the one or more processors to: determining whether the UE supports symetiousRxDataSSB-DiffNumerology; applying the scheduling constraint in response to determining that the UE supports symetiousRxDataSSB-DiffNumerology.

17. The medium of claim 16, further configured to:

19. the SSB and at least one of the PDCCH or PDSCH have different subcarrier spacings and are transmitted in frequency range 1 (FR1); The instructions, when executed by the one or more processors, cause the one or more processors to: determining whether the UE supports simultaneousRxDataSSB-DiffNumerology; In response to determining that the UE does not support simultaneousRxDataSSB-DiffNumerology, On the symbol corresponding to the SSB index configured for L1-RSRP measurement, the UE: Transmitting any one of a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and a Sounding Reference Signal (SRS), or receiving at least one of a PDCCH or a PDSCH or a channel state information reference signal (CSI-RS) for tracking or channel quality information (CQI); Deciding not to assume 17. The medium of claim 16, further configured to:

20. The instructions, when executed by the one or more processors, further configure the one or more processors to: receive from the UE an L1-RSRP report including the L1-RSRP measurement depending on a reporting constraint; The report constraints are: Limiting the sending of L1-RSRP reports to the report configuration configured for the Active Bandwidth Portion (BWP); avoiding transmission of the L1-RSRP report for timing differences of arrival at the UE between an SSB of a serving cell and an SSB of another cell that are greater than a cyclic prefix (CP) length of a corresponding subcarrier spacing (SCS); For timing offsets lower than the CP length, the L1-RSRP measurements in the L1-RSRP report may not meet L1-RSRP measurement reporting requirements based on accuracy requirements; The medium according to any one of claims 16 to 19, comprising:

Images