Interruption Capability for Life Cycle Management

Abstract

A method comprises transmitting, by a wireless device to a node, a capability message indicating a time duration associated with an interruption of communications with a base station. The interruption is based on a life cycle management (LCM) procedure.

Description

TITLEInterruption Capability for Life Cycle ManagementCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 675,783, filed July 26,2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0003] FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

[0005] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

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

[0007] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

[0008] FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

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

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

[0011] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

[0012] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

[0014] FIG. 10B illustrates an example of how aggregated cells may be configured into one or morePUCCH groups.

[0015] FIG. 11A illustrates an example of an SS / PBCH block structure and location.

[0016] FIG. 11 B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

[0018] FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

[0019] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.

[0020] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base station.

[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

[0023] FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure.

[0024] FIG. 18 illustrates an aspect of an example embodiment according to the present disclosure.

[0025] FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure

[0026] FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.

[0027] FIG. 21 illustrates an aspect of an example embodiment according to the present disclosure.

[0028] FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.

[0029] FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure.

[0030] FIGS. 24A and 24B illustrate aspects of an example embodiment according to the present disclosure.

[0031] FIG. 25 illustrates an aspect of an example embodiment according to the present disclosure.

[0032] FIG. 26 illustrates an aspect of an example embodiment according to the present disclosure.

[0033] FIG. 27 illustrates an aspect of an example embodiment according to the present disclosure

[0034] FIG. 28 illustrates an aspect of an example embodiment according to the present disclosure.

[0035] FIG. 29 illustrates an aspect of an example embodiment according to the present disclosure.

[0036] FIG. 30 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

[0037] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality andadvantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0038] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0039] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0040] In this disclosure, "a” and “an" and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of', as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes" and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0041] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH , cell2} are: {celH }, {cell2}, and {celH , cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0042] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0043] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0044] Many features presented are described as being optional through the use of “may” or the use of parentheses For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of thethree possible features, with any two of the three possible features or with three of the three possible features.

[0045] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. , hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0046] FIG. 1 A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

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

[0048] The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may 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. Downlinktransmissions may be separated from uplink transmissions using frequency division duplexing (FDD), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques.

[0049] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0050] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

[0051] A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.

[0052] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similarfunctions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

[0053] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0054] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). 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 may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non- 3GPP radio access technologies.

[0055] FIG. 1 B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1 B, 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 may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1 A.

[0056] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g , the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other networkfunctions. The network functions of the 5G-CN 152 may 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).

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

[0058] The AMF 158A may 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 3GPP 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 checking of roaming rights, mobility management control (subscription and policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

[0059] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1 B for the sake of clarity. For example, the 5G-CN 152 may 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).

[0060] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more ofthe ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0061] As shown in FIG. 1 B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1 B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

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

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

[0064] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Althoughonly one AMF / UPF 158 is shown in FIG. 1 B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

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

[0066] FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1 B.

[0067] FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

[0068] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

[0069] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messagesoriginate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

[0070] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer 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, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when 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 may map / de-map the split radio bearer between RLC channels belonging to cell groups.

[0071] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

[0072] The MACs 212 and 222 may perform m ulti plexing / demu I tiplexin g of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221 . The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through 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 means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

[0073] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface.These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

[0074] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

[0075] The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

[0076] The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g ., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222 The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

[0077] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0078] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) andat the end of a MAC PDU for uplink transmissions. MAC CEs may 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 for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0079] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

[0080] FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

[0081] - a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;

[0082] - a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;

[0083] - a common control channel (CCCH) for carrying control messages together with random access;

[0084] - a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and

[0085] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.

[0086] Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

[0087] - a paging channel (PCH) for carrying paging messages that originated from the PCCH;

[0088] - a broadcast channel (BCH) for carrying the M IB from the BCCH;

[0089] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;

[0090] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0091] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

[0092] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

[0093] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0094] -- a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;

[0095] - a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0096] -- a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;

[0097] - a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PM I), rank indicators (Rl), and scheduling requests (SR); and

[0098] - a physical random access channel (PRACH) for random access.

[0099] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

[0100] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221 , the MAGs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top ofthe stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0101] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may 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 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0102] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex controlplane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the 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, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

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

[0104] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1 B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the basestation. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the 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 may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

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

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

[0107] An RRC state may be associated with a mobility management mechanism. 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 notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified bya RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

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

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

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

[0111] A g N B, such as gNBs 160 in FIG. 1 B, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0112] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M- QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F timedomain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up- conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on acarrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

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

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

[0115] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

[0116] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275*12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacingsof 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

[0117] FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0118] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE may 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.

[0119] NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via 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 for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0120] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

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

[0122] For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (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. The UE may transmit uplink transmissions (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).

[0123] One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

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

[0125] A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g . , 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, 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 may switch from the active downlink BWP to the default downlink BWP.

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

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

[0128] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG 9, 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 and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0129] If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same / similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.

[0130] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

[0131] FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B) .

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

[0133] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The otheraggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

[0134] Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0135] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as selfscheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

[0136] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011 , an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051 , an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021 , an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061 , an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031 , UC1 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021 . Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071 , UC1 1072, and UC1 1073, may be transmitted in the uplink of the PSCell 1061 . In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061 , overloading may be prevented.

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

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

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

[0140] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

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

[0142] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may 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 the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD- SSB.

[0143] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

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

[0145] The UE may assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, averagegain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions having different SS / PBCH block indices.

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

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

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

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

[0150] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

[0151] The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlinkCSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

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

[0153] In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may 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 may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0154] A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

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

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

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

[0158] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

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

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

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

[0162] Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or morereference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

[0163] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0165] CSI-RSs such as those illustrated in FIG. 11 B (e.g., CSI-RS 1101 , 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI).The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may 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 may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0166] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).

[0167] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1 . This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

[0168] FIG. 12B illustrates examples of three uplink beam management procedures: U1 , U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweepfrom a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1 . This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0169] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).

[0170] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may 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 RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

[0171] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJDLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g , other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0172] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0173] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: 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 may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRCJNACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

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

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

[0176] The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 3 1313. The UE may 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). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

[0177] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 3 1313. As another example, the one or more RACH parameters may 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). A base station may 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 may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

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

[0179] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g , ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0180] RA-RNTI= 1 + s_id + 14 x t_id + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id , where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < t_id < 80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0 £ f_id < 8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0181] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g , using resources identified in the Msg 2 1312) The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 4 1314) maybe used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g . , a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0182] The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRCJDLE state or not otherwise 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 a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0183] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and / or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 3 1313 based on a channel clear assessment (e.g., a listen-before-talk).

[0184] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 4 1314.

[0185] The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station mayindicate or assign to the UE the preamble to be used for the Msg 1 1321 . The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-Preamblelndex).

[0186] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recovery SearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the con tention -free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

[0187] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

[0188] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331 . The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 4 1314 illustrated in FIG. 13A.

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

[0190] The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and / or an uplink transmit power for the preamble 1341 and / or thetransport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a RUSCH) may be multiplexed using RDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

[0191] The transport block 1342 may comprise 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 may transmit the Msg B 1332 as a response to the Msg A 1331 . The Msg B 1332 may comprise at least one of following: 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 may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

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

[0193] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

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

[0195] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as "FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0196] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1 _0) . DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

[0198] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the 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 the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

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

[0200] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored 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 the common search space set may be predefined and known to the UE. A set of CCEs in the UE- specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0201] As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCHcandidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g , number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0202] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (RUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0203] There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may 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 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteenOFDM symbols and may include more than two bits. The UE may 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.

[0204] The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to "0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having 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 may select a third PUCCH resource set having 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 may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

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

[0206] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1 B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

[0207] The base station 1504 may 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. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

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

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

[0210] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0211] As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may 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 / orbeamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0212] The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non- transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

[0213] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, 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, an onboard unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0214] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, 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, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526 The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 anda GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0215] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0216] FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

[0217] FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0218] FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0219] A wireless device may receive from a base station one or more messages (e.g., RRC messages) comprising configuration parameters of a plurality of cells (e.g., primary cell, secondary cell). The wireless device may 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 a part of the configurationparameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0220] A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0221] Artificial intelligence (Al) and / or machine learning (ML) (AI / ML) is a data driven algorithm, scheme, or mechanism. An AI / ML model may apply one or more AI / ML techniques for generating a set of outputs based on a set of inputs. For example, a wireless device may use training data for generating a set of outputs based on the training data. The training data may also be referred to as trained data or data for training. The generating may also be referred to as producing, creating, or forming the set of outputs.

[0222] The wireless device may use the AI / ML model, e.g., based on one or more AI / ML techniques. In the present disclosure, an AI / ML model may be referred to as an ML model and AI / ML techniques may also be referred to as machine learning techniques. Examples of AI / ML techniques may be federated learning, reinforcement learning, supervised learning, unsupervised learning, etc. Federated learning may also be referred to as a federated training technique.

[0223] In an example, a federated learning technique may train an AI / ML model across multiple decentralized nodes (e.g., wireless devices, base stations, etc.). Each node may locally train a model based on local data samples. The federated learning technique may involve (or comprise) multiple interactions of the model.

[0224] In an example, a reinforcement learning technique may train an AI / ML model from an input, and a feedback signal resulting from the output of the AI / ML model.

[0225] In an example, a supervised learning technique may train an AI / ML model from an input, and labels associated with the input data.

[0226] In an example, an unsupervised learning technique may train an AI / ML model from an input without labelled data.

[0227] In an example, an AI / ML model may also be referred to as a model. In an example, an AI / ML model may also be referred to as a radio procedure. In an example, a radio procedure may also be referred to as a radio access communication (RAC), a measurement procedure, a positioning procedure, or a radio link procedure. A measurement procedure may comprise a layer-3 measurement procedure, a mobility measurement procedure, etc. A positioning procedure may also be referred to as a positioning measurement procedure. A radio link procedure may comprise a radio link monitoring (RLM) procedure, or a beam management (BM) procedure. The BM procedure may also be referred to as a link recovery procedure (LRP)

[0228] In an example, a wireless device may use one or more AI / ML models for inferring data based on trained data. An AI / ML model used by a wireless device for inferring data may also be referred to as a single-sided, one-sided, or a wireless device-sided model. In another example, a base station may use one or more AI / ML models for inferring data based on trained data. An AI / ML model used by a base station for inferring data may also be referred to as a single-sided, a one-sided, or a base station-sided model. In an example, the set of data for training or trained data may be a set of measurement samples. In an example, the inferring data may include predicting one or more data. The predicting the one or more data may also be referred to as determining, identifying or estimating the one or more data.

[0229] In an example, a base station may infer data based on an AI / ML model. An AI / ML model used by a wireless device for inferring data may be referred to as a base station-side model. A base station-side model may be referred to as a base station-based model.

[0230] In an example, a wireless device and a base station may jointly infer data based on their respective AI / ML models. An AI / ML model used by a wireless device and a base station for jointly inferring data may be referred to as a two-sided model. A two-sided model may also be referred to as a double-sided model. In an example of the two-sided model, a part of the data is inferred by a wireless device and a part of the data is inferred by a base station. In an example of a two-sided model, a wireless device may use an AI / ML model based encoder to generate data. The wireless device may transmit, to a base station, the generated data. An example of the generated data may include a compressed channel state information (CSI) (e.g., a channel quality indicator (CQI)). The base station may use an AI / ML model based decoder to decode the received data.

[0231] A wireless device may communicate with a base station based on the AI / ML model. For example, the wireless device may transmit one or more messages to the base station based on the data inferred from the AI / ML model as discussed above.

