Temporary UE Capability Restriction for Simultaneous Network Connections

Abstract

A computer-readable storage medium stores instructions executed by one or more processors of a UE to configure the UE to simultaneously connect to a 5G NR network and at least a second network and cause the UE to operate. The operation includes procedures for encoding UE capability information for transmission to a base station. The UE capability information indicates that the UE supports MUSIM operation. First RRC signaling received from the base station includes a plurality of MUSIM configurations for configuring the UE for MUSIM operation. Interference is detected between at least one of the plurality of MUSIM configurations and the operation of the UE on at least the second network. Second RRC signaling is transmitted indicating a temporary UE capability restriction based on the interference.

Description

Technical Field

[0001] Priority Claim This application claims the benefit of priority under the following patent applications.

[0002] U.S. Provisional Patent Application No. 63 / 393,028, filed on July 28, 2022, entitled "TEMPORARY UE CAPABILITY RESTRICTION FOR SIMULTANEOUS CONNECTION TO 2 OR MORE NETWORKS";

[0003] U.S. Provisional Patent Application No. 63 / 393,745, filed on July 29, 2022, entitled "ENHANCED FREQUENCY DIVISION MULTIPLEXING (FDM) SOLUTION FOR IN-DEVICE COEXISTENCE"; and

[0004] U.S. Provisional Patent Application No. 63 / 483,490, filed on February 6, 2023, entitled "TEMPORARY UE CAPABILITY RESTRICTION FOR SIMULTANEOUS CONNECTION TO 2 OR MORE NETWORKS"

[0005] Each of the applications listed above is hereby incorporated by reference in its entirety.

[0006] [Technical Field] Aspects relate to wireless communications. Some aspects relate to wireless networks, including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-Advanced (LTE-A) networks, (MuLTEFire, LTE-U), and 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, fifth-generation (5G) networks, including 5G NR unlicensed spectrum (NR-U) networks, and other unlicensed networks, including Wi-Fi, CBRS (OnGo), etc. Other aspects are directed to techniques for temporary restriction of user equipment (UE) capability to simultaneously connect to two or more networks. Further aspects are directed to enhanced frequency-division multiplexing (FDM) solutions for in-device coexistence. [Background technology]

[0007] Mobile communication has evolved significantly from the early voice systems to today's highly sophisticated integrated communication platforms. With the increasing number of different types of devices communicating with various network devices, the use of 3GPP LTE systems is on the rise. The penetration of mobile devices (user equipment or UE) in modern society has continuously driven the demand for diverse networked devices in many heterogeneous environments. The fifth-generation (5G) wireless system is about to arrive soon and is expected to enable even greater speed, connectivity, and utility. The next-generation 5G network (or NR network) is expected to increase throughput, coverage, and robustness while reducing latency and operating and capital expenditures. The 5G-NR network 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 connection solutions that provide fast and abundant content and services. Due to the saturation of current cellular network frequencies, higher frequencies such as millimeter wave (mmWave) frequencies can be beneficial due to their high bandwidth.

[0008] Potential LTE operations in unlicensed spectrum include (but are not limited to) LTE operations in unlicensed spectrum via dual connectivity (DC) or DC-based LAA, and stand-alone LTE systems in unlicensed spectrum called MulteFire where LTE-based technologies operate only in unlicensed spectrum without requiring an "anchor" in licensed spectrum. Further enhanced operations of LTE and NR systems in both licensed and unlicensed spectrum are expected in future releases and 5G systems. Such enhanced operations can include techniques for simultaneous connection to two or more networks, techniques for temporary UE capability limitations, and enhanced FDM solutions for in-device coexistence.

Brief Description of the Drawings

[0009] In the several figures, these are not necessarily drawn to scale, but like reference numerals can describe like components in different figures. Like reference numerals with different subscripts can represent different examples of like components. The figures generally show, as examples and not as limitations, the various aspects considered in this specification.

[0010]

Figure 1A

[0011]

Figure 1B

Figure 1C

[0012]

Figure 2

Figure 3

Figure 4

[0013]

Figure 5

[0014]

Figure 6

[0015]

Figure 7

[0016]

Figure 8

[0017]

Figure 9

[0018]

Figure 10

[0019]

Figure 11

[0020] The following description and drawings sufficiently illustrate aspects to enable one skilled in the art to practice them. Other aspects may incorporate structural, logical, electrical, process, and other changes. Portions and features of some aspects may be included in, or substituted for, those of other aspects. Aspects outlined in the claims encompass all available equivalents of those claims.

[0021] 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, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0022] Any wireless link described herein (such as that used in communication network 140A or any other illustrated network) may operate in accordance with any exemplary wireless communication technology and / or standard.

[0023] LTE and LTE-Advanced are standards for wireless communication of high-speed data for UEs such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation, accordingly, can carry communications for a single UE using multiple carrier signals operating at different frequencies, thus increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used when one or more component carriers operate in unlicensed frequencies.

[0024] Aspects described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum (license) shared spectrum (e.g., 2.3 - 2.4 GHz, 3.4 - 3.6 GHz, 3.6 - 3.8 GHz, and Licensed Shared Access (LSA) at further frequencies, and Spectrum Access System (SAS) at 3.55 - 3.7 GHz and further frequencies).

[0025] Aspects described herein may also be applicable to different single carriers or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multi-carrier (FBMC), OFDMA, etc.), particularly 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0026] In some aspects, either UE101 and UE102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE that includes a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some aspects, either UE101 and UE102 may include a NarrowBand (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE, etc.). The IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based service (ProSe), or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC exchange of data can be an exchange of data initiated by a machine. The IoT network includes interconnecting IoT UEs (within the Internet infrastructure) that can include uniquely identifiable embedded computing devices with short-lived connections. The IoT UE can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connection to the IoT network.

[0027] In some aspects, either UE101 and UE102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0028] UE101 and UE102 may be configured to be communicatively coupled, for example, to connect to a radio access network (RAN) 110. The RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. UE101 and UE102 each utilize connections 103 and 104, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are illustrated as air interfaces for enabling a communication coupling and may be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM (registered trademark)) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a Push-to-Talk over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5th Generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0029] In one aspect, UE101 and UE102 may further directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface including 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).

[0030] UE102 is shown as being configured to access an access point (AP) 106 via a connection 107. The connection 107 can include, for example, a local wireless connection such as a connection compliant with any IEEE802.11 protocol, whereby the AP106 can include a Wireless Fidelity (WiFi (registered trademark)) router. In this example, the AP106 is shown as being connected to the Internet without being connected to the core network of the wireless system (to be described in more detail below).

[0031] RAN 110 may include one or more access nodes that enable connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), NodeB, evolved NodeB (eNB), Next Generation NodeB (gNB), and RAN network nodes, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). In some embodiments, communication nodes 111 and 112 may be transmission / reception points (TRP). When communication nodes 111 and 112 are NodeB (e.g., eNB or gNB), one or more TRP can function within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes for providing macro cells, such as macro RAN nodes, and one or more RAN nodes for providing femto cells or pico cells (e.g., cells with a smaller coverage area, smaller user capacity, or higher bandwidth compared to macro cells), such as low power (LP) RAN nodes or unlicensed spectrum-based secondary RAN nodes.

[0032] Either of communication nodes 111 and 112 may terminate the air interface protocol and may be the first contact points for UEs 101 and 102. In some embodiments, either of communication nodes 111 and 112 may implement various logical functions for RAN 110, including but not limited to radio bearer management, uplink, and downlink dynamic radio resource management and data packet scheduling, and mobility management, etc., which are functions of a radio network controller (RNC). In an example, either of 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.

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

[0034] In this aspect, 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. MME 121 can be functionally similar to the control plane of a legacy serving general packet radio service (GPRS) support node (SGSN). MME 121 can manage access mobility aspects such as gateway selection and tracking area list management. HSS 124 can include a database of network users that contains subscription-related information to support the processing of communication sessions of network entities. CN 120 can include one or several HSSs 124 depending on, for example, the number of mobile subscribers, the capacity of the devices, the network configuration, etc. For example, HSS 124 can provide support for routing / roaming, authentication, authorization, name / address resolution, location dependency, etc.

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

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

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

[0038] In some aspects, the communication network 140A can 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) spectrums. One of the current enablers of IoT is NarrowBand IoT (NB-IoT).

[0039] The NG system architecture can include the RAN 110 and the 5G core network (e.g., CN 120). The RAN 110 in the NG system can be referred to as the NG-RAN. The RAN 110 can include multiple nodes such as gNBs and ng-eNBs. The CN 120 (also referred to as the 5G core network or 5GC) can include an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via the NG interface. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by the NG-C interface and to the UPF by the NG-U interface. The gNBs and the NG-eNBs can be coupled to each other via the Xn interface.

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

