[go: up one dir, main page]

WO2025221633A1 - Timing for life cycle management - Google Patents

Timing for life cycle management

Info

Publication number
WO2025221633A1
WO2025221633A1 PCT/US2025/024475 US2025024475W WO2025221633A1 WO 2025221633 A1 WO2025221633 A1 WO 2025221633A1 US 2025024475 W US2025024475 W US 2025024475W WO 2025221633 A1 WO2025221633 A1 WO 2025221633A1
Authority
WO
WIPO (PCT)
Prior art keywords
procedure
wireless device
base station
lcm
reference signal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/024475
Other languages
French (fr)
Inventor
Muhammad Ali Kazmi
Ali Cagatay CIRIK
Esmael Hejazi Dinan
Kyungmin Park
Mohammad Ghadir Khoshkholgh Dashtaki
Hyoungsuk Jeon
Hua Zhou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ofinno LLC
Original Assignee
Ofinno LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ofinno LLC filed Critical Ofinno LLC
Publication of WO2025221633A1 publication Critical patent/WO2025221633A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00Machine learning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • FIG. 1 A and FIG. 1 B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.
  • FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.
  • NR New Radio
  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.
  • FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.
  • FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.
  • FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.
  • FIG. 6 is an example diagram showing RRC state transitions of a UE.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
  • FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.
  • FIG. 10A illustrates three carrier aggregation configurations with two component carriers.
  • FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.
  • FIG. 11A illustrates an example of an SS/PBCH block structure and location.
  • FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.
  • FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.
  • 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.
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • FIG. 14B illustrates an example of a COE-to-REG mapping for DOI transmission on a CORESET and PDCCH processing.
  • FIG. 15 illustrates an example of a wireless device in communication with a base station.
  • FIG. 16A, FIG. 16B, FIG. 160, and FIG. 16D illustrate example structures for uplink and downlink transmission.
  • FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 18 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 21 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 24 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 25 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 26 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 27 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 28 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 29 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 30 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 31 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 32 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 34 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 38 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 39 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 40 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 41 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 42 illustrates an aspect of an example embodiment according to the present disclosure.
  • FIG. 43 illustrates an aspect of an example embodiment according to the present disclosure.
  • 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.
  • 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).
  • 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.
  • a and B are sets and every element of A is an element of B, A is called a subset of B.
  • A is called a subset of B.
  • possible subsets of B ⁇ celH , cell2 ⁇ are: ⁇ celH ⁇ , ⁇ cell2 ⁇ , and ⁇ celH , cell2 ⁇ .
  • the phrase “based 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” 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” 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 “employin g/using” is indicative that the phrase following the phrase
  • ployin g/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.
  • 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.
  • parameters may comprise one or more information objects, and an information object may comprise one or more other objects.
  • an information object may comprise one or more other objects.
  • parameter (IE) N comprises parameter (IE) M
  • parameter (IE) M comprises parameter (IE) K
  • parameter (IE) K comprises parameter (information element) J.
  • N comprises K
  • N comprises J.
  • one or more messages comprise a plurality of parameters
  • 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.
  • 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 Script, or LabVI EWMathScript. 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, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (OPLDs).
  • 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.
  • HDL hardware description languages
  • VHDL VHSIC hardware description language
  • Verilog Verilog
  • FIG. 1A 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.
  • PLMN public land mobile network
  • the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.
  • CN core network
  • RAN radio access network
  • wireless device 106 wireless device
  • 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.
  • DNs data networks
  • 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.
  • 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.
  • Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques.
  • FDD frequency division duplexing
  • TDD time-division duplexing
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • RRHs remote radio heads
  • 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/similar functions 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.
  • 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.
  • 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.
  • 3GPP 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.
  • 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).
  • UMTS Universal Mobile Telecommunications System
  • 4G fourth generation
  • LTE Long-Term Evolution
  • 5G 5G System
  • 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).
  • NG- RAN next-generation RAN
  • Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG.
  • 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.
  • NR New Radio
  • 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.
  • 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. 1A.
  • 5G-CN 5G core network
  • NG-RAN 154 a 5G core network
  • UEs 156A and 156B collectively UEs 156
  • 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.
  • 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.
  • 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 network functions.
  • 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).
  • 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.
  • QoS quality of service
  • 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.
  • RAT intra-/inter-Radio Access Technology
  • PDU packet data unit
  • the UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.
  • 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 ON and a UE
  • AS may refer to the functionality operating between the UE and a RAN.
  • the 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity.
  • 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).
  • SMF Session Management Function
  • NRF Policy Control Function
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • AF Application Function
  • AUSF Authentication Server Function
  • 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.
  • one or more of the gNBs 160 and/or one or more of the 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.
  • 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.
  • IP internet protocol
  • the gNBs 160 and/or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface.
  • 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.
  • 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.
  • 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-0 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.
  • the gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface.
  • 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.
  • E-UTRA refers to the 3GPP 4G radio-access technology.
  • 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.
  • 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). Although only oneAMF/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.
  • 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.
  • 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. 1B.
  • FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220.
  • PHYs 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 (MAGs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDOPs) 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.
  • MAGs media access control layers
  • RLCs radio link control layers
  • PDOPs packet data convergence protocol layers
  • SDAPs service data application protocol layers
  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack.
  • 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
  • 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.
  • 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.
  • QFI QoS flow indicator
  • 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 messages originate 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-gNB 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.
  • 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).
  • MCG master cell group
  • SCG secondary cell group
  • 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.
  • 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.
  • TTI Transmission Time Interval
  • the MACs 212 and 222 may perform multiplexing/demultiplexing 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.
  • HARQ Hybrid Automatic Repeat Request
  • the MAGs 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 MAGs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223. [0086]
  • 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.
  • 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 MAGs 212 and 222.
  • 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.
  • 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.
  • 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.
  • SDU service data unit
  • PDU protocol data unit
  • the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.
  • 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.
  • 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.
  • the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A.
  • 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.
  • 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.
  • SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds
  • LCID logical channel identifier
  • F flag
  • R reserved bit
  • FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222.
  • a MAC such as MAC 223 or MAC 222.
  • 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) and at 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.
  • 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.
  • 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: [0094] - a paging control channel (POOH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;
  • POOH paging control channel
  • a broadcast control channel 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;
  • MIB master information block
  • SIBs system information blocks
  • COCH common control channel
  • a dedicated control channel for carrying control messages to/from a specific the UE to configure the UE
  • DTCH dedicated traffic channel
  • T ransport 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: [0100] - a paging channel (PCH) for carrying paging messages that originated from the PCCH; [0101] - a broadcast channel (BOH) for carrying the MIB from the BCCH;
  • PCH paging channel
  • BOH broadcast channel
  • DL-SCH downlink shared channel
  • UL-SCH uplink shared channel
  • 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:
  • PBCH physical broadcast channel
  • PDSCH physical downlink shared channel
  • a physical downlink control channel for carrying downlink control information (DOI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;
  • DOI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • a physical uplink control channel for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and
  • CQI channel quality indicators
  • PMI pre-coding matrix indicators
  • Rl rank indicators
  • SR scheduling requests
  • PRACH physical random access channel
  • the physical layer Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer.
  • 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.
  • FIG. 2B illustrates an example NR control plane protocol stack.
  • 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 PDOPs 214 and 224.
  • 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.
  • RRCs radio resource controls
  • 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 ON.
  • 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.
  • 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 control-plane 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.
  • RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.
  • 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.
  • a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).
  • RRC connected 602 e.g., RRC_CONNECTED
  • RRC idle 604 e.g., RRC_I DLE
  • RRC inactive 606 e.g., RRCJNACTIVE
  • 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 base station.
  • 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.
  • bearer configuration information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • security information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • PHY e.g., MAC, RLC, PDCP, and/or SDAP layer configuration information
  • 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
  • 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.
  • RRC idle 604 an RRC context may not be established for the UE.
  • the UE may not have an RRC connection with the base station.
  • the UE 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.
  • 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.
  • An RRC state may be associated with a mobility management mechanism.
  • 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 by a 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).
  • RAI RAN area identifier
  • TAI tracking area and identified by a tracking area identifier
  • 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.
  • RAN areas may be used to track the UE at the RAN level.
  • 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.
  • a base station may belong to one or more RAN notification areas.
  • 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.
  • 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.
  • a gNB 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.
  • OFDM orthogonal frequency divisional multiplexing
  • FAM frequency divisional multiplexing
  • M-QAM M-quadrature amplitude modulation
  • M-PSK M-phase shift keying
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols
  • 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 time-domain samples that represent the summation of the F orthogonal subcarriers.
  • the F time-domain samples may form a single OFDM symbol.
  • an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier 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).
  • DFT Discrete Fourier Transform
  • PAPR peak to average power ratio
  • 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.
  • 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.
  • 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.
  • the duration of a slot may depend on the numerology used for the OFDM symbols of the slot.
  • 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.
  • subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz
  • cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps.
  • 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.
  • 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 numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled.
  • 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.
  • 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.
  • Such a limitation may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
  • FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier.
  • multiple numerologies may be supported on the same carrier.
  • 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.
  • NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation.
  • BWP bandwidth parts
  • a BMP 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).
  • 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.
  • 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.
  • 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.
  • a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.
  • a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space.
  • CORESETs control resource sets
  • 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).
  • 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.
  • 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).
  • One or more BWP indicator fields may be provided in Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • 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.
  • a base station may sem i-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.
  • 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.
  • 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.
  • 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).
  • the UE may switch from the active downlink BWP to the default downlink BWP.
  • 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).
  • 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, DOI, expiration of a BWP inactivity timer, and/or an initiation of random access.
  • 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.
  • 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
  • the BWP 904 may be a default BWP.
  • the UE may switch between BWPs at switching points.
  • the UE may switch from the BWP 902 to the BWP 904 at a switching 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 DOI 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 DOI 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 DOI 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 DOI indicating BWP 902 as the active BWP.
  • 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.
  • two or more carriers can be aggregated and simultaneously transmitted to/from the same UE using carrier aggregation (GA).
  • the aggregated carriers in GA may be referred to as component carriers (00s).
  • 00s component carriers
  • the 00s may have three configurations in the frequency domain.
  • FIG. 10A illustrates the three GA configurations with two 00s.
  • the two 00s are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band.
  • the two 00s are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap.
  • the two 00s are located in frequency bands (frequency band A and frequency band B).
  • up to 3200s may be aggregated.
  • the aggregated 00s may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD).
  • a serving cell for a UE using GA may have a downlink CO.
  • one or more uplink 00s 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.
  • one of the aggregated cells for a UE may be referred to as a primary cell (PCell).
  • the POell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover.
  • the POell may provide the UE with NAS mobility information and the security input.
  • UEs may have different POells.
  • the carrier corresponding to the POell may be referred to as the downlink primary CO (DL POO).
  • the carrier corresponding to the POell may be referred to as the uplink primary CO (UL POO).
  • SCells secondary cells
  • the SCells may be configured after the POell is configured for the UE.
  • an SCell may be configured through an RRC Connection Reconfiguration procedure.
  • the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC).
  • DL SCC downlink secondary CC
  • UL SCC uplink secondary CC
  • 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.
  • a bitmap e.g., one bit per SCell
  • Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).
  • 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 self-scheduling.
  • 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
  • the PUCCH of the PCell may become overloaded.
  • Cells may be divided into multiple PUCCH groups.
  • 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.
  • 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 UC1 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.
  • 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.
  • a physical cell ID may be referred to as a carrier ID
  • a cell index may be referred to as a carrier index.
  • the disclosure 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.
  • the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.
  • a multi-carrier nature of a PHY may be exposed to a MAC.
  • 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.
  • 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).
  • RSs Reference Signals
  • 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) I physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • the base station may periodically transmit a burst of SS/PBCH blocks.
  • 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.
  • 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.
  • 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. 11A) 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 center frequency.
  • 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.
  • 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).
  • 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 celldefining SS block (CD-SSB).
  • a primary cell may be associated with a CD-SSB.
  • the CD-SSB may be located on a synchronization raster.
  • a cell selection/search and/or reselection may be based on the CD- SSB.
  • 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.
  • PCI physical cell identifier
  • the PBCH may use a QPSK modulation and may use forward error correction (FEC).
  • FEC forward error correction
  • 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.
  • MIB master information block
  • the RMSI may include a System Information Block Type 1 (SIB1).
  • 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.
  • 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, average gain, average delay, and/or spatial Rx parameters).
  • QCL quasi co-located
  • SS/PBCH blocks may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell).
  • a first SS/PBCH block may be transmitted in a first spatial direction using a first beam
  • a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.
  • a base station may transmit a plurality of SS/PBCH blocks.
  • 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.
  • 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.
  • 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.
  • 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.
  • periodic CSI reporting the UE may be configured with a timing and/or periodicity of a plurality of CSI reports.
  • the base station may request a CSI report.
  • the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements.
  • 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.
  • 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 downlink CSI-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.
  • Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation.
  • 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-MI MO, 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.
  • a transmitter may use a precoder matrices for a part of a transmission bandwidth.
  • 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).
  • PRG precoding resource block group
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE may transmit an uplink DMRS to a base station for channel estimation.
  • the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels.
  • 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-0 F DM)) 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.
  • CP-0 F DM cyclic prefix orthogonal frequency division multiplexing
  • 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.
  • a higher layer may configure up to three DMRSs for the PUSCH.
  • 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.
  • MCS Modulation and Coding Scheme
  • 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.
  • 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.
  • uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.
  • 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 may employ 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.
  • an SRS resource in an SRS resource set of the one or more SRS resource sets 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.
  • 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.
  • the UE 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.
  • 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, minislot, 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.
  • SRS resource configuration identifier e.g., an indication of periodic, semi-persistent, or aperiodic SRS
  • slot, minislot, and/or subframe level periodicity e.g., an indication of periodic, semi-persistent, or aperiodic SRS
  • 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.
  • the channel e.g., fading gain, multipath delay, and/or the like
  • a first antenna port and a second antenna port may be referred to as quasi colocated (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.
  • Beam management may comprise beam measurement, beam selection, and beam indication.
  • a beam may be associated with one or more reference signals.
  • 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 (OS l-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.
  • downlink reference signals e.g., a channel state information reference signal (OS l-RS)
  • FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains.
  • CSI-RSs channel state information reference signals
  • a square shown in FIG. 11 B 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.
  • 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.
  • 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.
  • FDM frequency division multiplexing
  • TDM time domain multiplexing
  • 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.
  • 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.
  • 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.
  • TCI transmission configuration indication
  • 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.
  • 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.
  • SRS sounding reference signal
  • 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).
  • 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.
  • 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 sweep from 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.
  • 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).
  • 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).
  • RSs reference signals
  • 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.
  • BLER block error rate
  • SINR signal to interference plus noise ratio
  • RSRQ reference signal received quality
  • 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.
  • the channel characteristics e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like
  • a network e.g., a gNB and/or an ng-eNB of a network
  • the UE may initiate a random access procedure.
  • a UE in an RRCJDLE state and/or an RRC_I NACTI VE 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 PUCOH 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).
  • SIBs system information blocks
  • 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.
  • FIG. 13A illustrates a four-step contention-based random access 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 31313, and a Msg 41314.
  • 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).
  • RAR random access response
  • 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.
  • 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 31313.
  • the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 41314.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 UE may 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).
  • a reference signal e.g., an SSB and/or CSI-RS
  • an uplink carrier e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier.
  • 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.
  • 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.
  • 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).
  • 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
  • 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_RAMP/NG_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 preamble transmissions 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).
  • the Msg 2 1312 received by the UE may include an RAR.
  • the Msg 21312 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 PDOCH using a random access RNTI (RA-RNTI).
  • RA-RNTI random access RNTI
  • 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).
  • TC-RNTI Temporary Cell RNTI
  • 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.
  • 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.
  • 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.
  • 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 ⁇ s_id ⁇ 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).
  • s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 ⁇ s_i
  • the UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 21312).
  • the Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A.
  • 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 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE.
  • 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).
  • the Msg 41314 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 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 will be received using a DL-SCH associated with the TC-RNTI.
  • the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed.
  • 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.
  • a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL 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 31313) 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.
  • the UE may determine and/or switch an uplink carrier for the Msg 1 1311 and/or the Msg 31313 based on a channel clear assessment (e.g., a listen- before-talk).
  • FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased 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 21322.
  • the Msg 1 1321 and the Msg 21322 may be analogous in some respects to the Msg 1 1311 and a Msg 21312 illustrated in FIG. 13A, respectively.
  • the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and/or the Msg 41314.
  • 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.
  • a base station may indicate 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).
  • the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR.
  • a time window e.g., ra-ResponseWindow
  • 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., recoverySearchSpace/d).
  • the UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space.
  • C-RNTI Cell RNTI
  • 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.
  • 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.
  • 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 41314 illustrated in FIG. 13A.
  • an RAR e.g., an RAR
  • the UE may initiate the two-step random access procedure in FIG. 130 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.
  • 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 the transport block 1342 included in the Msg A 1331.
  • the RACH parameters may indicate a modulation and coding schemes (MOS), 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
  • a time-frequency resource for transmission of the transport block 1342 e.g., a PUSCH
  • 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.
  • 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 (I MSI)).
  • 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 MOS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).
  • 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).
  • 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.
  • 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 (DOI).
  • the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.
  • 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.
  • CRC cyclic redundancy check
  • 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).
  • RNTI radio network temporary identifier
  • DCIs may be used for different purposes.
  • a purpose may be indicated by the type of RNTI used to scramble the CRC parity bits.
  • a DCI having CRC parity bits scrambled with a paging 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.
  • SI-RNTI may be predefined as “FFFF” in hexadecimal.
  • a DCI having CRC parity bits scrambled with a random access RNTI may indicate a random access response (RAR).
  • a DCI having CRC parity bits scrambled with a cell 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 may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A).
  • 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.
  • CS-RNTI Configured Scheduling RNTI
  • TPC-PUCCH-RNTI Transmit Power Control-PUSCH RNTI
  • TPC-SRS-RNTI Transmit Power Control-SRS RNTI
  • INT-RNTI Interruption RNTI
  • the base station may transmit the DCIs with one or more DCI formats.
  • 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.
  • the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation.
  • channel coding e.g., polar coding
  • a base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH.
  • 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).
  • REG may comprise a resource block in an 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).
  • 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 timefrequency 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.
  • 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.
  • 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 PDCOH reception in the CORESET.
  • DMRS demodulation reference signal
  • 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).
  • 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 PDCCH candidates 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).
  • 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.
  • HARQ hybrid automatic repeat request
  • 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).
  • SR scheduling requests
  • 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 (PUSCH).
  • HARQ-ACK HARQ acknowledgements
  • CSI report CSI report
  • SR SR
  • the UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
  • 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 fourteen OFDM 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.
  • 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.
  • a PUCCH resource identifier e.g., pucch-Resourceid
  • 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”.
  • a total bit length of the UCI information bits e.g., HARQ- ACK, SR, and/or CSI.
  • 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”.
  • 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 DOI may indicate one of eight PUCCH resources in the PUCCH resource set.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504.
  • 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.
  • 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.
  • a reception processing system 1512 may receive the uplink transmission from 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.
  • 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, Ml MO or multi-antenna processing, and/or the like.
  • a wireless device 1502 and the base station 1504 may include multiple antennas.
  • the multiple antennas may be used to perform one or more Ml MO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming.
  • the wireless device 1502 and/or the base station 1504 may have a single antenna.
  • the processing system 1508 and the processing system 1518 maybe associated with a memory 1514 and a memory 1524, respectively.
  • Memory 1514 and memory 1524 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.
  • 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.
  • 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 on-board unit, or any combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • 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.
  • 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).
  • sensors e.g., an accelerometer, a gyroscope, a temperature sensor, a
  • 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 and a 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.
  • 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.
  • SC-FDMA Single Carrier-Frequency Division Multiple Access
  • FIG. 16A illustrates an example structure for uplink transmission.
  • These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.
  • 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.
  • PRACH Physical Random Access Channel
  • 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 complexvalued 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 timedomain 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.
  • 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.
  • 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 configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device.
  • the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc.
  • the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.
  • 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.
  • a timer may be used to measure a time period/window for the procedure.
  • a random access response window timer may be used for measuring a window of time for receiving a random access response.
  • the time difference between two time stamps may be used.
  • 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.
  • AI/ML Artificial intelligence and/or machine learning (ML)
  • An AI/ML model may apply one or more AI/ML techniques for generating a set of outputs based on a set of inputs.
  • 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.
  • the wireless device may use the AI/ML model, e.g., based on one or more AI/ML techniques.
  • 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 are federated learning, reinforcement learning, supervised learning, unsupervised learning, etc. Federated learning may also be referred to as a federated training.
  • 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 require multiple interactions of the model.
  • 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 require multiple interactions of the model.
  • a reinforcement learning technique may train an AI/ML model from an input and a feedback signal resulting from the AI/ML model’s output.
  • a supervised learning technique may train an AI/ML model from an input and labels associated with the input data.
  • an unsupervised learning technique may train an AI/ML model from an input without labelled data.
  • an AI/ML model may also be referred to as a model.
  • an AI/ML model may also be referred to as a radio access communication (RAC).
  • RAC radio access communication
  • FIG. 17 illustrates an example of using an AI/ML model per an aspect of the present disclosure.
  • FIG. 17 may illustrate different stages comprising or involving the AI/ML model.
  • a stage may refer to as a mode, a step, an entity, or a unit.
  • the different stages comprising the AI/ML model may also be referred to as involving or belonging to the AI/ML model.
  • a stage of the different stages may be for generating the AI/ML model.
  • a stage of the different stages may be for inference procedure for inferring data based on the AI/ML model.
  • an AI/ML model generating stage of an AI/ML model may receive training data.
  • the AI/ML model generating stage may generate an output data for inferring data.
  • the inferring data may also be referred to as inferring result.
  • the inferring data may also be referred to as estimating data, determining data, forecasting data or predicting data.
  • an inferring data stage may receive the output data for an inference from the AI/ML model generating stage.
  • the inferring data stage may infer data based on the output data received from the AI/ML model generating stage.
  • FIG. 18 illustrates an example of a procedure for an AI/ML model capability transfer per an aspect of the present disclosure.
  • the procedure may also be referred to as a signaling flow.
  • the procedure may correspond to a wireless device.
  • the wireless device may communicate with a base station.
  • the communication between the wireless device and the base station may be based on the AI/ML model.
  • the communication may comprise the wireless device inferring (determining, predicting, and/or estimating) one or more measurement e.g. , a channel quality indicator (CSI), a positioning measurement, a downlink beam etc.
  • the communication may further comprise the wireless device transmitting, to a base station, the one or more measurements based on the inferring.
  • the wireless device may transmit or transfer the AI/ML model capability to the base station.
  • FIG. 18 illustrates a base station may configure a wireless device to transmit a capability.
  • the capability may comprise an AI/ML model capability of the wireless device.
  • the base station may transmit one or more RRC messages comprising one or more configuration parameters for the wireless device to transmit an AI/ML model capability.
  • the base station may transmit an inquiry message to the wireless device.
  • the inquiry message may be an RRC message.
  • the inquiry message may indicate a request for the wireless device to transmit the AI/ML model capability of the wireless device to the base station.
  • the AI/ML model capability may indicate that the wireless device supports both stages of the AI/ML model as illustrated in FIG. 17.
  • the AI/ML model capability may indicate that the wireless device may support (e.g., only) an AI/ML model generation stage of the AI/ML model as illustrated in FIG. 17.
  • the AI/ML model capability may indicate that the wireless device may support (e.g., only) an inferring data stage of the AI/ML model as illustrated in FIG. 17.
  • a wireless device may indicate, to a base station, that the wireless device may support one or more AI/ML models, e.g., by RRC.
  • FIG. 19 illustrates another example of a procedure for an AI/ML model capability transfer to a location management function (LMF) per an aspect of the present disclosure.
  • LMF location management function
  • the configuring of the UE to transmit AI/ML capability and the transmission of the AI/ML capability by the wireless device is described above with reference to FIG. 18.
  • a wireless device may indicate, to the LMF, 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)).
  • LMF location management function
  • wireless device may include, in a capability message (e.g., indicating the AI/ML capability of FIG. 18 and/or FIG. 19), 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 serves as a distinctive identifier for an AI/ML model.
  • a model ID of an AI/ML model enables a mutual understanding between a base station and a wireless device of the AI/ML model.
  • the capability message may include information about one or more conditions in which the wireless device may use an AI/ML model.
  • a condition may comprise a speed of a wireless device.
  • a condition may comprise a speed range of a wireless device.
  • a condition may comprise a frequency or frequency range.
  • a condition may comprise a frequency range.
  • 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.
  • a condition may comprise one or more radio channel characteristics.
  • a radio channel characteristic may comprise a Doppler frequency.
  • a radio channel characteristic may comprise a channel delay spread.
  • a radio channel characteristic may comprise a channel coherence time.
  • a wireless device may train an AI/ML model based on training data.
  • a base station may train an AI/ML model based on training data.
  • a base station may transmit one or more messages to the wireless device.
  • the one or more messages may comprise at least one RRC message.
  • the one or more messages may comprise at least one MAC CE.
  • the one or more messages may comprise one or more parameters of an AI/ML model.
  • the one or more parameters may correspond to the AI/ML mode.
  • the base station may transmit at least one DCI comprising the one or more parameters.
  • the one or more parameters of the AI/ML model may comprise an AI/ML model identifier.
  • the one or more parameters of the AI/ML model may comprise a set of data for training an AI/ML model.
  • the set of data for training may be a set of measurement samples.
  • the wireless device may train an AI/ML model by using the one or more parameters received from the base station.
  • a wireless device may use one or more AI/ML models for inferring data based on trained data.
  • the inferring data may comprise 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.
  • 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) for RLM; and/or beam failure detection (BFD); and/or candidate beam detection (OBD); and/or L1-RSRP; and/or L1-SINR associated with a link recovery procedure (LRP); and/or one or more positioning measurements; and/or one or more layer-3 mobility measurements.
  • CSI channel state information
  • IS in-sync
  • OOS out-of-sync
  • BFD beam failure detection
  • BFD candidate beam detection
  • L1-RSRP and/or L1-SINR associated with a link recovery procedure (LRP); and/or one or more positioning measurements; and/or one or more layer-3 mobility measurements.
  • Examples of the positioning measurement may comprise 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 (OPP); 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.
  • RSTD reference signal time difference
  • RTT round trip time
  • multi-RTT multi-RTT
  • OPP carrier phase measurement
  • CIR channel impulse response
  • TOA time of arrival
  • RSRP reference signal received power
  • RRPP reference signal received path power
  • PRS-RSRP positioning reference signal - reference signal received power
  • Examples of the layer-3 mobility measurement may comprise a pathloss; a reference signal received power (RSRP); a reference signal received quality (RSRQ); a signal to interference and noise ratio (SINR) etc.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • SINR signal to interference and noise ratio
  • a wireless device 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 wireless device-side model.
  • a wireless device-side model may also be referred to as a wireless device-based model.
  • 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.
  • 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.
  • a part of the data is inferred by a wireless device and a part of the data is inferred by a base station.
  • 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 comprise a compressed CSI.
  • the base station may use an AI/ML model based decoder to decode the received data.
  • a wireless device may communicate with a base station (and/or an LMF) based on the AI/ML model. For example, the wireless device may transmit one or more message to the base station (and/or LMF) based on the data inferred from the AI/ML model as discussed above.
  • a life cycle management (LCM) of an AI/ML model may comprise developing, deploying, managing or maintaining an AI/ML model.
  • an LCM of an AI/ML model involves performing one or more LCM procedures on the AI/ML model.
  • an LCM procedure may comprise performing at least one of: 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 and a modification of one or more parameters of the AI/ML model.
  • a wireless device may use a measurement procedure for obtaining a measurement.
  • the using the measurement procedure may also be referred to as applying the measurement procedure.
  • the obtaining a measurement may also be referred to as performing the measurement.
  • a measurement procedure may comprise performing a measurement based on a signal.
  • a measurement procedure may comprise performing a measurement based on a signal transmitted by and/or received by the wireless device.
  • the signal may comprise a reference signal.
  • performing an LCM procedure may comprise: 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; and/or modifying one or more parameters of the AI/ML model.
  • a wireless device may perform an LCM procedure on an AI/ML model stored in the wireless device.
  • a base station may perform an LCM procedure on an AI/ML model stored in the base station.
  • the LCM procedure may be a functionality-based LCM.
  • a base station may configure a wireless device to perform the LCM procedure for an AI/ML model stored in the wireless device.
  • a base station may configure a wireless device to perform the LCM procedure by RRC.
  • a base station may configure a wireless device to perform the LCM procedure by MAC-CE.
  • a base station may configure a wireless device to perform the LCM procedure by DCI.
  • 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.
  • a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) during an LCM procedure.
  • an interruption of the communication may comprise, the wireless device not receiving a signal from the base station and/or the wireless device not transmitting a signal to the base station.
  • a wireless device not transmitting a signal may also be referred to as dropping, discarding, or cancelling a signal.
  • a wireless device may use internal resources of the wireless device for performing a Life Cycle Management (LCM) procedure for an AI/ML model.
  • the internal resources of the wireless device may comprise a memory and/or processor.
  • the wireless device may share the internal resources for performing the LCM procedure and also for performing one or more additional tasks.
  • the one or more additional tasks may comprise at least one of processing data, receiving signal, transmitting signal, performing online and/or offline services (or functionalities or applications or the like) etc.
  • the one or more additional tasks may not correspond, 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 data transmission; and/or data reception.
  • RLM Radio Link Monitoring
  • the wireless device may interrupt communication 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 the communication may comprise not transmitting one or more UL sign als/ch an nels to the base station.
  • the interruption of the communication may comprise not receiving one or more DL signals/channels from the base station.
  • the LCM procedure may comprise (or require) 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.
  • the wireless device may interrupt communication with the base station due to the reconfiguration of the RF bandwidth of the wireless device.
  • the LCM procedure may comprise/require tuning/retuning/changing/reconfiguring one or more RF circuitries. Tuning, retuning, changing or reconfiguring the one or more RF circuitries my result in the interruption of the communication.
  • the RF circuitry may comprise one or more of an RF filter, a power amplifier (PA), a low noise amplifier (LNA), an antenna array, an antenna, an antenna element, a switch etc.
  • the LCM procedure may comprise retraining (or fine tuning) the AI/ML model.
  • the wireless device may use the shared resources for fetching one or more parameters (of the AI/ML model) in order to fine tune/retrain the AI/ML model.
  • Retraining the AI/ML mode may requires gathering/obtaining a new set of training data corresponding to the AK/ML model.
  • Retraining (or fine tuning) the AI/ML mode may comprising changing/updating one or more meta parameters of the AI/ML model.
  • Retraining (or fine tuning) the AI/ML mode may comprising reconstructing the AI/ML model.
  • the LCM procedure may comprise measuring at least one key performance indicator (KPI) corresponding to the AI/ML model.
  • KPI key performance indicator
  • the at least one KPI may demonstrate a performance/accuracy of the AI/ML mode. Measuring the at least one KPI may result in the interruption of the communication as the wireless device may require performing at least one measurement.
  • the wireless device may use the at least one KPI for selecting a new AI/ML mode.
  • the wireless device may use the at least one KPI for activating a new AI/ML mode and/or deactivating the AI/ML model.
  • the wireless device may use the at least one KPI for falling back form the AI/ML mode, e.g. , stop using the AI/ML model.
  • FIG. 20 illustrates an example of an LCM procedure per an aspect of the present disclosure.
  • a wireless device may autonomously perform an LCM procedure.
  • the LCM procedure may comprise one or more of: a selection of an AI/ML model, a switching of an AI/ML model to another AI/ML model, a deactivation of an AI/ML model, an activation of an AI/ML model and a fallback from an AI/ML model to a measurement procedure.
  • 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/activate the AI/ML mode for performing the handover/RLM/BFR or the like.
  • the LCM procedure may be performed after the handover procedure or an RLM procedure or a BFR procedure.
  • the wireless device may select/acti vate a new AI/ML mode and/or deactivate the AI/ML model.
  • a wireless device may (e.g., autonomously) perform an LCM procedure for an AI/ML model (e.g., as shown in an example in FIG. 20).
  • the wireless device may perform the LCM procedure at any arbitrary time.
  • the autonomously performing the LCM procedure for the AI/ML model (e.g., determining to autonomously perform the LCM procedure) may cause an interruption of communication between the wireless device and a base station.
  • the autonomously performing the LCM procedure for the AI/ML model may result in misalignment between the wireless device and the base station.
  • the base station may incur unexpected interruption of communication with the wireless device.
  • the base station may not be aware of whether the LCM procedure is ongoing or not at the wireless device.
  • the base station may not distinguish whether the interruption is due to the one or more additional tasks or the LCM procedure.
  • the base station may not correctly determine a duration of the interruption.
  • the base station may not correctly determine a location in time, of the interruption.
  • a base station may configure a wireless device, e.g., by RRC, MAC-CE or DCI, to perform an LCM procedure for an AI/ML model.
  • the configuration may allow the wireless device to perform the LCM procedure
  • the LCM procedure may cause an interruption of communication between the wireless device and a base station.
  • the interruption may occur (e.g., start) at an indefinite time point after the wireless receives, from the base station, a configuration message to perform an LCM procedure.
  • the wireless device may encounter uncertainty in performing the LCM procedure.
  • the measurement of the at least one KPI may occupy the internal resources of the wireless device.
  • the time point for performing the LCM procedure may be uncertain.
  • the base station may incur unexpected interruption of communication after transmitting, to the wireless device, the configuration message.
  • the base station may not be able to accurately determine (or identify or detect) the time point when the wireless device may perform the LCM and/or a duration of the interruption.
  • the performing an LCM procedure for an AI/ML model may result in a loss of uplink data and/or downlink data, e.g., loss of PUSCH, PDSCH etc.
  • the performing the LCM procedure may increase UL/DL data latency or reduce UL/DL data transmission rate.
  • the wireless device may not transmit an uplink data and/or receive a downlink data during the LCM procedure.
  • the performing an LCM procedure for an AI/ML model may result in loss of control signaling, e.g. a HARQ feedback, a CSI report etc.
  • the wireless device may not transmit an uplink control signaling and/or receive a downlink control signaling during the LCM procedure.
  • the performing an LCM procedure for an AI/ML model may result in loss of a reference signal.
  • 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 an accuracy of a measurement performed by a wireless device on a reference signal.
  • the performing an LCM procedure for an AI/ML model may waste radio resources (in time and/or frequency).
  • a radio resource may comprise a resource element.
  • a radio resource may comprise a resource block.
  • a base station may allocate, to the wireless device, one or more radio resources to perform one or more procedures.
  • 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.
  • the performing an LCM procedure may cause misalignment between a wireless device and a base station. The misalignment may cause an unexpected interruption of communication between the wireless device and the base station. The unexpected interruption may result in loss of data and/or control signaling.
  • the unexpected interruption may result in unused (e.g., wasted) allocated radio resources e.g., scheduling grant.
  • a wireless device may trigger an LCM procedure for a radio access communication (RAC).
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start based on the triggering of the LCM procedure.
  • An interruption of communication with a base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption.
  • Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a wireless device may trigger an LCM procedure for a RAC.
  • the wireless device may transmit, to a base station, an indication for starting an LCM procedure in response to triggering the LCM procedure.
  • the indication may include at least an identifier for the LCM procedure.
  • the wireless device may perform the LCM procedure based on the transmission of the indication.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start from the transmission of the indication.
  • An interruption of communication with a base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a wireless device may receive, from a base station, a request for performing an LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for an LCM procedure.
  • the wireless device may trigger the LCM procedure for a RAC based on the reception of the request for performing an LCM procedure.
  • the wireless device may perform the LCM procedure based on the triggering of the LCM procedure.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start from the reception of the request for performing an LCM procedure.
  • An interruption of communication with a base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a wireless device may receive, from a base station, a request for performing an LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for an LCM procedure.
  • the wireless device may transmit, to the base station, a response message corresponding to the request for performing an LCM procedure.
  • the wireless device may trigger the LCM procedure for a LAC based on the transmission of the response message.
  • the response message corresponds to the request for performing an LCM procedure.
  • the wireless device may perform the LCM procedure based on the triggering of the LCM procedure.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start from the transmission of the response message.
  • An interruption of communication with a base station may occur during the interruption duration.
  • a wireless device triggers an LCM procedure for a RAC.
  • the wireless device may transmit, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for the LCM procedure.
  • the wireless device may receive, from a base station, an indication enabling the LCM procedure based on the request for starting an LCM procedure.
  • the indication enabling the LCM procedure may indicate whether to perform, by the wireless device, the LCM procedure.
  • the wireless device may perform the LCM procedure based on the indication enabling the LCM procedure.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start from the reception of the indication enabling the LCM procedure.
  • An interruption of communication with a base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a wireless device may receive, from a base station, a request for performing an LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for an LCM procedure.
  • the request for performing an LCM procedure may trigger the LCM procedure for a RAC.
  • the wireless device may transmit, to the base station, an indication for starting an LCM procedure in response to receiving the request for performing an LCM procedure.
  • the request for performing an LCM procedure may indicate that, during the LCM procedure, an interruption of communication with base station may occur.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start based on the transmission of the indication for starting an LCM procedure.
  • the interruption of communication with the base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption.
  • Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a wireless device may receive, from a node (e.g., a location server, a core network node etc), a request for performing an LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for an LCM procedure.
  • the request for performing an LCM procedure may trigger the LCM procedure for a RAC.
  • the wireless device may transmit, to a base station, an indication for starting an LCM procedure in response to receiving the request for performing an LCM procedure.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start based on the transmission of the indication for starting an LCM procedure.
  • the interruption of communication with the base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption.
  • Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a base station may receive, from a node (e.g., a location server, a core network node etc), an indication that UE starting an LCM procedure.
  • a node e.g., a location server, a core network node etc.
  • the indication that UE starting an LCM procedure may include at least an identifier for an LCM procedure and an identifier of a wireless device.
  • a wireless device may receive, from a node (e.g., a location server, a core network node etc), a request for performing an LCM procedure.
  • the request for performing an LCM procedure may include at least an identifier for an LCM procedure.
  • the request for performing an LCM procedure may trigger the LCM procedure for a RAC.
  • the wireless device may perform the LCM procedure during an interruption duration.
  • the interruption duration may start based on the reception of the request for performing an LCM procedure.
  • the interruption of communication with the base station may occur during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption.
  • Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
  • a base station may receive, from a node (e.g., a location server, a core network node etc), a request for starting an LCM procedure for UE.
  • the request for starting an LCM procedure for UE may include at least an identifier for an LCM procedure and an identifier of a wireless device.
  • the base station may transmit, to the wireless device a request for performing an LCM procedure based on the request for starting an LCM procedure for UE.
  • the wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the reception of the request for performing an LCM procedure.
  • FIG. 21 illustrates an example for an LCM procedure as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 21 may be combined with the features previously discussed with reference to FIGs. 18, 19, and/or 20.
  • a wireless device may trigger the LCM procedure for a radio access communication (RAC).
  • the wireless device may perform the LCM procedure during an interruption duration (e.g., based on the LCM procedure illustrated in FIG. 20).
  • the interruption duration may start based on (or in response to or after) the triggering of the LCM procedure.
  • Example embodiments in FIG. 21 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • the wireless device may communicate with the base station, based on the LCM procedure, after the interruption.
  • the interruption duration may start in response to the triggering of the LCM procedure.
  • the interruption duration may start after the triggering of the LCM procedure.
  • the LCM procedure may be triggered during a time resource.
  • the time resource may comprise a symbol, a slot, a subframe, or a radio frame.
  • the interruption duration may start during the time resource.
  • the interruption duration may start from the beginning of the time resource.
  • the interruption duration may start after the end of the time resource or immediately after the end of the time resource.
  • a wireless device communicating with a base station, based on the LCM procedure may comprise inferring data based on a model for a RAC.
  • the one or more criteria for triggering an LCM procedure may comprise (or be based on) one or more radio channel characteristics (or measurements).
  • a radio channel characteristic of the one or more radio channel characteristics may comprise a Doppler frequency.
  • a radio channel characteristic of the one or more radio channel characteristics may comprise a channel delay spread.
  • a radio channel characteristic of the one or more radio channel characteristics may comprise a channel coherence time.
  • the wireless device may estimate the one or more radio channel characteristics based on a signal.
  • the signal may comprise a reference signal (RS).
  • the RS may comprise an SSB, CSI-RS, DMRS etc.
  • the wireless device may estimate the one or more radio channel characteristics by measuring the signal.
  • the wireless device may trigger the LCM procedure based on the Doppler frequency (Df) of the wireless device being below a first Doppler threshold (TD1).
  • TD2 Doppler threshold
  • the wireless device may trigger the LCM procedure based on the Doppler frequency (Df) estimated by the wireless device being above a second Doppler threshold (TD2).
  • the wireless device may trigger the LCM procedure based on the channel delay spread estimated by the wireless device being below a first delay spread threshold (TD1).
  • the wireless device may trigger the LCM procedure based on the channel delay spread estimated by the wireless device being above a second delay spread threshold (TSD2).
  • TSD2 second delay spread threshold
  • the wireless device may trigger the LCM procedure based on the channel coherence time estimated by the wireless device being below a first coherence time threshold (TCC1).
  • TCD2 first coherence time threshold
  • the wireless device may trigger the LCM procedure based on the channel coherence time estimated by the wireless device being above a second coherence time threshold (TCC2).
  • TD1, TD2, TD1, TSD2, TCC1 and TCC2 may be pre-determined.
  • the wireless device may receive a configuration comprising TD1, TD2, TD1, TSD2, TCC1 and TCC2.
  • the wireless device may receive the configuration by an RRC message.
  • the LCM procedure performed during the interruption duration may comprise one or more of the steps illustrated above in FIG. 20.
  • the LCM procedure may comprise an activation of an AI/ML model or a deactivation of the AI/ML model.
  • a wireless device may trigger the activation of the AI/ML model, e.g., based on the Df of the wireless device being below TD1.
  • a wireless device may trigger the deactivation of the AI/ML model based on the Df of the wireless device being above TD2.
  • the one or more criteria for triggering an LCM may comprise a location of the wireless device.
  • the location of the wireless device may also be referred to as a position or a geographic location or a footprint of the wireless device.
  • a wireless device may determine a location of the wireless device based on a positioning measurement.
  • a wireless device may measure a positioning signal to obtain the positioning measurement.
  • the positioning signal may comprise one or more of a Positioning Reference Signal (PRS), Sounding Reference Signal (SRS) etc.
  • PRS Positioning Reference Signal
  • SRS Sounding Reference Signal
  • a wireless device may receive a location information from a location server.
  • a wireless device may determine a location of the wireless device based on the received location information.
  • the location of the wireless device may change over time.
  • the wireless device may trigger the LCM procedure if the location of the wireless device changes.
  • the wireless device may trigger the LCM procedure based on a distance between a current location and a previous location of the wireless device.
  • the wireless device may trigger the LCM procedure based on a distance between the current and the previous location of the wireless device being more than a first distance threshold (TL1).
  • TL1 may be pre-determined.
  • the wireless device may receive a configuration comprising TL1. The wireless device may receive the configuration by an RRC message.
  • the LCM procedure performed during the interruption duration 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.
  • a wireless device 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 the wireless device being more than TL1.
  • a wireless device 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 the wireless device being less than or equal to TL1.
  • the one or more criteria for triggering an LCM procedure may comprise a downlink signal quality.
  • a wireless device may estimate a downlink signal quality (DSQ) based on a reference signal (RS).
  • a RS may comprise a SSB, CSI-RS, DMRS etc.
  • a wireless device may measure on a RS to estimate a signal quality.
  • the signal quality may comprise a signal to noise ratio (SNR), a signal to noise and interference radio (SI NR), a channel quality indicator (CQI), a reference signal received quality (RSRQ) etc.
  • SNR signal to noise ratio
  • SI NR signal to noise and interference radio
  • CQI channel quality indicator
  • RSRQ reference signal received quality
  • a wireless device may trigger an LCM procedure based on a DSQ being below a first DSQ threshold (TDQ1).
  • a wireless device may trigger an LCM procedure based on a DSQ being above a second DSQ threshold (TDQ2).
  • TDQ1 and TDQ2 may be pre-determined.
  • the wireless device may receive a configuration comprising TDQ1 and TDQ2.
  • the wireless device may receive the configuration by an RRC message.
  • the LCM procedure may comprise a switching an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching an AI/ML model from AI/ML2 model to AI/ML1 model.
  • AI/ML1 may be trained for a scenario based on a DSQ estimated by a wireless device being above TDQ2.
  • AI/ML1 may be suitable for a scenario based on a SQ estimated by a wireless device being below TDQ1.
  • a wireless device may trigger a switching an AI/ML model from AI/ML1 to AI/ML2 based on a DSQ estimated by the wireless device being below TDQ1.
  • a wireless device may trigger a switching an AI/ML model from AI/ML2 to AI/ML1 based on a DSQ estimated by the wireless device being above TDQ2.
  • the one or more criteria for triggering an LCM procedure may comprise an HARQ ACK/NACK.
  • a wireless device may transmit, to a base station, the HARQ ACK/NACK message in response to receiving, from a base station, a data channel e.g. PDSCH.
  • the wireless device may transmit, to the base station, an ACK in response to correctly decoding the data channel.
  • the wireless device may transmit, to the base station, a NACK in response to incorrectly decoding the data channel.
  • a wireless device may trigger an LCM procedure based on a number of ACKs and/or a number of NACKs transmitted by the wireless device during a first HARQ time period (Tp1).
  • a wireless device may trigger an LCM procedure based on a number of ACKs during Tp1 being below a first ACK threshold (TAK1). In an example, a wireless device 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, a wireless device may trigger an LCM procedure based on a number of NACKs during Tp1 being above a second NACK threshold (TNK2). In an example, TAK1, TAK2, TNK1 and TNK2 may be pre-determined. In an example, the wireless device may receive a configuration comprising TAK1, TAK2, TNK1 and TNK2. The wireless device may receive the configuration by an RRC message.
  • the wireless device communicating with a base station after the interruption duration may comprise, the wireless device transmitting a signal (e.g., an uplink singal or an uplink message)) to the base station and/or receiving a signal (e.g., a downlink signal or downlink message) from the base station.
  • a signal e.g., an uplink singal or an uplink message
  • a signal e.g., a downlink signal or downlink message
  • FIG. 22 illustrates an example 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. 18, 19, 20 and/or 21.
  • example embodiments in FIG. 22 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC).
  • Example embodiments in FIG. 22 may comprise the wireless device, transmitting, to a base station, an indication for starting an LCM procedure in response to triggering the LCM procedure.
  • Example embodiments in FIG. 22 may comprise the wireless device performing the LCM procedure based on the transmission of the indication for staring the LCM procedure.
  • Example embodiments in FIG. 22 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 22 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 22 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • the indication for starting the LCM procedure may comprise at least an identifier for the LCM procedure.
  • each LCM procedure may be associated with an identifier (ID).
  • the identifier may comprise one or more bits.
  • the indication for starting the LCM procedure may comprise an RRC message.
  • a wireless device may trigger an LCM procedure for a RAC based on one or more criteria.
  • the one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
  • the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK.
  • an interruption duration may start from the transmission of the indication for starting an LCM procedure.
  • the wireless device may transmit the indication for starting an LCM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources comprising the indication for starting an LCM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
  • the interruption duration may start from the end of the one or more time resources comprising the indication for starting an LCM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
  • a wireless device communicating with a base station after the interruption may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 23 illustrates an example 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. 18, 19, 20, 21, and/or 22.
  • example embodiments in FIG. 23 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC).
  • Example embodiments in FIG. 23 may comprise the wireless device, transmitting, to a base station, an indication for starting the LCM procedure in response to triggering the LCM procedure.
  • Example embodiments in FIG. 23 may comprise the wireless device performing the LCM procedure based on the transmission of the indication for starting the LCM procedure.
  • Example embodiments in FIG. 23 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start after a time period. The time period may start from the transmission of the indication for starting the LCM procedure.
  • Example embodiments in FIG. 23 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 23 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • the indication for starting the LCM procedure is according to the example embodiments in FIG. 22 (e.g., the indication for starting the LCM procedure).
  • a first time period may start from the transmission of the indication for starting an LCM procedure.
  • the wireless device may transmit the indication for starting an LCM procedure during one or more time resources.
  • the time period may start based on the one or more time resources comprising the indication for starting an LCM procedure.
  • the time period may start from the beginning of the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
  • the time period may start from the end of the last time resource comprising the indication for starting an LCM procedure.
  • the time period may start during the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
  • an interruption duration may start immediately after the time period.
  • the time period may comprise one or more time resources.
  • the interruption duration may start after the end of the last time resource of the one or more time resources comprising the time period.
  • the interruption duration may start immediately after the end of the last time resource of the one or more time resources comprising the time period.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the time period.
  • a wireless device may trigger an LCM procedure for a RAC based on one or more criteria.
  • the one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
  • the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 24 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, and/or 23.
  • example embodiments in FIG. 24 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure.
  • Example embodiments in FIG. 24 may comprise the wireless device triggering an LCM procedure based on the reception of the request for performing an LCM procedure.
  • Example embodiments in FIG. 24 may comprise the wireless device performing an LCM procedure based on the triggering of LCM procedure.
  • Example embodiments in FIG. 24 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 24 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 24 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • the request for performing an LCM procedure may comprise at least an identifier for the LCM procedure.
  • each LCM procedure may be associated with an identifier.
  • the identifier may comprise one or more bits.
  • the request for performing an LCM procedure may comprise an RRC message.
  • a base station may transmit, to a wireless device, the request for performing an LCM procedure based on one or more criteria.
  • the one or more criteria for transmitting, to a wireless device, the request for performing an LCM procedure may comprise an uplink signal quality.
  • a base station may estimate an uplink signal quality (USQ) based on an uplink reference signal (URS).
  • the URS may be transmitted by the wireless device.
  • an URS may comprise SRS, UL-DMRS etc.
  • a base station may measure an URS to estimate an uplink signal quality.
  • the uplink signal quality may comprise a signal to noise ratio (SNR), a signal to noise and interference radio (SI NR) etc.
  • a base station may transmit, to a wireless device, a request for performing an LCM procedure based on an USQ being below a first USQ threshold (TUQ1). In an example, may transmit, to a wireless device, a request for performing an LCM procedure based on an USQ being above a second USQ threshold (TUQ2).
  • the one or more criteria for triggering an LCM procedure may comprise an HARQ ACK/NACK.
  • a wireless device may transmit, to a base station, the HARQ ACK/NACK message in response to receiving, from a base station, a data channel e.g. PDSCH. In an example, the wireless device may transmit, to the base station, an ACK in response to correctly decoding the data channel.
  • the wireless device may transmit, to the base station, a NACK in response to incorrectly decoding the data channel.
  • a base station may trigger an LCM procedure based on a number of ACKs and/or a number of NACKs received from the wireless device during a second HARQ time period (Tp2).
  • a base station may trigger an LCM procedure based on a number of ACKs during Tp2 being below a third ACK threshold (TAK3).
  • a base station may trigger an LCM procedure based on a number of ACKs during Tp2 being above a fourth ACK threshold (TAK4).
  • a wireless device may trigger an LCM procedure based on a number of NACKs during Tp2 being below a third NACK threshold (TNK3).
  • a base station may trigger an LCM procedure based on a number of NACKs during Tp2 being above a fourth NACK threshold (TNK4).
  • a request for performing an LCM procedure may comprise an identifier of an LCM procedure.
  • the wireless device may perform an LCM procedure corresponding to the identifier of the LCM procedure comprised in the request for performing an LCM procedure.
  • the LCM procedure may comprise a switching, by the wireless device, an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching an AI/ML model from AI/ML2 model to AI/ML1 model.
  • AI/ML1 may be trained for a scenario based on an USQ estimated by a base station being above TUQ2.
  • AI/ML1 may be suitable for a scenario based on an USQ estimated by a base station being below TUQ1.
  • the request for performing an LCM procedure may indicate switching an AI/ML model from AI/ML1 to AI/ML2 based on an USQ estimated by the base station being below TUQ1.
  • the request for performing an LCM procedure may indicate switching an AI/ML model from AI/ML2 to AI/ML1 based on an USQ estimated by the base station being above TUQ2.
  • an interruption duration may start from the reception of the request for performing an LCM procedure.
  • the wireless device may receive the request for performing an LCM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LCM procedure.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LCM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LCM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LCM procedure. In an example, the interruption duration may start based on a successful decoding, by the wireless device, of the request for performing an LCM procedure message. In an example, the interruption duration may start after the successful decoding, by the wireless device, of the request for performing an LCM procedure message.
  • a wireless device communicating with a base station after interruption may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 25 illustrates an example 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. 18, 19, 20, 21, 22, 23, and/or 24.
  • example embodiments in FIG. 25 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure.
  • Example embodiments in FIG. 25 may comprise the wireless device triggering an LCM procedure based on the reception of the second message.
  • Example embodiments in FIG. 25 may comprise the wireless device performing an LCM procedure based on the triggering of LCM procedure.
  • Example embodiments in FIG. 25 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start after a time period.
  • Example embodiments in FIG. 25 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 25 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • the request for performing an LCM procedure is according to the example embodiments in FIG. 24 (e.g., the request for performing an LCM procedure).
  • a base station may transmit the request for performing an LCM procedure based on one or more criteria.
  • the one or more criteria are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and the HARQ ACK/NACK).
  • a time period may start from the reception of the request for performing an LCM procedure.
  • the wireless device may receive the request for performing an LCM procedure during one or more time resources.
  • the time period may start based on the one or more time resources during which the wireless device may receive the request for performing an LCM procedure.
  • the time period may start from the beginning of the last time resource of the one of more time resources comprising the request for performing an LCM procedure message.
  • the time period may start from the end of the last time resource of the one of more time resources comprising the request for performing an LCM procedure message.
  • the time period may start during the last time resource of the one of more time resources comprising the request for performing an LCM procedure message.
  • the time period may start based on a successful decoding, by the wireless device, of the request for performing an LCM procedure message. In an example, the time period may start after the successful decoding, by the wireless device, of the request for performing an LCM procedure message.
  • the interruption duration may start after the time period according to the example embodiments in FIG.23.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 26 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, and/or 25.
  • example embodiments in FIG. 26 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure.
  • Example embodiments in FIG. 26 may comprise the wireless device transmitting, to the base station, a response message corresponding to the request for performing an LCM procedure.
  • Example embodiments in FIG. 26 may comprise the wireless device performing an LCM procedure based on the transmission of the response message.
  • Example embodiments in FIG. 26 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 26 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 26 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a base station may transmit a request for performing an LCM procedure based on one or more criteria.
  • the one or more criteria are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and/or the HARQ ACK/NACK).
  • a request for performing an LCM procedure is according to the example embodiments in FIG. 24 (e.g., the request for performing an LCM procedure).
  • a request for performing an LCM procedure may be a MAC-CE.
  • a response message may comprise a feedback signal corresponding to request for performing an LCM procedure.
  • the feedback signal may comprise a HARQ message.
  • the feedback signal comprising the HARQ message may be in response to the request for performing LCM procedure comprising an MAC-CE.
  • the HARQ message may comprise an acknowledgement (ACK) message or a negative acknowledgement (NACK) message.
  • the HARQ message may comprise one or more bits.
  • the wireless device may transmit the ACK message in response to successful decoding of the request for performing an LCM procedure message.
  • the wireless device may transmit the NACK message in response to unsuccessful decoding of the request for performing an LCM procedure message.
  • the interruption duration may start from the transmission of the response message.
  • the interruption duration may start based on the transmission of the response message comprising an HARQ ACK.
  • the interruption duration may start from the transmission of the response message comprising an HARQ ACK.
  • the wireless device may transmit the response message during one or more time resources.
  • the interruption duration may start from the beginning of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the transmission of the response message. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the transmission of the response message.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the transmission of the HARQ ACK.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 27 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, 25, and/or 26.
  • example embodiments in FIG. 27 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure.
  • Example embodiments in FIG. 27 may comprise the wireless device transmitting, to the base station, a response message corresponding to the request for performing an LCM procedure.
  • Example embodiments in FIG. 27 may comprise the wireless device performing an LCM procedure based on the transmission of the response message.
  • Example embodiments in FIG. 27 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 27 may comprise the wireless device interrupting communication with the base station during the interruption duration. The interruption duration may start after a time period.
  • Example embodiments in FIG. 27 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a request for performing an LCM procedure is according to the example embodiments in FIG. 26 (e.g. the request for performing an LCM procedure).
  • a response message is according to the example embodiments in FIG. 26 (e.g., the response message).
  • a base station may transmit a request for performing an LOM procedure based on one or more criteria.
  • the one or more criteria for transmitting the request for performing an LOM procedure are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and the HARQ ACK/NACK).
  • the interruption duration may start after the time period according to the example embodiments in FIG.23.
  • the time period may start from the transmission of the response message.
  • the wireless device may transmit the response message during one or more time resources.
  • the time period may start from the beginning of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the time period may start from the end of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the time period may start during the last time resource of the one or more time resources comprising the transmission of the response message.
  • the time period may start from the beginning of last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the time period may start from the end of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the time period may start during the last time resource of the one or more time resources comprising the transmission of the HARQ ACK.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 28 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, 25, 26, and/or 27.
  • example embodiments in FIG. 28 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC).
  • Example embodiments in FIG. 28 may comprise the wireless device, transmitting, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure.
  • Example embodiments in FIG. 28 may comprise the wireless device, receiving, from the base station, an indication enabling the LCM procedure based on the request for starting an LCM procedure.
  • Example embodiments in FIG. 28 may comprise the wireless device performing an LCM procedure based on the reception of the indication enabling the LCM procedure.
  • Example embodiments in FIG. 28 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 28 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 28 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a wireless device may trigger an LOM procedure for a RAC based on one or more criteria. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
  • the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK.
  • the request for starting an LCM procedure may comprise a request to start, initiate or perform the LCM procedure.
  • the request for starting an LCM procedure may comprise at least an identifier for the LCM procedure.
  • the identifier may comprise one or more bits.
  • the request for starting an LCM procedure may comprise an RRC message.
  • a request for starting an LCM procedure may further comprise an identifier of one or more criteria for triggering, by the wireless device, the LCM procedure.
  • the one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG. 21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK).
  • the identifiers of the one or more criteria may comprise one or more bits.
  • a relation or mapping between the identifiers and the one or more criteria may be pre-determined.
  • an indication enabling the LCM procedure may comprise an RRC message or a MAC- CE.
  • the wireless device may receive, from the base station, an indication enabling the LCM procedure in response to the request for starting an LCM procedure.
  • an indication enabling the LCM procedure may indicate whether to perform, by the wireless device, the LCM procedure.
  • the indication enabling the LCM procedure may comprise a field.
  • the field may comprise two values e.g. a first value and a second value.
  • the first value of the field may indicate not to perform, by the wireless device, the LCM procedure; and the second value of the field may indicate to perform, by the wireless device, the LCM procedure.
  • the field may comprise one or more bits.
  • the first value of the field may be 0 and the second value of the field may be 1.
  • the wireless device may perform an LCM procedure based on the field of the indication enabling the LCM procedure being the second value.
  • the wireless device may not perform an LCM procedure based on the field of the indication enabling the LCM procedure being the first value.
  • the interruption duration may start from the reception of the indication enabling the LCM procedure.
  • the wireless device may receive the indication enabling the LCM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the indication enabling the LCM procedure.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the indication enabling the LCM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication enabling the LCM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the indication enabling the LCM procedure.
  • the interruption duration may start based on a successful decoding, by the wireless device, of the indication enabling the LCM procedure message. In an example, the interruption duration may start after the successful decoding, by the wireless device, of the indication enabling the LCM procedure message.
  • a wireless device communicating with a base station after the interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • 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. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, and/or 28.
  • example embodiments in FIG. 29 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC).
  • Example embodiments in FIG. 29 may comprise the wireless device, transmitting, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure.
  • Example embodiments in FIG. 29 may comprise the wireless device, receiving, from the base station, , an indication enabling the LCM procedure based on the request for starting an LCM procedure.
  • Example embodiments in FIG. 29 may comprise the wireless device performing an LCM procedure based on the reception of the indication enabling the LCM procedure.
  • Example embodiments in FIG. 29 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start from a time period.
  • Example embodiments in FIG. 29 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 29 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a wireless device may trigger an LCM procedure for a RAC based on one or more criteria.
  • the one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
  • the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK.
  • the request for starting an LCM procedure is according to the example embodiments in FIG. 28 (e.g., the request for starting an LCM procedure).
  • the indication enabling the LCM procedure is according to the example embodiments in FIG. 28 (e.g., the indication enabling the LCM procedure).
  • the interruption duration may start after the time period according to the example embodiments in FIG.23.
  • the time period starts from the reception of the indication enabling the LCM procedure.
  • the wireless device may receive the indication enabling the LCM procedure during one or more time resources.
  • the time period may start based on the one or more time resources during which the wireless device may receive the indication enabling the LCM procedure message.
  • the time period may start from the beginning of the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message.
  • the time period may start from the end of the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message.
  • the time period may start during the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message. In an example, the time period may start based on a successful decoding, by the wireless device, of the indication enabling the LCM procedure message. In an example, the time period may start after the successful decoding, by the wireless device, of the indication enabling the LCM procedure message.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • 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 FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, and/or 29.
  • example embodiments in FIG. 30 may comprise a wireless device, receiving, from a node, a request for performing an LCM procedure.
  • Example embodiments in FIG. 30 may comprise the wireless device transmitting, to the base station, an indication for starting an LCM procedure corresponding to the request for performing an LCM procedure.
  • Example embodiments in FIG. 30 may comprise the wireless device performing an LCM procedure based on the transmission of the indication for starting an LCM procedure.
  • Example embodiments in FIG. 30 may comprise the wireless device performing the LCM procedure during an interruption duration.
  • Example embodiments in FIG. 30 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 30 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a request for performing an LCM procedure may comprise at least an identifier of an LCM procedure.
  • a node may comprise a location server e.g. an LMF.
  • the location server may transmit, to a wireless device, the request for performing an LCM procedure using a positioning protocol e.g. an LTE positioning protocol (LPP) message.
  • LPF LTE positioning protocol
  • a node may comprise a core network node e.g. an AMF, an application server etc.
  • the core network node may transmit, to a wireless device, the request for performing an LCM procedure using a core network protocol e.g. a non-access stratum (NAS) message.
  • NAS non-access stratum
  • an indication for starting an LCM procedure may comprise at least an identifier of an LCM procedure.
  • the indication for starting an LOM procedure may further comprise an information corresponding to a positioning measurement.
  • the information corresponding to a positioning measurement may comprise an identifier of the positioning measurement, a name or tag of a positioning measurement, an indication whether the positioning measurement comprise only a downlink component; or only an uplink component; or both a downlink component and an uplink component etc.
  • Examples of a positioning measurement comprising only a downlink component may comprise a RSTD, a positioning reference signal - reference signal received power (PRS- RSRP) etc.
  • An example of a positioning measurement comprising only an uplink component may comprises an angle of department (AOD) etc.
  • Examples of a positioning measurement comprising both a downlink component and an uplink component may comprise an UE Rx-Tx time difference measurement, a round trip time (RTT) etc.
  • the identifier may identify a positioning measurement.
  • the identifier may comprise one or more bits e.g. 3 bits for indicating 8 different positioning measurements.
  • a relation between one or more identifiers and one or more positioning measurements may be pre-determined.
  • the indication for starting an LOM procedure may comprise an RRC message.
  • a reference signal (RS) configuration for positioning may comprise one or more parameters associated with a reference signal for positioning.
  • the reference signal for positioning may comprise a sounding reference signal (SRS), a positioning reference signal (PRS) etc.
  • the reference signal (RS) for positioning may also be a RS resource for positioning or simply a RS resource.
  • the SRS and/or the PRS may also be referred to as a SRS resource and/or a PRS resource respectively.
  • Examples of the one or more parameters associated with the reference signal (RS) for positioning may comprise one or more of: a periodicity of the RS; a RS transmission bandwidth; a numerology of the RS; a number of symbols of the RS; a time offset of the RS; a RS resource set; a RS resource repetition factor etc.
  • Examples of the numerology of the RS may comprise a subcarrier spacing, a slot duration, a symbol duration, a cyclic prefix length etc.
  • Examples of the one or more parameters associated with a PRS may comprise one or more of: a PRS transmission periodicity; a PRS transmission bandwidth; a PRS resource repetition factor; a number of PRS symbols in a PRS resource; a PRS muting pattern; a numerology of a PRS resource; a PRS subcarrier spacing; a PRS slot offset; a PRS resource set periodicity and slot offset; a PRS resource time gap; a number of PRS resources per PRS resource set, etc.
  • Examples of the one or more parameters associated with a SRS may comprise one or more of: a SRS resource set; a number of SRS resources per SRS resource; a number of SRS symbols in the SRS resource; a numerology of a SRS; a subcarrier spacing of a SRS resource etc.
  • the indication for starting an LOM procedure may further comprise a request for modifying a reference signal configuration for positioning.
  • the modifying the reference signal configuration for positioning may also be referred to as altering, updating or changing the reference signal configuration for positioning.
  • a base station may transmit, to the wireless device, a modified reference signal configuration based on the indication for starting an LOM procedure.
  • the wireless device may receive, from the base station, the modified reference signal configuration.
  • the modified reference signal configuration may comprise an RRC message.
  • the wireless device may modify one or more parameters associated with the reference signal configuration for positioning based on the modified reference signal configuration.
  • the wireless device may transmit a reference signal and/or receive a reference signal based on the one or more modified parameters associated with the reference signal configuration.
  • the indication for starting an LOM procedure may further comprise a request for transmitting a reference signal for positioning.
  • the request for transmitting a reference signal for positioning may comprise an RRC message.
  • the reference signal for positioning may comprise an SRS.
  • the request for transmitting the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement.
  • the request for transmitting the reference signal for positioning may be based on an LCM procedure.
  • the wireless device may transmit, to the base station, a request for transmitting a reference signal for positioning based on an LCM procedure comprising a switching from an AI/ML model to a positioning measurement procedure.
  • a wireless device may receive, from a base station, a response message based on or in response to the request for transmitting the reference signal for positioning.
  • the response message may comprise an RRC message.
  • the response message may comprise a reference signal (RS) configuration.
  • the RS configuration may comprise one or more parameters associated with the RS for positioning.
  • the wireless device may transmit a reference signal for positioning based on the response message e.g., based on the RS configuration.
  • the wireless device may perform a positioning measurement based on the reference signal e.g. a SRS. Examples of the positioning measurement may comprise an UE Rx-Tx time difference measurement, a RTT, an AOD etc.
  • the indication for starting an LCM procedure may further comprise a request for stopping, releasing, suspending, ceasing, cancelling, delaying, halting or postponing a transmission, by a wireless device, of a reference signal for positioning.
  • the reference signal for positioning may comprise an SRS.
  • the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the transmission of a reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement.
  • the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the transmission of a reference signal for positioning may be based on an LCM procedure.
  • the LCM procedure may comprise a switching from a positioning measurement procedure to an AI/ML model.
  • the LCM procedure may comprise a switching from a one AI/ML model to another AI/ML model.
  • a wireless device may receive, from a base station, a release message based on or in response to the request for stopping, releasing, suspending, ceasing, cancelling, delaying, halting or postponing the transmitting of the reference signal for positioning.
  • the release message may comprise an RRC message.
  • the release message may indicate the reference signal for positioning may not be transmitted by the wireless device.
  • the release message may further indicate a time duration during which the reference signal for positioning may not be transmitted by the wireless device. The time duration may start from the reception of the release message by the wireless device.
  • the wireless device may stop, release, suspend, cease, cancel, delay, halt or postpone the transmitting of the reference signal for positioning based on the release message.
  • the indication for starting an LOM procedure may further comprise a request for receiving a reference signal for positioning.
  • the receiving a reference signal for positioning may comprise receiving, by the wireless device, the reference signal for performing a positioning measurement e.g. an UE Rx-Tx time difference measurement, a RSTD, a PRS-RSRP etc.
  • the reference signal for positioning may comprise a PRS.
  • the request for receiving the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement.
  • the request for receiving the reference signal for positioning may be based on an LOM procedure.
  • the wireless device may transmit, to the base station, a request for receiving a reference signal for positioning based on an LOM procedure comprising a switching from an AI/ML model to a positioning measurement procedure.
  • a wireless device may receive, from a base station, a response message based on or in response to the request for receiving a reference signal for positioning.
  • the response message may comprise an RRC message.
  • the response message may comprise a reference signal (RS) configuration.
  • the RS configuration may comprise one or more parameters associated with the RS for positioning.
  • the wireless device may receive the reference signal for positioning (e.g., PRS) based on the received RS configuration.
  • the wireless device may perform a positioning measurement (e.g., a RSTD, a PRS-RSRP etc) based on the reference signal for positioning.
  • the indication for starting an LOM procedure may further comprise a request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing transmitting, by a base station, a reference signal for positioning.
  • the indication for starting an LOM procedure may further comprise a request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving, from a base station, a reference signal for positioning.
  • the reference signal for positioning may comprise a PRS.
  • the request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement. In an example, the request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving the reference signal for positioning may be based on an LOM procedure. In an example, the wireless device may transmit, to the base station, a request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving a reference signal for positioning based on an LOM procedure comprising a switching from a positioning measurement procedure to an AI/ML model. [0399] Referring to FIG.
  • a wireless device may receive, from a base station, a response message based on or in response to the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the receiving of the reference signal for positioning.
  • the response message may comprise an RRC message.
  • the response message may indicate the reference signal for positioning being not transmitted.
  • the response message may further indicate a time duration during which the base station may not transmit the reference signal for positioning. The time duration may start from the reception of the response message.
  • the wireless device may stop, suspending, cease, cancel, delay, halt or postpone the receiving of the reference signal for positioning based on the response message.
  • a wireless device may perform an LOM procedure corresponding to the identifier of the LOM procedure comprised in the request for performing an LOM procedure.
  • the LOM procedure may comprise a switching, by the wireless device, an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching an AI/ML model from AI/ML2 model to AI/ML1 model.
  • the LOM procedure may comprise a switching, by the wireless device, from an AI/ML model to a measurement procedure or a switching from a measurement procedure to an AI/ML1 model.
  • the measurement procedure may comprise a positioning measurement procedure.
  • the wireless device may perform a measurement based on the measurement procedure e.g. based on a positioning signal. Examples of the positioning signal comprise one or more of a positioning reference signal (PRS), a sounding reference signal (SRS) etc.
  • the wireless device may perform a positioning measurement based on the positioning measurement procedure.
  • a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria.
  • the one or more criteria for transmitting, to a wireless device, the request for performing an LOM procedure may comprise a positioning measurement.
  • the wireless device may infer or predict the positioning measurement based on a model.
  • the wireless device may perform the positioning measurement based on a positioning measurement procedure. Examples of the positioning measurement may comprise one or more of an RSTD, an UE Rx-Tx time difference, a PRS-RSRP etc.
  • the wireless device may transmit, to the node, the positioning measurement based on the inference.
  • the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement.
  • the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement being larger than a first positioning measurement threshold (TPM1).
  • the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement being smaller than a second positioning measurement threshold (TPM2).
  • the node may transmit, to a wireless device, the request for performing an LOM procedure based on positioning measurement being larger than a third positioning measurement threshold (TPM3) and smaller larger than a fourth positioning measurement threshold (TPM4).
  • TPM1 first positioning measurement threshold
  • TPM2 second positioning measurement threshold
  • TPM3 third positioning measurement threshold
  • TPM4 fourth positioning measurement threshold
  • the one or more criteria for transmitting, to a wireless device, the request for performing an LOM procedure may comprise a positioning measurement accuracy of a positioning measurement.
  • the node may determine the positioning measurement accuracy based on the positioning measurement and a reference value.
  • the node may receive, from the wireless device, the one or more positioning measurements.
  • the wireless device may perform the one or more positioning measurements based on a positioning measurement procedure.
  • the wireless device may infer or predict the one or more positioning measurements based on a model.
  • the reference value may correspond to an expected positioning measurement under one or more conditions. Examples of the one or more conditions comprise an environment, a carrier frequency of the wireless device, a speed of the wireless device etc.
  • Examples of the environment may comprise the wireless device receiving a line of sight (LOS) path of a signal, a non-line of sight (NLOS) path of a signal or a combination of the LOS and the NLOS paths of a signal.
  • the node may determine the positioning measurement accuracy based on a difference between the positioning measurement and the reference value.
  • the node may determine the positioning measurement accuracy based on a magnitude of a difference between the positioning measurement and the reference value.
  • the positioning measurement accuracy may comprise the difference between the positioning measurement and the reference value.
  • the positioning measurement accuracy may comprise the difference between the magnitude of the positioning measurement and the reference value.
  • the node may transmit, to a wireless device, the request for performing an LCM procedure based on the positioning accuracy being larger than a first positioning measurement accuracy threshold (TMA1 ) and smaller larger than a second positioning measurement accuracy threshold (TMA2).
  • TMA1 first positioning measurement accuracy threshold
  • TMA2 second positioning measurement accuracy threshold
  • the interruption duration may start from the transmission of the indication for starting an LCM procedure.
  • the wireless device may transmit the indication for starting the LCM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources time resource during which the wireless device may transmit the indication for starting the LCM procedure.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the indication for starting the LCM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication for starting the LCM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the indication for starting the LCM procedure.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 31 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 31 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, and/or 30.
  • example embodiments in FIG. 31 may comprise a wireless device, receiving, from a node, a request for performing an LCM procedure.
  • Example embodiments in FIG. 31 may comprise the wireless device transmitting, to the base station, an indication for starting an LCM procedure corresponding to the request for performing an LCM procedure.
  • Example embodiments in FIG. 31 may comprise the wireless device performing an LCM procedure based on the transmission of the indication for starting an LCM procedure.
  • Example embodiments in FIG. 31 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start from a time period.
  • Example embodiments in FIG. 31 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 31 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
  • a node is according to example embodiments in FIG.30 (e.g., the node e.g. the location server, the core network node etc.).
  • a request for performing an LCM procedure is according to example embodiments in FIG.30 (e.g., the request for performing an LCM procedure).
  • an indication for starting the LCM procedure is according to example embodiments in FIG.30 (e.g., the indication for starting the LCM procedure).
  • a node may transmit, to a wireless device, the request for performing an LCM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
  • an interruption duration may start after the time period according to the example embodiments in FIG.23.
  • the time period starts from the transmission of the indication for starting an LCM procedure.
  • the wireless device may transmit the indication for starting an LCM procedure during one or more time resources.
  • the time period may start based on the one or more time resources during which the wireless device may transmit the indication for starting an LCM procedure message.
  • the time period may start from the beginning of the last time resource of the one of more time resources comprising the indication for starting an LCM procedure message.
  • the time period may start from the end of the last time resource of the one of more time resources comprising the the indication for starting an LCM procedure message.
  • the time period may start during the last time resource of the one of more time resources comprising the indication for starting an LCM procedure message.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 32 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 32 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, and/or 31.
  • example embodiments in FIG. 32 may comprise a base station, receiving, from a node, an indication that UE starting an LOM procedure.
  • example embodiments in FIG. 32 may comprise a wireless device, receiving, from a node, a request for performing an LOM procedure.
  • Example embodiments in FIG. 32 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 32 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 32 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 32 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
  • an indication that UE starting an LOM procedure may comprise at least an identifier of an LOM procedure.
  • an indication that UE starting an LOM procedure may comprise an NR positioning protocol annex (NRPPa) message.
  • NRPPa NR positioning protocol annex
  • an indication that UE starting an LOM procedure may comprise an NG Application Protocol (NGAP) message.
  • NGAP NG Application Protocol
  • an indication that UE starting an LOM procedure may further comprise an identifier or identity of a wireless device.
  • the identifier may comprise one or more bits.
  • the identifier of the wireless device may comprise a temporary identifier.
  • the temporary identifier may be valid for a duration.
  • temporary identifier may be based on or depend on an RRC state of a wireless device.
  • temporary identifier may be based on or depend on an procedure e.g. a random access procedure, a reception of a paging message, a reception of a data channel (e.g., PDSCH) etc.
  • Examples of the RRC state may comprise a RRC connected state, a RRC inactive state or a RRC idle state.
  • the duration may be pre-determined.
  • An example of the temporary identifier may comprise a Radio Network Temporary Identifier (RNTI).
  • RNTI Radio Network Temporary Identifier
  • the indication that UE starting an LCM procedure may further comprise timing information.
  • the timing information may comprise a reference time.
  • the reference time may comprise one or more of a slot number, a subframe number, a system frame number (SFN), a hyper system frame number (H-SFN), an UTC etc.
  • SFN may range from 0 to 1023.
  • H-SFN may comprise multiple SFN cycles e.g., 10 SFN cycles.
  • the node may transmit, to the wireless device, the request for performing an LCM procedure based on the reference time. In an example, the node may transmit, to the wireless device, the request for performing an LCM procedure from the reference time. In an example, the wireless device may start an LCM procedure based on the reference time. In an example, the wireless device may start an LCM procedure from the reference time.
  • a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g. , the request for performing an LOM procedure).
  • a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g., the request for performing an LOM procedure).
  • a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
  • a node may transmit, to a base station, the indication that UE starting an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
  • the interruption duration may start from the reception of a request for performing an LOM procedure.
  • the wireless device may receive the request for performing an LOM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 33 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 33 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, and/or 32.
  • example embodiments in FIG. 33 may comprise a wireless device, receiving, from a node, a request for performing an LOM procedure.
  • Example embodiments in FIG. 33 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 33 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from a time period.
  • Example embodiments in FIG. 33 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 33 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
  • an indication that UE starting an LOM procedure is according to the example embodiments in FIG.31 (e.g., the indication that UE starting an LOM procedure).
  • a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g., the request for performing an LOM procedure).
  • a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
  • an interruption duration may start after the time period according to the example embodiments in FIG.23.
  • the time period starts from the request for performing an LOM procedure.
  • the wireless device may receive the request for performing an LOM procedure during one or more time resources.
  • the time period may start based on the one or more time resources during which the wireless device may receive the request for performing an LOM procedure.
  • the time period may start from the beginning of the last time resource of the one of more time resources comprising the request for performing an LOM procedure.
  • the time period may start from the end of the last time resource of the one of more time resources comprising the request for performing an LOM procedure.
  • the time period may start during the last time resource of the one of more time resources comprising the request for performing an LOM procedure.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • FIG. 34 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 34 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 , 32, and/or 33.
  • example embodiments in FIG. 34 may comprise a base station, receiving, from a node, a request for starting an LOM procedure for UE.
  • example embodiments in FIG. 34 may comprise a wireless device, receiving, from a base station, a request for performing an LOM procedure.
  • Example embodiments in FIG. 34 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 34 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 34 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 34 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
  • a request for starting an LOM procedure for UE may comprise at least an identifier of an LOM procedure.
  • the request for starting an LOM procedure for UE may further comprise timing information according to the example embodiments in FIG.32 (i.e., the indication that UE starting an LOM procedure).
  • a request for starting an LOM procedure for UE may further comprise an identifier or identity of a wireless device.
  • the identifier of the wireless device may comprise a temporary identifier.
  • An example of the temporary identifier may comprise a Radio Network Temporary Identifier (RNTI).
  • RNTI Radio Network Temporary Identifier
  • a request for starting an LOM procedure for UE may further comprise timing information according to the example embodiments in FIG.30 (e.g., the indication that UE starting an LOM procedure).
  • the interruption duration may start from the reception of a request for performing an LOM procedure.
  • the wireless device may receive the request for performing an LOM procedure during one or more time resources.
  • the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure.
  • the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • FIG. 35 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 35 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, and/or 34.
  • example embodiments in FIG. 35 may comprise a base station, receiving, from a node, a request for starting an LOM procedure for UE.
  • example embodiments in FIG. 35 may comprise a wireless device, receiving, from a base station, a request for performing an LOM procedure.
  • Example embodiments in FIG. 35 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure.
  • Example embodiments in FIG. 35 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from a time period.
  • Example embodiments in FIG. 35 may comprise the wireless device interrupting communication with the base station during the interruption duration.
  • Example embodiments in FIG. 35 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
  • a request for starting an LOM procedure is according to example embodiments in FIG.34 (e.g., the request for starting an LOM procedure).
  • a request for performing an LOM procedure is according to example embodiments in FIG.34 (e.g., the request for performing an LOM procedure).
  • a node may transmit, to a base station, the request for starting an LOM procedure for UE based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
  • an interruption duration may start after the time period according to the example embodiments in FIG.23.
  • the time period may start from the request for performing an LOM procedure.
  • the wireless device may receive the request for performing an LOM procedure during one or more time resources.
  • the time period may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure.
  • the time period may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the time period may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • the time period may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
  • a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
  • the wireless device may halt, suspend, stop, cancel, drop, discard or postpone UL transmissions and/or DL receptions.
  • the wireless device may not transmit an uplink signal to the base station and/or may not receive a downlink signal from the base station.
  • the wireless device may, in response to the LOM procedure being performed (e.g., after the interruption), may resume the at least UL transmissions or DL receptions.
  • the wireless device may transmit an uplink signal to the base station and/or may receive a downlink signal from the base station.
  • a signal may be referred to as a physical signal and/or a physical channel.
  • a physical signal may comprise a reference signal (RS).
  • RS reference signal
  • a downlink RS may comprise a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), Channel Status Information-RS (CSI-RS), Demodulation Reference Signal (DMRS), Synchronization Signal/PBCH block (SSB), a Positioning Reference Signal (PRS) etc.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • CSI-RS Channel Status Information-RS
  • DMRS Demodulation Reference Signal
  • SSB Synchronization Signal/PBCH block
  • PRS Positioning Reference Signal
  • an uplink RS may comprise a Demodulation Reference Signal (DMRS), a Sounding Reference Signal (SRS) etc.
  • a physical channel comprises higher layer information.
  • the higher layer information may comprise a logical channel, a transport channel etc.
  • the logical channel may comprise a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (COCH), a Dedicated Control Channel (DCCH), a Multi-cast Control Channel (MCCH), a Dedicated Traffic Channel (DTCH), a Multicast Traffic Channel (MTCH) etc.
  • a downlink physical channel may comprise a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Broadcast Channel (PBCH) etc.
  • an uplink physical channel may comprise a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH) etc.
  • the wireless device inferring data based on the model for the RAC may comprise inferring one or more of a CSI, a downlink beam, a positioning measurement etc.
  • the wireless device inferring data based on the model for the RAC may comprise inferring a CSI e.g. CQI.
  • the wireless inferring or predicting the CSI may comprise predicting the CSI in time domain.
  • the wireless inferring the CSI may comprise inferring the CSI in spatial-frequency domain.
  • the wireless device may further transmit, to the base station, the inferred CSI.
  • the wireless device inferring data based on the model for the RAC 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 harnesses historical measurement results derived from 'Set B’ to anticipate the best beam in 'Set A’ for one or more future time instances.
  • 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.’
  • 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. gNB) side or at the wireless device side.
  • 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’.
  • the wireless device may predict the beams.
  • the wireless device may further report, to the base station, the predicted beams.
  • the wireless device may trigger (or initiate or start performing) the LCM procedure (e.g., for the RAC).
  • the wireless device may trigger the LCM procedure based on one or more criteria.
  • the one or more criteria may be pre-determined.
  • wireless device may receive a configuration message comprising/indicating the one or more criteria.
  • the wireless device may receive the configuration message from a base station, a core network node or a location server.
  • the wireless device may receive, from the base station, the configuration message by an RRC message.
  • the wireless device may receive, from the location server, the configuration message by an LTE Positioning Protocol (LPP) message.
  • LTP LTE Positioning Protocol
  • the wireless device may receive, from the core network node, the configuration message by a Non-Access Stratum (NAS) message.
  • NAS Non-Access Stratum
  • the interruption duration may be pre-determined.
  • the interruption duration may also be referred to as an interruption period, an interruption length, an interruption window etc.
  • the interruption duration and/or the time period may comprise one or more time resources.
  • the time resource used may comprise any one of: one or more time units, one or more symbols, one or more sub-slots, one or more mini-slots, one or more time slots, one or more subframes and one or more radio frames.
  • a time unit may comprise a length of time. The length of time may be expressed in nanoseconds, milliseconds, seconds, minutes, hours etc.
  • the time period may be pre-determined.
  • the time period may also be referred to as a time duration, a procedure delay, a processing time etc.
  • an indication for starting an LOM procedure may comprise a field indicating a start time of an interruption duration.
  • a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
  • a response message may comprise a field indicating a start time of an interruption duration.
  • an indication enabling the LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
  • an indication for starting an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
  • a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
  • a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
  • the start time of the interruption duration may comprise a time resource number.
  • the time period may comprise a time resource number.
  • the time resource number may comprise a symbol number, a slot number, a subframe number, a radio frame number, a SFN or a H-SFN.
  • the time period may comprise a processing time of a wireless device.
  • the time period may comprise a time for the wireless device for completing one or more ongoing tasks.
  • Examples of the one or more tasks may comprise: performing a measurement, receiving a channel (e.g., PDSCH), transmitting a channel (e.g ., PUSCH), transmitting a feedback channel (e.g., HARQ ACK/NACK etc), transmitting a CSI report etc.
  • the time period may be zero.
  • the time period comprise a processing time of a base station.
  • the time period may comprise a time for the base station for completing one or more ongoing tasks.
  • Examples of the one or more tasks may comprise: receiving a channel (e.g., PUSCH), transmitting a channel (e.g., PDSCH), receiving, from a wireless device, a feedback channel (e.g., HARQ ACK/NACK etc), receiving, from a wireless device a CSI report etc.
  • the time period may be zero.
  • any of the uplink messages may comprise an RRC, an MAC-CE, an Uplink Control Information (UCI), an Hybrid Automatic Repeat Request Acknowledgement/Negative Acknowledgement (HARQ ACK/NACK), an Long Term Evolution (LTE) Positioning Protocol (LPP) or an Non-Access Stratum (NAS) message.
  • RRC Radio Resource Control
  • MAC-CE Uplink Control Information
  • UCI Uplink Control Information
  • HARQ ACK/NACK Hybrid Automatic Repeat Request Acknowledgement/Negative Acknowledgement
  • LTE Long Term Evolution
  • LTP Positioning Protocol
  • NAS Non-Access Stratum
  • any of the downlink messages may comprise an Radio Resource Control (RRC), an Medium Access Control- Control Element (MAC-CE), a Downlink Control Information (DCI), an Long Term Evolution (LTE) Positioning Protocol (LPP) or an Non-Access Stratum (NAS) message.
  • RRC Radio Resource Control
  • MAC-CE Medium Access Control- Control Element
  • DCI Downlink Control Information
  • LTE Long Term Evolution
  • LDP Positioning Protocol
  • NAS Non-Access Stratum
  • a core network node may comprise an Access Management Function (AMF).
  • AMF Access Management Function
  • a location may comprise a Location Management Function (LMF).
  • LMF Location Management Function
  • FIG. 36 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 36 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, and/or 35.
  • a wireless device may trigger an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption period may start based on the triggering of the LOM procedure.
  • the wireless device may determine whether the wireless device is to transmit signals to, and/or receive signals from, the base station during the interruption duration.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 36 illustrates a step of determining whether the wireless device is to transmit to, and/or receive signals from, the base station
  • this feature is optional and may be omitted.
  • the process may proceed directly from performing the LOM during the interruption duration to communicating, after the interruption duration, with the base station (e.g., as illustrated in FIG. 21).
  • the conditional relationship between the steps in FIG. 36 based on the determining may be omitted.
  • FIG. 37 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 37 may be combined with the features previously discussed with reference to FIG. 36.
  • a wireless device may transmit, to a base station, a core network node, or a location server, an indication for starting an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption period may start based on the transmission of the indication for starting an LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 38 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 38 may be combined with the features previously discussed with reference to FIGs. 36 and/or 37.
  • a wireless device may receive, from a base station, a request for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption duration may start based on the reception of the request for performing an LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 39 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 39 may be combined with the features previously discussed with reference to FIGs. 36, 37, and/or 38.
  • a wireless device may receive, from a base station, a request for performing an LOM procedure.
  • the wireless device may transmit, to the base station, a response message corresponding to the request for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption duration may start based on the transmission of the response message.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 40 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 40 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, and/or
  • a wireless device may transmit, to a base station, a request for performing an LOM procedure.
  • the wireless device may receive, from the base station, an indication enabling the LOM procedure based on the request for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption period may start based on the reception of the indication enabling the LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 41 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 41 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39, and/or 40.
  • a wireless device may receive, from a node, a request from node for performing an LOM procedure.
  • the wireless device may transmit, to a base station, an indication to base station for starting LOM procedure based on the request from node for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption duration may start based on the transmission of the indication to base station for starting LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 42 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 42 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39,
  • a wireless device may receive, from a node, a request from node for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption duration may start based on the reception of the request from node for performing an LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.
  • FIG. 43 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • the features illustrated in FIG. 43 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39, 40, 41, and/or 42.
  • a wireless device may receive, from a base station, a request from base station for performing an LOM procedure.
  • the wireless device may perform the LOM procedure during an interruption duration.
  • the interruption duration may start based on the reception of the request from the base station for performing an LOM procedure.
  • the wireless device may not communicate, during interruption duration, with a base station.
  • the wireless device may communicate, after interruption duration, with a base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method comprises receiving, by a wireless device from a node, a first message triggering a life cycle management (LCM) procedure for a radio access communication. The method comprises performing the LCM procedure, wherein an interruption occurs, in communications with a base station, during the LCM procedure.