[0232] FIG. 17 illustrates an example of using an AI / ML model 1700 per an aspect of the present disclosure. For example, FIG. 17 illustrates different stages comprising, or involving, AI / ML model 1700. A stage may refer to as a mode, a level, a step, an entity, or a unit. The different stages comprising AI / ML model 1700 may also be referred to as involving, or belonging to, AI / ML model 1700. A stage of the different stages may be for generating AI / ML model 1700. A stage of the different stages may be for inference procedure for inferring data based on AI / ML model 1700.

[0233] As illustrated in FIG. 17, AI / ML model 1700 comprises an AI / ML model generation stage 1720 and an interfering data stage 1740. In an example as shown in FIG. 17, AI / ML model generation stage 1720, of AI / ML model 1700, may receive training data 1702. AI / ML model generation stage 1720 may also be referred to as an AI / ML model generating stage or an AI / ML model generating level. AI / ML model generation stage 1720 may generate an output data used for inferring data. Inferring data may also be referred to as inferring a result. Inferring data may also be referred to as predicting data, estimating data, determining data, forecasting data, or presuming data. As illustrated in FIG. 17, the output data for inferring data may be, or may comprise, an input 1704 for inference. In the example in FIG.17, inferring data stage 1708 may receive input 1704 from AI / ML model generation stage 1720. Inferring data stage 1740 may generate inferred data 1706 based on input 1706 received from AI / ML model generating stage 1720. Generating inferred data 1706 may be referred to as inferring data.

[0234] A wireless device may use one or more AI / ML models for inferring data based on trained data. In an example, the inferring data may comprise predicting one or more data. Predicting the one or more data may also be referred to as determining, identifying or estimating the one or more data. The one or more data may comprise: a channel state information (CSI); and / or an in-sync (IS) detection for a radio link monitoring (RLM); and / or an out-of-sync (OOS) detection for the RLM; and / or a beam failure detection (BFD); and / or a candidate beam detection (CBD); and / or a layer-1 reference signal received power (L1- RSRP) for a link recovery procedure (LRP); and / or a layer-1 signal to interference and noise ratio (L1- SINR) for the LRP; and / or one or more positioning measurements; and / or one or more layer-3 mobility measurements.

[0235] Examples of the CSI may be a channel quality indicator (CQI); a rank indicator (Rl); a precoding matrix indicator (PMI), etc. In an example, a wireless device inferring or predicting the CSI may comprise predicting the CSI in time domain. In an example, a wireless device inferring the CSI may comprise inferring the CSI in spatial-frequency domain. In an example, the wireless device may further transmit, to the base station, the inferred (or the predicted) CSI.

[0236] Examples of the one or more positioning measurements may include a reference signal time difference (RSTD); an UE Rx-Tx time difference measurement; a round trip time (RTT); a multi-RTT; a carrier phase measurement (CPP); a channel impulse response (CIR); a time of arrival (TOA); a reference signal received power (RSRP); a reference signal received path power (RSRPP); a positioning reference signal - reference signal received power (PRS-RSRP); a positioning reference signal - reference signal received path power (PRS-RSRPP); an angle of arrival (AOA); an angle of departure (AOD); a power delay profile (PDP); a delay profile (DP), etc. In an example, the wireless device may transmit, to a location server (e.g., a location management function (LMF)), the inferred (or the predicted) one or more positioning measurements.

[0237] The layer-3 mobility measurement may also be referred to as a layer-3 measurement or a mobility measurement. Examples of the one or more layer-3 mobility measurements may include a pathloss; a reference signal received power (RSRP); a reference signal received quality (RSRQ); a signal to interference and noise ratio (SINR), etc. In an example, the wireless device may transmit, to a base station, the inferred (or the predicted) one or more layer-3 measurements.

[0238] In an example, a wireless device inferring data based on the model for a radio procedure may comprise inferring or predicting a spatial-domain downlink beam and / or a temporal downlink beam. The spatial-domain downlink beam prediction may leverage measurement outcomes from a designated set of downlink beams, denoted as ‘Set B,' to predict the best beam within another set of downlink beams, referred to as ‘Set A,’ at the present moment. The temporal downlink beam prediction may harness historical measurement results derived from ‘Set B’ to anticipate the best beam in ‘Set A’ for one or more future time instances. In an example, an input to an AI / ML model for the spatial-domain or temporal downlink beam prediction may be layer 1 reference signal received power (L1-RSRP) measurements of beams within ‘Set B.’ In an example, an output from the AI / ML model may be the predicted top-K beams in ‘Set A.’ The AI / ML model training and inference may reside at the base station (e.g., a gNB) side or at the wireless device side. In the former case, the wireless device may measure the L1-RSRP measurements for the beams within ‘Set B‘ . The wireless device may report, to the base station, the L1-RSRP measurements for the beams within ‘Set B’ . In the latter case, the wireless device may predict the beams. The wireless device may further transmit, to the base station, the predicted beams.

[0239] In an example, a base station inferring data based on the model for a radio procedure may comprise inferring a measurement. Examples of the base station measurement may be a secondary synchronization signal (SSS) transmit power; an uplink (UL) Relative Time of Arrival (TUL-RTOA); a base station Rx-Tx time difference (e.g., a gNB Rx-Tx time difference); a round trip time; an angle of arrival (AoA) (e.g., an UL AoA); an angle of departure (AoD) (e.g., an UL AoD); a reference signal received power (RSRP); a path loss; an uplink sounding reference signal - reference signal received power (UL SRS-RSRP); an UL SRS reference signal received path power (UL SRS-RSRPP); a Timing advance (TADV); a carrier phase measurement (CPP); an uplink reference signal carrier phase (UL RSCP); a channel impulse response (CIR); a delay profile (DP); a power delay profile (PDP); a signal to noise ratio (SNR); a signal to interference and noise ratio (SINR), etc. In an example, a base station inferring or predicting a measurement may comprise predicting or inferring the measurement in time domain, spatial domain, and / or frequency domain. In an example, the base station may further transmit, to another node (e.g., another base station, a location server, a core network node, etc.), the inferred (or the predicted) measurement.

[0240] A life cycle management (LCM) of an AI / ML model may include developing, deploying, managing, or maintaining an AI / ML model. In an example, an LCM of an AI / ML model may include performing one or more LCM procedures on the AI / ML model. In an example, an LCM procedure may include performing at least one of: an identification of the AI / ML model, a selection of an AI / ML model, an activation of the AI / ML model, a deactivation of the AI / ML, a fallback from the AI / ML model to a measurement procedure, a switching from a measurement procedure to the AI / ML model, a switch from the AI / ML model to another AI / ML model, a release of the AL / ML model, a monitoring of the AI / ML model, and a modification of one or more parameters of the AI / ML model.

[0241] In an example, a wireless device may use a measurement procedure for obtaining a measurement. In an example, a base station may use a measurement procedure for obtaining a measurement. In an example, using the measurement procedure may also be referred to as applying the measurement procedure. In an example, obtaining a measurement may also be referred to as performing the measurement. In an example, the measurement procedure may comprise performing a measurement based on a signal. In an example, the measurement procedure in a wireless device may comprise performing a measurement based on a signal transmitted and / or received by the wireless device. In an example, the signal may be a reference signal. In an example, a measurement procedure in a base station may comprise performing a measurement based on a signal transmitted and / or received by the base station.

[0242] In an example, performing an LCM procedure may include: identifying an AI / ML model; and / or selecting an AI / ML model; and / or activating an AI / ML model; and / or deactivating an AI / ML model; and / or falling back from an AI / ML model to using a measurement procedure; and / or switching from using a measurement procedure to an AI / ML model; and / or switching from an AI / ML model to another AI / ML model; monitoring an AI / ML model; releasing an AI / ML model; and / or modifying one or more parameters of an AI / ML model.

[0243] In an example, a wireless device may perform an LCM procedure on an AI / ML model stored in the wireless device.

[0244] In an example, a base station may perform an LCM procedure on an AI / ML model stored in the base station.

[0245] The LCM procedure may be a functionality-based LCM. Corresponding to the functionality-based LCM procedure, a base station may configure a wireless device to perform the LCM procedure for an AI / L model stored in the wireless device. In an example, a base station may configure a wireless device to perform the LCM procedure by RRC. In an example, a base station may configure a wireless device to perform the LCM procedure by MAC-CE. In an example, a base station may configure a wireless device to perform the LCM procedure by DCI. In some aspects, a mechanism for the base station to configure the wireless device with the LCM procedure may also be referred to as the functionality based LCM. The mechanism for the base station to configure the wireless device with the LCM procedure may also be referred as a procedure or protocol.

[0246] In an example, a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) during an LCM procedure. In an example, an interruption of the communication may include, the wireless device not receiving a signal from the base station, and / or the wireless device not transmitting a signal to the base station. In an example, a wireless device not transmitting a signal may also be referred to as dropping, discarding, abandoning, or cancelling a signal.

[0247] FIG. 18 illustrates an example of a Life cycle management (LCM) procedure 1800 of a model (e.g., an AI / ML model), such as an AI / ML model, per an aspect of the present disclosure. In an example, a wireless device may autonomously perform LCM procedure 1800 for a model. Additionally or alternatively, a base station may autonomously perform LCM procedure 1800 for a model. In the example of FIG. 18, LCM procedure 1800 may include one or more of: a model identification 1802 (e.g., an identification of an AI / ML model), a model selection 1804 (e.g., a selection of the AI / ML model), a model switching 1806 (e.g., switching of the AI / ML model to another AI / ML model), a model deactivation 1808 (e.g., deactivating the AI / ML model), a model activation (e.g., activating the AI / ML model), model monitoring 1812 (e.g., monitoring the AI / ML model), and / or a fallback 1814 (e.g., determining to fallback from the AI / ML model to a measurement procedure).

[0248] For example, LCM procedure 1800 may be performed prior to a cell reselection procedure, a handover procedure, a positioning procedure, a radio link procedure (RLM) procedure, or a link recovery procedure (LRP) (e.g., a beam failure recovery (BFR) procedure). In an example, a wireless device may perform LCM procedure 1800 to fine tune / update / modify / activate the AI / ML mode for performing the cell reselection / handover / RLM / LRP or the like. In another example, a base station may perform LCM procedure 1800 to fine tune / update / modify / activate the AI / ML mode for performing the handover of a wireless device.

[0249] In another example, LCM procedure 1800 may be performed by a wireless device after a cell selection, an RRC connection re-establishment, a cell reselection procedure, a handover procedure, apositioning procedure, an RLM procedure, or a LRP (e.g., a beam failure recovery (BFR) procedure). Based on / in response to the cell reselection / handover / RLM / LRP procedure, the wireless device may select / activate a new AI / ML mode and / or deactivate the AI / ML model. In another example, the LCM procedure 1800 may be performed by a base station after a handover procedure, an RRC connection release with redirection, a radio link recovery procedure, or a beam failure recovery procedure.

[0250] FIG. 19 illustrates an example of a procedure for an AI / ML model capability transfer 1900 per an aspect of the present disclosure. The procedure 1900 may also be referred to as a signaling flow. AI / ML model capability transfer 1900 is performed between a wireless device 1920 and a base station 1940.

[0251] Wireless device 1920 may communicate with base station 1940. The communication between wireless device 1920 and base station 1940 may be based on an AI / ML model (e.g., AI / ML model 1700 of FIG. 17).

