UE behavior when NCSG collides with other gaps

Abstract

A computer-readable storage medium having stored thereon instructions for execution by one or more processors of a UE causes the UE to perform operations including decoding first configuration signaling received from a base station associated with a first cell and received on a communication channel associated with a first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for a second frequency band, decoding second configuration signaling for configuring a legacy measurement gap for a third frequency band, detecting overlap between the NCSG measurement gap and the legacy measurement gap, performing first cell measurements of a second cell in the second frequency band during the NCSG measurement gap, and performing second cell measurements of the second cell in the third frequency band during the legacy measurement gap.

Description

[Background technology]

[0001] [Priority claim] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 422,360, entitled "USER EQUIPMENT (UE) BEHAVIOR WHEN NETWORK CONTROLLED SMALL GAPS (NCSGs) COLLIDING WITH OTHER GAPS IN CONCURRENT MEASUREMENT GAPS (MGs)," filed November 3, 2022, and incorporates the entire contents of that application by reference.

[0002] [Background technology] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The use of 3GPP LTE systems is increasing with the proliferation of different types of devices communicating with various network devices. The penetration of mobile devices (user equipment or UE) in modern society continues to drive demand for a variety of network-connected devices in many different environments. Fifth-generation (5G) wireless systems are emerging and are expected to enable even higher speeds, connectivity, and usability. Next-generation 5G networks (or NR networks) are expected to increase throughput, coverage, and robustness, and reduce latency and operational and capital expenditures. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver high-speed, rich content and services. As current cellular network frequencies become saturated, higher frequencies such as millimeter wave (mmWave) frequencies can be beneficial due to their higher bandwidth.

[0003] Potential LTE operation in unlicensed spectrum includes, but is not limited to, LTE operation in unlicensed spectrum via dual connectivity (DC) or DC-based LAA, and standalone LTE systems in unlicensed spectrum, whereby LTE-based technologies operate alone in unlicensed spectrum without the need for an "anchor" in licensed spectrum, known as MultiFire. Further enhanced operation of LTE and NR systems in licensed and unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for NCSG configuration, including UE behavior when NCSGs collide with other gaps, such as concurrent MGs. [Brief explanation of the drawings]

[0004] In the drawings, which are not necessarily to scale, like numerals may describe like components in different views. Like numerals with different subscripts may represent different instances of like components. The drawings illustrate generally, by way of example, but not by way of limitation, various aspects discussed in the present document. [Figure 1A] 1 illustrates a network architecture in accordance with some aspects. [Figure 1B] 1 illustrates a non-roaming 5G system architecture according to some aspects. [Figure 1C] 1 illustrates a non-roaming 5G system architecture according to some aspects. [Figure 2] 1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Figure 3] 1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Figure 4] 1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Figure 5]1 illustrates an exemplary configuration of overlapping NCSGs and legacy MGs, according to some aspects. [Figure 6] FIG. 1 illustrates a block diagram of a communications device, such as an evolved Node-B (eNB), new generation Node-B (gNB) (or another RAN node), NCR, access point (AP), wireless station (STA), mobile station (MS), or user equipment (UE), according to some aspects. DETAILED DESCRIPTION OF THE INVENTION

[0005] The following description and drawings sufficiently illustrate the 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. The embodiments outlined in the claims encompass all available equivalents of those claims.

[0006] 1A illustrates a network architecture according to some aspects. Communication network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and UE 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 a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and UE 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0007] Any of the wireless links described herein (eg, as used in communications network 140A or any other illustrated network) may operate according to any example wireless communications technology and / or standard.

[0008] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs, such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique in 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 aspects, carrier aggregation may be used when one or more component carriers operate on unlicensed frequencies.

[0009] The aspects described herein can be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond frequencies, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0010] The aspects described herein may 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 to 3GPP NR by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0011] In some aspects, either the UE 101 or the UE 102 may comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-term UE connections. In some aspects, either the UE 101 or the UE 102 may comprise a narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a Further Enhanced IoT (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over a public land mobile network (PLMN), proximity-based service (ProSe) or device-to-device (D2D) communications, sensor network, or IoT network. An 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), over short-term connections. IoT UEs may run background applications (e.g., key-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0012] In some aspects, either UE 101 or UE 102 may comprise an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0013] UE 101 and UE 102 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 110. RAN 110 may be, e.g., a Universal Mobile Telecommunications System (UMTS), an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. UE 101 and UE 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below), which in this example are shown as air interfaces for enabling communication coupling and may be consistent with cellular communication 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 fifth-generation (5G) protocol, a New Radio (NR) protocol, etc.

[0014] In one aspect, the UE 101 and the UE 102 may further directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface, which includes one or more logical channels, including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

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

[0016] The RAN 110 may include one or more access nodes (ANs) that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN network nodes, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission / reception points (TRPs). When the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN nodes, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell), e.g., low power (LP) RAN nodes or unlicensed spectrum-based secondary RAN nodes.

[0017] Either of the communication nodes 111 and 112 may terminate air interface protocols and may be the initial point of contact for the UE 101 and the UE 102. In some aspects, either of the communication nodes 111 and 112 may implement 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 one example, either of the communication nodes 111 and / or 112 may be a new generation Node-B (gNB), an evolved Node-B (eNB), or another type of RAN node.

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

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

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

[0021] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the EPC network 120 (e.g., the CN 120) and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element that provides applications that use IP bearer resources in conjunction with a core network (e.g., a UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., 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.

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

[0023] In some aspects, the communication network 140A may be an IoT network or a 5G network, including a 5G New Radio Network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is narrowband IoT (NB-IoT).

[0024] The NG system architecture may include a RAN 110 and a 5G core network 120 (e.g., a CN 120). The RAN 110 in the NG system may be referred to as an NG-RAN. The RAN 110 may include multiple nodes such as a gNB and an NG-eNB. The CN 120 (also referred to as a 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0025] In some aspects, the NG system architecture may use reference points between various nodes such as those provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a Home eNB, a RAN network node, etc. In some aspects, in a 5G architecture, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN). In some aspects, the master / primary node may operate in a licensed band and the secondary node may operate in an unlicensed band.

