CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/332,836, which was filed April 20, 2022.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to a wireless network testing procedure. Specifically, embodiments may relate to a testing procedure of a pre-configured measurement gap (pre-MG).

BACKGROUND

Various embodiments generally may relate to the field of wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates an example of a testing procedure related to an activated pre-MG, in accordance with various embodiments.

Figure 2 illustrates an example of a testing procedure related to a deactivated pre-MG, in accordance with various embodiments.

Figure 3 schematically illustrates an example wireless network in accordance with various embodiments.

Figure 4 schematically illustrates example components of a wireless network in accordance with various embodiments.

Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figure 6 schematically illustrates an alternative example wireless network, in accordance with various embodiments.

Figure 7 depicts an example procedure for practicing the various embodiments discussed herein.

Figure 8 depicts an alternative example procedure for practicing the various embodiments discussed herein. DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Embodiments herein may relate to a testing procedure for the pre-configured test cases in which the multiple necessary functionalities of pre-MGs can be tested jointly.

Generally, the following test cases for a new radio (NR) Pre-MG may be evaluated:

• Activation delay test case for Pre-configured measurement gap

• Reporting delay test cases for NR standalone cells o Intra-frequency

In summary, the following example test cases for Pre-MG core requirement s), as depicted in Table 1, may be considered. It will be noted that this list of test cases is not intended to be exhaustive, and additional/other embodiments may have additional/other test cases.

Table 1: Example test cases for Pre-MG core requirements

Embodiment 1 :

However, in order to reduce the number of test cases as possible, if the testing procedure relatese to three successive time periods being included, both the requirements of Pre-MG activation/deactivation and intra-frequency measurement with gap can be tested together.

The testing procedure for the enhanced measurement gap may be based on the test procedure for the legacy measurement gap in the third generation partnership project (3 GPP) release-16 (Rell6, Rel-16, Rel 16, etc.) specifications. One difference between the legacy procedure and embodiments herein may be that the pre-MG activation/deactivation in the testing procedure may be needed herein.

The test cases for Pre-MG activation/deactivation delay and measurement reporting may be combined, for example as shown in the testing procedure in Figure 1.

The testing procedure for measurements with activated Pre-MG may include three successive time periods, with time durations of Tl, T2 and T3 respectively. During the duration of T 1 , the UE may be configured with Pre-MG, but the Pre-MG may be deactivated.

At the start of time duration T2, the serving base station (e.g., a gNodeB or gNB) may trigger Pre-MG activation. The UE may be expected to complete the Pre-MG activation within T2. At the start of time duration T3, the UE may not have timing information of neighbor cell(s) to be measured (e.g. cell 2).

Embodiment 2:

As illustrated in Figure 1, the testing procedure for measurements with activated Pre-MG may include three successive time periods, with time durations of Tl, T2 and T3 respectively.

During the duration of Tl, the UE may be configured with Pre-MG, but the Pre-MG may be deactivated.

At the start of time duration T2, the serving base station may trigger Pre-MG activation. The UE may be expected to complete the Pre-MG activation within T2.

At the start of time duration T3, the UE may not have timing information of neighbor cell(s) to be measured (e.g. cell 2).

The testing procedure for measurements with a deactivated Pre-MG may include two successive time periods, with time durations of Tl and T2, respectively, as shown in Figure 2.

During the duration of Tl, th UE may be configured with Pre-MG, but the pre-MG may be deactivated.

At the start of time duration T2, the UE may not have timing information of neighbor cell(s) to be measured (e.g. cell 2).

SYSTEMS AND IMPLEMENTATIONS

Figures 3-6 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 3 illustrates a network 300 in accordance with various embodiments. The network 300 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 regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection. The UE 302 may be communicatively coupled with the RAN 304 by a Uu interface. The UE 302 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

In some embodiments, the network 300 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 302 may additionally communicate with an AP 306 via an over-the-air connection. The AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304. The connection between the UE 302 and the AP 306 may be consistent with any IEEE 802.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 302, RAN 304, and AP 306 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.

The RAN 304 may include one or more access nodes, for example, AN 308. AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302. In some embodiments, the AN 308 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 308 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 304 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

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

The RAN 304 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 302 or AN 308 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) 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 the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 304 may be an LTE RAN 310 with eNBs, for example, eNB 312. The LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318. The gNB 316 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 316 and the ng-eNB 318 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).

The NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC 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 a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 302 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 302 and in some cases at the gNB 316. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 304 is communicatively coupled to CN 320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 302). The components of the CN 320 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 320 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.

In some embodiments, the CN 320 may be an LTE CN 322, which may also be referred to as an EPC. The LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.

The MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322. The SGW 326 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc. The S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.

The HSS 330 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 330 and the MME 324 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 320.

The PGW 332 may terminate an SGi interface toward a data network (DN) 336 that may include an application/content server 338. The PGW 332 may route data packets between the LTE CN 322 and the data network 336. The PGW 332 may be coupled with the SGW 326 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 332 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 332 and the data network 3 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 332 may be coupled with a PCRF 334 via a Gx reference point.

The PCRF 334 is the policy and charging control element of the LTE CN 322. The PCRF 334 may be communicatively coupled to the app/content server 338 to determine appropriate QoS and charging parameters for service flows. The PCRF 332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 320 may be a 5GC 340. The 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 340 may be briefly introduced as follows.

The AUSF 342 may store data for authentication of UE 302 and handle authentication- related functionality. The AUSF 342 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 340 over reference points as shown, the AUSF 342 may exhibit an Nausf service-based interface.

The AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302. The AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages. AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF. AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions. Furthermore, AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface.

The SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 302 and the data network 336.

The UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session. The UPF 348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 348 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 350 may select a set of network slice instances serving the UE 302. The NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354. The selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF. The NSSF 350 may interact with the AMF 344 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 350 may exhibit an Nnssf service-based interface.

The NEF 352 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 360), edge computing or fog computing systems, etc. In such embodiments, the NEF 352 may authenticate, authorize, or throttle the AFs. NEF 352 may also translate information exchanged with the AF 360 and information exchanged with internal network functions. For example, the NEF 352 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 352 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 352 may exhibit an Nnef service-based interface.

The NRF 354 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 354 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” 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 execution of program code. Additionally, the NRF 354 may exhibit the Nnrf service-based interface.

The PCF 356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 358. In addition to communicating with functions over reference points as shown, the PCF 356 exhibit an Npcf service-based interface. The UDM 358 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 302. For example, subscription data may be communicated via an N8 reference point between the UDM 358 and the AMF 344. The UDM 358 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 358 and the PCF 356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 302) for the NEF 352. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 358, PCF 356, and NEF 352 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 358 may exhibit the Nudm service-based interface.

The AF 360 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 340 may enable edge computing by selecting operator/3 ^rd party services to be geographically close to a point that the UE 302 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 340 may select a UPF 348 close to the UE 302 and execute traffic steering from the UPF 348 to data network 336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 360. In this way, the AF 360 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 360 is considered to be a trusted entity, the network operator may permit AF 360 to interact directly with relevant NFs. Additionally, the AF 360 may exhibit an Naf service-based interface.

The data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 338.

Figure 4 schematically illustrates a wireless network 400 in accordance with various embodiments. The wireless network 400 may include a UE 402 in wireless communication with an AN 404. The UE 402 and AN 404 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 402 may be communicatively coupled with the AN 404 via connection 406. The connection 406 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 402 may include a host platform 408 coupled with a modem platform 410. The host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410. The application processing circuitry 412 may run various applications for the UE 402 that source/sink application data. The application processing circuitry 412 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

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

The modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 414 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, 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.

The modem platform 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426. Briefly, the transmit circuitry 418 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 422 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 424 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 418, receive circuitry 420, RF circuitry 422, RFFE 424, and antenna panels 426 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

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

A UE reception may be established by and via the antenna panels 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414. In some embodiments, the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.

A UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426. In some embodiments, the transmit components of the UE 404 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 426.

Similar to the UE 402, the AN 404 may include a host platform 428 coupled with a modem platform 430. The host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430. The modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446. The components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402. In addition to performing data transmission/reception as described above, the components of the AN 408 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 500.

The processors 510 may include, for example, a processor 512 and a processor 514. The processors 510 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 discussed herein), or any suitable combination thereof.

The memory/storage devices 520 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 520 may include, but are not limited to, 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.

The communication resources 530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via a network 508. For example, the communication resources 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 510 to perform any one or more of the methodologies discussed herein. The instructions 550 may reside, completely or partially, within at least one of the processors 510 (e.g., within the processor’s cache memory), the memory/storage devices 520, or any suitable combination thereof. Furthermore, any portion of the instructions 550 may be transferred to the hardware resources 500 from any combination of the peripheral devices 504 or the databases 506. Accordingly, the memory of processors 510, the memory/storage devices 520, the peripheral devices 504, and the databases 506 are examples of computer-readable and machine-readable media.

Figure 6 illustrates a network 600 in accordance with various embodiments. The network 600 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 600 may operate concurrently with network 300. For example, in some embodiments, the network 600 may share one or more frequency or bandwidth resources with network 300. As one specific example, a UE (e.g., UE 602) may be configured to operate in both network 600 and network 300. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 300 and 600. In general, several elements of network 600 may share one or more characteristics with elements of network 300. For the sake of brevity and clarity, such elements may not be repeated in the description of network 600.

The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 608 via an over-the-air connection. The UE 602 may be similar to, for example, UE 302. The UE 602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

Although not specifically shown in Figure 6, in some embodiments the network 600 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 6, the UE 602 may be communicatively coupled with an AP such as AP 306 as described with respect to Figure 3. Additionally, although not specifically shown in Figure 6, in some embodiments the RAN 608 may include one or more ANss such as AN 308 as described with respect to Figure 3. The RAN 608 and/or the AN of the RAN 608 may be referred to as a base station (BS), a RAN node, or using some other term or name.

The UE 602 and the RAN 608 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

The RAN 608 may allow for communication between the UE 602 and a 6G core network (CN) 610. Specifically, the RAN 608 may facilitate the transmission and reception of data between the UE 602 and the 6G CN 610. The 6G CN 610 may include various functions such as NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, AF 360, SMF 346, and AUSF 342. The 6G CN 610 may additional include UPF 348 and DN 336 as shown in Figure 6. Additionally, the RAN 608 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 624 and a Compute Service Function (Comp SF) 636. The Comp CF 624 and the Comp SF 636 may be parts or functions of the Computing Service Plane. Comp CF 624 may be a control plane function that provides functionalities such as management of the Comp SF 636, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 636 may be a user plane function that serves as the gateway to interface computing service users (such as UE 602) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 636 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 636 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 624 instance may control one or more Comp SF 636 instances.

Two other such functions may include a Communication Control Function (Comm CF) 628 and a Communication Service Function (Comm SF) 638, which may be parts of the Communication Service Plane. The Comm CF 628 may be the control plane function for managing the Comm SF 638, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 638 may be a user plane function for data transport. Comm CF 628 and Comm SF 638 may be considered as upgrades of SMF 346 and UPF 348, which were described with respect to a 5G system in Figure 3. The upgrades provided by the Comm CF 628 and the Comm SF 638 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 346 and UPF 348 may still be used.

