GAP

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States

Provisional Patent Application Serial No. 63/134,086, filed January 5, 2021, and United States Provisional Patent Application Serial No. 63/134,120, filed January 5, 2021, each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to next generation wireless communications. In particular, some embodiments relate to user equipment (UE) measurements during measurement gaps (MG).

BACKGROUND

[0003] The use and complexity of wireless systems, which include 5 ^th generation (5G) networks and are starting to include sixth generation (6G) networks among others, has increased due to both an increase in the types of devices UEs using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated. As expected, a number of issues abound with the advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES [0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document. [0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.

[0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. [0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates a flow diagram of a handover (HO) process in accordance with some aspects.

[0010] FIG. 4 illustrates bandwidth part (BWP) switching delay in accordance with some aspects.

[0011] FIG. 5 illustrates UE measurement behavior in accordance with some aspects. [0012] FIG. 6 illustrates UE behavior in accordance with some aspects.

DETAILED DESCRIPTION

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

[0014] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0015] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0016] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 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), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0017] In some aspects, any of the UEs 101 and 102 can comprise an

Intemet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short lived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep alive messages, status updates, etc.) to facilitate the connections of the IoT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0018] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), aNextGen RAN (NG RAN), or some other type of RAN.

[0019] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0020] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising 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] The UE 102 is shown to be configured to access an access point

(AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further 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, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances 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 NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0023] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for 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 an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

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

[0025] In this aspect, the CN 120 comprises the MMEs 121, the S-GW

122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0026] The S-GW 122 may terminate the SI interface 113 towards the

RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0027] The P-GW 123 may terminate an SGi interface toward a PDN.

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

[0028] The P-GW 123 may further be a node for policy enforcement and charging data collection. 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 a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a 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 communication network 140A can be an IoT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G R) and the unlicensed (5G R-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0030] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. [0031] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

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

[0033] The UPF 134 can provide a connection 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 network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0034] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to 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 may provide information on the packet flow to the

PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0036] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, 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 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0038] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),

N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown),

N10 (between the UDM 146 and the SMF 136, not shown), Nil (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 case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used. [0039] FIG. 1C illustrates a 5G system architecture 140C and a service- based representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

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

[0041] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0042] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure 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 taken by that machine. For example, the communication 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 before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0043] Examples, as described herein, may include, or may operate on, logic or a number of 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 certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0044] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0045] The communication device 200 may include a hardware processor (or equivalently 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 interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. 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, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, 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 or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0046] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated 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 the one or more instructions 224.

[0047] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; 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 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 ^th generation (5G) standards among others. 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 to connect to the transmission medium 226.

[0049] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0050] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[0051] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3 GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), 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) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel.

15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc ), 3 GPP 5G, 5G, 5G New Radio (5G R), 3 GPP 5G New Radio, 3 GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, EIMTS Terrestrial Radio Access (UTRA), Evolved EIMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy- phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. llad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 lp or IEEE 802.1 lbd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to-Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 lp based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 lbd based systems, etc.

[0052] 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 (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 lb/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under 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 ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as 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 near-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0053] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc. [0054] Aspects described herein can also be applied to different Single

Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0055] Some of the features are defined for the network side, such as

APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0056] As above, measurement gaps are used by a UE to perform measurements when the UE is unable to measure a target frequency while simultaneously transmitting/receiving on the serving cell. The serving cell does not transmit during measurement gaps to allow the UE to use the measurement gaps to perform inter-frequency and inter-radio access technology (RAT) measurements of neighbor cells. In one example, during the measurement gaps the UE may perform measurements on signalling system blocks (SSBs) of the neighbor cells. After the measurements are obtained and provided to the gNB, the network may determine, for example, whether handover of UE to a different gNB is appropriate. FIG. 3 illustrates a flow diagram of a handover process in accordance with some aspects. As shown:

[0057] 1. The source gNB-CU-CP sends HANDOVER REQUEST message to the target gNB-CU-CP. In case of Conditional Handover, the target gNB is regarded as a candidate gNB which is only accessed by the UE when the CHO condition(s) are fulfilled.

[0058] 2-4. Bearer Context Setup procedure is performed as described in Section 8.9.2 of 3GPP TS 38.401.

[0059] 5. The target gNB-CU-CP responds the source gNB-CU-CP with a HANDOVER REQUEST ACKNOWLEDGE message.

[0060] 6. The FI UE Context Modification procedure is performed to send the handover command to the UE, and to indicate to stop the data transmission for the UE. [0061] 7-8. Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer.

[0062] 9. The source gNB-CU-CP sends an SN STATUS TRANSFER message to the target gNB-CU-CP.

[0063] 10-11. Bearer Context Modification procedure is performed as described in Section 8.9.2. The target gNB-CU-CP does not transfer the PDCP UL/DL status carried from the SN STATUS TRANSFER message to the target gNB-CU-UP if the PDCP status does not need to be preserved (e.g. full configuration).

[0064] 12. Data Forwarding may be performed from the source gNB-

CU-UP to the target gNB-CU-UP.

[0065] 12a. In case of DAPS Handover or Conditional Handover, the target gNB-CU-CP sends the HANDOVER SUCCESS message to the source gNB-CU-CP to inform that the UE has successfully accessed the target cell.

[0066] 12b. In case of DAPS Handover or Conditional Handover, the

FI UE Context Modification procedure is performed to indicate to stop the data transmission for the UE.

[0067] 12c-12d. In case of DAPS Handover or Conditional Handover, the Bearer context modification procedure (gNB-CU-CP initiated) is performed to indicate the source gNB-CU-UP to stop packet delivery and also to retrieve the PDCP UL/DL status.