[0026] 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an access and mobility management function (AMF) 132, a location management function (LMF) 133, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a user plane function (UPF) 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146. The UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include a network slice selection function. The SMF 136 can be configured to set up and manage various sessions according to network policies. The UPF 134 can be deployed in one or more configurations according to the desired service type.The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0027] The LMF 133 may be used in connection with 5G positioning functions. In some aspects, the LMF 133 receives measurements and assistance information from the RAN 110 and a mobile device (e.g., UE 101) via the AMF 132 over the NL interface to calculate the position of the UE 101. In some aspects, the NR positioning protocol A (NRPPa) may be used to carry positioning information between the NG-RAN and the LMF 133 over the next generation control plane interface (NG-C). In some aspects, the LMF 133 configures the UE using the LTE positioning protocol (LPP) via the AMF 132. The RAN 110 configures the UE 101 using a radio resource control (RRC) protocol over the LTE-Uu and NR-Uu interfaces.

[0028] In some aspects, the 5G system architecture 140B configures different reference signals to enable positioning measurements. Exemplary reference signals that may be used for positioning measurements include NR positioning reference signals (PRS) in the downlink and sounding reference signals (SRS) for positioning in the uplink. The downlink positioning reference signals (PRS) are reference signals configured to support downlink-based positioning methods.

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

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

[0031] The reference point representation indicates that there may be interactions between the corresponding NF services. For example, Figure 1B shows 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 / HSS 146 and the AMF 132, not shown), N9 (between two UPFs, not shown), N10 (between the UDM / HSS 146 and the SMF 136, not shown), N11 (between the UDM / HSS 146 and the SMF 136, not shown), N12 (between the UPF 134 and the DN 152, not shown), N13 (between the UPF 134 and the DN 152, not shown), N14 (between the UDM / HSS 146 and the SMF 136, not shown), N15 (between the UPF 134 and the DN 152, not shown), N16 (between the UPF 134 and the DN 152, not shown), N17 (between the UDM / HSS 146 and the AMF 132, not shown), N18 (between the UDM / HSS 146 and the AMF 132, not shown), N19 (between two UPFs, not shown), N20 (between the UDM / HSS 1 1B shows 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 / HSS 146, not shown), N14 (between two AMFs, not shown), N15 (between the PCF 148 and the AMF 132 in a non-roaming scenario, or between the PCF 148 and the visited network and the AMF 132 in a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between the AMF 132 and the NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.

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

[0033] 1C , the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM / HSS 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (eg, Nudr, N5g-eir, and Nudsf) may also be used.

[0034] 2-7 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR networks, including 5G non-terrestrial networks (NTNs). UEs, base stations (such as gNBs), and / or other nodes (e.g., satellites or other NTN nodes) discussed herein may be configured to perform the disclosed techniques.

[0035] 2 illustrates a network 200 in accordance with various embodiments. Network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems.

[0036] The network 200 may include a UE 202, which may comprise any mobile or non-mobile computing device designed to communicate over a wireless connection with the RAN 204. The UE 202 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0037] In some embodiments, the network 200 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0038] In some embodiments, the UE 202 may further communicate with the AP 206 via a wireless connection. The AP 206 may manage a WLAN connection, which may function to offload some / all network traffic from the RAN 204. The connection between the UE 202 and the AP 206 may be consistent with any IEEE 802.11 protocol, and the AP 206 may be a wireless fidelity (Wi-Fi) router. In some embodiments, the UE 202, the RAN 204, and the AP 206 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may involve the UE 202 being configured by the RAN 204 to utilize both cellular radio resources and WLAN resources.

[0039] The RAN 204 may include one or more access nodes, such as the access node (AN) 208. The AN 208 may terminate air interface protocols for the UE 202 by providing access stratum protocols, including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this manner, the AN 208 may enable data / voice connectivity between the core network (CN) 220 and the UE 202. In some embodiments, the AN 208 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as, for example, a CRAN or virtual baseband unit pool. The AN 208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 208 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, lower user capacity, or higher bandwidth compared to a macrocell.

[0040] In embodiments where the RAN 204 includes multiple ANs, the multiple ANs may be coupled to one another via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into a control / user plane interface, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference control, etc.

[0041] Each AN of the RAN 204 may manage one or more cells, cell groups, component carriers, etc. to provide the UE 202 with an air interface for network access. The UE 202 may simultaneously connect to multiple cells provided by the same or different ANs of the RAN 204. For example, the UE 202 and the RAN 204 may use carrier aggregation to enable the UE 202 to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0042] The RAN 204 may provide an air interface over a licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using the PCell / SCell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0043] In a V2X scenario, the UE 202 or the AN 208 may be or function as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a static (or relatively static) UE. An RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an eNB may be referred to as an “eNB-type RSU,” a gNB may be referred to as a “gNB-type RSU,” and so forth. In one example, the RSU is a computing device coupled to radio frequency circuits located on the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, and media, as well as applications / software for detecting and controlling on-going vehicular and pedestrian traffic. The RSU may provide very low-latency communications required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0044] In some embodiments, the RAN 204 may be an LTE RAN 210 including an eNB, e.g., eNB 212. The LTE RAN 210 may provide the LTE air interface with the following features: 15 kHz sub-carrier spacing (SCS), CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL, turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in sub-6 GHz bands.

[0045] In some embodiments, the RAN 204 may be an NG-RAN 214 having a gNB, e.g., gNB 216, or an ng-eNB, e.g., ng-eNB 218. The gNB 216 may connect to a 5G-capable UE using a 5G NR interface. The gNB 216 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 218 may also connect to the 5G core through the NG interface, but may also connect to the UE through an LTE air interface. The gNB 216 and the ng-eNB 218 may connect to each other through an Xn interface.

[0046] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface), which carries traffic data between the nodes of the NG-RAN 214 and the UPF 248, and an NG control plane (NG-C) interface (e.g., N2 interface), which is the signaling interface between the nodes of the NG-RAN 214 and the AMF 244.

[0047] The NG-RAN 214 may provide the 5G NR air interface with the following features: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, and polar, repetition, simplex, and Reed-Muller codes for data control and LDPC. The 5G NR air interface may rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and tracking reference signals for time tracking. The 5G NR air interface may operate in the sub-6 GHz band, which includes the 24.25 GHz to 52.6 GHz band, or the FR1 band, which includes the FR2 band. The 5G NR air interface may include a synchronization signal and physical broadcast channel (SS / PBCH) block (SSB, SS / PBCH block), which is an area of ​​the downlink resource grid that includes the PSS / SSS / PBCH.

