Base station information exchange in radio access network

Abstract

A method may include receiving, by a first base station, configuration parameters for an event from a second base station. The parameters may include a time interval and a range of values. The method may also include configuration of the requested information for the event. The method may also include determining, by the first base station, that the event has occurred based on the measurements remaining outside the range of values within the time interval. The method may additionally include transmitting, by the first base station, the requested information to the second base station based on determining that the event has occurred.

Description

Cross Reference to Related Applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 456,268, filed March 31, 2023, which application is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF DRAWINGS

[0002] Examples of several of the various implementations of the present disclosure are described herein with reference to the accompanying drawings.

[0003] FIG. 1A and FIG. 1B An example mobile communication network in which implementations of the present disclosure can be implemented is illustrated.

[0004] FIG. 2A and FIG. 2B New Radio (NR) user plane and control plane protocol stacks are respectively illustrated.

[0005] FIG. 3 Examples of services provided between protocol layers of the NR user plane protocol stack are illustrated. FIG. 2A

[0006] FIG. 4A Examples of an example downlink data flow through the NR user plane protocol stack are illustrated. FIG. 2A

[0007] FIG. 4B An example format of a MAC subheader in a MAC PDU is illustrated.

[0008] FIG. 5A and FIG. 5B Mappings between logical channels, transport channels, and physical channels for downlink and uplink are respectively illustrated.

[0009] FIG. 6 is an example diagram showing RRC state transitions of a UE.

[0010] FIG. 7 An example configuration of an NR frame into which OFDM symbols are grouped is illustrated.

[0011] FIG. 8 An example configuration of slots in the time and frequency domains of an NR carrier is illustrated.

[0012] FIG. 9 Examples of bandwidth adaptation using three configured BWPs for an NR carrier are illustrated.

[0013] FIG. 10A Three carrier aggregation configurations with two component carriers are illustrated.

[0014] FIG. 10B ​​Examples are illustrated of how aggregated cells can be configured into one or more PUCCH groups.

[0015] FIG. 11A Examples are illustrated of SS / PBCH block structure and location.

[0016] FIG. 11B Examples are illustrated of CSI-RS mapped in time and frequency domain.

[0017] FIG. 12A and FIG. 12B Examples are illustrated of three downlink beam management procedures and three uplink beam management procedures, respectively.

[0018] FIG. 13A , FIG. 13B and FIG. 13C Examples are illustrated of four-step contention-based random access procedure, two-step contention-free random access procedure, and another two-step random access procedure, respectively.

[0019] FIG. 14A Examples are illustrated of CORESET configuration for bandwidth part.

[0020] FIG. 14B Examples are illustrated of PDCCH processing and CCE-to-REG mapping for DCI transmission on CORESET.

[0021] FIG. 15 Examples are illustrated of wireless device communicating with base station.

[0022] FIG. 16A , FIG. 16B , FIG. 16C and FIG. 16D Examples are illustrated of example structures for uplink and downlink transmissions.

[0023] FIG. 17 Examples are illustrated of functional architecture of artificial intelligence and / or machine learning.

[0024] FIG. 18 Examples are illustrated of using AI / ML in radio access network.

[0025] FIG. 19 Examples are illustrated of using AI / ML in radio access network.

[0026] FIG. 20 Examples are illustrated of predicted and actual values.

[0027] FIG. 21 Examples are illustrated of example implementations of the present disclosure.

[0028] FIG. 22 Examples are illustrated of example implementations of the present disclosure.

[0029] FIG. 23 Example embodiments of the present disclosure are illustrated.

[0030] FIG. 24 Example embodiments of the present disclosure are illustrated.

[0031] FIG. 25 Example embodiments of the present disclosure are illustrated.

[0032] FIG. 26 Example embodiments of the present disclosure are illustrated.

[0033] FIG. 27 Example embodiments of the present disclosure are illustrated.

[0034] FIG. 28 Example embodiments of the present disclosure are illustrated.

[0035] FIG. 29 Example embodiments of the present disclosure are illustrated.

[0036] FIG. 30 Example embodiments of the present disclosure are illustrated.

[0037] FIG. 31 Example embodiments of the present disclosure are illustrated.

[0038] FIG. 32 Example embodiments of the present disclosure are illustrated.

[0039] FIG. 33 Example embodiments of the present disclosure are illustrated.

[0040] FIG. 34 Example embodiments of the present disclosure are illustrated.

[0041] FIG. 35 Example embodiments of the present disclosure are illustrated.

[0042] FIG. 36 Example embodiments of the present disclosure are illustrated.

[0043] FIG. 37 Example embodiments of the present disclosure are illustrated.

[0044] FIG. 38 Example embodiments of the present disclosure are illustrated.

[0045] FIG. 39 Example embodiments of the present disclosure are illustrated.

[0046] FIG. 40 Example embodiments of the present disclosure are illustrated.

[0047] FIG. 41Example implementations of the present disclosure are illustrated.

[0048] FIG. 42 Example implementations of the present disclosure are illustrated.

[0049] FIG. 43 Example implementations of the present disclosure are illustrated.

[0050] FIG. 44 Example implementations of the present disclosure are illustrated.

[0051] FIG. 45 Example implementations of the present disclosure are illustrated. DETAILED DESCRIPTION

[0052] In this disclosure, various implementations are presented as examples of how the disclosed technology can be implemented and / or practiced in environments and scenarios. Various changes can be made in form and detail without departing from the scope. It will be apparent to those skilled in the relevant arts, upon reading this description, how to implement alternative implementations. This implementation should not be limited by any of the example implementations described. Implementations of the present disclosure will be described with reference to the drawings. Limitations, features, and / or elements from disclosed example implementations can be combined to create additional implementations within the scope of the present disclosure. Any figure that highlights functionality and advantages is presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable such that it can be utilized in ways other than shown. For example, in some implementations, the actions listed in any flowchart can be reordered or used only optionally.

[0053] Implementations can be configured to operate as desired. The disclosed mechanisms can be executed when certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, and / or a combination of the above, among others. Example criteria can be based at least in part on, for example, a wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, and / or a combination of the above, among others. Various example implementations can be applied when one or more criteria are met. Thus, example implementations that selectively implement the disclosed protocols can be realized.

[0054] A base station can communicate with various wireless devices. The wireless devices and / or the base station can support a number of technologies and / or versions of the same technology. The wireless devices can have some specific capabilities depending on the wireless device class and / or capabilities. When the present disclosure refers to a base station communicating with a plurality of wireless devices, the present disclosure can refer to a subset of all the wireless devices in a coverage area. The present disclosure can refer to, for example, a plurality of wireless devices of a given LTE or 5G release that have a given capability and that are in a given sector of the base station. The plurality of wireless devices in the present disclosure can refer to a selected plurality of wireless devices, and / or a subset of all the wireless devices in a coverage area that perform according to the disclosed methods, etc. There can be a plurality of base stations or a plurality of wireless devices in a coverage area that can not comply with the disclosed methods, for example, those wireless devices or base stations can perform based on an older release of the LTE or 5G technology.

[0055] In the present disclosure, “one” and like phrases are to be construed to mean “at least one” and “one or more.” Similarly, any term that ends with “(s)” is to be construed to mean “at least one” and “one or more.” In the present disclosure, the term “may” is to be construed as “e.g., may.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one possibility of a number of suitable possibilities that can or can not be employed by one or more of the various embodiments. As used herein, the terms “includes” and “comprises” recite a list of one or more components. The term “includes” can be used interchangeably with “including.” The term “comprises” can be used interchangeably with “comprising.” The term “comprises” provides for the recitation of an incomplete list of components that is not exclusive. As used herein, the term “based on” is to be construed as “based at least in part on,” and not “based solely on,” for example. As used herein, the term “and / or” means any possible combination of the elements listed. For example, “A, B, and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B, and C.

[0056] A is said to be a subset of B if every element of A is an element of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are: {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase “based on” (or, equivalently, “based at least on”) indicates that the phrase “based on” is an example of one possibility of a plurality of suitable possibilities that can or can not be used in one or more of various embodiments. The phrase “in response to” (or, equivalently, “at least in response to”) indicates that the phrase “in response to” is an example of one possibility of a plurality of suitable possibilities that can or can not be used in one or more of various embodiments. The phrase “in dependence of” (or, equivalently, “at least in dependence of”) indicates that the phrase “in dependence of” is an example of one possibility of a plurality of suitable possibilities that can or can not be used in one or more of various embodiments. The phrase “employ / using” (or, equivalently, “employ / using at least”) indicates that the phrase “employ / using” is an example of one possibility of a plurality of suitable possibilities that can or can not be used in one or more of various embodiments.

[0057] The term “configuration” can relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. Configuration can refer to particular settings in a device that affect the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, and / or memory values, among other examples, can be “configured,” whether the device is in an operational state or a non-operational state, to provide particular characteristics to the device. Terms such as “control message that causes an action in a device” can mean that the control message has parameters that can be used to configure a particular characteristic or can be used to cause certain actions in a device, whether the device is in an operational state or a non-operational state.

[0058] In this disclosure, a parameter (or, equivalently, a field or an information element: IE) can include one or more information objects, and an information object can include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J, then, for example, N includes K, and N includes J. In example embodiments, when one or more messages include multiple parameters, this means that the parameter in the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0059] Many of the features presented are described as optional by use of "may" or use of brackets. For the sake of conciseness and readability, the present disclosure does not explicitly describe every permutation of optional features that can be obtained by selecting from this set of optional features. The present disclosure should be interpreted to explicitly disclose all such permutations. For example, a system described as having three optional features can be embodied in seven ways, i.e., having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0060] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is herein defined as an element that performs a defined function and has a defined interface to other elements. The modules described in the present disclosure can be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element) or combinations thereof, which can be behaved equivalently. For example, a module can be implemented as a software routine in a computer language (e.g., C, C++, Fortran, Java, Basic, or

[0061] FIG. 1A An example of a mobile communication network 100 in which embodiments of the present disclosure can be implemented is illustrated. The mobile communication network 100 can be, for example, a public land mobile network (PLMN) operated by a network operator. As FIG. 1A As illustrated, the mobile communication network 100 comprises a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0062] The CN 102 can provide the wireless device 106 with access to one or more data networks (DNs) such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface functionality, the CN 102 can establish end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0063] The RAN 104 can connect the CN 102 to the wireless device 106 through radio communication over an air interface. As part of the radio communication, the RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink, and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. The downlink transmissions can be separated from the uplink transmissions using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination thereof.

[0064] The term “wireless device” can be used interchangeably herein with the term “mobile device” or “fixed (non-mobile) device” to refer to any device that needs or can use wireless communication. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle road side unit (RSU), relay node, automobile, and / or any combination thereof. The term “wireless device” encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0065] The RAN 104 can include one or more base stations (not shown). The term “base station” can be used interchangeably herein with the terms “Node B,” “eNode B (eNB),” “remote radio head (RRH),” “baseband processing unit coupled to one or more RRHs,” “repeater node or relay node used to extend the coverage area of a donor node,” “next generation eNode B (ng-eNB),” “generation node B (gNB),” “access point (AP)” associated with, for example, Wi-Fi or any other suitable wireless communication standard,” and / or “any combination thereof. A base station can include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0066] The base stations included in the RAN 104 can include one or more groups of antennas, which can be used to communicate with the wireless devices 106 through the air interface. For example, one or more of the base stations can include three groups of antennas to control the three cells (or sectors) respectively. The size of a cell can be determined by the range of a receiver (e.g., base station receiver) that can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. The cells of the base stations can together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0067] In addition to three-sector sites, other implementations of the base stations are possible. For example, one or more of the base stations in the RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more of the base stations in the RAN 104 can be implemented as an access point, a baseband processing unit coupled to a number of remote radio heads (RRHs), and / or a repeater or relay node used to extend the coverage area of a donor node. The baseband processing unit coupled to RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. A repeater node can amplify and re -broadcast the radio signals received from the donor node. A relay node can perform the same / similar functions as a repeater node but can decode the radio signals received from the donor node to remove noise before amplifying and re -broadcasting the radio signals.

[0068] The RAN 104 can be deployed as a homogeneous network of macro cell base stations with similar antenna gain patterns and similar transmit power levels. The RAN 104 can be deployed as a heterogeneous network. In a heterogeneous network, small- cell base stations can be used to provide hot -spot coverage where the demand for high data coverage is high or to provide additional coverage where the demand for high data coverage is low. In a heterogeneous network, small- cell base stations can have a similar antenna gain pattern and transmit power levels as macro cell base stations. In a heterogeneous network, small- cell base stations can have a different antenna gain pattern and / or transmit power levels from macro cell base stations. For example, small- cell base stations can be deployed to provide incremental coverage to existing macro cell base stations, to provide overall system capacity, or to provide additional coverage where the demand for high data coverage is high.

[0069] The Third Generation Partnership Project (3GPP) was formed in 1998 to FIG. 1AThe 3GPP has so far produced specifications for a third generation (3G) of mobile networks, referred to as the Universal Mobile Telecommunication System (UMTS), a fourth generation (4G) network referred to as Long Term Evolution (LTE), and a fifth generation (5G) network referred to as New Radio (NR). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as Next Generation RAN (NG-RAN). Embodiments can be applicable to the RAN of other mobile communication networks, such as FIG. 1A the RAN 104 in FIG. 1, RANs of earlier 3G and 4G networks, and RANs of future networks not yet specified (e.g., 3GPP 6G networks). The NG-RAN implements the 5G Radio Access Technology, referred to as New Radio (NR), and can be provided to implement 4G Radio Access Technology or other Radio Access Technologies, including non-3GPP Radio Access Technologies.

[0070] FIG. 1B Another example mobile communication network 150 is illustrated in which embodiments of the present disclosure can be implemented. The mobile communication network 150 can be, for example, a PLMN operated by a network operator. As FIG. 1B illustrated, the mobile communication network 150 includes a 5G Core Network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively, UEs 156). These components can be implemented and operate in the same or similar manner as corresponding components described above with regard to FIG. 1A the mobile communication network 100 in FIG. 1.

[0071] The 5G-CN 152 provides an interface for the UEs 156 to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface functionality, the 5G-CN 152 can establish end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. In comparison to the CN of a 3GPP 4G network, the 5G-CN 152 can be based on a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 can be defined as network functions that provide services via interfaces to other network functions. The network functions of the 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform, e.g., a cloud-based platform.

[0072] As FIG. 1B illustrated, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are illustrated in FIG. 1 for ease of illustration.FIG. 1B The AMF / UPF 158 is shown as one component AMF / UPF 158B. The UPF 158B can act as a gateway between the NG-RAN 154 and the one or more DN. The UPF 158B can perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification and traffic steering for breakout of traffic flows to the one or more DN, quality of service (QoS) handling for user plane traffic (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering and downlink data notification triggering, etc. The UPF 158B can act as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, a point of interconnect with the one or more DN, an external protocol (or packet) data unit (PDU) session point of interconnect, and / or a branching point for split routing and / or traffic steering. The UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and a DN.

[0073] The AMF 158A can perform functions such as non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3 GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including check on roaming permission, mobility management control (subscription and policies), network slice support, and / or session management function (SMF) selection. NAS can refer to functionality operating between a CN and a UE, and AS can refer to functionality operating between a UE and a RAN.

[0074] The 5G-CN 152 can include one or more additional network functions, which are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 can include one or more of a session management function (SMF), an NR repository function (NRF), a policy control function (PCF), a network exposure function (NEF), a unified data management (UDM), an application function (AF), and / or an authentication server function (AUSF).

[0075] NG-RAN 154 can connect 5G-CN 152 to UE 156 via radio communication over an air interface. NG-RAN 154 may include one or more gNBs (exemplified as gNB 160A and gNB 160B (collectively referred to as gNB 160)) and / or one or more ng-eNBs (exemplified as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162)). gNB 160 and ng-eNB 162 may be more generally referred to as base stations. gNB 160 and ng-eNB 162 may include one or more sets of antennas for communicating with UE 156 over an air interface. For example, one or more of gNB 160 and / or one or more of ng-eNB 162 may include three sets of antennas to control three cells (or sectors) respectively. The gNB 160 and ng-eNB 162 cells can work together to provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0076] like FIG. 1B As shown, gNB 160 and / or ng-eNB 162 can connect to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using a direct physical connection and / or an indirect connection via an underlying transport network such as an Internet Protocol (IP) transport network. gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... FIG. 1B As illustrated, the gNB 160A can connect to the UE 156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with each interface can be configured by... FIG. 1B The network elements in the system are used to exchange data and signaling messages, and can include two planes: the user plane and the control plane. The user plane processes data that is of interest to the user. The control plane processes signaling messages that are of interest to the network elements.

[0077] The gNBs 160 and / or ng-eNBs 162 can be connected through one or more NG interfaces to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158. For example, the gNB 160A can be connected through an NG-User (NG-U) interface to the UPF 158B of the AMF / UPF 158. The NG-U interface can provide for the delivery (e.g., non-guaranteed delivery) of user-plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A can be connected through an NG-Control (NG-C) interface to the AMF 158A. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, transfer of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0078] The gNBs 160 can provide NR user and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A can provide NR user and control plane protocol terminations towards the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user and control plane protocol terminations towards the UEs 156 over the Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B can provide E-UTRA user and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

[0079] The 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those of ordinary skill in the art will understand that NR can be connected to a 4G core network in a mode referred to as “non-standalone.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functionality (e.g., initial access, mobility, and paging). Although FIG. 1B Only one AMF / UPF 158 is shown in FIG. 1, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0080] As discussed, FIG. 2A Interfaces between network elements in FIG. 1 (e.g., the Uu interface, the Xn interface, and the NG interface) can be associated with a protocol stack that the network elements use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user, and the control plane can handle signaling messages of interest to the network elements.

[0081] FIG. 2B and FIG. 2AExamples of NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220 are illustrated respectively. FIG. 2B and FIG. 1B The protocol stack illustrated herein can be used for, for example FIG. 2A The protocol stack of the Uu interface between UE 156A and gNB 160A shown is the same or similar.

[0082] FIG. 3 An example is shown of a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the protocol stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers of the stack and correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include the Media Access Control (MAC) layer 212 and 222, the Radio Link Control (RLC) layer 213 and 223, the Packet Data Convergence Protocol (PDCP) layer 214 and 224, and the Service Data Application Protocol (SDAP) layer 215 and 225. These four protocols together constitute Layer 2 of the OSI model or the Data Link Layer.

[0083] FIG. 2A This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From FIG. 3 and FIG. 3 Starting at the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and the DN. This PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF158B) can map IP packets to one or more QoS flows in this PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between these one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. The mapping between QoS flows and data radio bearers can be notified to SDAP 215 at UE 210 via reflection mapping or control signaling received from gNB 220. For reflection mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS Flow Indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0084] The PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, perform ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and perform integrity protection (to ensure that control messages originate from an intended source). The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets that are received in repetition due to, for example, an intra-gNB handover. The PDCPs 214 and 224 can perform packet duplication to improve the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet duplication can be useful for services that require high reliability.