[0068] 12e. In case of DAPS Handover or Conditional Handover, the source gNB-CU-CP sends the SN STATUS TRANSFER message to the target gNB-CU-CP.

[0069] 12f-12g. In case of DAPS Handover or Conditional

Handover, the Bearer context modification procedure is performed to provide the PDCP UL/DL status to the target gNB-CU-UP only if the PDCP status needs to be preserved as described in TS 38.300. [0070] 13-15. Path Switch procedure is performed to update the DL

TNL address information for the NG-U towards the core network.

[0071] 16. The target gNB-CU-CP sends an UE CONTEXT

RELEASE message to the source gNB-CU-CP.

[0072] 17. and 19. Bearer Context Release procedure is performed. [0073] 18. FI UE Context Release procedure is performed to release the UE context in the source gNB-DU.

[0074] Turning back to the measurement gap, various configurations may be defined using RRC signaling (the RRC Reconfiguration message), dependent on the UE capability to support independent frequency range measurement and network preference. The network provides the timing of neighbor cell SSBs using a SS/physical broadcast channel (PBCH) Block Measurement Timing Configuration (SMTC). A typical gap length is 6 ms, of which 5 ms is used for measurement and 0.5 ms is used for RF re-tuning before and after the measurement gap. The measurement gap may repeat with a predetermined periodicity, e.g., 40 ms or 80 ms. In NR, measurement gap lengths of 1.5, 3, 3.5, 4, 5.5, and 6 ms may be used with measurement gap repetition periodicities of 20, 40, 80, and 160 ms, and a re-tuning time of 0.5 ms for carrier frequency measurements in frequency range 1 (FR1) and 0.25 ms for FR2.

[0075] In existing NR systems, two types of measurement gaps have been specified: per-UE and per-FR. The corresponding gap patterns and applicability are also defined in 3GPP TS 38.133 vl6.5.0 (2020-10-09) for both non-standalone (NS A) and standalone (SA) scenarios. TS 38.133 is herein incorporated by reference. However, some of the restriction conditions were assumed for the measurement gap design, which may also directly or indirectly cause limitations to network and UE implementation. In order to optimize the efficiency of Radio Resource Management (RRM) functionalities on both network and UE sides, enhancement of the current measurement gap design may be provided in Rel-17 standards. Potential enhancements include preconfigured measurement gap patterns (fast measurement gap configuration) per configured bandwidth part (BWP), multiple concurrent and independent measurement gap patterns, and use of a Network Controlled Small Gap (NCSG).

[0076] According to TS 38.321-5.15 BWP operation, BWP switching - i.e., switching between different BWPs (e.g., in different measurement gaps) can be performed based on a number of different scenarios. These scenarios include dedicated RRC signaling, over physical downlink control channel (PDCCH) downlink control information (DCI) (DCI 0 1 (UL Grant) and DCI 1 0 (DL Scheduling)), expiration of a bwp-inactivityTimer - ServingCellConfig.bwp- InactivityTimer, or by a medium access control (MAC) Control Element (CE).

In particular, the UE has an initial active BWP (e.g., default BWP) during the initial access until the UE is explicitly configured with BWPs during or after RRC connection establishment. At most one active DL BWP and at most one active UL BWP exists for the UE. bwp-inactivityTimer is the duration in ms after which the UE falls back to the default BWP.

[0077] The RRM requirements for preconfigured measurement gap patterns include mechanisms of activation/deactivation of a measurement gap following a downlink control information (DCI) or a timer-based BWP switch, e.g., a per-BWP measurement gap configuration, the specification of rules and UE behavior for activation/deactivation of a measurement gap following a DCI or timer-based BWP switch, and definitions of measurement period requirements with preconfigured measurement gap patterns in the presence of one or more BWP switch per measurement period. In addition, embodiments herein describe both the applicability, as well as procedures and signaling, for preconfigured measurement gap patterns, the latter of which includes the specification of protocol impacts of the mechanisms of activation/deactivation of the measurement gap following a DCI or timer-based BWP switch (e.g., per BWP measurement gap configuration based on a RAN4 input). Embodiments herein define UE capability on UE measurements with the preconfigured gaps in NR. [0078] FIG. 4 illustrates UE behavior in accordance with some aspects.

The example of FIG. 4 may operate as follows:

[0079] At operation 1, before the BWP switching, the UE can measure

SSB/CSI-RS of the serving cell and one or more neighbor cells that are in the same BWP as the active BWP of the UE. A measurement gap after BWP switching can be preconfigured by the serving gNB and forwarded to the UE with RRC signaling. In some implementations, more than one measurement gap pattern can be preconfigured as more than one type of measurement may be taken (e.g., SSB/multiple SSB/CSI-RS) after the BWP switch.

[0080] At operation 2, BWP switching is triggered by DCI or by timer based rather than via RRC signaling. When BWP switching occurs, interruption to the serving cell/activated BWP can be allowed (see e.g., TS 38.133, clause 8.2.1.2.7). The preconfigured gaps after T2 may be activated by the serving gNB. In some implementations, measurement gap activation can be included in the same DCI for BWP switching (e.g., using a suitable indicator field in the DCI, or the like) or may be activated afterwards.

[0081] At operation 3, when the UE decodes the DCI (for example), the

UE is able to determine BWP switching command after a BWP switching delay. Thus, the other BWP may be activated as shown in FIG. 5 at tO.