Two other such functions may include a Data Control Function (Data CF) 622 and Data Service Function (Data SF) 632 may be parts of the Data Service Plane. Data CF 622 may be a control plane function and provides functionalities such as Data SF 632 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 632 may be a user plane function and serve as the gateway between data service users (such as UE 602 and the various functions of the 6G CN 610) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

Another such function may be the Service Orchestration and Chaining Function (SOCF) 620, which may discover, orchestrate and chain up communication/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 620 may interact with one or more of Comp CF 624, Comm CF 628, and Data CF 622 to identify Comp SF 636, Comm SF 638, and Data SF 632 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 636, Comm SF 638, and Data SF 632 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 620 may also responsible for maintaining, updating, and releasing a created service chain.

Another such function may be the service registration function (SRF) 614, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 636 and Data SF 632 gateways and services provided by the UE 602. The SRF 614 may be considered a counterpart of NRF 354, which may act as the registry for network functions.

Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 626, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 612 and eSCP-U 634, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 626 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

Another such function is the AMF 644. The AMF 644 may be similar to 344, but with additional functionality. Specifically, the AMF 644 may include potential functional repartition, such as move the message forwarding functionality from the AMF 644 to the RAN 608.

Another such function is the service orchestration exposure function (SOEF) 618. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

The UE 602 may include an additional function that is referred to as a computing client service function (comp CSF) 604. The comp CSF 604 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 620, Comp CF 624, Comp SF 636, Data CF 622, and/or Data SF 632 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 604 may also work with network side functions to decide on whether a computing task should be run on the UE 602, the RAN 608, and/or an element of the 6G CN 610.

The UE 602 and/or the Comp CSF 604 may include a service mesh proxy 606. The service mesh proxy 606 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 606 may include one or more of addressing, security, load balancing, etc.

EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 3-6, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 7. The process of Figure 7 may include or relate to a method to be performed by a user equipment (UE) in a testing scenario, one or more elements of such a UE, and/or one or more electronic devices that include and/or implement such a UE. The process may include measuring, at 701, a value related to a wireless signal in a first time period where a pre-configured measurement gap (pre-MG) is disabled; measuring, at 702, a value related to a repetition of the wireless signal in a second time period that is subsequent to receipt of an indication to activate the pre-MG, and the measurement in the second time period is not performed based on the pre-MG; and measuring, at 703, a value related to a repetition of the wireless signal in a third time period, wherein the measurement in the third time period is performed based on the pre-MG.

Another such process is depicted in Figure 8. The process of Figure 8 may include or relate to a method to be performed by a base station in a testing scenario, one or more elements of such a base station, and/or one or more electronic devices that include and/or implement such a base station. The process may include transmitting, at 801 to a user equipment (UE) during a first time period in which a pre-configured measurement gap (pre-MG) is disabled at the UE, configuration information related to the pre-MG, wherein the UE is to perform a measurement of a value related to a wireless signal during the first time period; and transmitting, at 802 to the UE at a start of a second time period, an indication to activate the pre-MG, wherein the UE is to measure a value related to a repetition of the wireless signal in the second time period, and the measurement in the second time period is not performed based on the pre-MG; wherein the UE is further to measure a value related to a repetition of the wireless signal in a third time period, wherein the measurement in the third time period is performed based on the pre-MG.

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

EXAMPLES

Example 1 may include the method of UE testing procedure for NR measurements with the pre-configured gap.

Example 2 may include the method of example 1, and/or some other example herein, wherein the testing cases for pre-configured gap based measurements can be for measurement report period.

Example 3 may include the method of example 1, and/or some other example herein, wherein the testing cases for pre-configured gap based measurements can be for pre-configured gap activation/deactivation delay.

Example 4 may include the method of example 1, and/or some other example herein, wherein the testing procedure can be composed by three successive time periods, with time durations of Tl, T2 and T3 respectively.

Example 5 may include the method of example 4, and/or some other example herein, wherein during the duration of Tl, UE can be configured with Pre-MG but being deactivated .At the start of time duration T2, the serving gNB can trigger Pre-MG activation. And UE is expected to complete the Pre-MG activation within T2. At the start of time duration T3, the UE may not have any timing information of neighbor cell to be measured (e.g. cell 2).

Example 6 may include the method of example 5, and/or some other example herein, wherein with this procedure both the function of pre-configured gap activation and measurement delay can be tested jointly.

Example 7 includes a method to be performed by an electronic device, one or more components of the electronic device, or an apparatus that includes the electronic device, wherein the method comprises: performing a procedure to measure at least two pre-measurement gap (pre-MG) parameters; identifying, based on the performed procedure, an activation/deactivation parameter related to the pre-MG; and identifying, based on the performed parameter, an intra-frequency measurement related to the pre-MG.

Example 8 includes the method of example 7, and/or some other example herein, wherein the procedure is performed over three consecutive time periods.

Example 9 includes the method of example 8, and/or some other example herein, wherein the time periods correspond to different system configurations related to activation or deactivation of the pre-MG or timing information of a neighboring cell.

Example 10 includes the method of any of examples 7-9, and/or some other example herein, wherein the electronic device is a fifth generation (5G) nodeB (gNB).

Example 11 includes the method of any of examples 7-10, and/or some other example herein, wherein the pre-MG relates to a MG of a user equipment (UE).

Example 12 includes a method to be performed by a user equipment (UE) in a testing scenario, one or more elements of such a UE, and/or one or more electronic devices that include and/or implement such a UE, wherein the method comprises: measuring a value related to a wireless signal in a first time period where a pre-configured measurement gap (pre-MG) is disabled; measuring a value related to a repetition of the wireless signal in a second time period that is subsequent to receipt of an indication to activate the pre-MG, and the measurement in the second time period is not performed based on the pre-MG; and measuring a value related to a repetition of the wireless signal in a third time period, wherein the measurement in the third time period is performed based on the pre-MG.