Description

TITLE
Timing for Life Cycle Management
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional Application No. 63/634,749, filed April 16, 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. 1 A and FIG. 1 B 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 more PUCCH groups.
[0015] FIG. 11A illustrates an example of an SS/PBCH block structure and location.
[0016] FIG. 11B 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 COE-to-REG mapping for DOI 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. 160, 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] FIG. 24 illustrates an aspect 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.
[0037] FIG. 31 illustrates an aspect of an example embodiment according to the present disclosure.
[0038] FIG. 32 illustrates an aspect of an example embodiment according to the present disclosure.
[0039] FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.
[0040] FIG. 34 illustrates an aspect of an example embodiment according to the present disclosure.
[0041] FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.
[0042] FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.
[0043] FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure.
[0044] FIG. 38 illustrates an aspect of an example embodiment according to the present disclosure.
[0045] FIG. 39 illustrates an aspect of an example embodiment according to the present disclosure.
[0046] FIG. 40 illustrates an aspect of an example embodiment according to the present disclosure.
[0047] FIG. 41 illustrates an aspect of an example embodiment according to the present disclosure.
[0048] FIG. 42 illustrates an aspect of an example embodiment according to the present disclosure.
[0049] FIG. 43 illustrates an aspect of an example embodiment according to the present disclosure.
DETAILED DESCRIPTION
[0050] 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 and advantages, 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.
[0051] 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. [0052] 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.
[0053] 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. [0054] 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 “employin g/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase
“employin g/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.
[0055] 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.
[0056] 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.
[0057] 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 the three possible features, with any two of the three possible features or with three of the three possible features. [0058] 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 LabVI EWMathScript. 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, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (OPLDs). 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.
[0059] FIG. 1A 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.
[0060] 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.
[0061] 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. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques.
[0062] 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.
[0063] 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).
[0064] 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.
[0065] 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/similar functions 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.
[0066] 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.
[0067] 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. 1 A, 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.
[0068] 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. 1B, 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. 1A.
[0069] 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 ON 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 network functions. 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).
[0070] As illustrated in FIG. 1B, 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. [0071] 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 ON and a UE, and AS may refer to the functionality operating between the UE and a RAN.
[0072] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B 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).
[0073] 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 of the 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.
[0074] 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. 1B, 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.
[0075] 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-0 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.
[0076] 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.
[0077] 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). Although only oneAMF/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.
[0078] 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.
[0079] 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. 1B.
[0080] 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 (MAGs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDOPs) 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.
[0081] 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.
[0082] 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 messages originate 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-gNB 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.
[0083] 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.
[0084] 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.
[0085] The MACs 212 and 222 may perform multiplexing/demultiplexing 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 (GA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and/or padding. The MAGs 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 MAGs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223. [0086] 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 MAGs 212 and 222.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] 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) and at 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.
[0092] 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.
[0093] 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: [0094] - a paging control channel (POOH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;
[0095] - a broadcast control channel (BOOH) 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;
[0096] - a common control channel (COCH) for carrying control messages together with random access;
[0097] - a dedicated control channel (DOCH) for carrying control messages to/from a specific the UE to configure the UE; and
[0098] - a dedicated traffic channel (DTCH) for carrying user data to/from a specific the UE.
[0099] T ransport 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: [0100] - a paging channel (PCH) for carrying paging messages that originated from the PCCH; [0101] - a broadcast channel (BOH) for carrying the MIB from the BCCH;
[0102] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;
[0103] -- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and
[0104] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling. [0105] 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:
[0106] -- a physical broadcast channel (PBCH) for carrying the MIB from the BOH;
[0107] -- 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;
[0108] -- a physical downlink control channel (PDCCH) for carrying downlink control information (DOI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;
[0109] -- 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;
[0110] -- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and
[0111] -- a physical random access channel (PRACH) for random access.
[0112] 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.
[0113] 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 PDOPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the 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.
[0114] 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 ON. 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.
[0115] 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 control-plane 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.
[0116] 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., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).
[0117] 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 base station. 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. [0118] 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.
[0119] 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.
[0120] 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 by a 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).
[0121] 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.
[0122] 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.
[0123] 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.
[0124] A gNB, 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.
[0125] 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 time-domain 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 a carrier 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.
[0126] 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.
[0127] 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.
[0128] 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 numerologyindependent 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.
[0129] 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 275x12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
[0130] 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.
[0131] 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.
[0132] 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 BMP 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. [0133] 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.
[0134] 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.
[0135] 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).
[0136] 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.
[0137] A base station may sem i-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.
[0138] 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.
[0139] 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). [0140] 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, DOI, expiration of a BWP inactivity timer, and/or an initiation of random access.
[0141] 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 a switching 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 DOI 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 DOI 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 DOI 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 DOI indicating BWP 902 as the active BWP.
[0142] 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.
[0143] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to/from the same UE using carrier aggregation (GA). The aggregated carriers in GA may be referred to as component carriers (00s). When GA is used, there are a number of serving cells for the UE, one for a CO. The 00s may have three configurations in the frequency domain.
[0144] FIG. 10A illustrates the three GA configurations with two 00s. In the intraband, contiguous configuration 1002, the two 00s 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 00s 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 00s are located in frequency bands (frequency band A and frequency band B).
[0145] In an example, up to 3200s may be aggregated. The aggregated 00s may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD). A serving cell for a UE using GA may have a downlink CO. For FDD, one or more uplink 00s 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.
[0146] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The POell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover. The POell may provide the UE with NAS mobility information and the security input. UEs may have different POells. In the downlink, the carrier corresponding to the POell may be referred to as the downlink primary CO (DL POO). In the uplink, the carrier corresponding to the POell may be referred to as the uplink primary CO (UL POO). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the POell 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).
[0147] 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). [0148] 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 self-scheduling. 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.
[0149] 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 UC1 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.
[0150] 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.
[0151] In GA, 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.
[0152] 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) I 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.
[0153] 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.
[0154] 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. 11A) 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 center frequency. 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.
[0155] 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 celldefining 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.
[0156] 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.
[0157] 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.
[0158] 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, average gain, average delay, and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices.
[0159] 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.
[0160] 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.
[0161] 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. [0162] 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.
[0163] 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.
[0164] 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 downlink CSI-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.
[0165] 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-MI MO, 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.
[0166] 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).
[0167] 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.
[0168] 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 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. 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.
[0169] 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-0 F DM)) 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.
[0170] 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.
[0171] 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.
[0172] 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 may employ 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.
[0173] 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, minislot, 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.
[0174] 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 colocated (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.
[0175] 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 more reference 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 (OS l-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.
[0176] 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. 11 B 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. [0177] 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.
[0178] 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.
[0179] 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). [0180] 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.
[0181] 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 sweep from 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.
[0182] 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).
[0183] 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. [0184] 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 RRC_I NACTI VE 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 PUCOH 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.
[0185] 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 31313, and a Msg 41314. 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).
[0186] 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 31313. 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 41314.
[0187] 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. [0188] 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 UE may 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).
[0189] 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.
[0190] 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. [0191] 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_RAMP/NG_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 preamble transmissions 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).
[0192] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 21312 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 PDOCH using a random access RNTI (RA-RNTI). The Msg 21312 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:
[0193] 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 < s_id < 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).
[0194] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 21312). 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 41314) may be 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).
[0195] The Msg 41314 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 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 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. [0196] 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 31313) 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 31313 based on a channel clear assessment (e.g., a listen- before-talk).
[0197] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased 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 21322. The Msg 1 1321 and the Msg 21322 may be analogous in some respects to the Msg 1 1311 and a Msg 21312 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 41314. [0198] 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 may indicate 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).
[0199] 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., recoverySearchSpace/d). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-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.
[0200] 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.
[0201] 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 41314 illustrated in FIG. 13A.
[0202] The UE may initiate the two-step random access procedure in FIG. 130 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.
[0203] 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 the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MOS), 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 PUSCH) may be multiplexed using FDM, 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.
[0204] 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 (I MSI)). 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 MOS); 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).
[0205] 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.
[0206] 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 (DOI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.
[0207] 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).
[0208] 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.
[0209] 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.
[0210] 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 in an 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).
[0211] 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 timefrequency 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. [0212] 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 PDCOH reception in the CORESET.
[0213] 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).
[0214] 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 PDCCH candidates 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).
[0215] 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 (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
[0216] 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 fourteen OFDM 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.
[0217] 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”.
[0218] 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 DOI 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.
[0219] 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.
[0220] 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.
[0221] 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.
[0222] 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. [0223] 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, Ml MO or multi-antenna processing, and/or the like.
[0224] 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 Ml MO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming. In other examples, the wireless device 1502 and/or the base station 1504 may have a single antenna.
[0225] The processing system 1508 and the processing system 1518 maybe 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.
[0226] 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 on-board 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.
[0227] 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 and a 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.
[0228] 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.
[0229] 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.
[0230] 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 complexvalued 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 timedomain 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.
[0231] 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.
[0232] 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 configuration parameters) 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.
[0233] 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.
[0234] 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.
[0235] 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 are federated learning, reinforcement learning, supervised learning, unsupervised learning, etc. Federated learning may also be referred to as a federated training.
[0236] 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 require multiple interactions of the model.
[0237] In an example, a reinforcement learning technique may train an AI/ML model from an input and a feedback signal resulting from the AI/ML model’s output.
[0238] In an example, a supervised learning technique may train an AI/ML model from an input and labels associated with the input data.
[0239] In an example, an unsupervised learning technique may train an AI/ML model from an input without labelled data. [0240] 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 access communication (RAC).
[0241] FIG. 17 illustrates an example of using an AI/ML model per an aspect of the present disclosure. For example, FIG. 17 may illustrate different stages comprising or involving the AI/ML model. A stage may refer to as a mode, a step, an entity, or a unit. The different stages comprising the AI/ML model may also be referred to as involving or belonging to the AI/ML model. A stage of the different stages may be for generating the AI/ML model. A stage of the different stages may be for inference procedure for inferring data based on the AI/ML model.
[0242] In an example as shown in FIG. 17, an AI/ML model generating stage of an AI/ML model may receive training data. The AI/ML model generating stage may generate an output data for inferring data. The inferring data may also be referred to as inferring result. The inferring data may also be referred to as estimating data, determining data, forecasting data or predicting data. In the example in FIG.17, an inferring data stage may receive the output data for an inference from the AI/ML model generating stage. The inferring data stage may infer data based on the output data received from the AI/ML model generating stage.
[0243] FIG. 18 illustrates an example of a procedure for an AI/ML model capability transfer per an aspect of the present disclosure. The procedure may also be referred to as a signaling flow. The procedure may correspond to a wireless device. The wireless device may communicate with a base station. The communication between the wireless device and the base station may be based on the AI/ML model. In an example, the communication may comprise the wireless device inferring (determining, predicting, and/or estimating) one or more measurement e.g. , a channel quality indicator (CSI), a positioning measurement, a downlink beam etc. The communication may further comprise the wireless device transmitting, to a base station, the one or more measurements based on the inferring. The wireless device may transmit or transfer the AI/ML model capability to the base station.
[0244] FIG. 18 illustrates a base station may configure a wireless device to transmit a capability. The capability may comprise an AI/ML model capability of the wireless device. For example, the base station may transmit one or more RRC messages comprising one or more configuration parameters for the wireless device to transmit an AI/ML model capability. In another example, the base station may transmit an inquiry message to the wireless device. The inquiry message may be an RRC message. The inquiry message may indicate a request for the wireless device to transmit the AI/ML model capability of the wireless device to the base station.
[0245] In an example of FIG.18, the AI/ML model capability may indicate that the wireless device supports both stages of the AI/ML model as illustrated in FIG. 17.
[0246] In an example of FIG.18, the AI/ML model capability may indicate that the wireless device may support (e.g., only) an AI/ML model generation stage of the AI/ML model as illustrated in FIG. 17.
[0247] In an example of FIG.18, the AI/ML model capability may indicate that the wireless device may support (e.g., only) an inferring data stage of the AI/ML model as illustrated in FIG. 17. [0248] In an example as shown in FIG. 18, a wireless device may indicate, to a base station, that the wireless device may support one or more AI/ML models, e.g., by RRC.
[0249] FIG. 19 illustrates another example of a procedure for an AI/ML model capability transfer to a location management function (LMF) per an aspect of the present disclosure. The configuring of the UE to transmit AI/ML capability and the transmission of the AI/ML capability by the wireless device is described above with reference to FIG. 18. In an example as shown in FIG. 19, a wireless device may indicate, to the LMF, 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)).
[0250] In an example, wireless device may include, in a capability message (e.g., indicating the AI/ML capability of FIG. 18 and/or FIG. 19), 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 serves as a distinctive identifier for an AI/ML model. A model ID of an AI/ML model enables a mutual understanding between a base station and a wireless device of the AI/ML model. The capability message may include 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 a wireless device. In an example, a condition may comprise a speed range of a wireless device. In an example, a condition may comprise a frequency or frequency range. In an example, a condition may comprise a frequency range. 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 an 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 channel delay spread. In an example a radio channel characteristic may comprise a channel coherence time.
[0251] In an example, a wireless device may train an AI/ML model based on training data.
[0252] In an example, a base station may train an AI/ML model based on training data.
[0253] In an example, a base station may transmit one or more messages to the wireless device. The one or more messages may comprise at least one RRC message. The one or more messages may comprise at least one MAC CE. The one or more messages may comprise 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.
[0254] In an example, the one or more parameters of the AI/ML model may comprise 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 training may be a set of measurement samples. In an example, the wireless device may train an AI/ML model by using the one or more parameters received from the base station.
[0255] 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. The 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) for RLM; and/or beam failure detection (BFD); and/or candidate beam detection (OBD); and/or L1-RSRP; and/or L1-SINR associated with a link recovery procedure (LRP); and/or one or more positioning measurements; and/or one or more layer-3 mobility measurements.
[0256] Examples of the positioning measurement may comprise 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 (OPP); 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.
[0257] Examples of the layer-3 mobility measurement may comprise a pathloss; a reference signal received power (RSRP); a reference signal received quality (RSRQ); a signal to interference and noise ratio (SINR) etc.
[0258] In an example, a wireless device 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 wireless device-side model. A wireless device-side model may also be referred to as a wireless device-based model.
[0259] 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.
[0260] 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 comprise a compressed CSI. The base station may use an AI/ML model based decoder to decode the received data.
[0261] A wireless device may communicate with a base station (and/or an LMF) based on the AI/ML model. For example, the wireless device may transmit one or more message to the base station (and/or LMF) based on the data inferred from the AI/ML model as discussed above.
[0262] A life cycle management (LCM) of an AI/ML model may comprise developing, deploying, managing or maintaining an AI/ML model. In an example, an LCM of an AI/ML model involves performing one or more LCM procedures on the AI/ML model. In an example, an LCM procedure may comprise performing at least one of: 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 and a modification of one or more parameters of the AI/ML model.
[0263] In an example, a wireless device may use a measurement procedure for obtaining a measurement. The using the measurement procedure may also be referred to as applying the measurement procedure. The obtaining a measurement may also be referred to as performing the measurement. In an example, a measurement procedure may comprise performing a measurement based on a signal. In an example, a measurement procedure may comprise performing a measurement based on a signal transmitted by and/or received by the wireless device. In an example, the signal may comprise a reference signal.
[0264] In an example, performing an LCM procedure may comprise: 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; and/or modifying one or more parameters of the AI/ML model.
[0265] In an example, a wireless device may perform an LCM procedure on an AI/ML model stored in the wireless device.
[0266] In an example, a base station may perform an LCM procedure on an AI/ML model stored in the base station. [0267] 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/ML 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.
[0268] 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 comprise, 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, or cancelling a signal.
[0269] A wireless device may use internal resources of the wireless device for performing a Life Cycle Management (LCM) procedure for an AI/ML model. In an example, the internal resources of the wireless device may comprise a memory and/or processor. The wireless device may share the internal resources for performing the LCM procedure and also for performing one or more additional tasks. The one or more additional tasks may comprise at least one of processing data, receiving signal, transmitting signal, performing online and/or offline services (or functionalities or applications or the like) etc. The one or more additional tasks may not correspond, 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 data transmission; and/or data reception. In an example, the wireless device may interrupt communication 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 the communication may comprise not transmitting one or more UL sign als/ch an nels to the base station. The interruption of the communication may comprise not receiving one or more DL signals/channels from the base station.
[0270] The LCM procedure may comprise (or require) 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 communication with the base station due to the reconfiguration of the RF bandwidth of the wireless device.
[0271] For example, the LCM procedure may comprise/require tuning/retuning/changing/reconfiguring one or more RF circuitries. Tuning, retuning, changing or reconfiguring the one or more RF circuitries my result in the interruption of the communication. The RF circuitry may comprise one or more of an RF filter, a power amplifier (PA), a low noise amplifier (LNA), an antenna array, an antenna, an antenna element, a switch etc.
[0272] 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/retrain the AI/ML model. Retraining the AI/ML mode may requires gathering/obtaining a new set of training data corresponding to the AK/ML model. Retraining (or fine tuning) the AI/ML mode may comprising changing/updating one or more meta parameters of the AI/ML model. Retraining (or fine tuning) the AI/ML mode may comprising reconstructing the AI/ML model.
[0273] The LCM procedure may comprise measuring at least one key performance indicator (KPI) corresponding to the AI/ML model. The at least one KPI may demonstrate a performance/accuracy of the AI/ML mode. Measuring the at least one KPI may result in the interruption of the communication as the wireless device may require performing at least one measurement.
[0274] The wireless device may use the at least one KPI for selecting a new AI/ML mode.
[0275] The wireless device may use the at least one KPI for activating a new AI/ML mode and/or deactivating the AI/ML model.
[0276] The wireless device may use the at least one KPI for falling back form the AI/ML mode, e.g. , stop using the AI/ML model.
[0277] FIG. 20 illustrates an example of an LCM procedure per an aspect of the present disclosure. In the example of FIG.20, a wireless device may autonomously perform an LCM procedure. In the example of FIG.20, the LCM procedure may comprise one or more of: a selection of an AI/ML model, a switching of an AI/ML model to another AI/ML model, a deactivation of an AI/ML model, an activation of an AI/ML model and a fallback from an AI/ML model to a measurement procedure.
[0278] 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/activate the AI/ML mode for performing the handover/RLM/BFR or the like.
[0279] In another example, the LCM procedure may be performed after the handover procedure or an RLM procedure or a BFR procedure. Based on/in response to the handover/RLM/BFR procedure, the wireless device may select/acti vate a new AI/ML mode and/or deactivate the AI/ML model.
[0280] In existing technologies, a wireless device may (e.g., autonomously) perform an LCM procedure for an AI/ML model (e.g., as shown in an example in FIG. 20). For example, the wireless device may perform the LCM procedure at any arbitrary time. The autonomously performing the LCM procedure for the AI/ML model (e.g., determining to autonomously perform the LCM procedure) may cause an interruption of communication between the wireless device and a base station. The autonomously performing the LCM procedure for the AI/ML model may result in misalignment between the wireless device and the base station. For example, the base station may incur unexpected interruption of communication with the wireless device. In existing technologies, the base station may not be aware of whether the LCM procedure is ongoing or not at the wireless device. For example, the base station may not distinguish whether the interruption is due to the one or more additional tasks or the LCM procedure. In another example, the base station may not correctly determine a duration of the interruption. In another example, the base station may not correctly determine a location in time, of the interruption.
[0281] In existing technologies, a base station may configure a wireless device, e.g., by RRC, MAC-CE or DCI, to perform an LCM procedure for an AI/ML model. Although the configuration may allow the wireless device to perform the LCM procedure, the LCM procedure may cause an interruption of communication between the wireless device and a base station. The interruption may occur (e.g., start) at an indefinite time point after the wireless receives, from the base station, a configuration message to perform an LCM procedure. For example, due to the sharing of the internal resources of the wireless device, the wireless device may encounter uncertainty in performing the LCM procedure. The measurement of the at least one KPI may occupy the internal resources of the wireless device. Depending on a complexity/size of the AI/ML mode and required data/measurements for the measurement of the at least one KPI, the time point for performing the LCM procedure may be uncertain. In an example, the base station may incur unexpected interruption of communication 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 time point when the wireless device may perform the LCM and/or a duration of the interruption. [0282] In the existing technologies, the performing an 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, PDSCH etc. For example, the performing the LCM procedure may increase UL/DL data latency 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.
[0283] In the existing technologies, the performing an 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.
[0284] In the existing technologies, the performing an 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 an accuracy of a measurement performed by a wireless device on a reference signal.
[0285] In the existing technologies, the performing an LCM procedure for an AI/ML model may waste radio resources (in time and/or 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. [0286] In the existing technologies, the performing an LCM procedure may cause misalignment between a wireless device and a base station. The misalignment may cause an unexpected interruption of communication between the wireless device and the base station. The unexpected interruption may result in loss of data and/or control signaling.
The unexpected interruption may result in unused (e.g., wasted) allocated radio resources e.g., scheduling grant. [0287] 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.
[0288] In an example embodiment, a wireless device may trigger an LCM procedure for a radio access communication (RAC). The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the triggering of the LCM procedure. An interruption of communication with a base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0289] In an example embodiment, a wireless device may trigger an LCM procedure for a RAC. The wireless device, may transmit, to a base station, an indication for starting an LCM procedure in response to triggering the LCM procedure. The indication may include at least an identifier for the LCM procedure. The wireless device may perform the LCM procedure based on the transmission of the indication. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start from the transmission of the indication. An interruption of communication with a base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0290] In an example embodiment, a wireless device, may receive, from a base station, a request for performing an LCM procedure. The request for performing an LCM procedure may include at least an identifier for an LCM procedure. The wireless device may trigger the LCM procedure for a RAC based on the reception of the request for performing an LCM procedure. The wireless device may perform the LCM procedure based on the triggering of the LCM procedure. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start from the reception of the request for performing an LCM procedure. An interruption of communication with a base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0291] In an example embodiment, a wireless device, may receive, from a base station, a request for performing an LCM procedure. The request for performing an LCM procedure may include at least an identifier for an LCM procedure. The wireless device may transmit, to the base station, a response message corresponding to the request for performing an LCM procedure. The wireless device may trigger the LCM procedure for a LAC based on the transmission of the response message. The response message corresponds to the request for performing an LCM procedure. The wireless device may perform the LCM procedure based on the triggering of the LCM procedure. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start from the transmission of the response message. An interruption of communication with a base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption.
Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal. [0292] In an example embodiment, a wireless device triggers an LCM procedure for a RAC. The wireless device, may transmit, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure. The request for performing an LCM procedure may include at least an identifier for the LCM procedure. The wireless device, may receive, from a base station, an indication enabling the LCM procedure based on the request for starting an LCM procedure. The indication enabling the LCM procedure may indicate whether to perform, by the wireless device, the LCM procedure. The wireless device may perform the LCM procedure based on the indication enabling the LCM procedure. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start from the reception of the indication enabling the LCM procedure. An interruption of communication with a base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0293] In an example embodiment, a wireless device, may receive, from a base station, a request for performing an LCM procedure. The request for performing an LCM procedure may include at least an identifier for an LCM procedure. The request for performing an LCM procedure may trigger the LCM procedure for a RAC. The wireless device may transmit, to the base station, an indication for starting an LCM procedure in response to receiving the request for performing an LCM procedure. The request for performing an LCM procedure may indicate that, during the LCM procedure, an interruption of communication with base station may occur. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the transmission of the indication for starting an LCM procedure. The interruption of communication with the base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0294] In an example embodiment, a wireless device, may receive, from a node (e.g., a location server, a core network node etc), a request for performing an LCM procedure. The request for performing an LCM procedure may include at least an identifier for an LCM procedure. The request for performing an LCM procedure may trigger the LCM procedure for a RAC. The wireless device may transmit, to a base station, an indication for starting an LCM procedure in response to receiving the request for performing an LCM procedure. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the transmission of the indication for starting an LCM procedure. The interruption of communication with the base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0295] In an example embodiment, a base station, may receive, from a node (e.g., a location server, a core network node etc), an indication that UE starting an LCM procedure. The indication that UE starting an LCM procedure may include at least an identifier for an LCM procedure and an identifier of a wireless device.
[0296] In an example embodiment, a wireless device, may receive, from a node (e.g., a location server, a core network node etc), a request for performing an LCM procedure. The request for performing an LCM procedure may include at least an identifier for an LCM procedure. The request for performing an LCM procedure may trigger the LCM procedure for a RAC. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the reception of the request for performing an LCM procedure. The interruption of communication with the base station may occur during the interruption duration. The wireless device may communicate with the base station, based on the LCM procedure, after the interruption. Example embodiments of the present disclosure solve the problem of the unexpected interruption. Example embodiments of the present disclosure solve the problem of an unexpected loss of the uplink data; and/or the downlink data; and/or the uplink control signaling; and/or the downlink control signaling; and/or the uplink reference signal; and/or the downlink reference signal.
[0297] In an example embodiment, a base station, may receive, from a node (e.g., a location server, a core network node etc), a request for starting an LCM procedure for UE. The request for starting an LCM procedure for UE may include at least an identifier for an LCM procedure and an identifier of a wireless device. The base station, may transmit, to the wireless device a request for performing an LCM procedure based on the request for starting an LCM procedure for UE. The wireless device may perform the LCM procedure during an interruption duration. The interruption duration may start based on the reception of the request for performing an LCM procedure.
[0298] FIG. 21 illustrates an example for an LCM procedure as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 21 may be combined with the features previously discussed with reference to FIGs. 18, 19, and/or 20.
[0299] As shown in FIG. 21 a wireless device may trigger the LCM procedure for a radio access communication (RAC). The wireless device may perform the LCM procedure during an interruption duration (e.g., based on the LCM procedure illustrated in FIG. 20). The interruption duration may start based on (or in response to or after) the triggering of the LCM procedure. Example embodiments in FIG. 21 may comprise the wireless device interrupting communication with the base station during the interruption duration. As shown in FIG. 21, the wireless device may communicate with the base station, based on the LCM procedure, after the interruption. [0300] In an example, the interruption duration may start in response to the triggering of the LCM procedure. In an example, the interruption duration may start after the triggering of the LCM procedure. The LCM procedure may be triggered during a time resource. The time resource may comprise a symbol, a slot, a subframe, or a radio frame. In an example, the interruption duration may start during the time resource. In an example, the interruption duration may start from the beginning of the time resource. In an example, the interruption duration may start after the end of the time resource or immediately after the end of the time resource.
[0301] In an example, a wireless device communicating with a base station, based on the LCM procedure, may comprise inferring data based on a model for a RAC.
[0302] The one or more criteria for triggering an LCM procedure may comprise (or be based on) one or more radio channel characteristics (or measurements). In an example a radio channel characteristic of the one or more radio channel characteristics may comprise a Doppler frequency. In an example a radio channel characteristic of the one or more radio channel characteristics may comprise a channel delay spread. In an example a radio channel characteristic of the one or more radio channel characteristics may comprise a channel coherence time.
[0303] In an example, the wireless device 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, CSI-RS, DMRS etc. In an example, the wireless device may estimate the one or more radio channel characteristics by measuring the signal. For example, the wireless device may trigger the LCM procedure based on the Doppler frequency (Df) of the wireless device being below a first Doppler threshold (TD1). For example, the wireless device may trigger the LCM procedure based on the Doppler frequency (Df) estimated by the wireless device being above a second Doppler threshold (TD2). For example, the wireless device may trigger the LCM procedure based on the channel delay spread estimated by the wireless device being below a first delay spread threshold (TD1). For example, the wireless device may trigger the LCM procedure based on the channel delay spread estimated by the wireless device being above a second delay spread threshold (TSD2). For example, the wireless device may trigger the LCM procedure based on the channel coherence time estimated by the wireless device being below a first coherence time threshold (TCC1). For example, the wireless device may trigger the LCM procedure based on the channel coherence time estimated by the wireless device 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, the wireless device may receive a configuration comprising TD1, TD2, TD1, TSD2, TCC1 and TCC2. The wireless device may receive the configuration by an RRC message.
[0304] The LCM procedure performed during the interruption duration may comprise one or more of the steps illustrated above in FIG. 20. For example, the LCM procedure may comprise an activation of an AI/ML model or a deactivation of the AI/ML model. In an example, a wireless device may trigger the activation of the AI/ML model, e.g., based on the Df of the wireless device being below TD1. In an example, a wireless device may trigger the deactivation of the AI/ML model based on the Df of the wireless device being above TD2. [0305] The one or more criteria for triggering an LCM may comprise a location of the wireless device. The location of the wireless device may also be referred to as a position or a geographic location or a footprint of the wireless device. For example, a wireless device may determine a location of the wireless device based on a positioning measurement. For example, a wireless device 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, a wireless device may receive a location information from a location server. For example, a wireless device may determine a location of the wireless device based on the received location information. For example, the location of the wireless device may change over time. For example, the wireless device may trigger the LCM procedure if the location of the wireless device changes. For example, the wireless device may trigger the LCM procedure based on a distance between a current location and a previous location of the wireless device. For example, the wireless device may trigger the LCM procedure based on a distance between the current and the previous location of the wireless device being more than a first distance threshold (TL1). In an example, TL1 may be pre-determined. In an example, the wireless device may receive a configuration comprising TL1. The wireless device may receive the configuration by an RRC message.
[0306] As another example, the LCM procedure performed during the interruption duration 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, a wireless device 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 the wireless device being more than TL1. In an example, a wireless device 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 the wireless device being less than or equal to TL1.
[0307] The one or more criteria for triggering an LCM procedure may comprise 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, a RS may comprise a SSB, CSI-RS, DMRS etc. In an example, a wireless device may measure on a 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 (SI NR), 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 DSQ threshold (TDQ2). In an example, TDQ1 and TDQ2 may be pre-determined. In an example, the wireless device may receive a configuration comprising TDQ1 and TDQ2. The wireless device may receive the configuration by an RRC message. [0308] The LCM procedure may comprise a switching an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching 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 a wireless device being below TDQ1. In an example, a wireless device may trigger a switching an AI/ML model from AI/ML1 to AI/ML2 based on a DSQ estimated by the wireless device being below TDQ1. In an example, a wireless device may trigger a switching an AI/ML model from AI/ML2 to AI/ML1 based on a DSQ estimated by the wireless device being above TDQ2.
[0309] The one or more criteria for triggering an LCM procedure may comprise an HARQ ACK/NACK. A wireless device may transmit, to a base station, the HARQ ACK/NACK message in response to receiving, from a base station, a data channel e.g. PDSCH. In an example, the wireless device may transmit, to the base station, an ACK in response to correctly decoding the data channel. In an example, the wireless device 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 the wireless device during a first HARQ time period (Tp1). In an example, a wireless device may trigger an LCM procedure based on a number of ACKs during Tp1 being below a first ACK threshold (TAK1). In an example, a wireless device 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, a wireless device may trigger an LCM procedure based on a number of NACKs during Tp1 being above a second NACK threshold (TNK2). In an example, TAK1, TAK2, TNK1 and TNK2 may be pre-determined. In an example, the wireless device may receive a configuration comprising TAK1, TAK2, TNK1 and TNK2. The wireless device may receive the configuration by an RRC message.
[0310] The wireless device communicating with a base station after the interruption duration may comprise, the wireless device transmitting a signal (e.g., an uplink singal or an uplink message)) to the base station and/or receiving a signal (e.g., a downlink signal or downlink message) from the base station.
[0311] FIG. 22 illustrates an example 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. 18, 19, 20 and/or 21.
[0312] For example, example embodiments in FIG. 22 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC). Example embodiments in FIG. 22 may comprise the wireless device, transmitting, to a base station, an indication for starting an LCM procedure in response to triggering the LCM procedure. Example embodiments in FIG. 22 may comprise the wireless device performing the LCM procedure based on the transmission of the indication for staring the LCM procedure. Example embodiments in FIG. 22 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 22 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 22 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0313] Referring to FIG. 22, the indication for starting the LCM procedure may comprise at least an identifier for the LCM procedure. In an example, each LCM procedure may be associated with an identifier (ID). In an example, the identifier may comprise one or more bits. In an example, the indication for starting the LCM procedure may comprise an RRC message.
[0314] Referring to FIG. 22, a wireless device may trigger an LCM procedure for a RAC based on one or more criteria. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK).
[0315] Referring to FIG. 22, an interruption duration may start from the transmission of the indication for starting an LCM procedure. In an example, the wireless device may transmit the indication for starting an LCM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources comprising the indication for starting an LCM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication for starting an LCM procedure. In an example, the interruption duration may start from the end of the one or more time resources comprising the indication for starting an LCM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
[0316] Referring to FIG. 22, a wireless device communicating with a base station after the interruption may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
[0317] FIG. 23 illustrates an example 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. 18, 19, 20, 21, and/or 22.
[0318] For example, example embodiments in FIG. 23 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC). Example embodiments in FIG. 23 may comprise the wireless device, transmitting, to a base station, an indication for starting the LCM procedure in response to triggering the LCM procedure. Example embodiments in FIG. 23 may comprise the wireless device performing the LCM procedure based on the transmission of the indication for starting the LCM procedure. Example embodiments in FIG. 23 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start after a time period. The time period may start from the transmission of the indication for starting the LCM procedure. Example embodiments in FIG. 23 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 23 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0319] Referring to FIG. 23, the indication for starting the LCM procedure is according to the example embodiments in FIG. 22 (e.g., the indication for starting the LCM procedure).
[0320] Referring to FIG. 23, a first time period may start from the transmission of the indication for starting an LCM procedure. In an example, the wireless device may transmit the indication for starting an LCM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources comprising the indication for starting an LCM procedure. In an example, the time period may start from the beginning of the last time resource of the one or more time resources comprising the indication for starting an LCM procedure. In an example, the time period may start from the end of the last time resource comprising the indication for starting an LCM procedure. In an example, the time period may start during the last time resource of the one or more time resources comprising the indication for starting an LCM procedure.
[0321] Referring to FIG. 23, in an example, an interruption duration may start immediately after the time period. The time period may comprise one or more time resources. In an example, the interruption duration may start after the end of the last time resource of the one or more time resources comprising the time period. In an example, the interruption duration may start immediately after the end of the last time resource of the one or more time resources comprising the time period. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the time period.
[0322] Referring to FIG. 23, a wireless device may trigger an LCM procedure for a RAC based on one or more criteria. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK).
[0323] Referring to FIG. 23, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0324] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 24 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, and/or 23.
[0325] For example, example embodiments in FIG. 24 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure. Example embodiments in FIG. 24 may comprise the wireless device triggering an LCM procedure based on the reception of the request for performing an LCM procedure. Example embodiments in FIG. 24 may comprise the wireless device performing an LCM procedure based on the triggering of LCM procedure. Example embodiments in FIG. 24 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 24 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 24 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0326] Referring to FIG. 24, the request for performing an LCM procedure may comprise at least an identifier for the LCM procedure. In an example, each LCM procedure may be associated with an identifier. In an example, the identifier may comprise one or more bits. In an example, the request for performing an LCM procedure may comprise an RRC message.
[0327] Referring to FIG. 24, a base station may transmit, to a wireless device, the request for performing an LCM procedure based on one or more criteria. [0328] The one or more criteria for transmitting, to a wireless device, the request for performing an LCM procedure may comprise an uplink signal quality. In an example, a base station may estimate an uplink signal quality (USQ) based on an uplink reference signal (URS). The URS may be transmitted by the wireless device. In an example, an URS may comprise SRS, UL-DMRS etc. In an example, a base station may measure an URS to estimate an uplink signal quality. In an example, the uplink signal quality may comprise a signal to noise ratio (SNR), a signal to noise and interference radio (SI NR) etc. In an example, a base station may transmit, to a wireless device, a request for performing an LCM procedure based on an USQ being below a first USQ threshold (TUQ1). In an example, may transmit, to a wireless device, a request for performing an LCM procedure based on an USQ being above a second USQ threshold (TUQ2). [0329] Referring to FIG. 24, the one or more criteria for triggering an LCM procedure may comprise an HARQ ACK/NACK. A wireless device may transmit, to a base station, the HARQ ACK/NACK message in response to receiving, from a base station, a data channel e.g. PDSCH. In an example, the wireless device may transmit, to the base station, an ACK in response to correctly decoding the data channel. In an example, the wireless device may transmit, to the base station, a NACK in response to incorrectly decoding the data channel. In an example, a base station may trigger an LCM procedure based on a number of ACKs and/or a number of NACKs received from the wireless device during a second HARQ time period (Tp2). In an example, a base station may trigger an LCM procedure based on a number of ACKs during Tp2 being below a third ACK threshold (TAK3). In an example, a base station may trigger an LCM procedure based on a number of ACKs during Tp2 being above a fourth ACK threshold (TAK4). In an example, a wireless device may trigger an LCM procedure based on a number of NACKs during Tp2 being below a third NACK threshold (TNK3). In an example, a base station may trigger an LCM procedure based on a number of NACKs during Tp2 being above a fourth NACK threshold (TNK4).
[0330] Referring to FIG. 24, a request for performing an LCM procedure may comprise an identifier of an LCM procedure. The wireless device may perform an LCM procedure corresponding to the identifier of the LCM procedure comprised in the request for performing an LCM procedure. The LCM procedure may comprise a switching, by the wireless device, an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching 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 an USQ estimated by a base station being above TUQ2. In an example, AI/ML1 may be suitable for a scenario based on an USQ estimated by a base station being below TUQ1. In an example, the request for performing an LCM procedure may indicate switching an AI/ML model from AI/ML1 to AI/ML2 based on an USQ estimated by the base station being below TUQ1. In an example, the request for performing an LCM procedure may indicate switching an AI/ML model from AI/ML2 to AI/ML1 based on an USQ estimated by the base station being above TUQ2.
[0331] Referring to FIG. 24, in an example, an interruption duration may start from the reception of the request for performing an LCM procedure. In an example, the wireless device may receive the request for performing an LCM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LCM procedure. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LCM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LCM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LCM procedure. In an example, the interruption duration may start based on a successful decoding, by the wireless device, of the request for performing an LCM procedure message. In an example, the interruption duration may start after the successful decoding, by the wireless device, of the request for performing an LCM procedure message.
[0332] Referring to FIG. 24, a wireless device communicating with a base station after interruption may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station.
[0333] FIG. 25 illustrates an example 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. 18, 19, 20, 21, 22, 23, and/or 24.
[0334] For example, example embodiments in FIG. 25 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure. Example embodiments in FIG. 25 may comprise the wireless device triggering an LCM procedure based on the reception of the second message. Example embodiments in FIG. 25 may comprise the wireless device performing an LCM procedure based on the triggering of LCM procedure. Example embodiments in FIG. 25 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start after a time period. Example embodiments in FIG. 25 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 25 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0335] Referring to FIG. 25, the request for performing an LCM procedure is according to the example embodiments in FIG. 24 (e.g., the request for performing an LCM procedure).
[0336] Referring to FIG. 25, a base station may transmit the request for performing an LCM procedure based on one or more criteria. The one or more criteria are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and the HARQ ACK/NACK).
[0337] Referring to FIG. 25, in an example, a time period may start from the reception of the request for performing an LCM procedure.
[0338] In an example, the wireless device may receive the request for performing an LCM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources during which the wireless device may receive the request for performing an LCM procedure. In an example, the time period may start from the beginning of the last time resource of the one of more time resources comprising the request for performing an LCM procedure message. In an example, the time period may start from the end of the last time resource of the one of more time resources comprising the request for performing an LCM procedure message. In an example, the time period may start during the last time resource of the one of more time resources comprising the request for performing an LCM procedure message. In an example, the time period may start based on a successful decoding, by the wireless device, of the request for performing an LCM procedure message. In an example, the time period may start after the successful decoding, by the wireless device, of the request for performing an LCM procedure message.
[0339] Referring to FIG. 25, the interruption duration may start after the time period according to the example embodiments in FIG.23.
[0340] Referring to FIG. 25, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0341] FIG. 26 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, and/or 25.
[0342] For example, example embodiments in FIG. 26 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure. Example embodiments in FIG. 26 may comprise the wireless device transmitting, to the base station, a response message corresponding to the request for performing an LCM procedure. Example embodiments in FIG. 26 may comprise the wireless device performing an LCM procedure based on the transmission of the response message. Example embodiments in FIG. 26 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 26 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 26 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0343] Referring to FIG. 26, a base station may transmit a request for performing an LCM procedure based on one or more criteria. The one or more criteria are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and/or the HARQ ACK/NACK).
[0344] Referring to FIG. 26, in an example, a request for performing an LCM procedure is according to the example embodiments in FIG. 24 (e.g., the request for performing an LCM procedure).
[0345] Referring to FIG. 26, in another example, a request for performing an LCM procedure may be a MAC-CE. [0346] Referring to FIG. 26, a response message may comprise a feedback signal corresponding to request for performing an LCM procedure. In an example, the feedback signal may comprise a HARQ message. In an example, the feedback signal comprising the HARQ message may be in response to the request for performing LCM procedure comprising an MAC-CE. In an example, the HARQ message may comprise an acknowledgement (ACK) message or a negative acknowledgement (NACK) message. In an example, the HARQ message may comprise one or more bits. In an example, a bit 1 may comprise the ACK message; and a bit 0 may comprise the NACK message. In an example, the wireless device may transmit the ACK message in response to successful decoding of the request for performing an LCM procedure message. In an example, the wireless device may transmit the NACK message in response to unsuccessful decoding of the request for performing an LCM procedure message.
[0347] Referring to FIG. 26, the interruption duration may start from the transmission of the response message. [0348] Referring to FIG. 26, in an example, the interruption duration may start based on the transmission of the response message comprising an HARQ ACK. In an example, the interruption duration may start from the transmission of the response message comprising an HARQ ACK.
[0349] Referring to FIG. 26, the wireless device may transmit the response message during one or more time resources.
[0350] In an example, the interruption duration may start from the beginning of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the transmission of the response message. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the transmission of the response message.
[0351] In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the transmission of the HARQ ACK.
[0352] Referring to FIG. 26, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0353] FIG. 27 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, 25, and/or 26.
[0354] For example, example embodiments in FIG. 27 may comprise a wireless device, receiving, from a base station, a request for performing an LCM procedure. Example embodiments in FIG. 27 may comprise the wireless device transmitting, to the base station, a response message corresponding to the request for performing an LCM procedure. Example embodiments in FIG. 27 may comprise the wireless device performing an LCM procedure based on the transmission of the response message. Example embodiments in FIG. 27 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 27 may comprise the wireless device interrupting communication with the base station during the interruption duration. The interruption duration may start after a time period. Example embodiments in FIG. 27 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0355] Referring to FIG. 27, a request for performing an LCM procedure is according to the example embodiments in FIG. 26 (e.g. the request for performing an LCM procedure). [0356] Referring to FIG. 27, a response message is according to the example embodiments in FIG. 26 (e.g., the response message).
[0357] Referring to FIG. 27, a base station may transmit a request for performing an LOM procedure based on one or more criteria. The one or more criteria for transmitting the request for performing an LOM procedure are according to the example embodiments in FIG. 24 (e.g., the uplink signal quality and the HARQ ACK/NACK).
[0358] Referring to FIG. 27, the interruption duration may start after the time period according to the example embodiments in FIG.23.
[0359] Referring to FIG. 27, the time period may start from the transmission of the response message. In an example, the wireless device may transmit the response message during one or more time resources.
[0360] In an example, the time period may start from the beginning of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the time period may start from the end of last time resource of the one or more time resources comprising the transmission of the response message. In an example, the time period may start during the last time resource of the one or more time resources comprising the transmission of the response message.
[0361] In an example, the time period may start from the beginning of last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the time period may start from the end of the last time resource of the one or more time resources comprising the transmission of the HARQ ACK. In an example, the time period may start during the last time resource of the one or more time resources comprising the transmission of the HARQ ACK.
[0362] Referring to FIG. 27, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0363] FIG. 28 illustrates an example 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. 18, 19, 20, 21, 22, 23, 24, 25, 26, and/or 27.
[0364] For example, example embodiments in FIG. 28 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC). Example embodiments in FIG. 28 may comprise the wireless device, transmitting, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure. Example embodiments in FIG. 28 may comprise the wireless device, receiving, from the base station, an indication enabling the LCM procedure based on the request for starting an LCM procedure. Example embodiments in FIG. 28 may comprise the wireless device performing an LCM procedure based on the reception of the indication enabling the LCM procedure. Example embodiments in FIG. 28 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 28 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 28 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption. [0365] Referring to FIG. 28, a wireless device may trigger an LOM procedure for a RAC based on one or more criteria. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK).
[0366] Referring to FIG. 28, the request for starting an LCM procedure may comprise a request to start, initiate or perform the LCM procedure. The request for starting an LCM procedure may comprise at least an identifier for the LCM procedure. In an example, the identifier may comprise one or more bits. In an example, the request for starting an LCM procedure may comprise an RRC message.
[0367] Referring to FIG. 28, a request for starting an LCM procedure may further comprise an identifier of one or more criteria for triggering, by the wireless device, the LCM procedure. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG. 21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK). In an example, the identifiers of the one or more criteria may comprise one or more bits. In an example, a relation or mapping between the identifiers and the one or more criteria may be pre-determined.
[0368] Referring to FIG. 28, an indication enabling the LCM procedure may comprise an RRC message or a MAC- CE.
[0369] Referring to FIG. 28, in an example, the wireless device may receive, from the base station, an indication enabling the LCM procedure in response to the request for starting an LCM procedure.
[0370] Referring to FIG. 28, in an example an indication enabling the LCM procedure may indicate whether to perform, by the wireless device, the LCM procedure. In an example, the indication enabling the LCM procedure may comprise a field. In an example, the field may comprise two values e.g. a first value and a second value. In an example, the first value of the field may indicate not to perform, by the wireless device, the LCM procedure; and the second value of the field may indicate to perform, by the wireless device, the LCM procedure. In an example, the field may comprise one or more bits. In an example, the first value of the field may be 0 and the second value of the field may be 1. For example, the wireless device may perform an LCM procedure based on the field of the indication enabling the LCM procedure being the second value. For example, the wireless device may not perform an LCM procedure based on the field of the indication enabling the LCM procedure being the first value.
[0371] Referring to FIG. 28, the interruption duration may start from the reception of the indication enabling the LCM procedure.
[0372] In an example, the wireless device may receive the indication enabling the LCM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the indication enabling the LCM procedure. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the indication enabling the LCM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication enabling the LCM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the indication enabling the LCM procedure. In an example, the interruption duration may start based on a successful decoding, by the wireless device, of the indication enabling the LCM procedure message. In an example, the interruption duration may start after the successful decoding, by the wireless device, of the indication enabling the LCM procedure message.
[0373] Referring to FIG. 28, a wireless device communicating with a base station after the interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0374] 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. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, and/or 28.
[0375] For example, example embodiments in FIG. 29 may comprise a wireless device triggering an LCM procedure for a radio access communication (RAC). Example embodiments in FIG. 29 may comprise the wireless device, transmitting, to a base station, a request for starting an LCM procedure in response to triggering the LCM procedure. Example embodiments in FIG. 29 may comprise the wireless device, receiving, from the base station, , an indication enabling the LCM procedure based on the request for starting an LCM procedure. Example embodiments in FIG. 29 may comprise the wireless device performing an LCM procedure based on the reception of the indication enabling the LCM procedure. Example embodiments in FIG. 29 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start from a time period. Example embodiments in FIG. 29 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 29 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0376] Referring to FIG. 29, a wireless device may trigger an LCM procedure for a RAC based on one or more criteria. The one or more criteria for triggering the LCM procedure are according to the example embodiments in FIG.
21 (e.g., the radio channel characteristics, the location of the wireless device, the downlink signal quality and the HARQ ACK/NACK).
[0377] Referring to FIG. 29, the request for starting an LCM procedure is according to the example embodiments in FIG. 28 (e.g., the request for starting an LCM procedure).
[0378] Referring to FIG. 29, the indication enabling the LCM procedure is according to the example embodiments in FIG. 28 (e.g., the indication enabling the LCM procedure).
[0379] Referring to FIG. 29, the interruption duration may start after the time period according to the example embodiments in FIG.23.
[0380] Referring to FIG. 29, in an example, the time period starts from the reception of the indication enabling the LCM procedure. [0381] In an example, the wireless device may receive the indication enabling the LCM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources during which the wireless device may receive the indication enabling the LCM procedure message. In an example, the time period may start from the beginning of the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message. In an example, the time period may start from the end of the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message. In an example, the time period may start during the last time resource of the one of more time resources comprising the indication enabling the LCM procedure message. In an example, the time period may start based on a successful decoding, by the wireless device, of the indication enabling the LCM procedure message. In an example, the time period may start after the successful decoding, by the wireless device, of the indication enabling the LCM procedure message.
[0382] Referring to FIG. 29, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0383] 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 FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, and/or 29.
[0384] For example, example embodiments in FIG. 30 may comprise a wireless device, receiving, from a node, a request for performing an LCM procedure. Example embodiments in FIG. 30 may comprise the wireless device transmitting, to the base station, an indication for starting an LCM procedure corresponding to the request for performing an LCM procedure. Example embodiments in FIG. 30 may comprise the wireless device performing an LCM procedure based on the transmission of the indication for starting an LCM procedure. Example embodiments in FIG. 30 may comprise the wireless device performing the LCM procedure during an interruption duration. Example embodiments in FIG. 30 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 30 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0385] Referring to FIG. 30, a request for performing an LCM procedure may comprise at least an identifier of an LCM procedure.
[0386] Referring to FIG. 30, a node may comprise a location server e.g. an LMF. In an example, the location server may transmit, to a wireless device, the request for performing an LCM procedure using a positioning protocol e.g. an LTE positioning protocol (LPP) message.
[0387] Referring to FIG. 30, a node may comprise a core network node e.g. an AMF, an application server etc. In an example, the core network node may transmit, to a wireless device, the request for performing an LCM procedure using a core network protocol e.g. a non-access stratum (NAS) message.
[0388] Referring to FIG. 30, an indication for starting an LCM procedure may comprise at least an identifier of an LCM procedure. [0389] Referring to FIG. 30, in an example, the indication for starting an LOM procedure may further comprise an information corresponding to a positioning measurement. Examples of the information corresponding to a positioning measurement may comprise an identifier of the positioning measurement, a name or tag of a positioning measurement, an indication whether the positioning measurement comprise only a downlink component; or only an uplink component; or both a downlink component and an uplink component etc. Examples of a positioning measurement comprising only a downlink component may comprise a RSTD, a positioning reference signal - reference signal received power (PRS- RSRP) etc. An example of a positioning measurement comprising only an uplink component may comprises an angle of department (AOD) etc. Examples of a positioning measurement comprising both a downlink component and an uplink component may comprise an UE Rx-Tx time difference measurement, a round trip time (RTT) etc. The identifier may identify a positioning measurement. The identifier may comprise one or more bits e.g. 3 bits for indicating 8 different positioning measurements. In an example, a relation between one or more identifiers and one or more positioning measurements may be pre-determined. In an example, the indication for starting an LOM procedure may comprise an RRC message.
[0390] In an example, a reference signal (RS) configuration for positioning (or simply a RS configuration) may comprise one or more parameters associated with a reference signal for positioning. Examples of the reference signal for positioning may comprise a sounding reference signal (SRS), a positioning reference signal (PRS) etc. The reference signal (RS) for positioning may also be a RS resource for positioning or simply a RS resource. The SRS and/or the PRS may also be referred to as a SRS resource and/or a PRS resource respectively. Examples of the one or more parameters associated with the reference signal (RS) for positioning may comprise one or more of: a periodicity of the RS; a RS transmission bandwidth; a numerology of the RS; a number of symbols of the RS; a time offset of the RS; a RS resource set; a RS resource repetition factor etc. Examples of the numerology of the RS may comprise a subcarrier spacing, a slot duration, a symbol duration, a cyclic prefix length etc. Examples of the one or more parameters associated with a PRS may comprise one or more of: a PRS transmission periodicity; a PRS transmission bandwidth; a PRS resource repetition factor; a number of PRS symbols in a PRS resource; a PRS muting pattern; a numerology of a PRS resource; a PRS subcarrier spacing; a PRS slot offset; a PRS resource set periodicity and slot offset; a PRS resource time gap; a number of PRS resources per PRS resource set, etc. Examples of the one or more parameters associated with a SRS may comprise one or more of: a SRS resource set; a number of SRS resources per SRS resource; a number of SRS symbols in the SRS resource; a numerology of a SRS; a subcarrier spacing of a SRS resource etc.
[0391] Referring to FIG. 30, in an example, the indication for starting an LOM procedure may further comprise a request for modifying a reference signal configuration for positioning. The modifying the reference signal configuration for positioning may also be referred to as altering, updating or changing the reference signal configuration for positioning. A base station may transmit, to the wireless device, a modified reference signal configuration based on the indication for starting an LOM procedure. The wireless device may receive, from the base station, the modified reference signal configuration. The modified reference signal configuration may comprise an RRC message. In an example, the wireless device may modify one or more parameters associated with the reference signal configuration for positioning based on the modified reference signal configuration. In an example, the wireless device may transmit a reference signal and/or receive a reference signal based on the one or more modified parameters associated with the reference signal configuration.
[0392] Referring to FIG. 30, in an example, the indication for starting an LOM procedure may further comprise a request for transmitting a reference signal for positioning. In an example, the request for transmitting a reference signal for positioning may comprise an RRC message. In an example, the reference signal for positioning may comprise an SRS. In an example, the request for transmitting the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement. In an example, the request for transmitting the reference signal for positioning may be based on an LCM procedure. In an example, the wireless device may transmit, to the base station, a request for transmitting a reference signal for positioning based on an LCM procedure comprising a switching from an AI/ML model to a positioning measurement procedure.
[0393] Referring to FIG. 30, in an example, a wireless device may receive, from a base station, a response message based on or in response to the request for transmitting the reference signal for positioning. The response message may comprise an RRC message. The response message may comprise a reference signal (RS) configuration. The RS configuration may comprise one or more parameters associated with the RS for positioning. In an example, the wireless device may transmit a reference signal for positioning based on the response message e.g., based on the RS configuration. In an example, the wireless device may perform a positioning measurement based on the reference signal e.g. a SRS. Examples of the positioning measurement may comprise an UE Rx-Tx time difference measurement, a RTT, an AOD etc.
[0394] Referring to FIG. 30, in an example, the indication for starting an LCM procedure may further comprise a request for stopping, releasing, suspending, ceasing, cancelling, delaying, halting or postponing a transmission, by a wireless device, of a reference signal for positioning. In an example, the reference signal for positioning may comprise an SRS. In an example, the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the transmission of a reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement. In an example, the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the transmission of a reference signal for positioning may be based on an LCM procedure. In an example, the LCM procedure may comprise a switching from a positioning measurement procedure to an AI/ML model. In another example, the LCM procedure may comprise a switching from a one AI/ML model to another AI/ML model.
[0395] Referring to FIG. 30, in an example, a wireless device may receive, from a base station, a release message based on or in response to the request for stopping, releasing, suspending, ceasing, cancelling, delaying, halting or postponing the transmitting of the reference signal for positioning. The release message may comprise an RRC message. The release message may indicate the reference signal for positioning may not be transmitted by the wireless device. The release message may further indicate a time duration during which the reference signal for positioning may not be transmitted by the wireless device. The time duration may start from the reception of the release message by the wireless device. The wireless device may stop, release, suspend, cease, cancel, delay, halt or postpone the transmitting of the reference signal for positioning based on the release message.
[0396] Referring to FIG. 30, in an example, the indication for starting an LOM procedure may further comprise a request for receiving a reference signal for positioning. In an example, the receiving a reference signal for positioning may comprise receiving, by the wireless device, the reference signal for performing a positioning measurement e.g. an UE Rx-Tx time difference measurement, a RSTD, a PRS-RSRP etc. In an example, the reference signal for positioning may comprise a PRS. In an example, the request for receiving the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement. In an example, the request for receiving the reference signal for positioning may be based on an LOM procedure. In an example, the wireless device may transmit, to the base station, a request for receiving a reference signal for positioning based on an LOM procedure comprising a switching from an AI/ML model to a positioning measurement procedure.
[0397] Referring to FIG. 30, in an example, a wireless device may receive, from a base station, a response message based on or in response to the request for receiving a reference signal for positioning. The response message may comprise an RRC message. The response message may comprise a reference signal (RS) configuration. The RS configuration may comprise one or more parameters associated with the RS for positioning. The wireless device may receive the reference signal for positioning (e.g., PRS) based on the received RS configuration. In an example, the wireless device may perform a positioning measurement (e.g., a RSTD, a PRS-RSRP etc) based on the reference signal for positioning.
[0398] Referring to FIG. 30, in an example, the indication for starting an LOM procedure may further comprise a request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing transmitting, by a base station, a reference signal for positioning. In an example, the indication for starting an LOM procedure may further comprise a request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving, from a base station, a reference signal for positioning. In an example, the reference signal for positioning may comprise a PRS. In an example, the request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving the reference signal for positioning may be based on whether the wireless device may use an AI/ML model for inferring a positioning measurement. In an example, the request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving the reference signal for positioning may be based on an LOM procedure. In an example, the wireless device may transmit, to the base station, a request for stopping, suspending, ceasing, cancelling, halting or postponing the receiving a reference signal for positioning based on an LOM procedure comprising a switching from a positioning measurement procedure to an AI/ML model. [0399] Referring to FIG. 30, in an example, a wireless device may receive, from a base station, a response message based on or in response to the request for stopping, suspending, ceasing, cancelling, delaying, halting or postponing the receiving of the reference signal for positioning. The response message may comprise an RRC message. The response message may indicate the reference signal for positioning being not transmitted. The response message may further indicate a time duration during which the base station may not transmit the reference signal for positioning. The time duration may start from the reception of the response message. The wireless device may stop, suspending, cease, cancel, delay, halt or postpone the receiving of the reference signal for positioning based on the response message. [0400] Referring to FIG. 30, a wireless device may perform an LOM procedure corresponding to the identifier of the LOM procedure comprised in the request for performing an LOM procedure. In an example, the LOM procedure may comprise a switching, by the wireless device, an AI/ML model from a first AI/ML (AI/ML1) model to a second AI/ML (AI/ML2) model or a switching an AI/ML model from AI/ML2 model to AI/ML1 model. In an example, the LOM procedure may comprise a switching, by the wireless device, from an AI/ML model to a measurement procedure or a switching from a measurement procedure to an AI/ML1 model. In an example, the measurement procedure may comprise a positioning measurement procedure. The wireless device may perform a measurement based on the measurement procedure e.g. based on a positioning signal. Examples of the positioning signal comprise one or more of a positioning reference signal (PRS), a sounding reference signal (SRS) etc. In an example, the wireless device may perform a positioning measurement based on the positioning measurement procedure.
[0401] Referring to FIG. 30, a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria.
[0402] The one or more criteria for transmitting, to a wireless device, the request for performing an LOM procedure may comprise a positioning measurement. In an example, the wireless device may infer or predict the positioning measurement based on a model. In an example, the wireless device may perform the positioning measurement based on a positioning measurement procedure. Examples of the positioning measurement may comprise one or more of an RSTD, an UE Rx-Tx time difference, a PRS-RSRP etc. The wireless device may transmit, to the node, the positioning measurement based on the inference. In an example, the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement. In an example, the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement being larger than a first positioning measurement threshold (TPM1). In another example, the node may transmit, to a wireless device, the request for performing an LOM procedure based on the positioning measurement being smaller than a second positioning measurement threshold (TPM2). In another example, the node may transmit, to a wireless device, the request for performing an LOM procedure based on positioning measurement being larger than a third positioning measurement threshold (TPM3) and smaller larger than a fourth positioning measurement threshold (TPM4).
[0403] The one or more criteria for transmitting, to a wireless device, the request for performing an LOM procedure may comprise a positioning measurement accuracy of a positioning measurement. In an example, the node may determine the positioning measurement accuracy based on the positioning measurement and a reference value. In an example, the node may receive, from the wireless device, the one or more positioning measurements. In an example, the wireless device may perform the one or more positioning measurements based on a positioning measurement procedure. In an example, the wireless device may infer or predict the one or more positioning measurements based on a model. The reference value may correspond to an expected positioning measurement under one or more conditions. Examples of the one or more conditions comprise an environment, a carrier frequency of the wireless device, a speed of the wireless device etc. Examples of the environment may comprise the wireless device receiving a line of sight (LOS) path of a signal, a non-line of sight (NLOS) path of a signal or a combination of the LOS and the NLOS paths of a signal. In an example, the node may determine the positioning measurement accuracy based on a difference between the positioning measurement and the reference value. In an example, the node may determine the positioning measurement accuracy based on a magnitude of a difference between the positioning measurement and the reference value. In an example, the positioning measurement accuracy may comprise the difference between the positioning measurement and the reference value. In an example, the positioning measurement accuracy may comprise the difference between the magnitude of the positioning measurement and the reference value. In an example, the node may transmit, to a wireless device, the request for performing an LCM procedure based on the positioning accuracy being larger than a first positioning measurement accuracy threshold (TMA1 ) and smaller larger than a second positioning measurement accuracy threshold (TMA2).
[0404] Referring to FIG. 30, the interruption duration may start from the transmission of the indication for starting an LCM procedure.
[0405] In an example, the wireless device may transmit the indication for starting the LCM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources time resource during which the wireless device may transmit the indication for starting the LCM procedure. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the indication for starting the LCM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the indication for starting the LCM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the indication for starting the LCM procedure.
[0406] Referring to FIG. 30, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0407] FIG. 31 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 31 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, and/or 30.
[0408] For example, example embodiments in FIG. 31 may comprise a wireless device, receiving, from a node, a request for performing an LCM procedure. Example embodiments in FIG. 31 may comprise the wireless device transmitting, to the base station, an indication for starting an LCM procedure corresponding to the request for performing an LCM procedure. Example embodiments in FIG. 31 may comprise the wireless device performing an LCM procedure based on the transmission of the indication for starting an LCM procedure. Example embodiments in FIG. 31 may comprise the wireless device performing the LCM procedure during an interruption duration. The interruption duration may start from a time period. Example embodiments in FIG. 31 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 31 may comprise the wireless device communicating with the base station, based on the LCM procedure, after the interruption.
[0409] Referring to FIG. 31 , a node is according to example embodiments in FIG.30 (e.g., the node e.g. the location server, the core network node etc.).
[0410] Referring to FIG. 31 , a request for performing an LCM procedure is according to example embodiments in FIG.30 (e.g., the request for performing an LCM procedure).
[0411] Referring to FIG. 31, an indication for starting the LCM procedure is according to example embodiments in FIG.30 (e.g., the indication for starting the LCM procedure).
[0412] Referring to FIG. 31 , a node may transmit, to a wireless device, the request for performing an LCM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
[0413] Referring to FIG. 31 , an interruption duration may start after the time period according to the example embodiments in FIG.23.
[0414] Referring to FIG. 31 , in an example, the time period starts from the transmission of the indication for starting an LCM procedure.
[0415] In an example, the wireless device may transmit the indication for starting an LCM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources during which the wireless device may transmit the indication for starting an LCM procedure message. In an example, the time period may start from the beginning of the last time resource of the one of more time resources comprising the indication for starting an LCM procedure message. In an example, the time period may start from the end of the last time resource of the one of more time resources comprising the the indication for starting an LCM procedure message. In an example, the time period may start during the last time resource of the one of more time resources comprising the indication for starting an LCM procedure message.
[0416] Referring to FIG. 31 , a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0417] FIG. 32 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 32 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, and/or 31. [0418] For example, example embodiments in FIG. 32 may comprise a base station, receiving, from a node, an indication that UE starting an LOM procedure. For example, example embodiments in FIG. 32 may comprise a wireless device, receiving, from a node, a request for performing an LOM procedure. Example embodiments in FIG. 32 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure. Example embodiments in FIG. 32 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from the reception of the request for performing an LOM procedure. Example embodiments in FIG. 32 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 32 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
[0419] Referring to the example embodiments in FIG. 32, an indication that UE starting an LOM procedure may comprise at least an identifier of an LOM procedure.
[0420] Referring to the example embodiments in FIG. 32, in an example, an indication that UE starting an LOM procedure may comprise an NR positioning protocol annex (NRPPa) message.
[0421] Referring to the example embodiments in FIG. 32, in an example, an indication that UE starting an LOM procedure may comprise an NG Application Protocol (NGAP) message.
[0422] Referring to FIG. 32, in an example, an indication that UE starting an LOM procedure may further comprise an identifier or identity of a wireless device. The identifier may comprise one or more bits. In an example, the identifier of the wireless device may comprise a temporary identifier. The temporary identifier may be valid for a duration. In an example, temporary identifier may be based on or depend on an RRC state of a wireless device. In an example, temporary identifier may be based on or depend on an procedure e.g. a random access procedure, a reception of a paging message, a reception of a data channel (e.g., PDSCH) etc. Examples of the RRC state may comprise a RRC connected state, a RRC inactive state or a RRC idle state. In an example, the duration may be pre-determined. An example of the temporary identifier may comprise a Radio Network Temporary Identifier (RNTI).
[0423] Referring to the example embodiments in FIG. 32, in an example, the indication that UE starting an LCM procedure may further comprise timing information. In an example, the timing information may comprise a reference time. Examples of the reference time may comprise one or more of a slot number, a subframe number, a system frame number (SFN), a hyper system frame number (H-SFN), an UTC etc. In an example, an SFN may range from 0 to 1023. In an example, a H-SFN may comprise multiple SFN cycles e.g., 10 SFN cycles.
[0424] Referring to the example embodiments in FIG. 32, in an example, the node may transmit, to the wireless device, the request for performing an LCM procedure based on the reference time. In an example, the node may transmit, to the wireless device, the request for performing an LCM procedure from the reference time. In an example, the wireless device may start an LCM procedure based on the reference time. In an example, the wireless device may start an LCM procedure from the reference time. [0425] Referring to the example embodiments in FIG. 32, a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g. , the request for performing an LOM procedure).
[0426] Referring to the example embodiments in FIG. 32, a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g., the request for performing an LOM procedure).
[0427] Referring to FIG. 32, a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
[0428] Referring to FIG. 32, a node may transmit, to a base station, the indication that UE starting an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
[0429] Referring to FIG. 32, the interruption duration may start from the reception of a request for performing an LOM procedure.
[0430] In an example, the wireless device may receive the request for performing an LOM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
[0431] Referring to FIG. 32, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0432] FIG. 33 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 33 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, and/or 32.
[0433] For example, example embodiments in FIG. 33 may comprise a wireless device, receiving, from a node, a request for performing an LOM procedure. Example embodiments in FIG. 33 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure. Example embodiments in FIG. 33 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from a time period. Example embodiments in FIG. 33 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 33 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption. [0434] Referring to the example embodiments in FIG. 33, an indication that UE starting an LOM procedure is according to the example embodiments in FIG.31 (e.g., the indication that UE starting an LOM procedure).
[0435] Referring to the example embodiments in FIG. 33, a request for performing an LOM procedure is according to the example embodiments in FIG.31 (e.g., the request for performing an LOM procedure).
[0436] Referring to FIG. 33, a node may transmit, to a wireless device, the request for performing an LOM procedure based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
[0437] Referring to FIG. 33, an interruption duration may start after the time period according to the example embodiments in FIG.23.
[0438] Referring to FIG. 33, in an example, the time period starts from the request for performing an LOM procedure. [0439] In an example, the wireless device may receive the request for performing an LOM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources during which the wireless device may receive the request for performing an LOM procedure. In an example, the time period may start from the beginning of the last time resource of the one of more time resources comprising the request for performing an LOM procedure. In an example, the time period may start from the end of the last time resource of the one of more time resources comprising the request for performing an LOM procedure. In an example, the time period may start during the last time resource of the one of more time resources comprising the request for performing an LOM procedure.
[0440] Referring to FIG. 34, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0441] FIG. 34 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 34 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 , 32, and/or 33.
[0442] For example, example embodiments in FIG. 34 may comprise a base station, receiving, from a node, a request for starting an LOM procedure for UE. For example, example embodiments in FIG. 34 may comprise a wireless device, receiving, from a base station, a request for performing an LOM procedure. Example embodiments in FIG. 34 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure. Example embodiments in FIG. 34 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from the reception of the request for performing an LOM procedure. Example embodiments in FIG. 34 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 34 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
[0443] Referring to FIG. 34, a request for starting an LOM procedure for UE may comprise at least an identifier of an LOM procedure. In an example, the request for starting an LOM procedure for UE may further comprise timing information according to the example embodiments in FIG.32 (i.e., the indication that UE starting an LOM procedure). [0444] Referring to FIG. 34, in an example, a request for starting an LOM procedure for UE may further comprise an identifier or identity of a wireless device. In an example, the identifier of the wireless device may comprise a temporary identifier. An example of the temporary identifier may comprise a Radio Network Temporary Identifier (RNTI).
[0445] Referring to FIG. 34, in an example, a request for starting an LOM procedure for UE may further comprise timing information according to the example embodiments in FIG.30 (e.g., the indication that UE starting an LOM procedure).
[0446] Referring to FIG. 34, the interruption duration may start from the reception of a request for performing an LOM procedure.
[0447] In an example, the wireless device may receive the request for performing an LOM procedure during one or more time resources. In an example, the interruption duration may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure. In an example, the interruption duration may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the interruption duration may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the interruption duration may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
[0448] FIG. 35 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 35 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, and/or 34.
[0449] For example, example embodiments in FIG. 35 may comprise a base station, receiving, from a node, a request for starting an LOM procedure for UE. For example, example embodiments in FIG. 35 may comprise a wireless device, receiving, from a base station, a request for performing an LOM procedure. Example embodiments in FIG. 35 may comprise the wireless device performing an LOM procedure based on the reception of the request for performing an LOM procedure. Example embodiments in FIG. 35 may comprise the wireless device performing the LOM procedure during an interruption duration. The interruption duration may start from a time period. Example embodiments in FIG. 35 may comprise the wireless device interrupting communication with the base station during the interruption duration. Example embodiments in FIG. 35 may comprise the wireless device communicating with the base station, based on the LOM procedure, after the interruption.
[0450] Referring to FIG. 35, a request for starting an LOM procedure is according to example embodiments in FIG.34 (e.g., the request for starting an LOM procedure).
[0451] Referring to FIG. 35, a request for performing an LOM procedure is according to example embodiments in FIG.34 (e.g., the request for performing an LOM procedure). [0452] Referring to FIG. 35, a node may transmit, to a base station, the request for starting an LOM procedure for UE based on one or more criteria according to example embodiments in FIG.30 (e.g., the positioning measurement, the positioning measurement accuracy etc).
[0453] Referring to FIG. 35, an interruption duration may start after the time period according to the example embodiments in FIG.23.
[0454] Referring to FIG. 35, in an example, the time period may start from the request for performing an LOM procedure.
[0455] In an example, the wireless device may receive the request for performing an LOM procedure during one or more time resources. In an example, the time period may start based on the one or more time resources time resource during which the wireless device may receive the request for performing an LOM procedure. In an example, the time period may start from the beginning of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the time period may start from the end of the last time resource of the one or more time resources comprising the request for performing an LOM procedure. In an example, the time period may start during the last time resource of the one or more time resources comprising the request for performing an LOM procedure.
[0456] Referring to FIG. 35, a wireless device communicating with a base station after interruption duration may comprise, the wireless device transmitting a signal to the base station and/or receiving a signal from the base station. [0457] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, during the LOM procedure (e.g., during the interruption), the wireless device may halt, suspend, stop, cancel, drop, discard or postpone UL transmissions and/or DL receptions. For example, during the interruption duration, the wireless device may not transmit an uplink signal to the base station and/or may not receive a downlink signal from the base station. The wireless device may, in response to the LOM procedure being performed (e.g., after the interruption), may resume the at least UL transmissions or DL receptions. For example, after the interruption duration, the wireless device may transmit an uplink signal to the base station and/or may receive a downlink signal from the base station.
[0458] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, a signal may be referred to as a physical signal and/or a physical channel. A physical signal may comprise a reference signal (RS). In an example, a downlink RS may comprise a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), Channel Status Information-RS (CSI-RS), Demodulation Reference Signal (DMRS), Synchronization Signal/PBCH block (SSB), a Positioning Reference Signal (PRS) etc. In an example, an uplink RS may comprise a Demodulation Reference Signal (DMRS), a Sounding Reference Signal (SRS) etc. A physical channel comprises higher layer information. In an example, the higher layer information may comprise a logical channel, a transport channel etc. Examples of the logical channel may comprise a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (COCH), 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 comprise 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 comprise a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH) etc.
[0459] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, the wireless device inferring data based on the model for the RAC may comprise inferring one or more of a CSI, a downlink beam, a positioning measurement etc.
[0460] In an example, the wireless device inferring data based on the model for the RAC may comprise inferring a CSI e.g. CQI. In an example, the wireless inferring or predicting the CSI may comprise predicting the CSI in time domain. In an example, the wireless inferring the CSI may comprise inferring the CSI in spatial-frequency domain. In the an example, the wireless device may further transmit, to the base station, the inferred CSI.
[0461] In an example, the wireless device inferring data based on the model for the RAC 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 harnesses 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. 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 report, to the base station, the predicted beams.
[0462] The wireless device may trigger (or initiate or start performing) the LCM procedure (e.g., for the RAC). The wireless device may trigger the LCM procedure based on one or more criteria. In an example, the one or more criteria may be pre-determined. In an example, wireless device may receive a configuration message comprising/indicating the one or more criteria. In an example, the wireless device may receive the configuration message from a base station, a core network node or a location server. In an example, the wireless device may receive, from the base station, the configuration message by an RRC message. In an example, the wireless device may receive, from the location server, the configuration message by an LTE Positioning Protocol (LPP) message. In an example, the wireless device may receive, from the core network node, the configuration message by a Non-Access Stratum (NAS) message. [0463] Referring to the example embodiments in FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, any of the messages, request, indication, signaling, feedback or responses may comprise an ID of an LOM procedure. In an example, the IDs of LOM procedures may comprise: an activation of an AI/ML model with an ID = 0; a deactivation of an AI/ML model with an ID = 1; a fallback from the AI/ML model to a measurement procedure with an ID =2; a switching from a measurement procedure to the AI/ML model with an ID = 3; a switch from the AI/ML model to another AI/ML model with an ID = 4; and a modification of one or more parameters of the AI/ML model with an ID = 5.
[0464] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, the interruption duration may be pre-determined.
[0465] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, the interruption duration may also be referred to as an interruption period, an interruption length, an interruption window etc.
[0466] Referring to the example embodiments in FIG. 21 , FIG. 22, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG.30, FIG.31, FIG.32, FIG.33, FIG.34, and FIG.35, the interruption duration and/or the time period may comprise one or more time resources.
[0467] The time resource used may comprise any one of: one or more time units, one or more symbols, one or more sub-slots, one or more mini-slots, one or more time slots, one or more subframes and one or more radio frames. In an example, a time unit may comprise a length of time. The length of time may be expressed in nanoseconds, milliseconds, seconds, minutes, hours etc.
[0468] Referring to the example embodiments in FIG. 23, FIG. 25, FIG. 27, FIG. 29, FIG.31, FIG.33, and FIG.35, the time period may be pre-determined.
[0469] Referring to the example embodiments in FIG. 23, FIG. 25, FIG. 27, FIG. 29, FIG.31, FIG.33, and FIG.35, the time period may also be referred to as a time duration, a procedure delay, a processing time etc.
[0470] Referring to the example embodiments in FIG. 22 and FIG. 23, an indication for starting an LOM procedure may comprise a field indicating a start time of an interruption duration.
[0471] Referring to the example embodiments in FIG. 24 and FIG. 25, a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
[0472] Referring to the example embodiments in FIG. 26 and FIG. 27, a response message may comprise a field indicating a start time of an interruption duration.
[0473] Referring to the example embodiments in FIG. 28 and FIG. 29, an indication enabling the LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
[0474] Referring to the example embodiments in FIG. 30 and FIG. 31 , an indication for starting an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period. [0475] Referring to the example embodiments in FIG. 32 and FIG. 33, a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
[0476] Referring to the example embodiments in FIG. 34 and FIG. 35, a request for performing an LOM procedure may comprise a field indicating a start time of an interruption duration and/or a time period.
[0477] In an example, the start time of the interruption duration may comprise a time resource number.
[0478] In an example, the time period may comprise a time resource number. Examples of the time resource number may comprise a symbol number, a slot number, a subframe number, a radio frame number, a SFN or a H-SFN.
[0479] Referring to the example embodiments in FIG. 23, FIG. 25, FIG. 27, FIG. 29, FIG.31, FIG.33, and FIG.35, in an example, the time period may comprise a processing time of a wireless device. In an example, the time period may comprise a time for the wireless device for completing one or more ongoing tasks. Examples of the one or more tasks may comprise: performing a measurement, receiving a channel (e.g., PDSCH), transmitting a channel (e.g ., PUSCH), transmitting a feedback channel (e.g., HARQ ACK/NACK etc), transmitting a CSI report etc. In an example, the time period may be zero.
[0480] Referring to the example embodiments in FIG. 23, FIG. 25, FIG. 27, FIG. 29, FIG.31, FIG.33, and FIG.35, in an example, the time period comprise a processing time of a base station. In an example, the time period may comprise a time for the base station for completing one or more ongoing tasks. Examples of the one or more tasks may comprise: receiving a channel (e.g., PUSCH), transmitting a channel (e.g., PDSCH), receiving, from a wireless device, a feedback channel (e.g., HARQ ACK/NACK etc), receiving, from a wireless device a CSI report etc. In an example, the time period may be zero.
[0481] Referring to the example embodiments in FIG. 22, FIG. 23, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG. 30, and FIG. 31, any of the uplink messages may comprise an RRC, an MAC-CE, an Uplink Control Information (UCI), an Hybrid Automatic Repeat Request Acknowledgement/Negative Acknowledgement (HARQ ACK/NACK), an Long Term Evolution (LTE) Positioning Protocol (LPP) or an Non-Access Stratum (NAS) message.
[0482] Referring to the example embodiments in FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 28, FIG. 29, FIG. 30, and FIG. 31 any of the downlink messages may comprise an Radio Resource Control (RRC), an Medium Access Control- Control Element (MAC-CE), a Downlink Control Information (DCI), an Long Term Evolution (LTE) Positioning Protocol (LPP) or an Non-Access Stratum (NAS) message.
[0483] Referring to the example embodiments in FIG. 30, FIG. 31 , FIG. 32, FIG. 33, FIG. 34, and FIG. 35, a core network node may comprise an Access Management Function (AMF).
[0484] Referring to the example embodiments in FIG. 30, FIG. 31 , FIG. 32, FIG. 33, FIG. 34, and FIG. 35, a location may comprise a Location Management Function (LMF).
[0485] FIG. 36 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 36 may be combined with the features previously discussed with reference to FIGs. 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, and/or 35. [0486] Referring to FIG. 36, a wireless device may trigger an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption period may start based on the triggering of the LOM procedure. The wireless device may determine whether the wireless device is to transmit signals to, and/or receive signals from, the base station during the interruption duration. In response to determining that the wireless device is to transmit signals to, and/or receive signals from, the base station during the interruption time, the wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station. In response to determining that the wireless device is not to transmit signals to, and/or receive signals from, the base station during the interruption time, the wireless device may communicate, after interruption duration, with a base station.
[0487] Although FIG. 36 illustrates a step of determining whether the wireless device is to transmit to, and/or receive signals from, the base station, this feature is optional and may be omitted. For example, the process may proceed directly from performing the LOM during the interruption duration to communicating, after the interruption duration, with the base station (e.g., as illustrated in FIG. 21). Furthermore, the conditional relationship between the steps in FIG. 36 based on the determining may be omitted.
[0488] FIG. 37 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 37 may be combined with the features previously discussed with reference to FIG. 36.
[0489] Referring to FIG. 37, a wireless device may transmit, to a base station, a core network node, or a location server, an indication for starting an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption period may start based on the transmission of the indication for starting an LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.
[0490] FIG. 38 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 38 may be combined with the features previously discussed with reference to FIGs. 36 and/or 37. [0491] Referring to FIG. 38, a wireless device may receive, from a base station, a request for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption duration may start based on the reception of the request for performing an LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.
[0492] FIG. 39 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 39 may be combined with the features previously discussed with reference to FIGs. 36, 37, and/or 38. [0493] Referring to FIG. 39, a wireless device may receive, from a base station, a request for performing an LOM procedure. The wireless device may transmit, to the base station, a response message corresponding to the request for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption duration may start based on the transmission of the response message. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.
[0494] FIG. 40 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 40 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, and/or
39.
[0495] Referring to FIG. 40, a wireless device may transmit, to a base station, a request for performing an LOM procedure. The wireless device may receive, from the base station, an indication enabling the LOM procedure based on the request for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption period may start based on the reception of the indication enabling the LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.
[0496] FIG. 41 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 41 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39, and/or 40.
[0497] Referring to FIG. 41 , a wireless device may receive, from a node, a request from node for performing an LOM procedure. The wireless device may transmit, to a base station, an indication to base station for starting LOM procedure based on the request from node for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption duration may start based on the transmission of the indication to base station for starting LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station. [0498] FIG. 42 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 42 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39,
40, and/or 41.
[0499] Referring to FIG. 42, a wireless device may receive, from a node, a request from node for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption duration may start based on the reception of the request from node for performing an LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.
[0500] FIG. 43 illustrates an example as per an aspect of an embodiment of the present disclosure. The features illustrated in FIG. 43 may be combined with the features previously discussed with reference to FIGs. 36, 37, 38, 39, 40, 41, and/or 42.
[0501] Referring to FIG. 43, a wireless device may receive, from a base station, a request from base station for performing an LOM procedure. The wireless device may perform the LOM procedure during an interruption duration. The interruption duration may start based on the reception of the request from the base station for performing an LOM procedure. The wireless device may not communicate, during interruption duration, with a base station. The wireless device may communicate, after interruption duration, with a base station.