[0082] At operation 4, the DCI can be decoded by the UE to determine the (simultaneously activated) preconfigured measurement gap. Then, at the first SSB/CSI-RS resource to be measured after BWP switching (e.g., the second SSB for neighbor 1 FIG. 5), the UE may retune to the central frequency of the bandwidth in which the SSB/CSI is to be measured. During the gap interval (e.g., during GAP#1 and GAP #2), the serving gNB may not schedule any data to the UE to permit the UE to perform the configured measurements on another frequency. At the end of the measurement gap the UE may retune to the activated BWP. [0083] At operation 5, if the UE-activated BWP has switched to the original BWP, which can overlap with the SSB/CSI, the measurement gap may be automatically disabled. That is, the serving gNB can schedule data transmission to the UE after the BWP switch to the original BWP. The UE can report the measurement data to the serving gNB before or after switching to the original BWP.

[0084] Based on the preconfigured gap example of FIG. 4, multiple

RRM requirements can be studied and/or enhanced.

[0085] Delay for Measurement Gap Activation [0086] One of the RRM requirements is the delay for measurement gap activation. For example, in operation 2 of FIG. 4, when the preconfigured measurement gap is activated after BWP switching, the delay for measurement gap activation is specified as a BWP switching delay in TS 38.133. FIG. 5 illustrates BWP switching delay in accordance with some aspects. As shown in FIG. 5, BWP is triggered by DCI, in particular, the UE decodes the DCI command to trigger BWP switching at slot n. After m slots (which may include a partial slot), the UE may be ready for reconfiguration of the RF or baseband (BB), and the new RF/BB parameters may be applied during the next slot. Thus, the delay may extend, as shown, from the beginning of slot n to the end of slot n+m+1.

[0087] Depending on whether the DCI command to activate the preconfigured measurement gap can be conveyed together with that of the DCI command to activate BWP switching, the delay of the measurement gap activation can be either separated or not separated. In the latter case, the DCI for the preconfigured measurement gap may be piggybacked in the DCI for BWP activation. In the former case, the use of an extra DCI for the preconfigured measurement gap may significantly impact RANI standardization. In various embodiments, a UE can autonomously activate the preconfigured measurement gap using a BWP switching DCI in Rel-15.

[0088] Thus, the preconfigured measurement gap pattern may be indicated to the UE prior to switching to the new BWP. Activation of the preconfigured measurement gap pattern may be indicated to the UE at the time the UE is instructed to switch to the new BWP, or may be delayed until later. [0089] Depending on UE capability bwp-SwitchingDelay, the UE finishes BWP switch within the time duration TewPswitchDeiay defined in Table

8.6.2-1.

Table 8.6.2-1: BWP switch delay _ _

[0090] Interruption Requirements

[0091] In various embodiments, a preconfigured measurement gap can include the duration for RF retuning. During the measurement gap, the serving gNB may not schedule data to the activated serving cells (PCell/SCell) and BWP. This may avoid interruption to the serving cell or activated BWP. [0092] The preconfigured measurement gaps used for measurement after the BWP switching may have little impact on the measurement minimum performance requirement (e.g., cell detection delay, measurement period, etc.). That is, the measurement delay requirements can be same as that of intra frequency measurement in Section 9.2 of TS 38.133. However, scheduling restrictions may be revisited (e.g., TS 38.133, clause 9.2.1. “For intra-frequency SSB based measurements without measurement gaps, UE may cause scheduling restriction as specified in clause 9.2.5.3”).

[0093] Measurement Period Requirements

[0094] According to various embodiments, the minimum requirements for intra-frequency SSB measurement can follow that of intra-frequency SSB measurement requirements with the gap specified in clause 9.2.6 of TS 38.133. According to various embodiments, the minimum requirements for intra frequency SSB measurements and CSI-RS measurements with a preconfigured measurement gap can follow that of intra-frequency SSB measurement requirements with a measurement gap specified in clause 9.2.6 of TS 38.133 and inter-frequency CSI-RS measurement requirements specified in clause 9.10.3 of TS 38.133, respectively.

[0095] Applicability of a Preconfigured Measurement Gap Period

[0096] Since BWP switching is per-UE, the relevant operations (e.g., both BWP and preconfigured measurement gap activation) is per-UE. Thus, the applicability of a preconfigured measurement gap is per-UE.

[0097] APPLICATION SCENARIOS

[0098] One application scenario to utilize a pre-config measurement gap is an intra-frequency SSB-based measurement after BWP switching. However, since multiple measurements (e.g., SSB, channel state information reference signals (CSI-RS), and positioning reference signals (PRS)) were introduced in Rel-16, whether measurements other than intra-frequency SSB-based measurement can utilize the preconfigured gaps may be considered. Thus, further clarifications on such application scenarios for measurements based on PRS and CSI-RS is described. [0099] Accordingly, consideration of the applicable scenarios may depend on which types of reference signal to be measured within the preconfigured gap (e.g., SSB, multiple SSBs, CSI-RS, PRS). For example, in Rel-16, a UE may not be expected to process a downlink (DL) PRS without a measurement gap configuration. That is, the measurement gap for PRS may be persistently configured if PRS measurement is requested, independent of whether BWP switching is to occur.

[00100] FIG. 6 illustrates UE measurement behavior in accordance with some aspects. As shown in FIG. 6, the UE receives LTE positioning protocol (LPP) assistance data from an evolved Serving Mobile Location Center (E- SMLC). Based on the LPP data, the UE determines that inter-frequency Reference Signal Time Difference (RSTD) measurements are desired and that measurement gaps are either not configured or, if configured, the measurement gaps are not sufficient. The UE initiates the measurement procedure to obtain location data by transmitting an RRC InterFreqRSTDMeasurementlndication IE to the gNB. The gNB configured the measurement gap pattern for the UE and indicates the pattern in an RRCConnectionReconfiguration message, which the UE responds to with an RRCConnectionReconfigurationComplete message.

The E-SMLC then sends an LPP RequestLocation Information message to the UE to initiate the RSTD measurements using the measurement gap pattern provided by the gNB, and the UE performs inter-frequency (and perhaps intra- frequency) RSTD measurements. The UE then sends an LPP ProvideLocation Information message to the E-SMLC with the measurement data as well as an RRC InterFreqRSTDMeasurementlndication IE to the gNB to stop the RSTD measurement. The gNB subsequently restores the previous measurement gap pattern for the UE.

[00101] In some cases, the gap for the PRS measurement is configured at the same time as when the UE was requested to perform PRS measurements. In this case, consideration of the preconfigured gap by BWP switching for PRS measurement may be avoided.

[00102] For CSI-RS measurements, an intra-frequency CSI-RS measurement is defined (see, e.g., TS. 38.133 clause 9.10.2.1 and 9.10.2.2) provided that, per clause 9.10.2: the subcarrier spacing (SCS) of CSI-RS resources on the neighbor cell configured for measurement is the same as the SCS of CSI-RS resources on the serving cell indicated for measurement (60 KHz), the cyclic prefix (CP) type of CSI-RS resources on the neighbor cell configured for measurement is the same as the CP type of CSI-RS resources on the serving cell indicated for measurement, and the center frequency of CSI-RS resources on the neighbor cell configured for measurement is the same as the center frequency of CSI-RS resources on the serving cell indicated for measurement. The requirements in clause 9.10.2 apply, provided: all CSI-RS resources in the same measurement object (MO) are configured with the same csi-rs-MeasurementBW, the bandwidth of the CSI-RS on the intra-frequency neighbor cell is within the active BWP of the UE, the CSI-RS resources and the associated SSB of the cell being identified or measured are detectable, and the bandwidth of CSI-RS resources of intra-MO is the same as that of the CSI-RS resources configured for the serving cell.

[00103] In other words, when BWP switching occurs (e.g., the central frequency of the CSI-RS resource is changed), the CSI-RS measurement on the new active BWP/cells is an inter-frequency CSI-RS measurement in which a measurement gap is to be used. It is desirable from an efficiency standpoint for this measurement gap to be preconfigured to reduce the total measurement delay and signaling to request such a measurement gap.

[00104] In light of the above, the preconfigured gap can help to reduce measurement gap configuration delay for inter-frequency CSI-RS measurement. Therefore, in one embodiment, application scenarios for a preconfigured gap include Scenario 1: intra-frequency SSB-based measurement after BWP switching and Scenario 2: inter-frequency CSI-RS measurement after BWP switching.

[00105] As interpreted for the above embodiment, if multiple measurements with a preconfigured measurement gap are desired, the total preconfigured measurement gaps may be larger than one. To minimize the system overhead because there is no scheduling within a measurement gap however, the serving gNB can activate only the part of preconfigured measurement gaps associated with particular measurements when measurements are to be taken after the BWP switching. For example, if there are no CSI-RS signals available during bwp-InactivityTimer after BWP switching, only preconfigured measurement GAP#1 (which the UE uses to measure the SSB - see FIG. 4) can be activated rather than all of the preconfigured measurement gaps being activated. bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, mslO, ms20, ms30, ms40, ms50, ms60, ms80, mslOO, ms200, ms300, ms500, ms750, msl280, msl920, ms2560, sparelO, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, sparel }

OPTIONAL, —Need R

[00106] In some embodiments, there may be no restrictions on the total number of preconfigured measurement gaps. In this case, at least two measurement gap patterns may be preconfigured if both an intra-frequency SSB measurement and inter-frequency CSI-RS measurement can be performed with the preconfigured measurement gaps. In some embodiments, a limited number (rather than all) of the preconfigured measurement gaps may be activated by the serving gNB as concurrent measurement gaps.

[00107] In some embodiments, there may be multiple concurrent measurement gap patterns that are activated after UE BWP switching (e.g., both SSB and CSI-RS). In this case, the measurement gap patterns used for the UE can be autonomously selected by both the UE and the serving gNB depending on known measurement configurations (e.g., SMTC for SSB-based measurement) as shown below.

MeasObj ectNR : := SEQUENCE { ssbFrequency ARFCN-ValueNR

OPTIONAL, - Cond SSBorAssociatedSSB ssbSubcarrierSpacing SubcarrierSpacing

OPTIONAL, - Cond SSBorAssociatedSSB smtcl SSB-MTC

OPTIONAL, - Cond SSBorAssociatedSSB smtc2 SSB-MTC2 OPTIONAL, — Cond IntraFreqConnected refFreqCSI-RS ARFCN-ValueNR

OPTIONAL, - Cond CSI-RS referenceSignalConfig ReferenceSignalConfig,

OPTIONAL, — Need R absThreshCSI-RS-Consolidation ThresholdNR

OPTIONAL, — Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, — Need R nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS- ResourcesTo Average)

OPTIONAL, — Need R quantityConfiglndex INTEGER (1.maxNrofQuantityConfig), offsetMO Q-OffsetRangeList, cellsToRemoveList PCI-List OPTIONAL, — Need N cell sTo AddModLi st Cell sTo AddModLi st OPTIONAL, — Need N blackCellsToRemoveList PCI-RangelndexLi st OPTIONAL, — Need N blackCellsToAddModList SEQUENCE (SIZE (L.maxNrofPCI- Ranges)) OF PCI-RangeElement OPTIONAL, — Need N whiteCellsToRemoveLi st PCI-RangelndexLi st

OPTIONAL, — Need N whiteCellsTo AddModLi st SEQUENCE (SIZE (1..maxNrofPCI-

Ranges)) OF PCI-RangeElement OPTIONAL, — Need N

[[ freqB andlndi catorNR F reqB andlndi catorNR

OPTIONAL, — Need R measCycleSCell ENUMERATED (sfl60, sf256, sf320, sf512, sf640, sfl024, sfl280} OPTIONAL - Need R

]],

[[ smtc31ist-rl6 SSB-MTC3List-rl6

OPTIONAL, — Need R rmtc-Config-rl6 SetupRelease {RMTC-Config-rl6}

OPTIONAL, — Need M t312-rl6 SetupRelease { T312-rl6 }

OPTIONAL - Need M

]]

}

