Measurement delay for simultaneous reception of multiple reception chains

Abstract

Various embodiments of the present application provide techniques for defining measurement periods and / or alternative measurement configurations of user equipment (UE) for simultaneous reception (e.g., using multiple antenna panels). The UE may perform measurements on each reference signal (RS) and / or resource. The required measurement period may depend on one or more factors, such as whether the receiving (RX) beam sweep factor and / or RS overlap. Other embodiments are described and may be claimed.

Description

Background Art

[0001] Cross - reference to related applications This application claims priority to U.S. Provisional Patent Application No. 63 / 494,956, filed Apr. 7, 2023. Background User equipment (UE) in a wireless cellular network performs measurements on respective reference signals for various purposes. The UE requires a measurement delay to perform the measurements, which is typically defined in the specifications of the Third Generation Partnership Project (3GPP®).

Brief Description of the Drawings

[0002] Embodiments will be readily understood by the following detailed description in connection with the accompanying drawings. For the sake of ease of explanation, like reference numerals denote like structural elements. Embodiments are shown in the figures of the accompanying drawings by way of example and not as a limitation.

[0003] [Figure 1] A wireless network according to various embodiments is schematically shown. [Figure 2] Components of a wireless network according to various embodiments are schematically shown. [Figure 3] A block diagram showing components that can read instructions from a machine - readable or computer - readable medium (e.g., a non - transitory machine - readable storage medium) and execute any one or more of the methodologies described herein. [Figure 4] A network according to various embodiments is shown. [Figure 5] Exemplary procedures for implementing various embodiments herein are shown.

Modes for Carrying Out the Invention

[0004] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details such as particular structures, architectures, interfaces, and techniques are described for illustrative purposes only, not limiting purposes, to provide a full understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who are interested in this disclosure that various aspects of the various embodiments may be practiced in other examples that deviate from these particular details. In certain cases, descriptions of well-known devices, circuits, and methods are omitted so as not to bury the description of the various embodiments with unnecessary details. For the purposes of this specification, the terms "A or B" and "A / B" mean (A), (B), or (A and B).

[0005] Various embodiments of this specification define measurement periods and / or alternative measurement configurations for user equipment (UE) for simultaneous reception (e.g., using multiple antenna panels). The UE may perform measurements on each reference signal (RS) and / or resource. Measurement delays have not been previously defined for simultaneous reception using multiple panels. There are several types of resources for measurement. The required measurement period may depend on one or more factors, such as whether the receiving (RX) beam sweep factor and / or RS are overlapping. Various embodiments of this specification may define measurement periods for various measurement configurations, for example, for simultaneous reception.

[0006] Definition of measurement period In legacy Layer 1 (L1) - Reference Signal Received Power (RSRP) reporting, one resource set is configured. The L1 measurement period is defined for each RS within that resource set.

[0007] In group-based reporting, two resource sets are constructed. For example, there may be two transmit / receive points (TRPs), each TRP having one resource set. Each resource set may contain multiple RSs.

[0008] In the embodiment, there may be different types of resource configurations used for L1 measurement in group-based reporting. For example, the resource configurations may be as follows: 1. A resource set based on two synchronization signal blocks (SSBs). 2. Two RS-based resource sets of channel state information (CSI) with iteration turned off. 3. One SSB-based resource set and one CSI-RS-based resource set with iteration turned off.

[0009] In some embodiments, the measurement period can be defined on each RS, for example, how long a measurement time is required for one RS.

[0010] In some embodiments, for SSB-based resource sets, the corresponding measurement period may be based on the RX beam sweep factor.

[0011] Definition of RX beam sweeping factor There are different possible implementations for the UE to perform RX beam sweep. For example, the UE may use one of the following cases: 1. Sweep the RX beam across the entire spatial range without any prior measurement information. 2. Using the previously measured data, the RX beam is swept over the reduced spatial range.

[0012] Case 1 can be considered a worst-case scenario because the UE has no prior information. For one RS, the UE needs to sweep the RX beam over the entire spatial range covered by two antenna panels. The UE needs to measure the RS using the two panels and then select the better one (e.g., the one with higher signal power and / or quality). In legacy implementations, the UE sweeps the beam over the two panels using a time-division multiplexing (TDM) scheme. If the beam sweep factor N is defined as N=8, it means that for full coverage using the two panels, the UE must sweep a total of eight beams. For each panel, the UE can sweep four beams. If the UE is capable of simultaneous reception, the UE can sweep two beams in parallel on each of the two panels, so the total number of RX beam sweeps can be reduced from eight to four.

[0013] In Case 2, if the UE has previous Layer 3 (L3) measurement information, it may know which panel performs better for RS. Therefore, the UE only needs to sweep the RX beam over a reduced spatial range. In this case, the number of beams can be reduced compared to the number of beams required for a full spatial sweep. In some implementations, it is up to the UE whether to still sweep with more beams. If the UE can reduce the RX beam sweep range to one panel, the UE may only need four beams or fewer.

[0014] Using previous information, the spatial range can be reduced, which in turn reduces the number of RX beams that need to be swept. Therefore, the RX beam sweep factor should be defined in terms of the worst-case scenario, for example, the number of beam sweeps required for complete spatial range. For complete spatial coverage, the UE needs to sweep on two panels for one RS.

[0015] As described above, for the two cases, the maximum number of RX beam sweeps is 4. Therefore, for the simultaneous reception scenario, the UE can reduce the RX beam sweep factor from 8 to 4.

[0016] Measurement period when two SSB resource sets are configured. In some embodiments of this specification, the RX beam sweep factor can be defined based on a worst-case scenario, for example, when the UE needs to sweep the RX beams for RS on two panels for L1 measurement. In that case, the RX beam sweep factor can be reduced from 8 to 4.

[0017] In some embodiments, since the two SSB resource sets do not overlap for the in-cell multi-TRP (mTRP) case, there may be no need to consider the overlapping cases for the two L1 measurements. Furthermore, the requirements can be restricted so that simultaneous L3 and L1 measurements are not performed. Since the RX beam sweep factor is reduced, the total measurement period for one RS will be reduced.

[0018] For example, Table 1 shows the measurement periods for SSB-based L1-RSRP measurements for different discontinuous reception (DRX) configurations in Frequency Range 2 (FR2) according to various embodiments.

Table 1

[0019] Measurement period when two CSI-RS resource sets are configured. Embodiments can define the requirements when the two CSI-RS resource sets are configured with iterative off.

[0020] In some embodiments, when two CSI-RS resource sets are configured with repetition off, RX beam sweeping is not required (e.g., N = 1). The configured CSI-RS should be of quasi co-located (QCL) type D with one previously measured source SSB or CSI-RS.

[0021] Legacy requirement applicability is as follows: For periodic CSI-RS resources within a resource set configured with the upper layer parameter repetition set to OFF, N = 1. qcl-InfoPeriodicCSI-RS is configured for all resources within the resource set, and each resource has one RS · SSB for L1-RSRP measurement, or · Another CSI-RS in a resource set configured with repetition ON with QCL-Type D.

[0022] In a resource set for group-based reporting, since there is no repeating CSI-RS, the requirement applicability needs to be modified.

[0023] Duplicate RS Two CSI-RSs with repetition off from two sets can overlap on the same symbol. The UE can measure two overlapping CSI-RSs using two panels simultaneously. A common factor between the overlapping RSs is not required. For CSI-RS, since repetition is off, an RX beam sweeping factor is not required for the measurement period.