[0041] Figure 1B shows a non-roaming 5G system architecture according to some embodiments. Referring to Figure 1B, a 5G system architecture 140B in reference point representation is shown. More specifically, the UE 102 can communicate with the RAN 110 and one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes a plurality of 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 a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include 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 depending on the desired service type.PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). UDM can be configured to store subscriber profiles and data (similar to HSS in a 4G communication system).

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

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

[0044] In some embodiments, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and multiple IP multimedia core network subsystem entities such as a Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF, which can operate as a Proxy CSCF (P-CSCF) 162BE, 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 the session state in the network, and the E-CSCF can be configured to handle specific aspects of an emergency session such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as a point of contact within the operator's network for all IMS connections destined for a subscriber of that network operator or a roaming subscriber currently located within the network operator's service area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170, for example, an IMS operated by a different network operator.

[0045] In some embodiments, the UDM / HSS 146 can be coupled to an Application Server (AS) 160B that can include a Telephony Application Server (TAS) or another AS. The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

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

[0047] FIG. 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated 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 can be service-based, and the interactions between network functions can be represented by the corresponding point-to-point reference points Ni or service-based interfaces.

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

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

[0050] Figure 2 shows network 200 according to various embodiments. Network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this regard, and the described embodiments may be applicable to other networks that benefit from the principles described herein, such as future 3GPP systems or the like.

[0051] Network 200 may include UE 202, which may include any mobile or non-mobile computing device designed to communicate with RAN 204 via an over-the-air connection. UE 202 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, in-vehicle infotainment, in-vehicle entertainment devices, instrument clusters, head-up display devices, on-board diagnostic devices, dash-top mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, network devices, machine type communication devices, M2M or D2D devices, IoT devices, etc.

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

[0053] In some embodiments, UE202 may further communicate with AP206 via an over-the-air connection. AP206 may manage a WLAN connection that may function to offload some / all network traffic from RAN204. The connection between UE202 and AP206 may be consistent with any IEEE802.11 protocol, where AP206 may be a Wireless Fidelity (Wi-Fi (R)) router. In some embodiments, UE202, RAN204, and AP206 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE202 configured by RAN204 to utilize both cellular radio resources and WLAN resources.

[0054] RAN204 may include one or more access nodes, e.g., access node (AN) 208. AN208 may terminate an air interface protocol for UE202 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this way, AN208 may enable a data / voice connection between core network (CN) 220 and UE202. In some embodiments, AN208 may be implemented in a discrete device or as one or more software entities running on a server computer, e.g., as part of a virtual network, that may be referred to as a Cloud RAN or virtual baseband unit pool. AN208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN208 may be a macrocell base station or low-power base station for providing a femtocell, picocell, or other similar cell having a coverage area smaller than, user capacity smaller than, or bandwidth higher than that of a macrocell.

[0055] In embodiments where RAN204 includes a plurality of ANs, they may be coupled to each other via an X2 interface or (if RAN204 is an LTE RAN) an Xn interface (if RAN204 is a 5G RAN). In some embodiments, the X2 / Xn interface that may be separated into a control / user plane interface may enable ANs to communicate information regarding handover, data / context transfer, mobility, load management, interference coordination, etc.

[0056] Each of the ANs of RAN204 may manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE202. UE202 may be simultaneously connected to a plurality of cells provided by the same or different ANs of RAN204. For example, UE202 and RAN204 may use carrier aggregation to enable UE202 to connect to a plurality of component carriers corresponding to a Pcell or SCell, respectively. 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 eNB, gNB, ng-eNB, etc.

[0057] RAN204 may provide an air interface on a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using a PCell / SCell. Before accessing the unlicensed spectrum, the node may perform media / carrier sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0058] In a V2X scenario, UE 202 or AN 208 can be, or operate as, a roadside unit (RSU) that can refer to any transport infrastructure entity used for V2X communication. The RSU can be implemented in, or by, a suitable AN or a static (or relatively static) UE. The RSU implemented in or by the UE may be referred to as a "UE-type RSU", the eNB may be referred to as an "eNB-type RSU", the gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located roadside that provides connectivity support to passing vehicle UEs. The RSU may also include an internal data storage circuit for storing intersection map shapes, traffic statistics, and media, as well as applications / software for sensing and controlling the traffic of passing vehicles and pedestrians. The RSU can provide communication with very low latency, which is required for high-speed events such as collision avoidance and traffic warnings. Further, or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU may be packaged in an all-weather housing suitable for outdoor installation and may include a network interface controller that provides a wired connection (e.g., Ethernet (R)) to a traffic signal controller or a backhaul network.

[0059] In some embodiments, RAN204 may be an LTE RAN210 having an eNB, e.g., eNB212. The LTE RAN210 may provide an LTE air interface having the following features: a 15 kHz sub-carrier spacing (SCS); a CP-OFDM waveform for downlink (DL) and an SC-FDMA waveform for uplink (UL); a turbo code for data and a TBCC for control; etc. The LTE air interface may utilize 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 measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in a band below 6 GHz.

[0060] In some embodiments, RAN204 may be an NG-RAN214 having a gNB, e.g., gNB216, or an ng-eNB, e.g., ng-eNB218. The gNB216 may connect to 5G-capable UEs using a 5G NR interface. The gNB216 may connect to a 5G core through an NG interface that may include an N2 interface or an N3 interface. The ng-eNB218 may also connect to the 5G core through the NG interface, or may connect to UEs via the LTE air interface. The gNB216 and the ng-eNB218 may connect on the Xn interface.

[0061] In some embodiments, the NG interface that carries traffic data between nodes of the NG-RAN214 and the UPF248 may be split into two parts: an NG user plane (NG-U) interface (e.g., the N3 interface), and an NG control plane (NG-C) interface (e.g., the N2 interface), which is a signaling interface between nodes of the NG-RAN214 and the AMF244.

[0062] NG-RAN214 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM, and DFT-s-OFDM for UL; polar, convolutional, simplex, and Reed-Muller codes for control and LDPC for data. The 5G NR air interface may utilize CSI-RS, 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; and may use PTRS for tracking reference signals for phase tracking and time tracking of PDSCH. The 5G-NR air interface may operate in the FR1 band including bands below 6 GHz, or in the FR2 band including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include a Synchronization Signal and Physical Broadcast Channel (SS / PBCH) Block (SSB), which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0063] In some embodiments, the 5G-NR air interface may utilize Bandwidth Parts (BWPs) for various purposes. For example, a BWP may be used for dynamic application of SCS. For example, UE202 may be configured using multiple BWPs with different SCS for each BWP configuration. When a change in the BWP is indicated to UE202, the SCS for transmission also changes. Another use case of BWPs is related to power saving. In particular, multiple BWPs may be configured for UE202 having different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. A BWP with a smaller number of PRBs can be used for data transmission with low traffic load, enabling power saving in UE202 and in some cases in gNB216. A BWP with a larger number of PRBs can be used in scenarios with higher traffic load.

[0064] RAN 204 may be communicatively coupled to a CN 220 that includes network elements that provide various functions for supporting data and telephone communication services to a customer / subscriber (e.g., a user of the UE 202). Components of the CN 220 may be implemented in one physical node or 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 on physical computing / storage resources in servers, switches, etc. The logical instantiation of the CN 220 may be referred to as a network slice, and the logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice.

[0065] In some embodiments, the CN 220 may be connected to an LTE radio network as part of an Enhanced Packet System (EPS) 222, which may also be referred to as an 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 to each other on the interfaces (or “reference points”) as shown. The functions of the elements of the EPC 222 may be briefly described below.

[0066] The MME 224 may implement a mobility management function for tracking the current location of the UE 202 and facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0067] 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 a local mobility anchor point for inter-RAN node handover and may also provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and any policy enforcement.

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

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

[0070] The PGW 232 can terminate the SGi interface towards the data network (DN) 236 which may include the application / content server 238. The PGW 232 can route data packets between the LTE CN and the data network 236. The PGW 232 can be coupled to the SGW 226 via the S5 reference point, facilitating user plane tunneling and tunnel management. The PGW 232 may further include nodes for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point between the PGW 232 and the data network 236 can be for the provisioning of public, private PDNs external to the operator, or inter-operator packet data networks, e.g., IMS services. The PGW 232 can be coupled to the PCRF 234 via the Gx reference point.

[0071] PCRF 234 is the policy and charging control element of CN 220. PCRF 234 can be communicatively coupled to the application / content server 238 to determine appropriate QoS and charging parameters for the service flow. PCRF 234 can provision the relevant rules to the PCEF (via the Gx reference point) using appropriate TFT and QCI.

[0072] In some embodiments, CN 220 can be 5GC 240. 5GC 240 can include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260, which are coupled to each other on the interfaces (or "reference points") as shown. The functions of the elements of 5GC 240 can be briefly described below.

