EP4275384A1 - Ue configurable to support multiple measurement gaps - Google Patents

Abstract

A generation node B (gNB) encodes an RRC reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a single measurement gap (MG) configuration. The MG configuration may indicate two or more independent MG patterns that are to be concurrently activated for the UE. The UE may encode one or more measurement report messages that include measurements performed on reference signals in accordance with the two or more independent MG patterns.

Description

UE CONFIGURABLE TO SUPPORT^' MULTIPLE MEASUREMENT GAPS

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional

Patent Application Serial No. 63/135,429, filed January 8, 2021 [reference number AD4517-Z] which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) and fifth -generation (5G) networks including 5G new- radio

(NR) (or 5G-NR) networks. Some embodiments pertain to configuring User Equipment with multiple measurement gap (MG) patterns.

BACKGROUND

[0003] The time duration during which a user equipment (LJE) suspends it communication with its serving cell to perform certain measures is known as a Measurement Gap (MeasGap), One issue with a conventional measurement gap pattern is that it may be insufficient for performing certain measurements required to be performed by a UE.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.

[0005] FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments. [0006] FIG. 2 illustrates the use of one or more measurement gap paterns in accordance with some embodiments.

[0007] FIG. 3 illustrates a functional block diagram of a wireless communication device in accordance with some embodiments. [0008] FIG. 4 is a flow chart of a procedure performed by a generation

Node B igNB) for configuring UE with two or more independent MG patterns in accordance with some embodiments.

[0009] 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.

[0010] In NR R15/R16, only one MG pattern can be configured per-UE or per-FR (subject to capability). Lack of support for more than one MG patern per measurement, period creates undesired inflexibility in scheduling on the network (NW) side as well as prolonged measurement delay on the LIE side. For typical intra-frequency and inter-frequency neighbor cell measurements, the NW has to ensure that the synchronization signal block (SSB) based radio-resource management (RRM) measurement timing configuration (SMTC) corresponding to all configured measurement objects fall within the same measurement gap. Moreover, UE will have to share the same measurement gap pattern for all measurements resulting in longer measurement delays. Moreover, with additional features and enhancements in NR requiring gap-based measurements, even more measurements will compete for the same measurement gap pattern. Often, the features needing gap-based measurements have different and even contradicting requirements (e.g., low latency positioning requirements necessitating the need for shorter measurement delays vs. legacy measurements for mobility or low duty cycle inter-RAT measurements). Furthermore, the reference signal used by UE for measurements are typically of different nature and periodicity (e.g., CSl-RS, SSB, PRS,...) which makes it difficult for NW to align them in time so they can he shared with the same gap patern. To address diverse measurement requirements using same or different reference signals, both NW and LIE can significantly benefit from multiple (or at least two) independent MG patterns.

[0011] Embodiments disclosed herein are directed to configurating user equipment with two or more independent MG patterns. Some embodiments are directed to a generation node B (gNB). In these embodiments, the gNB may encode an RRC reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a single measurement gap (MG) configuration. The MG configuration may indicate two or more independent MG patterns that are to be concurrently activated for the UE. In these embodiments, the gNB may decode one or more measurement report messages from the UE. The one or more measurement report messages may include measurements from the UE performed in accordance with the two or more independent MG patterns. These embodiments, as well as others, are described in more detail below.

[0012] In some of these embodiments, a single MG configuration indicated by a MeasGapConfig IE may be used to configure a UE with multiple gaps and/or multiple gap patterns. In some embodiments, a single MG configuration indicated by a MeasGapConfig IE may configure aUE with multiple gaps and/or multiple gap patterns for the same frequency range (e.g., FR1 or FR2), although the scope of the embodiments is not limited in this respect. In other embodiments, a single MG configuration indicated by a MeasGapConfig IE may configure a UE with multiple gaps and/or multiple gap patterns for different frequency ranges.

[0013] In some embodiments, a single MG configuration indicated by a

MeasGapConfig IE may configure a UE with multiple gaps and/or multiple gap patterns for a same measurement time, while in other embodiments, a single MG configuration indicated by a MeasGapConfig IE may configure aUE with multiple gaps and/or multiple gap patterns for different measurement types. Examples of measurement types may include Sync Signal/PBCH block (SSB) signals, channel -state information reference signals (CSI-RS) and positioning reference signals (PRS).