Claims

1. A method comprising: receiving, by a wireless device from a node, a first message triggering a life cycle management (LCM) procedure for a radio access communication; in response to the receiving the first message, transmitting a second message indicating that, during the LCM procedure, an interruption occurs in communications with a base station; performing the LCM procedure during a time duration, wherein: the time duration starts based on transmission of the second message; and the interruption occurs during the time duration based on the second message indicating the interruption; and communicating, with the base station based on the LCM procedure, after the interruption.
2. A method comprising: receiving, by a wireless device from a node, a first message triggering a life cycle management (LCM) procedure for a radio access communication; and performing the LCM procedure, wherein an interruption occurs, in communications with a base station, during the LCM procedure.
3. The method of claim 2, wherein: during a time duration, the interruption occurs in communications with the base station; and the LCM procedure is performed during the time duration.
4. The method of claim 3, wherein a part of the LCM procedure is performed during the time duration.
5. The method of claim 3 or 4, comprising, based on receiving the first message, transmitting a second message indicating that, during the time duration, the interruption occurs in communications with the base station.
6. The method of any one of claims 2-4, comprising, based on receiving the first message, transmitting a second message indicating that, during the LCM procedure, the interruption occurs in communications with the base station.
7. The method of claim 5 or 6, wherein the time duration starts based on transmission of the second message.
8. The method of any one of claims 3-7, wherein the interruption occurs during the time duration, based on the second message indicating the interruption.
9. The method of any one of claims 2-8, comprising, based on the LCM procedure, communicating with the base station, after the interruption.
10. The method of any one of claims 5-9, wherein the time duration starts from a timing of the transmission of the second message.
11. The method of any one of claims 5-9, wherein: the time duration starts after a first time duration; and the first time duration starts from a timing of the transmission of the second message.
12. The method of any one of claims 3-9, wherein: the time duration starts after a first time duration; and the first time duration starts from a timing of the reception of the first message.
13. The method of any one of claims 2-12, wherein the first message comprises an identifier for the LCM procedure.
14. The method of any one of claims 2-13, wherein the node is either a base station or a location server.
15. The method of any one of claims 5-14, wherein the second message is transmitted to the node.
16. The method of claim 15, wherein the second message is an acknowledgement message acknowledging receipt of the first message.
17. The method of any one of claims 5-14, wherein the second message is transmitted to the base station.
18. The method of claim 17, wherein the second message indicates a request for stopping a transmission of a reference signal or a request for transmitting a reference signal.
19. The method of any one of claims 2-18, wherein the LCM procedure is a procedure for managing a life cycle of an artificial intelligence (Al) and/or machine language (ML) (AI/ML) model for the radio access communication.
20. The method of claim 19, wherein the LCM procedure comprises one or more of: developing, deploying, managing, and/or maintaining the AI/ML model.
21. The method of any of claims 19-20, wherein the LCM procedure comprises performing one or more of: an activation of the AI/ML model; a deactivation of the AI/ML model; a switch to using the AI/ML model from using a different AI/ML model; a switch from using the AI/ML model to using a different AI/ML model; a switch from using the AI/ML model to a measurement procedure; a switch from a measurement procedure to using the AI/ML model; and/or a modification of one or more parameters of the AI/ML model.
22. The method of claim 21, wherein: the AI/ML model is used to predict one or more measurements; and the measurement procedure comprises performing one or more measurements without using the AI/ML model.
23. The method of any one of claims 2-22, wherein the interruption comprises one or more of: the wireless device not receiving one or more downlink signals from the base station; and/or the wireless device not transmitting one or more uplink signals to the base station.
24. The method of any one of claims 19-23, wherein the second message comprises a request for modifying a reference signal configuration.
25. The method of claim 24, comprising: based on transmitting the second message, receiving a modified reference signal configuration; modifying one or more parameters associated with the reference signal configuration, based on the modified reference signal configuration; and receiving or transmitting the reference signal, based on the modified one or more parameters.
26. The method of any one of claims 19-23, wherein the second message comprises a request for transmitting a reference signal.
27. The method of claim 26, wherein the request for transmitting the reference signal is based on: whether the wireless device is to use the AI/ML model for inferring a measurement; and/or the LCM procedure comprising a switching from using the AI/ML model to a measurement procedure.
28. The method of any one of claims 26-27, comprising: based on the request for transmitting the reference signal, receiving a response message comprising a reference signal configuration, wherein the reference signal configuration comprises one or more parameters associated with the reference signal; transmitting the reference signal, based on the reference signal configuration; and performing a measurement based on the reference signal.
29. The method of any one of claims 19-23, wherein the second message comprises a request for stopping, cancelling, or delaying a transmission of a reference signal.
30. The method of claim 28, wherein the request for stopping, cancelling, or delaying the transmission of the reference signal is based on one or more of: whether the wireless device is to use the AI/ML model for inferring a measurement; and/or the LCM procedure comprising a switching from a measurement to using the AI/ML model or a switching from using the AI/ML model to a different AI/ML model.
31. The method of claim 29 or 30, comprising: receiving, based on the request for stopping, cancelling, or delaying the transmission of the reference signal, a response message indicating that the reference signal is not to be transmitted by the wireless device; and based on the response message, stopping, cancelling, or delaying the transmission of the reference signal.
32. The method of claim 30, wherein the response message indicates a time duration during which the reference signal is not to be transmitted by the wireless device.
33. The method of claim 31 , wherein the time duration starts from a timing of receiving the response message.
34. The method of any one of claims 19-23, wherein the second message comprises a request for a reference signal.
35. The method of claim 34, wherein the request for the reference signal is based on one or more of: whether the wireless device is to use the AI/ML model for inferring a measurement; and/or the LCM procedure comprising a switching from using the AI/ML model to a measurement procedure.
36. The method of claim 34 or 35, comprising, based on the request for the reference signal, receiving a response message indicating a reference signal configuration, wherein the reference signal configuration comprises one or more parameters associated with the reference signal.
37. The method of claim 36, comprising receiving the reference signal, based on the reference signal configuration.
38. The method of claim 37, comprising performing a positioning measurement based on the reference signal.
39. The method of any one of claims 19-23, wherein the second message comprises a request for stopping, cancelling, or delaying a transmission of a reference signal.
40. The method of claim 39, wherein the request for stopping, cancelling, or delaying the transmission of the reference signal is based on one or more of: whether the wireless device is to use the AI/ML model for inferring a measurement; and/or the LCM procedure comprising a switching from a measurement to using the AI/ML model.
41. The method of claim 39 or 40, comprising: receiving, based on the request for stopping, cancelling, or delaying the transmission of the reference signal, a response message indicating that the reference signal is not to be transmitted by the base station; and based on the response message, stopping, cancelling, or delaying a reception of the reference signal.
42. The method of claim 41 , wherein the response message indicates a time duration during which the base station does not transmit the reference signal.
43. The method of claim 42, wherein the time duration starts from a timing of receiving the response message.
44. 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-43.
45. 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-43.
PCT/US2025/024475 2024-04-16 2025-04-14 Timing for life cycle management Pending WO2025221633A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463634749P 2024-04-16 2024-04-16
US63/634,749 2024-04-16