Example 13 includes the method of example 12, and/or some other example herein, wherein the wireless signal is a synchronization signal block (SSB) that is transmitted from a neighbor cell.

Example 14 includes the method of example 13, and/or some other example herein, wherein the UE is configured to measure the value related to the repetition of the wireless signal in the third time period without pre-configured timing information of the neighbor cell.

Example 15 includes the method of any of examples 12-14, and/or some other example herein, wherein the indication to activate the pre-MG is received from a serving base station.

Example 16 includes the method of any of examples 12-15, and/or some other example herein, wherein the second time period relates to bandwidth part (BWP) switching by the UE based on activation of the pre-MG.

Example 17 includes the method of any of examples 12-16, and/or some other example herein, further comprising outputting, based on measured values in the first, second, and third time periods, an indication of an activation delay related to the pre-MG and an indication of measurement delay related to the wireless signal.

Example 18 includes the method of any of examples 12-17, and/or some other example herein, wherein the method comprises measuring a plurality of values that are respectively related to a plurality of repetitions of the wireless signal in the third time period.

Example 19 includes a method to be performed by a base station in a testing scenario, one or more elements of such a base station, and/or one or more electronic devices that include and/or implement such a base station, wherein the method comprises: transmitting, to a user equipment (UE) during a first time period in which a pre-configured measurement gap (pre-MG) is disabled at the UE, configuration information related to the pre-MG, wherein the UE is to perform a measurement of a value related to a wireless signal during the first time period; and transmitting, to the UE at a start of a second time period, an indication to activate the pre-MG, wherein the UE is to measure a value related to a repetition of the wireless signal in the second time period, and the measurement in the second time period is not performed based on the pre- MG; wherein the UE is further to measure a value related to a repetition of the wireless signal in a third time period, wherein the measurement in the third time period is performed based on the pre-MG.

Example 20 includes the method of example 19, and/or some other example herein, wherein the wireless signal is a synchronization signal block (SSB) that is transmitted from a neighbor cell.

Example 21 includes the method of example 20, and/or some other example herein, wherein the UE is configured to measure the value related to the repetition of the wireless signal in the third time period without pre-configured timing information of the neighbor cell.

Example 22 includes the method of any of examples 19-21, and/or some other example herein, wherein the second time period relates to bandwidth part (BWP) switching by the UE based on activation of the pre-MG.

Example 23 includes the method of any of examples 19-22, and/or some other example herein, wherein the UE is further configured to output, based on measured values in the first, second, and third time periods, an indication of an activation delay related to the pre-MG and an indication of measurement delay related to the wireless signal.

Example 24 includes the method of any of examples 19-23, and/or some other example herein, wherein the UE is configured to measure a plurality of values that are respectively related to a plurality of repetitions of the wireless signal in the third time period.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein. Example Z04 may include a method, technique, or process as described in or related to any of examples 1-24, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples 1-24, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

3 GPP Third and Mobility ASN. l Abstract

Generation Management Syntax Notation

Partnership Function One

Project AN Access AUSF

4G Fourth 40 Network 75 Authentication

Generation AnLF Server Function

5G Fifth Analytics AWGN

Generation Logical Function Additive White

5GC 5G Core ANR Gaussian Noise network 45 Automatic 80 BAP

AC Neighbour Relation Backhaul

Application AOA Adaptation Protocol

Client Angle of BCH

ACR Arrival Broadcast

Application 50 AP 85 Channel

Context Relocation Application BER Bit

ACK Protocol, Antenna Error Ratio

Acknowledgem Port, Access Point BFD Bea ent API m Failure Detection

ACID 55 Application 90 BLER Block

Application Programming Interface Error Rate

Client Identification APN Access BPSK Binary

ADRF Point Name Phase Shift Keying

Analytical Data ARP BRAS

Repository Function 60 Allocation and 95 Broadband

AF Retention Priority Remote Access

Application ARQ Server

Function Automatic BSS Business

AM Repeat Request Support System

Acknowledged 65 AS Access 100 BS Base Mode Stratum Station

AMBR ASP BSR Buffer

Aggregate Application Service Status Report

Maximum Bit Rate Provider BW

AMF Access 70 105 Bandwidth BWP Enhancement CM

Bandwidth Part CDM Content Connection

C-RNTI Delivery Network Management,

Cell Radio CDMA Conditional

Network 40 Code-Division 75 Mandatory

Temporary Multiple Access CMAS Identity CDR Commercial

CA Carrier Charging Data Mobile Alert Service

Aggregation, Request CMD

Certification 45 CDR 80 Command

Authority Charging Data CMS Cloud

CAPEX Response Management System

CAPital CFRA CO

Expenditure Contention Free Conditional

CBD 50 Random Access 85 Optional

Candidate CG Cell CoMP

Beam Detection Group Coordinated

CBRA CGF Multi-Point

Contention Charging Gateway CORESET

Based Random 55 Function 90 Control

Access CHF Resource Set

CC Charging Function COTS

Component CI Cell Commercial

Carrier, Country Identity Off-The-Shelf

Code, Cryptographic 60 CID Cell-ID 95 CP Control Checksum (e.g., positioning Plane, Cyclic Prefix,

CCA Clear method) Connection

Channel Assessment CIM Point

CCE Control Common CPD

Channel Element 65 Information Model 100 Connection

CCCH CIR Carrier Point Descriptor

Common to Interference CPE

Control Channel Ratio Customer

CE CK Cipher Premise

Coverage 70 Key 105 Equipment CPICH Service Archive Charging Trigger

Common Pilot CSI Function