[0014] In some other embodiments, two or more MG configurations may be indicated by a MeasGapCoiifig IE, each MG configurations may configure a UE with one or more independent MG patterns (e.g., multiple gaps and/or multiple gap patterns).

[0015] In some embodiments, the gNB may encode the MeasGapConfig

IE to include the two or more independent MG patterns as a list (e.g., multi GapConfigList).

[0016] In some embodiments, the gNB may encode the MeasGapConfig

IE to indicate a reference signal type (rsType) for each of the two or more independent MG patterns indicated in the MeasGapConfig IE. In these embodiments, each indicated reference signal type may comprise one of Sync Signai/PBCH block (SSB) signals, channel -state information reference signals (CSI-RS) and positioning reference signals (PRS). In these embodiments, the purpose (i.e., which signal is to measured) of each of the configured independent MG patterns may be indicated in the MeasGapConfig IE.

[0017] In some embodiments, the gNB may encode the MeasGapConfig

IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, one or more MG configuration parameters. The MG configuration parameters may include: a gap offset (gapOffset), a measurement gap length (MGL), a measurement gap repetition period (MGRP), and a measurement gap timing advance (MGTA).

[0018] In some embodiments, the gNB may further encode the

MeasGapConfig IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, a reference sendee cell indicator (refServCelllndicator).

[0019] In some embodiments, the gNB may further encode the

MeasGapConfig IE to include a gap disable flag (gapDisable) field for each of the two or more independent MG patterns. In these embodiments, the gap disable flag, when set, may configure the UE to disable a corresponding one of the independent MG patterns. [0020] In some embodiments, the gNB may further encode the

MeasGapConfig IE to include a gap disable bandwidth part (BWP) identifier (ID) (gapDisableBWPid) field for each of the two or more independent MG patterns. In these embodiments, the MeasGapConfig IE may configure the UE to disable (e.g,, deactivate) a corresponding one of the independent MG patterns for a currently active BWP when the currently active BWP is identified by the disable BWP ID field. These embodiments may allow for an autonomous enable or disable of a measurement gap configuration based on a BWP. In these embodiments, one of the independent MG patterns for the currently active BWP may be disabled when the currently active BWP is identified by the disable BWP ID field. When the currently active BWP is not identified by the disable BWP ID field, the independent MG pattern for the currently active BWP is not disabled. [0021] In some embodiments, the gNB may decode a capabilities information message from the UE. The capabilities information message may indicate whether or not the UE is capable of supporting the two or more independent MG patterns. In these embodiments, when the UE has indicated a capability to support the two or more independent MG patterns, the gNB may encode the RRC reconfiguration message to include the MeasGapConfig IE to configure the UE with a single MG configuration comprising the two or more independent MG patterns. In these embodiments, when the UE has not indicated a capability to support multiple concurrent independent MG patterns or has indicated that it does not have the capability to support multiple concurrent independent MG patterns, the gNB may encode the RRC reconfiguration message to include the MeasGapConfig IE to configure the UE with the single MG configuration comprising only one MG pattern.

[0022] In some embodiments, when the UE is configured with the two or more independent MG patterns, a first of the two or more independent MG patterns may configure the UE for measurement of a first type of reference signal (e.g., radio-resource management (RRM)) and a second of the two or more independent MG patterns may configure the UE for measurement of a second type of reference signal (e.g., positioning reference signal (PRS) or channel state information reference signals (CSI-RS)). In some embodiments, when the UE is configured with the twO or more independent MG patterns, a first of the two or more independent MG patterns may configure the UE for radio-resource management (RKM) and a second of the two or more independent MG patterns may configure the LIE for measurement of positioning reference signal (PRS). In some embodiments, a third independent MG patterns may be used by the UE for C8I-RS measurements. In these embodiments, when the UE is configured with only one MG pattern, the one MG pattern is configured to the LIE for both the RRM and for measurement of the PRS signals.

[0023] Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a generation node B (gNB). In these embodiments, the processing circuitry' may encode an RRC reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a measurement gap (MG) configuration. In these embodiments, the processing circuitry may also decode one or more measurement report messages from the UE that include measurements from the LIE performed in accordance with the two or more independent MG patterns. [0024] Some embodiments are directed to a user equipment (UE). In these embodiments, the UE may decode an RRC reconfiguration message received from a generation node B (gNB) that includes a measurement gap configuration information element (MeasGapConfig IE) to configure the UE with a measurement gap (MG) configuration. In these embodiments, the MG configuration may comprise two or more independent MG patterns that are to be concurrently activated for the UE. The UE may also encode one or more measurement report messages for transmission to the gNB that include measurements from the UE performed in accordance with the two or more independent MG patterns. These embodiments are described in more detail below.