[0048] In some embodiments, the 5G NR air interface may utilize bandwidth parts (BWPs) for various purposes. For example, BWPs can be used for dynamic SCS adaptation. For example, a UE 202 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 202, the SCS of the transmission changes as well. Another use case for BWPs relates to power saving. In particular, multiple BWPs with different amounts of frequency resources (e.g., PRBs) can be configured for a UE 202 to support data transmission under different traffic load scenarios. A BWP with a smaller number of PRBs can be used for data transmissions with low traffic, enabling power savings at the UE 202 and, in some cases, at the gNB 216. A BWP with a larger number of PRBs can be used for scenarios with higher traffic loads.

[0049] The RAN 204 is communicatively coupled to the CN 220, which includes network elements for providing various functions to support data and telecommunication services to customers / subscribers (e.g., users of UEs 202). The components of the CN 220 may be implemented on a single physical node or on separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 220 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice.

[0050] In some embodiments, the CN 220 may be connected to an LTE wireless network as part of an Enhanced Packet System (EPS) 222, which may also be referred to as the EPC (or Evolved Packet Core). The EPC 222 may include an MME 224, an SGW 226, an SGSN 228, an HSS 230, a PGW 232, and a PCRF 234 coupled together over interfaces (or "reference points") as shown. The functionality of the elements of the EPC 222 may be briefly introduced as follows.

[0051] The MME 224 may implement mobility management functions to track the current location of the UE 202 and facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0052] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the EPC 222. The SGW 226 may be the local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0053] The SGSN 228 may track the location of the UE 202 and perform security functions and access control. Additionally, the SGSN 228 may perform EPC inter-node signaling for mobility between different RAT networks, PDN and S-GW selection as specified by the MME 224, MME selection for handover, etc. The S3 reference point between the MME 224 and the SGSN 228 may enable the exchange of user and bearer information for inter-3GPP access network mobility in idle / active state.

[0054] The HSS 230 may include a database for network users, including subscription-related information, to support the handling of communication sessions by network entities. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 230 and the MME 224 may enable the transfer of subscription and authentication data to authenticate / authorize user access to an LTE CN (e.g., CN 220).

[0055] The PGW 232 may terminate an SGi interface toward a data network (DN) 236, which may include an application / content server 238. The PGW 232 may route data packets between the LTE CN and the data network 236. The PGW 232 may be coupled to the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 232 may further include a node for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point between the PGW 232 and the data network 236 may be an operator-external public or private PDN or an intra-operator packet data network, e.g., for the provision of IMS services. The PGW 232 may be coupled to the PCRF 234 via a Gx reference point.

[0056] The PCRF 234 is the policy and charging control element of the CN 220. The PCRF 234 may be communicatively coupled to the app / content server 238 to determine the appropriate QoS and charging parameters for the service flow. The PCRF 234 may provide the associated rules to the PCEF (over the Gx reference point) with the appropriate TFT and QCI.

[0057] In some embodiments, CN 220 may be 5GC 240. 5GC 240 may include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled together over interfaces (or "reference points") as shown. The functionality of the elements of 5GC 240 may be briefly introduced as follows.

[0058] The AUSF 242 may store data and handle authentication-related functions for authentication of the UE 202. The AUSF 242 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 240 over reference points as shown, the AUSF 242 may exhibit a Nausf service-based interface.

[0059] The AMF 244 may enable other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and to subscribe to notifications about mobility events related to the UE 202. The AMF 244 may be responsible for registration management (e.g., for UE 202 registration), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 244 may provide transport of SM messages between the UE 202 and the SMF 246 and act as a transparent proxy for routing of SM messages. The AMF 244 may also provide transport of SMS messages between the UE 202 and the SMSF. The AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Additionally, the AMF 244 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 204 and the AMF 244, and the AMF 244 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 244 may also support NAS signaling with the UE 202 over the N3 IWF interface.

[0060] The SMF 246 may be responsible for SM (e.g., session establishment between the UPF 248 and the AN 208, tunnel management), UE IP address allocation and management (including optional authorization), UP function selection and control, traffic steering configuration in the UPF 248 to route traffic to the appropriate destination, termination of the interface towards the policy control function, policy enforcement, control of parts of charging and quality of service, lawful interception (for SM events and interface to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information sent over N2 to the AN 208 via the AMF 244, and determination of the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.

[0061] The UPF 248 may function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 236, and a branching point for supporting multi-homed PDU sessions. The UPF 248 may also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), traffic usage reporting, user plane quality of service processing (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., mapping flows from SDF to QoS), marking transport-level packets in the uplink and downlink, buffering downlink packets, and triggering downlink data notifications. The UPF 248 may include an uplink classifier to support routing of traffic flows to the data network.

[0062] The NSSF 250 may select a set of network slice instances to serve the UE 202. The NSSF 250 may also determine the allowed NSSAIs and, if necessary, their mapping to subscribed S-NSSAIs. The NSSF 250 may also determine an AMF set, or a list of candidate AMFs, to be used to serve the UE 202 based on a preferred configuration, possibly by querying the NRF 254. The selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 to which the UE 202 is registered, by interacting with the NSSF 250, which may result in an AMF change. The NSSF 250 may interact with the AMF 244 via the N22 reference point and may communicate with another NSSF in a visited network via the N31 reference point (not shown). Additionally, the NSSF 250 may present an Nnssf service-based interface.

[0063] The NEF 252 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal publication / republication, AFs (e.g., AF 260), edge computing or fog computing systems, etc. In such embodiments, the NEF 252 may authenticate, authorize, or throttle AFs. The NEF 252 may also translate information exchanged with the AF 260 and with internal network functions. For example, the NEF 252 may translate between AF service identifiers and internal 5GC information. The NEF 252 may also receive information from other NFs based on the other NFs' published capabilities. This information may be stored in the NEF 252 as structured data or may be stored in a data storage NF using a standardized interface. The stored information can then be republished by the NEF 252 to other NFs and AFs or used for other purposes, such as analysis. Additionally, the NEF 252 may present an NEF service-based interface.

[0064] The NRF 254 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to the NF instances. The NRF 254 may also maintain information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and an "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 254 may expose an Nnrf service-based interface.