[0024] For example, Table 2 shows the measurement periods for CSI-RS based L1-RSRP measurement in FR2 according to various embodiments.

Table 2

[0025] Measurement period when one SSB resource set and one CSI-RS resource set are configured. In some embodiments, for a mixed configuration with one SSB resource set and one CSI-RS resource set, RX beam sweep is applied to the SSB resources, but not to the CSI-RS resources.

[0026] If the SSB and CSI-RS resources do not overlap, the UE applies L1 measurements to them separately. The measurement period for SSB or CSI-RS may be the same as when two sets of SSB resources or two sets of CSI-RS resources are configured.

[0027] When SSB resources and CSI-RS overlap, the requirements may differ. For example, for SSB measurements, the UE may need to sweep on two panels. If two panels are used simultaneously for SSB measurements, the UE cannot receive CSI-RS on the same symbol. According to various embodiments, some exemplary options for when there is an overlap include:

[0028] 1. The UE measures SSB and CSI-RS using the TDM method. For example, the UE first measures SSB using two panels, and then measures CSI-RS. Shared factors may be added to the measurement period. 2. The UE measures SSB and CSI-RS simultaneously. The measurement time for SSB is extended. 3. Define measurement limits. For example, in this case, the UE is not required to measure both signals.

[0029] System and Implementation Figures 1 to 4 show various systems, devices, and components that can implement aspects of the disclosed embodiments.

[0030] Figure 1 shows Network 100 in various embodiments. Network 100 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0031] Network 100 may include UE 102, which may include any mobile or non-mobile computing device designed to communicate with RAN 104 via a wireless connection. UE 102 may be coupled to RAN 104 in a communicative manner via a Uu interface. UE 102 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0032] In some embodiments, the network 100 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH, but are not limited to these.

[0033] In some embodiments, UE 102 may further communicate with AP 106 via a wireless connection. AP 106 may manage a WLAN connection that can function to offload some / all network traffic from RAN 104. The connection between UE 102 and AP 106 may be compatible with any IEEE 802.11 protocol, where AP 106 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, UE 102, RAN 104, and AP 106 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may include UE 102 being configured by RAN 104 to utilize both cellular radio resources and WLAN resources.

[0034] RAN 104 may include one or more access nodes, for example, AN 108. AN 108 may terminate the air interface protocol for UE 102 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 108 may enable data / voice connectivity between CN 120 and UE 102. In some embodiments, AN 108 may be implemented as one or more software entities running on a discrete device or on a server computer as part of a virtual network which may be called CRAN or virtual baseband unit pool. AN 108 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 108 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

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

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

[0037] RAN 104 may provide an air interface through licensed or unlicensed spectra. To operate in unlicensed spectra, nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / SCell. Prior to accessing unlicensed spectra, nodes may perform medium / carrier detection operations, for example, based on a listen-before-talk (LBT) protocol.

[0038] In a V2X scenario, UE 102 or AN 108 may be or act as an RSU. An RSU can refer to any transport infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU may be called a “UE-type RSU” if it is implemented in or by a UE; an “eNB-type RSU” if it is an eNB; a “gNB-type RSU” if it is a gNB, and so on. In one example, an RSU is a roadside computing device coupled to radio frequency circuitry that provides connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, an RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

[0039] In some embodiments, RAN 104 may be an LTE RAN 110 having an eNB, for example, eNB 112. The LTE RAN 110 may provide an LTE air interface having the following characteristics: 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo coding for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and on CRS for cell discovery and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection in the UE. The LTE air interface may operate in the sub-6 GHz band.

[0040] In some embodiments, the RAN 104 may be an NG-RAN 114 having a gNB, for example, gNB 116, or an ng-eNB, for example, ng-eNB 118. The gNB 116 may connect to a 5G-enabled UE using a 5G NR interface. The gNB 116 may connect to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 118 may also connect to the 5G core through an NG interface, but may connect to the UE via an LTE air interface. The gNB 116 and ng-eNB 118 may connect to each other through an Xn interface.

[0041] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the NG-RAN114 nodes and the UPF 148, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN114 nodes and the AMF 144.

[0042] NG-RAN 114 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, iterative, 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 CRS but may use PBCH DMRS for PBCH demodulation; may use PTRS for phase tracking for PDSCH; and may use a tracking reference signal for time tracking. The 5G-NR air interface may operate on the FR1 band, including the sub-6GHz band, or the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSB, which is the area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0043] In some embodiments, a 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, UE 102 may consist of multiple BWPs, each with a different SCS. When a BWP change is indicated to UE 102, the SCS for transmission is also changed. Another use case for BWPs relates to power saving. In particular, multiple BWPs may be configured for UE 102 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs may be used for data transmission with small traffic loads, allowing power saving in UE 102 and, in some cases, in gNB 116. BWPs with more PRBs may be used for scenarios with higher traffic loads.

[0044] RAN 104 is communicatively coupled to CN 120, which contains network elements for providing various functions to support data and telecommunications services to customers / subscribers (e.g., users of UE 102). The components of CN 120 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV can be used to virtualize some or all of the functions provided by the network elements of CN 120 on physical computing / storage resources such as servers and switches. Logical instantiations of CN 120 may be called network slices, and some logical instantiations of CN 120 may be called network subslices.

[0045] In some embodiments, CN 120 may be LTE CN 122, sometimes referred to as EPC. LTE CN 122 may include MME 124, SGW 126, SGSN 128, HSS 130, PGW 132, and PCRF 134 coupled to one another through an interface (or “reference point”), as shown in the figure. The functions of the elements of LTE CN 122 can be briefly described below.

[0046] The MME 124 can implement mobility management capabilities to track the current location of the UE 102, facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0047] SGW 126 terminates the S1 interface toward the RAN and can route data packets between the RAN and LTE CN 122. SGW 126 may also be a local mobility anchor point for inter-RAN node handover and may provide an anchor for 3GPP inter-mobility. Other responsibilities may include lawful interception, billing, and any policy enforcement.

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

[0049] HSS 130 may include a database for network users, containing subscription-related information to support the handling of communication sessions by network entities. HSS 130 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between HSS 130 and MME 124 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to LTE CN 120.

[0050] PGW 132 may terminate an SGi interface toward a data network (DN) 136, which may include an application / content server 138. PGW 132 may route data packets between the LTE CN 122 and the data network 136. PGW 132 may be coupled with SGW 126 by an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 132 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. Furthermore, the SGi reference point between PGW 132 and the data network 136 may be an external public, private PDN, or intra-operator packet data network, for example, for providing IMS services. PGW 132 may be coupled with PCRF 134 via a Gx reference point.

[0051] PCRF 134 is the policy and billing control element of LTE CN 122. PCRF 134 can be communicatively coupled to the app / content server 138 to determine appropriate QoS and billing parameters for the service flow. PCRF 132 can provision the relevant rules to the PCEF (via the Gx reference point) with appropriate TFT and QCI.

[0052] In some embodiments, CN 120 may be 5GC 140. 5GC 140 may include AUSF 142, AMF 144, SMF 146, UPF 148, NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, and AF 160, coupled to one another through an interface (or "reference point"), as shown in the figure. The functions of the elements of 5GC 140 can be briefly described below.

[0053] The AUSF 142 can store data for authentication of the UE 102 and handle authentication-related functions. The AUSF 142 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 140 through the reference point, as shown, the AUSF 142 can present a Nausf service-based interface.