[00108] Cited portions of TS 38.133

• 8.2.1.2.7 Interruptions due to Active BWP switching Requirement

The requirements for DCI-based BWP switch, timer-based BWP switch or UL BWP switch triggered by consistent uplink CCA failures in this clause apply to the case that the BWP switch is performed on a single CC or multiple CCs.

When either of the DCI-based, timer-based or RRC -based downlink BWP switch and/or uplink BWP switch occur on multiple CCs simultaneously or over partially overlapping period, the interruption requirements described in this clause apply for each BWP switch.

When UE receives a DCI indicating UE to switch its active BWP involving changes in any of the parameters listed in Table 8.2.1.2.7-2, the UE is allowed to cause interruption of up to X slot to other active serving cells if the UE is not capable of per-FR gap, or if the BWP switching involves SCS changing. When the BWP switch imposes changes in any of the parameters listed in Table

8.2.1.2.7-2 and the UE is capable of per-FR gap, the UE is allowed to cause interruption of up to X slot to other active serving cells in the same frequency range wherein the EE is performing BWP switching. X is defined in Table

8.2.1.2.7-1. The starting time of interruption is only allowed within the BWP switching delay TewPswitchDeiay as defined in clause 8.6.2 when BWP switch occurs on a single CC. The starting time of interruption caused by each BWP switch is only allowed within the BWP switch delay TMuitipieBWPswitchDeiay +Y as defined in clause 8.6.2A.1 when BWP switch occurs on multiple CCs. Interruptions are not allowed during BWP switch involving any other parameter change.