[0025 [ FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 140A 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 Personal Data Assistants (PDAs), pagers, laptop computers, 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 LIE 101, and LIE 101 can be used to perform one or more of the techniques disclosed herein.

[0026] 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.

[0027] LTE and LIE -Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE- Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0028] Embodiments described herein can be used in the context of any spectami 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 further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

[0029] Embodiments described herein can also be applied to different

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

[0030] In some embodiments, any of the UEs 101 and 102 can comprise an Intern et-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived LIE connections. In some embodiments, any of the UEs 101 and 102 can include a narrowhand (NB) loT UE (e.g., such as an enhanced NB-

IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT LIE 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 embodiments, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0031] 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), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of winch 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- Taik (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0032] 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 side!ink 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), and a Physical Sidelink Broadcast Channel (PSBCH). [0033] 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).

[0034] 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 embodiments, 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 I l l, and one or more RAN nodes for providing femtocells or picocells (e.g., ceils having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low pow^?er (LP) RAN node 112. [0035] 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 embodiments, 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 new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

[0036] The RAN 110 is shown to he communicatively coupled to a core network (CN) 120 via an SI interface 113. In embodiments, 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 SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and

MMEs 121.

[0037] 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 embodiments 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.

[0038] 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.

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

The P-GW 123 may route data packets between the EPC network 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 sewer 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LIE 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 sendees (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,

[0040] 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 C N 120. In a non-roaming scenario, in some embodiments, 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.

[0041] In some embodiments, the communication network 140A can be an IoT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT).

[0042] An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 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 embodiments, 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.

[0043] In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, 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 embodiments, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[00441 FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring to FIG. IB, there is illustrated a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities. The 5G system architecture 14013 includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146. The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator sendees, Internet access, or third-party sendees. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policy. The UPF 134 can be deployed in one or more configurations according to the desired sendee type. 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).

[0045] In some embodiments, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 16813 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) 16413, 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 embodiments 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 sendee area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator,

[0046] In some embodiments, 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.

[0047] 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), 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 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.

[0048] FIG. IC 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 embodiments, 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.

[0049] In some embodiments, 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 theNEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the IJDM 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 AU8F 144), Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0050] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1 A-1C can be configured to perform the functionalities described herein.

[0051] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next, generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications, NR is expected to be a unified network/system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different, services and applications. In general, NR will evolve based on 3 GPP LTE- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services.

[0052] ReI-15 NR systems are designed to operate on the licensed spectrum. The NR-unlicensed (NR-U), a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

[0053] FIG. 2 illustrates the use of one or more measurement gap patterns in accordance with some embodiments.

[0054] FIG. 3 illustrates a functional block diagram of a wireless communication device in accordance with some embodiments. Wireless communication device 300 may be suitable for use as a UE or gNB configured for operation in a 5G NR network. The communication device 300 may include communications circuitry 302 and a transceiver 310 for transmiting and receiving signals to and from other communication devices using one or more antennas 301. The communications circuitry 302 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmiting and receiving signals. The communication device 300 may also include processing circuitry 306 and memory 308 arranged to perform the operations described herein. In some embodiments, the communications circuitry 302 and the processing circuitry 306 may be configured to perform operations detailed in the above figures, diagrams, and flows.

[0055] In accordance with some embodiments, the communications circuitry' 302 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 302 may be arranged to transmit and receive signals. The communications circuitry_'’ 302 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry? 306 of the communication device 300 may include one or more processors. In other embodiments, two or more antennas 301 may be coupled to the communications circuitry 302 arranged for sending and receiving signals. The memory 308 may store information for configuring the processing circuitry¹ 306 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 308 may include any type of memory, including non -transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 308 may include a computer-readable storage device, read-only memory_' (ROM), random- access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

[0056] In some embodiments, the communication device 300 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[0057] In some embodiments, the communication device 300 may include one or more antennas 301. The antennas 301 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characters sties that may result between each of the antennas and the antennas of a transmitting device.