[0065] The PCF 256 may provide policy rules to control plane functions and enforce them, and may support a unified policy framework to govern network behavior. The PCF 256 may also implement a front end to access subscription information relevant to policy decisions in the UDRs of the UDM 258. In addition to communicating with functions over reference points as shown, the PCF 256 may expose an Npcf service-based interface.

[0066] The UDM 258 may process subscription-related information to support processing of communication sessions by network entities and may store subscription data for the UE 202. For example, the subscription data may be communicated via the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for publishing and application data for the NEF 252 (including PFDs for application discovery and application request information for multiple UEs). A Nudr service-based interface may be presented by the UDR 221 to enable the UDM 258, the PCF 256, and the NEF 252 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of changes to the associated data in the UDR. The UDM may include a UDM-FE responsible for certificate handling, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 258 may present a Nudm service-based interface.

[0067] The AF 260 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0068] In some embodiments, the 5GC 240 may enable edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 202 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 240 may select a UPF 248 close to the UE 202 and perform traffic steering from the UPF 248 to the data network 236 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 260. In this way, the AF 260 may influence UPF (re)selection and traffic routing. Based on operator deployment, if the AF 260 is considered a trusted entity, the network operator may allow the AF 260 to interact directly with the associated NF. Additionally, the AF 260 may present a NAF service-based interface.

[0069] Data network 236 may represent various network operator services, internet access, or third party services, which may be provided by one or more servers, including, for example, application / content server 238 .

[0070] In some aspects, the network 200 is configured for NR positioning using a location management function (LMF) 245, which can be configured as an LMF node or as a function within a different type of node. In some embodiments, the LMF 245 is configured to receive measurements and assistance information from the NG-RAN 214 and the UE 202 via the AMF 244 (e.g., using an NL interface) to calculate the position of the UE. In some embodiments, the NR positioning protocol A (NRPPa) protocol can be used to convey positioning information between the NG-RAN 214 and the LMF 245 over a next-generation control plane interface (NG-C). In some embodiments, the LMF 245 configures the UE 202 using the LTE positioning protocol (LPP) (e.g., an LPP-based communication link) via the AMF 244. In some aspects, the NG-RAN 214 configures the UE 202 using, for example, radio resource control (RRC) protocol signaling, e.g., over the LTE-Uu and NR-Uu interfaces. In some aspects, the UE 202 uses the LTE-Uu interface to communicate with the ng-eNB 218 and the NR-Uu interface to communicate with the gNB 216. In some aspects, the ng-eNB 216 and the gNB 216 use the NG-C interface to communicate with the AMF 244.

[0071] In some embodiments, the following reference signals can be used to accomplish positioning measurements in an NR communication network: an NR positioning reference signal (NR PRS) in the downlink and a sounding reference signal (SRS) for positioning in the uplink. The downlink positioning reference signal (PRS) can be used as a reference signal to support downlink-based positioning techniques. In some aspects, the entire NR bandwidth can be covered by transmitting the PRS over multiple symbols, which can be aggregated to accumulate power.

[0072] 3 illustrates a schematic diagram of a wireless network 300 in accordance with various embodiments. The wireless network 300 may include a UE 302 that communicates wirelessly with an AN 304. The UE 302 and the AN 304 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

[0073] The UE 302 may be communicatively coupled to the AN 304 via a connection 306. The connection 306 is shown as an air interface that enables the communicative coupling and may be consistent with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating in mmWave or sub-6 GHz frequencies.

[0074] The UE 302 may include a host platform 308 coupled to a modem platform 310. The host platform 308 may include an application processing circuit 312 that may be coupled to a protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 may execute various applications for the UE 302 to source / sink application data. The application processing circuit 312 may further implement one or more layer operations for transmitting / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0075] The protocol processing circuitry 314 may implement one or more of the layer operations to facilitate transmission or reception of data over the connection 306. The layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0076] The modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations in a network protocol stack "below" the layer operations performed by the protocol processing circuitry 314. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0077] The modem platform 310 may include transmit circuitry 318, receive circuitry 320, RF circuitry 322, and an RF front end (RFFE) 324 that may include or connect to one or more antenna panels 326. Briefly, the transmit circuitry 318 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc., the receive circuitry 320 may include analog-to-digital converters, mixers, IF components, etc., the RF circuitry 322 may include low noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 324 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and configuration of the transmit circuitry 318, receive circuitry 320, RF circuitry 322, RFFE 324, and one or more antenna panels 326 components (commonly referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communication is TDM or FDM, mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be configured with multiple parallel transmit / receive chains, located on the same or different chips / modules, etc.

[0078] In some embodiments, the protocol processing circuitry 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0079] UE reception may be established by and through one or more antenna panels 326, RFFE 324, RF circuitry 322, receive circuitry 320, digital baseband circuitry 316, and protocol processing circuitry 314. In some embodiments, one or more antenna panels 326 may receive transmissions from AN 304 by receive beamforming signals received by multiple antennas / antenna elements of the one or more antenna panels 326.

[0080] UE transmissions may be established by and through protocol processing circuitry 314, digital baseband circuitry 316, transmit circuitry 318, RF circuitry 322, RFFE 324, and one or more antenna panels 326. In some embodiments, the transmit components of UE 302 may apply spatial filters to data to be transmitted to form transmit beams that are radiated by antenna elements of one or more antenna panels 326.

[0081] Similar to the UE 302, the AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled to a protocol processing circuit 334 of the modem platform 330. The modem platform may further include a digital baseband circuit 336, a transmit circuit 338, a receive circuit 340, an RF circuit 342, an RFFE circuit 344, and an antenna panel 346. The components of the AN 304 may be similar to, or substantially interchangeable with, similarly named components of the UE 302. In addition to performing data transmission / reception as described above, the components of the AN 304 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0082] 4 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein, according to some example embodiments. Specifically, FIG. 4 illustrates a schematic representation of hardware resources 400, including one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 402 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 400.

[0083] The one or more processors 410 may include, for example, processor 412 and processor 414. The one or more processors 410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, or a combination of both. The processor may be a DSP such as a computing processor, a graphics processing unit (GPU), a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

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