[0073] AUSF 242 can store data for the authentication of UE 202 and process authentication-related functions. AUSF 242 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 240 on the reference points as shown, AUSF 242 can present an Nausf service-based interface.

[0074] The AMF 244 may enable other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and subscribe to notifications about mobility events related to the UE 202. The AMF 244 may be responsible for registration management (e.g., registration of the UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 244 may provide transport for SM messages between the UE 202 and the SMF 246 and act as a transparent proxy for routing SM messages. The AMF 244 may also provide transport for 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. Furthermore, 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; the AMF 244 is 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.

[0075] The SMF 246 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 248 and the AN 208); UE IP address allocation and management (including any authorization); selection and control of the UP function; configuration of traffic steering in the UPF 248 to route traffic to the appropriate destination; termination of the interface towards the policy control function; control of policy enforcement, charging, and parts of QoS; lawful interception (for SM events, and the 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 via the AMF 244 to the AN 208; 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.

[0076] UPF 248 can act as an anchor point for RAT - internal and RAT - inter mobility, an external PDU session point for the interconnection with the data network 236, and a branching point for supporting multi - home PDU sessions. UPF 248 also performs packet routing and forwarding, performs packet inspection, enforces the user - plane part of policy rules, lawfully intercepts packets (UP set), performs traffic utilization reporting, performs QoS processing for the user - plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs uplink traffic verification (e.g., SDF - QoS flow mapping), transports level packet marking in the uplink and downlink, and may perform downlink packet buffering and downlink data notification triggering. UPF 248 may include an uplink classifier for supporting routing traffic flows to the data network.

[0077] NSSF 250 can select a set of network slice instances that provide services to UE 202. NSSF 250 can also determine the permitted NSSAI and, if necessary, determine the mapping for the subscribed S - NSSAI. NSSF 250 can also, based on a suitable configuration, optionally query NRF 254 to determine a list of AMF sets or candidate AMFs used to serve UE 202. The selection of the set of network slice instances for UE 202 can be triggered by AMF 244, which interacts with NSSF 250 to register UE 202, which may result in a change of AMF. NSSF 250 can interact with AMF 244 via the N22 reference point and communicate with another NSSF in the visited network via an N31 reference point (not shown). Further, NSSF 250 can present an Nnssf service - based interface.

[0078] NEF252 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re - exposure, AF (e.g., AF260), edge computing or fog computing systems. In such embodiments, NEF252 can authenticate, authorize, or throttle the AF. NEF252 can also transform information exchanged with the AF260 and information exchanged with internal network functions. For example, NEF252 can transform between AF service identifiers and internal 5GC information. NEF252 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be stored in NEF252 as structured data or in a data storage NF using a standardized interface. The stored information can then be re - exposed by NEF252 to other NFs and AFs or used for other purposes such as analysis. Additionally, NEF252 can present an Nnef service - based interface.

[0079] NRF254 can support a service discovery function, receive NF discovery requests from NF instances, and provide information about discovered NF instances to the NF instances. NRF254 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object that can occur during the execution of program code. Additionally, NRF254 can present an Nnrf service - based interface.

[0080] The PCF256 may provide and enforce policy rules for control plane functions and may also support an integrated policy framework for controlling network behavior. The PCF256 may also implement a front end for accessing subscription information related to policy decisions in the UDR of the UDM258. In addition to communicating with functional entities at the reference points as shown, the PCF256 presents an Npcf service-based interface.

[0081] The UDM258 may process subscription-related information to support the processing of communication sessions by network entities and may store the subscription data of the UE202. For example, the subscription data may be communicated via the N8 reference point between the UDM258 and the AMF244. The UDM258 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM258 and the PCF256, and / or structured data and application data for exposure for the NEF252 (including PFDs for application detection and application request information for multiple UEs). The Nudr service-based interface may be presented by the UDR, enabling the UDM258, the PCF256, and the NEF252 to access a specific set of stored data and read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE, which is responsible for processing such as certificate handling, location management, and subscription management. 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 certificate handling, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through the reference points as shown, the UDM258 may present an Nudm service-based interface.

[0082] AF260 can provide application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0083] In some embodiments, 5GC240 can enable edge computing by selecting operator / third-party services that are geographically closer to the point where UE202 is connected to the network. This can reduce latency and load on the network. To provide an edge computing implementation, 5GC240 can select a UPF248 close to UE202 and perform traffic steering from UPF248 to data network 236 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF260. In this way, AF260 can influence UPF (re)selection and traffic routing. Based on the operator's deployment, when AF260 is considered a trusted entity, the network operator can permit AF260 to directly interact with the relevant NF. Further, AF260 can present a Naf service-based interface.

[0084] Data network 236 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers including, for example, application / content server 238.

[0085] In some aspects, 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 in a different type of node. In some embodiments, LMF 245 is configured to receive measurement and assistance information from NG-RAN 214 and UE 202 via AMF 244 (e.g., using the NL interface) for calculating the position of the UE. In some embodiments, the NR Positioning Protocol A (NRPPa) protocol can be used to carry positioning information between NG-RAN 214 and LMF 245 on the Next Generation Control Plane Interface (NG-C). In some embodiments, LMF 245 configures UE 202 using the LTE Positioning Protocol (LPP) (e.g., an LPP-based communication link) via AMF 244. In some aspects, NG-RAN 214 configures UE 202, for example, on the LTE-Uu and NR-Uu interfaces, using, for example, Radio Resource Control (RRC) protocol signaling. In some aspects, UE 202 communicates with ng-eNB 218 using the LTE-Uu interface and communicates with gNB 216 using the NR-Uu interface. In some aspects, ng-eNB 216 and gNB 216 communicate with AMF 244 using the NG-C interface.

[0086] In some embodiments, the following reference signals: the NR Positioning Reference Signal (NR PRS) in the downlink and the Sounding Reference Signal (SRS) for positioning in the uplink can be used to achieve positioning measurements in the NR communication network. 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 on multiple symbols that can be aggregated to accumulate power.

[0087] Figure 3 schematically shows a wireless network 300 according to various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 are similar to and may be substantially interchangeable with similarly named components described elsewhere in this specification.

[0088] The UE 302 may be communicatively coupled to the AN 304 via a connection 306. The connection 306 is illustrated as an air interface to enable a communication coupling and may be consistent with a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at millimeter wave or frequencies below 6 GHz.

[0089] 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 that are sources / sinks of application data. The application processing circuit 312 may further implement one or more layer operations and transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

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

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