Channel Channel -State CTS Clear-

CQI Channel Information to-Send Quality Indicator 40 CSI-IM 75 CW

CPU CSI CSI Codeword processing unit, Central Interference cws

Processing Unit Measurement Contention

C/R CSI-RS Window Size

Command/Resp 45 CSI Reference 80 D2D Device- onse field bit Signal to-Device

CRAN Cloud CSI-RSRP DC Dual

Radio Access CSI reference Connectivity, Direct

Network, Cloud signal received power Current RAN 50 CSI-RSRQ 85 DCI

CRB CSI reference Downlink

Common signal received quality Control

Resource Block CSI-SINR Information

CRC Cyclic CSI signal-to- DF Redundancy Check 55 noise and 90 Deployment

CRI interference Flavour

Channel-State ratio DL

Information CSMA Carrier Downlink

Resource Sense Multiple DMTF Indicator, CSI-RS 60 Access 95 Distributed

Resource CSMA/CA Management Task

Indicator CSMA with Force

C-RNTI collision DPDK Data

Cell RNTI avoidance Plane Development Kit

CS Circuit 65 CSS 100 DM-RS, DMRS

Switched Common Demodulation

CSCF Search Space, CellReference Signal call session specific Search DN Data control function Space network

CSAR Cloud 70 CTF 105 DNN Data Network Name ECCE Server

DNAI Data Enhanced EESID Network Access Control Channel Edge Enabler Identifier Element, Server Identification

40 Enhanced CCE 75 EHE

DRB Data ED Energy Edge Hosting Radio Bearer Detection Environment

DRS EDGE EGMF

Discovery Enhanced Exposure

Reference Signal 45 Datarates for GSM 80 Governance

DRX Evolution Management

Discontinuous (GSM Evolution) Function Reception EAS EGPRS

DSL Domain Edge Enhanced Specific Language. 50 Application Server 85 GPRS

Digital EASID EIR Subscriber Line Edge Equipment

DSLAM Application Server Identity Register

DSL Access Identification eLAA

Multiplexer 55 ECS 90 enhanced

DwPTS Edge Configuration Licensed Assisted

Downlink Pilot Server Access,

Time Slot ECSP enhanced LAA

E-LAN Edge Computing EM Element

Ethernet Local 60 Service Provider 95 Manager

Area Network EDN eMBB

E2E End-to- Edge Data Enhanced

End Network Mobile

EAS Edge EEC Broadband Application Server 65 Edge Enabler Client 100 EMS Element

ECCA EECID Management System extended clear Edge Enabler eNB evolved channel Client Identification NodeB, E-UTRAN assessment, EES Node B extended CCA 70 Edge Enabler 105 EN-DC E-UTRA-NR E-UTRAN FCC Federal

Dual Connectivity Evolved Communications

EPC Evolved UTRAN Commission

Packet Core EV2X FCCH

EPDCCH 40 Enhanced V2X 75 Frequency enhanced F1AP Fl Correction CHannel PDCCH, enhanced Application Protocol FDD

Physical Fl-C Fl Frequency Downlink Control Control plane interface Division Duplex

Cannel 45 Fl-U Fl User 80 FDM

EPRE Energy plane interface Frequency per resource element FACCH Division

EPS Evolved Fast Associated Multiplex

Packet System Control CHannel FDMA

EREG 50 FACCH/F 85 Frequency enhanced REG, Fast Associated Division Multiple enhanced resource Control Access element groups Channel/Full FE Front

ETSI rate End

European 55 FACCH/H 90 FEC Forward

Telecommunica Fast Associated Error Correction tions Standards Control FFS For Institute Channel/Half Further Study

ETWS rate FFT Fast

Earthquake and 60 FACH Forward 95 Fourier

Tsunami Warning Access Channel Transformation

System FAUSCH feLAA further eUICC Fast Uplink enhanced Licensed embedded Signalling Channel Assisted

UICC, embedded 65 FB 100 Access, further

Universal Functional enhanced LAA

Integrated Circuit Block FN Frame

Card FBI Number

E-UTRA Feedback FPGA Field-

Evolved UTRA 70 Information 105 Programmable Gate Array centralized unit UE Identity

FR gNB-DU HARQ Hybrid

Frequency gNB -distributed ARQ, Hybrid

Range unit, Next Automatic

FQDN Fully 40 Generation 75 Repeat Request Qualified Domain NodeB HANDO Name distributed unit Handover

G-RNTI GNSS Global HFN

GERAN Radio Navigation Satellite HyperFrame

Network 45 System 80 Number

Temporary GPRS General HHO Hard Identity Packet Radio Service Handover

GERAN GPSI G HLR Home

GSM EDGE eneric Public Location Register RAN, GSM EDGE 50 Subscription 85 HN Home

Radio Access Identifier Network Network GSM Global HO

GGSN Gateway System for Mobile Handover GPRS Support Communication HPLMN

Node 55 s, Groupe Special 90 Home Public

GLONASS Mobile Land Mobile Network

GLObal'naya GTP GPRS HSDPA

NAvigatsionnay Tunneling Protocol High Speed a Sputnikovaya GTP-UGPRS Downlink Packet Si sterna (Engl.: 60 Tunnelling Protocol 95 Access Global Navigation for User Plane HSN Hopping

Satellite GTS Go To Sequence Number

System) Sleep Signal (related HSPA High gNB Next to WUS) Speed Packet Access Generation NodeB 65 GUMMEI 100 HSS Home gNB-CU Globally Subscriber Server gNB- Unique MME HSUPA centralized unit, Next Identifier High Speed

Generation GUTI Globally Uplink Packet Access

NodeB 70 Unique Temporary 105 HTTP Hyper Text Transfer Protocol IEI IMPU IP