[0058] In some embodiments, the communication device 300 may include one or more of a keyboard, a display, a non-volatile memory' port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0059] Although the communication device 300 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication device 300 may refer to one or more processes operating on one or more processing elements.

[0060] FIG. 4 is a flow chart of a procedure 400 performed by a generation Node B (gNB) for configuring UE with two or more independent MG patterns in accordance with some embodiments. Operation 402 comprises encoding an RRC reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a single measurement gap (MG) configuration. The MG configuration comprises two or more independent MG patterns that are to be concurrently activated for the UE. Operation 404 comprises decoding one or more measurement report, messages from the UE. The one or more measurement report messages may include measurements from the UE that are performed by the UE in accordance with the two or more independent MG patterns.

[0061] Embodiments herein provide techniques to configure multiple measurement gaps.

MeasGapConfig

[0062] The IE MeasGapConfig specifies the measurement gap configuration and controls setup/release of measurement gaps.

[0063] MeasGapConfig information element

- ASNl START

- TAG-MEASGAPCONFIG-START MeasGapConfig SEQUENCE { gapFR2 SetupRelease { GapConflg }

OPTIONAL, - Need M ff gapFRl SetupRelease { GapConfig }

OPTIONAL, — Need M gapUE SetupRelease { GapConfig }

OPTIONAL — Need M

11 }

GapC on fig SEQUENCE { gapOftset INTEGER (0..159), mgl ENUMERATED (msldotS, rns3, ms3dot5, ms4, ms5do†.5, ms6), mgrp ENUMERATED (ms20, ms40, ms80, msl60}, rngta ENUMERATED {msO, ms0dot25, msOdotS), • - ·? ff refServCel!Indicator ENUMERATED {pCell, pSCeil, mcg-FR2} OPTIONAL — Cond NEDCorNRDC ]],

[[ refFR2 ServCell AsyncCA-rl 6 ServCelllndex OPTIONAL, - Cond AsyncCA mgl-rl6 ENUMERATED (nislO, ms20}

OPTIONAL - Cond PRS

]]

}

-- T AG-ME A S GAP C QNF I G- S TOP - ASN1 STOP

[0064] Embodiment 1 : adding a multiple gap configuration as a list in MeasGapConfig (example shown in underline below)

[0065] MeasGapConfig information element

- ASM START

— TAG-MEASGAPCONFIG-START