[0252] Before such communication between wireless device 1920 and base station 1940, base station 1940 may configure or request wireless device 1920 to transmit a capability. The capability may include or may be a model capability (e.g., an AI / ML model capability) of wireless device 1920. For example, base station 1940 may transmit one, or more RRC messages including one, or more configuration parameters for wireless device 1920 to transmit an AI / ML model capability. In another example, base station 1940 may transmit, to wireless device 1920, a capability inquiry 1902. Capability inquiry 1902 may be an RRC message. Capability inquiry 1902 may also be referred to as a capability request message, an inquiry message, or a radio access capability inquiry. Capability inquiry 1902 may indicate a request for wireless device 1920 to transmit, to base station 1840, the AI / ML model capability of wireless device 1920. Wireless device 1920 may transmit, to base station 1940, a capability information 1904 including (or indicating) an AI / ML model of wireless device 1920 in response to, or based on capability inquiry 1902.

[0253] In an example of FIG. 19, capability information 1904 may indicate that wireless device 1920 supports both stages of AI / ML model 1700 as illustrated in FIG. 17.

[0254] In an example of FIG.19, capability information 1904 may indicate that wireless device 1920 may support (or only support) AI / ML model generation stage 1720 of AI / ML model 1700 as illustrated in FIG. 17.

[0255] In an example of FIG.19, capability information 1904 may indicate that wireless device 1920 may support (or only support) an inferring data stage 1740 of AI / ML model 1700 as illustrated in FIG. 17.

[0256] In an example of FIG. 19, wireless device 1920 may indicate, to base station 1940, that wireless device 1920 may support one, or more AI / ML models, e.g., by RRC.

[0257] FIG. 20 illustrates an example of a procedure 2000 for an AI / ML model capability transfer from a wireless device 2020 to a location server 2040 per an aspect of the present disclosure. The location server may also be referred to as a positioning node, a positioning server, or a location management function (LMF). The configuring of wireless device 2020 to transmit AI / ML capability (e.g., capability inquiry 2002),and the transmission of the AI / ML capability (e.g., capability information 2004) by wireless device 2020 is described above with reference to FIG. 20. In an example as shown in FIG. 20, wireless device 2020 may indicate, to location server 2040, its capability of supporting one or more AI / ML models (as discussed above in FIG. 18), e.g., by a positioning protocol (or an LTE positioning protocol (LPP)).

[0258] In the example of FIG. 19 and the example of FIG. 20, wireless devices 1920 and 2020 may include in messages 1904 and 2004, respectively, an identifier (ID) for each AI / ML model supported by the wireless device. The identifier may be referred to as an AI / ML model ID or a model ID. A model ID may serve as a distinctive identifier for an AI / ML model. A model ID of an AI / ML model may enable a mutual understanding between a base station and a wireless device of the AI / ML model. For example, each identifier may comprise two bits, e.g., 00, 01 and 11. For example, the identifiers comprising bits 00, 01 , 10, and 11 , may indicate (or correspond to) an AI / ML model for determining a predicted CSI, an AI / ML model for determining a predicted layer- measurement, an AI / ML model for determining a predicted layer-3 measurement, and an AI / ML model for a positioning measurement, respectively.

[0259] Wireless devices 1920 and 2020 may further include in messages 1904 and 2004, respectively, information about one or more conditions in which the wireless device may use an AI / ML model. In an example, a condition may comprise a speed of the wireless device. In an example, a condition may comprise a speed range of the wireless device. In an example, a condition may comprise a geographical area. A geographical area may also be referred to as a region. An example of a geographical area may comprise a set of geographical coordinates. In another example, a condition may comprise one or more radio channel characteristics. In an example a radio channel characteristic may comprise a Doppler frequency. In an example a radio channel characteristic may comprise a Doppler spectrum or a Doppler spread. In an example a radio channel characteristic may comprise a channel delay spread. In an example a radio channel characteristic may comprise a channel coherence time.

[0260] In an example, a wireless device may train an AI / ML model , such as those discussed above, based on training data.

[0261] In an example, a base station may train an AI / ML model , such as those discussed above, based on training data.

[0262] In an example, a base station may transmit one or more messages to the wireless device. The one or more messages may include at least one RRC message, at least one MAC CE, and / or at least one DCI. The one or more messages may include one or more parameters of an AI / ML model. The one or more parameters may correspond to the AI / ML mode. In some cases, the base station may transmit at least one DCI comprising the one or more parameters. In an example, the one or more parameters of the AI / ML model may include an AI / ML model identifier. In an example, the one or more parameters of the AI / ML model may comprise a set of data for training an AI / ML model. In an example, the set of data for trainingthe AI / ML model may be a set of measurement samples. In an example, the wireless device may train the AI / ML model by using the one or more parameters received from the base station.

[0263] The wireless device may further receive, from a base station, a reference signal configuration, e.g., via RRC signaling. The reference signal configuration may be included in a measurement configuration (e.g., a measurement object (MO)). The reference signal configuration may comprise one or more parameters, e.g., a reference signal index or identifier, a reference signal duration or occasion or window, a reference signal periodicity, a time offset, etc.

[0264] In an example, the reference signal may be a downlink reference signal, e.g., transmitted by a base station. For example, the reference signal may be transmitted in one or more cells, e.g., in a serving cell and one or more neighbor cells of the wireless device. The one or more cells may be operated, managed, or served by one or more network nodes, e.g., one or more base stations. Examples of the downlink reference signals may be a SS / PBCH block (SSB), a CSI-RS, a positioning reference signal (PRS), a tracking reference signal (TRS), a DMRS, a SS / PBCH Block Measurement Timing Configuration (SMTC), etc. Each SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH) within 4 successive symbols. The SMTC configuration may be associated with one or more SMTC parameters, e.g. a SMTC index or identifier, a SMTC duration or window, a SMTC periodicity, a SMTC time offset, etc. One or multiple SSBs are comprised within a SMTC duration. The SMTC occasion may occur with a periodicity, e.g., every 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms, etc. In another example, the reference signal may be an uplink reference signal, e.g., transmitted by the wireless device. Examples of the uplink reference signals may be a SRS, a DMRS, etc. For example, the wireless device may transmit the uplink reference signals (e.g., a SRS) in a serving cell of the wireless device.

[0265] In an example, the wireless device may further receive, from a base station, a measurement configuration for one or more measurements (e.g., a cell identification, a RSRP, a RSRQ, a SINR, a global cell ID (CGI), etc). In another example, the wireless device may further receive, from a location server, a measurement configuration (e.g., an assistance data or an assistance information) for one or more positioning measurements (e.g., a RSTD, a UE Rx-Tx time difference, an AOA, an AOD, a CPP, a PD, a PDP, a CIR, a PRS-RSRP, a PRS-RSRPP, etc).

[0266] In an example, the measurement configuration may further include information about (or associated with) one or more carrier frequencies. The one or more carrier frequencies are associated with (or related to) the one or more measurements included in the measurement configuration.