HTTPS Information Multimedia PUblic

Hyper Text Element identity Transfer Protocol Identifier IMS IP

Secure (https is 40 IEIDL 75 Multimedia Subsystem http/ 1.1 over Information IMSI SSL, i.e. port 443) Element International

I-Block Identifier Data Mobile

Information Length Subscriber

Block 45 IETF Internet 80 Identity

ICCID Engineering Task loT Internet

Integrated Force of Things

Circuit Card IF IP Internet

Identification Infrastructure Protocol

IAB 50 IIOT 85 Ipsec IP

Integrated Industrial Security, Internet

Access and Internet of Things Protocol

Backhaul IM Security

ICIC InterInterference IP-CAN

Cell Interference 55 Measurement, 90 IP-Connectivity

Coordination Intermodulation Access Network

ID Identity, , IP Multimedia IP-M IP identifier IMG IMS Multicast

IDFT Inverse Credentials IPv4 Internet

Discrete Fourier 60 IMEI 95 Protocol Version 4

Transform International IPv6 Internet

IE Mobile Protocol Version 6

Information Equipment IR Infrared element Identity IS In

IBE In-Band 65 IMGI 100 Sync

Emission International IRP

IEEE Institute mobile group identity Integration of Electrical and IMPI IP Reference Point

Electronics Multimedia Private ISDN

Engineers 70 Identity 105 Integrated Services Digital KQI Key LCID Lo Network Quality Indicator gical Channel ID ISIM IM KSI Key Set LI Layer Services Identity Identifier Indicator Module 40 ksps kilo- 75 LLC Logical

ISO symbols per second Link Control, Low International KVM Kernel Layer Organisation for Virtual Machine Compatibility Standardisation LI Layer 1 LMF ISP Internet 45 (physical layer) 80 Location Service Provider Ll-RSRP Management Function IWF Layer 1 LOS Interworking- reference signal Line of Sight Function received power LPLMN I-WLAN 50 L2 Layer 2 85 Local PLMN

Interworking (data link layer) LPP LTE WLAN L3 Layer 3 Positioning Protocol Constrai (network layer) LSB Least nt length of the LAA Significant Bit convolutional 55 Licensed 90 LTE Long code, USIM Assisted Access Term Evolution

Individual key LAN Local LWA LTE- kB Kilobyte Area Network WLAN aggregation (1000 bytes) LADN LWIP kbps kilo-bits 60 Local Area 95 LTE/WLAN per second Data Network Radio Level

Kc LBT Listen Integration with

Ciphering key Before Talk IPsec Tunnel

Ki LCM LTE Long

Individual 65 LifeCycle 100 Term Evolution subscriber Management M2M authentication LCR Low Machine-to- key Chip Rate Machine KPI Key LCS Location MAC Medium Performance Indicator 70 Services 105 Access Control (protocol Cell Group Management layering context) MCOT Information Base

MAC Message Maximum MIMO Multiple authentication code Channel Input Multiple (security/ encrypti on 40 Occupancy 75 Output context) Time MLC Mobile MAC-A MCS Location Centre

MAC used for Modulation and MM Mobility authentication coding scheme Management and key 45 MDAF 80 MME Mobility agreement Management Management Entity (TSG T WG3 context) Data Analytics MN Master

MAC-IMAC Function Node used for data integrity MDAS MNO of signalling 50 Management 85 Mobile Network messages (TSG Data Analytics Operator

T WG3 context) Service MO

MANO MDT Measurement

Management Minimization of Object, Mobile and Orchestration 55 Drive Tests 90 Originated

MBMS ME Mobile MPBCH

Multimedia Equipment MTC Physical

Broadcast and MeNB master Broadcast CHannel

Multicast eNB MPDCCH

Service 60 MER Message 95 MTC Physical

MBSFN Error Ratio Downlink Control

Multimedia MGL CHannel

Broadcast Measurement MPDSCH multicast Gap Length MTC Physical service Single 65 MGRP 100 Downlink Shared

Frequency Measurement CHannel

Network Gap Repetition MPRACH

MCC Mobile Period MTC Physical Country Code MIB Master Random Access

MCG Master 70 Information Block, 105 CHannel MPUSCH s Dual Connectivity

MTC Physical MTLF Model NEF Network Uplink Shared Training Logical Exposure Function

Channel Function NF Network

MPLS 40 mMTC massive 75 Function

MultiProtocol MTC, massive NFP Network

Label Switching Machine-Type Forwarding Path

MS Mobile Communication NFPD Network

Station s Forwarding Path

MSB Most 45 MU-MIMO 80 Descriptor Significant Bit Multi User NFV Network

MSC Mobile MIMO Functions Switching Centre MWUS Virtualization

MSI MTC wake-up NFVI NFV

Minimum 50 signal, MTC WUS 85 Infrastructure

System NACK NFVO NFV

Information, Negative Orchestrator MCH Scheduling Acknowledgement NG Next Information NAI Network Generation, Next Gen

MSID Mobile 55 Access Identifier 90 NGEN-DC Station Identifier NAS Non- NG-RAN E-

MSIN Mobile Access Stratum, Non- UTRA-NR Dual

Station Access Stratum Connectivity

Identification layer NM Network

Number 60 NCT Network 95 Manager

MSISDN Connectivity NMS Network

Mobile Topology Management System

Subscriber ISDN NC-JT N-PoP Network

Number Non-Coherent Joint Point of Presence

MT Mobile 65 Transmission 100 NMIB, N-MIB Terminated, Mobile NEC Network Narrowband MIB

Termination Capability NPBCH

MTC Exposure Narrowband

Machine-Type NE-DC Physical Communication 70 NR-E-UTRA 105 Broadcast CHannel Narrowband type 2