[0092] The modem platform 310 may further include a transmission circuit 318, a reception circuit 320, an RF circuit 322, and an RF front end (RFFE) 324 that may include or be connected to one or more antenna panels 326. Briefly, the transmission circuit 318 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc., the reception circuit 320 may include an analog-to-digital converter, a mixer, an IF component, etc., the RF circuit 322 may include a low-noise amplifier, a power amplifier, a power tracking component, 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 components of the transmission circuit configuration 318, the reception circuit configuration 320, the RF circuit configuration 322, the RFFE 324, and one or more antenna panels 326 (generally referred to as "transmission / reception components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, whether it is millimeter wave or a frequency below 6 GHz, etc. In some embodiments, the transmission / reception components may be arranged in a plurality of parallel transmission / reception chains and may be disposed on the same or different chips / modules, etc.

[0093] In some embodiments, the protocol processing circuit 314 may include one or more instances of a control circuit (not shown) that provides control functions for the transmission / reception components.

[0094] UE reception may be established by and through one or more antenna panels 326, the RFFE 324, the RF circuit configuration 322, the reception circuit configuration 320, the digital baseband circuit configuration 316, and the protocol processing circuit configuration 314. In some embodiments, one or more antenna panels 326 may receive transmissions from AN304 by reception beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 326.

[0095] UE transmission can be established by and through a protocol processing circuit configuration 314, a digital baseband circuit configuration 316, a transmission circuit configuration 318, an RF circuit configuration 322, an RFFE 324, and one or more antenna panels 326. In some embodiments, the transmission components of UE 302 can apply a spatial filter to the data being transmitted to form a transmission beam radiated by the antenna elements of one or more antenna panels 326.

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

[0097] FIG. 4 is a block diagram showing components according to some exemplary embodiments capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methodologies discussed herein. Specifically, FIG. 4 shows a graphical representation of a hardware resource 400 that can include 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 can be communicatively coupled via a bus 440 or other interface circuit. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 402 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resource 400.

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

[0099] 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 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., but is not limited thereto.

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

[0101] Command 450 may include other executable code for causing software, a program, an application, an applet, an app, or one or more of the methodologies contemplated herein to be executed by at least any one of one or more processors 410. Command 450 may be present in at least one of one or more processors 410, memory / storage device 420, or any suitable combination thereof (e.g., within a processor, in cache memory), in whole or in part. Further, any portion of Command 450 may be transmitted from one or more peripheral devices 404 or any combination of one or more databases 406 to hardware resource 400. Accordingly, the memory of one or more processors 410, memory / storage device 420, one or more peripheral devices 404, and one or more databases 406 are examples of computer-readable and machine-readable media.

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

[0103] The term "application" may refer to a complete and deployable package or an environment for realizing specific functions in an operating environment. Terms such as "AI / ML application" can be applications that include some artificial intelligence (AI) / machine learning (ML) model and application-level descriptions. In some embodiments, the AI / ML application can be used to construct or implement one or more of the disclosed aspects.

[0104] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models that perform specific tasks relying on patterns and inferences instead of using explicit instructions. The ML algorithm builds or infers a mathematical model (referred to as an "ML model") based on sample data (referred to as "training data" or "model training information") and makes predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience regarding some task and some performance metric, and an ML model can be any object or data structure created after the ML algorithm is trained with one or more training data sets. After training, the ML model can be used to make predictions on new data sets. The term "ML algorithm" refers to a different concept from the term "ML model", but these terms considered in this specification can be used interchangeably in the present disclosure.

[0105] Terms such as "machine learning model" or "ML model" may also refer to concepts used by ML methods and ML support solutions. An "ML support solution" is a solution that uses an ML algorithm during operation to address a specific use case. An ML model includes supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithm, support vector machine, Bayesian algorithm, ensemble algorithm, 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.), and neural networks. Depending on the implementation, a specific ML model may have many submodels as components, and the ML model may train all the submodels together. Individually trained ML models can also be combined together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, functions, or functional entities specific to an ML support solution, and the ML pipeline may include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or several data sources in an actor. An "actor" is an entity that hosts an ML support solution using the output of an 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 the inference mode (which includes 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 determines an action (an "action" is executed by the actor as a result of the output of the ML support solution). The term "model inference information" refers to information used as input to an ML model to determine an inference. The data used to train an ML model and the data used to determine an inference may overlap. However, "training data" and "inference data" refer to different concepts.

[0106] In Rel-15 / 16, the coordination between network (NW) A and NW B is left to the UE implementation, while in Rel-17, the coordination between NW A and B is performed via NW A in response to a gap request from the UE, or by entering the idle mode in NW A.

[0107] 3GPP supports in Rel-18 that a multi-universal subscriber identity module (MUSIM) device operates in the RRC-connected state simultaneously in two networks. In some aspects, the following configurations may be used by the disclosed techniques.

[0108] (a) Specify a mechanism for indicating preferences for temporary UE capability restrictions and releases (e.g., capability updates, cell releases, (de)activation of configured resources) using NW A when the UE requires transmission or reception for MUSIM purposes (e.g., initiation / stop of connection to NW B).

[0109] (a.1) Radio Access Technology (RAT) simultaneity: Network A is NR SA or NR DC (using CA). Network B can be either LTE or NR.

[0110] (a.2) Applicable UE architecture: Dual RX / dual TX UE.

[0111] The disclosed techniques include a mechanism for indicating preferences for temporary UE capability restrictions and releases.

[0112] In the Rel-16 power saving indication and overheat indication, the UE may not be able to specifically indicate the component carrier, or SCell, or the corresponding bandwidth, and / or MIMO layer to be restricted. Therefore, the network may not be able to provide the UE with a temporary UE capability restriction for the purpose of MUSIM described in this specification without applying the correct restriction.

[0113] In some aspects, the disclosed technology may include the stage of specifically indicating the component carriers and SCell that the UE needs to temporarily restrict in NW A in order to meet the requirements for establishing and maintaining services in NW B while the UE is in the RRC connected mode in both NW A and NW B and while the static UE radio capabilities are kept unchanged in both NW A and NW B. Further, the network can also configure the number of CCs that can be restricted / reduced, the number of MIMO layers of each CC, and the limits for the bandwidth.

[0114] Since the UE specifically indicates the component carriers and SCell for the temporary UE capability restriction, the network can enforce the restriction and the UE can use its UE capabilities for NW B. UE assistance information

[0115] In some embodiments, for the temporary UE capability restriction, any of the following information may be provided in the indication from the UE to the network.

[0116] (a) FrequencyInfoDL (SCS-SpecificCarrier, absoluteFrequencyPointA, FreqBandIndicatorNRs) for the DL CC that is no longer possible or, if still possible, the corresponding number of MIMO layers needs to be reduced or only the bandwidth position is restricted for FrequencyInfoDL.

[0117] (b) If not possible anymore, or if still possible, whether the corresponding number of MIMO layers needs to be reduced or the bandwidth position for FrequencyInfoDL is only restricted for the DL CC, FrequencyInfoUL(SCS-SpecificCarrier, absoluteFrequencyPointA, FreqBandIndicatorNRs).

[0118] (c) If the CC is already configured, in order to indicate the following, SCellIndex may be provided instead of the DL / UL CC:

[0119] (c.1) Whether DL or UL or both are not possible anymore; and

[0120] (c.2) Whether DL or UL or both are still possible (e.g., indicating that the corresponding number of MIMO layers needs to be reduced or the bandwidth position for FrequencyInfoDL is restricted).

[0121] (d) Which band is restricted.

[0122] (e) No restriction.

[0123] In some embodiments, the UE provides all restrictions to the network. In addition to simply indicating bands that are no longer available to the UE's network, the capability restrictions can also include corresponding combinations of bands that are no longer available. In another embodiment, the network infers / calculates restrictions on the list of combinations of bands from the previously provided UE capabilities based on the capability restrictions of the bands signaled by the UE that are no longer available. UE Assistance Information (UAI) Format

[0124] The above information may be transmitted in an RRC message or in a new RRC message as part of the RRC UE assistance information.

[0125] Figure 5 shows an exemplary ASN500 that constitutes an indication in RRC signaling as part of the UE assistance information according to some aspects.

[0126] Figure 6 shows an exemplary ASN600 that constitutes an indication in RRC signaling as part of the UE assistance information according to some aspects.

[0127] If there is a restriction on a CC that is not currently configured but may potentially be configured in the future, NW A has not used it yet, and the UE can use it for NW B just before the signaling in network A is completed. In terms of latency, it may be sufficient to provide that restriction to that CC using an RRC message.

[0128] However, if the CC is configured (i.e., already configured as an SCell), although the use of RRC is still possible as discussed above, it may be necessary to indicate it to the network more quickly so that it can be used promptly by the UE connection to NW B. In this case, an indication in MAC signaling (i.e., a MAC CE) may be used. An example of such a MAC CE is provided in Figure 7.

[0129] Figure 7 is a diagram of a MAC CE700 for indicating an SCell affected by a network (NW) (e.g., NW B) according to some aspects.

[0130] Figure 8 is a diagram of an exemplary message sequence 800 related to the disclosed technology according to some aspects.

[0131] Referring to FIG. 8, an exemplary message sequence chart is shown below in the following steps (also shown in FIG. 8).

[0132] Step 1. The UE enters the RRC connected state and provides UE capability information to the base station (including UE support for Rel-18 MUSIM) if requested by the network.

[0133] Step 2. If the UE supports Rel-18 MUSIM and the network also supports it, it may configure the UE in the Rel-18 MUSIM configuration (i.e., which of the restricted CCs and / or SCell and / or bands the UE is permitted to request, and / or the number of MIMO layers within the CC / SCell / band to be reduced, and / or the bandwidth and position of the CC / SCell band).

[0134] Step 3. If the connection at NW B requests UE configuration restrictions from NW A, the UE can indicate temporary UE capability restrictions by indicating that a particular configuration is not preferred based on the Rel-18 MUSIM configuration in Step 2.

[0135] Step 4. Upon receiving an indication from the UE, the network can perform either RRC reconfiguration for releasing SCell and / or reducing MIMO layers and / or reducing bandwidth, or L1 signaling via PDCCH for performing a BWP switch or MAC CE for deactivating SCell.

[0136] In some embodiments, steps 3 and 4 can be repeated while the UE is connected to NW A in RRC connected mode in response to a configuration change in network B. For example, if network B configures a different CC, this may impose further restrictions on the acceptable configurations from network A. This may be signaled towards network A, and network A may release its configuration. In some embodiments, step 3 can also indicate to the network that there are no restrictions (e.g., when the connection to NW B or a specific configuration has been released). The configuration in network B is asynchronous and unpredictable with respect to the procedures in network A (i.e., the UE has no prior knowledge of which configuration will be used when in network B), and thus a prohibition timer (a timer that prevents the UE from repeating the preference indication) cannot prevent the UE from requesting such a change.

[0137] In some embodiments, if a cell does not support Rel-18 MUSIM procedures, the UE can recognize this as network A does not provide a MUSIM configuration. In that case, the UE may not provide a preference to the network. The UE may use any implementation-specific method to connect to network B. This configuration can be any of the legacy procedures supported by the network, such as using overheat assistance information or autonomously releasing the connection to A. When the UE is handed over to a cell that does not support Rel-18 MUSIM, the MUSIM configuration from the previous cell is released. In this case, the UE behaves as mentioned above in a cell that does not support Rel-18 MUSIM.

[0138] In the case of a handover (HO) to a cell that supports Rel-18 MUSIM, the previously provided UE preference is transferred to the new cell and used by the new cell to provide / update / continue the current UE configuration.

[0139] When the UE becomes inactive or in the idle mode, any UE preference signaled is released by the network and the UE.

[0140] In some aspects, the number of UE Assistance Information indications (UAI), or any other form of UE feedback, may be limited.

[0141] In some embodiments, based on the number of restrictions that the UE can request for MUSIM or other purposes, the network can configure the UE. With the above information, the network can limit the maximum number of CCs that the UE can request from the network, the maximum number of reducible MIMO layers per CC, and the maximum bandwidth reduction per CC.

[0142] In some aspects, a UE that provides proactive UE assistance to NWA regarding the capabilities used by NWB may cause unnecessary signaling overhead to NWA, especially if the limitations of this capability indicated by the UE are not configured by NWA. In some aspects, the use of the same capabilities need not occur at the same time.

[0143] Another embodiment regarding limiting UAI or any other form of UE feedback is that in the configuration of UE assistance, or when the UE can infer it from the neighbor cell list of the SIB, or in either combination of these two, the network can optionally indicate to the UE the bands of interest (e.g., those that it can use to configure the UE). Due to the activity in NW B, if the UE needs to restrict these bands in network A, the UE can proactively provide UAI or other forms of UE feedback to notify network A of this restriction. For other bands (i.e., bands not included in the "bands of interest" by network A), the UE does not have to provide UAI or other forms of UE feedback. This limits the amount of signaling to network A because restrictions on uninteresting bands are not signaled.

[0144] In another embodiment, if the configuration of NW B restricts the use of these bands in network A, the UE does not have to proactively indicate the restriction of its capabilities for these bands. Instead, the UE indicates the restriction only when NW A attempts to configure a CC for the UE for these bands. When this occurs, the UE can reject NW A's attempt to configure a CC for these bands that are restricted due to the current configuration already being used by NW B. The UE can provide an indication of UE assistance information with the restriction to network A either in the rejection message itself or in a separate message via UAI or other forms of UE feedback. Scenarios for Capacity Limitation Requirement / UAI

[0145] In some aspects, it can be considered that the following scenarios may trigger some form of capacity limitation behavior.

[0146] (a) Scenario 1: The UE is connected to NW A and is starting a connection to NW B.

[0147] (b) Scenario 2: The UE has started connecting to NW A and is connected to NW B.

[0148] (c) Scenario 3: The UE is connected to both NW A and NW B.

[0149] Each of the above scenarios will be further considered below.

[0150] Scenario 1: The UE is connected to NW A and has started connecting to NW B. The following sub - scenarios can occur as shown in Table 1 below.

Table 1

[0151] Scenario 2: The UE has started connecting to NW A and is connected to NW B. The following sub - scenarios can occur as shown in Table 2 below.

Table 2

[0152] Scenario 3: The UE is connected to both NW A and NW B. The following sub - scenarios can occur as shown in Table 3 below.

Table 3

[0153] Based on the above analysis of Scenarios 1 - 3, possible actions regarding UAI can be listed as follows.

[0154] (a) The UE sends UAI post - reactively to the first network to indicate that the current configuration cannot be supported and to request a change in the current configuration. This can be due to receiving a configuration in the second network.

[0155] (b) The UE proactively sends a UAI to the first network to indicate that it has some capacity limitations that may affect future configurations in the first network. This may be due to receiving a configuration in the current configuration of the second network.

[0156] (c) The UE sends a UAI or a rejection message to the first network reactively to indicate that the configuration requested by the reconfiguration message in the first network cannot be supported. This may be due to the current configuration in the second network being incompatible with the received configuration in the first network.

[0157] (d) The UE sends a release / inability of CA and / or DC during a connection / resumption request to the first network. Next, the UE may continue to perform a complete capacity limitation (UAI) for the first network after security activation. Next, the first network may configure only CA / DC. This may be due to the configuration in the second network restricting the CA / DC configuration in the first network.

[0158] In some aspects, the UE may send a UAI reactively or proactively. A reactive approach may cause a delay in reconfiguration or increase the likelihood of reconfiguration rejection.

[0159] In some aspects, in any of the previous messages, the UE can indicate limitations on CA, DC, MIMO layers, bandwidth, etc.

[0160] One embodiment, such as in Scenario 2, can indicate CA / DC release / inability during a UE connection / resumption request to the network, such that the network can know that the UE capabilities may be limited, and thus can wait until the UE provides UE cap limitations before further reconfiguring the UE for higher throughput, e.g., via CA or SCG, MIMO layers, bandwidth, etc. Such an indication can be included in the RRC setup or resume request message, or the RRC setup or resume complete message.

[0161] In some aspects, the UE provides proactive UE assistance information regarding resources / capabilities not being used in a network (e.g., Network A), to avoid any future incompatible configurations by the network (i.e., Network A) where such resources / capabilities are used by another network (e.g., Network B). One major issue with the UE providing proactive UE assistance to NW A is that it can result in unnecessary signaling overhead to NW A, especially when the UE - indicated capability limitations are not (currently or in the future) configured by NW A. Another embodiment is that NW A can optionally be able to indicate to the UE explicitly or implicitly the bands of interest (e.g., the bands or CCs it can configure) (e.g., neighbor cell list in SIB, measurement objects). Due to activities in NW B, if the UE needs to restrict these bands in Network A, the UE proactively provides UAI or other forms of UE feedback to notify Network A of this restriction. For other bands (i.e., bands not included in the "bands of interest" by Network A), the UE does not provide UAI or other forms of UE feedback. This can limit the amount of signaling to Network A as restrictions on un - interested bands are not signaled.

[0162] In some embodiments, the disclosed technology may be based on providing UE assistance information to assist MUSIM and other purposes in order to enable a UE to connect to two or more networks simultaneously by providing capacity limitations.

[0163] In some aspects, the UE provides to network A, as UE assistance information, the band and / or DL frequency information and / or UL frequency information regarding a component carrier, and / or the bandwidth and the position of the bandwidth regarding a CC, and / or the number of MIMO layers affected by another network (e.g., network B).

[0164] In some aspects, upon receiving UE assistance information, network A avoids configuring the UE in a configuration related to the UE assistance information, or releasing and / or deactivating these configurations / resources.

[0165] In some aspects, when a configuration is no longer used by network B, the UE indicates the corresponding UE assistance to network A to release the limitation.

[0166] In some embodiments, as part of the configuration of UE assistance information, network A can configure the number of bands that a UE can request as UE assistance, the number of CCs per band, the number of MIMO layers per CC / band, and the minimum bandwidth per CC / band.

[0167] In some aspects, when network B configures the UE, the UE initiates, for network A, UE assistance information corresponding to the configuration / resources configured by network B.

[0168] In some embodiments, only when Network B configures a configuration / resource corresponding to the configuration / resource indicated by Network A, the UE starts UE assistance information corresponding to the configuration / resource configured by Network B for Network A; otherwise, the UE does not start the UE assistance information.

[0169] In some aspects, only when Network A attempts to configure a configuration / resource affected by the configuration / resource configured by Network B, the UE starts UE assistance information corresponding to the configuration / resource configured by Network B for Network A.

[0170] In some aspects, the UE provides the UE assistance information to Network A either as part of a rejection message to reject the configuration / resource or as a separate message.

[0171] In some embodiments, the UE assistance information can be an RRC message, such as L1 signaling in a MAC CE or DCI.

[0172] In some embodiments, the network infers from the UE assistance information (e.g., restricted bands) from the UE and derives combinations of bands that are no longer available.

[0173] In some aspects, the UE provides an indication to the network (e.g., Network A) indicating whether UE capability restrictions may need to be applied to the connection in an RRC setup, resume request, or RRC setup or resume completion.

[0174] In some aspects, upon receiving the above indication in claim 12, the network waits until it receives the complete UE capability restrictions before configuring the UE with CA / DC / MIMO, etc.

[0175] In some aspects, the UE provides proactive UE assistance information regarding resources / capabilities not currently used in a network (e.g., Network A) to avoid any future incompatible configurations by the network (i.e., Network A) that could result from such restrictions being applied to resources / capabilities used by another network (e.g., Network B).

[0176] For a UE equipped with multiple radio transceivers, the interference power from radio transmitters located in the same place can be much higher than the actual received power level of the desired signal at the receiver. This configuration can cause in-device coexistence (IDC) interference, which is referred to as the IDC problem. The disclosed technology introduces a frequency division multiplexing (FDM) solution to solve the IDC problem by using serving frequencies that are not affected by the IDC problem.

[0177] The problem with the NR FDM solution for IDC is that, since the granularity is the serving frequency, it cannot sufficiently represent the frequencies affected. Even if only a portion of the frequency resources at the serving frequency are affected by the IDC problem, the UE cannot use the serving frequency, which affects the scheduling of network resources.

[0178] The disclosed technology includes an enhanced FDM solution for IDC to show a higher granularity of the frequency resources affected by the IDC problem. The disclosed technology can improve the utilization efficiency of radio resources when solving the problem of in-device coexistence between NR and other RATs (e.g., WiFi and Bluetooth). FDM Resource Indication Technology

[0179] Regarding the UE assistance information related to FDM in the IDC, the resource indication granularity of the frequency affected by the IDC problem can be one or more of the bandwidth part (BWP), physical resource block (PRB), or resource block group (RBG). Alternatively, a separate configuration other than RBG can be used for the enhanced FDM report.

[0180] When the granularity is RBG or PRB, several of the following methods can be considered for the indication signaling.

[0181] (a) A bitmap-based method can be used. For example, a bitmap of RBGs within the bandwidth can be reported for each BWP.

[0182] (b) A start - length pair method (similar to the resource allocation type 1 of PDSCH / PUSCH) can be used. A clear {start, length} can be signaled, or a more signaling-efficient method can be used. For example, when the signaling is at the PRB granularity,

Number

Number

Number

Number

Number

Number

[0183] In some embodiments, the above approach may be used when the signaling is at the PRB granularity. Similar approaches can be used when the granularity is RBG or otherwise.

[0184] (c) As an extended version of option b), a plurality of start - length pairs can be indicated. Indication of frequency resources affected for the duplex mode

