Fast Radio Resource Management (RRM) procedures

Abstract

The computer-readable storage medium stores instructions for configuring a UE for radio resource management (RRM) measurements in a 5G NR network and causing the UE to perform operations. The operations include decoding RRC signaling. The RRC signaling includes system information associated with an Inter-RAT cell of a target base station. The system information includes an indicator for supporting enhanced RRM measurements by the Inter-RAT cell. Configuration information from a source base station is decoded. The configuration information includes a handover command for performing a handover from the source base station to the target base station. Whether to perform the enhanced RRM measurements and handover is determined based on the indicator.

Description

[Technical field]

[0001] The present invention relates to wireless communications in some aspects. Some aspects relate to 5th generation (5G) networks and beyond, including 3GPP (Third Generation Partnership Project) networks, 3GPP (Long Term Evolution) networks, 3GPP (LTE) LTE Advanced (LTE-A) networks, (MultiFire, LTE-U), and 5G New Radio (NR) (or 5G-NR) networks, 5G-LTE networks (such as 5G NR unlicensed spectrum (NR-U) networks), and other unlicensed networks including Wi-Fi, CBRS (OnGo), and the like. Other aspects are directed to techniques for configuring user equipment (UE) support for fast radio resource management (RRM) procedures in 5G-NR (and beyond) networks. [Background technology]

[0002] (Priority Claim) This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 158,504, entitled “User Equipment Support of Fast Radio Resource Management (RRM) Procedures,” filed March 9, 2021, which is hereby incorporated by reference in its entirety.

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The use of 3GPP® LTE systems has increased with the increase in different types of devices communicating with various network devices. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for a wide variety of network devices in many different environments. The fifth generation (5G) wireless systems are emerging and are expected to provide even faster speeds, improved connectivity and ease of use. The next generation of 5G networks (or NR networks) are expected to improve throughput, coverage, robustness and reduce latency, operational and capital expenditures. 5G-NR networks continue to evolve with the potential of new radio access technologies (RATs) in addition to 3GPP® LTE-Advanced to enrich people's lives with seamless wireless connectivity solutions that deliver high speeds and rich content and services. As current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies are beneficial due to their high bandwidth.

[0004] Potential LTE operation in unlicensed spectrum includes (but is not limited to) LTE operation in unlicensed spectrum via dual connectivity (DC) or DC-based LAA and standalone LTE systems in unlicensed spectrum. According to this, LTE-based technologies will operate exclusively in unlicensed spectrum without the need for an "anchor" in licensed spectrum, called MultiFire. Further enhanced operation of LTE and NR systems in licensed spectrum as well as unlicensed spectrum is expected in future releases and 5G (and beyond) systems. Such enhanced operation includes techniques to configure UE support of RRM procedures at high speed in 5G-NR (and beyond) networks. [Brief description of the drawings]

[0005] The figures are not necessarily drawn to scale and may represent similar components in different views, such as numerals, and may represent different instances of similar components, such as numerals with different letter suffixes. These figures illustrate generally, by way of example, and not by way of limitation, various aspects discussed in this document.

[0006] [Figure 1A] 1 illustrates a network architecture according to several aspects. [Figure 1B] 1 illustrates the architecture of a non-roaming 5G system according to several aspects. [Figure 1C] 1 illustrates the architecture of a non-roaming 5G system according to several aspects. [Diagram 2] Various systems, devices and components are illustrated in which aspects of the disclosed embodiments can be implemented. [Diagram 3] Various systems, devices and components are illustrated in which aspects of the disclosed embodiments can be implemented. [Figure 4] Various systems, devices and components are illustrated in which aspects of the disclosed embodiments can be implemented. [Diagram 5] A high speed communication scenario using the disclosed technology is illustrated in accordance with some aspects. [Figure 6] A block diagram of a communication device, such as an evolved Node-B (eNB), new generation Node-B (gNB) (or other RAN node or base station), transmission / reception point (TRP), access point (AP), radio station (STA), mobile station (MS), or user equipment (UE), is shown in accordance with some aspects. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The following description and drawings sufficiently explain the aspects to enable one skilled in the art to practice them. Other aspects can include structural, logical, electrical, process and other changes. Portions and features of one aspect can be included in or substituted for other aspects. Aspects outlined in the claims include all available equivalents of those claims.

[0008] 1A illustrates a network architecture according to some aspects. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices 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 other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

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