Publications (1)

Publication Number Publication Date
WO2025221633A1 true WO2025221633A1 (en) 2025-10-23

Family

ID=95656209

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/024475 Pending WO2025221633A1 (en) 2024-04-16 2025-04-14 Timing for life cycle management

Country Status (1)

Country Link
WO (1) WO2025221633A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11889503B2 (en) * 2021-03-26 2024-01-30 Qualcomm Incorporated UE feedback of non-preferred time-frequency resources

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11889503B2 (en) * 2021-03-26 2024-01-30 Qualcomm Incorporated UE feedback of non-preferred time-frequency resources

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Seamless UE context recovery (Release 18)", 20 April 2022 (2022-04-20), XP052136872, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/Latest_SA2_Specs/Latest_draft_S2_Specs/23700-61-020.zip 23700-61-020-MCCClean.docx> [retrieved on 20220420] *
WEI ZENG ET AL: "Discussion on general aspect of AI/ML framework", vol. RAN WG1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), XP052222369, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_111/Docs/R1-2211804.zip R1-2211804 - AI general framework.docx> [retrieved on 20221107] *

Similar Documents

Publication Publication Date Title
US20220346028A1 (en) Power Control for Configured Uplink Grant
EP3871359A1 (en) Downlink reception in multiple transmission and reception points
US12082216B2 (en) Transmission power determination for uplink channel repetition
US20210105751A1 (en) Beam Management Procedures in Radio Systems
US20230023600A1 (en) Pathloss Reference Signal Update
US20220361006A1 (en) Beam Determination Procedures in Radio Systems
EP4483635A1 (en) Timing advance procedures with multiple transmission reception points
EP4381677A2 (en) Beam management using a reference cell
US12010701B2 (en) Signal multiplexing in uplink channel repetition
US12501324B2 (en) Timing advance for mobility
WO2024072784A1 (en) Measurements in a radio access network
US20250374105A1 (en) Wireless Device Measurement Reporting in a Radio Access Network
WO2025221633A1 (en) Timing for life cycle management
WO2025235991A1 (en) Method of configuring gap pattern for lcm procedures for ai/ml model
WO2025144952A1 (en) Mobility and timing advance
WO2025144953A1 (en) Mobility and validity of timing advance
EP4639949A1 (en) Model performance evaluation in radio access network
WO2024186835A1 (en) Indication of unused uplink resources
WO2025144742A1 (en) Timing advance determination and report
WO2025212768A1 (en) User equipment capability report
WO2025111292A1 (en) Fast cell switch in radio access network
WO2024211673A1 (en) Model capability information in a radio access network
WO2025212777A1 (en) User equipment report
WO2025233503A1 (en) Measurement prediction frequency range
WO2024072957A1 (en) Information report based on low-layer mobility

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25724148

Country of ref document: EP

Kind code of ref document: A1