[0267] The carrier frequency may also be referred to as a carrier, a frequency, a component carrier (CC), a layer, a frequency layer, frequency channel, positioning frequency layer (PFL), etc. The carrier frequency may belong to a frequency band. The frequency band may include one or multiple carrier frequencies. Thenumber of the carrier frequencies within a frequency band may depend on a passband (e.g., length of the band in frequency domain) and / or a bandwidth of the carrier frequencies and / or a raster (e.g., a point in frequency where a carrier frequency may be centered, etc.

[0268] The information about (or associated with) the one or more carrier frequencies may be indicated by a channel number or an identifier. In example, the channel number or the identifier may be pre-defined. For example, the channel number may be an absolute radio frequency channel number (ARFCN). Examples of the ARFCN may be E-UTRA ARFCN (EARFCN), NR ARFCN (NR-ARFCN), etc. For example, a carrier frequency associated with SSB based measurements (e.g., SS-RSRP, SS-RSRQ, SS-SINR, etc.) may be indicated by an SSB ARFCN, e.g., in the measurement configuration. For example, the SSB ARFCN may indicate a frequency location within a bandwidth of an SSB. For example, the SSB may include 20 resource blocks enumerated from resource block # 0 to resource block # 19. In an example, the indicated frequency location (e.g , a SSB ARFCN) may correspond to a resource element # 0 within a resource block # 0 of the resource blocks of the SSB.

[0269] A wireless device may use internal resources of the wireless device for performing a Life Cycle Management (LCM) procedure (e.g., LCM procedure 1800 in FIG. 18) for an AI / ML model (e.g., AI / ML model 1700 in FIG. 17). In an example, the internal resources of the wireless device may comprise a memory and / or a processor and / or battery power. The wireless device may share the internal resources used for performing the LCM procedure to also perform one or more additional tasks. The one or more additional tasks may comprise at least one of processing data, receiving a signal, transmitting a signal, performing online and / or offline services (or functionalities or applications or the like), etc. The one or more additional tasks may not correspond to, or include, the LCM procedure. An online and / or offline service may also be referred to as a functionality or an application. The one or more additional tasks may correspond to a Radio Link Monitoring (RLM) procedure; and / or a handover procedure; cell reselection procedure; and / or a link recovery procedure; and / or a measurement procedure; and / or a positioning procedure; and / or a data transmission; and / or data reception. In an example, the wireless device may be configured with a multicarrier operation for the data reception and / or for the data transmission. Examples of the multicarrier operation may be a carrier aggregation, a multi-connectivity, or a dual connectivity. In an example, the wireless device may be configured with a multi-antenna operation for the data reception and / or for the data transmission. An example of multi-antenna operation may be an (MxN) multiple input multiple output (MIMO) configuration, where M may correspond to a number of transmit antennas, and N may correspond to a number of receive antennas. The multicarrier operation and / or the multi-antenna operation may increase the usage of the internal resources of the wireless devices. In an example, the wireless device may interrupt communications with the base station due to the sharing of the internal resources between the LCM procedure and due to performing the one or more additional tasks. The interruption of thecommunications may comprise not transmitting one or more signals to the base station. The interruption of the communications may comprise not receiving one or more signals from the base station.

[0270] FIG. 21 illustrates an example of communications 2100 between a wireless device 2120 and a base station 2140 per an aspect of the present disclosure. Communications between wireless device 2120 and base station 2140 may be based on an AI / ML model (e.g., AI / ML model 1700 of FIG. 17).

[0271] FIG. 21 illustrates an example comprising base station 2140 transmitting, to wireless device 2120, a downlink signal 2106. In an example, wireless device 2120 may trigger an LCM procedure (e.g., LCM procedure 1800 in FIG. 18). As illustrated in the example of FIG. 21 , wireless device 2120 may start an LCM procedure 2102 based on the triggering of the LCM procedure. As illustrated in the example of FIG. 21 , an interruption duration 2104 may start based on (or due to) the LCM procedure. For example, interruption duration 2104 may start from the start of LCM procedure 2102. As illustrated in the example of FIG 21 , wireless device 2120 may interrupt (e.g., not receive, not detect, not decode) downlink signals 2106 during interruption duration 2104. For example, interruption of the communications between wireless device 2120 and base station 2140 may occur during interruption duration 2104.

[0272] The LCM procedure may comprise a reconfiguration of a radio frequency (RF) bandwidth of the wireless device. The reconfiguration of a radio frequency (RF) bandwidth of the wireless device may comprise switching from using an AI / ML model to a measurement procedure or vice versa. In an example, the wireless device may interrupt communications with the base station (e.g., not transmit and / or not receive) due to the reconfiguration of the RF bandwidth of the wireless device.

[0273] For example, the LCM procedure may comprise tuning, retuning, changing, and / or reconfiguring one or more RF circuitries. Tuning, retuning, changing or reconfiguring the one or more RF circuitries my result in the interruption of the communications. The RF circuitry may comprise one or more of an RF filter, a power amplifier (PA), a low noise amplifier (LNA), an antenna, an antenna panel, an antenna array, an antenna element, a switch, etc.

[0274] In another example, the LCM procedure may comprise retraining (or fine tuning) the AI / ML model. For example, the wireless device may use the shared resources for fetching one or more parameters (of the AI / ML model) in order to fine tune (or retrain) the AI / ML model. Retraining the AI / ML mode may comprise gathering (or obtaining or acquiring or receiving) a new set of training data corresponding to the AI / ML model. Retraining (or fine tuning) the AI / ML mode may comprise changing / updating one or more meta parameters of the AI / ML model. Retraining (or fine tuning) the AI / ML mode may comprise reconstructing the AI / ML model.

[0275] The LCM procedure may comprise measuring (or determining or estimating) one or more key performance indicators (KPIs) (e.g., metrics, criteria, performance measures, etc.) corresponding to the AI / ML model. The one or more KPIs may demonstrate a performance (or an accuracy) of the AI / ML mode.Measuring (or determining or estimating) the one or more KPIs (e.g., metrics, criteria, performance measures, etc.) may result in the interruption of the communications as the wireless device may perform at least one measurement.

[0276] The wireless device may use the one or more KPIs for selecting an AI / ML mode.

[0277] The wireless device may use the one or more KPIs for activating an AI / ML mode and / or deactivating an AI / ML model.

[0278] The wireless device may use the one or more KPIs for fallback from an AI / ML mode, e.g., stop using the AI / ML model.

[0279] In the example of FIG.18, in one example, a wireless device may autonomously perform the LCM procedure.

[0280] For example, the LCM procedure may be performed prior to a handover procedure or an RLM procedure or a beam failure recovery (BFR) procedure. The wireless device may perform the LCM procedure to finetune, update, and / or activate an AI / ML model for performing the handover, the RLM, and / or the BFR or the like.

[0281] In another example, the LCM procedure may be performed after a handover procedure, an RLM procedure, or a BFR procedure. Based on (e.g., in response to) the handover, the RLM procedure, and / or the BFR procedure, the wireless device may select (e.g., activate) a new AI / ML mode and / or deactivate the AI / ML model.

[0282] In existing technologies, a wireless device may (e.g., autonomously) perform an LCM (e.g., LCM procedure 1800 in FIG. 18) procedure for an AI / ML model (e.g., AI / ML model 1700 in FIG. 17). For example, the wireless device may perform the LCM procedure at any arbitrary time. By autonomously performing the LCM procedure for the AI / ML model (e.g., determining to autonomously perform the LCM procedure), the wireless device may cause an interruption of communication between the wireless device and a base station, which may result in misalignment between the wireless device and the base station.

[0283] In existing technologies, the base station may configure the wireless device, e.g., by RRC, MAC- CE or DCI, to perform the LCM procedure (e.g., LCM procedure 1800 in FIG. 18) for an AI / ML model (e.g., AI / ML model 1700 in FIG. 17). Although the configuration may allow the wireless device to perform the LCM procedure, the LCM procedure may cause an interruption of communications between the wireless device and a base station. In an example, the base station may incur unexpected interruption of communications after transmitting, to the wireless device, the configuration message. In another example, as the LCM procedure may depend on the internal resources of the wireless device (e.g., whether the internal resources are fully or partially available for the performing the LCM procedure), the base station may not be able to accurately determine (or identify or detect) the actual duration of the interruption.

[0284] In the existing technologies, performing the LCM procedure for an AI / ML model (e.g., during the interruption window) may result in a loss of uplink data and / or downlink data (e.g., loss of PUSCH and / or PDSCH). For example, performing the LCM procedure may increase UL / DL data latency and / or reduce UL / DL data transmission rate. In an example, the wireless device may not transmit an uplink data and / or receive a downlink data during the LCM procedure.

[0285] In the existing technologies, performing the LCM procedure for an AI / ML model may result in loss of control signaling (e.g., a HARQ feedback, a CSI report, etc.). In an example, the wireless device may not transmit an uplink control signaling and / or receive a downlink control signaling during the LCM procedure.

[0286] In the existing technologies, performing the LCM procedure for an AI / ML model may result in loss of a reference signal. In an example, the wireless device may not transmit an uplink reference signal and / or receive a downlink reference signal during the LCM procedure. The existing technologies, when implemented for performing an LCM procedure for an AI / ML model, may degrade accuracy of a measurement performed by a wireless device based on a reference signal.

[0287] In the existing technologies, performing the LCM procedure for an AI / ML model may waste radio resources (in time and / or in frequency). In an example, a radio resource may comprise a resource element. In an example, a radio resource may comprise a resource block. In an example, a base station may allocate, to the wireless device, one or more radio resources to perform one or more procedures. In an example, the one or more procedures may comprise: transmitting data; and / or receiving data; and / or transmitting a control signaling; and / or receiving a control signaling.

[0288] In existing technologies, a duration of the interruption due to an LCM procedure (e.g., LCM procedure 1800 in FIG. 18) may be fixed (or predefined) (e.g. a fixed duration of the interruption). The fixed duration may be defined regardless of the internal resources supported by the wireless device (e.g., a memory, a processor, battery power, etc., supported by the wireless device). The fixed duration may be defined regardless of the currently available internal resources in the wireless device. The fixed duration may be defined regardless of whether the wireless device is performing the one or more additional tasks. The fixed duration may be defined regardless of the number of the one or more additional tasks is being performed by the wireless device.

[0289] In an exemplary scenario, the wireless device may not always be using all the internal resources of the wireless device for performing the one or more additional tasks. In another exemplary scenario, the number of the additional tasks being performed by the wireless device may not be larger than a threshold. The implementation of wireless devices may vary or differ with each other. For example, different wireless devices may support (or may be capable of) different size / amount of the internal resources. For example, depending on the implementation of the wireless device, in practice, the wireless device may interrupt the communications with the base station over a duration shorter than the predefined duration of theinterruption. For example, a base station (e.g., base station 2140 in FIG. 21) may not transmit signal (e.g., downlink signal 2106 in FIG. 21) over the predefined duration of the interruption (e.g., interruption duration 2104 in FIG. 21). The fixed duration (or the pre-defined duration) of the interruption due to (or caused by) the LCM procedure (e.g., LCM procedure 1800 in FIG. 18) may be inefficient, may result in loss of throughput, and may degrade system performance (e.g. reduction of user data rate).

[0290] In existing technologies, a fixed (or pre-defined) duration of the interruption of communications due to an LCM procedure (e.g., LCM procedure 1800 in FIG. 18) may be defined (or specified) regardless of the internal resources of the wireless device and / or regardless of the number of the additional tasks (e.g., other than the LCM procedure) being performed by the wireless device. The fixed duration (or the pre-defined duration) of the interruption due to an LCM procedure (e.g., LCM procedure 1800 in FIG. 18) may be inefficient. The fixed duration of the interruption may lead to unnecessary interruption of communications. The fixed duration of the interruption may degrade performance (e.g , throughput loss).

[0291] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described further below.

[0292] In an example embodiment, a wireless device may receive, from a node, a request for a capability of the wireless device. The wireless device may transmit, to the node and based on the request, a capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure for a radio procedure.

[0293] By the capability message indicating the time duration associated with the interruption of communications that occurs based on the LCM procedure for the radio procedure, reliability in the communications between the wireless device and base station may be improved (e.g., as the network is aware of the time duration associated with the interruption) based on the alignment in communications between the wireless device and the base station relative to the interruption.

[0294] In an example embodiment, a wireless device may receive, from a node, a request for a capability of the wireless device. The wireless device may transmit, to the node and based on the request, a first capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure for a radio procedure. The time duration may be determined based on the LCM procedure.

[0295] In an example embodiment, a wireless device may receive, from a node, a request for a capability of the wireless device. The wireless device may transmit, to the node and based on the request, a first capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure for a radio procedure. The time duration may be a switching time for a transceiver. A duration of the interruption may be determined based on the time duration and an offset.

[0296] In an example embodiment, a wireless device may receive, from a node, a request for a capability of the wireless device. The wireless device may transmit, to the node and based on the request, a first capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure for a radio procedure. The wireless device may transmit, to the node, a second capability message indicating an update to the time duration.

[0297] By the second capability message indicating the update to the time duration associated with the interruption of communications that occurs based on the LCM procedure for the radio procedure, reliability in the communications between the wireless device and base station may be improved (e.g., as this makes network aware of the current (or updated or latest) time duration associated with the interruption) based on the alignment in communications between the wireless device and the base station relative to the interruption.

[0298] FIG. 22 illustrates an example of a capability transfer procedure 2200 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 22 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, and / or 21 .

[0299] As illustrated in FIG. 22, a wireless device 2220 may receive, from a node 2240, a capability inquiry 2202. Wireless device 2220 may transmit, to node 2240 and based on (e.g., in response to) capability inquiry 2202, a capability information 2204 indicating a time duration 2206 associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure (e.g., LCM procedure 1800 in FIG. 18) for a radio procedure.

[0300] In an example, wireless device 2220 may receive, from node 2240, capability inquiry 2202 via an RRC message or a positioning protocol signaling (e.g., an LTE positioning protocol (LPP) message).

[0301] In an example, wireless device 2220 may transmit, to node 2240, capability information 2204 via an RRC message or a positioning protocol signaling (e.g., an LTE positioning protocol (LPP) message).

[0302] In an example, node 2240 may be a base station. Examples of the base station may be a g N B, a gNB control unit (gNB-CU), a transmission reception point (TRP), etc.

[0303] In an example, node 2240 may be a location server (e.g., a location management function (LMF)). The location server may also be referred to as a location node, a positioning node, or a positioning server.

[0304] In an example, node 2240 may be a core network node (e.g., an access and mobility management function (AMF)).

[0305] In an example, time duration 2206 may comprise one or more time units, or one or more time resources. Examples of the time resource may be a symbol, a slot, sub-slot, a mini-slot, a subframe, a radio frame, etc. The time unit may also be referred to as a length of time. The time unit may be expressed in nanoseconds (e.g., tu1 ns), milliseconds (e.g., tu2 ms), microsecond (e.g., tu3 pis), seconds, minutes, hours, etc.

[0306] In an example, two or more time durations may be pre-defined. For example, wireless device 2220 may determine (or select) one of the two or more pre-defined time durations as time duration 2206. For example, wireless device 2220 may determine time duration 2206 (e.g., from among the two or more predefined time durations) based on the implementation of wireless device 2220 (e.g., memory and / or processing capabilities of wireless device 2220). In an example, four time durations corresponding to Tx1 , Tx2, Tx3, and Tx4 may be pre-determined. In an example, Tx1 , Tx2, Tx3, and Tx4 may be expressed in time units (e.g., Tx1 pis, Tx2 pis, Tx3 pis, and Tx4 pis). In another example, Tx1 , Tx2, Tx3, and Tx4 may be expressed in time resources (e.g., Tx1 symbols, Tx2 symbols, Tx3 symbols, and Tx4 symbols). In an example, wireless device may include Tx2 as time duration 2206 in capability information 2204.

[0307] In an example, time duration 2206 may be determined based on (or may be associated with) one or more conditions (as described below). The one more conditions may also be referred to as one or more configurations, or one or more scenarios. Examples of the one or more conditions may be an LCM procedure, a model, a radio procedure, a numerology, a bandwidth, a frequency band, a frequency range, a signal range, a multicarrier configuration, a multi-antenna configuration, a power class, a beam management, a mobility state, etc.

[0308] In an example, time duration 2206 may be determined based on (or may be associated with) the LCM procedure (e.g., LCM procedure 1800 in FIG. 18).

[0309] In an example, time duration 2206 may be different for different LCM procedures. For example, capability information 2204 may indicate time durations 2206 supported by wireless device 2220 for the corresponding LCM procedures. For example, capability information 2204 may indicate time durations 2206 as t11 pis for model identification 1802 (in FIG. 18), t12 pis for model selection 1804 (in FIG. 18), t13 pis for model switching 1806 (in FIG. 18), t14 pis for model deactivation 1808 (in FIG. 18), and so on.

[0310] In another example, time duration 2206 may be the same for LCM procedures belonging to the same LCM group. For example, an LCM group may include (or comprise) two or more LCM procedures. LCM groups may be pre-determined, or configured (or created) by node 2240 (e.g., by the base station, or by the LMF). For example, a first LCM group may include model identification 1802, model selection 1804, and model monitoring 1812 (e.g., in FIG. 18). For example, a second LCM group may include model switching 1806, deactivation 1808, model activation 1810, and fallback 1814 (e.g., in FIG. 18). For example, time duration 2206 for the LCM procedures belonging to (or included in) the first group may be t21 pis. For example, time duration 2206 for the LCM procedures belonging to (or included in) the second group may be t22 pis. For example, capability information 2204 may indicate time durations 2206 supported by wireless device 2220 for the corresponding LCM groups. For example, capability information 2204 may indicate time durations 2206 as t21 pis for the LCM procedures in the first LCM group and t22 pis for the LCM procedures in the second LCM group.

[0311] In an example, time duration 2206 may be determined based on (or may be associated with) the model (e.g., AI / ML model 1700 in FIG. 17). For example, the model may be associated with (or identified by) an identifier. The identifier is according to the example embodiments in FIG. 17 (e.g , the AI / ML model identifier). For example, capability information 2204 may indicate time duration 2206 associated with each model (e.g., AI / ML model 1700 in FIG. 17) supported by wireless device 2220.

[0312] In an example, time duration 2206 may be determined based on (or may be associated with) the radio procedure (e.g., the radio access communication (RAC), the measurement procedure, the positioning procedure, or the radio link procedure as described earlier). Wireless device may perform the LCM for the radio procedure (e.g., model switching 1804 (in FIG. 18) for the positioning procedure, model switching 1804 (in FIG. 18) for the measurement procedure, etc.). For example, capability information 2204 may indicate time duration 2206 associated with the radio procedure for which wireless device 2220 may perform the LCM procedure.

[0313] In an example, time duration 2206 may be determined based on (or may be associated with) the numerology. The numerology may be associated with an uplink signal and / or a downlink signal. Examples of numerology may be a subcarrier spacing (SCS), a symbol duration, a slot duration, a subframe duration, a frame duration (or length), a cyclic prefix (CP) length, etc. Examples of the SCS may be 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz, etc. Examples of the slot duration may be 1 ms, 0.5 ms, 0.25 ms, 0.125 ms, 0.0125 ms, 0.00625 ms, etc. For example, capability information 2204 may indicate time duration 2206 associated with each numerology supported by wireless device 2220. For example, capability information 2204 may indicate time durations 2206 as tn 1 pis for the SCS corresponding to 15 kHz, tn2 pis for the SCS corresponding to 30 kHz, tn3 pis for the SCS corresponding to 60 kHz, and so on.

[0314] In an example, time duration 2206 may be determined based on (or may be associated with) the bandwidth, or a range of bandwidths. The bandwidth may be associated with wireless device 2220 and / or node 2240 (e.g., a base station). For example, wireless device 2220 may be configured with the bandwidth for a radio procedure (e.g., a radio access communication, a measurement procedure, a positioning procedure, etc). The bandwidth may be expressed in terms of frequency units (e.g., K11 MHz), or a number of resource blocks (e.g., a K12 number of resource blocks). For example, capability information 2204 may indicate time duration 2206 associated with the bandwidth, or the range of the bandwidths. For example, capability information 2204 may indicate time durations 2206 as tb1 pis for the bandwidth up to 20 MHz, tb2 pis for the bandwidth larger than 20 MHz and up to 100 MHz, tb3 pis for the bandwidth larger than 100 MHz and up to 200 MHz, and so on.

[0315] In an example, time duration 2206 may be determined based on (or may be associated with) the frequency band. The frequency band may be identified by an identifier (e.g., n1 , n2, n3, and so on). The identifier (e.g., n1 , n2, n3, etc.) may also be referred to as a band indicator, a band identifier, a bandnumber, etc. The frequency band may also be referred to as a band, an operating band, an operating frequency band, a transmission band, etc. For example, wireless device 2220 may use the frequency band for a radio procedure In an example, the radio procedure may comprise communications between wireless device 2220 and node 2240 (e.g., a base station). In an example, the radio procedure may comprise a measurement procedure, a radio link procedure, or a positioning procedure. For example, capability information 2204 may indicate time duration 2206 associated with the frequency band. For example, capability information 2204 may indicate time durations 2206 as tf1 pis for a frequency band # 1 (e.g., n 1 ), tf2 pis for a frequency band # 2 (e.g., n2), tf3 pis for a frequency band # 3 (e.g., n3), and so on.

[0316] In an example, time duration 2206 may be determined based on (or may be associated with) the frequency range. For example, the frequency range may be a frequency range # 1 (FR1) or a frequency range # 2 (FR2). The frequencies within FR1 may be lower than frequencies in FR2. The FR2 may also be referred to as a millimeter wave frequency range or simply a millimeter wave frequency range. In an example, FR1 may include frequencies from 410 MHz up to 7125 MHz. In an example, FR2 may include frequencies from 24.25 GHz up to 71 GHz. For example, wireless device 2220 may transmit signals and / or receive signals on a carrier frequency, which may belong to FR1 or FR2. For example, capability information 2204 may indicate time durations 2206 associated with FR1 and FR2. For example, capability information 2204 may indicate time durations 2206 as tr1 pis for FR1 and tr2 pis for FR2.

[0317] In an example, time duration 2206 may be determined based on (or may be associated with) the signal direction. A signal transmitted by wireless device 2220 may be referred to as an uplink signal (or an uplink transmission or signal transmission). A signal received by wireless device 2220 may be referred to as a downlink signal (or a downlink reception or a signal reception). For example, wireless device 2220 may transmit signals and / or receive signals for a radio procedure. Wireless device 2220 may perform the LCM for the radio procedure. For example, capability information 2204 may indicate time durations 2206 associated with the signal direction of the radio procedure. For example, capability information 2204 may indicate time durations 2206 as ts1 pis for performing the LCM for radio procedure on the uplink signal and ts2 pis for performing the LCM for the radio procedure on the downlink signal.

[0318] In an example, time duration 2206 may be determined based on (or may be associated with) the multicarrier (MC) configuration. The MC configuration may be associated with a multicarrier (MC) operation. Wireless device 2220 may transmit and / or receive signals based on (or using) the MC operation (e.g., to increase data rate) For example, wireless device 2220 may receive, from node 2240, information about the MC configuration (e.g., via an RRC message). The MC operation may be a carrier aggregation (CA), a multi-connectivity (MuC), or a dual connectivity (DC). The MC configuration may be referred to as a number of serving cells of wireless device 2220 when wireless device 2220 is configured with the MC operation. The MC configuration may include with two or more serving cells. For example, the CA may include aprimary cell (PCell) and one or more secondary cells (SCells). For example, the DC may include at least a PCell in a master cell group (MCG) and at least a primary secondary cell (PSCell) in a secondary cell group (SCG). The DC may further include one or more SCells in the MCG and / or one or more SCells in the SCG. The PCell or the PSCell may also be referred to as a special cell (spCell) . The spCell, PCell, PSCell, or SCell may be referred to as the serving cell. For example, capability information 2204 may indicate time durations 2206 associated with a number of serving cells included in the MC configuration of the MC operation of wireless device 2220. For example, capability information 2204 may indicate time durations 2206 as tm1 pis for the MC configuration including two serving cells, tm2 pis for the MC configuration including three serving cells, tm3 pis for the MC configuration including four serving cells, and so on. In another example, capability information 2204 may indicate time durations 2206 as tm4 pis for the MC configuration including up to three serving cells and tm4 pis for the MC configuration including more than three serving cells.

[0319] In an example, time duration 2206 may be determined based on (or may be associated with) the multi-antenna configuration. The multi-antenna configuration may be associated with a multi-antenna operation. For example, wireless device 2220 may transmit and / or receive signals based on (or using) the multi-antenna operation (e.g., to increase data rate). For example, wireless device 2220 may receive, from node 2240, information about the multi-antenna configuration (e.g., via an RRC message). The multiantenna configuration may include a number of receive antennas and / or a number of transmit antennas. In an example, time duration 2206 may be determined based on the number of the received antennas and / or the number of the transmit antennas comprised in the multi-antenna configuration. For example, capability information 2204 may indicate time duration 2206 as ta1 pis based on the received antennas being larger than a first antenna threshold (HA1) and / or the number of the transmit antennas being larger than a second antenna threshold (HA2). In another example, capability information 2204 may indicate time duration 2206 as ta2 pis based on the received antennas being less than a third antenna threshold (HA3) and / or the number of the transmit antennas being less than a four antenna threshold (HA4).

[0320] In an example, time duration 2206 may be determined based on (or may be associated with) the power class. The power class may be associated with wireless device 2220. The power class may also be referred to as (or correspond to) a nominal power, a maximum output power, a maximum output power, etc. Wireless device 2220 may transmit signals based on the power class supported by wireless device 2220. Wireless device 2220 may support (or be capable of) one or more power classes. Examples of the power class may be a power class 1 (PC1), a power class 2 (PC2), a power class 1 .5 (PC1 .5), a power class 3 (PC3), or a power class 5 (PC5). In an example, PC1 , PC1 .5, PC2, PC3, and PC5 may correspond to 31 dBm, 29 dBm, 26 dBm, 23 dBm, and 20 dBm respectively. For example, capability information 2204 may indicate time durations 2206 as tp1 pis, tp2 pis, tp3 pis, tp4 pis, and tp5 pis corresponding to PC1 , PC1 .5,PC2, PC3, and PC5 respectively. In an example, capability information 2204 may indicate time duration 2206 as tp6 pis based on the power class being larger than a first power class threshold (HP1). In another example, capability information 2204 may indicate time duration 2206 as tp7 pis based on the power class being less than or equal to a second power class threshold (HP2).

[0321] In an example, time duration 2206 may be determined based on (or may be associated with) the beam management. Two or more beams may be associated with (or operate based on) the beam management. A beam may be (or correspond to) a signal (e.g., a reference signal such as an SSB, a CSI- RS, etc., or a data channel such as a PDSCH, a PDCCH, a PUSCH, or a PUCCH, etc.). Wireless device 2220 may transmit the two more beams and / or receive the two more beams. Examples of the beam management may be a common beam management (CBM), an independent beam management (IBM), etc. Wireless device 2220 may support (or be capable of) the CBM and / or the IBM for transmitting and / or receiving beams. For example, wireless device 2220 may use (or apply) a single transceiver to transmit the two or more beams and / or receive the two or more beams based on the CBM. For example, wireless device 2220 may use (or apply) at least two transceivers to transmit the two or more beams and / or receive the two or more beams based on the IBM. For example, time duration 2206 supported by wireless device 2220 may depend on (or may be associated with) the CBM or the IBM. In an example, capability information 2204 may indicate time duration 2206 as tb1 pis associated with (or corresponding to) the CBM. In another example, capability information 2204 may indicate time duration 2206 as tb2 pis associated with (or corresponding to) the IBM.

[0322] In an example, time duration 2206 may be determined based on (or may be associated with) the mobility state. The mobility state may correspond to (or referred to as) a speed of wireless device 2220. The speed may be defined (or expressed) in terms of a Doppler frequency (e.g., S11 Hertz) or distance per unit time (e.g., S12 km / hour). In an example, capability information 2204 may indicate time duration 2206 as tm1 pis based on the speed being larger than a first speed threshold (HS1). In another example, capability information 2204 may indicate time duration 2206 as tm2 pis based on the speed being less than a second speed threshold (HS2). In another example, capability information 2204 may indicate time duration 2206 as tm3 pis based on wireless device 2220 being stationary (e.g., the speed is zero). In another example, capability information 2204 may indicate time duration 2206 as tm4 pis based on wireless device 2220 not being stationary (e.g., the speed is larger than zero).

[0323] In an example, time duration 2206 may be (or may correspond to) a switching time for a transceiver of wireless device 2220. The switching time may also be referred to as a processing time, a tuning time, an radio frequency (RF) switching time, an RF tuning time, or an RF reconfiguration time. The transceiver may also be referred to as a receiver and / or a transmitter.

[0324] In an example, wireless device 2220 may trigger (or initiate) the LCM procedure for the radio procedure. Wireless device 2220 may perform the LCM procedure based on the triggering (or initiation) of the LCM procedure. In an example, wireless 2220 may trigger (e.g., autonomously) the LCM procedure based on one or more criteria (as described below). The one or more criteria may also be referred to as triggering criteria.

[0325] In an example, the one or more criteria for triggering the LCM procedure may be pre-determined. In an example, wireless device 2220 may receive a configuration message comprising / indicating the one or more criteria. In an example, wireless device 2220 may receive, from node 2240, the configuration message. In an example, wireless device 2220 may receive, from node 2240 (e.g., a base station), the configuration message by an RRC message. In an example, wireless device 2220 may receive, from node 2240 (e.g., a location server), the configuration message by an LTE Positioning Protocol (LPP) message. In an example, wireless device 2220 may receive, from node 2240 (e.g., a core network node), the configuration message by a Non-Access Stratum (NAS) message (e.g., a next generation application protocol (NGAP).

[0326] In an example, one of the one or more criteria for triggering the LCM procedure may be one or more radio channel characteristics (or measurements). Examples of the one or more radio channel characteristics may be a Doppler frequency, a Doppler spread, a channel delay spread, a channel coherence time, etc. In an example, wireless device 2220 may estimate the one or more radio channel characteristics based on a signal. In an example, the signal may comprise a reference signal (RS). In an example, the RS may comprise an SSB, a CSI-RS, a DMRS, etc. In an example, wireless device 2220 may estimate the one or more radio channel characteristics by measuring the signal. For example, wireless device 2220 may trigger the LCM procedure based on the Doppler frequency (Df) of wireless device 2220 being below a first Doppler threshold (TD1). For example, wireless device 2220 may trigger the LCM procedure based on the Doppler frequency (Df) estimated by wireless device 2220 being above a second Doppler threshold (TD2). For example, wireless device 2220 may trigger the LCM procedure based on the channel delay spread estimated by wireless device 2220 being below a first delay spread threshold (TD1). For example, wireless device 2220 may trigger the LCM procedure based on the channel delay spread estimated by wireless device 2220 being above a second delay spread threshold (TSD2). For example, wireless device 2220 may trigger the LCM procedure based on the channel coherence time estimated by wireless device 2220 being below a first coherence time threshold (TCC1). For example, wireless device 2220 may trigger the LCM procedure based on the channel coherence time estimated by wireless device 2220 being above a second coherence time threshold (TCC2). In an example, TD1 , TD2, TD1 , TSD2, TCC1 and TCC2 may be pre-determined. In an example, wireless device 2220 may receive a configurationcomprising TD1 , TD2, TD1 , TSD2, TCC1 and TCC2. Wireless device 2220 may receive the configuration by an RRC message.

[0327] In an example, one of the one or more criteria for triggering the LCM procedure may be a location of wireless device 2220. The location of wireless device 2220 may also be referred to as a position or a geographic location or a footprint of wireless device 2220. For example, wireless device 2220 may determine the location of wireless device 2220 based on a positioning measurement. For example, wireless device 2220 may measure a positioning signal to obtain the positioning measurement. For example, the positioning signal may comprise one or more of a Positioning Reference Signal (PRS), Sounding Reference Signal (SRS) etc. For example, wireless device 2220 may receive a location information from node 2240 (e.g., a location server). For example, wireless device 2220 may determine the location of wireless device 2220 based on the received location information. For example, the location of wireless device 2220 may change over time. For example, wireless device 2220 may trigger the LCM procedure if the location of wireless device 2220 changes. For example, wireless device 2220 may trigger the LCM procedure based on a distance between a current location and a previous location of wireless device 2220. For example, wireless device 2220 may trigger the LCM procedure based on a distance between the current and the previous location of wireless device 2220 being more than a first distance threshold (TL1). In an example, TL1 may be pre-determined. In an example, wireless device 2220 may receive a configuration comprising TL1 . wireless device 2220 may receive the configuration by an RRC or an LPP message.

[0328] As another example, the LCM procedure may comprise a switching from an AI / ML model to a measurement procedure or a switching from a measurement procedure to an AI / ML model. In an example, wireless device 2220 may trigger a switching from an AI / ML model to a measurement procedure based on a distance between the current and the previous locations of wireless device 2220 being more than TL1 . In an example, wireless device 2220 may trigger a switching from a measurement procedure to an AI / ML model based on a distance between the current location and the previous location of wireless device 2220 being less than or equal to TL1 .

[0329] In an example, one of the one or more criteria for triggering the LCM procedure may be a downlink signal quality. In an example, a wireless device may estimate a downlink signal quality (DSQ) based on a reference signal (RS). In an example, the RS may comprise an SSB, a CSI-RS, a DMRS, etc. In an example, wireless device 2220 may measure on the RS to estimate a signal quality. In an example, the signal quality may comprise a signal to noise ratio (SNR), a signal to noise and interference radio (SINR), a channel quality indicator (CQI), a reference signal received quality (RSRQ) etc. In an example, a wireless device may trigger an LCM procedure based on a DSQ being below a first DSQ threshold (TDQ1). In an example, a wireless device may trigger an LCM procedure based on a DSQ being above a second DSQthreshold (TDQ2). In an example, TDQ1 and TDQ2 may be pre-determined. In an example, wireless device 2220 may receive a configuration comprising TDQ1 and TDQ2. Wireless device 2220 may receive the configuration by an RRC message.

[0330] The LCM procedure may comprise a switching of an AI / ML model from a first AI / ML (AI / ML1 ) model to a second AI / ML (AI / ML2) model or a switching of an AI / ML model from AI / ML2 model to AI / ML1 model. In an example, AI / ML1 may be trained for a scenario based on a DSQ estimated by a wireless device being above TDQ2. In an example, AI / ML1 may be suitable for a scenario based on a SQ estimated by wireless device 2220 being below TDQ1 . In an example, wireless device 2220 may trigger a switching of an AI / ML model from AI / ML1 to AI / ML2 based on a DSQ estimated by wireless device 2220 being below TDQ1 . In an example, wireless device 2220 may trigger a switching of an AI / ML model from AI / ML2 to AI / ML1 based on a DSQ estimated by wireless device 2220 being above TDQ2.

[0331] In another example, one of the one or more criteria for triggering the LCM procedure may be an HARQ ACK / NACK. Wireless device 2220 may transmit, to a base station, the HARQ ACK / NACK message in response to receiving, from node 2240 (e.g., a base station), a data channel e.g. PDSCH. In an example, wireless device 2220 may transmit, to the base station, an ACK in response to correctly decoding the data channel. In an example, wireless device 2220 may transmit, to the base station, a NACK in response to incorrectly decoding the data channel. In an example, a wireless device may trigger an LCM procedure based on a number of ACKs and / or a number of NACKs transmitted by wireless device 2220 during a first HARQ time period (Tp1). In an example, wireless device 2220 may trigger an LCM procedure based on a number of ACKs during Tp1 being below a first ACK threshold (TAK1). In an example, wireless device 2220 may trigger an LCM procedure based on a number of ACKs during Tp1 being above a second ACK threshold (TAK2). In an example, a wireless device may trigger an LCM procedure based on a number of NACKs during Tp1 being below a first NACK threshold (TNK1). In an example, wireless device 2220 may trigger an LCM procedure based on a number of NACKs during Tp 1 being above a second NACK threshold (TNK2). In an example, TAK1 , TAK2, TNK1 and TNK2 may be pre-determined. In an example, wireless device 2220 may receive a configuration comprising TAK1 , TAK2, TNK1 and TNK2. Wireless device 2220 may receive the configuration by an RRC message.

[0332] In another example, wireless device 2220 may receive, from node 2240, an indication for starting the LCM procedure for the radio procedure. Wireless device 2220 may trigger the LCM procedure based on the indication. Wireless device 2220 may perform the LCM procedure based on the triggering (or initiation) of the LCM procedure. Wireless device 2220 may receive the indication via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message.

[0333] In another example, wireless device 2220 may transmit, to node 2240, a request for performing the LCM procedure for the radio procedure. Wireless device 2220 may trigger the LCM procedure based on therequest. Wireless device 2220 may perform the LCM procedure based on the triggering (or initiation) of the LCM procedure. Wireless device 2220 may transmit the request via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message.

[0334] In another example, wireless device 2220 may transmit, to node 2240, a request for performing the LCM procedure for the radio procedure. Wireless device 2220 may receive, from node 2240, a response message corresponding to the request. Wireless device 2220 may trigger the LCM procedure based on the response message. Wireless device 2220 may perform the LCM procedure based on the triggering (or initiation) of the LCM procedure. Wireless device 2220 may transmit the request for performing the LCM procedure via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message. Wireless device 2220 may receive the response message via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message.

[0335] In another example, wireless device 2220 may transmit, to node 2240, a request for starting the LCM procedure for the radio procedure. Wireless device 2220 may receive, from node 2240, an indication for starting the LCM procedure for the radio procedure. Wireless device 2220 may trigger the LCM procedure based on the indication. Wireless device 2220 may perform the LCM procedure based on the triggering (or initiation) of the LCM procedure. Wireless device 2220 may transmit the request for starting the LCM procedure via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message. Wireless device 2220 may receive the indication for starting the LCM procedure via a MAC CE, a DCI, an RRC, an LPP, or an NGAP message.

[0336] In an example, time duration 2206 may correspond to (or may be equal to) a duration of the interruption of the communications. In another example, the duration of the interruption may be determined based on time duration 2206.

[0337] FIG. 23 illustrates an example of communications 2300 between a wireless device 2320 and a base station 2340 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 23 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , and / or 22.

[0338] As illustrated in FIG. 23, wireless device 2320 may start an LCM procedure 2302 (e.g., LCM procedure 1800 in FIG. 18). Wireless device 2320 may start LCM procedure 2302 based on the triggering of the LCM procedure according to the example embodiments in FIG. 22 (e.g., the triggering of the LCM procedure). Wireless device 2320 may interrupt signals over an interruption duration 2304. For example, interruption of communications between wireless device 2320 and base station 2340 may occur over interruption duration 2304. For example, wireless device 2320 may not transmit or receive any signal over interruption duration 2304.

[0339] Communications 2306 between wireless device 2320 and base station 2340 may start (or resume) after interruption duration 2304. For example, wireless device 2320 may receive a downlink signal 2308and / or transmit an uplink signal 2310 during communications 2306. Downlink signal 2308 may be a downlink reference signal and / or a downlink channel. Uplink signal 2310 may be an uplink reference signal and / or an uplink channel.

[0340] In an example, a downlink reference signal may be a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Channel Status Information-RS (CSI-RS), Demodulation Reference Signal (DMRS), Synchronization Signal / PBCH block (SSB), a Positioning Reference Signal (PRS), a tracking reference signal (TRS), etc. In an example, an uplink reference may be a Demodulation Reference Signal (DMRS), a Sounding Reference Signal (SRS), etc.

[0341] The uplink or the downlink physical channel may include higher layer information. In an example, the higher layer information may include (or comprise) a logical channel, and / or a transport channel. Examples of the logical channel may be a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Dedicated Control Channel (DCCH), a Multi-cast Control Channel (MCCH), a Dedicated Traffic Channel (DTCH), a Multicast Traffic Channel (MTCH) etc. In an example, a downlink physical channel may be a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Broadcast Channel (PBCH), etc. In an example, an uplink physical channel may be a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), etc.

[0342] Referring to FIG. 23, interruption duration 2304 may start based on (or due to, caused by, or triggered by) LCM procedure 2302. In an example, interruption duration 2304 may start anytime during LCM procedure 2302. In an example, interruption duration 2304 may start after the start of LCM procedure 2302. In an example, interruption duration 2304 may start from the start of a first time resource (e.g., a symbol, a slot, a subframe, a frame, etc) occurring after the start of LCM procedure 2302. In another example, interruption duration 2304 may start from the end of a time resource (e.g., a symbol, a slot, a subframe, a frame, etc) in which LCM procedure 2302 may start. In an example, interruption duration 2304 may correspond to (or equal to) time duration 2206 (e.g., in FIG. 22). In another example, interruption duration 2304 may be determined based on time duration 2206 (e.g., in FIG. 22). For example, interruption duration 2304 may be longer than time duration 2206 (e.g., in FIG. 22).

[0343] FIG. 24A illustrates an example of an interruption duration 2410 and a time duration 2412 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 24A may be combined with the features previously discussed with reference to Fl Gs. 17, 18, 19, 20, 21 , 22, and / or 23.

[0344] As illustrated in FIG. 24A, interruption duration 2410 corresponds to the time duration 2412. For example, a wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may interrupt communications (e.g., communications 2306 in FIG. 23) over interruption duration 2410 based on the LCM procedure (e.g., LCM procedure 1800 in FIG. 18). Time duration 2412 is according to the exampleembodiments in FIG. 22 (e.g., time duration 2206). For example, capability information 2204 (e.g., in FIG. 22) may indicate time duration 2412.

[0345] FIG. 24B illustrates an example of an interruption duration 2420, a time duration 2422, and an offset 2424 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 24B may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, and / or 24 A.

[0346] As illustrated in FIG. 24B, interruption duration 2420 may be determined based on time duration 2422 and an offset 2424. For example, interruption duration 2420 may be a sum of time duration 2422 and offset 2424. For example, a wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may interrupt communications (e.g., communications 2306 in FIG. 23) over interruption duration 2420 based on the LCM procedure (e.g., LCM procedure 1800 in FIG. 18).

[0347] Time duration 2422 is according to the example embodiments in FIG. 22 (e.g., time duration 2206). For example, capability information 2204 (e.g., in FIG. 22) may indicate time duration 2422. In an example, offset 2424 may be pre-defined. In an example, offset 2424 may be a processing time, or an implementation margin of the wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23). In an example, offset 2424 may depend on a numerology. The numerology is according to the example embodiments in FIG. 22 (e.g., the numerology).