NPDCCH Reference Signal OFDM

Narrowband NS Network Orthogonal

Physical Service Frequency Division

Downlink 40 NSA Non- 75 Multiplexing

Control CHannel Standalone operation OFDMA

NPDSCH mode Orthogonal

Narrowband NSD Network Frequency Division

Physical Service Descriptor Multiple Access

Downlink 45 NSR Network 80 OOB Out-of-

Shared CHannel Service Record band

NPRACH NSSAINetwork OOS Out

Narrowband Slice Selection of Sync

Physical Random Assistance OPEX

Access CHannel 50 Information 85 OPerating

NPUSCH S-NNSAI EXpense

Narrowband Single-NSSAI OSI Other

Physical Uplink NSSF Network System Information

Shared CHannel Slice Selection OSS

NPSS 55 Function 90 Operations

Narrowband NW Network Support System

Primary NWDAF OTA over-

Synchronization Network Data the-air Signal Analytics Function PAPR Peak-to-

NSSS 60 NWUS 95 Average Power

Narrowband Narrowband Ratio

Secondary wake-up signal, PAR Peak to

Synchronization N arrowb and WU S Average Ratio Signal NZP NonPBCH Physical

NR New 65 Zero Power 100 Broadcast Channel

Radio, Neighbour O&M PC Power

Relation Operation and Control, Personal

NRF NF Maintenance Computer

Repository Function ODU2 Optical PCC Primary

NRS 70 channel Data Unit - 105 Component Carrier, Primary CC Downlink Shared Record

P-CSCF Channel POC PTT

Proxy CSCF PDU Protocol over Cellular

PCell Primary Data Unit PP, PTP

Cell 40 PEI 75 Point-to-Point

PCI Physical Permanent PPP Point-to-

Cell ID, Physical Equipment Point Protocol

Cell Identity Identifiers PRACH

PCEF Policy PFD Packet Physical RACH and Charging 45 Flow Description 80 PRB Physical

Enforcement P-GW PDN resource block

Function Gateway PRG Physical

PCF Policy PHICH resource block Control Function Physical group

PCRF Policy 50 hybrid-ARQ indicator 85 ProSe

Control and Charging channel Proximity

Rules Function PHY Physical Services,

PDCP Packet layer Proximity-

Data Convergence PLMN Public Based Service

Protocol, Packet 55 Land Mobile Network 90 PRS

Data Convergence PIN Personal Positioning

Protocol layer Identification Number Reference Signal

PDCCH PM PRR Packet

Physical Performance Reception Radio

Downlink Control 60 Measurement 95 PS Packet

Channel PMI Services

PDCP Packet Precoding PSBCH

Data Convergence Matrix Indicator Physical

Protocol PNF Physical Sidelink Broadcast

PDN Packet 65 Network Function 100 Channel

Data Network, PNFD Physical PSDCH

Public Data Network Function Physical

Network Descriptor Sidelink Downlink

PDSCH PNFR Physical Channel

Physical 70 Network Function 105 PSCCH Physical QCL Quasi RAT Radio

Sidelink Control co-location Access Technology

Channel QFI QoS RAU Routing

PSSCH Flow ID, QoS Flow Area Update

Physical 40 Identifier 75 RB

Sidelink Shared QoS Quality Resource block,

Channel of Service Radio Bearer

PSFCH QPSK RBG physical sidelink Quadrature Resource block feedback channel 45 (Quaternary) Phase 80 group

PSCell Primary Shift Keying REG

SCell QZSS Quasi - Resource

PSS Primary Zenith Satellite Element Group Synchronization System Rel Release

Signal 50 RA-RNTI 85 REQ

PSTN Public Random Access REQuest

Switched Telephone RNTI RF Radio

Network RAB Radio Frequency

PT-RS PhaseAccess Bearer, RI Rank tracking reference 55 Random Access 90 Indicator signal Burst RIV

PTT Push-to- RACH Random Resource

Talk Access Channel indicator value

PUCCH RADIUS RL Radio

Physical Uplink 60 Remote 95 Link

Control Channel Authentication Dial RLC Radio

PUSCH In User Service Link Control, Radio

Physical Uplink RAN Radio Link Control

Shared Channel Access Network layer

QAM 65 RAND 100 RLC

Quadrature RANDom AM RLC

Amplitude number (used for Acknowledged Mode

Modulation authentication) RLC

QCI QoS RAR Random UM RLC class of identifier 70 Access Response 105 Unacknowledged Mode Control layer Application Protocol

RLF Radio RRM Radio SI -MME

Link Failure Resource SI for the

RLM Radio Management control plane Link Monitoring 40 RS 75 Sl-U SI for

RLM-RS Reference the user plane

Reference Signal S-CSCF

Signal for RLM RSRP serving CSCF

RM Reference S-GW Serving Registration 45 Signal Received 80 Gateway

Management Power S-RNTI

RMC RSRQ SRNC Radio

Reference Reference Network

Measurement Channel Signal Received Temporary RMSI 50 Quality 85 Identity

Remaining RS SI S-TMSI

MSI, Remaining Received Signal SAE

Minimum Strength Temporary Mobile

System Indicator Station Information 55 RSU Road 90 Identifier

RN Relay Side Unit SA

Node RSTD Standalone

RNC Radio Reference operation mode

Network Controller Signal Time SAE System RNL Radio 60 difference 95 Architecture

Network Layer RTP Real Evolution

RNTI Radio Time Protocol SAP Service

Network Temporary RTS Ready- Access Point

Identifier To-Send SAPD Service ROHC RObust 65 RTT Round 100 Access Point

Header Trip Time Descriptor

Compression Rx SAPI Service

RRC Radio Reception, Access Point