MeasGapConfig ::= SEQUENCE { gapFR2 SetupRelease { GapConfig }

OPTIONAL, - Need M [[^' gapFRl SetupRelease { GapConfig } - Need M SetupRelease { GapConfig } - Need M multiGapConfigList SEQUENCE (SIZE (1 ..maxNumGap)) OF MultiGaoConfig OPTIONAL,

_ 31

1

MultiGaoConfig ::= _ SEQUENCE f

_ gapConfig _ Setup Release 1 GapConfig L

\ i

[0066] Embodiment 2: adding purpose of the gap in the configuration

[0067] Option 1 : add inside multiple gap config

MultiGaoConfig ::= _ SEQUENCE { gapConfig _ Setup Release i GapConfig i. rsTvoe ENUMERATED { SSR CSI-RS, PRS 1 ms5dot5, ms6}, rngrp ENUMERATED (ms20, ms40, ms80, msl60], mgta ENUMERATED (msO, ms0dot25, msOdotS), [[^' refServCelllndicator ENUMERATED (pCell, pSCell, mcg-FR2}

OPTIONAL — Cond NEDCorNRDC

]],

[[ refFR2ServCellAsyncCA-rl 6 ServCelllndex

OPTIONAL, — Cond AsyncCA mgl -r 16 ENUMERATED {mslO, ms20}

OPTIONAL - Cond PRS

E IL rsType ENUMERATED ]SSB_: CSI-RS. PRS}

I [0069] Embodiment 3: adding flag for autonomous enable/disable gap based on current BWP. When the flag is configured to true, the UE disable the measurement gap when the measurement (example shown in underlined below). [0070] When the UE current BWP is BWP-Id, and the gapDisable is set to true, the UE disable the associated gap. Alternatively, the gapDisable can be eliminated, only BWP id is present gap is disable when current active BWP is the same as BWP id configured. MultiGapConfig ::=^;: SEQUENCE X gapConfie Setup Release I GapConfig }, rsType _ ENUMERATED ; SSB. CSI-RS, PRS}, gapDisable _ ENUMERATED (TRUE), gapDi sableB WPid BWP-Id.

[0071] Examples:

[0072] Example 1 may include a method to define UE multiple measurement gap configuration, wherein the configuration is sent to the UE by RRC message.

[0073] Example 2 may include the method of example 1 or some other example herein, wherein adding a multiple gap configuration as a list in MeasGapC onfig. [0074] Example 3 may include the method of example 1 or some other example herein, wherein adding purpose of the gap in the configuration (add inside multiple gap config or add inside GapConfig).

[0075] Example 4 may include the method of example 1 or some other example herein, wherein adding flag for autonomous enable/disable gap based on current BWP.

[0076] Example 5 may include a method comprising:

[0077] receiving an RRC message that includes configuration information to indicate multiple measurement gap patterns; and [0078] performing measurements using one or more of the multiple measurement gap patterns. [0079] Example 6 may include the method of example 5 or some other example herein, wherein the multiple measurement gap patterns are indicated in a list in a MeasGapConfig information element (IE) in the RRC message.

[0080] Example 7 may include the method of example 5-6 or some other example herein, wherein the configuration information includes an indicate of a purpose of one or more individual gap patterns of the multiple gap patterns. [0081] Example 8 may include the method of example 5-7 or some other example herein, wherein the configuration information includes one or more flags to enable and/or disable the respective measurement gap patterns based on a current BWP.

[0082] Example 9 may include the method of example 5-8 or some other example herein, wherein the method is performed by a UE or a portion thereof

[0083] The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow⁷ the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What, is claimed is:

1. An apparatus of a generation node B (gNB), the apparatus comprising: processing circuitry; and memory', the processing circuitry configured to: encode a radio-resource control (RRC) reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a measurement gap (MG) configuration, the MG configuration comprising two or more independent MG patterns that are to he concurrently activated for the UE; and decode one or more measurement report messages from the UE, the one or more measurement report messages including measurements from the UE performed in accordance with the two or more independent MG patterns, wherein the memory is configured to store the MeasGapConfig IE.

2. The apparatus of claim 1, wherein the processing circuitry is to encode the MeasGapConfig IE to include the two or more independent MG patterns as a list.

3. The apparatus of claim 1, wherein the processing circuitry is to encode the MeasGapConfig IE to indicate a reference signal type (rsType) for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, wherein each indicated reference signal type comprises one of Sync Signal/PBCH block (SSB) signals, channel-state information reference signals (CSI-RS) and positioning reference signals (PRS).

4. The apparatus of claim 2, wherein the processing circuitry is to encode the MeasGapConfig IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, one or more MG configuration parameters, the MG configuration parameters comprising: a gap offset (gapOffset), a measurement gap length (MGL); a measurement gap repetition period (MGRP), and a measurement, gap timing advance (MGTA).

5. The apparatus of claim 4, wherein the processing circuitry is to further encode the MeasGapConfig IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, a reference sendee cell indicator (refServCei!Indicator).

6. The apparatus of claim 4, wherein the processing circuitry is to further encode the MeasGapConfig IE to include a gap disable flag (gapDisable) field for each of the two or more independent MG patterns, wherein the gap disable flag, when set, is to configure the UE to disable a corresponding one of the independent MG patterns.

7. The apparatus of claim 4, wherein the processing circuitry is to further encode the MeasGapConfig IE to include a gap disable bandwidth part (BWP) identifier (ID) (gapDisableBWPid) field for each of the two or more independent MG patterns, wherein the MeasGapConfig IE is to configure the LIE to disable a corresponding one of the independent MG patterns for a currently active BWP when the currently active BWP is identified by the disable BWP ID field.

8. The apparatus of any of claims 1 - 7, wherein the processing circuitry is configured to: decode a capabilities information message from the UE, the capabilities information message indicating whether the UE is capable of supporting the two or more independent MG patterns; and wherein when the UE has indicated a capability to support the two or more independent MG patterns, the processing circuitry is to encode the RRC reconfiguration message to include the MeasGapConfig IE to configure the UE with a single MG configuration comprising the two or more independent MG patterns; and wherein when the UE has not indicated a capability to support multiple concurrent independent MG patterns or has indicated that it does not have the capability to support multiple concurrent independent MG patterns, the processing circuitry is to encode the RRC reconfiguration message to include the MeasGapConfig IE to configure the HE with the single MG configuration comprising only one MG pattern.

9. The apparatus of claim 8, wherein when the UE is configured with the two or more independent MG patterns, a first of the two or more independent MG patterns is to configure the UE for radio-resource management (RRM) and a second of the two or more independent MG patterns is to configure the UE for measurement of positioning reference signal (PRS), and wherein when the UE is configured with only one MG pattern, the one MG pattern is configured to the LIE for both the RRM and for measurement of the PRS signals.

10. The apparatus of claim 1, wherein the processing circuitry includes a baseband processor.

11. A n on-transitory computer-readable storage medium that stores instructions for execution by processing circuitry' of a generation node B (gNB), the processing circuitry configured to: encode an RRC reconfiguration message to include a measurement gap configuration information element (MeasGapConfig IE) to configure a user equipment (UE) with a measurement gap (MG) configuration, the MG configuration comprising two or more independent MG patterns that are to be concurrently activated for the UE; and decode one or more measurement report messages from the UE, the one or more measurement report messages including measurements from the UE performed in accordance with the two or more independent MG patterns.

12. The non-transitory computer-readable storage medium of claim 11, wherein the processing circuitry is to encode the MeasGapConfig IE to include the two or more independent MG patterns as a list.

13. The non-transitory computer-readable storage medium of claim 11, wherein the processing circuitry is to encode the MeasGapConfig IE to indicate a reference signal type (rsType) for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, wherein each indicated reference signal type comprises one of Sync Signal/PBCH block (SSB) signals, channel- state information reference signals (CSI-RS) and positioning reference signals (PRS).

14. The non-transitory computer-readable storage medium of claim 12, wherein the processing circuitry is to encode the MeasGapConfig IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, one or more MG configuration parameters, the MG configuration parameters comprising: a gap offset (gapOffset), a measurement gap length (MGL); a measurement gap repetition period (MGRP), and a measurement gap timing advance (MGTA).

15. The non-transitory computer-readable storage medium of claim 14, wherein the processing circuitry' is to further encode the MeasGapConfig IE to indicate, for each of the two or more independent MG patterns indicated in the MeasGapConfig IE, a reference service cell indicator (refServCelllndicator).

16. The non-transitory computer-readable storage medium of claim 14, wherein the processing circuitry' is to further encode the MeasGapConfig IE to include a gap disable flag (gapDisable) field for each of the two or more independent MG patterns, wherein the gap disable flag, when set, is to configure the UE to disable a corresponding one of the independent MG patterns.

17. The non-transitory computer-readable storage medium of claim 14, wherein the processing circuitry is to further encode the MeasGapConfig IE to include a gap disable bandwidth part (BWP) identifier (ID) (gapDisabieBWPid) field for each of the two or more independent MG patterns, wherein the MeasGapConfig IE is to configure the UE to disable a corresponding one of the independent MG patterns for a currently active BWP when the currently active BWP is identified by the disable BWP ID field.

18. An apparatus of a user equipment (UE), the apparatus comprising: processing circuitry; and memory', the processing circuitry configured to: decode an RRC reconfiguration message received from a generation node B (gNB) that includes a measurement gap configuration information element (MeasGapConfig IE) to configure the UE with a measurement gap (MG) configuration, the MG configuration comprising two or more independent MG patterns that are to he concurrently activated for the UE; and encode one or more measurement report messages for transmission to the gNB, the one or more measurement report messages including measurements from the UE performed in accordance with the two or more independent MG patterns, wherein the memory is configured to store the MeasGapConfig IE.

19. The apparatus of claim 18, wherein the MeasGapConfig IE indicates a reference signal type (rsType) for each of the two or more independent MG paterns indicated in the MeasGapConfig IE, wherein each indicated reference signal type comprises one of Sync Signa!/PBCH block (SSB) signals, channel- state information reference signals (CSI-RS) and positioning reference signals (PRS).

20. The apparatus of claim 19, wherein the MeasGapConfig IE includes a gap disable bandwidth part (BWP) identifier (ID) (gapDisableBWPid) field for each of the two or more independent MG patterns, wherein the processing circuitry is to configure the UE to disable a corresponding one of the independent MG patterns for a currently active B WP when the currently active BWP is identified by the disable BWP ID field.