[0185] In FDD, the DL and UL frequencies are different, and the frequency resources affected in DL and UL can be different. The enhanced resource indication method can be used for only DL (when UL is not affected), only UL (when DL is not affected), or both DL and UL (when both DL and UL are affected). In the latter case, separate indications can be used for DL and UL.

[0186] In TDD, the same frequency is used for DL and UL. There can be two different methods for TDD indication.

[0187] In some embodiments, a single frequency resource indication is used and the interference direction is further indicated.

[0188] The same frequency is used for both DL and UL, but the interference situation can be different depending on factors such as different transmission powers. Therefore, similar to the indication method in FDD above, the enhanced resource indication method can be used for DL only (when UL is not affected), UL only (when DL is not affected), or both DL and UL (when both DL and UL are affected). In the latter case, separate indications can be used for DL and UL.

[0189] Considering the previous two sections on the resource indication method and FDD, an exemplary ASN.1 signaling structure is shown in Figure 9. In the example, a single frequency resource indication is used for TDD.

[0190] Figure 9 shows an exemplary ASN900 that constitutes the indication of frequency resources affected by the duplex mode in several aspects. IDC assistance information for non-serving frequencies

[0191] According to Note 2 in Section 5.7.4.2 of TS38.331, IDC assistance information for non-serving frequencies can be provided.