[0010] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs such as mobile phones. Carrier aggregation is a technique in LTE-Advanced and various wireless systems that uses multiple carrier signals operating at different frequencies to communicate for a single UE, increasing the bandwidth available to a single device. In some aspects, carrier aggregation is used when one or more component carriers operate in unlicensed frequencies.

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

[0012] The aspects described herein can also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDM, etc.), in particular 3GPP New Radio (NR), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0013] In some aspects, any of the UEs 101 and 102 may include Internet of Things (IoT) UEs or Cellular IoT (CIoT) UEs, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. In some aspects, any of the UEs 101 and 102 may include a Narrowband (NB) IoT UE (e.g., Enhanced NB-IoT) eNB-IoT (UE and Further Enhanced) FeNB-IoT (UE, etc.). The IoT UEs may utilize technologies such as Machine-to-Machine (M2M) or Machine-Type Communication (MTC) to exchange data with MTC servers or devices over Public Land Mobile Networks (PLMNs), Proximity-Based Services (ProSe), or Device-to-Device (D2D) communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. IoT networks include the ability to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), over short-term connections. The IoT UE may run background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0014] In some aspects, any of the UEs 101 and 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0015] The UEs 101 and 102 may be configured to communicatively couple with a Radio Access Network (RAN) 110, for example. 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 other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each including a physical communication interface or layer (described in further detail below). In this example, the connections 103 and 104 are illustrated as air interfaces enabling the communicative coupling and may be consistent with cellular communication protocols such as a Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP® Long Term Evolution (LTE) protocol, a Fifth Generation (5G) protocol, a New Radio (NR) protocol, or the like.

[0016] In one aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may also be referred to as a sidelink interface that includes one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink detection channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0017] The UE 102 is configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, whereby the AP 106 may include a Wireless Fidelity (Wi-Fi®) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

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

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

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

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

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

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

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

[0025] In an aspect, the communication network 140A may be an IoT network or a 5G network, including 5G new wireless networks that use communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One current implementation of IoT is Narrowband IoT (NB-IoT).

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

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

[0028] FIG. 1B illustrates a non-roaming 5G system architecture according to some aspects. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an Access and Mobility Management Function (AMF) 132, a Location Management Function (LMF) 133, a Session Management Function (SMF) 136, a Policy Control Function (PCF) 148, an Application Function (AF) 150, a User Plane Function (UPF) 134, a Network Slice Selection Function (NSSF) 142, an Authentication Server Function (AUSF) 144, and a Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, Internet access, or third party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. 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. The PCF 148 can be configured to provide a policy framework with network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0029] The LMF 133 can be used in connection with a 5G positioning function. In some aspects, the LMF 133 receives measurement and assistance information from the Next Generation Radio Access Network (NG-RAN) 110 and the mobile device (e.g., UE 101) via the AMF 132 from the NLs interface to calculate the position of the UE 101. In some aspects, the NR Positioning Protocol A (NRPPa) can be used to transmit positioning information between the NG-RAN and the LMF 133 over the Next Generation Control Plane Interface (NG-C). In some aspects, the LMF 133 configures the UE using the LTE Positioning Protocol (LPP) via the AMF 132. The NG RAN 110 configures the UE 101 using the Radio Resource Control (RRC) protocol over the LTE-Uu and NR-Uu interfaces.

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

[0031] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as a Call Session Control Function (CSCF), as well as an IP Multimedia Subsystem (IMS) 168B. More specifically, the IMS 168B includes CSCFs acting as a Proxy CSCF (P-CSCF) 162BE, a Service CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogation CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured as an initial point of contact for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state within the network, and the E-CSCF can be configured to handle certain aspects of the emergency session, such as routing the emergency request to the appropriate emergency center or PSAP. The I-CSCF 166B can be configured to act as a contact point within the operator's network for all IMS connections destined for that network operator's subscribers or roaming subscribers currently located within that network operator's service area. In some aspects, the I-CSCF 166B can connect to another IP multimedia network 170E, e.g., an IMS operated by another network operator.

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

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

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

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

[0036] 2, 3 and 4 illustrate various systems, devices and components that can implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR (and beyond) networks. UEs, base stations (such as gNBs) and / or other nodes (e.g., satellites or other NTN nodes) described in connection with FIGS. 1A-4 can be configured to perform the disclosed techniques.

[0037] 2 illustrates a 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 example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP® systems.