[0054] The AMF 144 may allow other functions of the 5GC 140 to communicate with the UE 102 and RAN 104 and subscribe to notifications about mobility events concerning the UE 102. The AMF 144 may be responsible for registration management (e.g., for registering the UE 102), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 144 may provide transport for SM messages between the UE 102 and the SMF 146 and act as a transparent proxy for routing SM messages. The AMF 144 may also provide transport for SMS messages between the UE 102 and the SMSF. The AMF 144 may interact with the AUSF 142 and UE 102 to perform various security anchor and context management functions. Furthermore, AMF 144 may be the endpoint of the RAN CP interface, including or potentially being the N2 reference point between RAN 104 and AMF 144; AMF 144 may be the endpoint of NAS(N1) signaling, performing NAS encryption and integrity protection. AMF 144 may also support NAS signaling with UE 102 via the N3 IWF interface.

[0055] SMF 146 may be responsible for SM (e.g., session establishment, tunnel management between UPF 148 and AN 108); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in UPF 148 for routing traffic to appropriate destinations; interface termination toward policy control functions; control of policy enforcement, billing, and some QoS; legal interception (for SM events and interface to LI systems); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information transmitted to AN 108 via AMF 144 through N2; and determination of the session's SSC mode. SM may also refer to the management of PDU sessions, and PDU session or “session” may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 102 and data network 136.

[0056] UPF 148 can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 136, and a branch point to support multi-homed PDU sessions. UPF 148 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 148 may include an uplink classifier to support routing of traffic flows to the data network.

[0057] NSSF 150 may select a set of network slice instances to serve UE 102. NSSF 150 may also determine, if necessary, the allowed NSSAIs and their mappings to subscribed S-NSSAIs. NSSF 150 may also determine, based on appropriate configuration and possibly by querying NRF 154, a set of AMFs, or a list of candidate AMFs, to be used to serve UE 102. The selection of a set of network slice instances for UE 102 may also be triggered by AMF 144, to which UE 102 registers by interacting with NSSF 150, which may result in a change of AMF. NSSF 150 may interact with AMF 144 via the N22 reference point and may communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, NSSF 150 may represent an Nnssf service-based interface.

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

[0059] NRF 154 supports service discovery functionality, receiving NF discovery requests from NF instances and providing NF instances with information about discovered NF instances. NRF 154 also maintains information about available NF instances and their supported services. Where used herein, terms such as “instantiate” and “instantiate” can refer to the creation of an instance, and “instance” can refer to the specific occurrence of an object, for example, during the execution of program code. In addition, NRF 154 can represent an Nnrf service-based interface.

[0060] PCF 156 can provide control plane functions with the authority to enforce policy rules and may also support a unified policy framework to govern network behavior. PCF 156 can also implement a front-end for accessing subscription information relevant to policy decisions in the UDR of UDM 158. In addition to communicating with functions through reference points as shown in the diagram, PCF 156 provides an Npcf service-based interface.

[0061] UDM 158 may process subscription-related information to support the processing of communication sessions of network entities and may store subscription data for UE 102. For example, subscription data may be communicated via an N8 reference point between UDM 158 and AMF 144. UDM 158 may consist of two parts: an application frontend and a UDR. The UDR may store subscription and policy data for UDM 158 and PCF 156, and / or structured data for exposure and application data for NEF 152 (including PFD for application discovery and application request information for multiple UE 102). A Nudr service-based interface may be presented by UDR 221 and may allow UDM 158, PCF 156, and NEF 152 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes within the UDR. The UDM may include a UDM-FE responsible for credential processing, location management, and subscription management. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 158 may present a Nudm service-based interface.

[0062] AF 160 provides application impact on traffic routing, offers access to NEF, and can interact with policy frameworks for policy control.

[0063] In some embodiments, the 5GC 140 may enable edge computing by selecting operator / third-party services to be geographically closer to the point where the UE 102 is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 140 may select a UPF 148 close to the UE 102 and perform traffic steering from the UPF 148 to the data network 136 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 160. In this way, the AF 160 may influence UPF (re)selection and traffic routing. When the AF 160 is considered a trusted entity based on the operator deployment, the network operator may allow the AF 160 to interact directly with the relevant NF. Furthermore, the AF 160 may represent a NAF service-based interface.

[0064] The data network 136 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, including, for example, an application / content server 138.

[0065] Figure 2 schematically shows the wireless network 200 according to various embodiments. The wireless network 200 may include a UE 202 that wirelessly communicates with AN 204. UE 202 and AN 204 are similar to and substantially interchangeable components of similar names described elsewhere in this specification.

[0066] UE 202 may be communicatively coupled to AN 204 via connection 206. Connection 206 is shown as an air interface to enable communication coupling and may be compatible with cellular communication protocols such as LTE or 5G NR protocols operating at millimeter wave (mmWave) or sub-6GHz frequencies.

[0067] The UE 202 may include a host platform 208 coupled with a modem platform 210. The host platform 208 may include an application processing circuit 212 which may be coupled with a protocol processing circuit 214 of the modem platform 210. The application processing circuit 212 may run various applications for the UE 202, which will be a source / sink for application data. The application processing circuit 212 may further implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0068] The protocol processing circuit 214 may implement one or more layer operations to facilitate the transmission or reception of data through connection 206. Layer operations implemented by the protocol processing circuit 214 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0069] The modem platform 210 may further include a digital baseband circuit 216 that can implement one or more layer operations, which are “lower” layer operations performed by the protocol processing circuit 214 in the network protocol stack. These operations may include PHY operations, for example, one or more of the following: HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding, which may include one or more of the following: space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and other related functions.

[0070] The modem platform 210 may further include a transmitting circuit 218, a receiving circuit 220, an RF circuit 222, and an RF front end (RFFE) 224, the RFFE of which may include or be connected to one or more antenna panels 226. Briefly, the transmitting circuit 218 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 220 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 222 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 224 may include filters (e.g., surface / bulk acoustic wave filters), switches, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and arrangement of the components of the transmitting circuit 218, receiving circuit 220, RF circuit 222, RFFE 224, and antenna panel 226 (commonly referred to as “transmitting / receiving components”) may be specific to the details of the implementation, such as whether the communication is TDM or FDM, and whether it is millimeter wave or sub-6 GHz frequency. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmit / receiving chains, or they may be arranged on the same or different chips / modules, etc.

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

[0072] UE reception may be established by and through the antenna panel 226, RFFE 224, RF circuit 222, receiving circuit 220, digital baseband circuit 216, and protocol processing circuit 214. In some embodiments, the antenna panel 226 may receive transmissions from AN 204 by received beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 226.

[0073] UE transmission can be established by and through the protocol processing circuit 214, the digital baseband circuit 216, the transmit circuit 218, the RF circuit 222, the RFFE 224, and the antenna panel 226. In some embodiments, the transmit components of UE 204 may apply spatial filters to the data to be transmitted in order to form a transmit beam emitted by the antenna elements of the antenna panel 226.