[0085] Although FIG. 3 Although not shown in FIG. 2, the PDCPs 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells, or more generally, to two cell groups (a master cell group (MCG) and a secondary cell group (SCG)). A split bearer is a case where a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 can map / de-map the split radio bearers between RLC channels that belong to a cell group.

[0086] The RLCs 213 and 223 can perform segmentation, retransmission by automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the mentioned functions. The RLC configuration can be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As FIG. 3 As shown, the RLCs 213 and 223 can provide RLC channels as a service to the PDCPs 214 and 224, respectively.

[0087] The MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing can include multiplexing / demultiplexing of data units belonging to one or more logical channels into / from transport blocks (TBs) that are delivered to / from the PHYs 211 and 221. The MAC 222 can be configured to perform scheduling between UEs, scheduling information reporting, and priority handling by dynamic scheduling. Scheduling for downlink and uplink can be performed in the gNB 220 (at the MAC 222). The MACs 212 and 222 can be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 by logical channel prioritization, and / or padding. The MACs 212 and 222 can support one or more numerologies and / or transmission timings. In an example, mapping restrictions in the logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As FIG. 3 illustrated, the MACs 212 and 222 can provide logical channels to the RLCs 213 and 223 as services.

[0088] The PHYs 211 and 221 can perform mapping of transport channels to physical channels and of the digital and analog signal processing functions used for transmission and reception of information over the air interface. These digital and analog signal processing functions can include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 can perform multi-antenna mapping. As FIG. 4A illustrated, the PHYs 211 and 221 can provide one or more transport channels to the MACs 212 and 222 as services.

[0089] FIG. 4A An example downlink data flow through the NR user plane protocol stack is illustrated. FIG. 4A An example downlink data flow through the NR user plane protocol stack to generate two TBs at the gNB 220 from three IP packets n , n+1 and m is illustrated. An uplink data flow through the NR user plane protocol stack can be similar to the downlink data flow depicted in FIG. 4A .

[0090] A downlink data flow of FIG. 4A begins when the SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to a radio bearer. FIG. 4A In n , the SDAP 225 maps the IP packets n+1Mapped to the first radio bearer 402, and the IP packet is... m Mapped to the second radio bearer 404. SDAP header (in FIG. 4A (Chart marked with "H") is added to IP packets. Data units originating from / going to higher protocol layers are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to lower protocol layers are called higher protocol layer Protocol Data Units (PDUs). FIG. 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224, and is also the PDU of SDAP 225.

[0091] FIG. 3 The remaining protocol layers can perform their associated functionalities (e.g., regarding...). FIG. 4A Add the corresponding header and forward its output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). FIG. 4A China targets IP packets m As shown), it forwards its output to MAC 222. MAC 222 can multiplex multiple RLC PDUs and can attach MAC sub-headers to RLCPDUs to form transport blocks. In NR, MAC sub-headers can be distributed across MAC PDUs, such as... FIG. 4B As illustrated. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure reduces processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

[0092] FIG. 4B An example format of the MAC sub-header in a MAC PDU is shown. The MAC sub-header includes: an SDU length field, which indicates the length of the MAC SDU corresponding to the MAC sub-header (e.g., in bytes); a Logical Channel Identifier (LCID) field, which identifies the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) field, which indicates the size of the SDU length field; and a reserved bit (R) field for future use.

[0093] FIG. 4B Further examples illustrate MAC control elements (CEs) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, FIG. 4B This example illustrates two MAC CEs inserted into a MAC PDU. MAC CEs can be inserted at the beginning of a MAC PDU used for downlink transmission (e.g., ...). FIG. 5A(As shown) and at the end of the MAC PDU used for uplink transmission. MAC CEs can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used to activate / deactivate PDCP copy detection, channel state information (CSI) reports, sounding reference signal (SRS) transmission, and previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader with a format similar to that described for the MAC SDU and may be identified by a reserved value in the LCID field, which indicates the type of control information included in the MAC CE.

[0094] Before describing the NR control plane protocol stack, we will first describe the mapping between logical channels, transport channels, and physical channels, as well as channel types. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack, which will be described later below.

[0095] FIG. 5B and FIG. 5A The mappings between logical channels, transport channels, and physical channels are illustrated for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as traffic channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example: The Paging Control Channel (PCCH) is used to carry paging messages, which are used to page UEs whose location is unknown to the network at the cell level; The Broadcast Control Channel (BCCH) is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by the UE to obtain information about how to configure the cell and how to operate within the cell; The Common Control Channel (CCCH) is used to carry control messages and random access. A dedicated control channel (DCCH) is used to carry control messages to / from a specific UE to configure the UE; and Dedicated Traffic Channel (DTCH) is used to carry user data to / from a specific UE.

[0096] Transport channels are used between the MAC layer and the PHY layer and can be defined by how the information it carries is transmitted over the air interface. The set of transport channels defined by NR includes, for example: a paging channel (PCH) for carrying paging messages originating from the PCCH; a broadcast channel (BCH) for carrying the MIB from the BCCH; a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from the BCCH; an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and a random access channel (RACH) for allowing the UE to contact the network without any prior scheduling.

[0097] The PHY can use physical channels to pass information between the processing stages of the PHY. A physical channel can have a set of associated time-frequency resources for carrying the information of one or more transport channels. The PHY can generate control information to support low-level operations of the PHY and provide the control information to the lower levels of the PHY via a physical control channel, referred to as the L1 / L2 control channel. The set of physical channels and physical control channels defined by NR includes, for example: a physical broadcast channel (PBCH) for carrying the MIB from the BCH; a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some cases, uplink control information (UCI) as described below; a physical uplink control channel (PUCCH) for carrying UCI, which can include HARQ acknowledgements, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and scheduling requests (SRs); and a physical random access channel (PRACH) for random access.

[0098] Similar to the physical control channels, the physical layer generates physical signals to support low-level operations of the physical layer. As FIG. 5B and FIG. 2BAs shown, the physical layer signals defined by the NR include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), channel state information reference signals (CSI-RSs), demodulation reference signals (DMRSs), sounding reference signals (SRSs), and phase tracking reference signals (PT-RSs). These physical layer signals are described in more detail below.

[0099] FIG. 2B An example NR control plane protocol stack is illustrated. As FIG. 6 As shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the example NR user plane protocol stack. The four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. The NR control plane stack has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack, rather than having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack.

[0100] The NAS protocols 217 and 237 can provide control plane functionality between the UE 210 and an AMF 230 (e.g., the AMF 158A), or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 can provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 over which NAS messages can be transmitted. NAS messages can be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 can provide control plane functionality such as authentication, security, connection establishment, mobility management, and session management.

[0101] RRC 216 and 226 can provide control plane functionality between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRC 216 and 226 can provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages can be sent using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers between the UE 210 and the RAN. The MAC can multiplex control plane data and user plane data into the same transport blocks (TBs). The RRC 216 and 226 can provide control plane functionality such as: broadcasting of system information related to AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN; security functions, including key management; signaling radio bearers and data radio bearers establishment, configuration, maintenance, and release; mobility functions; QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, the RRC 216 and 226 can establish an RRC context, which can involve configuring parameters for communication between the UE 210 and the RAN.

[0102] FIG. 1A is an example diagram illustrating RRC state transitions of a UE. The UE can be the same as or similar to the wireless device 106, FIG. 2A depicted in FIG. 1, FIG. 2B and FIG. 6 the UE 210 depicted in FIG. 2, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, FIG. 1A the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC CONNECTED), RRC idle 604 (e.g., RRC IDLE), and RRC inactive 606 (e.g., RRC INACTIVE).

[0103] In the RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with a base station. The base station can be the same as or similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1, FIG. 1B the gNB 160 or ng-eNB 162 depicted in FIG. 1, FIG. 2A and FIG. 2B and FIG. 1BThe base station to which a UE is connected can have an RRC context for the UE. The RRC context, referred to as a UE context, can include parameters for communication between the UE and the base station. These parameters can include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. Mobility for a UE, while in an RRC connected 602, can be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE can measure signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station can request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608, or to RRC inactive 606 through a connection suspend procedure 610.

[0104] In RRC idle 604, there can not be an RRC context for the UE established. In RRC idle 604, the UE can not have an RRC connection with a base station. While in RRC idle 604, the UE can spend most of the time in a sleep state (e.g., to conserve battery power). The UE can periodically wake up (e.g., once per discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility for the UE can be managed by the UE through a procedure known as cell reselection. The RRC state can transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which can involve a random access procedure, discussed in more detail below.

[0105] In RRC inactive 606, a previously established RRC context is maintained in the UE and the base station. This allows for a quick transition to RRC connected 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE can be in a sleep state, and mobility for the UE can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614, or to RRC idle 604 through a connection release procedure 616, which can be the same as or similar to the connection release procedure 608.

[0106] RRC states can be associated with mobility management mechanisms. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to inform the UE of events via paging messages without having to broadcast the paging messages throughout the mobile communication network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 can allow the network to track the UE at a cell group level, such that a paging message can be broadcast within the cell group that the UE is currently camped within, rather than throughout the mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE at a cell group level. These mechanisms can use different grouping granularities for tracking. For example, there can be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and a group of cells within a RAN area, which is referred to as a tracking area and identified by a tracking area identifier (TAI).

[0107] Tracking areas can be used to track the UE at a CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE’s registration area. If the UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with the UE’s registration area, the UE can perform a registration update with the CN to allow the CN to update the UE’s location and provide the UE with a new UE registration area.

[0108] RAN areas can be used to track the UE at a RAN level. For a UE in RRC inactive 606 state, the UE can be assigned a RAN notification area. The RAN notification area can include one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station can belong to one or more RAN notification areas. In an example, a cell can belong to one or more RAN notification areas. If the UE moves through cell reselection to a cell that is not included in the RAN notification area assigned to the UE, the UE can perform a notification area update with the RAN to update the UE’s RAN notification area.

[0109] A base station that stores the RRC context of the UE or the last serving base station of the UE can be referred to as an anchor base station. The anchor base station can maintain the RRC context of the UE at least during a period of time that the UE stays in the RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.

[0110] A gNB, such as gNB 104, can be a base station of a RAN (e.g., NG-RAN 104 or 5G-RAN 154) that provides RRC services to UEs. The gNB can be a base station of a RAN that provides RRC services to UEs in RRC idle 604 and RRC inactive 606 states. FIG. 5AThe gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0111] In NR, physical signals and physical channels (about FIG. 5B and FIG. 7 The concepts discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is... F A multicarrier communication scheme that transmits data on orthogonal subcarriers (or frequency modulation). Before transmission, the data can be mapped to a series of complex symbols (e.g., M-QAM or M-PSK symbols), which are called source symbols and are divided into... F A parallel symbol stream. F The parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) symbols that transform them to the time domain. An IFFT block can receive... F One source symbol, one source symbol comes from this F Each of the parallel symbol streams, and using each source symbol to modulate the signal. F Corresponding to each orthogonal subcarrier F The magnitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent the magnitude and phase of that sinusoidal basis function. F The sum of orthogonal subcarriers F One time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an IFFT block. This operation produces OFDM symbols pre-decoded by Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing of the OFDM symbols can be performed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0112] FIG. 7An example configuration of an NR frame into which OFDM symbols are grouped is illustrated. An NR frame can be identified by a system frame number (SFN). The SFN can repeat with a period of 1024 frames. As illustrated, the duration of one NR frame can be 10 milliseconds (ms), and can include 10 subframes of 1 ms duration. The subframes can be divided into slots, which include, for example, 14 OFDM symbols per slot.

[0113] The duration of a slot can depend on the numerology of the OFDM symbols used for the slot. In NR, flexible numerologies are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the millimeter wave range). A numerology can be defined in terms of subcarrier spacing and cyclic prefix duration. For numerologies in NR, the subcarrier spacing can be scaled by powers of 2 from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be scaled by powers of 2 from a baseline cyclic prefix duration of 4.7 μβ. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μβ; 30 kHz / 2.3 μβ; 60 kHz / 1.2 μβ; 120 kHz / 0.59 μβ; and 240 kHz / 0.29 μβ.

[0114] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations, and accordingly, more slots per subframe. FIG. 7 This dependence of slot duration and per-subframe slot transmission structure on numerology is illustrated (for ease of illustration, FIG. 8 numerologies with 240 kHz subcarrier spacing are not shown in FIG. 1). Subframes in NR can be used as a time reference independent of numerology, while slots can be used as the unit on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR can be decoupled from slot duration, and can start at any OFDM symbol, and continue for as many symbols as needed for the transmission. These partial-slot transmissions can be referred to as mini-slot or sub-slot transmissions.

[0115] FIG. 8 An example configuration of a slot in the time and frequency domains of an NR carrier is illustrated. A slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. As shown, an RE spans one OFDM symbol in the time domain and one subcarrier in the frequency domain. FIG. 8 As shown, an RE spans one OFDM symbol in the time domain and one subcarrier in the frequency domain. FIG. 8As shown, an RB spans twelve consecutive REs in the frequency domain. An NR carrier can be limited to a width of 275 RBs or 275 x 12 = 3300 subcarriers. If such a limit is used, an NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth limit can be set on a per-carrier basis.

[0116] FIG. 9 A single numerology used across the entire bandwidth of an NR carrier is illustrated. In other example configurations, multiple numerologies can be supported on the same carrier.

[0117] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs can be capable of receiving the full carrier bandwidth (e.g., due to hardware limitations). Furthermore, receiving the full carrier bandwidth can be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE can adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

[0118] NR defines bandwidth parts (BWPs) to support UEs that are not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of contiguous RBs on a carrier. A UE can be configured (e.g., via an RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs of a serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0119] For unpaired spectrum, a downlink BWP from the set of configured downlink BWPs can be associated with an uplink BWP from the set of configured uplink BWPs if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. For unpaired spectrum, a UE can expect the center frequency of a downlink BWP to be the same as the center frequency of an uplink BWP.

[0120] For a downlink BWP in a configured set of downlink BWPs on a primary cell (PCell), a base station can configure the UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in time and frequency domain where a UE can find control information. A search space can be a UE-specific search space or a common search space (potentially able to be used by multiple UEs). For example, a base station can configure a UE with a common search space on a PCell in an active downlink BWP on a PCell or on a primary secondary cell (PSCell).

[0121] For an uplink BWP in a configured set of uplink BWPs, a BS can configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE can receive a downlink reception (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. A UE can transmit an uplink transmission (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length) for the uplink BWP.

[0122] One or more BWP indicator fields can be provided in downlink control information (DCI). A value of a BWP indicator field can indicate which BWP in a configured set of BWPs is an active downlink BWP for one or more downlink receptions. Values of the one or more BWP indicator fields can indicate an active uplink BWP for one or more uplink transmissions.

[0123] A base station can semi-statically configure a UE with a default downlink BWP within a configured set of downlink BWPs associated with a PCell. If the base station does not provide the UE with a default downlink BWP, the default downlink BWP can be an initial active downlink BWP. A UE can determine which BWP is an initial active downlink BWP based on CORESET configuration obtained using PBCH.

[0124] A base station can configure a UE with a BWP inactivity timer value for a PCell. A UE can start or restart a BWP inactivity timer at any appropriate time. For example, a UE can start or restart a BWP inactivity timer when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation; or a b ​) When the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than a default downlink BWP or a default uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI during a time interval (e.g., 1 ms or 0.5 ms), the UE can run a BWP inactivity timer to expiration (e.g., increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0125] In an example, a base station can semi-statically configure a UE with one or more BWPs. In response to receiving a DCI indicating a second BWP as an active BWP and / or in response to expiration of a BWP inactivity timer (e.g., if the second BWP is a default BWP), the UE can switch the active BWP from a first BWP to the second BWP.

[0126] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a currently inactive BWP) can be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0127] FIG. 9 Examples are illustrated for bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs can switch from one BWP to another BWP at a switching point. In FIG. 9 In the illustrated example, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz, a subcarrier spacing of 15 kHz; a BWP 906 with a bandwidth of 20 MHz, a subcarrier spacing of 60 kHz. The BWP 902 can be an initial active BWP, and the BWP 904 can be a default BWP. The UE can switch between the BWPs at a switching point. In FIG. 10AIn the example of FIG. 9, the UE can switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 can occur for any suitable reason, e.g., in response to expiration of a BWP inactivity timer (indicating a switch to a default BWP) and / or in response to receiving a DCI indicating BWP 904 as an active BWP. In response to receiving a DCI indicating BWP 906 as an active BWP, the UE can switch from active BWP 904 to BWP 906 at switch point 910. In response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as an active BWP, the UE can switch from active BWP 906 to BWP 904 at switch point 912. In response to receiving a DCI indicating BWP 902 as an active BWP, the UE can switch from active BWP 904 to BWP 902 at switch point 914.

[0128] If a UE is configured for a secondary cell with a timer value and a default downlink BWP in a configured set of downlink BWPs, the UE procedure for switching BWPs on the secondary cell can be the same / similar as on the primary cell. For example, the UE can use the timer value and the default downlink BWP for the secondary cell in the same / similar manner that the UE uses these values for the primary cell.

[0129] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit to / from the same UE simultaneously. The carriers aggregated in CA can be referred to as component carriers (CCs). When CA is used, there are multiple serving cells for a UE, one serving cell for each CC. CCs can have three configurations in the frequency domain.

[0130] FIG. 4B Three CA configurations with two CCs are illustrated. In intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are directly adjacent to each other within the frequency band. In intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated by a gap in the frequency band. In inter-band configuration 1006, the two CCs are in frequency bands (frequency band A and frequency band B).

[0131] In an example, up to 32 CCs can be aggregated. The aggregated CCs can have the same or different bandwidth, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell of a UE using CA can have downlink CCs. For FDD, one or more uplink CCs can optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers can be useful when a UE has more data traffic in the downlink than in the uplink.

[0132] When using CA, one of the UE's aggregated cells can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE initially connects at RRC connection setup, re-establishment, and / or handover. The PCell can provide NAS mobility information and security input to the UE. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). The UE's other aggregated cells can be referred to as secondary cells (SCells). In an example, SCells can be configured after the PCell is configured for the UE. For example, SCells can be configured through an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to an SCell can be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to an SCell can be referred to as an uplink secondary CC (UL SCC).

[0133] Configured SCells of a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivating an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Configured SCells can be activated and deactivated using MAC CEs for SCell Activation / Deactivation. FIG. 10B