[0038] The network 200 may include UEs 202, which may include any mobile or non-mobile computing device designed to communicate with the RAN 204 over a wireless connection. The UEs 202 may be, but are not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, in-vehicle infotainment, in-vehicle entertainment devices, instrument clusters, heads-up display devices, in-vehicle diagnostic devices, dashboard 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, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, and the like.

[0039] In some embodiments, the network 200 may include multiple 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 PSBCH, PSDCH, PSCH, PSCCH, PSFCH, etc.

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

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

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

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

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

[0045] In a V2X scenario, the UE 202 or AN 208 may be or function as a Roadside Unit (RSU), which refers to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU." An eNB may be referred to as an "eNB-type RSU." A gNB may be referred to as a "gNB-type RSU." And so on. In one example, the RSU is a computing device coupled with radio frequency circuitry located on the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuitry that stores intersection map geometry, traffic statistics, media, as well as applications / software to detect and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications necessary for high speed events such as crash avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller that provides a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

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

[0047] In some embodiments, the RAN 204 may be an NG-RAN 214 having a gNB, e.g., gNB 216, or an ng-eNB, e.g., ng-eNB 218. The gNB 216 may connect with a 5G-capable UE using a 5G NR interface. The gNB 216 may connect with a 5G core via an NG interface, including an N2 interface or an N3 interface. The ng-eNB 218 may connect with a 5G core via an NG interface, but may connect with a UE via an LTE air interface. The gNB 216 and the ng-eNB 218 may connect with an Xn interface.

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

[0049] The NG-RAN 214 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM, CP-OFDM, DFT-s-OFDM for DL; polar, repetition, simplex, Reed-Muller codes for control, LDPC codes for data. The 5G-NR air interface may rely on 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. It uses PTRS for phase tracking of the PDSCH and tracking reference signals for time tracking. The 5G-NR air interface operates in the FR1 band, which includes the sub-6 GHz band, or the FR2 band, which includes the 24.25 GHz to 52.6 GHz band. The 5G-NR air interface may include synchronization signals and physical broadcast channel (SS / PBCH) blocks (SSBs), which are regions of the downlink resource grid that include PSS / SSS / PBCH.

[0050] In some embodiments, the 5G-NR air interface can utilize BWPs (bandwidth portions) for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For example, the UE 202 can be configured with multiple BWPs with different SCS for each BWP configuration. When a change in BWP is indicated to the UE 202, the SCS of the transmission is also changed. Another use case of BWPs is related to power saving. In particular, multiple BWPs can be configured on the UE 202 with different amounts of frequency resources (e.g., PRBs) to support data transmissions in different traffic load scenarios. BWPs with a smaller number of PRBs can be used for data transmissions with a smaller traffic load while enabling power saving at the UE 202 and possibly the gNB 216. BWPs with a larger number of PRBs can be used for high traffic load scenarios.

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

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

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

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

[0055] 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 EPC inter-node signaling for mobility between different RAT networks. Selection of PDN and S-GW designated by the MME 224; selection of MME for handover; S3 reference point between the MME 224 and the SGSN 228 allows user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0056] The HSS 230 may include a database for network users, including subscription-related information to support processing of communication sessions of the network entities. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 230 and the MME 224 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 220.

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

[0058] The PCRF 234 is the policy and charging control element of the LTE CN 220. The PCRF 234 may be communicatively coupled to an app / content server 238 to determine appropriate QoS and charging parameters for a service flow. The PCRF 234 may provision the PCEF (via the Gx reference point) with the appropriate TFT and QCI related rules.

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

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

[0061] The AMF 244 enables other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and subscribe to notifications regarding mobility events regarding the UE 202. The AMF 244 may be responsible for registration management (e.g., when registering 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 of 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 of SMS messages between the UE 202 and the SMF. The AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Additionally, the AMF 244 may be a termination point of the RAN CP interface that includes or is the N2 reference point between the RAN 204 and the AMF 244. The AMF 244 may also be the termination point for NAS (N1) signaling and may perform NAS encryption and integrity protection. The AMF 244 may also support NAS signaling with the UE 202 over the N3 IWF interface.

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

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

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

[0065] The NEF 252 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF 260), edge computing or fog computing systems, etc. In such an embodiment, the NEF 252 may authenticate, authorize, or throttle the AF. The NEF 252 may also translate information exchanged with the AF 260 and with internal network functions. For example, the NEF 252 may translate between AF service identifiers and ~internal 5GC information. The NEF 252 may also receive information from other NFs based on the exposed capabilities of the other NFs. This information may be stored in the NEF 252 as structured data or in a data storage NF using a standardized interface. The stored information may be re-exposed by the NEF 252 to other NFs or AFs or used for other purposes such as analytics. Additionally, the NEF 252 may also display NEF service-based interfaces.

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