[0348] In another example, offset 2424 may be applied (or added) to time duration 2422 (in time units) to determine interruption duration 2420 (in time resources). For example, time duration 2422 may be indicated (e.g., in capability information 2204 in FIG. 22) in one or more time units (e.g., in Ty1 pis). Interruption duration 2420 may be determined (or derived, transformed, or translated) in one or more time resources (e.g., Ty2 slots) based on time duration 2422 and offset 2424.

[0349] FIG. 25 illustrates an example of an LCM-SwitchingTime 2510 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 25 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, 24A, and / or 24B.

[0350] FIG. 25 illustrates an example of an indication of a switching time (e.g., time duration 2206 in FIG. 22, time duration 2410 in FIG. 24A, and / or time duration 2422 in FIG. 24B) for an LCM procedure (e.g., LCM procedure 1800 in FIG. 18) supported by a wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23).

[0351] As an example, the wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may support one of the values included in LCM-SwitchingTime (e.g., in FIG. 25) for the switching time based on the LCM procedure. The wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may include the supported value of LCM-SwitchingTime in a capabilityinformation (e.g., in capability information 2204 in FIG. 22). LCM-SwitchingTime 2510 may be an RRC or an LPP message.

[0352] FIG. 26 illustrates an example of an LCM-SwitchingTime 2610 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 26 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, 24A, 24B, and / or 25.