[0074] Similar to UE 202, AN 204 may include a host platform 228 coupled with a modem platform 230. The host platform 228 may include an application processing circuit 232 coupled with the protocol processing circuit 234 of the modem platform 230. The modem platform may further include a digital baseband circuit 236, a transmit circuit 238, a receive circuit 240, an RF circuit 242, an RFFE circuit 244, and an antenna panel 246. The components of AN 204 are similar to and substantially interchangeable with similarly named components of UE 202. In addition to performing data transmission / reception as described above, the components of AN 208 may perform a variety of logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0075] Figure 3 is a block diagram showing components, in several exemplary embodiments, that can read instructions from a machine-readable or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and execute any one or more of the methodologies described herein. Specifically, Figure 3 shows a graphical representation of hardware resources 300, including one or more processors (or processor cores) 310, one or more memory / storage devices 320, and one or more communication resources 330, each of which may be communicatively coupled via a bus 340 or other interface circuitry. In embodiments where node virtualization (e.g., NFV) is utilized, the hypervisor 302 may be executed to provide execution environments for one or more network slices / subslice to utilize the hardware resources 300.

[0076] Processor 310 may include, for example, processors 312 and 314. Processor 310 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite 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.

[0077] The memory / storage device 320 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 320 may include, but is 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, or solid-state storage.

[0078] The communication resource 330 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 304 or one or more databases 306 or other network elements via the network 308. For example, the communication resource 330 may include a wired communication component (for coupling via USB, Ethernet®, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0079] Instruction 350 may include other executable code causing at least one of the following to execute any one or more of the methodologies discussed herein: software, programs, applications, applets, apps, or processors 310. Instruction 350 may reside entirely or partially in at least one of the processors 310 (for example, in the processor's cache memory), in the memory / storage devices 320, or in any preferred combination thereof. Furthermore, any part of instruction 350 may be transferred to hardware resources 300 from any combination of peripheral devices 304 or databases 306. Thus, the memory of processor 310, the memory / storage devices 320, the peripheral devices 304, and databases 306 are examples of computer-readable and machine-readable media.

[0080] Figure 4 shows network 400 in various embodiments. Network 400 may operate in accordance with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, network 400 may operate concurrently with network 100. For example, in some embodiments, network 400 may share one or more frequency or bandwidth resources with network 100. As one particular example, a UE (e.g., UE 402) may be configured to operate in both network 400 and network 100. Such a configuration may be based on a UE that includes circuitry configured for communication with the frequency and bandwidth resources of both network 100 and network 400. In general, some elements of network 400 may share one or more characteristics with elements of network 100. For simplicity, such elements may not be repeated in the description of network 400.

[0081] Network 400 may include UE 402, which may include any mobile or non-mobile computing device designed to communicate with RAN 408 via a wireless connection. UE 402 may be, for example, similar to UE 102. UE 402 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0082] Although not specifically shown in Figure 4, in some embodiments, the network 400 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be M2M / D2D devices communicating using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc., but are not limited to these. Similarly, although not specifically shown in Figure 4, UE 402 may be communicably coupled to an AP such as AP 106 as described with respect to Figure 1. Furthermore, although not specifically shown in Figure 4, in some embodiments, the RAN 408 may include one or more ANs such as AN 108 as described with respect to Figure 1. The RAN 408 and / or the ANs of the RAN 408 may be referred to as base stations (BS), RAN nodes, or by any other term or name.

[0083] UE 402 and RAN 408 may be configured to communicate via an air interface sometimes referred to as a sixth-generation (6G) air interface. A 6G air interface may include one or more features such as communication in terahertz (THz) or sub-THz bandwidths, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows wireless communication and radar-based sensing through various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communication in a frequency range of 80 GHz or higher. Such frequency ranges may be additionally or alternatively referred to as “millimeter wave” or “millimeter wave” frequency ranges.

[0084] RAN 408 may allow communication between UE 402 and 6G core network (CN) 410. Specifically, RAN 408 may facilitate the transmission and reception of data between UE 402 and 6G CN 410. 6G CN 410 may include various functions such as NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, AF 160, SMF 146, and AUSF 142. 6G CN 410 may further include UPF 148 and DN 136, as shown in Figure 4.

[0085] Furthermore, RAN 408 may include a variety of additional functions in addition to, or as a replacement for, the functionality of legacy cellular networks such as 4G or 5G networks. Two such functions may include Computation Control Function (Comp CF) 424 and Computation Service Function (Comp SF) 436. Comp CF 424 and Comp SF 436 may be part of or functions of the compute service plane. Comp CF 424 may be a control plane function that provides functionality such as managing Comp SF 436, generating and managing compute task contexts (e.g., create, read, modify, delete), and interacting with the underlying compute infrastructure for compute resource management. Comp SF 436 may be a user plane function that acts as a gateway for interfaceping compute service users (such as UE 402) with the compute nodes behind the Comp SF instance. Some functions of Comp SF 436 may include parsing computing service data received from users to compute tasks that can be performed by computing nodes; maintaining a service mesh entry gateway or service API gateway; enforcing service and billing policies; and performance monitoring and telemetry collection. In some embodiments, a Comp SF 436 instance may act as a user plane gateway for a cluster of computing nodes. A Comp CF 424 instance may control one or more Comp SF 436 instances.

[0086] The other two such functions may include a communication control function (Comm CF) 428 and a communication service function (Comm SF) 438, which may be part of the communication service plane. Comm CF 428 may be a control plane function for managing communication session creation / configuration / release and managing the communication session context. Comm SF 438 may be a user plane function for data transport. Comm CF 428 and Comm SF 438 can be considered upgrades to SMF 146 and UPF 148 described in relation to the 5G system in Figure 1. The upgrades provided by Comm CF 428 and Comm SF 438 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 146 and UPF 148 may still be used.

[0087] The other two such functions may include a data control function (data CF) 422, and a data service function (data SF) 432 may be part of the data service plane. The data CF 422 may also be a control plane function, providing functionality such as data SF 432 management, data service creation / configuration / release, and data service context management. The data SF 432 may also be a user plane function, acting as a gateway between data service users (such as various functions of UE 402 and 6G CN 410) and data service endpoints behind the gateway. Certain functionalities may include parsing data service user data, forwarding it to the corresponding data service endpoint, generating billing data, and reporting data service status.

[0088] Another such function may be a Service Orchestration and Chaining Function (SOCF) 420, which can discover, orchestrate, and chain communication / computation / data services provided by functions within the network. Upon receiving a service request from a user, the SOCF 420 may interact with one or more of the Comp CF 424, Comm CF 428, and Data CF 422 to identify instances of Comp SF 436, Comm SF 438, and Data SF 432, configure service resources, and generate a service chain that may include multiple instances of Comp SF 436, Comm SF 438, and Data SF 432 and their associated computing endpoints. Workload processing and data movement can then be performed within the generated service chain. The SOCF 420 may also be responsible for maintaining, updating, and releasing the created service chain.

[0089] Another such function may be the Service Registration Function (SRF) 414, which can act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 436 and Data SF 432 gateways, as well as services provided by the UE 402. The SRF 414 can be considered a counterpart to the NRF 154, which can act as a registry for network functions.

[0090] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 426, which can provide service communication infrastructure for control plane services and user plane services. The eSCP may be associated with a 5G service communication proxy (SCP) with added user plane service communication proxy capabilities. Thus, the eSCP is represented by two parts for the control plane service communication proxy and the user plane service communication proxy, namely eSCP-C 412 and eSCP-U 434, respectively. SICF 426 can control and configure eCSP instances with respect to service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0091] Another such function is AMF 444. AMF 444 may be similar to 144 but has additional functions. Specifically, AMF 444 may include potential function redistributions, such as transferring message forwarding functionality from AMF 444 to RAN 408.

[0092] Another such function is the Service-Oriented Exposure Function (SOEF) 418. SOEF can be configured to expose service-oriented and chained services to external users, such as applications.