[0134] Downlink control information for a cell, such as scheduling assignments and scheduling grants, can be transmitted on the cell corresponding to the allocation and grant, which is referred to as self-scheduling. DCI for the cell can be transmitted on another cell, which is referred to as cross-carrier scheduling. Uplink control information for aggregated cells, for example, HARQ acknowledgements and channel state feedback such as CQI, PMI, and / or RI, can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH can become overloaded. Cells can be divided into multiple PUCCH groups.

[0135] FIG. 10B Examples are illustrated of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In FIG. 10B ​In the example of PUCCH group 1010, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. In the example, PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary SCell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In an example, if FIG. 5A If the aggregated cells depicted in FIG. 10 were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell would be used to transmit UCI related to the downlink CCs, and that PCell can become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overloading can be prevented.

[0136] A cell, which includes a downlink carrier and optionally an uplink carrier, can be assigned a physical cell ID and a cell index. The physical cell ID or the cell index can identify the downlink carrier and / or the uplink carrier of the cell, e.g., depending on the context in which the physical cell ID is used. The physical cell ID can be determined using a synchronization signal transmitted on a downlink component carrier. The cell index can be determined using an RRC message. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure refers to a first physical cell ID of a first downlink carrier, this disclosure can mean that the first physical cell ID is for a cell that includes the first downlink carrier. The same / similar concept can apply to, e.g., carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell that includes the first carrier is activated.

[0137] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, a HARQ entity can operate on a serving cell. Transport blocks can be generated per allocation / grant of a serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to the serving cell.

[0138] In the downlink, a base station can transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG. 5B ). In the uplink, a UE can transmit one or more RSs (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. 11A ). The PSS and SSS can be transmitted by a base station and used by a UE to synchronize with the base station. The PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station can periodically transmit a burst of SS / PBCH blocks.

[0139] FIG. 11A Examples of structures and locations of SS / PBCH blocks are illustrated. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11A ). The burst can be transmitted periodically (e.g., every 2 frames or 20 ms). The burst can be limited to a half frame (e.g., the first half frame with a duration of 5 ms). It should be understood that FIG. 11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, location of the burst within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the numerology or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factors. In examples, a UE can assume a subcarrier spacing of SS / PBCH blocks based on the monitored carrier frequency, unless the radio network configures the UE to assume a different subcarrier spacing.

[0140] An SS / PBCH block can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11B ) and can span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, SSS, and PBCH can have a common center frequency. The PSS can be transmitted first and can span, for example, 1 OFDM symbol and 127 subcarriers. The SSS can be transmitted after the PSS (e.g., two symbols later) and can span 1 OFDM symbol and 127 subcarriers. The PBCH can be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and can span 240 subcarriers.

[0141] A UE can not know the location of an SS / PBCH block in time and frequency domains (e.g., if the UE is searching for a cell). To find and select the cell, the UE can monitor a carrier for a PSS. For example, the UE can monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in time and frequency domains, the UE can determine the locations of an SSS and a PBCH, respectively, based on a known structure of the SS / PBCH block. The SS / PBCH block can be a cell-defining SS block (CD-SSB). In an example, a primary cell can be associated with a CD-SSB. The CD-SSB can be located on a synchronization raster. In an example, cell selection / searching and / or reselection can be based on the CD-SSB.

[0142] An SS / PBCH block can be used by a UE to determine one or more parameters of a cell. For example, the UE can determine a physical cell identifier (PCI) of the cell based on sequences of a PSS and an SSS, respectively. The UE can determine a location of a frame boundary of the cell based on a location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission pattern in which SS / PBCH blocks in the transmission pattern are a known distance from a frame boundary.

[0143] A PBCH can use QPSK modulation and can use forward error correction (FEC). The FEC can use polar coding. One or more symbols spanned by the PBCH can carry one or more DMRSs used to demodulate the PBCH. The PBCH can include an indication of a current system frame number (SFN) and / or an SS / PBCH block timing index of the cell. These parameters can facilitate time synchronization of the UE to the base station. The PBCH can include a master information block (MIB) used to provide one or more parameters to the UE. The MIB can be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI can include a system information block type 1 (SIB1). The SIB1 can contain information needed by the UE to access the cell. The UE can use one or more parameters of the MIB to monitor a PDCCH, which can be used to schedule a PDSCH. The PDSCH can include the SIB1. The SIB1 can be decoded using parameters provided in the MIB. The PBCH can indicate an absence of the SIB1. Based on the PBCH indicating the absence of the SIB1, the UE can be pointed to a frequency. The UE can search for an SS / PBCH block at the frequency to which the UE is pointed.

[0144] A UE can assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (e.g., have a same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameter). The UE can not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices.

[0145] SS / PBCH blocks (e.g., those within a half frame) can be transmitted in spatial directions (e.g., using different beams that span a coverage area of a cell). In an example, a first SS / PBCH block can be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block can be transmitted in a second spatial direction using a second beam.

[0146] In an example, a base station can transmit multiple SS / PBCH blocks within a frequency span of a carrier. In an example, a first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks can be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations can be different or the same.

[0147] A CSI-RS can be transmitted by a base station and used by a UE to acquire channel state information (CSI). A base station can configure one or more CSI-RSs for a UE for channel estimation or any other suitable purpose. A base station can configure a UE with one or more of the same / similar CSI-RSs. A UE can measure the one or more CSI-RSs. A UE can estimate a downlink channel state and / or generate a CSI report based on measurements of the one or more downlink CSI-RSs. A UE can provide a CSI report to a base station. A base station can use feedback provided by a UE (e.g., estimated downlink channel state) to perform link adaptation.

[0148] A base station can semi-statically configure a UE with one or more CSI-RS resource sets. A CSI-RS resource can be associated with a location in time and frequency domain and a periodicity. A base station can selectively activate and / or deactivate a CSI-RS resource. A base station can indicate to a UE that a CSI-RS resource in a CSI-RS resource set is activated and / or deactivated.

[0149] A base station can configure a UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with a timing and / or periodicity of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure a configured CSI-RS resource and provide a CSI report related to the measurement. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate the periodic reporting. The base station can use RRC signaling to configure a set of CSI-RS resources and CSI reports for a UE.

[0150] A CSI-RS configuration can include one or more parameters indicating, for example, up to 32 antenna ports. When a downlink CSI-RS and a control resource set (CORESET) are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of physical resource blocks (PRBs) configured for the CORESET, the UE can be configured to take the same OFDM symbols for the downlink CSI-RS and the CORESET. When a downlink CSI-RS and a SS / PBCH block are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH block, the UE can be configured to take the same OFDM symbols for the downlink CSI-RS and the SS / PBCH block.

[0151] A downlink DMRS can be transmitted by a base station and used by a UE for channel estimation. For example, a downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network can support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for a PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to 4 orthogonal downlink DMRS ports per UE. A radio network can support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence can be the same or different. A base station can transmit a downlink DMRS and a corresponding PDSCH using a same precoding matrix. A UE can use one or more downlink DMRSs for coherent demodulation / channel estimation of a PDSCH.

[0152] In an example, a transmitter (e.g., a base station) can use a precoder matrix for a portion of a transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix can be different based on the first bandwidth being different than the second bandwidth. A UE can assume a same precoding matrix is used across a set of PRBs. The set of PRBs can be denoted as a precoding resource block group (PRG).

[0153] A PDSCH can include one or more layers. A UE can assume that there is at least one symbol with a DMRS on one of the one or more layers of the PDSCH. A higher layer can configure a PDSCH with up to 3 DMRS.

[0154] Downlink PT-RS can be transmitted by a base station and used by a UE for phase- noise compensation. Whether or not a downlink PT-RS is present can depend on RRC configuration. The presence and / or pattern of a downlink PT-RS can be configured on a UE- specific basis using a combination of RRC signaling and / or association with one or more parameters (e.g., modulation and coding scheme (MCS)) for other purposes (which can be indicated by DCI). When configured, the dynamic presence of a downlink PT-RS can be associated with one or more DCI parameters including at least MCS. An NR network can support multiple PT-RS densities defined in the time and / or frequency domain. When present, a frequency-domain density can be associated with at least one configuration of a scheduled bandwidth. A UE can assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports can be fewer than a number of DMRS ports in a scheduled resource. A downlink PT-RS can be confined in a scheduled time / frequency duration for the UE. A downlink PT-RS can be transmitted on a symbol to facilitate phase tracking at a receiver.

[0155] A UE can transmit an uplink DMRS to a base station for channel estimation. For example, a base station can use an uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, a UE can transmit an uplink DMRS with a PUSCH and / or a PUCCH. An uplink DM-RS can span a range of frequencies similar to a range of frequencies associated with a respective physical channel. A base station can configure a UE with one or more uplink DMRS configurations. At least one DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs can be configured to be transmitted at one or more symbols of a PUSCH and / or a PUCCH. A base station can semi- statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for a PUSCH and / or a PUCCH that the UE can use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network can support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) where a DMRS location, a DMRS pattern, and / or a scrambling sequence for a DMRS can be the same or different.

[0156] A PUSCH can include one or more layers, and a UE can transmit at least one symbol with a DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer can configure up to three DMRSs for a PUSCH.

[0157] Uplink PT-RS (which can be used by a base station for phase tracking and / or phase noise compensation) can or can not be present, depending on the RRC configuration of the UE. The presence and / or pattern of uplink PT-RS can be configured on a UE- specific basis by a combination of RRC signaling and / or one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters including at least MCS. A radio network can support multiple uplink PT-RS densities defined in time domain / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can assume the same precoding for DMRS ports and PT-RS ports. In the scheduled resources, the number of PT-RS ports can be fewer than the number of DMRS ports. For example, uplink PT-RS can be confined in the scheduled time / frequency duration of the UE.

[0158] SRS can be transmitted by a UE to a base station for channel state estimation to support scheduling and / or link adaptation depending on the uplink channel. The SRS transmitted by a UE can allow the base station to estimate a state of the uplink channel at one or more frequencies. A scheduler at the base station can employ the estimated state of the uplink channel to assign one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically configure one or more SRS resource sets for a UE. For an SRS resource set, the base station can configure the UE with one or more SRS resources. SRS resource set applicability can be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, SRS resources in an SRS resource set of the one or more SRS resource sets (e.g., with same / similar time domain behavior, periodicity, and / or aperiodic, etc.) can be transmitted at one time (e.g., simultaneously). The UE can transmit one or more SRS resources in an SRS resource set. An NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the one or more trigger types can include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format can be used for the UE to select at least one configured SRS resource set of one or more configured SRS resource sets. SRS trigger type 0 can refer to SRS triggered based on higher layer signaling. SRS trigger type 1 can refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE can be configured to transmit SRS after transmitting the PUSCH and corresponding uplink DMRS.

[0159] A base station can semi-statically configure a UE with one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier; a number of SRS ports; a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); a slot, mini-slot, and / or subframe level periodicity; an offset of periodic and / or aperiodic SRS resources; a number of OFDM symbols in the SRS resource; a starting OFDM symbol of the SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.

[0160] An antenna port is defined such that a symbol conveyed on the antenna port can be inferred from another symbol conveyed on the same antenna port. If a first symbol and a second symbol are transmitted on the same antenna port, a receiver can infer a channel used to convey the second symbol on the antenna port from a channel used to convey the first symbol on the antenna port (e.g., a fading gain and / or a multipath delay, etc.). A first antenna port and a second antenna port can be referred to as being quasi co-located (QCLed) if one or more large scale properties of a channel conveying a first symbol on the first antenna port can be inferred from a channel conveying a second symbol on the second antenna port. The one or more large scale properties can include at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or a spatial receive (Rx) parameter.

[0161] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamformed reference signals. A UE can perform downlink beam measurement based on a downlink reference signal (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE can perform a downlink beam measurement procedure after establishing an RRC connection with a base station.

[0162] FIG. 11B An example of a channel state information reference signal (CSI-RS) mapped in time and frequency domain is illustrated. FIG. 11BThe squares shown in the middle can span resource blocks (RBs) within a bandwidth of a cell. The base station can transmit one or more RRC messages that include CSI-RS resource configuration parameters that indicate one or more CSI-RSs. For a CSI-RS resource configuration, one or more of the following parameters can be configured by higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), CSI-RS subframe configuration (e.g., subframe locations, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., qcl-csi-rs-configNZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0163] FIG. 11B The three beams illustrated in the middle can be configured for a UE in a UE-specific configuration. FIG. 11B Three beams (Beam #1, Beam #2, and Beam #3) are illustrated in the middle, more or fewer beams can be configured. Beam #1 can be allocated with CSI-RS 1101, which can be transmitted in one or more subcarriers in the RBs of the first symbol. Beam #2 can be allocated with CSI-RS 1102, which can be transmitted in one or more subcarriers in the RBs of the second symbol. Beam #3 can be allocated with CSI-RS 1103, which can be transmitted in one or more subcarriers in the RBs of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time division multiplexing (TDM), a beam for a UE can be configured such that the beam for the UE uses a symbol from a beam for another UE.

[0164] A CSI-RS (such as FIG. 12AThe CSI-RSs (e.g., CSI-RSs 1101, 1102, 1103) illustrated in the middle can be transmitted by a base station and used by a UE for one or more measurements. For example, a UE can measure a reference signal received power (RSRP) of a configured CSI-RS resource. The base station can configure a reporting configuration for the UE, and the UE can report the RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, the base station can determine one or more transmission configuration indication (TCI) states including multiple reference signals based on the reported measurements. In an example, the base station can indicate the one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with receive (Rx) beams determined based on the one or more TCI states. In an example, the UE can or can not have a beam correspondence capability. If the UE has a beam correspondence capability, the UE can determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of a corresponding Rx beam. If the UE does not have a beam correspondence capability, the UE can perform an uplink beam selection procedure to determine a spatial domain filter of a Tx beam. The UE can perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station can select and indicate an uplink beam for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0165] In a beam management procedure, a UE can evaluate (e.g., measure) a channel quality of one or more beam pair links, a beam pair link including a transmit beam transmitted by a base station and a receive beam received by the UE. Based on the evaluation, the UE can transmit a beam measurement report indicating one or more beam pair quality parameters including, for example, one or more beam identifications (e.g., beam indices or reference signal indices, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0166] FIG. 12BExamples of three downlink beam management procedures (P1, P2, and P3) are illustrated. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit receive point (TRP) (or multiple TRPs), e.g., to support selection of one or more base station Tx beams and / or UE Rx beams (illustrated as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping over a set of beams (illustrated as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping over a set of beams (illustrated as ellipses rotating in a clockwise direction, indicated by dashed arrows, in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (illustrated as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top row of P2). The UE and / or base station can perform procedure P2 using a smaller set of beams than used in procedure P1, or using narrower beams than used in procedure P1. This can be referred to as beam optimization. The UE can perform procedure P3 for Rx beam determination by using the same Tx beams at the base station and sweeping Rx beams at the UE.

[0167] FIG. 13A Examples of three uplink beam management procedures (U1, U2, and U3) are illustrated. Procedure U1 can be used to enable a base station to perform measurements of Tx beams of a UE, e.g., to support selection of one or more UE Tx beams and / or base station Rx beams (illustrated as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, e.g., Tx beam sweeping over a set of beams (illustrated as ellipses rotating in a clockwise direction, indicated by dashed arrows, in the bottom rows of U1 and U3). Beamforming at the base station can include, e.g., Rx beam sweeping over a set of beams (illustrated as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top rows of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beams when a UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than used in procedure P1, or using narrower beams than used in procedure P1. This can be referred to as beam optimization. The UE can adjust its Tx beams when a base station uses a fixed Rx beam by performing procedure U3.

[0168] A UE can initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE can transmit a BFR request (e.g., a preamble, UCI, SR, and / or MAC CE, etc.) based on initiation of the BFR procedure. The UE can detect a beam failure based on determining that a quality of a beam pair link of an associated control channel is not satisfactory (e.g., has an error rate above an error rate threshold, a received signal power below a received signal power threshold, and / or expiration of a timer, etc.).

[0169] A UE can measure a quality of a beam pair link using one or more reference signals (RSs) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link can be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. A base station can indicate that a RS resource is quasi co-located (QCL) with one or more DM-RSs of a channel (e.g., a control channel and / or a shared data channel, etc.). The RS resource and the one or more DMRSs of the channel can be QCL when channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, and / or fading, etc.) of transmissions to the UE via the RS resource are similar or the same as channel characteristics of transmissions to the UE via the channel.

[0170] A network (e.g., a gNB and / or ng-eNB of the network) and / or a UE can initiate a random access procedure. A UE in an RRC_IDLE state and / or an RRC_INACTIVE state can initiate a random access procedure to request connection setup to the network. A UE can initiate a random access procedure from an RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for an uplink transmission of an SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when an uplink synchronization status is non-synchronized). A UE can initiate a random access procedure for a beam failure recovery request. A network can initiate a random access procedure for a handover and / or for establishing a time alignment for SCell addition.

[0171] FIG. 13A A four-step contention-based random access procedure is illustrated. Prior to initiating the procedure, a base station can transmit a configuration message 1310 to a UE. FIG. 13AThe procedure illustrated in the middle includes the transmission of four messages (Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314). Msg 1 1311 can include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 can include and / or be referred to as a random access response (RAR).

[0172] The configuration message 1310 can be transmitted, for example, using one or more RRC messages. The one or more RRC messages can indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters can include at least one of: general parameters for one or more random access procedures (e.g., RACH configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station can broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages can be UE-specific (e.g., a dedicated RRC message sent to a UE in RRC CONNECTED state and / or in RRC INACTIVE state). The UE can determine time-frequency resources and / or uplink transmit power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE can determine reception timing and downlink channels for receiving Msg 2 1312 and Msg 4 1314.

[0173] The one or more RACH parameters provided in the configuration message 1310 can indicate one or more physical RACH (PRACH) occasions that can be used for transmitting Msg 1 1311. The one or more PRACH occasions can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters can indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters can indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals can be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters can indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH block.

[0174] The one or more RACH parameters provided in the configuration message 1310 can be used to determine an uplink transmit power for Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for a preamble transmission (e.g., a reception target power and / or an initial power for the preamble transmission). There can be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters can indicate: a power ramping step; a power offset between SSBs and CSI-RSs; a power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters can indicate one or more thresholds based on which the UE can determine at least one reference signal (e.g., SSBs and / or CSI-RSs) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0175] Msg 1 1311 can include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group can include one or more preambles. The UE can determine a preamble group based on a path loss measurement and / or a size of Msg 3 1313. The UE can measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, the UE can select at least one preamble associated with the one or more reference signals and / or a selected preamble group if an association between the one or more preambles and the at least one reference signal is configured by the RRC message.

[0176] The UE can determine a preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE can determine a preamble based on a path loss measurement, an RSRP measurement, and / or a size of Msg 3 1313. In another example, the one or more RACH parameters can indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE can determine a preamble to include in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH occasions. The UE can use one or more reference signals (e.g., SSBs and / or CSI-RSs) to select a preamble and determine a PRACH occasion. The one or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate an association between the PRACH occasion and the one or more reference signals.

[0177] If no response is received after a preamble transmission, the UE can perform a preamble retransmission. The UE can increase an uplink transmit power for the preamble retransmission. The UE can select an initial preamble transmit power based on a path loss measurement and / or a target received preamble power configured by the network. The UE can determine a retransmission preamble and can ramp up the uplink transmit power. The UE can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step can be an amount of incremental increase of the uplink transmit power for the retransmission. If the UE determines the same reference signal (e.g., SSB and / or CSI-RS) as a previous preamble transmission, the UE can ramp up the uplink transmit power. The UE can count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold (e.g., preambleTransMax) configured by the one or more RACH parameters, the UE can determine that the random access procedure is not successfully completed.

[0178] Msg 2 1312 received by the UE can include a RAR. In some scenarios, Msg 2 1312 can include multiple RARs corresponding to multiple UEs. Msg 2 1312 can be received after or in response to transmitting Msg 1 1311. Msg 2 1312 can be scheduled on a DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 can indicate that Msg 1 1311 was received by the base station. Msg 2 1312 can include a time alignment command that can be used by the UE to adjust the UE’s transmit timing, a scheduling grant to transmit Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting a preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to start the time window based on the PRACH occasion the UE used to transmit the preamble. For example, the UE can start the time window one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH occasion from the end of the preamble transmission). The one or more symbols can be determined based on the numerology. The PDCCH can be in a common search space (e.g., Type 1-PDCCH common search space) configured by an RRC message. The UE can identify the RAR based on a radio network temporary identifier (RNTI). The RNTI can be used depending on one or more events that initiated the random access procedure. The UE can use a random access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH occasion in which the UE transmitted the preamble. For example, the UE can determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or an UL carrier indicator of the PRACH occasion. An example of the RA-RNTI can be as follows: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id where s_id can be an index of the first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id can be an index of the first slot of the PRACH occasion in a system frame (e.g., 0 ≤ t_id < 80), f_id can be an index of the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for the preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0179] The UE can transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using resources identified in Msg 2 1312). Msg 3 1313 can be used, for example, to request resources for transmission of data to the base station. Msg 3 1313 can include a CCCH SDU that was transmitted in Msg 1 1311. FIG. 13B Contention resolution in the illustrated contention-based random access procedure. In some scenarios, multiple UEs can transmit the same preamble to the base station, and the base station can provide a RAR corresponding to the UE. If multiple UEs interpret the RAR as corresponding to themselves, a collision can occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE can include a device identifier (e.g., a C-RNTI (if assigned), a TC-RNTI included in Msg 2 1312, and / or any other suitable identifier) in Msg 3 1313.

[0180] Msg 4 1314 can be received after or in response to transmitting Msg 3 1313. If a C-RNTI is included in Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in RRC IDLE state or is otherwise not connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to a CCCH SDU transmitted (e.g., sent) in Msg 3 1313, the UE can determine that contention resolution is successful and / or the UE can determine that the random access procedure is successfully completed.

[0181] A UE can be configured with a supplemental uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) can be supported in the uplink carrier. For example, a base station can configure a UE with two separate RACH configurations: one for the SUL carrier and the other for the NUL carrier. For random access in a cell configured with a SUL carrier, the network can indicate which carrier to use (NUL or SUL). For example, a UE can determine a SUL carrier if the measurement quality of one or more reference signals is below a broadcast threshold. Uplink transmissions (e.g., Msg 1 1311 and / or Msg 3 1313) of the random access procedure can remain on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch the uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on a channel clear assessment (e.g., listen before talk).