[0067] The PCF 256 may provide and enforce policy rules for controlling plane functions and may also support a unified policy framework for controlling network behavior. The PCF 256 may also implement a front end for accessing subscription information related to policy decisions in the UDRs of the UDM 258. As shown, the PCF 256 exhibits an Npcf service-based interface in addition to communicating with functions via reference points.

[0068] The UDM 258 may process subscription related information to support the processing of communication sessions of the network entities and store subscription data of the UE 202. For example, the subscription data may be communicated via the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 may include two parts, an application front-end and a UDR. The UDR may store structured data (PFD for application discovery, 202 including application requirement information of multiple UEs) for subscription data and policy data of the UDM 258 and the PCF 256, and / or exposure and application data of the NEF 252. The Nudr service-based interface is exposed by the UDR and allows the UDM 258, the PCF 256, and the NEF 252 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe notifications of relevant data changes in the UDR. The UDM may include a UDM-FE responsible for processing authentication information, location management, subscription management, etc. Different front-ends may provide services to the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. As shown in the figure, in addition to communicating with other NFs via reference points, the UDM 258 can expose a Nudm service-based interface.

[0069] The AF 260 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

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

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

[0072] 3 illustrates a schematic of a wireless network 300 according to various embodiments. The wireless network 300 can include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 are similar to and substantially interchangeable with similarly named components described elsewhere herein.

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

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

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

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

[0077] The modem platform 310 further includes transmit circuitry 318, receive circuitry 320, RF circuitry 322, and an RF front end (RFFE) 324, which may include or be connected to one or more antenna panels 326. Briefly, the transmit circuitry 318 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc. The receive circuitry 320 may include analog-to-digital converters, mixers, IF components, etc. The RF circuitry 322 may include low noise amplifiers, power amplifiers, power tracking components, etc. 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 arrangement of the transmit circuitry 318, receive circuitry 320, RF circuitry 322, RFFE 324, and antenna panel 326 components (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains and may be located on the same or different chips / modules.

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

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

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

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

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

[0083] Processor 410 may include, for example, processor 412 and processor 414. Processor 410 may 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 described herein), or any suitable combination thereof.

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

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

[0086] The instructions 450 may include software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 410 to perform any one or more of the methodologies described herein. The instructions 450 may reside, completely or partially, within at least one of the processors 410 (e.g., in a cache memory of the processor), the memory / storage 420, or any suitable combination thereof. Additionally, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripherals 404 or the database 406. Thus, the memory of the processor 410, the memory / storage 420, the peripherals 404, and the database 406 are examples of computer-readable and machine-readable media.

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

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

[0089] The term "machine learning" or "ML" refers to the use of computer systems that implement algorithms and / or statistical models to perform specific task(s) without explicit instructions, relying instead on patterns and inference. ML algorithms build or infer mathematical models (called "ML models" or the like) based on sample data (called "training data", "model training information", etc.) to make predictions or decisions not explicitly programmed to perform such tasks. In general, ML algorithms are computer programs that learn from experience regarding a task and a performance measurement, and ML models may be any object or data structure created after an ML algorithm is trained on one or more training data sets. After training, ML models can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept than the term "ML model", these terms discussed herein may be used interchangeably in this disclosure.

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

[0091] In some aspects, the UE is configured to report a single capability to support RRM enhanced measurements targeting either the NR carrier or the LTE carrier while moving under a threshold speed (e.g., a maximum speed of 500 km / h or less). If the UE can perform RRM enhanced measurements on an LTE carrier with a maximum speed of 500 km / h (also can operate with an NR module) but cannot operate with an LTE module below that speed, the UE may not be able to correctly report the configuration or measurements to the network. As a result, when the network hands over (or redirects) the UE to an LTE cell (or when the UE reselects an LTE cell), the connection fails.

[0092] When an LTE cell operates with a UE moving at a speed below a preset threshold speed (e.g., 500 km / h), the UE may not need to meet the connected mode measurement requirements so that the network does not handover or redirect the UE from an NR base station to an LTE base station. The UE may not need to meet the idle mode measurement requirements so that the UE does not reselect from an NR base station to an LTE base station. The UE can determine from a network signal whether the target LTE base station is configured to communicate with a UE moving at a speed below a threshold speed (e.g., a maximum speed of 500 km / h), and the signal can provide the UE as a reference in the disclosed technology.