[0353] FIG. 26 illustrates an example of an indication of a downlink and an uplink switching times (e.g., time duration 2206 in FIG. 22, time duration 2410 in FIG. 24A, and / or time duration 2422 in FIG. 24B) for an LCM procedure (e.g., LCM procedure 1800 in FIG. 18) supported by a wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23).

[0354] As an example, the wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may support one of the values included in LCM-SwitchingTimeDL (e.g., in FIG. 26) for the downlink switching time based on the LCM procedure. The wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may support one of the values included in LCM- SwitchingTimeUL (e.g., in FIG. 26) for the uplink switching time based on the LCM procedure. The wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may include the supported values of LCM-SwitchingTimeDL and / or LCM-SwitchingTimeUL in a capability information (e.g., in capability information 2204 in FIG. 22). LCM-SwitchingTime 2610 may be an RRC or an LPP message.

[0355] FIG. 27 illustrates an example of an interruption due to LCM procedure 2710 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 27 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, 24A, 24B, 25, and / or 26.

[0356] FIG. 27 illustrates an example of a definition of an interruption duration (e.g., interruption duration 2304 in FIG. 23, interruption duration 2410 in FIG. 24A, and / or interruption duration 2420 in FIG. 24B) over which a wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) may interrupt communications with a base station (e.g., base station 2340 in FIG. 23) based on (or due to) the LCM procedure (e.g., LCM procedure 1800 in FIG. 18).