[0182] FIG. 13A A two-step contention-free random access procedure is illustrated. Similar to the four-step contention-based random access procedure illustrated in FIG. 13B , a base station can transmit a configuration message 1320 to a UE prior to initiating the procedure. The configuration message 1320 can be similar in some aspects to the configuration message 1310. FIG. 13A The procedure illustrated in FIG. 13A includes the transmission of two messages (Msg 1 1321 and Msg 2 1322). Msg 1 1321 and Msg 2 1322 can be similar in some aspects to Msg 1 1311 and Msg 2 1312, respectively, illustrated in FIG. 13B and FIG. 13B , as will be appreciated.

[0183] FIG. 13B The contention-free random access procedure illustrated in

[0184] After transmitting the preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for a RAR. In the case of a beam failure recovery request, the base station can configure a separate time window and / or a separate PDCCH for the UE in a search space (e.g., recoverySearchSpaceId) indicated by an RRC message. The UE can monitor the search space for a PDCCH transmission addressed to a cell RNTI (C-RNTI). In FIG. 13C In the illustrated contention-free random access procedure, the UE can determine that the random access procedure is successfully completed after or in response to transmitting the Msg 1 1321 and receiving the corresponding Msg 2 1322. For example, the UE can determine that the random access procedure is successfully completed if the PDCCH transmission is addressed to a C-RNTI. For example, the UE can determine that the random access procedure is successfully completed if the UE receives a RAR that includes a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC subPDU with the preamble identifier. The UE can respond with an indication of an acknowledgement of the SI request.

[0185] FIG. 13A Another two-step random access procedure is illustrated. Similar to the random access procedures illustrated in FIG. 13B and FIG. 13C The base station can transmit a configuration message 1330 to the UE prior to initiating the procedure. The configuration message 1330 can be similar in some aspects to the configuration message 1310 and / or the configuration message 1320. FIG. 13A The procedure illustrated in includes the transmission of two messages (Msg A 1331 and Msg B 1332).

[0186] The Msg A 1331 can be transmitted by the UE in an uplink transmission. The Msg A 1331 can include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 can include content similar to and / or equivalent to the content of the Msg 3 1313 illustrated in FIG. 13A The transport block 1342 can include UCI (e.g., SR and / or HARQ ACK / NACK, etc.). The UE can receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 can include content similar to and / or equivalent to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg4 1314 illustrated in FIG. 13B and FIG. 13A The Msg B 1332 can include content similar to and / or equivalent to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg4 1314 illustrated in FIG. 13C The Msg B 1332 can include content similar to and / or equivalent to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg4 1314 illustrated in

[0187] A UE can initiate a two-step random access procedure in 1330 for a licensed spectrum and / or an unlicensed spectrum. The UE can determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors can be: a radio access technology in use (e.g., LTE and / or NR, etc.); whether the UE has a valid TA; a cell size; an RRC state of the UE; a spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors. FIG. 13A

[0188] The UE can determine radio resources and / or uplink transmit power for the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on two-step RACH parameters included in the configuration message 1330. The RACH parameters can indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the transport block 1342. The time-frequency resources for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmitting the transport block 1342 (e.g., PUSCH) can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters can enable the UE to determine a reception timing and a downlink channel for monitoring and / or receiving Msg B 1332.

[0189] The transport block 1342 can include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an international mobile subscriber identity (IMSI)). The base station can transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 can include at least one of: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure is successfully completed in some cases: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., the transport block 1342).

[0190] The UE and the base station can exchange control signaling. The control signaling can be referred to as L1 / L2 control signaling and can originate from a PHY layer (e.g., layer 1) and / or a MAC layer (e.g., layer 2). The control signaling can include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0191] ​Downlink control signaling can include: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transmission format; time slot format information; pre-emption indication; power control commands; and / or any other suitable signaling. A UE can receive downlink control signaling in a payload sent by a base station on a physical downlink control channel (PDCCH). The payload sent on the PDCCH can be referred to as downlink control information (DCI). In some scenarios, the PDCCH can be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0192] A base station can attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When a DCI is intended for a UE (or a group of UEs), the base station can scramble the CRC parity bits using an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits using an identifier can include modulo-2 addition (or an exclusive-OR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of a radio network temporary identifier (RNTI).

[0193] DCIs can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled using a paging RNTI (P-RNTI) can indicate paging information and / or a system information change notification. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled using a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or a trigger of a random access of a PDCCH order. A DCI with CRC parity bits scrambled using a temporary cell RNTI (TC-RNTI) can indicate a contention resolution (e.g., similar to a PDCCH order). FIG. 14AMsg 3 1313 (e.g., Msg 3 of Msg 3 1313 illustrated in FIG. 13). Other RNTIs configured to the UE by the base station can include configured scheduling RNTI (CS-RNTI), transmit power control - PUCCH RNTI (TPC-PUCCH-RNTI), transmit power control - PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control - SRS RNTI (TPC-SRS-RNTI), interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), and / or modulation and coding scheme cell RNTI (MCS-C-RNTI), among others.

[0194] Depending on the purpose and / or content of the DCI, the base station can transmit the DCI using one or more DCI formats. For example, DCI format 0 0 is used for PUSCH scheduling in a cell. DCI format 0 0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0 1 can be used for PUSCH scheduling in a cell (e.g., with more DCI payload than DCI format 0 0). DCI format 1 0 is used for PDSCH scheduling in a cell. DCI format 1 0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1 1 can be used for PDSCH scheduling in a cell (e.g., with more DCI payload than DCI format 1 0). DCI format 2 0 can be used to provide slot format indication to a group of UEs. DCI format 2 1 can be used to inform the group of UEs of the physical resource blocks and / or OFDM symbols in which the UEs can assume no transmission intended for the UEs is transmitted. DCI format 2 2 can be used to transmit a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2 3 can be used to transmit a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions can be defined in future releases. DCI formats can have different DCI sizes, or can share the same DCI size.

[0195] After scrambling the DCI with the RNTI, the base station can process the DCI using channel decoding (e.g., polar decoding), rate matching, scrambling, and / or QPSK modulation. The base station can map the decoded and modulated DCI on resource elements used and / or configured for the PDCCH. Based on a payload size of the DCI and / or a coverage of the base station, the base station can transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of contiguous CCEs (referred to as an aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE can include a number of (e.g., 6) resource element groups (REGs). A REG can include a resource block in an OFDM symbol. Mapping the decoded and modulated DCI on resource elements can be based on a mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

[0196] FIG. 14B Examples of CORESET configuration for a bandwidth part are illustrated. A base station can transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode DCI using one or more search spaces. The base station can configure a CORESET in a time-frequency domain. In an example, a first CORESET 1401 and a second CORESET 1402 occur at a first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at a seventh symbol in the slot. CORESETs can have different numbers of resource blocks in the frequency domain. FIG. 15

[0197] FIG. 1A Examples of PDCCH processing and CCE-to-REG mapping for DCI transmission on a CORESET are illustrated. The CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station can perform different or the same CCE-to-REG mapping on different CORESETs. A CORESET can be associated with a CCE-to-REG mapping by RRC configuration. A CORESET can be configured with an antenna port quasi-co-location (QCL) parameter. The antenna port QCL parameter can indicate QCL information for a demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0198] ​A base station can transmit, to a UE, an RRC message including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters can indicate an association between a search space set and a CORESET. A search space set can include a set of PDCCH candidates formed by CCEs of a given aggregation level. The configuration parameters can indicate: a number of PDCCH candidates to monitor per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in a common search space set can be predefined and known to the UE. A set of CCEs in a UE-specific search space set can be configured based on an identity (e.g., C-RNTI) of the UE.

[0199] As shown in FIG. 1B , a UE can determine time-frequency resources of a CORESET based on the RRC message. The UE can determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) of the CORESET based on the configuration parameters of the CORESET. The UE can determine a number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE can monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring can include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI formats. The monitoring can include decoding DCI content of one or more PDCCH candidates having a possible (or configured) PDCCH location, a possible (or configured) PDCCH format (e.g., a number of CCEs, a number of PDCCH candidates in a common search space, and / or a number of PDCCH candidates in a UE-specific search space), and a possible (or configured) DCI format. The decoding can be referred to as blind decoding. The UE can determine a DCI as valid for the UE in response to a CRC check (e.g., a scrambled bit of a CRC parity of the DCI matches a RNTI value). The UE can process information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, and / or downlink preemption, etc.).

[0200] A UE can send uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling can include a hybrid automatic repeat request (HARQ) acknowledgement for a received DL-SCH transport block. The UE can send the HARQ acknowledgement after receiving the DL-SCH transport block. The uplink control signaling can include channel state information (CSI) indicating a channel quality of a physical downlink channel. The UE can send the CSI to the base station. The base station can determine a transmission format parameter (e.g., including a multiple antenna and beamforming scheme) for a downlink transmission based on the received CSI. The uplink control signaling can include a scheduling request (SR). The UE can send the SR indicating that there is uplink data available to send to the base station. The UE can send the UCI (e.g., HARQ acknowledgement (HARQ-ACK), CSI report, and SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE can send the uplink control signaling via the PUCCH using one of several PUCCH formats.

[0201] There can be five PUCCH formats, and the UE can determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of the UCI transmission and a number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. The UE can use PUCCH format 0 to send UCI in a PUCCH resource if the transmission is on one or two symbols and a number of HARQ-ACK / SR bits with a positive or negative SR is one or two. PUCCH format 1 can occupy a number of symbols between four and fourteen OFDM symbols and can include two or fewer bits. The UE can use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. The UE can use PUCCH format 2 if the transmission is on one or two symbols and the number of UCI bits is two or more. PUCCH format 3 can occupy a number of symbols between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 can occupy a number of symbols between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

[0202] A base station can transmit configuration parameters of multiple PUCCH resource sets to a UE using, for example, an RRC message. Multiple PUCCH resource sets (e.g., up to four sets) can be configured on an uplink BWP of a cell. A PUCCH resource set can be configured with a PUCCH resource set index, multiple PUCCH resources with PUCCH resources identified by PUCCH resource identifiers (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits that a UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, a UE can select one of the multiple PUCCH resource sets based on a total bit length of UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is 2 or less, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than 2 and less than or equal to a first configured value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to “3”.

[0203] After determining a PUCCH resource set from the multiple PUCCH resource sets, a UE can determine a PUCCH resource for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE can determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with DCI format 1 0 or DCI format 1 1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI can indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE can transmit the UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0204] FIG. 15 An example of a wireless device 1502 communicating with a base station 1504 is illustrated in accordance with the embodiments of the present disclosure. The wireless device 1502 and the base station 1504 can be part of a mobile communication network, such as the mobile communication network 100, FIG. 15 illustrated in FIG. 1, FIG. 2AThe mobile communication network 150 illustrated in the middle or any other communication network. FIG. 2B Only one wireless device 1502 and one base station 1504 are illustrated in the middle, but it should be understood that a mobile communication network can include more than one UE and / or more than one base station having the same or similar configuration as illustrated in the middle. FIG. 3 More than one UE and / or more than one base station having the same or similar configuration as illustrated in the middle can be included in the mobile communication network.

[0205] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. The downlink transmissions can be separated from the uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques. Other techniques, including multipath, such as downlink over a Uu interface and uplink over a PC5 interface, are also allowed.

[0206] In the downlink, data to be transmitted to the wireless device 1502 from the base station 1504 can be provided to a processing system 1508 of the base station 1504. The data can be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be transmitted to the base station 1504 from the wireless device 1502 can be provided to a processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 can include, for example, an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer with respect to FIG. 4A , FIG. 2B , FIG. 2A and FIG. 2B . Layer 3 can include an RRC layer as with respect to FIG. 3 .

[0207] After processing by the processing system 1508, the data to be transmitted to the wireless device 1502 can be provided to a transmit processing system 1510 of the base station 1504. Similarly, after processing by the processing system 1518, the data to be transmitted to the base station 1504 can be provided to a transmit processing system 1520 of the wireless device 1502. The transmit processing system 1510 and the transmit processing system 1520 can implement layer 1 OSI functionality. Layer 1 can include a PHY layer with respect to FIG. 4A , FIG. 2A , FIG. 2B and FIG. 3 . For transmit processing, the PHY layer can perform, for example, forward error correction decoding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, and / or multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0208] At base station 1504, receive processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 can receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 can implement layer 1 OSI functionality. Layer 1 can include a PHY layer with respect to FIG. 4A 、 FIG. 15 、 FIG. 15 and FIG. 16A For receive processing, the PHY layer can perform error detection, forward error correction decoding, de-interleaving, demapping of transport channels to physical channels, demodulation of physical channels, and / or MIMO or multi-antenna processing, etc.

[0209] As shown in FIG. 16A , wireless device 1502 and base station 1504 can include multiple antennas. The multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, wireless device 1502 and / or base station 1504 can have a single antenna.

[0210] Processing system 1508 and processing system 1518 can be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) can store computer program instructions or code that can be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functionalities discussed in the present application. Although FIG. 16B not shown in FIG. 15, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 can be coupled to a memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functionalities.

[0211] The processing system 1508 and / or the processing system 1518 can include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors can include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board memories, or any combination thereof. The processing system 1508 and / or the processing system 1518 can perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that can enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0212] The processing system 1508 and / or the processing system 1518 can be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware providing features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, and / or a camera, among others). The processing system 1508 and / or the processing system 1518 can receive user input data from and / or provide user output data to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power supply and / or can be configured to distribute the power to the other components in the wireless device 1502. The power supply can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to GPS chipset 1517 and GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0213] FIG. 16CExample structures for uplink transmission are illustrated. A baseband signal representing a physical uplink shared channel can perform one or more functions. The one or more functions can include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transmission layers; transform precoding to generate complex-valued symbols; precoding complex-valued symbols; mapping precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA) or CP-OFDM signals for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission can be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission can be generated by FIG. 16D transforming and precoding complex-valued symbols. These functions are illustrated as examples. Other mechanisms can be implemented in various embodiments.

[0214] FIG. 17 Another example structure for modulating and upconverting a baseband signal to a carrier frequency is illustrated. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0215] FIG. 17 Example structures for downlink transmission are illustrated. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions can include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating scrambled bits to generate complex-valued modulation symbols; mapping complex-valued modulation symbols onto one or more transmission layers; precoding complex-valued modulation symbols on a layer for transmission on an antenna port; mapping complex-valued modulation symbols for an antenna port to resource elements; generating complex-valued time-domain OFDM signals for an antenna port; and / or the like. These functions are illustrated as examples. Other mechanisms can be implemented in various embodiments.

[0216] FIG. 18 Another example structure for modulating and upconverting a baseband signal to a carrier frequency is illustrated. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0217] A wireless device can receive, from a base station, one or more messages (e.g., RRC messages) that include configuration parameters for a plurality of cells (e.g., primary cells, secondary cells). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g., as part of the configuration parameters) can include parameters for configuring a physical layer, a MAC layer, a RLC layer, a PCDP layer, a SDAP layer, a RRC layer of the wireless device. For example, the configuration parameters can include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters can include parameters that indicate values for timers for the physical layer, the MAC layer, the RLC layer, the PCDP layer, the SDAP layer, the RRC layer, and / or communication channels.