[0093] In some aspects, 3GPP® Technical Specifications (TS) 38.331 and TS 36.331 may specify two sets of UE capabilities (e.g., as specified in Tables 1 and 2 below) respectively for the UE to indicate to the network whether it supports 500 km / h fast RRM measurements. Both capabilities are options that the UE supports. [Table 1] [Table 2]

[0094] In some aspects, the TS may specify that for a UE indicating NR capability HighSpeedParameters-r16, it must support faster RRM measurements performed at speeds below 500 km / h, targeting either neighboring NR or LTE base station cells. In some embodiments, the UE may include baseband implementations of separate NR and LTE hardware modules, where the UE can operate while moving at a threshold speed (e.g., 500 km / h) with its NR module but not with its LTE module (e.g., vendors tend to advance hardware NR modules but not LTE modules). In some aspects, separate Inter-RAT (for LTE cells) and Intra-NR (for NR cells) high speed parameters may be configured to indicate whether the UE supports threshold speed (e.g., 500 km / h) high speed RRM measurements using its LTE and NR modules, respectively.

[0095] 5 illustrates a diagram 500 of a high speed communication scenario using the disclosed techniques in accordance with some aspects. With reference to FIG 5, a UE 502 may be moving in a direction indicated by an arrow in FIG 5 (e.g., the UE 502 may be in a moving train or other vehicle).

[0096] While moving, the UE 502 can communicate with one or more base stations, such as base station 504 and base station 506. In some aspects, base station 504 can be a source base station and base station 506 can be a target base station. In some embodiments, the UE 502 can receive configuration information (e.g., system information blocks 508 and 512) from the respective base stations 504 and 506. In some embodiments, the UE 502 can communicate data or configuration information (e.g., UE capability information) to the base stations 504 and 506 via physical uplink shared channels (PUCCHs) 510 and 514, respectively. Additional functionality in accordance with the disclosed techniques is discussed herein below in connection with the provided examples and aspects.

[0097] In some embodiments, the moving UE may use system information received from the base station (e.g., a system information block (SIB) such as SIB5) to determine whether a configured target inter-RAT LTE cell can communicate with the UE moving at a speed less than 500 km / h. In this regard, the SIB may be used to prevent the UE from erroneously handing over / redirecting / reselecting from an NR base station to an LTE base station, and also to prevent further communication failures due to the UE being unable to operate using an LTE module configured to operate at a higher speed less than 500 km / h.

[0098] Examples of SIBs that can be used in conjunction with the disclosed technology are shown in Table 3 below. [Table 3]

[0099] In some aspects, the SIB information may be configured to indicate whether the communication base station is configured for inter-RAT measurement requirements and capable of supporting communication with UEs moving at speeds up to 500 km / h.

[0100] In some embodiments, the UE is configured to operate in NR while traveling at a speed less than 500 km / h and measure target cells while traveling at a speed of 500 km / h with an NR baseband module, but when the UE switches the baseband to an LTE module, it is unable to communicate with LTE cells while traveling at 500 km / h.

[0101] In some aspects, when the UE is in connected mode, the UE is configured by the network to measure one LTE target frequency / cell.

[0102] In some embodiments, the UE compares the target LTE frequency in the measurement configuration with the LTE frequency information received from the system information block to determine whether the cell is capable of communicating with the UE moving at a speed of 500 km / h, in which case the UE may not perform measurements and generate a corresponding report to the network to prevent itself from being handed over or redirected to that cell.

[0103] In some aspects, when the UE enters idle mode and performs a cell reselection procedure, the UE compares the target LTE frequency with the LTE frequency information received via the system information block to determine whether the target base station includes a cell configured to communicate with the UE moving at a high speed of 500 km / h, in which case the UE does not reselect to the LTE cell even if the cell is deemed sufficient in terms of signal quality.

[0104] In some aspects, a UE can be forced to support LTE fast RRM procedures as a prerequisite for supporting NR fast RRM procedures.

[0105] 6 illustrates a block diagram of a communications device, such as an evolved Node-B (eNB), new generation Node-B (gNB) (or other RAN node or base station), transmit / receive point (TRP), access point (AP), radio station (STA), mobile station (MS), or user equipment (UE), in accordance with some aspects. In alternative aspects, communications device 600 may operate as a standalone device or may be connected (e.g., networked) to other communications devices.