[0357] As an example, the wireless device (e.g., wireless device 2220 in FIG. 22 or wireless device 2320 in FIG. 23) and / or a node (e.g., node 2240 in FIG. 22, base station 2340 in FIG. 23) may determine the interruption duration in number of slots based on a switching time (e.g., LCM-SwitchingTime 2510 in FIG. 25 or LCM-SwitchingTime 2610 in FIG. 26) and a numerology (e.g., an NR slot length in FIG. 27).

[0358] FIG. 28 illustrates an example of an updated capability transfer procedure 2710 as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 28 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, 24A, 24B, 25, 26, and / or 27.

[0359] As illustrated in FIG. 28, a wireless device 2820 may transmit, to node 2840, a capability information 2802. Capability information 2802 may include an updated time duration 2804. Updated time duration 2804 may be an update to (or a modification of or change in) time duration 2206 (e.g., in FIG. 22).

[0360] Node 2840 is according to the example embodiments in FIG. 22 (e.g., node 2240) and / or in FIG. 23 (e.g., base station 2340).

[0361] Wireless device 2820 may transmit capability information 2802 according to the example embodiments in FIG. 22 (e.g., via an RRC, an LPP, or an NGAP message).

[0362] Updated time duration 2804 is according to the example embodiments in FIG. 22 (e.g., time duration 2206), in FIG. 24A (e.g., time duration 2410), in FIG. 24A (e.g., time duration 2422), in FIG. 25 (e.g., LCM-SwitchingTime 2510), and / or in FIG. 26 (e.g., LCM-SwitchingTime 2610).

[0363] In an example, updated time duration 2804 may be determined (or time duration 2206 in FIG. 22 may be updated, modified, transformed, or changed to updated time duration 2804) based on a change in one or more conditions. The one or more conditions are according to the example embodiments in FIG. 22 (e.g., the one or more conditions).

[0364] Referring to FIG. 28, wireless device 2820 may receive, from node 2840, a configuration message indicating change in (or modification of) the one or more conditions. Wireless device 2820 may modify (or update) the one or more conditions based on the configuration message. In an example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the bandwidth. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the numerology. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the power class of wireless device 2820. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the multi-antenna configuration of wireless device 2820. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the multicarrier configuration of wireless device 2820. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the mobility state of wireless device 2820. In another example, wireless device 2820 may transmit capability information 2802 including updated time duration 2804 based on the change in the beam management (e.g., from the CBM to the IBM, or vice versa)

[0365] FIG. 29 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 29 may be combined with the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21 , 22, 23, 24A, 24B, 25, 26, 27, and / or 28.

[0366] Referring to FIG. 29, process 2900 comprises a step 2910 of receiving, by a wireless device, a request for a capability of the wireless device. Process 2900 further comprises a step 2920 of transmitting, based on the request, a capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure.

[0367] Additional aspects, with examples, of step 2910, step 2920, and process 2900 are discussed below. Each of the additional aspects, and examples, below may be considered an embodiment. Each aspect of the embodiments may be combined with, or substituted for, the aspects of the embodiment of process 2900 illustrated in FIG. 29, such as step 2910 and / or step 2920. Furthermore, each of the additional aspects and examples below may be combined with each other.

[0368] In an example, process 2900 further comprises triggering the LCM procedure for the radio procedure; and performing the LCM procedure based on the triggering.

[0369] In an example, process 2900 further comprises receiving, from a node, an indication for starting the LCM procedure, wherein triggering the LCM procedure for the radio procedure is based on the indication.

[0370] In an example, process 2900 further comprises transmitting, to a node, a request for performing an LCM procedure, wherein triggering the LCM procedure is based on the request.

[0371] In an example, process 2900 further comprises transmitting, to a node, a request for performing an LCM procedure; and receiving, from the node, a response message corresponding to the request, wherein triggering the LCM procedure is based on the response message.

[0372] In an example, process 2900 further comprises transmitting, to a node, a request for starting an LCM procedure; and receiving, from the node, an indication for starting the LCM procedure based on the request, wherein triggering the LCM procedure is based on the indication.

[0373] In an example, the interruption of communications occurs with a base station.

[0374] In an example, process 2900 further comprises communicating with a base station based on the LCM procedure after the interruption.

[0375] In an example, communicating with the base station comprises transmitting an uplink signal to the base station and / or receiving a downlink signal from the base station.

[0376] In an example, time duration is determined based on at least one of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

[0377] In an example, the time duration is a switching time for a transceiver.

[0378] In an example, the time duration is equal to a duration of the interruption.

[0379] In an example, a duration of the interruption is determined based on the time duration and an offset.