[0093] UE 402 may include an additional function called Compute Client Service Function (comp CSF) 404. Comp CSF 404 may have both control plane and user plane functions and may interact with corresponding network-side functions such as SOCF 420, Comp CF 424, Comp SF 436, Data CF 422, and / or Data SF 432 for service discovery, request / response, and compute task workload exchange. Comp CSF 404 may also work with network-side functions to determine whether a compute task should be executed on elements of UE 402, RAN 408, and / or 6G CN 410.

[0094] UE 402 and / or Comp CSF 404 may include a service mesh proxy 406. The service mesh proxy 406 may act as a proxy for inter-service communication in the user plane. The capabilities of the service mesh proxy 406 may include one or more of the following: addressing, security, load balancing, etc.

[0095] Exemplary procedure In some embodiments, electronic devices, networks, systems, chips, or components, or parts or implementations thereof, shown in Figures 1 to 4, or any other figures herein, may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein. For example, Figure 5 shows an exemplary process 500 according to various embodiments. Process 500 may be performed by a UE or a part thereof.

[0096] In 502, process 500 may include receiving configuration information to indicate a first resource set for a first reference signal associated with a first antenna panel and a second resource set for a second reference signal associated with a second antenna panel. In 504, process 500 may further include identifying a received beam sweep factor for group-based measurement reporting associated with the first and second resource sets, the identified received beam sweep factor being based on simultaneous reception on the first and second antenna panels. In 506, process 500 may further include performing measurements on the first and second resource sets based on the received beam sweep factor. In 508, process 500 may further include reporting the measurements.

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

[0098] Several non-limiting examples of various embodiments are provided below.

[0099] Embodiment 1 is a user equipment (UE) device comprising: a memory for storing configuration information for simultaneous reception using the first and second antenna panels for a first reference signal associated with the first antenna panel and a second reference signal associated with the second antenna panel; and a processor circuit coupled to the memory. The processor circuit is configured to perform: a step of identifying a received beam sweep factor for group-based measurement reporting associated with the first and second reference signals, wherein the identified received beam sweep factor is based on simultaneous reception; a step of performing measurements on the first and second reference signals based on the received beam sweep factor; and a step of reporting the measurements.

[0100] Example 2 is the same apparatus as Example 1, where the first and second reference signals are synchronization signal blocks (SSBs).

[0101] Example 3 is the apparatus of Example 2, and its configuration information includes a first SSB resource set for a first reference signal and a second SSB resource set for a second reference signal.

[0102] Example 4 is the apparatus of Example 1, in which measurements of the first and second reference signals are performed during the measurement period, which is based on the received beam sweep factor.

[0103] Example 5 is the apparatus of Example 1, and the measurement includes L1-reference signal received power (RSRP) measurement.

[0104] Example 6 is one of the devices from Examples 1 to 5, and the received beam sweep factor is 4.

[0105] Embodiment 7 is a computer-readable medium storing instructions, which, when executed by one or more processors, causes a user device (UE) to: receive configuration information indicating a first resource set for a first reference signal associated with a first antenna panel and a second resource set for a second reference signal associated with a second antenna panel; identify a received beam sweep factor for group-based measurement reporting associated with the first and second resource sets, wherein the identified received beam sweep factor is based on simultaneous reception on the first and second antenna panels; perform measurements on the first and second resource sets based on the received beam sweep factor; and report the measurements.

[0106] Example 8 is one or more computer-readable media from Example 7, wherein the first and second reference signals include a synchronization signal block (SSB).

[0107] Example 9 is one or more computer-readable media from Example 7, and measurements for the first and second resource sets are performed during the measurement period, which is based on the received beam sweep factor.

[0108] Example 10 is one or more computer-readable media from Example 7, wherein the measurement includes L1-reference signal received power (RSRP) measurement.

[0109] Example 11 is one or more computer-readable media from any one of Examples 7 to 10, and the received beam sweep factor is 4.

[0110] Embodiment 12 is a user equipment (UE) comprising a first antenna panel, a second antenna panel, and a processor circuit coupled to the first and second antenna panels. The processor circuit is configured to perform: a step of receiving configuration information indicating a first resource set for a first reference signal received by the first antenna panel and a second resource set for a second reference signal received by the second antenna panel, wherein the first and second reference signals are received simultaneously; a step of identifying a received beam sweep factor for a group-based measurement report associated with the first and second reference signals, wherein the identified received beam sweep factor is based on simultaneous reception; a step of performing measurements on the first and second reference signals based on the received beam sweep factor; and a step of reporting the measurements.

[0111] Example 13 is the UE of Example 12, where the first and second reference signals are synchronization signal blocks (SSBs).

[0112] Example 14 is the UE of Example 13, and its configuration information includes a first SSB resource set for a first reference signal and a second SSB resource set for a second reference signal.

[0113] Example 15 is the UE of Example 12, in which measurements for the first and second reference signals are performed during the measurement period, which is based on the received beam sweep factor.

[0114] Example 16 is a UE of Example 12, wherein the measurement includes L1-reference signal received power (RSRP) measurement.

[0115] Example 17 is one of the UEs from Examples 12 to 16, and the received beam sweep factor is 4.

[0116] Example 18 may include, for group-based reporting, the definition of the measurement period for each RS, for example, how long a measurement time is required for one RS.

[0117] Example 19 may include the ability to reduce the spatial range for beam sweeping by using previously obtained L3 measurement information.

[0118] Example 20 may include defining the RX beam sweep factor in a worst-case scenario, for example, the number of RX beam sweeps required on two panels for complete spatial domain coverage.

[0119] Example 21 may include, in group-based reports, that the RX beam sweep factor can be reduced from 8 to 4.

[0120] Example 22 may include the fact that when two SSB-based resource sets are configured, the RX beam sweep factor is reduced, thus shortening the measurement period for one SSB resource. [Table 3] Here, N1 is the RX beam sweep factor, which is reduced to 4.

[0121] Example 23 may include a periodic CSI-RS resource in a resource set configured with repetition off. N=1. The configured CSI-RS should be a QCL-type D with one source SSB or CSI-RS configured for L1 or L3 previously measured.

[0122] Example 24 may include the case where, when two CSI-RS resource sets are configured, an RX beam sweep factor is not required for the measurement period. [Table 4]

[0123] Example 25 may include the fact that when one SSB resource set and one CSI-RS resource set are configured, the measurement period for the SSB / CSI-RS resources is the same as that defined for two SSB / CSI-RS resource sets, provided that the SSB and CSI-RS do not overlap.

[0124] Example 26 may include cases where the SSB resource and CSI-RS overlap. In the case of overlap, there are three options: 1. The UE measures SSB and CSI-RS using the TDM method. The UE first measures SSB using two panels, and then measures CSI-RS. A shared factor must be included during the measurement period. 2. The UE measures SSB and CSI-RS simultaneously. The measurement time for SSB is extended. 3. Define measurement limits. In this case, the UE does not need to measure both signals.

[0125] Example 27 may include a method of UE, which includes: receiving configuration information for a first reference signal associated with a first antenna panel and a second reference signal associated with a second antenna panel for simultaneous reception using a first antenna panel and a second antenna panel; and performing and reporting measurements on the first reference signal and the second reference signal based on measurement requirements, wherein the measurement requirements are based on a time period for performing a complete beam sweep using the first antenna panel and the second antenna panel.