[0192] Regarding non-serving frequencies, reporting IDC problems indicates the expectation that if one or more non-serving frequencies become one or more serving frequencies, this will cause interference problems that the UE cannot solve by itself.

[0193]

[0194] There is no information about the bandwidth / BWP of non-serving frequencies. The disclosed technology can include two options for how to use the enhanced FDM solution for non-serving frequencies, which will be described below.

[0195] (a) Option 1: Additional information is provided by the gNB, such as BWP configuration, bandwidth information, RBG size configuration. The exact information varies depending on which granularity is selected for the serving frequency. Such additional information can be added by adding an IE to expand the following CandidateServingFreqListNR-r16.

[0196] Figure 10 shows an exemplary ASN1000 that constitutes an indication of additional information provided by a base station according to some aspects.

[0197] (b) Option 2: The UE indicates the frequency resources affected, assuming a fixed configuration where, for example, the BWP covers all PRBs and a specific RBG size (an example is Configuration 2 in Sections 5.1.2.2.1 (for DL) and 6.1.2.2.1 (for UL) of 3GPP TS 38.214).

[0198] In some embodiments, a UE in a wireless communication system includes circuitry for reporting UE assistance information for frequency resources affected by in-device coexistence issues at a higher granularity than the carrier frequency. In some aspects, a resource block group is the granularity of the resource indication. In some aspects, a bitmap is reported for the frequency resources affected by the carrier frequency. In some aspects, a start-length pair is reported for the frequency resources affected by the carrier frequency.

[0199] In some aspects, multiple start-length pairs are reported for the frequency resources affected by the carrier frequency. In some aspects related to FDD, the frequency resources affected are indicated independently for DL and UL.

[0200] In some aspects related to TDD, the frequency resources affected are indicated independently for DL and UL.

[0201] In some aspects related to TDD, the affected frequency resources and interference directions are indicated.

[0202] In some aspects, the affected frequency resources are indicated for non-serving frequencies.

[0203] In some embodiments, for non-serving frequencies, additional information such as BWP configuration, bandwidth information, and RBG size configuration is provided by the gNB.

[0204] In some aspects, the UE indicates the affected frequency resources assuming a fixed configuration.

[0205] FIG. 11 shows a block diagram of a communication device such as an evolved Node B (eNB), a next-generation Node B (gNB) (or another RAN node such as a base station), a network control repeater (NCR), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE) for executing one or more of the techniques disclosed herein according to some aspects. In an alternative aspect, the communication device 1100 can operate as a stand-alone device or can be connected to other communication devices (e.g., network-connected).

[0206] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of a device 1100 that includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit components can become flexible over time. A circuit can include members that can execute a specified operation alone or in combination at runtime. In one example, the hardware of a circuit can be designed to execute a particular operation (e.g., hardwired). In one example, the hardware of a circuit can include a physically modified machine-readable medium (e.g., a magnetic, electrically movable arrangement of immutable particles) that encodes instructions for a particular operation, and can include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.).

[0207] When connecting physical components, the electrical characteristics underlying the hardware components are changed, for example, from an insulator to a conductor or vice versa. Instructions enable an embedded hardware (e.g., an execution unit or a load mechanism) to generate members of a circuit within the hardware via a variable connection to execute portions of a particular operation during operation. Thus, in one example, a machine-readable medium element is part of a circuit or communicatively coupled to other components of the circuit when the device is operating. In one example, any of the physical components can be used within more than one member of more than one circuit. For example, during operation, an execution unit can be used in a first circuit of a first circuit configuration at one point in time, reused by a second circuit in the first circuit configuration, or by a third circuit in a second circuit configuration at a different time. Additional examples of these components with respect to device 1100 are described below.

[0208] In some embodiments, device 1100 may operate as a stand-alone device or may be connected to other devices (e.g., network-connected). In the context of a network connection, communication device 1100 may operate as a server communication device, a client communication device, or in both capacities in a server-client network environment. In one example, communication device 1100 may operate as a peer communication device within a peer-to-peer (P2P) (or other distributed) network environment. Communication device 1100 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web device, network router, switch or bridge, or any communication device that may execute (sequential or otherwise) instructions that specify actions to be taken by the communication device. Further, although only a single communication device is shown, the term "communication device" should also be understood to include any collection of communication devices that individually or jointly execute a set (or sets) of instructions to perform any one or more of the methodologies contemplated herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

[0209] As described herein, an example may include, or operate on, logic or some components, modules, or mechanisms. A plurality of modules may be tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, a circuit may be arranged as a module in a specified way (e.g., internally or with respect to external entities such as other circuits). In an example, one or more computer systems (e.g., stand-alone, client, or server computer systems), or portions of one or more hardware processors, may be configured as modules that operate to perform specified operations by firmware or software (e.g., instructions, an application portion, or an application). In one example, the software may reside on a communication device-readable medium. In an example, the software causes the hardware to perform specified operations when executed by the underlying hardware of the module.

[0210] Accordingly, the term "module" is understood to include a tangible entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., ephemerally) configured (e.g., programmed) to operate in a specified manner or to perform some or all of any of the operations described herein. Considering an example where a module is ephemerally configured, each of the modules need not be instantiated at any one point in time. For example, if a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Accordingly, the software may configure the hardware processor, for example, to configure a particular module at one instance time and a different module at a different instance time.

[0211] A communication device (e.g., UE) 1100 may include a hardware processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1104, a static memory 1106, and a storage device 1116 (e.g., a hard drive, a tape drive, a flash storage, or other block or storage device), some or all of which may communicate with each other via an interlink 1108 (e.g., a bus).