[0218] Once a timer is started, the timer can begin running and continue to run until the timer is stopped or until the timer expires. The timer can be started if the timer is not running or restarted if the timer is running. A timer can be associated with a value (e.g., the timer can be started or restarted from a value, or can be started from zero and expire once the timer reaches the value). The duration of the timer can not be updated until the timer is stopped or expires (e.g., due to a BWP switch). A timer can be used to measure a time period / window of a procedure. When this specification refers to specific implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways to implement a timer can be used to measure the time period / window of the procedure. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In an example, a time difference between two timestamps can be used instead of a start and an expiration of a random access response window timer. When a timer is restarted, the procedure for measuring the time window can be restarted. A timer can be implemented as a countdown timer that expires when a zero value is reached, a positive counting timer that expires when a target value is reached, or any other desired manner. A timer can be stopped and expire at the same time, or a timer can be stopped before expiration and can potentially be restarted. A timer can be set for a single contiguous time period with a single start time and a single end time. Alternatively, a timer can be set for a group of non-contiguous time periods, each period having a start time and an end time. In the non-contiguous case, the time periods can be periodic, as in the start time and / or end time, or can be aperiodic. Other example implementations can be provided to restart the measurement of the time window.

[0219] FIG. 19 Examples of functional architecture of artificial intelligence (AI) and / or machine learning (ML) are illustrated.

[0220] The data collection function 1701 is a function that provides input data to the model training function 1702 and the model inference function 1703.

[0221] Input data from the data collection function 1701 to the model training function 1702 is referred to as training data. The training data is used to train, validate, and test the AI / ML model in the model training function 1702. Examples of training data are measurements and statistics.

[0222] Input data from the data collection function 1701 to the model inference function 1703 is referred to as inference data. The inference data is used to generate output in the model inference function 1702. The inference data is also used to generate model performance feedback in the model inference function 1702. Examples of inference data are measurements and statistics.

[0223] The model training function 1702 is a function that can be used for training, validating, and testing of the AI / ML model. The model training function 1702 can also perform AI / ML model specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) using the training data received from the data collection function 1701.

[0224] The AI / ML model can be deployed into the model inference function 1703. The AI / ML model can be trained and tested by the model training function 1702 (e.g., prior to deployment).

[0225] The model inference function 1703 is a function that uses the deployed AI / ML model to generate inference output. The output is provided to the actor function 1704 to perform an action based on the output received from the model inference function 1703. The model inference function 1703 can perform AI / ML model specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) using the training data received from the data collection function 1701. Examples of output are determinations (predictions), policies, strategies, execution plans, and requests.

[0226] The actor function 1704 can be a function that receives output from the model inference function 1703 and performs a corresponding action.

[0227] After the actor function 1704 performs an action, feedback information can be generated and forwarded to the data collection function 1701, where it can become part of the training data or inference data. Examples of feedback information are measurements and performance indicators.

[0228] Model inference function 1703 can use inference data (including feedback information) from data collection function 1701 to monitor the performance of the deployed AI / ML model and report model performance feedback to model training function 1702. For example, over time, the characteristics of the data used to train the currently deployed AI / ML model can change. In this case, the currently deployed AI / ML model can not provide sufficiently accurate output. This can be indicated in the model performance feedback. Based on the received model performance feedback, model training function 1702 can deploy an updated AI / ML model to model inference function 1703.

[0229] In another example, the processes of AI / ML model training, AI / ML model updating, and AI / ML model inference can be performed in parallel in real-time. This is referred to as online training, as opposed to offline training. In offline training, an AI / ML model can be trained, validated, tested, and can provide acceptable performance prior to deployment.

[0230] As will be discussed in more detail below, FIG. 17 The AI / ML function architecture illustrated in FIGS. 1-3 can be used to address various tasks in a radio access network. For example, the architecture can be used to improve network signaling efficiency, network energy efficiency, perform load balancing, perform mobility optimization, or any other suitable task.

[0231] Each element of the AI / ML function architecture can reside and / or be deployed within a single network element, or across multiple network elements. Different elements of a single AI / ML function architecture can reside and / or be deployed within a single network element or in different network elements. Signaling (e.g., arrows) within the AI / ML function architecture can be performed within a particular network element or using a network interface between network elements. Network elements can include, for example, wireless devices (UEs, etc.), access networks (radio access networks, base stations, eNBs, ng-eNBs, gNBs, gNB-CUs, gNB-DUs, etc.), core network elements (AMFs, SMFs, UPFs, NWDAFs, etc.), and / or operations, administration, and maintenance (OAM).

[0232] In examples, training data and inference data can include measurements, estimates, configuration information, etc. In examples, the output of model inference 1703 can include predictions, estimates, actions, determinations, etc. In examples, feedback can include measurements, UE key performance indicators (KPIs), system-wide KPIs, etc.

[0233] The methods described in this disclosure can include one or more determinations (e.g., picks, selections, decisions, etc.). As will be discussed in more detail below, FIG. 18 and FIG. 19 It is shown that the AI / ML function architecture can be based on a model that is trained based on data collected from a network, such as a radio access network. FIG. 17 to FIG. 19The AI / ML functional architecture described in the paper is similar to the AI / ML functional architecture used in this paper to perform one or more determinations. Specifically, FIG. 18 An example of model training performed by OAM is shown, and FIG. 18 An example of model training performed by a base station is illustrated. In both cases, model inference is performed by the base station. The base station may include an actor 1704 and / or use the output of model inference 1703 to perform one or more actions (e.g., energy-saving actions). It should be understood that other architectures are possible. It should be further understood that AI / ML is not required to implement one or more of the determinations described in this disclosure. FIG. 17 Only one or more of the features described in this disclosure are shown, which may optionally be wholly or partially based on AI / ML.

[0234] FIG. 18 An example of using AI / ML in a radio access network is shown. FIG. 19 May include with FIG. 17 The AI / ML functional architecture is similar to that of the other AI / ML functional architecture. In this example, the model training function 1702 is deployed in OAM, and the model inference function 1703 is deployed in BS1 (e.g., base station, base station distributed unit, and / or base station central unit).

[0235] BS1 transmits Measurement Configuration Message 1801 to the UE. Measurement Configuration Message 1801 can configure the UE to perform measurements associated with AI / ML operations. Measurement Configuration Message 1801 can also configure the UE to provide reports associated with the measurements (e.g., measurement reports).

[0236] The UE performs measurement 1802. Measurement 1802 can be performed based on measurement configuration message 1801. The UE transmits measurement report 1803 to BS1.

[0237] BS1 transmits the received UE measurement report to OAM. The UE measurement report can be used as input data for model training 1804. The input data for model training 1804 may include measurements performed by BS1 and / or other data collected by BS1.

[0238] BS2 can transmit the input data used for model training 1805 to OAM. The input data used for model training 1805 can be similar to the input data used for model training 1804 in BS1.

[0239] The OAM performs model training 1806. The model training 1806 can be based on the measurement reports 1803, the input data for model training 1804, the input data for model training 1805, and / or other data determined by the OAM. For example, the number of measurement reports 1803, the input data for model training 1804, and the input data for model training 1805 can be in the tens of thousands, hundreds of thousands, millions, or even more. The measurement reports 1803 can be received from any number of UEs, and the input data for model training 1805 / 1806 can be received from any number of BSs. Information from other sources that can host data collection functions can be used as input for AI / ML model training.

[0240] The OAM deploys the trained AI / ML model to BS1 (model deployment / update 1807).

[0241] BS2 communicates input data for model inference 1808 to BS1.

[0242] The UE communicates a UE measurement report 1809 to BS1.

[0243] BS1 performs model inference 1810. Information from other sources that can host data collection functions can be used as input for AI / ML model inference. BS1 can also evaluate the deployed AI / ML model and communicate model performance feedback 1811 to the OAM.

[0244] Based on the output of the model inference 1810, BS1 performs actions 1812. These actions can involve UEs and other BSs, such as the UE and BS2 shown in FIG. 19 These actions can include, for example, actions to improve network energy efficiency and / or actions to perform load balancing and / or actions to perform mobility optimization in the radio access network. These actions can include, for example, communicating predictions from BS1 to BS2 and / or performing a handover of one or more wireless devices from BS1 to BS2.

[0245] After performing the actions 1812, BS1 communicates feedback 1813 to the OAM. BS2 communicates feedback 1814 to the OAM. Information from other sources that can host actor functions can be used as feedback.

[0246] FIG. 20 An example is illustrated in which AI / ML is used in a radio access network. The AI / ML can be similar to the AI / ML of FIG. 21 In this example, the model training function 1702 and the model inference function 1703 are deployed in BS1 (e.g., a base station, a base station distributed unit, and / or a base station central unit).

[0247] BS1 transmits Measurement Configuration Message 1901 to the UE. Measurement Configuration Message 1901 can configure the UE to perform measurements associated with AI / ML operations. Measurement Configuration Message 1901 can also configure the UE to provide reports associated with the measurements (e.g., measurement reports).

[0248] The UE performs measurement 1902. Measurement 1902 can be performed based on measurement configuration message 1901. The UE transmits measurement report 1903 to BS1.

[0249] BS2 transmits the input data for model training 1904 to BS1. The input data for model training 1904 may include measurements performed by BS2 and / or other data collected by BS2.

[0250] BS1 performs model training 1905. Model training 1905 may be based on measurement report 1903, input data for model training 1904, and / or other data determined by BS1. For example, the amount of measurement report 1903 and input data for model training 1904 may be tens of thousands, hundreds of thousands, millions, or even more. Measurement report 1903 can be received from any number of UEs, and input data for model training 1904 can be received from any number of BSs. Information from other sources of manageable data collection capabilities can be used as input for AI / ML model training.

[0251] BS2 transmits the input data 1906 used for model inference to BS1.

[0252] The UE transmits UE measurement report 1907 to BS1.

[0253] BS1 performs model inference 1908. Information from other sources of managed data collection capabilities can be used as input for AI / ML model inference.

[0254] Based on the output of model inference 1908, BS1 executes action 1909. These actions can involve the UE and other BSs, for example... FIG. 22 The UE and BS2 are shown in the diagram. These actions may include, for example, actions to improve network energy efficiency and / or actions to perform load balancing and / or actions to perform mobility optimization in the radio access network. These actions may include, for example, transmitting predictions from BS1 to BS2 and / or performing handover of one or more radio devices from BS1 to BS2.

[0255] After executing action 1909, BS2 sends feedback 1910 to BS1. Information from other sources of managed actor functions can be used as feedback.

[0256] The output of the model inference can have some degree of accuracy. For example, the accuracy of the prediction can be 95% or 90% or 30%, where a higher value corresponds to a higher prediction accuracy. For example, BS1 can determine that the prediction of the load of its cell 10 seconds from now will be 80%. The actual load of the cell of BS1 10 seconds later (prediction time) can be 75%. For this prediction, the accuracy is 93.75%. The accuracy can be determined by averaging the accuracy values for a number of predictions. For example, BS1 can predict candidate cells for handover of UEs. In some cases, the UEs will perform a handover to the predicted cell, in some cases, the UEs will perform a handover to another cell. For example, if 963 out of 1000 UEs perform a handover to the cell predicted by BS1 for them, the accuracy of the prediction by BS1 is 96.3%.

[0257] Whether the accuracy of the prediction is 75% or 90%, there can be cases where the prediction is inaccurate (e.g., 25% and 10% cases). Depending on the particular application in which the prediction is used, the inaccurate prediction can result in a degradation of user experience and / or an overuse of system resources of the radio access network (RAN) and / or the core network (CN).

[0258] FIG. 23 An example of a prediction and actual value of the load of cell 1 of BS1 is illustrated. The prediction can be determined, for example, in BS2. The prediction can be determined in BS2, for example, using a model. The model can include an artificial intelligence (AI) model. The model can include a machine learning (ML) model. The model can include an AI / ML model. The prediction can be determined in any other way, for example, using an extrapolation method and / or a regression method.

[0259] BS2 can predict that the load of cell 1 of BS1 will be lower than 50% for the time interval between time 1 and time 2. In the example, the load of cell 2 of BS2 can be equal to 60%. Based on the prediction and its own load (60%), BS2 can decide to offload part of the UEs served by cell 2 of BS2 to cell 1 of BS1. Based on the decision, BS2 can start performing one or more handovers of one or more UEs served by cell 2 of BS2 to cell 1 of BS1.

[0260] In an example, the actual load of Cell 1 of BS1 will become almost 100% during the time interval between Time 1 and Time 2. Since Cell 1 of BS1 will become almost fully loaded (the load is almost 100%), it will not be able to accept UEs from Cell 2 of BS2. Therefore, the handover attempt from Cell 2 of BS2 to Cell 1 of BS1 will fail. This can result in unnecessary handover signaling between BS1 and BS2. Even though some UEs will successfully handover from Cell 2 of BS2 to Cell 1 of BS1, the load of Cell 2 of BS2 will become less than 60% and the load of Cell 1 of BS1 will become almost 100%. This can result in load balancing handover from Cell 1 of BS1 to Cell 2 of BS2. Based on the inaccurate prediction of the load of Cell 1 of BS2 determined by BS2, BS2 can be making handovers of UEs to BS1, resulting in an unbalanced load situation, and BS1 can be making handovers of UEs back to BS2. This can result in unnecessary handover signaling between BS1 and BS2.

[0261] The prediction in BS2 is not limited to a prediction of the load. Other examples can include, alone or in combination, any of the following: a prediction of a signal level and / or signal quality and / or SINR; a prediction of a location and / or trajectory; a prediction of energy consumption; a prediction of QoS and / or QoE; a prediction of traffic; or a prediction of serving cells and / or neighbor cells and / or beams.

[0262] In the prior art, BS1 can transmit actual measurements of the load of Cell 1 of BS1 to BS2. BS2 can compare the actual measurements of the load of Cell 1 of BS1 to the prediction determined by BS2 to evaluate the accuracy of the prediction. If the actual measurements are not transmitted very frequently from BS1 to BS2 and the prediction is not accurate enough, BS2 can attempt to perform one or more handover attempts to BS1 before BS1 is aware that the prediction is not accurate enough. This can result in unnecessary signaling related to handovers between BS1 and BS2. If the actual measurements are transmitted very frequently from BS1 to BS2 and the prediction is accurate enough, a lot of resources can be used for signaling related to transmitting actual measurements from BS1 to BS2, and the actual measurements will not have an impact on the behavior of BS2 because the prediction of BS2 is accurate enough.

[0263] There is a need for a solution that enables at least one of the devices to determine that the prediction of BS2 is not accurate while limiting the signaling between BS2 and BS1 to only what is necessary to make the determination.

[0264] Example embodiments of the present disclosure implement enhanced mechanisms for a BS2 to configure a BS1 to perform event-based reporting to the BS2. Example embodiments of the present disclosure implement enhanced mechanisms for the BS1 to determine that a prediction by the BS2 is inaccurate based on configuration parameters received from the BS2. Example embodiments of the present disclosure implement enhanced mechanisms for the BS1 to transmit a report to the BS2 indicating that the prediction by the BS2 is inaccurate, where the report can include information requested by the BS2. This can allow the BS2 to take action to avoid negative consequences of the inaccurate prediction. For example, based on the report received from the BS1, the BS2 can determine a new prediction that can be more accurate.

[0265] Whether a prediction is accurate and / or a level of accuracy can depend on an application in which the prediction is used.

[0266] For example, the prediction can be a candidate target cell for a handover of a UE. In this case, the prediction is accurate if the UE has performed a handover to the predicted cell. The prediction is inaccurate if the UE has performed a handover to another cell.

[0267] For example, the prediction can be a load of a cell. Depending on the application, for example, a level of accuracy of 90% can be considered as sufficiently accurate. For example, the predicted load value is 40%. If the actual load measured at the time of the prediction is 38% (accuracy is 95%), the prediction can be considered as accurate. If the actual load measured at the time of the prediction is 16% (accuracy is 40%), the prediction can be considered as inaccurate.

[0268] For another example, the prediction can be a location of a UE. Depending on the application, for example, a level of accuracy of 200 meters can be configured as accurate. For example, if a distance between the predicted UE location and the actual UE location measured at the time of the prediction is 100 meters, the prediction is accurate. If a distance between the predicted UE location and the actual UE location measured at the time of the prediction is 500 meters, the prediction is inaccurate.

[0269] In example embodiments of the present disclosure, a first base station can receive, from a second base station, configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. The first base station can transmit one or more reports to the second base station based on a measured value remaining outside of the value range for the time interval.

[0270] In example embodiments of the present disclosure, the measured value can remain outside of the value range for an entire duration of the time interval.

[0271] In example implementations of the disclosure, a second base station can transmit configuration parameters for an event to a first base station. The configuration parameters for the event can include a time interval and a value range. The second base station can receive one or more reports from the first base station based on a measured value remaining outside the value range for the time interval.

[0272] In example implementations of the disclosure, a gNB-CU can receive configuration parameters for an event from a gNB-DU. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can transmit one or more reports to the gNB-DU based on a measured value remaining outside the value range for the time interval.

[0273] In example implementations of the disclosure, a gNB-DU can transmit configuration parameters for an event to a gNB-CU. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can receive one or more reports from the gNB-CU based on a measured value remaining outside the value range for the time interval.

[0274] In example implementations of the disclosure, a gNB-DU can receive configuration parameters for an event from a gNB-CU. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can transmit one or more reports to the gNB-CU based on a measured value remaining outside the value range for the time interval.

[0275] In example implementations of the disclosure, a gNB-CU can transmit configuration parameters for an event to one or more gNB-DUs. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can receive one or more reports from the one or more gNB-DUs based on a measured value remaining outside the value range for the time interval.

[0276] In example implementations of the disclosure, a gNB-CU-CP can receive configuration parameters for an event from a gNB-CU-UP. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-CP can transmit one or more reports to the gNB-CU-UP based on a measured value remaining outside the value range for the time interval.

[0277] In example implementations of the disclosure, a gNB-CU-UP can transmit configuration parameters for an event to a gNB-CU-CP. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-UP can receive one or more reports from the gNB-CU-CP based on a measured value remaining outside the value range for the time interval.

[0278] In example embodiments of the present disclosure, a gNB-CU-UP can receive configuration parameters for an event from a gNB-CU-CP. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-UP can transmit one or more reports to the gNB-CU-CP based on a measurement value remaining outside the value range for the time interval.

[0279] In example embodiments of the present disclosure, a gNB-CU-CP can transmit configuration parameters for an event to a gNB-CU-UP. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-CP can receive one or more reports from the gNB-CU-UP based on a measurement value remaining outside the value range for the time interval.

[0280] In example embodiments of the present disclosure, the configuration parameters for one or more reports can further include a value identifier.

[0281] In example embodiments of the present disclosure, the time interval can include one or more time points. The time interval can include a duration. The time interval can include a start time and an end time. The time interval can include a start time and a duration. The time interval can include a duration and an end time.