[0126] Example 28 may include an apparatus comprising means for performing one or more elements of any method described in Examples 1 to 27, or related to any of Examples 1 to 21, or any other method or process described herein.

[0127] Example 29 may include one or more non-temporary computer-readable media containing instructions that cause an electronic device to perform one or more elements of any other method or process described herein, or any other method or process described herein, when an instruction is executed by one or more processors of the electronic device.

[0128] Example 30 may include an apparatus comprising logic, modules, or circuits that perform one or more elements of any method described in or related to any of Examples 1 to 27, or any other method or process described herein.

[0129] Example 31 may include any of Examples 1 to 27, or any part or portion thereof, or related methods, techniques, or processes.

[0130] Example 32 may include an apparatus comprising one or more processors and one or more computer-readable media containing instructions that, when executed by one or more processors, cause one or more processors to perform any or a part thereof of a method, technique, or process described in Examples 1 to 27 or related thereto.

[0131] Example 33 may include signals described in or related to any of Examples 1 to 27, or parts or portions thereof.

[0132] Example 34 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described in any of Examples 1 to 27, or in part or in part thereof, or otherwise described in this disclosure.

[0133] Example 35 may include a signal encoded with data described in or related to any of Examples 1 to 27, or any part or portion thereof, or otherwise described in this disclosure.

[0134] Example 36 may include a signal that encodes a datagram, packet, frame, segment, protocol data unit (PDU), or message described in any of Examples 1 to 27, or any part or portion thereof, or otherwise described in this disclosure.

[0135] Example 37 may include an electromagnetic signal that carries a computer-readable instruction, and the execution of the computer-readable instruction by one or more processors causes one or more processors to perform a method, technique, or process described in or related to any or part thereof of Examples 1 to 27.

[0136] Example 38 may include a computer program containing instructions, and the execution of the program by the processing element causes the processing element to perform a method, technique, or process described in or related to any or part of Examples 1 to 27.

[0137] Example 39 may include signals in a wireless network, as illustrated and described herein.

[0138] Example 40 may include a method of communication in a wireless network as illustrated and described herein.

[0139] Example 41 may include a system for providing wireless communication as illustrated and described herein.

[0140] Example 42 may include a device for providing wireless communication as illustrated and described herein.

[0141] Any of the above examples may be combined with any other examples (or combinations thereof) unless otherwise noted. The above descriptions of one or more implementations are illustrative and explanatory, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations may be possible in light of the above teachings or obtained from the implementation of various embodiments.

[0142] Abbreviation Unless otherwise used herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this paper, the following abbreviations may be applied to the examples and embodiments discussed herein.