When a BWP timer bwp-InactivityTimer defined in TS 38.331 [2] expires, UE is allowed to cause interruption of up to X slot to other active serving cells due to switching its active BWP involving changes in any of the parameters listed in Table 8.2.1.2.7-2 if the UE is not capable of per-FR gap, or if the BWP switching involves SCS changing. When the BWP switch imposes changes in any of the parameters listed in Table 8.2.1.2.7-2 and the UE is capable of per-FR gap, the UE is allowed to cause interruption of up to X slot to other active serving cells in the same frequency range wherein the UE is performing BWP switching. X is defined in Table 8.2.1.2.7-1. The starting time of interruption is only allowed within the BWP switching delay TewPswitchDeiay as defined in clause 8.6.2 when BWP switch occurs on a single CC. The starting time of interruption caused by each BWP switch is only allowed within the BWP switch delay TMuitipieBWPswitchDeiay as defined in clause 8.6.2B.1 when BWP switch occurs on multiple CCs simultaneously or TMuitipieBWPswitchDeiay Total as defined in clause 8.6.2B.2 when BWP switch occurs on multiple CCs over partially overlapping time period. Interruptions are not allowed during BWP switch involving any other parameter change.

When UE receives an RRC reconfiguration that only requests UE to switch its active BWP on one single CC, the UE is allowed to cause interruption of up to X slot to other active serving cells due to switching its active BWP involving changes in any of the parameters listed in Table 8.2.1.2.7-2 if the UE is not capable of per-FR gap, or if the BWP switching involves SCS changing. When the BWP switch imposes changes in any of the parameters listed in Table 8.2.1.2.7-2 and the UE is capable of per-FR gap, the UE is allowed to cause interruption of up to X slot to other active serving cells in the same frequency range wherein the EE is performing BWP switching. X is defined in Table 8.2.1.2.7-1. The interruption is only allowed within the delay

TRRCprocessingDeiay TBWPswitchDeiayRRC defined in clause 8.6.3 when BWP switch occurs on a single CC. The interruption is only allowed within the delay

TRRCprocessingDeiay + TBWPswitchDeiayRRC + DRRC*(N-1) as defined in clause 8.6 3 A when BWP switch occurs on multiple CCs. When EE BWP switch is triggered by consistent uplink CCA failures [7], the EE is allowed to cause interruption of up to X slot to other active serving cells due to switching its active EE BWP involving changes in any of the parameters listed in Table 8.2.1.2.7-2 if the EE is not capable of per-FR gap, or if the EE BWP switching involves SCS changing. When the EE BWP switch imposes changes in any of the parameters listed in Table 8.2.1.2.7-2 and the EE is capable of per-FR gap, the EE is allowed to cause interruption of up to X slot to other active serving cells in the same frequency range wherein the EE is performing EE BWP switching. X is defined in Table 8.2.1.2.7-1. The starting time of interruption is only allowed within the EE BWP switching delay TBWPswitchDeiay as defined in clause 8.6.2. Interruptions are not allowed during UL BWP switch involving other parameter change.

Table 8.2.1.2.7-1: interruption length X

Table 8.2.1.2.7-2: Parameters which cause interruption other than SCS • 9.2.1 Introduction

A measurement is defined as a S SB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs are also the same.

The UE shall be able to identify new intra-frequency cells and perform SS- RSRP, SS-RSRQ, and SS-SINR measurements of identified intra-frequency cells if carrier frequency information is provided by PCell or the PSCell, even if no explicit neighbour list with physical layer cell identities is provided.

The UE can perform intra-frequency SSB based measurements without measurement gaps if

- the UE indicates ‘no-gap’ via intraFreq-needForGap for intra-frequency measurement, or