[0282] In example embodiments of the present disclosure, the value range can include values equal to one or more reference values. The value range can include values not equal to one or more reference values. The value range can include values greater than and / or greater than or equal to a threshold value. The value range can include values less than and / or less than or equal to a threshold value. The value range can include values greater than and / or greater than or equal to a first threshold value or less than and / or less than or equal to a second threshold value. The value range can include values within one or more location areas. The value range can include values outside one or more location areas.

[0283] In example implementations of the disclosure, the measurement value can comprise one or more signal metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurement value can comprise one or more location metrics of one or more wireless devices. The measurement value can comprise one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurement value can comprise one or more QoS metrics of one or more wireless devices. The measurement value can comprise one or more QoE metrics of one or more wireless devices. The measurement value can comprise one or more channel usage metrics of one or more sidelink channels for one or more wireless devices. The measurement value can comprise one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurement value can comprise one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurement value can comprise one or more cell identifiers of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs. The measurement value can comprise one or more beam identifiers of one or more beams of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs.

[0284] In example implementations of the disclosure, a first base station can receive, from a second base station, a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can comprise a time interval and a value range. The first base station can determine that the event has occurred based on a measurement value remaining outside of the value range for the time interval. The first base station can transmit the requested information to the second base station based on determining that the event has occurred.

[0285] In example embodiments of the present disclosure, a second base station can transmit, to a first base station, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The second base station can receive the requested information from the first base station based on a measurement value remaining outside the value range for the time interval.

[0286] In example embodiments of the present disclosure, a gNB-CU can receive, from a gNB-DU, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can determine that the event has occurred based on a measurement value remaining outside the value range for the time interval. The gNB-CU can transmit the requested information to the gNB-DU based on determining that the event has occurred.

[0287] In example embodiments of the present disclosure, a gNB-DU can transmit, to a gNB-CU, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can receive the requested information from the gNB-CU based on a measurement value remaining outside the value range for the time interval.

[0288] In example embodiments of the present disclosure, a gNB-DU can receive, from a gNB-CU, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can determine that the event has occurred based on a measurement value remaining outside the value range for the time interval. The gNB-DU can transmit the requested information to the gNB-CU based on determining that the event has occurred.

[0289] In example embodiments of the present disclosure, a gNB-CU can transmit, to one or more gNB-DUs, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can receive the requested information from the one or more gNB-DUs based on a measurement value remaining outside the value range for the time interval.

[0290] In example embodiments of the present disclosure, a gNB-CU-CP can receive, from a gNB-CU-UP, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-CP can determine that the event has occurred based on a measurement value remaining outside the value range for the time interval. The gNB-CU-CP can transmit the requested information to the gNB-CU-UP based on determining that the event has occurred.

[0291] In example embodiments of the disclosure, a gNB-CU-UP can transmit, to a gNB-CU-CP, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-UP can receive the requested information from the gNB-CU-CP based on a measurement value remaining outside the value range for the time interval.

[0292] In example embodiments of the disclosure, a gNB-CU-UP can receive, from a gNB-CU-CP, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-UP can determine that the event has occurred based on a measurement value remaining outside the value range for the time interval. The gNB-CU-UP can transmit the requested information to the gNB-CU-CP based on determining that the event has occurred.

[0293] In example embodiments of the disclosure, a gNB-CU-CP can transmit, to a gNB-CU-UP, configuration parameters for an event and a configuration of requested information for the event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU-CP can receive the requested information from the gNB-CU-UP based on a measurement value remaining outside the value range for the time interval.

[0294] In example embodiments of the disclosure, the requested information can include one or more signal metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more location metrics of one or more wireless devices. The requested information can include one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more QoS metrics of one or more wireless devices. The requested information can include one or more QoE metrics of one or more wireless devices. The requested information can include one or more channel usage metrics of one or more sidelink channels for one or more wireless devices. The requested information can include one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more cell identifiers of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs. The requested information can include one or more beam identifiers of one or more beams of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs.

[0295] In example embodiments of the disclosure, the configuration of the requested information can include one or more identifiers of the requested information.

[0296] In example embodiments of the present disclosure, the configuration of the requested information can include one or more frequency identifiers. The configuration of the requested information can include a number of frequencies. The configuration of the requested information can include one or more RAT identifiers. The configuration of the requested information can include a number of RATs. The configuration of the requested information can include one or more identifiers of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or cells and / or beams and / or wireless devices. The configuration of the requested information can include a number of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or wireless devices. The configuration of the requested information can include DL and / or UL and / or sidelink. The configuration of the requested information can include a number of requested reporting information request values. The configuration of the requested information can include a time interval between values of the requested reporting information.

[0297] Example embodiments of the present disclosure implement enhanced mechanisms for a second base station to configure a first base station to perform event-based reporting to the second base station. Example embodiments of the present disclosure implement enhanced mechanisms for a first base station to determine that a prediction of the second base station is inaccurate based on configuration parameters received from the second base station. Example embodiments of the present disclosure implement enhanced mechanisms for a first base station to transmit a report to a second base station indicating that a prediction of the second base station is inaccurate, where the report can include information requested by the second base station. This can allow the second base station to take action to avoid negative consequences of an inaccurate prediction. For example, based on the report received from the first base station, the second base station can determine a new prediction that can be more accurate. Example embodiments of the present disclosure also implement enhanced mechanisms between a gNB-CU and one or more gNB-DUs and between a gNB-CU-CP and a gNB-CU-UP.

[0298] FIG. 22 Example embodiments of the present disclosure are illustrated.

[0299] In example embodiments of the present disclosure, BS1 can receive one or more messages 2101 from BS2. The one or more messages 2101 can include configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. BS1 can transmit one or more reports 2102 to BS2 based on the measurement values remaining outside of the value range for the time interval. Remaining outside of the value range can occur when each measurement value during the time interval is outside of the value range, whether there is one measurement value or multiple measurement values. Remaining outside of the value range can not occur if at least one of the measurement values is within the value range during the time interval. The time interval can also be referred to as a time period.

[0300] In example embodiments of the disclosure, the configuration parameter for the event can further include a percentage. BS 1 can transmit one or more reports 2102 to BS 2 based on a percentage of measurement values that remain outside the range of values for the time interval. For example, the percentage can equal 95%. BS 1 can transmit one or more reports 2102 to BS 2 if at least 95% of the measurement values are outside the range of values during the time interval. For example, the percentage can equal 90%. BS 1 can transmit one or more reports 2102 to BS 2 if at least 90% of the measurement values are outside the range of values during the time interval.

[0301] In example embodiments of the disclosure, BS 2 can transmit one or more messages 2101 to BS 1. The one or more messages 2101 can include a configuration parameter for an event. The configuration parameter for the event can include a time interval and a range of values. BS 2 can receive one or more reports 2102 from BS 1 based on measurement values remaining outside the range of values for the time interval.

[0302] In example embodiments of the disclosure, the measurement values can remain outside the range of values for an entire duration of the time interval.

[0303] FIG. 23 and FIG. 22 Example embodiments of the disclosure are illustrated.

[0304] In FIG. 22 and FIG. 23 In examples where the range of values is between a first threshold value and a second threshold value, the time interval is between a start time and an end time.

[0305] In FIG. 23 In examples where 4 measurement values are measured, all four measurement values are below the first threshold value (outside the range of values between the first threshold value and the second threshold value). In FIG. 22 In examples where the event occurs, the measurement values remain outside the range of values for an entire duration of the time interval.

[0306] In FIG. 22 In examples where 4 measurement values are measured, 2 of the 4 measurement values are within the range of values between the first threshold value and the second threshold value. In FIG. 23 In examples where the event does not occur, the measurement values do not remain outside the range of values for an entire duration of the time interval.

[0307] In example embodiments of the disclosure, the range of values can be associated with one or more predicted values during the time interval. In FIG. 24In examples of the first case, the measurement value can differ significantly from the prediction (e.g., more than 30% or 40% of the prediction) and remain outside the value range for the entire duration of the time interval. In examples of the second case, the measurement value can not differ significantly from the prediction (e.g., less than 10% or 20% of the prediction) and not remain outside the value range for the entire duration of the time interval. The degree of difference can be adjusted by how the value range is configured. The degree of difference can be different for different models and / or model outputs and / or applications. FIG. 25 In examples of the first case, the event occurs. In examples of the second case, the event does not occur. FIG. 26 In examples of the first case, the measurement value can not differ significantly from the prediction (e.g., less than 10% or 20% of the prediction) and not remain outside the value range for the entire duration of the time interval. The degree of difference can be adjusted by how the value range is configured. The degree of difference can be different for different models and / or model outputs and / or applications.

[0308] FIG. 27 Example implementations of the present disclosure are illustrated.

[0309] In example implementations of the present disclosure, a gNB-CU can receive one or more messages 2401 from a gNB-DU. The one or more messages 2401 can include configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can transmit one or more reports 2402 to the gNB-DU based on a measurement value remaining outside the value range for the time interval.

[0310] In example implementations of the present disclosure, a gNB-DU can transmit one or more messages 2401 to a gNB-CU. The one or more messages 2401 can include configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can receive one or more reports 2402 from the gNB-CU based on a measurement value remaining outside the value range for the time interval.

[0311] FIG. 28 Example implementations of the present disclosure are illustrated.

[0312] In example implementations of the present disclosure, a gNB-DU can receive one or more messages 2501 from a gNB-CU. The one or more messages 2501 can include configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. The gNB-DU can transmit one or more reports 2502 to the gNB-CU based on a measurement value remaining outside the value range for the time interval.

[0313] In example implementations of the present disclosure, a gNB-CU can transmit one or more messages 2501 to one or more gNB-DUs. The one or more messages 2501 can include configuration parameters for an event. The configuration parameters for the event can include a time interval and a value range. The gNB-CU can receive one or more reports 2502 from the one or more gNB-DUs based on a measurement value remaining outside the value range for the time interval.

[0314] FIG. 29 Example embodiments of the present disclosure are illustrated.

[0315] In example embodiments of the present disclosure, a gNB-CU-CP can receive one or more messages 2601 from a gNB-CU-UP. The one or more messages 2601 can include configuration parameters for an event. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-CP can transmit one or more reports 2602 to the gNB-CU-UP based on a measurement value remaining outside the value range for the time interval.

[0316] In example embodiments of the present disclosure, a gNB-CU-UP can transmit one or more messages 2601 to a gNB-CU-CP. The one or more messages 2601 can include configuration parameters for an event. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-UP can receive one or more reports 2602 from the gNB-CU-CP based on a measurement value remaining outside the value range for the time interval.

[0317] FIG. 30 Example embodiments of the present disclosure are illustrated.

[0318] In example embodiments of the present disclosure, a gNB-CU-UP can receive one or more messages 2701 from a gNB-CU-CP. The one or more messages 2701 can include configuration parameters for an event. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-UP can transmit one or more reports 2702 to the gNB-CU-CP based on a measurement value remaining outside the value range for the time interval.

[0319] In example embodiments of the present disclosure, a gNB-CU-CP can transmit one or more messages 2701 to a gNB-CU-UP. The one or more messages 2701 can include configuration parameters for an event. The configuration parameters for an event can include a time interval and a value range. The gNB-CU-CP can receive one or more reports 2702 from the gNB-CU-UP based on a measurement value remaining outside the value range for the time interval.

[0320] In example embodiments of the present disclosure, the configuration parameters for one or more reports can further include a value identifier.

[0321] In example embodiments of the present disclosure, the value identifier can comprise one or more identifiers (e.g., integers or names) that identify one or more values. For example, value 10 or value 22 can identify a load. For example, value 13 or value 52 can identify an energy consumption. For example, name “load” can identify a load. For example, name “energy consumption” can identify an energy consumption. The value identifier can be indicated as a string, a bitmap, or any other desired manner.

[0322] In example embodiments of the present disclosure, the value identifier can comprise one or more bitmaps, where a value in each position identifies whether a particular value should be determined (e.g., 1 or true if it should be determined, and 0 or false if it should not be determined). For example, “1” in position 1 or position 3 can identify a load. For example, “1” in position 2 or position 11 can identify an energy consumption.

[0323] In example embodiments of the present disclosure, the time interval can comprise one or more time points. The time point can comprise an absolute time as measured by International Atomic Time (TAI). The time point can be equal to, for example, 2023-02-08 T04:23:13 and / or 2023-03-09 T11:33:33. The time point can comprise a time offset between an absolute time reference and an absolute time as measured by the TAI. The absolute time reference can be chosen to be equal to, for example, 1980-01-06 T00:00:19 as measured by the TAI. The offset can be equal to, for example, 0043-00-00 T00:00:00 and / or 0043-01-00 T09:24:10.

[0324] In example embodiments of the present disclosure, the time interval can comprise a duration. The duration can be equal to, for example, 100 milliseconds (ms) and / or 1.2 seconds (s).

[0325] In example embodiments of the present disclosure, the time interval can comprise a start time and an end time. The start time and / or the end time can comprise an absolute time as measured by TAI. The start time and / or the end time can be equal to, for example, 2023-02-08 T04:23:13 and / or 2023-03-09 T11:33:33. The start time and / or the end time can comprise a time offset between an absolute time reference and an absolute time as measured by the TAI. The absolute time reference can be chosen to be equal to, for example, 1980-01-06 T00:00:19 as measured by the TAI. The offset can be equal to, for example, 0043-00-00 T00:00:00 and / or 0043-01-00 T09:24:10.

[0326] In example embodiments of the present disclosure, the time interval can comprise a start time and a duration. The start time can comprise an absolute time as measured by a TAI. The start time can be equal to, for example, 2023-02-08 T04:23:13 and / or 2023-03-09 T11 :33:33. The start time can comprise a time offset between an absolute time reference and an absolute time as measured by the TAI. The absolute time reference can be selected to be equal to, for example, 1980-01-06 T00:00:19 as measured by the TAI. The offset can be equal to, for example, 0043-00-00 T00:00:00 and / or 0043-01-00 T09:24:10. The duration can be equal to, for example, 100 milliseconds (ms) and / or 1.2 seconds (s).

[0327] In example embodiments of the present disclosure, the time interval can comprise a duration and an end time. The duration can be equal to, for example, 100 milliseconds (ms) and / or 1.2 seconds (s). The end time can comprise an absolute time as measured by a TAI. The end time can be equal to, for example, 2023-02-08 T04:23:13 and / or 2023-03-09 T11 :33:33. The end time can comprise a time offset between an absolute time reference and an absolute time as measured by the TAI. The absolute time reference can be selected to be equal to, for example, 1980-01-06 T00:00:19 as measured by the TAI. The offset can be equal to, for example, 0043-00-00 T00:00:00 and / or 0043-01-00 T09:24:10.

[0328] In example embodiments of the present disclosure, the value range can comprise values equal to one or more reference values. For example, the value range can be defined as three reference SINR values: 2 dB, 3 dB, and 4 dB. In this case, if a SINR measured at a UE is not equal to any of these values, the SINR is outside the value range. For example, a SINR measured at a UE can be equal to 5.5 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can be defined as two cell identifiers. In this case, if a cell identifier measured at a UE is not equal to any of the two cell identifiers, the cell identifier is outside the value range.

[0329] In example embodiments of the disclosure, the value range can include values that are not equal to one or more reference values. For example, the value range can be defined as all values that are not equal to three reference SINR values (2 dB, 3 dB, and 4 dB). In this case, if the SINR measured at the UE is equal to any of these values, the SINR is outside the value range. For example, the SINR measured at the UE can be equal to 2 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can be defined as all cell identifiers that are not equal to either of the two cell identifiers. In this case, if the cell identifier measured at the UE is equal to either of the two cell identifiers, the cell identifier is outside the value range.

[0330] In example embodiments of the disclosure, the value range can include values that are greater than and / or greater than or equal to a threshold value. For example, the value range can include SINR values that are greater than 10 dB. For example, the SINR measured at the UE can be equal to 5 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can include UE transmit power values that are greater than or equal to 10 dBm. For example, the UE transmit power measured at the UE can be equal to 5 dBm. In this case, the UE transmit power measured at the UE is outside the value range.

[0331] In example embodiments of the disclosure, the value range can include values that are less than and / or less than or equal to a threshold value. For example, the value range can include SINR values that are less than 10 dB. For example, the SINR measured at the UE can be equal to 15 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can include UE transmit power values that are less than or equal to 10 dBm. For example, the UE transmit power measured at the UE can be equal to 15 dBm. In this case, the UE transmit power measured at the UE is outside the value range.

[0332] In example embodiments of the disclosure, the value range can include values that are greater than and / or greater than or equal to a first threshold value or less than and / or less than or equal to a second threshold value. For example, the value range can include SINR values that are greater than 15 dB or less than or equal to 5 dB. For example, the SINR measured at the UE can be equal to 12 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can include UE transmit power values that are greater than or equal to 15 dBm or less than 10 dBm. For example, the UE transmit power measured at the UE can be equal to 14 dBm. In this case, the UE transmit power measured at the UE is outside the value range.

[0333] In example embodiments of the disclosure, the value range can include values that are greater than and / or greater than or equal to a first threshold and less than and / or less than or equal to a second threshold. For example, the value range can include SINR values that are greater than 5 dB and less than or equal to 10 dB. For example, the SINR measured at the UE can be equal to 15 dB. In this case, the SINR measured at the UE is outside the value range. For example, the value range can include UE transmit power values that are greater than or equal to 5 dBm and less than 10 dBm. For example, the UE transmit power measured at the UE can be equal to 15 dBm. In this case, the UE transmit power measured at the UE is outside the value range.

[0334] In example embodiments of the disclosure, the value range can include values that are within one or more location areas. The location area can include one or more reference locations. In this case, the UE location is outside the location area if the UE location measured at the UE is different from at least one reference location. The value range can include values that are outside one or more location areas. The location area can include one or more reference locations. In this case, the UE location is outside the location area if the UE location measured at the UE is the same as at least one reference location.

[0335] In example embodiments of the disclosure, the value range can include values that are within one or more location areas. The location area can include an area bounded by one or more reference locations. In this case, the UE location is outside the location area if the UE location measured at the UE is outside the area bounded by the one or more reference locations. The value range can include values that are outside one or more location areas. The location area can include an area bounded by one or more reference locations. In this case, the UE location is outside the location area if the UE location measured at the UE is within the area bounded by the one or more reference locations.

[0336] In example embodiments of the disclosure, the value range can include values that are within one or more location areas. The location area can include an area bounded by a reference location and a distance from the reference location. In this case, the UE location is outside the location area if the UE location measured at the UE is outside the area bounded by the reference location and the distance from the reference location. The value range can include values that are outside one or more location areas. The location area can include an area bounded by a reference location and a distance from the reference location. In this case, the UE location is outside the location area if the UE location measured at the UE is within the area bounded by the reference location and the distance from the reference location.