[0085] The one or more communication resources 430 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 404 or one or more databases 406 or other network elements over the network 408. For example, the one or more communication resources 430 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0086] The instructions 450 may include software, a program, an application, an applet, an app, or other executable code for causing one or more of the processors 410 to perform any one or more of the methodologies discussed herein. The instructions 450 may reside, completely or partially, within one or more of the processors 410 (e.g., in a processor's cache memory), the memory / storage device 420, or any suitable combination thereof. Furthermore, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of one or more peripheral devices 404 or one or more databases 406. Thus, the memory of one or more processors 410, the memory / storage device 420, the one or more peripheral devices 404, and the one or more databases 406 are examples of computer-readable and machine-readable media.

[0087] For one or more embodiments, at least one of the components outlined in one or more of the above figures may be configured to perform one or more operations, techniques, processes, and / or methods as outlined in the example section below. For example, baseband circuitry associated with one or more of the above figures may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, satellite, network element, etc., as described above in connection with one or more of the above figures, may be configured to operate according to one or more of the examples described below in the example section.

[0088] The term "application" may refer to a complete, deployable package or environment for achieving a specific function in an operating environment. Terms such as "AI / ML application" may refer to an application that includes several artificial intelligence (AI) / machine learning (ML) models and application-level descriptions. In some embodiments, an AI / ML application may be used to configure or implement one or more aspects of the disclosure.

[0089] The terms "machine learning" or "ML" refer to the use of computer systems that implement algorithms and / or statistical models to perform specific tasks without explicit instructions, relying instead on patterns and inference. ML algorithms build or infer mathematical models (e.g., referred to as "ML models") based on sample data (e.g., referred to as "training data," "model training information," etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance indicators, and an ML model may be any object or data structure created after an ML algorithm is trained on one or more training datasets. After training, the ML model may be used to make predictions on new datasets. Although the term "ML algorithm" refers to a different concept from the term "ML model," these terms may be used interchangeably in this disclosure as discussed herein.

[0090] Terms such as "machine learning model," "ML model," and the like may also refer to ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that uses ML algorithms to address a specific use case during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a particular ML model may have many submodels as components, and the ML model may train all the submodels together. Separately trained ML models may also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, functions, or functional entities specific to an ML-assisted solution, and an ML pipeline may include one or several data sources among a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. An "actor" is an entity that hosts an ML-assisted solution using the output of ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during inference mode (including both model execution and, if applicable, any online learning). The ML host notifies the actor about the output of the ML algorithm, and the actor decides on an action (an "action" is performed by the actor as a result of the output of the ML-assisted solution).The term "model inference information" refers to information used as input to an ML model to determine an inference; although the data used to train the ML model and the data used to determine the inference may overlap, "training data" and "inference data" refer to different concepts.

[0091] The following objectives can be considered in connection with the disclosed technology:

[0092] (a) Pre-configured MG, multiple concurrent MGs and NCSG extensions.

[0093] (a.1) Define radio resource management (RRM) requirements for UEs configured with a combination of pre-configured MG and / or multiple concurrent MGs and / or NCSGs.

[0094] (a.1.1) Prioritize joint requirements for UEs configured as follows:

[0095] (a.1.1.1) Case 1: Pre-configured MG and multiple concurrent MGs (i.e., concurrent MGs where at least one of the gaps is a pre-configured gap).

[0096] (a.1.1.2) Case 2: NCSG and multiple simultaneous MGs (i.e., simultaneous MGs where at least one of the gaps is an NCSG).

[0097] In some aspects, priorities between other possible combinations of pre-configured MGs, concurrent MGs and NCSGs may be considered.

[0098] In some aspects, according to the requirements for dropping rules in Rel. 17, when an NCSG collides with other gaps within a simultaneous gap, the UE needs to drop one of them based on the assigned priority. However, this configuration results in higher resource waste.

[0099] As shown in FIG. 5, there are some cases where both NCSG and other legacy measurement gaps are configured within a simultaneous measurement gap.

[0100] FIG. 5 illustrates a diagram 500 of an example configuration of overlapping NCSGs and legacy MGs, according to some aspects.

[0101] Referring to Figure 5, in case (a), the start / end points of the two gaps are interlaced. If the UE supports NCSG for two frequency bands f1 and f2 (e.g., in addition to supporting frequency bands f0 and f1), the UE can return to the RF chain for data before t2 for f2 at t2 for measurement at f2. In this regard, there is no need to drop the measurement gap.

[0102] In case (b), the legacy MG (Type 1 / 2-MG) can be fully covered by the NCSG measurement gap. If the UE supports NCSG for frequency bands f1 and f2 (e.g., in addition to supporting frequency bands f0 and f1), the UE can revert to the RF chain for data before t2 for f2 at t2 for measurements at f2. In this regard, there is no need to drop the measurement gap.

[0103] If the UE does not support NCSG for frequency bands f1 and f2 (in addition to supporting frequency bands f0 and f1), the UE may not use two RF chains simultaneously on both f1 and f2. In this regard, the UE may need to drop one of them (e.g., based on a lower priority). In this regard, it is not necessary to drop measurement gaps.

[0104] In case (c), the NCSG can be completely contained by the legacy MG (Type 1 / 2-MG). The UE can perform measurements in frequency band f2 using "RX RF Chain 1" from time t1. At time t2, the UE can retune to another RX RF Chain 2 that was used for data Rx in frequency bands f0 to f2. In this regard, there is no need to drop the measurement gap.

[0105] In an NCSG configuration, the UE is not expected to transmit (Tx) or receive (Rx) any data during the visible interruption length (VIL) period that may be at the beginning and end of the NCSG.

[0106] In some aspects, both the NCSG and the legacy MG are configured via radio resource control (RRC) signaling. The configuration of the NCSG and any legacy MG may include a priority indicator for the NCSG and MG, respectively, to indicate the priority of the corresponding gap. Measurements for one or both of the NCSG and MG may be initiated or dropped based on such priority indicator.

[0107] In case (a), the UE can perform measurements on a carrier in frequency band f1 from time t1. Because the UE can support NCSG for the combination of frequency bands f0 and f1, the UE can also receive data on the primary cell carrier in frequency band f0 from time t1 to time t3. Therefore, when the UE needs to perform measurements on another carrier (e.g., frequency band f2) from time t2, the UE needs to drop one of the measurement gaps based on the rules of Rel. 17. However, if the UE can also support simultaneous multiple RF chain operation (e.g., NCSG capability) on frequency bands f1 and f2, the UE can retune the available RF chain used for data reception during the time interval [t1, t2] to frequency band f2. Measurements for both frequency bands f1 and f2 can then be performed. That is, in this situation, it is not necessary to drop any one of the simultaneous gaps (NCSG and Type 1-MG).

[0108] In some embodiments, in the case of simultaneous MG where one of the NCSGs is configured, if the UE can support NCSG capabilities for both the band combination of frequency bands f0 and f1 and the band combination of f1 and f2, the UE does not need to drop any of the gap instances (time points) when they collide.

[0109] In some embodiments, in the case of a collision between NCSG and other types of gap opportunities, the UE may perform measurements in each opportunity of the measurement gap if the measurement objects associated with these measurement gaps are within the same band or bands that support the NCSG capability.

[0110] In some embodiments, in the case of a collision between NCSG and other types of gap opportunities, if the UE supports an empty RF chain shared between the serving cell's carrier and other carriers to be measured, the UE may perform measurements at each opportunity in the measurement gap.

[0111] In some embodiments, there are methods for defining UE behavior when an NCSG is configured in a concurrent measurement gap. In some aspects, the NCSG collides with other measurement gap opportunities. In some aspects, the UE does not drop any of the overlapping gap instances. In some aspects, the UE can support NCSG capabilities in the bands of all measurement objects. In some aspects, the measurement objects configured for the UE are in the same band. In some aspects, a measurement carrier with an NCSG and / or other carriers with other types of gaps can share an empty RF chain with the serving cell carrier.

[0112] 6 illustrates a block diagram of a communications device such as an evolved Node-B (eNB), new generation Node-B (gNB) (or another RAN node such as a base station), network-controlled repeater (NCR), access point (AP), wireless station (STA), mobile station (MS), or user equipment (UE) for performing one or more of the techniques disclosed herein, according to some aspects. In alternative aspects, communications device 600 may operate as a standalone device or may be connected (e.g., network-connected) to other communications devices.

[0113] A circuit (e.g., processing circuit) is a collection of circuits implemented in a tangible entity of device 600, including hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership may be flexible over time. A circuit includes elements that, when operational, can perform specified operations, either alone or in combination. In one example, the hardware of a circuit may be invariably designed (e.g., hardwired) to perform specific operations. In one example, the hardware of a circuit may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include machine-readable media that are physically modified (e.g., magnetically, electrically, a movable arrangement of invariant assembly particles, etc.) to encode instructions for specific operations.

[0114] When connecting physical components, the underlying electrical properties of the hardware components are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., an execution unit or loading mechanism) to create members of a circuit within the hardware through variable connections to perform some of the specific operations during operation. Thus, in one example, a machine-readable medium element is part of a circuit or is communicatively coupled to other components of a circuit when the device is operating. In one example, any of the physical components may be used in more than one member of more than one circuit. For example, during operation, an execution unit may be used in a first circuit of a first circuit at one time and reused by a second circuit of the first circuit or a third circuit of the second circuit at a different time. Further examples of these components with respect to device 600 follow below.

[0115] In some aspects, device 600 may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked deployment, communications device 600 may operate in the capacity of a server communications device, a client communications device, or both in a server-client network environment. In one example, communications device 600 may operate as a peer communications device in a peer-to-peer (P2P) (or other distributed) network environment. Communications device 600 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web appliance, network router, switch, or bridge, or any communications device capable of executing instructions (sequential or otherwise) that specify operations to be performed by the communications device. Furthermore, while only a single communications device is shown, the term “communications device” shall also be interpreted to include any collection of communications devices that individually or collectively execute a set (or sets) of instructions to perform any one or more of the methodologies discussed herein, such as in cloud computing, software as a service (SaaS), or other computer cluster configurations.

[0116] The examples described herein may include or operate on logic or several components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that can perform specified operations and may be configured or arranged in a particular manner. In one example, a circuit may be arranged as a module (e.g., internally or relative to an external entity such as another circuit) in a specified manner. In one example, one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured in whole or in part with firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In one example, the software may reside on a communication device-readable medium. In one example, the software, when executed by the underlying hardware of a module, causes the hardware to perform specified operations.

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

[0118] A communications device (e.g., a UE) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604, a static memory 606, and a storage device 616 (e.g., a hard drive, a tape drive, flash storage, or other block or storage device), some or all of which may communicate with each other via an interlink 608 (e.g., a bus).

[0119] The communication device 600 may further include a display device 610, an input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In one example, the display device 610, the input device 612, and the UI navigation device 614 may be touchscreen displays. The communication device 600 may further include a signal generating device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0120] The storage device 616 may include a device-readable medium 622 on which one or more sets of data structures or instructions 624 (e.g., software) are stored that embody or are utilized by any one or more of the techniques or functions described herein. In some aspects, the registers of the hardware processor 602, the main memory 604, the static memory 606, and / or the storage device 616 may be, or may include (completely or at least partially) the device-readable medium 622 on which one or more sets of data structures or instructions 624 are stored that embody or are utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute the device-readable medium 622.