[0212] The communication device 1100 may further include a display device 1110, an input device 1112 (e.g., a keyboard), and a user interface (UI) navigation device 1114 (e.g., a mouse). In one example, the display device 1110, the input device 1112, and the UI navigation device 1114 may be a touch screen display. The communication device 1100 may further include a signal generation device 1118 (e.g., a speaker), a network interface device 1120, and one or more sensors 1121 such as a global positioning system (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 1100 may include an output controller 1128 for communicating or controlling with one or more peripheral devices (e.g., a printer, a card reader, etc.), such as a serial (e.g., a universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection).

[0213] Storage device 1116 may include a machine-readable medium 1122 storing one or more sets of data structures or instructions 1124 (e.g., software) that implement or are utilized by any one or more of the techniques or functions described herein. In some aspects, the registers of hardware processor 1102, main memory 1104, static memory 1106, and / or storage device 1116 may be, or may include (wholly or at least in part), a machine-readable medium 1122 storing one or more sets of data structures or instructions 1124 that implement or are utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of hardware processor 1102, main memory 1104, static memory 1106, or storage device 1116 may constitute a machine-readable medium 1122.

[0214] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium". While device-readable medium 1122 is shown as one medium, the term "communications device-readable medium" can include one or more media (e.g., a centralized or distributed database, and / or associated cache and server) configured to store instructions 1124. The term "communications device-readable medium" includes the terms "machine-readable medium" or "computer-readable medium" and can store, encode, or carry instructions (e.g., instructions 1124) executed by a communications device 1100 to cause the communications device 1100 to execute any one or more of the techniques of the present disclosure, or can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of communications device-readable media can include solid state memory, and optical and magnetic media. Specific examples of communications device-readable media can 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, communications device-readable medium can include non-transitory communications device-readable medium. In some examples, communications device-readable medium can include communications device-readable medium that is not a transitory propagated signal.

[0215] Command 1124 may further be transmitted or received on communication network 1126 using a transmission medium via network interface device 1120 utilizing any one of several transfer protocols. In one example, network interface device 1120 may include one or more physical jacks (e.g., Ethernet jack, coaxial jack, or phone jack), or one or more antennas connected to communication network 1126. In an example, network interface device 1120 may include multiple antennas for wireless communication using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) technologies. In some examples, network interface device 1120 may communicate wirelessly using multi-user MIMO technology.

[0216] The term "transmission medium" is to be construed to include any intangible medium that is capable of storing, encoding, or carrying a command executed by communication device 1100, and includes digital or analog communication signals for facilitating such software communication or another intangible medium. In this regard, the transmission medium in the context of the present disclosure is a device-readable medium.

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

[0218] The described implementations of the subject matter may include one or more features, alone or in combination, as exemplified below.

[0219] Example 1 is an apparatus for a user equipment (UE) configured to operate in a fifth generation new radio (5G NR) network, the apparatus comprising a processing circuit, wherein to configure the UE to simultaneously connect to the 5G NR network and at least a second network, the processing circuit encodes UE capability information for transmission to a base station of the 5G NR network, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; decodes first radio resource control (RRC) signaling received from the base station, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; detects interference between at least one of the plurality of MUSIM configurations and the operation of the UE on the at least second network; encodes second RRC signaling for transmission to the base station, the second RRC signaling indicating a temporary UE capability limitation based on the interference; and a memory coupled to the processing circuit and configured to store the first RRC signaling and the second RRC signaling.

[0220] In Example 2, the subject matter of Example 1 includes the subject matter in which the processing circuit decodes the plurality of MUSIM configurations to determine at least one of a list of component carriers used by the MUSIM operation; a list of communication bands used by the MUSIM operation; a list of secondary cells (SCells) used by the MUSIM operation; the number of MIMO layers within a component carrier, SCell, or communication band associated with the MUSIM operation; and a bandwidth reduction associated with the MUSIM operation.

[0221] In Example 3, the subject matters of Examples 1 and 2 include the subject matter that the processing circuit encodes the second RRC signaling as UE assistance information (UAI) for transmission to the base station using a physical uplink shared channel (PUSCH).

[0222] In Example 4, the subject matter of Example 3 includes the subject matter that the processing circuit encodes the UAI to include at least one of: one or more bands used by the operation of the UE on the at least second network; one or more downlink (DL) frequencies used by the operation of the UE on the at least second network; one or more uplink (UL) frequencies used by the operation of the UE on the at least second network; and at least one of one or more MIMO layers used by the operation of the UE on the at least second network.

[0223] In Example 5, the subject matters of Examples 1 to 4 include the subject matter that the processing circuit detects that at least one of the plurality of MUSIM configurations does not interfere with the operation of the UE on the at least second network.

[0224] In Example 6, the subject matter of Example 5 includes the subject matter that the processing circuit encodes a third RRC signaling for transmission to the base station, and the third RRC signaling includes UE assistance information (UAI) indicating release of the temporary UE capability restriction.

[0225] In Example 7, the subject matters of Examples 1 to 6 include the subject matter that the processing circuit encodes a third RRC signaling for transmission to the base station based on the configuration of the UE by the at least second network before detecting the interference, and the third RRC signaling indicates at least one configuration related to the operation of the UE on the at least second network.

[0226] In Example 8, the subject matter of Examples 1 to 7 includes the subject matter in which the processing circuit encodes the second RRC signaling so that the UE assistance information is further included, and the UE assistance information indicates frequency resources affected by in-device coexistence interference received by at least one transceiver in the UE.

[0227] In Example 9, the subject matter of Example 8 includes the subject matter in which the processing circuit encodes the UE assistance information so as to include a bitmap of frequency resources of a carrier frequency, and the frequency resources are affected by the in-device coexistence interference.

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

[0229] Example 11 is a computer-readable storage medium storing instructions executed by one or more processors of a base station, the instructions configuring the base station to simultaneously connect to a fifth-generation new radio (5G NR) network and at least a second network, and to decode user equipment (UE) capability information received from the UE via the 5G NR network at the base station, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; encoding first radio resource control (RRC) signaling for transmission to the UE, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; and decoding second RRC signaling received from the UE in response to the first RRC signaling, the second RRC signaling indicating at least one MUSIM configuration among the plurality of MUSIM configurations and a temporary UE capability limitation based on interference during operation of the UE on the at least second network.

[0230] In Example 12, the subject matter of Example 11 includes the operation of obtaining at least one of one or more bands used by the UE's operation on the at least second network; one or more downlink (DL) frequencies used by the UE's operation on the at least second network; one or more uplink (UL) frequencies used by the UE's operation on the at least second network; and one or more MIMO layers used by the UE's operation on the at least second network, further including the procedure of decoding the second RRC signaling to obtain the above.

[0231] In Example 13, the subject matter of Example 12 includes the procedure of encoding third RRC signaling for transmission to the UE, where the third RRC signaling includes one or more revisions to the plurality of MUSIM configurations based on the one or more bands, the one or more DL frequencies, the one or more UL frequencies, and the one or more MIMO layers indicated by the second RRC signaling.

[0232] Example 14 is a computer-readable storage medium storing instructions executable by one or more processors of a user equipment (UE), the instructions causing the UE to be configured to simultaneously connect to a fifth-generation new radio (5G NR) network and at least a second network, and causing the UE to perform procedures for encoding UE capability information for transmission to a base station of the 5G NR network, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; procedures for decoding first radio resource control (RRC) signaling received from the base station, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; procedures for detecting interference between at least one of the plurality of MUSIM configurations and operation of the UE on the at least second network; and procedures for encoding second RRC signaling for transmission to the base station, the second RRC signaling indicating a temporary UE capability limitation based on the interference.

[0233] In Example 15, the subject matter of Example 14 includes operations including procedures for decoding the plurality of MUSIM configurations to determine at least one of a list of component carriers used by the MUSIM operation; a list of communication bands used by the MUSIM operation; a list of secondary cells (SCells) used by the MUSIM operation; the number of MIMO layers within a component carrier, SCell, or communication band associated with the MUSIM operation; and bandwidth reduction associated with the MUSIM operation.

[0234] In Example 16, the subject matter of Examples 14 to 15 includes operations including procedures for encoding the second RRC signaling as UE assistance information (UAI) for transmission to the base station using a physical uplink shared channel (PUSCH).

[0235] In Example 17, the subject matter of Example 16 includes one or more bands used by the operation of the UE on the at least second network; one or more downlink (DL) frequencies used by the operation of the UE on the at least second network; one or more uplink (UL) frequencies used by the operation of the UE on the at least second network; and an operation including a procedure for encoding the UAI to include at least one of one or more MIMO layers used by the operation of the UE on the at least second network.