[0337] In example embodiments of the disclosure, the value range can include values within one or more location areas. The location area can include a registration area. In this case, the UE location is outside the location area if the UE location measured at the UE is outside the registration area. The value range can include values outside one or more location areas. The location area can include a registration area. In this case, the UE location is outside the location area if the UE location measured at the UE is inside the registration area.

[0338] In example embodiments of the disclosure, the value range can include values within one or more location areas. The location area can include a tracking area. In this case, the UE location is outside the location area if the UE location measured at the UE is outside the tracking area. The value range can include values outside one or more location areas. The location area can include a tracking area. In this case, the UE location is outside the location area if the UE location measured at the UE is inside the tracking area.

[0339] In example embodiments of the disclosure, the value range can include values within one or more location areas. The location area can include a coverage area. In this case, the UE location is outside the location area if the UE location measured at the UE is outside the coverage area. The value range can include values outside one or more location areas. The location area can include a coverage area. In this case, the UE location is outside the location area if the UE location measured at the UE is inside the coverage area. The location area can include a cell coverage area. The location area can include a beam coverage area.

[0340] In example embodiments of the disclosure, the one or more location areas can include one or more reference locations. The one or more location areas can include one or more areas bounded by one or more reference locations. The one or more location areas can include one or more areas bounded by one or more reference locations and one or more distances from the reference location. The one or more location areas can include one or more registration areas. The one or more location areas can include one or more tracking areas. The one or more location areas can include one or more coverage areas. The one or more location areas can include one or more cell coverage areas. The one or more location areas can include one or more beam coverage areas. The one or more location areas can include one or more cell identifiers. The one or more location areas can include one or more beam identifiers.

[0341] In example embodiments of the present disclosure, the measurement values can comprise one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices. The measurement values can comprise one or more averages of one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices. The measurement values can comprise one or more values determined based on one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices.

[0342] In example embodiments of the present disclosure, the measurements can include one or more signal metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurements can include one or more location metrics of one or more wireless devices. The measurements can include one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurements can include one or more QoS metrics of one or more wireless devices. The measurements can include one or more QoE metrics of one or more wireless devices. The measurements can include one or more channel usage metrics of one or more sidelink channels for one or more wireless devices. The measurements can include one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurements can include one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The measurements can include one or more cell identifiers of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs. The measurements can include one or more beam identifiers of one or more beams of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs.

[0343] In example embodiments of the present disclosure, the one or more signal metrics can include a signal level (e.g., RSRP). The value of RSRP can equal, for example, -62 decibel-milliwatts (dBm). The value of RSRP can equal, for example, -83 dBm. The one or more signal metrics can include a signal quality (e.g., RSRQ). The value of RSRQ can equal, for example, -10 decibels (dB). The value of RSRQ can equal, for example, 15 dB. The one or more signal metrics can include a SINR measurement. The value of SINR can equal, for example, -3 dB. The value of SINR can equal, for example, 27 dB. The one or more signal metrics can include interference. The value of interference can equal, for example, -93 dBm. The value of interference can equal, for example, -105 dBm.

[0344] In example embodiments of the present disclosure, the one or more location metrics can include one or more locations. The one or more location metrics can include one or more coordinates. The coordinates of the UE can equal, for example, (38.948159, -77.333221), where 38.948159 is the latitude and -77.333221 is the longitude. The coordinates of the UE can equal, for example, (38.928327, -77.366305). The one or more location metrics can include one or more registration areas. The one or more location metrics can include one or more tracking areas. The one or more location metrics can include one or more coverage areas. The one or more location metrics can include one or more cell coverage areas. The one or more location metrics can include one or more beam coverage areas. The one or more location metrics can include one or more cell identifiers. The one or more location metrics can include one or more beam identifiers. Two-dimensional Cartesian coordinates are used as an example, but polar coordinates (e.g., center coordinates and radius) or volumetric coordinates (e.g., latitude, longitude, and altitude) can be used.

[0345] In example embodiments of the present disclosure, the one or more energy consumption metrics can include an amount of energy consumed over a period of time. The energy consumption of the UE can equal, for example, 0.1 watt-hours (Wh). The energy consumption of the UE can equal, for example, 0.07 Wh. The one or more energy consumption metrics can include a percentage of energy consumed over a period of time. The one or more energy consumption metrics can include energy efficiency. The energy efficiency of the UE can equal, for example, 1.1 megabits per joule (Mb / J). The energy efficiency of the UE can equal, for example, 2.3 Mb / J. The one or more energy consumption metrics can include a percentage of energy efficiency. The one or more energy consumption metrics can include power consumption. The power consumption of the UE can equal, for example, 10 dBm. The power consumption of the UE can equal, for example, 5 dBm. The one or more energy consumption metrics can include a percentage of power consumption. The one or more energy consumption metrics can include an amount of energy consumed and an amount of data transmitted and / or received using the energy.

[0346] In example embodiments of the disclosure, the one or more QoS and QoE metrics can include throughput. The throughput can equal, for example, 1 megabit per second (Mb / s). The throughput can equal, for example, 5.2 Mb / s. The one or more QoS metrics and QoE metrics can include latency. The latency can equal, for example, 3 milliseconds (ms). The latency can equal, for example, 124 ms. The one or more QoS metrics and QoE metrics can include delay. The delay can equal, for example, 3 ms. The delay can equal, for example, 124 ms. The one or more QoS metrics and QoE metrics can include loss rate. The loss rate measurement can equal, for example, 0.000001. The loss rate measurement can equal, for example, 0.000891.

[0347] In example embodiments of the disclosure, the load metric can include a radio resource status. The load metric can include a physical resource block (PRB) usage. The load metric can include a scheduled physical downlink control channel (PDCCH) control channel element (CCE) usage. The load metric can include a PRB usage for multiple input multiple output (MIMO) transmission. The load metric can include a transport network layer (TNL) capacity indicator. The load metric can include a capacity provided by the TNL. The load metric can include an available capacity of the TNL. The load metric can include a composite available capacity group. The load metric can include a capacity class value. The load metric can include a capacity value. The load metric can include a slice available capacity. The load metric can include a number of active user equipment (UEs). The load metric can include a number of RRC connections. The load metric can include an available RRC connection capacity value. The load metric can include a channel occupancy time percentage. The load metric can include a quality of experience (QoE). The load metric can include a quality of service (QoS). The load metric can include a number of stored inactive UE contexts. The load metric can include a traffic of the UE. The load metric can include a transmit power. The load metric can include a transmit power per PRB. The load metric can include a hardware capacity indicator. The load metric can include a hardware load indicator. The load metric can include an almost blank subframe status. The load metric can include a buffer status, such as a downlink buffer status. The load metric can include a bandwidth occupancy. The load metric can include a percentage or number of active remote radio heads (RRHs) or distributed units (DUs). The load metric can include a base station power consumption level.

[0348] In example embodiments of the disclosure, the load metric can be determined per PLMN. The load metric can be determined per BS. The load metric can be determined per gNB-CU. The load metric can be determined per gNB-DU. The load metric can be determined per gNB-CU-CP. The load metric can be determined per gNB-CU-UP. The load metric can be determined per UE. The load metric can be determined per cell. The load metric can be determined per beam. The load metric can be determined per coverage area. The load metric can be determined per portion of coverage area. The load metric can be determined per downlink (DL). The load metric can be determined per uplink (UL). The load metric can be determined per supplemental uplink (SUL). The load metric can be determined per guaranteed bit rate (GBR) traffic. The load metric can be determined per non-guaranteed bit rate (non-GBR) traffic. The load metric can be determined per total traffic. The load metric can be determined per synchronization signal block (SSB) area. The load metric can be determined per slice. The load metric can be determined per radio bearer. The load metric can be determined per 5G QoS indicator. The load metric can be determined per QoS class indicator.

[0349] In example embodiments of the disclosure, the one or more channel usage metrics can include a channel busy ratio. The channel busy ratio measurement can be equal to, for example, 20%. The channel busy ratio measurement can be equal to, for example, 60%. The one or more channel usage metrics can include a channel occupancy ratio. The channel occupancy ratio measurement can be equal to, for example, 10%. The channel occupancy ratio measurement can be equal to, for example, 20%.

[0350] In example embodiments of the disclosure, the one or more traffic metrics can be determined per one or more DLs. The one or more traffic metrics can be determined per UL. The one or more traffic metrics can be determined per SUL. The one or more traffic metrics can be determined per one or more slices. The one or more traffic metrics can be determined per one or more 5G QoS indicators. The one or more traffic metrics can be determined per one or more QoS class indicators. The one or more traffic metrics can be determined per one or more base stations. The one or more traffic metrics can be determined per gNB-CU. The one or more traffic metrics can be determined per gNB-DU. The one or more traffic metrics can be determined per gNB-CU-CP. The one or more traffic metrics can be determined per gNB-CU-UP. The one or more traffic metrics can be determined per one or more cells. The one or more traffic metrics can be determined per one or more beams. The traffic measurement can be equal to, for example, 10 Mb / s. The traffic measurement can be equal to, for example, 5 Mb / s.

[0351] In example embodiments of the disclosure, the one or more cell identifiers can include a serving cell identifier of the UE. The one or more cell identifiers can include a neighboring cell identifier of the UE. The one or more cell identifiers can include a candidate target cell identifier of the UE.

[0352] FIG. 31 Example embodiments of the disclosure are illustrated.

[0353] In example embodiments of the disclosure, BS1 can receive one or more messages 2801 from BS2. The one or more messages 2801 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. BS1 can determine that the event has occurred based on a measurement value remaining outside of the value range for the time interval. BS1 can transmit the requested information 2802 to BS2 based on determining that the event has occurred.

[0354] FIG. 32 Example embodiments of the disclosure are illustrated.

[0355] In example embodiments of the disclosure, BS2 can transmit one or more messages 2901 to BS1. The one or more messages 2901 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. BS2 can receive the requested information 2902 from BS1 based on a measurement value remaining outside of the value range for the time interval.

[0356] FIG. 33 Example embodiments of the disclosure are illustrated.

[0357] In example embodiments of the disclosure, a gNB-CU can receive one or more messages 3001 from a gNB-DU. The one or more messages 3001 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU can determine that the event has occurred based on a measurement value remaining outside of the value range for the time interval. The gNB-CU can transmit the requested information 3002 to the gNB-DU based on determining that the event has occurred.

[0358] FIG. 34 Example embodiments of the disclosure are illustrated.

[0359] In an example embodiment of the disclosure, a gNB-DU can transmit one or more messages 3101 to a gNB-CU. The one or more messages 3101 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-DU can receive the requested information 3102 from the gNB-CU based on a measurement value remaining outside of the value range for the time interval.

[0360] FIG. 35 An example embodiment of the disclosure is illustrated.

[0361] In an example embodiment of the disclosure, a gNB-DU can receive one or more messages 3201 from a gNB-CU. The one or more messages 3201 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-DU can determine that the event has occurred based on a measurement value remaining outside of the value range for the time interval. The gNB-DU can transmit the requested information 3202 to the gNB-CU based on determining that the event has occurred.

[0362] FIG. 36 An example embodiment of the disclosure is illustrated.

[0363] In an example embodiment of the disclosure, a gNB-CU can transmit one or more messages 3301 to a gNB-DU. The one or more messages 3301 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU can receive the requested information 3302 from the gNB-DU based on a measurement value remaining outside of the value range for the time interval.

[0364] FIG. 37 An example embodiment of the disclosure is illustrated.

[0365] In an example embodiment of the disclosure, a gNB-CU-CP can receive one or more messages 3401 from a gNB-CU-UP. The one or more messages 3401 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU-CP can determine that the event has occurred based on a measurement value remaining outside of the value range for the time interval. The gNB-CU-CP can transmit the requested information 3402 to the gNB-CU-UP based on determining that the event has occurred.

[0366] FIG. 38 An example embodiment of the disclosure is illustrated.

[0367] In example embodiments of the disclosure, a gNB-CU-UP can transmit one or more messages 3501 to a gNB-CU-CP. The one or more messages 3501 can include a configuration parameter for an event and a configuration for requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU-UP can receive the requested information 3502 from the gNB-CU-CP based on a measured value remaining outside the value range for the time interval.

[0368] FIG. 39 Example embodiments of the disclosure are illustrated.

[0369] In example embodiments of the disclosure, a gNB-CU-UP can receive one or more messages 3601 from a gNB-CU-CP. The one or more messages 3601 can include a configuration parameter for an event and a configuration for requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU-UP can determine that the event has occurred based on a measured value remaining outside the value range for the time interval. The gNB-CU-UP can transmit the requested information 3602 to the gNB-CU-CP based on determining that the event has occurred.

[0370] FIG. 40 Example embodiments of the disclosure are illustrated.

[0371] In example embodiments of the disclosure, a gNB-CU-CP can transmit one or more messages 3701 to a gNB-CU-UP. The one or more messages 3501 can include a configuration parameter for an event and a configuration for requested information for the event. The configuration parameter for the event can include a time interval and a value range. The gNB-CU-CP can receive the requested information 3702 from the gNB-CU-UP based on a measured value remaining outside the value range for the time interval.

[0372] In example embodiments of the disclosure, the requested information can include one or more signal metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more location metrics of one or more wireless devices. The requested information can include one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more QoS metrics of one or more wireless devices. The requested information can include one or more QoE metrics of one or more wireless devices. The requested information can include one or more channel usage metrics of one or more sidelink channels for one or more wireless devices. The requested information can include one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested information can include one or more cell identifiers of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs. The requested information can include one or more beam identifiers of one or more beams of one or more cells of one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs.

[0373] In example embodiments of the disclosure, the configuration of the requested information can include one or more identifiers of the requested information.

[0374] In example embodiments of the disclosure, the identifier of the requested information can include one or more identifiers (e.g., integers or names) that identify the requested information. The identifier of the requested information can include one or more bitmaps, where a value in each position identifies the requested information (e.g., 1 or true if the information is requested, and 0 or false if the information is not requested).

[0375] In example embodiments of the disclosure, the configuration of the requested information can include one or more frequency identifiers. The configuration of the requested information can include a number of frequencies. The configuration of the requested information can include one or more RAT identifiers. The configuration of the requested information can include a number of RATs. The configuration of the requested information can include one or more identifiers of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or cells and / or beams and / or wireless devices. The configuration of the requested information can include a number of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or wireless devices. The configuration of the requested information can include DL and / or UL and / or sidelink. The configuration of the requested information can include a number of requested values of the requested reporting information. The configuration of the requested information can include a time interval between values of the requested reporting information.

[0376] In example embodiments of the disclosure, the frequency identifier can include a channel number. The frequency identifier can include a center frequency and a bandwidth. The frequency identifier can include a start frequency and an end frequency.

[0377] In example embodiments of the disclosure, the RAT identifier can include 3GPP access and / or non-3GPP access. The RAT identifier can include 3G and / or 4G and / or 5G. The RAT identifier can include LTE and / or LTE-Advanced and / or NR.

[0378] FIG. 41 Example embodiments of the disclosure are illustrated.

[0379] In example embodiments of the disclosure, BS2 can determine a prediction. BS2 can transmit one or more messages 3801 to BS1. The one or more messages 3801 can include a configuration parameter for an event associated with the prediction, and a configuration of requested information for the event associated with the prediction. The configuration parameter for the event can include a time interval and a value range. BS2 can receive the requested information from BS1 based on a measured value remaining outside the value range for the time interval. BS2 can determine a new prediction based at least in part on the requested information received from BS1.

[0380] In example embodiments of the disclosure, the prediction can comprise, for example, a signal level prediction. The configuration parameter for the event can be associated with the prediction, e.g., the value range can be a signal level value range. The configuration of the requested information for the event can be associated with the prediction, e.g., the requested information can comprise one or more signal level measurements. The new prediction can comprise, for example, a new signal level prediction determined based on the requested information (one or more signal level measurements).

[0381] In example embodiments of the disclosure, the prediction can comprise, for example, a load metric prediction. The configuration parameter for the event can be associated with the prediction, e.g., the value range can be a load metric value range. The configuration of the requested information for the event can be associated with the prediction, e.g., the requested information can comprise one or more load metric measurements. The new prediction can comprise, for example, a new load metric prediction determined based on the requested information (one or more load metric measurements).

[0382] FIG. 42 Example embodiments of the disclosure are illustrated.

[0383] In example embodiments of the disclosure, BS1 can receive one or more messages 3901 from BS2. The one or more messages 3901 can comprise a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can comprise a time interval and one or more location areas. BS1 can determine that the event occurred based on a measured location metric of the wireless device remaining outside of the one or more location areas for the time interval. BS1 can transmit the requested information 3902 to BS2 based on determining that the event occurred.

[0384] In example embodiments of the disclosure, the requested information can comprise one or more signal metrics of the wireless device and / or one or more cells and / or one or more beams. The requested information can comprise one or more location metrics of the wireless device. The requested information can comprise one or more cell identifiers of one or more cells of one or more base stations. The requested information can comprise one or more beam identifiers of one or more beams of one or more cells of one or more base stations.

[0385] FIG. 43 Example embodiments of the disclosure are illustrated.

[0386] In example embodiments of the disclosure, BS1 can receive one or more messages 4001 from BS2. The one or more messages 4001 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a traffic metric value range. BS1 can determine that the event has occurred based on a measured traffic metric value remaining outside of the traffic metric value range for the time interval. BS1 can transmit the requested information 4002 to BS2 based on determining that the event has occurred.

[0387] FIG. 44 Example embodiments of the disclosure are illustrated.

[0388] In example embodiments of the disclosure, gNB-CU-UP can receive one or more messages 4101 from gNB-CU-CP. The one or more messages 4101 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a traffic metric value range. gNB-CU-UP can determine that the event has occurred based on a measured traffic metric value remaining outside of the traffic metric value range for the time interval. The gNB-CU-UP can transmit the requested information 4102 to the gNB-CU-CP based on determining that the event has occurred.

[0389] In example embodiments of the disclosure, the requested information can include one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-UP and / or one or more cells and / or one or more beams. The requested information can include one or more QoS metrics of one or more wireless devices. The requested information can include one or more QoE metrics of one or more wireless devices. The requested information can include one or more load metrics of one or more wireless devices and / or one or more base stations and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-UP and / or one or more cells and / or one or more beams. The requested information can include one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-UP and / or one or more cells and / or one or more beams.

[0390] FIG. 45 Example embodiments of the disclosure are illustrated.

[0391] In example implementations of the disclosure, BS1 can receive one or more messages 4201 from BS2. The one or more messages 4201 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and an energy consumption metric value range. BS1 can determine that the event occurred based on a measured energy consumption metric value remaining outside of the energy consumption metric value range for the time interval. BS1 can transmit the requested information 4202 to BS2 based on determining that the event occurred.