[0121] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." While the device-readable medium 622 is depicted as a single medium, the term "communications device-readable medium" may include a single medium or multiple media (e.g., centralized or distributed databases and associated caches and servers) configured to store the instructions 624. The term "communications device-readable medium" may include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 624) for execution by the communications device 600, causing the communications device 600 to perform any one or more of the techniques of this disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of communications device-readable media may include solid-state memory, optical, and magnetic media. Specific examples of communication device 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. In some examples, communication device readable media may include non-transitory communication device readable media. In some examples, communication device readable media may include communication device readable media that are not transitory propagating signals.

[0122] Additionally, the instructions 624 may be sent or received over the communications network 166 using a transmission medium via the network interface device 620 utilizing any one of several transport protocols. In one example, the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas for connecting to the communications network 626. In one example, the network interface device 620 may include multiple antennas for communicating wirelessly using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input-single-output (MISO) technologies.

[0123] The term "transmission medium" shall be construed as including any intangible medium capable of storing, encoding, or carrying instructions for execution by communication device 600, including digital or analog communication signals or other intangible media for facilitating the communication of such software. In this regard, transmission media in the context of the present disclosure are device-readable media.

[0124] The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure. These terms are defined to include both mechanical storage media and transmission media. Thus, these terms include both storage devices / media and carrier wave / modulated data signals.

[0125] Implementations of the described subject matter can include one or more of the features, alone or in combination, such as, by way of example, the following:

[0126] Example 1 is an apparatus for a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, comprising: To configure the UE for measurements during the simultaneous measurement gap: decoding first configuration signaling received from a base station associated with the first cell, where the first configuration signaling is received on a communication channel associated with the first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for the second frequency band; decoding second configuration signaling received from the base station, where the second configuration signaling is for configuring a legacy measurement gap for a third frequency band; Detecting overlap between NCSG measurement gaps and legacy measurement gaps; performing a first cell measurement of the second cell in the second frequency band during the NCSG measurement gap and a second cell measurement of the second cell in the third frequency band during the legacy measurement gap based on the overlap; a processing circuit for encoding the first cell measurement and the second cell measurement for transmission to a base station; An apparatus includes a memory coupled to the processing circuit and configured to store first configuration signaling and second configuration signaling.

[0127] In Example 2, the subject matter of Example 1 includes subject matter where the NCSG measurement gap and the legacy measurement gap overlap, and the start time of the legacy measurement gap is after the start time of the NCSG measurement gap.

[0128] In Example 3, the subject matter of Example 2 includes subject matter where the processing circuit decodes data received on a communication channel associated with the first frequency band between a start time of the NCSG measurement gap and a start time of the legacy measurement gap.

[0129] In Example 4, the subject matter of Example 3 further comprises: the processing circuitry configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at a start time of the legacy measurement gap; Subject matter includes performing, after a start time of the legacy measurement gap, second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain.

[0130] In Example 5, the subject matter of Examples 1-4 includes subject matter where the start time and end time of the legacy measurement gap are within the NCSG measurement gap.

[0131] In Example 6, the subject matter of Example 5 includes subject matter where the processing circuit decodes data received on a communication channel associated with the first frequency band between a start time of the NCSG measurement gap and a start time of the legacy measurement gap, and between an end time of the legacy measurement gap and an end time of the NCSG measurement gap.

[0132] In Example 7, the subject matter of Example 6 further comprises: the processing circuitry configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at a start time of the legacy measurement gap; Subject matter includes performing, after a start time of the legacy measurement gap, second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain.

[0133] In Example 8, the subject matter of Examples 1-7 includes subject matter in which the start time and end time of the NCSG measurement gap are within the legacy measurement gap.

[0134] In Example 9, the subject matter of Example 8 further comprises: the processing circuit refraining from receiving data on a communication channel associated with the first frequency band between a start time of the legacy measurement gap and an end time of the legacy measurement gap; Configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at a start time of the legacy measurement gap; Subject matter includes performing, after a start time of the legacy measurement gap, second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain.

[0135] In Example 10, the subject matter of Examples 1-9 includes a transceiver circuit coupled to the processing circuit and one or more antennas coupled to the transceiver circuit.

[0136] Example 11 is a computer-readable storage medium storing instructions for execution by one or more processors of a base station associated with a first cell, the instructions comprising: The instruction is to the base station: encoding first configuration signaling for transmission to a user equipment (UE), wherein the first configuration signaling is transmitted on a communication channel associated with the first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for a second frequency band; encoding second configuration signaling for transmission to the UE, where the second configuration signaling is for configuring a legacy measurement gap for the third frequency band, wherein the NCSG measurement gap and the legacy measurement gap at least partially overlap; Decode a first cell measurement and a second cell measurement of a second cell, where the first cell measurement is performed during an NCSG measurement gap and the second cell measurement is performed during a legacy measurement gap. The present invention is a computer-readable storage medium for causing a computer to perform operations including:

[0137] In Example 12, the subject matter of Example 11 includes subject matter where the NCSG measurement gap and the legacy measurement gap overlap, and the start time of the legacy measurement gap is after the start time of the NCSG measurement gap.

[0138] Example 13 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions comprising: The instructions configure a UE for measurements during a simultaneous measurement gap in a fifth generation new radio (5G NR) network, and instruct the UE to: decoding first configuration signaling received from a base station associated with the first cell, where the first configuration signaling is received on a communication channel associated with the first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for the second frequency band; decoding second configuration signaling received from the base station, where the second configuration signaling is for configuring a legacy measurement gap for a third frequency band; Detecting overlap between NCSG measurement gaps and legacy measurement gaps; performing a first cell measurement of the second cell in the second frequency band during the NCSG measurement gap and a second cell measurement of the second cell in the third frequency band during the legacy measurement gap based on the overlap; Encoding the first cell measurement and the second cell measurement for transmission to a base station The present invention is a computer-readable storage medium for causing a computer to perform operations including:

[0139] In Example 14, the subject matter of Example 13 includes subject matter where the NCSG measurement gap and the legacy measurement gap overlap, and the start time of the legacy measurement gap is after the start time of the NCSG measurement gap.

[0140] In Example 15, the subject matter of Example 14 includes operations further including decoding data received on a communication channel associated with the first frequency band between a start time of the NCSG measurement gap and a start time of the legacy measurement gap.

[0141] In Example 16, the subject matter of Example 15 includes operations further including configuring a radio frequency (RF) chain of the UE to retune from the first frequency band to a third frequency band at a start time of the legacy measurement gap, and performing second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain after the start time of the legacy measurement gap.

[0142] In Example 17, the subject matter of Examples 13-16 includes subject matter where the start time and end time of the legacy measurement gap are within the NCSG measurement gap.

[0143] In Example 18, the subject matter of Example 17 includes operations further including decoding data received on a communication channel associated with the first frequency band between a start time of the NCSG measurement gap and a start time of the legacy measurement gap, and between an end time of the legacy measurement gap and an end time of the NCSG measurement gap.

[0144] In Example 19, the subject matter of Example 18 configures retuning a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at a start time of the legacy measurement gap; The method further includes performing, after a start time of the legacy measurement gap, second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain.

[0145] In Example 20, the subject matter of Examples 13-19 includes subject matter wherein the start time and end time of the NCSG measurement gap are within the legacy measurement gap; The operation includes refraining from receiving data on a communication channel associated with the first frequency band between a start time of the legacy measurement gap and an end time of the legacy measurement gap; Configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at a start time of the legacy measurement gap; The method further includes, after a start time of the legacy measurement gap, performing second cell measurements of the second cell in the third frequency band during the legacy measurement gap using the RF chain.

[0146] Example 21 is at least one machine-readable medium containing instructions that, when executed by a processing circuit, cause the processing circuit to perform acts to implement any of Examples 1-20.