[0106] A circuit (e.g., processing circuit) is a collection of circuits implemented in a tangible entity of the device 600 that includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership may be flexible over time. A circuit includes members that, alone or in combination, can perform a specified operation when in operation. In one example, the hardware of a circuit may be immutably designed to perform a specific operation (e.g., wired). In one example, the hardware of a circuit may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include machine-readable media (e.g., magnetic, electrical, arrangements of movable invariant mass particles, etc.) that are physically modified to encode instructions for a specific operation.

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

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

[0109] As described herein, examples may include or operate on logic or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that can perform certain operations and may be configured or arranged in a particular manner. In one example, a circuit may be arranged in a predetermined manner (e.g., internally or with respect to external entities such as other circuits) as a module. In one example, all or part of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured as modules that operate to perform certain operations by firmware or software (e.g., instructions, application parts, or applications). In one example, the software may reside on a communication device readable medium. In one example, the software, when executed by the hardware underlying the module, causes the hardware to perform the specified operations.

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

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

[0112] The communication device 600 may further include a display device 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In one example, the display device 610, the input device 612, and the UI navigation device 614 may be touch screen displays. The communication device 600 may further include a signal generating device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 600 may include an output controller 628, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.).

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

[0114] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." Although the communication device-readable medium 622 is illustrated as a single medium, the term "communication device-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 624. The term "communication device-readable medium" includes the term "machine-readable medium" or "computer-readable medium" and may include any medium that can store, encode or carry instructions (e.g., instructions 624) for execution by the communication device 600, cause the communication device 600 to perform any one or more of the techniques of this disclosure, or store, encode or carry data structures used by or associated with such instructions. Non-limiting examples of communication device-readable media include solid-state memory and optical and magnetic media. Specific examples of communication device readable media include non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device readable media may include non-transient communication device readable media. In some examples, communication device readable media may include communication device readable media that is not a non-transient propagating signal.

[0115] The instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any of a number of transport protocols. In one example, the network interface device 620 may include one or more physical jacks (such as Ethernet, coaxial, phone jacks, etc.) or one or more antennas for connecting to the communications network 626. In one example, the network interface device 620 may include multiple antennas for wireless communication using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) technology. In some examples, the network interface device 620 may wirelessly communicate using multi-user MIMO technology.

[0116] The term "transmission medium" is intended to include any intangible medium capable of storing, encoding, or transmitting instructions for execution by communication device 600, including digital or analog communication signals or other intangible media that facilitate the communication of such software. In this regard, transmission media in the context of this disclosure are device-readable media.

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

[0118] The described implementations of the subject matter may include one or more of the features alone or in combination, as illustrated by way of example below.

[0119] Example 1 is an apparatus for a user equipment (UE) configured to operate in a fifth generation new radio (5G NR) network, the apparatus including a processing circuit, for configuring the UE for radio resource management (RRM) measurements in the 5G NR network, the processing circuit is to decode radio resource control (RRC) signaling, the RRC signaling including system information associated with an Inter-Radio Access Technology (interRAT) cell of a target base station, and system information including an indicator for supporting enhanced RRM measurements with the interRAT cell, configuration information from a source base station, the configuration information including a handover command for performing a handover from the source base station to the target base station, and determining whether to perform the enhanced RRM measurements and a handover from the source base station to the target base station based on the indicator for supporting enhanced RRM measurements with the interRAT cell, and a memory coupled to the processing circuit and configured to store the system information.

[0120] In Example 2, the subject matter of Example 1 includes subject matter where the processing circuitry is configured to not perform the enhanced RRM measurements and the handover from the source base station to the target base station if the UE does not support the enhanced RRM measurements covering the Inter-RAT cell.

[0121] In Example 3, the subject matter of Examples 1-2 includes the subject matter where the system information is System Information Block 5 (SIB5).

[0122] In Example 4, the subject matter of Examples 1-3 includes subject matter where the indicator indicates whether the Inter-RAT cell of the target base station supports enhanced RRM measurements when the UE is traveling at a speed up to the threshold speed.

[0123] In Example 5, the subject matter of Example 4 includes subject matter where the threshold speed is 500 km / h.

[0124] In Example 6, the subject matter of Examples 4-5 includes subject matter in which the processing circuitry is configured to not perform target base station selection or reselection based on the indicator to support enhanced RRM measurements with Inter-RAT cells.