[0143] 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACR Application Context Relocation ACK (Acknowledgement) ACID Application Client Identification ADRF Analytics Data Repository Function AF Application Function AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network AnLF Analytics Logical Function ANR Automatic Neighbor Relation AOA Angle of Arrival AP (Application Protocol), Antenna Port, Access Point API Application Programming Interface APN (Access Point Name) ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access Layer ASP Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function AWGN Additive White Gaussian Noise BAP (Backhaul Adaptation Protocol) BCH Broadcast Channel BER (Bit Error Ratio) BFD Beam Failure Detection BLER Block Error Rate BPSK (Binary Phase Shift Keying) - 2-state phase shift keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity CA (Carrier Aggregation), Certification Authority CAPEX CAPital Expenditure Capital Expenditure CBD Candidate Beam Detection CBRA Contention-Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment (Available Channel Assessment) CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM (Content Delivery Network) CDMA Code-Division Multiple Access CDR Charging Data Request CDR Charging Data Response CFRA Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI cell characteristics [identification information] CID Cell-ID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier-to-Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set Control resource set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU (CSI processing unit), Central Processing Unit (CSI processing unit) C / R Command / Response field bit CRAN (Cloud Radio Access Network) CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSCF call session control function CSAR Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send transmission enabled. CWCodeword Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data Network DNN Data Network Name DNAI (Data Network Access Identifier) DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL (Domain Specific Language), Digital Subscriber Line DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network E2E End-to-End EAS Edge Application Server ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EAS Edge Application Server EASID (Edge Application Server Identification) ECS Edge Configuration Server ECSP (Edge Computing Service Provider) EDN (Edge Data Network) EEC Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server EESID: Edge Enabler Server Identification EHE Edge Hosting Environment EGMF Exposure Governance Management Function: Public Governance Table Management Function EGPRS Enhanced GPRS Enhanced GPRS EIR Equipment Identity Register eLAA (enhanced Licensed Assisted Access) EM, Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS Evolved Packet System EREG (enhanced REG), enhanced resource element groups ETSI (European Telecommunications Standards Institute) ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Improved V2X F1AP F1 Application Protocol F1-C F1 Control Plane Interface F1-U F1 User Plane Interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH (Forward Access Channel) FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC (Federal Communications Commission) FCCH Frequency Correction Channel FDD (Frequency Division Duplex) FDM Frequency Division Multiplexing FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA (Further Enhanced Licensed Assisted Access) FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN: Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN (GSM EDGE RAN), GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB Next Generation NodeB gNB-CU (gNB-centralized unit), Next Generation NodeB Centralized unit gNB-DU (gNB-distributed unit), Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GPSI Generic Public Subscription Identifier General public subscription identifier GSM Global System for Mobile Communications, Groupe Spécial Mobile GSM Alliance GTP GPRS Tunneling Protocol GTP-U GPRS Tunneling Protocol for User Plane GTS Go To Sleep Signal (Sleep Transition Signal related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO handover HFN HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA (High Speed ​​Downlink Packet Access) HSN Hopping Sequence Number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP (Hypertext Transfer Protocol) HTTPS (Hypertext Transfer Protocol Secure) is a secure hypertext transfer protocol (HTTPS stands for http / 1.1 over SSL, i.e., port 443). I-Block Information Block ICCID (Integrated Circuit Card Identification) IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, Identifier Identification information, Identifier IDFT Inverse Discrete Fourier Transform IE Information Element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IIOT (Industrial Internet of Things) IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMS Credentials IMEI (International Mobile Equipment Identity) IMGI International mobile group identity IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT (Internet of Things) IP Internet Protocol IPsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync Syncing IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organization for Standardization ISP (Internet Service Provider) IWF Interworking Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM individual key kB Kilobyte (1000 bytes) kbps: kilobits per second Kc Ciphering key Encryption key Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (data link layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN (Local Area Network) LADN (Local Area Data Network) LBT Listen Before Talk LCM (Life Cycle Management) LCR Low Chip Rate LCS Location Services LCID: Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LMF Location Management Function LOS Line of Sight LPLMN Local PLMN Local PLMN LPP LTE Positioning Protocol LSB (Least Significant Bit) LTE Long Term Evolution LWA LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel: LTE / WLAN radio level integration via IPsec tunnel. LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (in the context of protocol layering) MAC Message authentication code (in the context of security / encryption) MAC-A MAC used for authentication and key agreement (in the context of TSG T WG3) MAC-I MAC used for data integrity in signaling messages (in the context of TSG T WG3) MANO Management and Orchestration MBMS (Multimedia Broadcast and Multicast Service) MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Minimization of Drive Tests (MDT) ME Mobile Equipment Mobile Devices MeNB master eNB Master eNB MER Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO: Measurement Object, Mobile Originated. MPBCH MTC Physical Broadcast Channel MPDCCH MTC Physical Downlink Control Channel MPDSCH MTC Physical Downlink Shared Channel MPRACH MTC Physical Random Access Channel MPUSCH MTC Physical Uplink Shared Channel MPLS (MultiProtocol Label Switching) MS Mobile Station Mobile station MSB (Most Significant Bit) MSC Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated, Mobile Termination MTC Machine-Type Communications MTLF Model Training Logical Functions mMTC (massive MTC) - massive Machine-Type Communications MU-MIMO (Multi-User MIMO) MWUS MTC wake-up signal, MTC WUS MTC WUS NACK (Negative Acknowledgement) NAI (Network Access Identifier) NAS Non-Access Stratum, Non-Access Stratum layer NCT Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure: Network Function Disclosure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function (Network Exposure Function) NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV (Network Functions Virtualization) NFVI NFV Infrastructure NFV Infrastructure NFVO NFV orchestrator NFV orchestrator NG Next Generation Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB, Narrowband MIB NPBCH (Narrowband Physical Broadcast Channel) NPDCCH Narrowband Physical Downlink Control Channel NPDSCH Narrowband Physical Downlink Shared Channel NPRACH Narrowband Physical Random Access Channel NPUSCH Narrowband Physical Uplink Shared Channel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR (New Radio), Neighbor Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD (Network Service Descriptor) NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWDAF Network Data Analytics Function NWUS (Narrowband WUS) NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical Channel Data Unit - Type 2 OFDM (Orthogonal Frequency Division Multiplexing) OFDMA (Orthogonal Frequency Division Multiple Access) OOB (Out-of-band) OOS (Out of Sync) OPEX: Operating Expenses OSI Other System Information OSS Operations Support System OTA over-the-air PAPR (Peak-to-Average Power Ratio) PAR (Peak to Average Ratio) PBCH (Physical Broadcast Channel) PC Power Control, Personal Computer PCC Primary Component Carrier, Primary CC P-CSCF Proxy CSCF Proxy CSCF PCell Primary Cell Main cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function PDCP (Packet Data Convergence Protocol) and Packet Data Convergence Protocol layer. PDCCH Physical Downlink Control Channel PDCP (Packet Data Convergence Protocol) PDN (Packet Data Network), Public Data Network PDSCH (Physical Downlink Shared Channel) PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network Public Land Mobile Network PIN Personal Identification Number Personal Identification Number PM Performance Measurement Performance Measurement PMI Precoding Matrix Indicator Precoding Matrix Indicator PNF Physical Network Function Physical Network Function PNFD Physical Network Function Descriptor Physical Network Function Descriptor PNFR Physical Network Function Record Physical Network Function Record POC PTT over Cellular PTT over Cellular PP, PTP Point-to-Point Point-to-Point PPP Point-to-Point Protocol Point-to-Point Protocol PRACH Physical RACH Physical RACH PRB Physical resource block Physical resource block PRG Physical resource block group Physical resource block group ProSe Proximity Services, Proximity-Based Service Proximity Services, Proximity-Based Service PRS Positioning Reference Signal Positioning Reference Signal PRR Packet Reception Radio Packet Reception Radio PS Packet Services Packet Services PSBCH Physical Sidelink Broadcast Channel Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSFCH (Physical Sidelink Feedback Channel) PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM (Quadrature Amplitude Modulation) QCI QoS class of identifier QCL Quasi co-location (quasi-co-location) QFI QoS Flow ID, QoS Flow Identifier QoS (Quality of Service) QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI (Random Access RNTI) RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial In User Service RAN Radio Access Network RAND: Random number (used for authentication) RAR (Random Access Response) RAT Radio Access Technology RAU Routing Area Update RB Resource block, Radio Bearer RBG Resource block group REG Resource Element Group Rel Release REQ REQuest Request RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control, Radio Link Control layer RLC AM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLF Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC RObust Header Compression RRC Radio Resource Control, Radio Resource Control layer Radio Resource Control layer RRM Radio Resource Management RS Reference Signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP (Real Time Protocol) RTS Ready-To-Send Ready to send RTT (Round Trip Time) Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-CSCF serving CSCF serviceCSCF S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA (Single Carrier Frequency Division Multiple Access) SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP (Service Data Adaptation Protocol) - Service Data Adaptation Protocol Layer SDL Supplementary Downlink SDNF (Structured Data Storage Network Function) SDP Session Description Protocol SDSF (Structured Data Storage Function) SDT Small Data Transmission SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot Format Indication SFTD (Space-Frequency Time Diversity), SFN (Space-Frequency Network) and frame timing difference SFN System Frame Number SgNB Secondary gNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Table RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiation Protocol SiP System in Package SL Sidelink SLA (Service Level Agreement) SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC (System on Chip) SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signaling Radio Bearer SRS Sounding Reference Signal Detection reference signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID (Service Set Identifier) SS / PBCH Block SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Syncheronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal-based Signal-to-Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO (Single User MIMO) SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD (Time Division Duplex) TDM Time Division Multiplexing TDMA (Time Division Multiple Access) TE Terminal Equipment TEID: Tunnel End Point Identifier TFT Traffic Flow Template TMSI (Temporary Mobile Subscriber Identity) TNL (Transport Network Layer) TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standards TTI Transmission Time Interval Tx Transmission, Transmitting, Transmission, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management: Centralized Data Management UDP User Datagram Protocol UDSF (Unstructured Data Storage Network Function) UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode (No Acknowledgment Response Mode) UML (Unified Modeling Language) UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN (Universal Terrestrial Radio Access Network) UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastructure V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link, VLAN (Virtual LAN), Virtual Local Area Network VM (Virtual Machine) VNF (Virtualized Network Function) VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP (Voice-over-IP, Voice-over-Internet Protocol) VPLMN Visited Public Land Mobile Network VPN (Virtual Private Network) VRB (Virtual Resource Block) WiMAX Worldwide Interoperability for Microwave Access WLAN (Wireless Local Area Network) WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2-U X2-User plane XML eXtensible Markup Language XRES Expected User Response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Power

[0144] Terminology For the purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0145] The term "application" can refer to a complete, deployable package or environment for achieving a specific function in an operating environment. The term "AI / ML application," for example, can refer to an application that includes several AI / ML models and application-level descriptions.

[0146] As used herein, the term “circuit” refers to, is part of, or includes hardware components configured to provide the functions described, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memory (shared, dedicated, or group), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-performance PLDs (HCPLDs), constructed ASICs, or programmable SoCs), and digital signal processors (DSPs). In some embodiments, a circuit may run one or more software or firmware programs to provide at least some of the functionalities described. The term “circuit” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) having program code used to perform the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0147] As used herein, the term “processor circuit” refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuit” may also refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other devices that can execute or otherwise operate computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuit may include more hardware accelerators, such as microprocessors and programmable processing devices. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may also be referred to as “processor circuit.”

[0148] As used herein, the term “interface circuit” refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term “interface circuit” may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or others.

[0149] As used herein, the terms “User Equipment” or “UE” refer to a device having wireless communication capabilities and may represent a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, a 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 terms “User Equipment” or “UE” may include any computing device including any type of wireless / wired device or wireless communication interface.

[0150] As used herein, the term “Network Element” 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 with, and / or referred to as, networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, wireless network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and / or others.

[0151] As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms “computer system” and / or “system” may refer to various components of a computer that are interconnected by communication. Additionally, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected by communication and configured to share computing and / or networking resources.

[0152] As used herein, terms such as “appliance” and “computer appliance” refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular computing resource. A “virtual appliance” is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance, or is otherwise dedicated in a way to provide a particular computing resource.