[0147] Example 22 is an apparatus including means for carrying out any of Examples 1 to 20.

[0148] Example 23 is a system that implements any of Examples 1 to 20.

[0149] Example 24 is a method for carrying out any of Examples 1 to 20.

[0150] While the embodiments have been described with reference to certain exemplary embodiments, it will be apparent 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. This detailed description is therefore not to be taken in a limiting sense, and the scope of the various embodiments is defined solely by the appended claims, along with the full range of equivalents to which such claims are entitled.

Claims

1. 1. An apparatus for user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, comprising: to configure the UE for measurements during a simultaneous measurement gap, decoding first configuration signaling received from a base station associated with a first cell, wherein the first configuration signaling is received on a communication channel associated with a first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for a second frequency band; decoding second configuration signaling received from the base station, wherein the second configuration signaling is for configuring a legacy measurement gap for a third frequency band; Detecting an overlap between the NCSG measurement gap and the legacy measurement gap; performing a first cell measurement of a second cell on the second frequency band during the NCSG measurement gap and a second cell measurement of the second cell on the third frequency band during the legacy measurement gap based on the overlap; a processing circuit for encoding the first cell measurement and the second cell measurement for transmission to the base station; a memory coupled to the processing circuit and configured to store the first configuration signaling and the second configuration signaling; An apparatus comprising:

2. The apparatus of claim 1 , wherein the NCSG measurement gap and the legacy measurement gap partially overlap, and a start time of the legacy measurement gap is after a start time of the NCSG measurement gap.

3. The processing circuitry 3. The apparatus of claim 2, further comprising: decoding data received on the communication channel associated with the first frequency band between the start time of the NCSG measurement gap and the start time of the legacy measurement gap.

4. The processing circuitry configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 4. The apparatus of claim 3, further comprising: after the start time of the legacy measurement gap, performing the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

5. The apparatus of claim 1 , wherein the start time and end time of the legacy measurement gap are within the NCSG measurement gap.

6. The processing circuitry 6. The apparatus of claim 5, wherein the apparatus is configured to decode data received on the communication channel associated with the first frequency band between a start time of the NCSG measurement gap and the start time of the legacy measurement gap, and between an end time of the legacy measurement gap and the end time of the NCSG measurement gap.

7. The processing circuitry configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 7. The apparatus of claim 6, further comprising: after the start time of the legacy measurement gap, performing the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

8. The apparatus of claim 1 , wherein the start and end times of the NCSG measurement gap are within the legacy measurement gap.

9. The processing circuitry refraining from receiving data on the communication channel associated with the first frequency band between a start time of the legacy measurement gap and an end time of the legacy measurement gap; configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 9. The apparatus of claim 8, further comprising: after the start time of the legacy measurement gap, performing the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

10. a transceiver circuit coupled to the processing circuit; one or more antennas coupled to the transceiver circuitry; 10. The apparatus of claim 1, further comprising:

11. 1. A computer program comprising instructions for execution by one or more processors of a base station associated with a first cell, the computer program comprising: The instructions include: encoding first configuration signaling for transmission to a user equipment (UE), wherein the first configuration signaling is transmitted on a communication channel associated with a first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for a second frequency band; encoding second configuration signaling for transmission to the UE, wherein the second configuration signaling is for configuring a legacy measurement gap for a third frequency band, wherein the NCSG measurement gap and the legacy measurement gap at least partially overlap; decoding a first cell measurement and a second cell measurement of a second cell, where the first cell measurement is performed during the NCSG measurement gap and the second cell measurement is performed during the legacy measurement gap; A computer program that causes a computer to perform operations including:

12. The computer program product of claim 11 , wherein the NCSG measurement gap and the legacy measurement gap partially overlap, and a start time of the legacy measurement gap is after a start time of the NCSG measurement gap.

13. 1. A computer program comprising instructions for execution by one or more processors of a user equipment (UE), comprising: The instructions configure a UE for measurements during a simultaneous measurement gap in a fifth generation new radio (5G NR) network; The UE, decoding first configuration signaling received from a base station associated with a first cell, wherein the first configuration signaling is received on a communication channel associated with a first frequency band, the first configuration signaling being for configuring a network controlled small gap (NCSG) measurement gap for a second frequency band; decoding second configuration signaling received from the base station, wherein the second configuration signaling is for configuring a legacy measurement gap for a third frequency band; Detecting an overlap between the NCSG measurement gap and the legacy measurement gap; performing a first cell measurement of a second cell on the second frequency band during the NCSG measurement gap and a second cell measurement of the second cell on the third frequency band during the legacy measurement gap based on the overlap; encoding the first cell measurement and the second cell measurement for transmission to the base station; A computer program that causes a computer to perform operations including:

14. The computer program product of claim 13 , wherein the NCSG measurement gap and the legacy measurement gap partially overlap, and a start time of the legacy measurement gap is after a start time of the NCSG measurement gap.

15. The operation is 15. The computer program product of claim 14, further comprising decoding data received on the communication channel associated with the first frequency band between the start time of the NCSG measurement gap and the start time of the legacy measurement gap.

16. The operation is configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 16. The computer program product of claim 15, further comprising: performing, after the start time of the legacy measurement gap, the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

17. The computer program product of claim 13 , wherein the start time and end time of the legacy measurement gap are within the NCSG measurement gap.

18. The operation is 20. The computer program product of claim 17, further comprising decoding data received on the communication channel associated with the first frequency band between a start time of the NCSG measurement gap and the start time of the legacy measurement gap, and between an end time of the legacy measurement gap and the end time of the NCSG measurement gap.

19. configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 20. The computer program product of claim 18, further comprising: performing, after the start time of the legacy measurement gap, the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

20. the start time and end time of the NCSG measurement gap are within the legacy measurement gap; The operation is refraining from receiving data on the communication channel associated with the first frequency band between a start time of the legacy measurement gap and an end time of the legacy measurement gap; configuring a retuning of a radio frequency (RF) chain of the UE from the first frequency band to the third frequency band at the start time of the legacy measurement gap; 14. The computer program product of claim 13, further comprising: performing, after the start time of the legacy measurement gap, the second cell measurements for the second cell in the third frequency band during the legacy measurement gap using the RF chain.

21. A computer-readable storage medium storing the computer program according to claim 11 or 12.

22. A computer-readable storage medium storing a computer program according to any one of claims 13 to 20.

Images