- the SSB is completely contained in the active BWP of the UE, or

- the active downlink BWP is initial BWP[3]

For intra-frequency SSB based measurements without measurement gaps, UE may cause scheduling restriction as specified in clause 9.2.5.3.

SSB based measurements are configured along with one or two measurement timing configuration(s) (SMTC(s)) which provides periodicity, duration and offset information on a window of up to 5ms where the measurements are to be performed. For intra-frequency connected mode measurements, up to two measurement window periodicities may be configured. A single measurement window offset and measurement duration are configured per intra-frequency measurement object.

When measurement gaps are needed, the UE is not expected to detect SSB which start earlier than the gap starting time + switching time, nor detect SSB which end later than the gap end - switching time. Switching time is 0.5ms for frequency range FR1 and 0.25ms for frequency range FR2.

The requirements in this clause shall also apply, when the UE is configured to perform SRS carrier based switching and using measurement gaps. The measurement requirements defined for an activated SCell with a non- dormant active BWP defined in this clause shall also apply to an activated SCell with dormant BWP as active BWP.

• 9.2.6 Intra-frequency measurements with measurement gaps

• 9.2.6.1 Void

• 9.2.6.2 Intra-frequency cell identification

The UE shall be able to identify a new detectable intra frequency cell within T _{identify intra without index} if UE is not indicated to report SSB based RRM measurement result with the associated SSB index (reportQuantityRsIndexes or maxNrqfRSI ndexes Ί o Re port is not configured), or the UE has been indicated that the neighbour cell is synchronous with the serving cell ( deriveSSB - IndexFromCell is enabled). Otherwise UE shall be able to identify a new detectable intra frequency cell within Tidentifyjntra_with index. The UE shall be able to identify a new detectable intra frequency SS block of an already detected cell within Tidentifyjntra_withoutjndex. It is assumed that deriveSSB-IndexFromCell is always enabled for FR1 TDD and FR2.

T _{identify_intra_without_index} TSS/SSS_sync_intra + T SSB measuremenfyperiod intra ms

T _{identify_intra_without_i} ⁼ _nd T _ex pSS/SSS_sync_ntra + T SSB measuremenfyperiod intra + TsSB time index intra ms

Where:

Tpss/sss syncjntra: it is the time period used in PSS/SSS detection given in table 9.2.6.2-1 or 9.2.6.2-2.

TSSB timejndexjntra: it is the time period used to acquire the index of the SSB being measured given in table 9.2.6.2-3.

T ssB measuremenfyperiod intra: equal to a measurement period of SSB based measurement given in table 9.2.6.3-1 or 9.2.6.3-2.

CSSFintra: it is a carrier specific scaling factor and is determined according to C S SF within gap, i in clause 9. 1.5.2 for measurement conducted within measurement gaps. M _P ss/sss_sync_with gaps : For a UE supporting FR2 power class 1 or 5,

Mpss/sss sync with gaps=40. For a UE supporting FR2 power class 2, Mpss/sss _sync with gaps =24. For a UE supporting FR2 power class 3, Mpss/sss sync with _gaps =24. For a UE supporting power class 4, M _pss /sss_sync with gaps =24 Mmeas_period_ with gaps: For a UE Supporting power class 1 or 5, Mmeas_period_ with gaps =40. For a UE supporting power class 2, Mmcas pc nod with gaps =24. For a UE supporting power class 3, Mmeas_period_ with gaps =24. For a UE supporting power class 4, Mmeas _j eriod with gaps =24.

If the higher layer signaling in TS 38.331 [2] of smtc2 is present and smtcl is fully overlapping with measurement gaps and smtc2 is partially overlapping with measurement gaps, requirements are not specified for Tidentifyjntra_withoutjndex or

T _{identify_intra_without_} . _index

If MCG DRX is in use, cell identification requirements for intra-frequency measurement in MCG specified in Table 9.2.6.2-1, Table 9.2.6.2-2, and Table 9.2.6.2-3 shall depend on the MCG DRX cycle. If SCG DRX is in use, cell identification requirements for intra-frequency measurement in SCG specified in Table 9.2.6.2-1, Table 9.2.6.2-2, and Table 9.2.6.2-3 shall depend on the SCG DRX cycle. Otherwise, the requirements for when DRX is not in use shall apply.

Table 9.2.6.2-1: Time period for PSS/SSS detection (FR1)

Table 9.2.6.2-3: Time period for time index detection (Frequency range

FR1)

• 9.2.6.3 Intrafrequency Measurement Period

The measurement period for FR1 intrafrequency measurements with gaps is as shown in table 9.2.6.3-1.

The measurement period for FR2 intrafrequency measurements with gaps is as shown in table 9.2.6.3-2.

When MghSpeedMeasFlag-rl6 is configured, T SSB measurement penod mtra is specified in Table 9.2.6.3-3.

If MCG DRX is in use, measurement period requirements for intra-frequency measurement in MCG specified in Table 9.2.6.3-1 and Table 9.2.6.3-2, shall depend on the MCG DRX cycle. If SCG DRX is in use, measurement period requirements for intra-frequency measurement in SCG specified in Table 9.2.6.3-land Table 9.2.6.3-2, shall depend on the SCGDRX cycle. Otherwise, the requirements for when DRX is not in use shall apply.

For either an FR1 or FR2 serving cell, longer measurement period would be expected during the period Tidentify_CGi when the UE is requested to decode an NR CGI.

Table 9.2.6.3-1: Measurement period for intra-frequency measurements with gaps(FRl)

Table 9.2.6.3-2: Measurement period for intra-frequency measurements with gaps(FR2)

Table 9.2.6.3-3: Measurement period When highSpeedMeasFlag-rl6 is configured (Frequency Range FR1)