[0125] In Example 7, the subject matter of Examples 1-6 includes subject matter where the processing circuitry is configured to encode an information element (IE) for transmission to a source base station over a physical uplink shared channel (PUSCH), the IE indicating UE capabilities related to support of enhanced RRM measurements by the UE.

[0126] In Example 8, the subject matter of Example 7 includes km / h.

[0127] In Example 9, the subject matter of Example 8 includes subject matter where the processing circuitry is configured to not perform enhanced RRM measurements and handover from the source base station to the target base station based on the UE capabilities indicated by the IE.

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

[0129] Example 11 is a computer-readable storage medium storing instructions for execution by one or more processors of a source base station, instructions for configuring the base station for radio resource management (RRM) measurements in a fifth generation new radio (5G NR) network, and for causing the base station to perform operations, the instructions including: encoding radio resource control (RRC) signaling for transmission to a user equipment (UE), the RRC signaling including system information related to an Inter-Radio Access Technology (Inter-RAT) cell of a target base station, and the system information including an indicator for supporting enhanced RRM measurements with the Inter-RAT cell; and encoding configuration information for transmission to the UE, the configuration information including a handover instruction for performing a handover from the source base station to the target base station based on the indicator:

[0130] In Example 12, the subject matter of Example 11 includes the subject matter where the system information is System Information Block 5 (SIB5).

[0131] Example 13 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), instructions for configuring the UE for radio resource management (RRM) measurements in a fifth generation new radio (5G NR) network, and instructions for causing the UE to perform operations including: decoding radio resource control (RRC) signaling, the RRC signaling including system information related to an Inter-Radio Access Technology (Inter-RAT) cell of a target base station, and system information including an indicator for supporting enhanced RRM measurements with the Inter-RAT cell; decoding configuration information from a source base station, the configuration information including a handover command for performing a handover from the source base station to the target base station; and determining whether to perform enhanced RRM measurements and a handover from the source base station to the target base station based on the enhanced RRM measurement support indicator with the Inter-RAT cell.

[0132] In Example 14, the subject matter of Example 13 includes not performing the enhanced RRM measurements and the handover from the source base station to the target base station if the UE does not support the enhanced RRM measurements for the inter-RAT cell.

[0133] In Example 15, the subject matter of Examples 13-14 includes the subject matter where the system information is System Information Block 5 (SIB5).

[0134] In Example 16, the subject matter of Examples 13-15 includes subject matter where the indicator indicates whether the Inter-RAT cell of the target base station supports enhanced RRM measurements when the UE is moving at a speed up to the threshold speed.

[0135] In Example 17, the subject matter of Example 16 includes subject matter where the threshold speed is 500 km / h.

[0136] In Example 18, the subject matter of Examples 16-17 further includes the operations including refraining from performing selection or reselection of the target base station based on the indication to support enhanced RRM measurements by the Inter-RAT cell.

[0137] In Example 19, the subject matter of Examples 13-18 further includes the operations including encoding an information element (IE) for transmission to a source base station via a physical uplink shared channel (PUSCH), the IE indicating UE capabilities related to supporting enhanced RRM measurements by the UE.

[0138] In Example 20, the subject matter of Example 19 includes km / h.

[0139] Example 21 includes at least one machine-readable medium including instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of examples 1-20.

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

[0141] Example 23 is a system implementing any of Examples 1 to 20.

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

[0143] Although certain aspects have been described with reference to specific exemplary aspects, 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 should be regarded in an illustrative rather than a restrictive sense. Thus, the specification is not to be construed in a restrictive sense, and the scope of the various aspects is defined only by the appended claims and all equivalents to which such claims are entitled.

Claims

1. 1. An apparatus configured to operate in a fifth generation new radio (5G NR) network, the apparatus being or being located in a user equipment (UE), the apparatus comprising: A processing circuit for configuring the UE for fast radio resource management (RRM) measurements in the 5G NR network, encoding capability information indicating whether the UE supports the RRM measurement at high speed for transmission to a base station; decoding system information received from the base station, the system information indicating that an Evolved Universal Terrestrial Radio Access (E-UTRA) carrier of an inter-RAT (inter-Radio Access Technology) Long-Term Evolution (LTE) cell supports the RRM measurements at high speed; and performing the RRM measurement at high speed in the inter-RAT LTE cell if the RRM measurement at high speed is configured by the base station and capability information indicates that the UE supports the RRM measurement at high speed; and a memory coupled to the processing circuit and configured to store the functional information; Including, The apparatus, wherein performing the RRM measurement at high speed in the inter-RAT LTE cell includes comparing a target LTE frequency set to be measured by the UE from the 5G NR network with LTE frequency information received via the system information, and determining whether the inter-Rat LTE cell is a cell capable of communicating with the UE.