[0392] In example implementations of the disclosure, the requested information can include one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more cells and / or one or more beams. The requested information can include one or more QoS metrics of one or more wireless devices. The requested information can include one or more QoE metrics of one or more wireless devices. The requested information can include one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more cells and / or one or more beams. The requested information can include one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more cells and / or one or more beams.

[0393] ​ Example implementations of the disclosure are illustrated.

[0394] In example implementations of the disclosure, BS1 can receive one or more messages 4301 from BS2. The one or more messages 4301 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a signal metric value range. BS1 can determine that the event occurred based on a measured signal metric value remaining outside of the signal metric value range for the time interval. BS1 can transmit the requested information 4302 to BS2 based on determining that the event occurred.

[0395] In example implementations of the disclosure, the requested information can include one or more signal metrics of one or more wireless devices and / or one or more cells and / or one or more beams. The requested information can include one or more location metrics of one or more wireless devices. The requested information can include one or more cell identifiers of one or more cells of one or more base stations. The requested information can include one or more beam identifiers of one or more beams of one or more cells of one or more base stations.

[0396] ​ Example implementations of the disclosure are illustrated.

[0397] In example implementations of the disclosure, BS1 can receive one or more messages 4401 from BS2. The one or more messages 4401 can include a configuration parameter for an event and a configuration of requested information for the event. The configuration parameter for the event can include a time interval and a range of load metric values. BS1 can determine that the event occurred based on a measured load metric value remaining outside of the range of load metric values for the time interval. BS1 can transmit the requested information 4402 to BS2 based on determining that the event occurred.

[0398] In example implementations of the disclosure, the requested reporting information can include one or more energy consumption metrics for one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested reporting information can include one or more channel usage metrics for one or more sidelink channels for one or more wireless devices. The requested reporting information can include one or more load metrics for one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams. The requested reporting information can include one or more traffic metrics for one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams.

[0399] In example implementations of the disclosure, the configuration parameter for the event can further include an event identifier.

[0400] In example implementations of the disclosure, the requested information can further include transmitting an event identifier.

[0401] In example implementations of the disclosure, the event identifier can include one or more identifiers (e.g., integers or names) that identify the event. The event identifier can include one or more bitmaps, where the value in each position identifies a particular event (e.g., 1 or true if related to the event, 0 or false if not related to the event).

[0402] ​ Example implementations of the disclosure are illustrated.

[0403] In example embodiments of the disclosure, a first base station (BS1) can receive configuration parameters for an event from a second base station (BS2), including a time interval and a value range. BS1 can also receive a configuration of requested information for the event from BS2. This can be received in the same message or in different messages. In some cases, the event can be initially configured and later modified by a second message. In this case, the second message can indicate changes relative to the first message.

[0404] In the illustrated example embodiment, BS1 can determine that the event occurred based on the measured value remaining outside of the value range for the time interval.

[0405] In this example, BS1 can transmit the requested information to BS2 based on determining that the event occurred. If the event did not occur, BS1 can not transmit any indication or can transmit an indication that the event did not occur. In the latter case, the indication that the event did not occur can not be accompanied by the requested information.

Claims

1. A method comprising: receiving, by a first base station from a second base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration for requested information for the event; determining, by the first base station, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the first base station to the second base station, the requested information based on determining that the event occurred.

2. A method comprising: receiving, by a first base station from a second base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and transmitting, by the first base station to the second base station, one or more reports based on a measured value remaining outside the value range for the time interval.

3. A method comprising: transmitting, by a second base station to a first base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and receiving, by the second base station from the first base station, one or more reports based on a measured value remaining outside the value range for the time interval.

4. A method comprising: receiving, by a gNB-CU from a gNB-DU: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and transmitting, by the gNB-CU to the gNB-DU, one or more reports based on a measured value remaining outside the value range for the time interval.

5. A method comprising: transmitting, by a gNB-DU to a gNB-CU: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and receiving, by the gNB-DU from the gNB-CU, one or more reports based on a measured value remaining outside the value range for the time interval.

6. A method comprising: receiving, by a gNB-DU from a gNB-CU: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and transmitting, by the gNB-DU to the gNB-CU, one or more reports based on a measured value remaining outside the value range for the time interval.

7. A method comprising: transmitting, by a gNB-CU to one or more gNB-DUs: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and receiving, by the gNB-CU from the one or more gNB-DUs, one or more reports based on a measured value remaining outside the value range for the time interval.

8. A method comprising: receiving, by a gNB-CU-CP from a gNB-CU-UP: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and transmitting, by the gNB-CU-CP to the gNB-CU-UP, one or more reports based on a measured value remaining outside the value range for the time interval.

9. A method comprising: transmitting, by a gNB-CU-UP to a gNB-CU-CP: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and receiving, by the gNB-CU-UP from the gNB-CU-CP, one or more reports based on a measured value remaining outside the value range for the time interval.

10. A method comprising: receiving, by a gNB-CU-UP from a gNB-CU-CP: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and transmitting, by the gNB-CU-UP to the gNB-CU-CP, one or more reports based on a measured value remaining outside the value range for the time interval.

11. A method comprising: transmitting, by a gNB-CU-CP to a gNB-CU-UP: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and receiving, by the gNB-CU-CP from the gNB-CU-UP, one or more reports based on a measured value remaining outside the value range for the time interval.

12. A method comprising: receiving, by a first base station from a second base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; determining, by the first base station, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the first base station to the second base station, the requested information based on determining that the event occurred.

13. A method comprising: transmitting, by a second base station to a first base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; receiving, by the second base station from the first base station, the requested information based on a measured value remaining outside the value range for the time interval.

14. A method comprising: receiving, by a gNB-CU from a gNB-DU: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; determining, by the gNB-CU, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the gNB-CU to the gNB-DU, the requested information based on determining that the event occurred.

15. A method comprising: transmitting, by a gNB-DU to a gNB-CU: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; receiving, by the gNB-DU from the gNB-CU, the requested information based on a measured value remaining outside the value range for the time interval.

16. A method comprising: receiving, by a gNB-DU from a gNB-CU, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; determining, by the gNB-DU, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the gNB-DU to the gNB-CU, the requested information based on determining that the event occurred.

17. A method comprising: transmitting, by a gNB-CU to one or more gNB-DUs, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; receiving, by the gNB-CU from the one or more gNB-DUs, the requested information based on a measured value remaining outside the value range for the time interval.

18. A method comprising: receiving, by a gNB-CU-CP from a gNB-CU-UP, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; determining, by the gNB-CU-CP, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the gNB-CU-CP to the gNB-CU-UP, the requested information based on determining that the event occurred.

19. A method comprising: transmitting, by a gNB-CU-UP to a gNB-CU-CP, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; receiving, by the gNB-CU-UP from the gNB-CU-CP, the requested information based on a measured value remaining outside the value range for the time interval.

20. A method comprising: receiving, by a gNB-CU-UP from a gNB-CU-CP, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; determining, by the gNB-CU-UP, that the event occurred based on a measured value remaining outside the value range for the time interval; and transmitting, by the gNB-CU-UP to the gNB-CU-CP, the requested information based on determining that the event occurred.

21. A method comprising: transmitting, by a gNB-CU-CP to a gNB-CU-UP, the following: configuration parameters for an event, the configuration parameters comprising: a time interval; and a value range; and a configuration of requested information for the event; receiving, by the gNB-CU-CP from the gNB-CU-UP, the requested information based on a measured value remaining outside the value range for the time interval.

22. A method comprising: determining, by a second base station, a prediction; transmitting, by the second base station to a first base station, the following: a configuration parameter for an event associated with the prediction, the configuration parameter comprising: a time interval; and a value range; and a configuration of requested information for the event associated with the prediction; receiving, by the second base station from the first base station, the requested information based on the measured value remaining outside the value range for the time interval; determining, by the second base station, a new prediction based at least in part on the requested information received from the first base station.

23. A method, the method comprising: receiving, by a first base station from a second base station, the following: a configuration parameter for an event, the configuration parameter comprising: a time interval; and one or more location areas; and a configuration of requested information for the event; determining, by the first base station, that the event occurred based on a measured location metric of a wireless device remaining outside the one or more location areas for the time interval; and transmitting, by the first base station to the second base station, the requested information based on determining that the event occurred.

24. A method, the method comprising: receiving, by a first base station from a second base station, the following: a configuration parameter for an event, the configuration parameter comprising: a time interval; and a traffic metric value range; and a configuration of requested information for the event; determining, by the first base station, that the event occurred based on a measured traffic metric value remaining outside the traffic metric value range for the time interval; and transmitting, by the first base station to the second base station, the requested information based on determining that the event occurred.

25. A method, the method comprising: receiving, by a gNB-CU-UP from a gNB-CU-CP, the following: a configuration parameter for an event, the configuration parameter comprising: a time interval; and a traffic metric value range; and a configuration of requested information for the event; determining, by the gNB-CU-UP, that the event occurred based on a measured traffic metric value remaining outside the traffic metric value range for the time interval; and transmitting, by the gNB-CU-UP to the gNB-CU-CP, the requested information based on determining that the event occurred.

26. A method, the method comprising: receiving, by a first base station from a second base station, the following: a configuration parameter for an event, the configuration parameter comprising: a time interval; and an energy consumption metric value range; and a configuration of requested information for the event; determining, by the first base station, that the event occurred based on a measured energy consumption metric value remaining outside the energy consumption metric value range for the time interval; and transmitting, by the first base station to the second base station, the requested information based on determining that the event occurred.

27. A method, the method comprising: receiving, by a first base station from a second base station, the following: a configuration parameter for an event, the configuration parameter comprising: a time interval; and a signal metric value range; and a configuration of requested information for the event; determining, by the first base station, that the event occurred based on a measured signal metric value remaining outside of the signal metric value range for the time interval; and transmitting, by the first base station, the requested information to the second base station based on determining that the event occurred.

28. A method comprising: receiving, by a first base station from a second base station: configuration parameters for an event, the configuration parameters comprising: a time interval; and a load metric value range; and a configuration for requested information for the event; determining, by the first base station, that the event occurred based on a measured load metric value remaining outside of the load metric value range for the time interval; and transmitting, by the first base station, the requested information to the second base station based on determining that the event occurred.

29. The method of any of claims 1-28, wherein the time interval comprises at least one of: one or more time points; a duration; a time window; a timer value; a start time and an end time; a start time and a duration; or a duration and an end time.

30. The method of any of claims 1-22 or 29, wherein the measured value remains outside of the value range for an entire duration of the time interval.

31. The method of any of claims 1-30, wherein the configuration parameters comprise a value identifier.

32. The method of claim 31, wherein the value identifier comprises at least one of: one or more identifiers that identify one or more values; or one or more bitmaps, wherein a value in each position identifies whether a particular value should be determined.

33. The method of any of claims 1-32, wherein the configuration parameters for the event further comprise an event identifier.

34. The method of claim 33, wherein the event identifier comprises one or more of: one or more identifiers that identify the event, or one or more bitmaps, wherein a value in each position of the bitmap identifies a particular event.

35. The method of claim 33 or 34, wherein the transmitting the requested information or the transmitting the one or more reports further comprises: transmitting the event identifier.

36. The method of any of claims 1-22 or 29-35, wherein the value range comprises at least one of: values equal to one or more reference values; values not equal to one or more reference values; values greater than and / or greater than or equal to a threshold value; values less than and / or less than or equal to a threshold value; values greater than and / or greater than or equal to a first threshold value or less than and / or less than or equal to a second threshold value; values within one or more location areas; or values outside of one or more location areas.

37. The method of any of claims 23 or 29-36, wherein the one or more location areas comprise: one or more reference locations, and / or one or more areas bounded by one or more reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one or more areas bounded by one or more reference locations and one or more distances from the reference locations, and / or one one or more registration areas, and / or one or more tracking areas, and / or one or more coverage areas, and / or one or more cell coverage areas, and / or one or more beam coverage areas, and / or one or more cell identifiers, and / or one or more beam identifiers.

38. The method of any one of claims 1 to 22 or 29 to 37, wherein the measurement values comprise: one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices; and / or one or more averages of one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices; and / or one or more values determined based on one or more measurements determined at the base station and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-CP and / or one or more wireless devices.

39. The method of any one of claims 1 to 22 or 29 to 38, wherein the measurement values comprise: one or more signal metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams, and / or one or more location metrics of one or more wireless devices, and / or one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams, and / or one or more QoS metrics of one or more wireless devices, and / or one or more QoE metrics of one or more wireless devices, and / or one or more channel usage metrics for one or more sidelink channels of one or more wireless devices, and / or one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams, and / or one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams, and / or one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams, and / or one or more cell identifiers of one or more cells of the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs, and / or one or more beam identifiers of one or more beams of one or more cells of the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs.

40. The method of any one of claims 1 or 12-39, wherein the requested information comprises at least one of: one or more signal metrics of the one or more wireless devices and / or the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs and / or the one or more cells and / or the one or more beams; one or more location metrics of the one or more wireless devices; one or more energy consumption metrics of the one or more wireless devices and / or the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs and / or the one or more cells and / or the one or more beams; one or more QoS metrics of the one or more wireless devices; one or more QoE metrics of the one or more wireless devices; one or more channel usage metrics for one or more sidelink channels of the one or more wireless devices; one or more load metrics of the one or more wireless devices and / or the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs and / or the one or more cells and / or the one or more beams; one or more traffic metrics of the one or more wireless devices and / or the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs and / or the one or more cells and / or the one or more beams; one or more cell identifiers of one or more cells of the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs; or one or more beam identifiers of one or more beams of one or more cells of the one or more base stations and / or the one or more gNB-CUs and / or the one or more gNB-DUs and / or the one or more gNB-CU-CPs and / or the one or more gNB-CU-UPs.

41. The method of any one of claims 1 or 12-40, wherein the requested information comprises at least one of: one or more energy consumption metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams; one or more channel usage metrics for one or more sidelink channels of one or more wireless devices, and / or one or more QoS metrics of one or more wireless devices; one or more QoE metrics of one or more wireless devices; one or more load metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams; or one or more traffic metrics of one or more wireless devices and / or one or more base stations and / or one or more gNB-CUs and / or one or more gNB-DUs and / or one or more gNB-CU-CPs and / or one or more gNB-CU-UPs and / or one or more cells and / or one or more beams.

42. The method of any one of claims 1 or 12-41, wherein the configuration of the requested information comprises one or more identifiers of the requested information.

43. The method of claim 42, wherein the one or more identifiers of the requested information comprise: one or more identifiers that identify the requested information; and / or one or more bitmaps, wherein a value in each position identifies the requested information.

44. The method of any one of claims 1 or 12-43, wherein the configuration of the requested information comprises: one or more frequency identifiers, and / or a number of frequencies, and / or one or more RAT identifiers, and / or a number of RATs, and / or one or more identifiers of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or cells and / or beams and / or wireless devices, and / or a number of base stations and / or gNB-CUs and / or gNB-DUs and / or gNB-CU-CPs and / or gNB-CU-UPs and / or wireless devices, and / or DL and / or UL and / or sidelink, and / or a number of requested values of the requested information, and / or a time interval between the values of the requested information.

45. The method of any one of claims 39-44, wherein the one or more signal metrics comprise: a signal level (RSRP), and / or a signal quality (RSRQ), and / or a SINR measurement, and / or interference.

46. The method of any one of claims 23 or 29-45, wherein the one or more location metrics comprise: one or more locations, and / or one or more coordinates, and / or one or more registration areas, and / or one or more tracking areas, and / or one or more coverage areas, and / or one or more cell coverage areas, and / or one or more beam coverage areas, and / or one or more cell identifiers, and / or one or more beam identifiers.

47. The method of any one of claims 26 or 29-46, wherein the one or more energy consumption metrics comprise: an amount of energy consumed over a period of time, and / or a percentage of energy consumed over a period of time, and / or an energy efficiency, and / or a percentage of energy efficiency, and / or a power consumption, and / or a percentage of power consumption. an amount of data transmitted and / or received using the energy.

48. The method of any one of claims 39-47, wherein the one or more QoS metrics and / or QoE metrics comprise: a throughput, and / or a latency, and / or a delay, and / or a loss rate.

49. The method of any one of claims 39-48, wherein the load metric comprises at least one of: a radio resource status; a physical resource block (PRB) usage; a scheduled physical downlink control channel (PDCCH) control channel element (CCE) usage; a PRB usage for multiple input multiple output (MIMO) transmission; a transport network layer (TNL) capacity indicator; a TNL provided capacity; a TNL available capacity; a composite available capacity group; a capacity class value; a capacity value; a slice available capacity; a number of active user equipment (UEs); a number of RRC connections; an available RRC connection capacity value; a channel occupancy time percentage; a quality of experience (QoE); a quality of service (QoS); a number of stored inactive UE contexts; a UE’s traffic; a transmit power; a transmit power per PRB; a hardware capacity indicator; a hardware load indicator; or an almost blank subframe status.

50. The method of any one of claims 39-49, wherein the load metric is determined per PLMN and / or per BS and / or per UE and / or per cell and / or per beam and / or per coverage area and / or per a portion of a coverage area and / or per downlink (DL) and / or per uplink (UL) and / or per supplementary uplink (SUL) and / or per guaranteed bit rate (GBR) traffic and / or per non-GBR traffic and / or per total traffic and / or per synchronization signal block (SSB) area and / or per slice and / or per radio bearer and / or per 5G QoS indicator and / or per QoS class indicator.

51. The method of any one of claims 39-50, wherein the one or more channel usage metrics comprise: a channel busy ratio, and / or a channel occupancy ratio.

52. The method of any one of claims 39-51, wherein the one or more traffic metrics are determined per: one or more downlink and / or uplink and / or supplemental uplink, and / or one or more slices, and / or one or more 5G QoS indicators, and / or one or more QoS class indicators, and / or one or more base stations and / or gNB-CU and / or gNB-DU and / or gNB-CU-CP and / or gNB-CU-UP, and / or one or more cells, and / or one or more beams.

53. The method of any one of claims 37-52, wherein the one or more cell identifiers comprise at least one of: a serving cell identifier of the wireless device; an adjacent cell identifier of the wireless device; or a candidate target cell identifier of the wireless device.

54. The method of any one of claims 44-53, wherein the one or more frequency identifiers comprise: a channel number, and / or a center frequency and a bandwidth, and / or a start frequency and an end frequency.

55. The method of any one of claims 44-54, wherein the one or more RAT identifiers comprise at least one of: 3GPP access and / or non-3GPP access; 3G and / or 4G and / or 5G; or LTE and / or LTE-Advanced and / or NR.

56. An apparatus, comprising one or more processors and memory storing instructions for execution by the one or more processors to cause the apparatus to at least perform the method of any one of claims 1-55.

57. A non-transitory computer-readable medium comprising instructions to cause a device, upon execution of the instructions by one or more processors of the device, to perform the method of any one of claims 1-55.

58. An apparatus, comprising means for performing the method of any one of claims 1-55.

Images