Resource Control, Receiving, Receiver Identifier Radio Resource 70 S1AP SI 105 see Secondary SDNF SI System

Component Carrier, Structured Data Information

Secondary CC Storage Network SI-RNTI

SCell Function System

Secondary Cell 40 SDP Session 75 Information RNTI

SCEF Description Protocol SIB System

Service SDSF Information Block

Capability Exposure Structured Data SIM

Function Storage Function Subscriber

SC-FDMA 45 SDT Small 80 Identity Module

Single Carrier Data Transmission SIP Session

Frequency Division SDU Service Initiated Protocol

Multiple Access Data Unit SiP System

SCG SEAF Security in Package

Secondary Cell 50 Anchor Function 85 SL Sidelink

Group SeNB SLA Service

SCM Security secondary eNB Level Agreement

Context SEPP Security SM Session

Management Edge Protection Management SCS 55 Proxy 90 SMF Session

Subcarrier SFI Slot Management Function

Spacing format indication SMS Short

SCTP Stream SFTD Space- Message Service

Control Frequency Time SMSF SMS

Transmission 60 Diversity, SFN 95 Function

Protocol and frame timing SMTC S SB¬

SDAP Service difference based Measurement

Data Adaptation SFN System Timing

Protocol, Frame Number Configuration

Service Data 65 SgNB 100 SN

Adaptation Secondary gNB Secondary

Protocol layer SGSN Serving Node, Sequence

SDL GPRS Support Node Number

Supplementary S-GW Serving SoC System

Downlink 70 Gateway 105 on Chip SON SelfSynchronization SU-MIMO

Organizing Network Signal Block Single User

SpCell Special Resource MI MO

Cell Indicator SUL

SP-CSI- 40 SSC Session 75 Supplementary

RNTISemi-Persistent and Service Uplink

CSI RNTI Continuity TA Timing

SPS Semi- SS-RSRP Advance, Tracking

Persistent Scheduling Synchronization Area

SQN 45 Signal based 80 TAC

Sequence Reference Tracking Area number Signal Received Code

SR Power TAG Timing

Scheduling SS-RSRQ Advance Group

Request 50 Synchronization 85 TAI

SRB Signal based Tracking Area

Signalling Reference Identity

Radio Bearer Signal Received TAU

SRS Quality Tracking Area

Sounding 55 SS-SINR 90 Update

Reference Signal Synchronization TB

SS Signal based Signal Transport Block

Synchronization to Noise and TBS

Signal Interference Ratio Transport Block

SSB 60 SSS 95 Size

Synchronization Secondary TBD To Be

Signal Block Synchronization Defined

SSID Servic Signal TCI e Set Identifier SSSG Search Transmission

SS/PBCH 65 Space Set Group 100 Configuration

Block SSSIF Search Indicator

SSBRI Space Set Indicator TCP

SS/PBCH SST Transmission

Block Resource Slice/Service Communication

Indicator, 70 Types 105 Protocol TDD Time TRS UDSF

Division Duplex Tracking Unstructured

TDM Time Reference Signal Data Storage Network

Division Multiplexing TRx Function

TDMATime 40 Transceiver 75 UICC

Division Multiple TS Universal

Access Technical Integrated Circuit

TE Specifications, Card

Terminal Technical UL Uplink

Equipment 45 Standard 80 UM

TEID Tunnel TTI Unacknowledge

End Point Identifier Transmission d Mode

TFT Traffic Time Interval UML Unified

Flow Template Tx Modelling Language

TMSI 50 Transmission, 85 UMTS

Temporary Transmitting, Universal

Mobile Transmitter Mobile

Subscriber U-RNTI Tel ecommuni ca

Identity UTRAN Radio tions System

TNL 55 Network 90 UP User

Transport Temporary Plane

Network Layer Identity UPF User

TPC UART Plane Function

Transmit Power Universal URI Uniform

Control 60 Asynchronous 95 Resource Identifier

TPMI Receiver and URL Uniform

Transmitted Transmitter Resource Locator

Precoding Matrix UCI Uplink URLLC

Indicator Control Information Ultra-Reliable

TR 65 UE User 100 and Low Latency

Technical Equipment USB

Report UDM Unified Universal Serial

TRP, TRxP Data Management Bus

Transmission UDP User USIM

Reception Point 70 Datagram Protocol 105 Universal Subscriber Identity Network Function Control plane Module VNFFG X2-U X2-User

USS UE- VNF plane specific search space Forwarding Graph XML

UTRA UMTS 40 VNFFGD 75 extensible

Terrestrial Radio VNF Markup

Access Forwarding Graph Language

UTRAN Descriptor XRES

Universal VNFMVNF EXpected user

Terrestrial Radio 45 Manager 80 RESponse

Access VoIP Voice- XOR

Network over-IP, Voice-over- exclusive OR

UwPTS Internet ZC Zadoff-

Uplink Pilot Protocol Chu

Time Slot 50 VPLMN 85 ZP Zero

V2I Vehicle- Visited Public Power to-Infrastruction Land Mobile Network

V2P Vehicle- VPN Virtual to-Pedestrian Private Network

V2V Vehicle- 55 VRB Virtual to-Vehicle Resource Block

V2X Vehicle- WiMAX to-everything Worldwide

VIM Interoperability

Virtualized 60 for Microwave

Infrastructure Manager Access

VL Virtual WLANWireless

Link, Local Area Network

VLAN Virtual WMAN

LAN, Virtual Local 65 Wireless

Area Network Metropolitan Area

VM Virtual Network

Machine WPANWireless

VNF Personal Area Network

Virtualized 70 X2-C X2- Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AI/ML application” or the like may be an application that contains some AI/ML models and application-level descriptions.

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

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.