2. The apparatus of claim 1 , wherein the capability information is a HighSpeedParameters information element (IE).

3. The apparatus of claim 1 , wherein the system information is System Information Block 5 (SIB5).

4. The base station is a source base station, the inter-RAT LTE cell is a cell of a target base station, the system information includes an indicator for fast support of the RRM measurement, and the processing circuitry: Decoding configuration information from the source base station, the configuration information including a handover command for performing a handover to the target base station; and The apparatus of claim 1 , further comprising: determining whether to perform a handover from the source base station to a target base station based on the indicator of fast support for the RRM measurements by the inter-RAT LTE cell.

5. The apparatus of claim 4 , wherein the processing circuitry is configured to not perform the RRM measurements and the handover from the source base station to the target base station if the UE does not support the RRM measurements at a high speed.

6. The apparatus of claim 5 , wherein the indicator indicates whether the inter-RAT LTE cell supports the RRM measurements when the UE is traveling at a speed up to a threshold speed.

7. 7. The apparatus of claim 6, wherein the threshold speed is 500 km / h.

8. The apparatus of claim 6 , wherein the processing circuitry does not select or reselect the target base station based on the indicator for supporting the RRM measurements by the inter-RAT LTE cell.

9. 5. The apparatus of claim 4, wherein the processing circuitry encodes an information element (IE) for transmission to the source base station via a physical uplink shared channel (PUSCH), the IE indicating UE capabilities related to supporting the RRM measurements by the UE.

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

11. A computer-readable non-transitory storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for radio resource management (RRM) measurements in a fifth generation new radio (5G NR) network, the instructions comprising: encoding capability information for transmission to a base station, the capability information indicating whether the UE supports the RRM measurements at high speed; decoding system information received from the base station, the system information indicating an Evolved Universal Terrestrial Radio Access (E-UTRA) carrier of an inter-RAT (inter-Radio Access Technology) Long-Term Evolution (LTE) cell indicating that the RRM measurement is supported at high speed; and performing the RRM measurement at high speed in the inter-RAT LTE cell if the RRM measurement at high speed is configured by the base station and the capability information indicates that the UE supports the RRM measurement at high speed; Perform an operation that includes The performing the RRM measurement at high speed in the inter-RAT LTE cell includes comparing a target LTE frequency set to be measured by the UE from the 5G NR network with LTE frequency information received via the system information, and determining whether the inter-Rat LTE cell is a cell capable of communicating with the UE. A computer-readable non-transitory storage medium.

12. The computer-readable non-transitory storage medium of claim 11 , wherein the capability information is a HighSpeedParameters information element (IE).

13. The computer-readable non-transitory storage medium of claim 11 , wherein the system information is System Information Block 5 (SIB5).

14. The base station is a source base station, the inter-RAT LTE cell is a cell of a target base station, the system information includes an indicator for fast support of the RRM measurement, and the operation includes: decoding configuration information from the source base station, the configuration information including a handover command for performing a handover from the source base station to the target base station; determining whether to perform the handover from the source base station to the target base station based on the indicator for supporting the RRM measurements at high speed by the inter-RAT LTE cell; The computer-readable non-transitory storage medium of claim 11 , further comprising:

15. The operations include not performing the RRM measurements and the handover from the source base station to the target base station if the UE does not support the RRM measurements at high speed; 15. The computer-readable non-transitory storage medium of claim 14, further comprising:

16. 16. The computer-readable non-transitory storage medium of claim 15, wherein the indicator indicates whether the inter-RAT LTE cell supports the RRM measurements when the UE is moving at a speed up to a threshold speed.

17. the operations including not performing selection or reselection of the target base station based on the indicator for supporting the RRM measurements by the inter-RAT LTE cell; 20. The computer-readable non-transitory storage medium of claim 16, further comprising:

18. The operations include encoding an information element (IE) for transmission to the source base station via a physical uplink shared channel (PUSCH), the IE indicating UE capabilities related to supporting the RRM measurements by the UE; 15. The computer-readable non-transitory storage medium of claim 14, further comprising:

Images