[0380] In an example, the LCM procedure comprises developing, deploying, managing, and / or maintaining the radio procedure.

[0381] In an example, the LCM procedure comprises an identification of the radio procedure, a selection of the radio procedure, an activation of the radio procedure, a deactivation of the radio procedure, a fallback from the radio procedure to a measurement procedure, a switch from the radio procedure to another radio procedure, a release of the radio procedure, a monitoring of the radio procedure, and / or a modification of one or more parameters of the radio procedure.

[0382] In an example, the radio procedure comprises a radio access communication (RAC), a measurement procedure, a positioning procedure, a link recovery procedure, and / or a radio link procedure.

[0383] In an example, the radio procedure comprises a model.

[0384] In an example, the model comprises an artificial intelligence (Al) and / or machine language (ML) (AI / ML) model. In another example, the model is an AI / ML model.

[0385] In an example, process 2900 further comprises receiving, from a node, the request for the capability; and transmitting, to the node, the capability message.

[0386] In an example, the node is a base station, a gNB, a gNB control unit (gNB-CU), a location server, or a core network node.

[0387] In an example, FR1 comprises frequences from 410 MHz to 7125 MHz.

[0388] In an example, FR2 comprises frequences from 24 GHz to 71 GHz.

[0389] In an example, process 2900 further comprises transmitting a second capability message indicating an update to the time duration.

[0390] In an example, transmitting the second capability message is based on at least one of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

[0391] FIG. 30 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 30 may be combined with the features previously discussed with reference to FIG. 29.

[0392] Referring to FIG. 30, process 3000 comprises a step 3010 of transmitting, by a node, a request for a capability of a wireless device. Process 3000 further comprises a step 3020 of receiving, based on the request, a capability message indicating a time duration associated with an interruption of communications that occurs based on a life cycle management (LCM) procedure.

[0393] Additional aspects, with examples, of step 3010, step 3020, and process 3000 are discussed below. Each of the additional aspects, and examples, below may be considered an embodiment. Each aspect of the embodiments may be combined with, or substituted for, the aspects of the embodiment ofprocess 3000 illustrated in FIG. 30, such as step 3010 and / or step 3020. Furthermore, each of the additional aspects and examples below may be combined with each other.

[0394] In an example, process 3000 further comprises triggering the LCM procedure for the radio procedure; and performing the LCM procedure based on the triggering.

[0395] In an example, process 3000 further comprises transmitting, to the wireless device, an indication for starting the LCM procedure, wherein triggering the LCM procedure for the radio procedure is based on the indication.

[0396] In an example, process 3000 further comprises receiving, from the wireless device, a request for performing an LCM procedure, wherein triggering the LCM procedure is based on the request.

[0397] In an example, process 3000 further comprises receiving, from the wireless device, a request for performing an LCM procedure; and transmitting, to the wireless device, a response message corresponding to the request, wherein triggering the LCM procedure is based on the response message.

[0398] In an example, process 3000 further comprises receiving, from the wireless device, a request for starting an LCM procedure; and transmitting, to the wireless device, an indication for starting the LCM procedure based on the request, wherein triggering the LCM procedure is based on the indication.

[0399] In an example, the interruption of communications occurs with a base station.

[0400] In an example, process 3000 further comprises communicating with a base station based on the LCM procedure after the interruption.

[0401] In an example, communicating with the base station comprises transmitting an uplink signal to the base station and / or receiving a downlink signal from the base station.

[0402] In an example, time duration is determined based on at least one of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

[0403] In an example, the time duration is a switching time for a transceiver.

[0404] In an example, the time duration is equal to a duration of the interruption.

[0405] In an example, a duration of the interruption is determined based on the time duration and an offset.

[0406] In an example, the LCM procedure comprises developing, deploying, managing, and / or maintaining the radio procedure.

[0407] In an example, the LCM procedure comprises an identification of the radio procedure, a selection of the radio procedure, an activation of the radio procedure, a deactivation of the radio procedure, a fallback from the radio procedure to a measurement procedure, a switch from the radio procedure toanother radio procedure, a release of the radio procedure, a monitoring of the radio procedure, and / or a modification of one or more parameters of the radio procedure.

[0408] In an example, the radio procedure comprises a radio access communication (RAC), a measurement procedure, a positioning procedure, a link recovery procedure, and / or a radio link procedure.

[0409] In an example, the radio procedure comprises a model.

[0410] In an example, the model comprises an artificial intelligence (Al) and / or machine language (ML) (AI / ML) model. In another example, the model is an AI / ML model.

[0411] In an example, process 3000 further comprises transmitting, to the wireless device, the request for the capability; and transmitting, to the node, the capability message.

[0412] In an example, the node is a base station, a gNB, a gNB control unit (gNB-CU), a location server, or a core network node.

[0413] In an example, FR1 comprises frequences from 410 MHz to 7125 MHz.

[0414] In an example, FR2 comprises frequences from 24 GHz to 71 GHz.

[0415] In an example, process 3000 further comprises receiving a second capability message indicating an update to the time duration.

[0416] In an example, receiving the second capability message is based on at least one of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

Claims

CLAIMS1. A method comprising: receiving, by a wireless device from a node, a request for information about a capability of the wireless device; based on the request, transmitting, to the node, a first capability message indicating a time duration associated with an interruption of communications with a base station, wherein: the interruption is based on a life cycle management (LCM) procedure; and the LCM procedure comprises switching between performing a signal measurement and predicting a signal measurement based on an artificial intelligence (Al) / machine learning (ML) model; and transmitting, to the node, a second capability message indicating an update to the time duration, based on a change in one or more radio configuration parameters of the wireless device.

2. A method comprising transmitting, by a wireless device to a node, a capability message indicating a time duration associated with an interruption of communications with a base station, wherein the interruption is based on a life cycle management (LCM) procedure.

3. The method of claim 2, wherein the LCM procedure comprises switching between performing a signal measurement and predicting a signal measurement based on an artificial intelligence (Al) / machine learning (ML) model.

4. The method of claim 2 or 3, comprising receiving, by the wireless device from the node, a request for information about a capability of the wireless device, wherein the capability message is transmitted by the wireless device to the node, based on the request.

5. The method of any one of claims 2-4, comprising transmitting, to the node, a second capability message indicating an update to the time duration, based on a change in one or more radio configuration parameters of the wireless device.

6. The method of any one of claims 3-5, wherein the interruption of the communications with the base station occurs during a time interval, including the time duration, during which the wireless device switches between the performing a signal measurement and the predicting a signal measurement based on the AI / ML model.

7. The method of any of claims 2-6, comprising communicating with the base station based on the LCM procedure, after the interruption.

8. The method of claim 7, wherein the communicating with the base station comprises: transmitting an uplink signal to the base station; and / or receiving a downlink signal from the base station.

9. The method of any of claims 2-8, wherein the time duration is determined based on one or more of:an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

10. The method of any of claims 2-9, wherein the time duration is a switching time for switching a transceiver of the wireless device.

11. The method of any of claims 2-10, wherein the time duration is equal to a duration of the interruption.

12. The method of any of claims 2-11, wherein a duration of the interruption is determined based on the time duration and an offset.

13. The method of any of claims 2-12, wherein the LCM procedure comprises developing, deploying, managing, or maintaining a radio procedure14. The method of claim 13, wherein the LCM procedure comprises one or more of: an identification of the radio procedure; a selection of the radio procedure; an activation of the radio procedure; a deactivation of the radio procedure; a fallback from the radio procedure to a measurement procedure; a switch from the radio procedure to another radio procedure; a release of the radio procedure; a monitoring of the radio procedure; and / or a modification of one or more parameters of the radio procedure.

15. The method of any of claims 2-14, wherein the radio procedure comprises a radio access communication (RAC), a measurement procedure, a positioning procedure, a link recovery procedure, or a radio link procedure.

16. The method of any of claims 2-15, wherein the radio procedure comprises using a model.

17. The method of claim 16, wherein the model comprises an AI / ML model.

18. The method of any one of claims 5-17, wherein the second capability message is transmitted, based on one or more of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1 ); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and a mobility state.

19. A method comprising: transmitting, by a node to a wireless device, a request for information about a capability of the wireless device; based on the request, receiving, from the node, a first capability message indicating a time duration associated with an interruption of communications with a base station, wherein: the interruption is based on a life cycle management (LCM) procedure; and the LCM procedure comprises switching between performing a signal measurement and predicting a signal measurement based on an artificial intelligence (Al) / machine learning (ML) model; and receiving, from the node, a second capability message indicating an update to the time duration, based on a change in one or more radio configuration parameters of the wireless device.

20. A method comprising receiving, by a node from a wireless device, a capability message indicating a time duration associated with an interruption of communications with a base station, wherein the interruption is based on a life cycle management (LCM) procedure.21 . The method of claim 20, wherein the LCM procedure comprises switching between performing a signal measurement and predicting a signal measurement based on an artificial intelligence (Al) / machine learning (ML) model.

22. The method of claim 20 or 21, comprising transmitting, by the node to the wireless device, a request for information about a capability of the wireless device, wherein the capability message is received by the node from the wireless device, based on the request.

23. The method of any one of claims 20-22, comprising receiving, from the wireless device, a second capability message indicating an update to the time duration, based on a change in one or more radio configuration parameters of the wireless device.

24. The method of any one of claims 21-23, wherein the interruption of the communications with the base station occurs during a time interval, including the time duration, during which the wireless device switches between the performing a signal measurement and the predicting a signal measurement based on the AI / ML model.

25. The method of any of claims 20-24, wherein the wireless device is configured to communicate with the base station based on the LCM procedure, after the interruption.

26. The method of claim 25, wherein the communicating with the base station comprises: transmitting an uplink signal to the base station; and / or receiving a downlink signal from the base station.

27. The method of any of claims 20-26, wherein the time duration is determined based on one or more of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1 ); a frequency range 2 (FR2); a signal direction; a multicarrier configuration; a multi-antenna configuration; a power class; a beam management; and / or a mobility state.

28. The method of any of claims 20-27, wherein the time duration is a switching time for switching a transceiver of the wireless device.

29. The method of any of claims 20-28, wherein the time duration is equal to a duration of the interruption.

30. The method of any of claims 20-29, wherein a duration of the interruption is determined based on the time duration and an offset.31 . The method of any of claims 20-30, wherein the LCM procedure comprises developing, deploying, managing, or maintaining a radio procedure.

32. The method of claim 31 , wherein the LCM procedure comprises one or more of: an identification of the radio procedure; a selection of the radio procedure; an activation of the radio procedure; a deactivation of the radio procedure; a fallback from the radio procedure to a measurement procedure; a switch from the radio procedure to another radio procedure; a release of the radio procedure; a monitoring of the radio procedure; and / or a modification of one or more parameters of the radio procedure.

33. The method of any of claims 20-32, wherein the radio procedure comprises a radio access communication (RAC), a measurement procedure, a positioning procedure, a link recovery procedure, or a radio link procedure.

34. The method of any of claims 20-33, wherein the radio procedure comprises using a model.

35. The method of claim 34, wherein the model comprises an AI / ML model.

36. The method of any one of claims 23-35, wherein the second capability message is transmitted, based on one or more of: an LCM procedure; a model; a radio procedure; a numerology; a bandwidth; a frequency band; a frequency range 1 (FR1); a frequency range 2 (FR2); a signal direction; a multicarrier configuration;a multi-antenna configuration; a power class; a beam management; and a mobility state.

37. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-36.

38. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1-36.

Images