[0236] In Example 18, the subject matter of Examples 14 to 17 includes a procedure for detecting that at least one of the plurality of MUSIM configurations does not interfere with the operation of the UE on the at least second network, and a procedure for encoding third RRC signaling for transmission to the base station, the third RRC signaling including UE assistance information (UAI) indicating release of the temporary UE capability restriction.

[0237] In Example 19, the subject matter of Examples 14 to 18 includes a procedure for encoding third RRC signaling for transmission to the base station based on the configuration of the UE by the at least second network before detecting the interference, the third RRC signaling indicating at least one configuration related to the operation of the UE on the at least second network.

[0238] In Example 20, the subject matter of Examples 14 to 19 includes a procedure for encoding the second RRC signaling to further include UE assistance information, the UE assistance information indicating frequency resources affected by in-device coexistence interference received by at least one transceiver in the UE; and a procedure for encoding the UE assistance information to include a bitmap of frequency resources of carrier frequencies, the frequency resources being affected by the in-device coexistence interference.

[0239] Example 21 is at least one machine-readable medium including instructions that, when executed by a processing circuit, cause the processing circuit to perform operations for implementing any one of Examples 1 to 20.

[0240] Example 22 is an apparatus comprising means for implementing any one of Examples 1 to 20.

[0241] Example 23 is a system for implementing any one of Examples 1 to 20.

[0242] Example 24 is a method for implementing any one of Examples 1 to 20.

[0243] Although aspects have been described with respect to specific exemplary modes, it will be apparent that various modifications and changes can be made to these aspects 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 limiting sense. Therefore, the embodiments for carrying out the present invention should not be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims together with the full scope of equivalents having rights with respect to such claims.

Claims

1. An apparatus for a user equipment (UE) configured to operate in a fifth generation new radio (5G NR) network, the apparatus comprising: a processing circuit configured to configure the UE to simultaneously connect to the 5G NR network and at least a second network, the processing circuit: encoding UE capability information for transmission to a base station of the 5G NR network, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; decoding first radio resource control (RRC) signaling received from the base station, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; detecting interference between at least one of the plurality of MUSIM configurations and the operation of the UE on the at least second network; and encoding second RRC signaling for transmission to the base station, the second RRC signaling indicating a temporary UE capability limitation based on the interference; and a memory coupled to the processing circuit and configured to store the first RRC signaling and the second RRC signaling An apparatus comprising.

2. The processing circuit: decoding the plurality of MUSIM configurations to determine at least one of: a list of component carriers used by the MUSIM operation; a list of communication bands used by the MUSIM operation; a list of secondary cells (SCells) used by the MUSIM operation; the number of MIMO layers within a component carrier, SCell, or communication band associated with the MUSIM operation; and a bandwidth reduction associated with the MUSIM operation The apparatus according to claim 1.

3. The processing circuit encodes the second RRC signaling as UE assistance information (UAI) for transmission to the base station using a physical uplink shared channel (PUSCH). The apparatus according to claim 1.

4. The processing circuit: one or more bands used by the operation of the UE on the at least second network; one or more downlink (DL) frequencies used by the operation of the UE on the at least second network; one or more uplink (UL) frequencies used by the operation of the UE on the at least second network; and one or more MIMO layers used by the operation of the UE on the at least second network The apparatus according to claim 3, wherein the UAI is encoded to include at least one of the foregoing. **Claim 5** The processing circuit The apparatus according to claim 1, wherein the processing circuit detects that at least one of the plurality of MUSIM configurations does not interfere with the operation of the UE on the at least second network. **Claim 6** The processing circuit The apparatus according to claim 5, wherein the processing circuit encodes third RRC signaling for transmission to the base station, and the third RRC signaling includes UE assistance information (UAI) indicating release of the temporary UE capability restriction. **Claim 7** The processing circuit The apparatus according to claim 1, wherein the processing circuit encodes third RRC signaling for transmission to the base station based on the configuration of the UE by the at least second network before detecting the interference, and the third RRC signaling indicates at least one configuration related to the operation of the UE on the at least second network. **Claim 8** The processing circuit The apparatus according to claim 1, wherein the processing circuit encodes the second RRC signaling to further include UE assistance information, and the UE assistance information indicates frequency resources affected by in-device coexistence interference received by at least one transceiver in the UE. **Claim 9** The processing circuit The apparatus according to claim 8, wherein the processing circuit encodes the UE assistance information to include a bitmap of frequency resources of a carrier frequency, and the frequency resources are affected by the in-device coexistence interference. **Claim 10** a transceiver circuit coupled to the processing circuit; and one or more antennas coupled to the transceiver circuit The apparatus according to any one of claims 1 to 9, further comprising. **Claim 11** A computer-readable storage medium storing instructions executed by one or more processors of a base station, the instructions configuring the base station to simultaneously connect to a fifth-generation new radio (5G NR) network and at least a second network, and causing the base station to A procedure for decoding user equipment (UE) capability information received from a UE via the 5G NR network, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; A procedure for encoding first radio resource control (RRC) signaling for transmission to the UE, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; and A procedure for decoding second RRC signaling received from the UE in response to the first RRC signaling, the second RRC signaling indicating at least one MUSIM configuration of the plurality of MUSIM configurations and a temporary UE capability limitation based on interference during operation of the UE on the at least second network, A computer-readable storage medium for causing an operation including the above.

12. The operation is One or more bands used by the operation of the UE on the at least second network; One or more downlink (DL) frequencies used by the operation of the UE on the at least second network; One or more uplink (UL) frequencies used by the operation of the UE on the at least second network; and One or more MIMO layers used by the operation of the UE on the at least second network A procedure for decoding the second RRC signaling to obtain at least one of the above The computer-readable storage medium according to claim 11, further including the above.

13. The operation is A procedure for encoding third RRC signaling for transmission to the UE, the third RRC signaling including one or more revisions to the plurality of MUSIM configurations based on the one or more bands, the one or more DL frequencies, the one or more UL frequencies, and the one or more MIMO layers indicated by the second RRC signaling, The computer-readable storage medium according to claim 12, further including the above.

14. A computer-readable storage medium storing instructions to be executed by one or more processors of a user equipment (UE), the instructions configuring the UE to simultaneously connect to a fifth generation new radio (5G NR) network and at least a second network, and causing the UE to a procedure for encoding UE capability information for transmission to a base station of the 5G NR network, the UE capability information indicating that the UE supports multi-universal subscriber identity module (MUSIM) operation; a procedure for decoding first radio resource control (RRC) signaling received from the base station, the first RRC signaling including a plurality of MUSIM configurations for configuring the UE for the MUSIM operation; a procedure for detecting interference between at least one MUSIM configuration of the plurality of MUSIM configurations and the operation of the UE on the at least second network; and a procedure for encoding second RRC signaling for transmission to the base station, the second RRC signaling indicating a temporary UE capability limitation based on the interference, A computer-readable storage medium that causes the above operations to be performed. **Claim 15** The operations are a procedure for decoding the plurality of MUSIM configurations to determine at least one of a list of component carriers used by the MUSIM operation; a list of communication bands used by the MUSIM operation; a list of secondary cells (SCells) used by the MUSIM operation; the number of MIMO layers within a component carrier, SCell, or communication band related to the MUSIM operation; and bandwidth reduction related to the MUSIM operation The computer-readable storage medium according to claim 14, including the above. **Claim 16** The operations are a procedure for encoding the second RRC signaling as UE assistance information (UAI) for transmission to the base station using a physical uplink shared channel (PUSCH) The computer-readable storage medium according to any one of claims 14 to 15, including the above. **Claim 17** The operations are one or more bands used by the operation of the UE on the at least second network; one or more downlink (DL) frequencies used by the operation of the UE on the at least second network; one or more uplink (UL) frequencies used by the operation of the UE on the at least second network; and one or more MIMO layers used by the operation of the UE on the at least second network A procedure for encoding the UAI to include at least one of The computer-readable storage medium according to claim 16, comprising

18. The operation is A procedure for detecting that at least one of the plurality of MUSIM configurations does not interfere with the operation of the UE on the at least second network; and A procedure for encoding third RRC signaling for transmission to the base station, the third RRC signaling including UE assistance information (UAI) indicating release of the temporary UE capability restriction The computer-readable storage medium according to claim 14, comprising

19. The operation is A procedure for encoding third RRC signaling for transmission to the base station based on the configuration of the UE by the at least second network before detecting the interference, the third RRC signaling indicating at least one configuration related to the operation of the UE on the at least second network The computer-readable storage medium according to claim 14, comprising

20. The operation is A procedure for encoding the second RRC signaling to further include UE assistance information, the UE assistance information indicating frequency resources affected by in-device coexistence interference received by at least one transceiver in the UE; and A procedure for encoding the UE assistance information to include a bitmap of frequency resources of the carrier frequency, the frequency resources being affected by the in-device coexistence interference The computer-readable storage medium according to any one of claims 14 to 19, comprising

Images