• 9.10.2 CSI-RS based intra-frequency measurements · 9.10.2.1 Introduction

A measurement is defined as a CSI-RS based intra-frequency measurement provided that:

- the SCS of the CSI-RS resource of the neighbour cell configured for measurement is the same as the SCS of the CSI-RS resource on the serving cell indicated for measurement, and

- the CP type of the CSI-RS resource of neighbour cell configured for measurement is the same as the CP type of the CSI-RS resource of the serving cell indicated for measurement, and

- It is applied for SCS = 60KHz - the centre frequency of the CSI-RS resource of the neighbour cell configured for measurement is the same as the centre frequency of the CSI-RS resource of the serving cell indicated for measurement The UE shall be able to identify new intra-frequency cells and perform CSI- RSRP, CSI-RSRQ and CSI-SINR measurements of identified intra-frequency cells if carrier frequency information is provided by PCell or the PSCell.

No measurement gap is needed for intra-frequency CSI-RS resources measurements.

For intra-frequency CSI-RS based measurements, UE may cause scheduling restriction as specified in clause 9.10.2.6.

Note: Extended CP for CSI-RS based measurement is not supported in this release.

• 9.10.2.2 Requirements applicability

The measurement of the associated SSB follows the same requirements as SSB based measurements defined in 9.2.

The requirements in clause 9.10.2 apply, provided:

- Only one intra-frequency CSI-RS layer per serving cell is configured, and

- The BW of the CSI-RS on the intra-frequency neighbor cell is within the active BWP of the UE, and

- The associated SSB of the CSI-RS resources being identified or measured are detectable, and the CSI-RS resources configured for CSI-RS based L3 measurements are measurable, and

- The bandwidth of CSI-RS resources of intra-MO is the same as that of the CSI-RS resources configured for the serving cell, and

- All CSI-RS resources on one intra-frequency layer are configured within up to two separate windows where each window is up to 5ms, and

- for the case of single window further provided

- The periodicity of the configured CSI-RS resources is 10ms, 20ms or 40ms- for the case of two separate windows further provided

- The two windows are either both fully non-overlapped with MG or both partially overlapped with MG

- The periodicity of the configured CSI-RS resources is 20ms or 40ms, and The gap between two 5ms windows is half of the CSI-RS periodicity.

- The starting point of the first window is the slot boundary of the serving cell, where the corresponding slot contains the configured L3 CSI-RS resource of the serving cell in the servingCellMO with the smallest offset, and

- The starting point of the second window is determined by an offset of half of the CSI-RS periodicity in slots with regards to the starting point of the first 5ms window, and

- Numerology for intra-frequency CSI-RS and data of serving cell are the same.

An intra-frequency cell shall be considered detectable when for each relevant associated SSB:

- SS-RSRP related side conditions given in clauses 10.1.2.1 and 10.1.3.1 for FR1 and FR2, respectively, for a corresponding Band,

- SS-RSRQ related side conditions given in clauses 10.1.7.1 and 10.1.8.1 for FR1 and FR2, respectively, for a corresponding Band,

- SS-SINR related side conditions given in clauses 10.1.12.1 and 10.1.13.1 for FR1 and FR2, respectively, for a corresponding Band,

- SSB RP and SSB Es/Iot according to Annex B.2.2 for a corresponding Band.

A CSI-RS resource shall be considered measurable when for each relevant CSI- RS resource:

- CSI-RSRP related side conditions given in clauses 10.1.2.3 and 10.1.3.3 for FR1 and FR2, respectively, for a corresponding Band,

- CSI-RSRQ related side conditions given in clauses 10.1.7.2 and 10.1.8.2 for FR1 and FR2, respectively, for a corresponding Band,

- CSI-SINR related side conditions given in clauses 10.1.12.2 and 10.1.13.2 for FR1 and FR2, respectively, for a corresponding Band, - CSI RP and CSI-RS Es/Iot according to Annex B.2.12 for a corresponding

Band.

• 9.10.3 CSI-RS based Inter-frequency measurements · 9.10.3.1 Introduction

A measurement is defined as a CSI-RS based inter-frequency measurement provided it is not defined as an intra-frequency measurement according to clause 9.10.2.

If a UE is configured with the higher layer parameter CSI-RS-Resource-Mobility and the higher layer parameter associatedSSB is configured, the UE shall be able to identify inter-frequency cells indicated for measurement and perform CSI- RSRP, CSI-RSRQ, and CSI-SINR measurements of identified inter-frequency cells.

When measurement gaps are needed, the UE is not expected to detect the associated SSB nor perform measurement of the CSI-RS resource configured in CSI-RS-Resource-Mobility on an inter-frequency measurement object which start earlier than the gap starting time + switching time, and ends later than the gap end - switching time. When the inter-frequency cells are in FR2 and the per-FR gap is configured to the UE in EN-DC, SA NR, NE-DC and NR-DC, or the serving cells are in FR2, the inter-frequency cells are in FR2 and the per-UE gap is configured to the UE in SA NR and NR-DC, the switching time is 0.25ms. Otherwise the switching time is 0.5ms.

• 9.10.3.2 Requirements applicability

The associated SSB layer of the CSI-RS follows the same requirements as SSB based measurements defined in 9.3.

The requirements in clause 9.10.3 apply, provided:

- The associated SSB of the cell being identified or measured is detectable, and

- All CSI-RS resources on one inter-frequency layer are configured within a window of up to 5ms, and

- The periodicity of the configured CSI-RS resources is 10ms, 20ms or 40ms, and CSI-RS resources for measurements and the associated SSB for cell identification are configured within measurement gap.