[0153] As used herein, the term “resource” refers to physical or virtual devices, physical or virtual components, and / or physical or virtual components within a particular device in a computing environment, including computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operation, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, and workload units. “Hardware resources” may refer to computing, storage, and / or network resources provided by a physical hardware element(s). “Virtualized resources” may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc., by a virtualization infrastructure. The term “network resources” or “communication resources” may refer to resources accessible by computer devices / systems over a communication network. The term “system resources” may refer to any kind of shared entity providing services, and may include computing and / or network resources. System resources can be considered as a set of coherent functions, network data objects, or services that reside on a single host or multiple hosts and are accessible via a clearly identifiable server.

[0154] As used herein, the term “channel” refers to any tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may be synonymous and / or equivalent to any other similar term indicating a path or medium through which data is communicated, such as “communication channel,” “data communication channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” and / or any other similar term. Furthermore, as used herein, the term “link” refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0155] As used herein, terms such as "instantiate" and "instantiate" refer to the creation of an instance. An "instance" can also refer to the specific occurrence of an object, for example, during the execution of program code.

[0156] The terms “coupled” and “communicationally coupled” are used herein together with their derivatives. The term “coupled” may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are indirectly in contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between elements said to be coupled to each other. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicationally coupled” may mean that two or more elements are in contact with each other by means of communication, such as through wires or other interconnections, through wireless communication channels or links.

[0157] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains contents.

[0158] The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to the SS / PBCH block.

[0159] The term "Primary Cell" refers to the MCG cell operating on the primary frequency from which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term "primary SCG cell" refers to the SCG cell through which the UE performs random access when executing the Reconfiguration with Sync procedure for DC operation. The term "Secondary Cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured using CA. The term "sub-cell group" refers to a subset of serving cells that includes a PSCell and zero or more sub-cells for a UE composed of DCs. The term "Serving Cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell that constitutes a primary cell. The term "serving cell" or "multiple serving cells" refers to a set of cells that includes the special cell for the UE in RRC_CONNECTED configured with CA / , and all sub-cells. The term "special cell" refers to MCG's PCell or SCG's PSCell for DC operation; otherwise, the term "special cell" refers to Pcell.

[0160] The term “machine learning” or “ML” refers to the use of computer systems that implement algorithms and / or statistical models to perform a particular task(s) by relying on patterns and inference, rather than using explicit instructions. An ML algorithm builds or estimates a mathematical model(s) ("ML model," etc.) based on sample data ("training data," "model training information," etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with some task and some measure of performance, and an ML model can be any object or data structure created after an ML algorithm has been trained on one or more training datasets. After training, an ML model can be used to make predictions on new datasets. The term “ML algorithm” refers to a different concept from the term “ML model,” but these terms are interchangeable for the purposes of this disclosure as discussed herein.

[0161] The terms "machine learning model" and "ML model" can also refer to the ML methods and concepts used in ML-assisted solutions. An "ML-assisted solution" is a solution that uses ML algorithms in operation to address a specific use case. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithm, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-arm bandit learning, deep RL, etc.), and neural networks. Depending on the implementation, a particular ML model can have many submodels as components, and an ML model can train all its submodels together. Separately trained ML models can also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of features, functions, or feature entities specific to an ML-assisted solution, and an ML pipeline may include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or more data sources within the actors. An "actor" is an entity that hosts an ML-assisted solution using the output of an ML model inference. The term "ML training host" refers to an entity such as a network function that hosts the training of a model. The term "ML inference host" refers to an entity such as a network function that hosts a model during inference mode (which includes both model execution and any online learning, if applicable). The ML host informs the actor about the output of the ML algorithm, and the actor makes decisions about actions ("actions" are performed by the actor as a result of the output of the ML-assisted solution). The term "model inference information" refers to information used as input to the ML model to make inference decisions, and while the data used to train the ML model and the data used to make inference decisions may overlap, "training data" and "inference data" refer to different concepts.

Claims

1. A user equipment (UE) device, said device: A memory for storing configuration information for simultaneous reception using the first and second antenna panels, relating to a first reference signal associated with the first antenna panel and a second reference signal associated with the second antenna panel; The memory is coupled to a processing circuit, the processing circuit comprising: A step of identifying a received beam sweep factor for a group-based measurement report associated with the first reference signal and the second reference signal, wherein the identified received beam sweep factor is based on the simultaneous reception, in the step of; A step of performing measurements on the first reference signal and the second reference signal based on the received beam sweep factor; The step of reporting the aforementioned measurements and A device that performs this task.

2. The apparatus according to claim 1, wherein the first reference signal and the second reference signal are a synchronization signal block (SSB).

3. The apparatus according to claim 2, wherein the configuration information includes a first SSB resource set for the first reference signal and a second SSB resource set for the second reference signal.

4. The apparatus according to claim 1, wherein the measurement of the first reference signal and the second reference signal is performed during a measurement period, the measurement period being based on the received beam sweep factor.

5. The apparatus according to claim 1, wherein the measurement includes L1-reference signal received power (RSRP) measurement.

6. The apparatus according to claim 5, wherein the receiving beam sweep factor is 4.

7. One or more computer-readable media storing instructions, the instructions, when executed by one or more processors, to the user device (UE): The steps include receiving configuration information indicating a first resource set for a first reference signal associated with a first antenna panel and a second resource set for a second reference signal associated with a second antenna panel; A step of identifying the received beam sweep factors for group-based measurement reports associated with the first resource set and the second resource set, wherein the identified received beam sweep factors are based on simultaneous reception at the first antenna panel and the second antenna panel; A step of performing measurements on the first resource set and the second resource set based on the received beam sweep factor; The step of reporting the aforementioned measurements and One or more computer-readable media configured to execute [the specified action].

8. The first and second reference signals include a synchronization signal block (SSB) in one or more computer-readable media according to claim 7.

9. The measurements in the first resource set and the second resource set are performed over a measurement period, the measurement period being based on the received beam sweep factor, one or more computer-readable media according to claim 7.

10. The measurement includes L1-reference signal received power (RSRP) measurement, one or more computer-readable media according to claim 7.

11. The computer-readable medium according to claim 10, wherein the received beam sweep factor is 4.

12. First antenna panel and; The second antenna panel and; Processor circuit coupled to the first antenna panel and the second antenna panel A user device (UE) comprising the following, wherein the processor circuit is: A step of receiving configuration information indicating a first resource set for a first reference signal received by the first antenna panel and a second resource set for a second reference signal received by the second antenna panel, wherein the first and second reference signals are received simultaneously; A step of identifying a received beam sweep factor for a group-based measurement report associated with the first reference signal and the second reference signal, wherein the identified received beam sweep factor is based on simultaneous reception; A step of performing measurements on the first reference signal and the second reference signal based on the received beam sweep factor; The step of reporting the aforementioned measurements and The UE is configured to execute.

13. The UE according to claim 12, wherein the first and second reference signals are synchronization signal blocks (SSBs).

14. The UE according to claim 13, wherein the configuration information includes a first SSB resource set for the first reference signal and a second SSB resource set for the second reference signal.

15. The measurement of the first reference signal and the second reference signal is performed over a measurement period, the measurement period being based on the received beam sweep factor, according to claim 12.

16. The UE according to claim 12, wherein the measurement includes L1-reference signal received power (RSRP) measurement.

17. The UE according to claim 16, wherein the received beam sweep factor is 4.

Images