An inter-frequency cell shall be considered detectable when for each relevant associated SSB: - SS-RSRP related side conditions given in clauses 10.1.4.1 and 10.1.5.1 for

FR1 and FR2, respectively, for a corresponding Band,

- SS-RSRQ related side conditions given in clauses 10.1.9.1 and 10.1.10.1 for FR1 and FR2, respectively, for a corresponding Band,

- SS-SINR related side conditions given in clauses 10.1.14.1 and 10.1.15.1 for FR1 and FR2, respectively, for a corresponding Band,

- SSB RP and SSB Es/Iot according to Annex B.2.3 for a corresponding Band.

A CSI-RS resource shall be considered measurable when for each relevant CSI- RS resource: - CSI-RSRP related side conditions given in clauses 10.1.4.3 and 10.1.5.3 for FR1 and FR2, respectively, for a corresponding Band,

- CSI-RSRQ related side conditions given in clauses 10.1.9.2 and 10.1.10.2 for FR1 and FR2, respectively, for a corresponding Band,

- CSI-SINR related side conditions given in clauses 10.1.14.2 and 10.1.15.2 for FR1 and FR2, respectively, for a corresponding Band,

- CSI _RP and CSI-RS Es/Iot according to Annex B.2.13 for a corresponding Band.

• 9.10.3.3 Number of cells and number of CSI-RS resources

• 9.10.3.3.1 Requirements for FR1 For each inter-frequency CSI-RS layer, during each layer 1 measurement period, the UE shall be capable of performing CSI-RSRP, CSI-RSRQ, and CSI-SINR measurements for at least:

- 14 CSI-RS s with different CSI-RS index and/or PCI , and - The cells to be monitored based on CSI-RS are the same set or a subset of the cells monitored based on the layer of the associated SSB.

• 9.10.3.3.2 Requirements for FR2

For each inter-frequency CSI-RS layer, during each layer 1 measurement period, the UE shall be capable of performing CSI-RSRP, CSI-RSRQ, and CSI-SINR measurements for at least:

- 24 CSI-RS s with different CSI-RS index and/or PCI, and

- The cells to be monitored based on CSI-RS are the same set or a subset of the cells monitored based on the layer the associated SSB.

• 9.10.3.4 Measurements reporting requirements

• 9.10.3.4.1 Periodic Reporting

Reported CSI-RSRP, CSI-RSRQ, and CSI-SINR measurements contained in periodically triggered measurement reports shall meet the requirements in clauses 10.1.4.2, 10.1.5.2, 10.1.9.2, 10.1.10.2, 10.1.14.2 and 10.1.15.2..

• 9.10.3.4.2 Event-triggered Periodic Reporting

Reported CSI-RSRP, CSI-RSRQ, and CSI-SINR measurements contained in periodically triggered measurement reports shall meet the requirements in clauses 10.1.4.2, 10.1.5.2, 10.1.9.2, 10.1.10.2, 10.1.14.2 and 10.1.15.2..

The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause 9.10.3.4.3.

• 9.10.3.4.3 Event-triggered Reporting

Reported CSI-RSRP, CSI-RSRQ, and CSI-SINR measurements contained in periodically triggered measurement reports shall meet the requirements in clauses 10.1.4.2, 10.1.5.2, 10.1.9.2, 10.1.10.2, 10.1.14.2 and 10.1.15.2..

The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.

The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement report.

The event triggered measurement reporting delay, measured without L3 filtering shall be within CSI-RS based measurement defined in clause . When L3 filtering is used an additional delay can be expected.

• 9.10.3.5 Inter frequency measurements with measurement gaps

When measurement gaps are provided, if configured with the higher layer parameters CSI-RS-Resource-Mobility and associatedSSB, the UE shall be able to identify a new detectable CSI-RS based inter frequency cell within T csi-

RS identify inter,

T CSI-RS_identify inter ⁼ (TpSS/SSS sync + T CSI-RS measurement_period inter + TcSI-RS_SFN_inter) ms

Where:

Tpss/sss_sync is the time period used in PSS/SSS detection which is determined according to Tpss/sss_sync_mter in clause 9.3.4,

TCSI-RS_SFN_inter is the time period used to acquire the SFN information of the cell being measured, which is shown in Table 9.10.3.5-3 for FR1 and equals inter-frequency TSSB time index inter in Clause 9.3.4 for FR2,

Tcsi-RS_measurement_period_inter: equal to a measurement period of CSI-RS based measurement given in table 9.10.3.5-1 and table 9.10.3.5-2..

Mmeas _j eriodjnter: For a UE supporting FR2 power class 1 or 5,

Mmeas_period_inter =8xN samples. For a UE supporting FR2 power class 2, Mmeas_periodjnter=5xN samples. For a UE supporting FR2 power class 3, Mmeas_period_inter =5xN samples. For a UE supporting FR2 power class 4, Mmeas_period_inter = 5xN samples. Note that scaling factor N = [8]

CSSFinter: it is a carrier specific scaling factor and is determined according to CSSF _W ithm_gap,i in clause 9.1.5 for measurement conducted within measurement gaps.

Additionally, for a given CSI-RS resource, if the associated SSB is configured but not detected by the UE, or if CSI-RS configured with associated SSB but not QCL-ed to the associated SSB, the UE is not required to monitor the corresponding CSI-RS resource. Table 9.10.3.5-1: Measurement period for CSI-RS based inter-frequency measurements with gaps (Frequency FR1)

Table 9.10.3.5-2: Measurement period for CSI-RS based inter-frequency measurements with gaps (Frequency FR2)

Table 9.10.3.5-3: Time period for SFN acuisition for interfrequency CSI-RS based measurements with gaps(Frequency FR1)

[00109] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00110] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00111] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00112] The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, 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. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.