Wireless device trajectory in radio access network

Abstract

The invention relates to wireless device trajectories in a radio access network. A method may include transmitting, by a first base station, one or more messages to a second base station. The messages may include one or more time indications. The messages may also include, for each of the one or more time indications, a prediction of one or more candidate serving cells of the wireless device. The messages may also include, for each candidate serving cell of the one or more candidate serving cells, a prediction of a priority of the candidate serving cell to become a serving cell of the wireless device.

Description

Cross-reference to related applications

[0001] This application is a divisional application of the invention patent application with international application number PCT / US2023 / 036247, international application date of October 30, 2023, entry into the Chinese national phase date of April 25, 2025, Chinese national application number 202380075343.1, and invention title "Trajectory of Wireless Devices in Radio Access Networks".

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 420,358, filed on October 28, 2022, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0003] Examples of several embodiments of the various implementations of this disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B An example mobile communication network in which embodiments of this disclosure can be implemented is illustrated.

[0005] Figure 2A and Figure 2B The new radio (NR) user plane and control plane protocol stacks are illustrated separately.

[0006] Figure 3 Examples are shown in Figure 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Examples are given by Figure 2A Example downlink data stream of the NR user plane protocol stack.

[0008] Figure 4B This example illustrates the format of the MAC subheader in a MAC PDU.

[0009] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels used for downlink and uplink are illustrated respectively.

[0010] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0011] Figure 7 An example configuration of an NR frame in which OFDM symbols are grouped is shown.

[0012] Figure 8 Example configurations of time slots in the time and frequency domains for NR carriers are illustrated.

[0013] Figure 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

[0014] Figure 10A An example of a three-carrier aggregation configuration with two component carriers is shown.

[0015] Figure 10B Examples of how aggregated cells can be configured into one or more PUCCH packets are shown.

[0016] Figure 11A An example of the SS / PBCH block structure and location is shown.

[0017] Figure 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0018] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are given respectively.

[0019] Figure 13A , Figure 13B and Figure 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are illustrated respectively.

[0020] Figure 14A An example of CORESET configuration for the bandwidth portion is shown.

[0021] Figure 14B An example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0022] Figure 15 An example of a wireless device communicating with a base station is shown.

[0023] Figure 16A , Figure 16B , Figure 16C and Figure 16D Example structures for uplink and downlink transmission are shown.

[0024] Figure 17 Examples of functional architectures for artificial intelligence and / or machine learning are illustrated.

[0025] Figure 18 An example of using AI / ML in a radio access network is shown.

[0026] Figure 19 An example of using AI / ML in a radio access network is shown.

[0027] Figure 20 An example of UE trajectory prediction in the prior art is given.

[0028] Figure 21 Example implementations of this disclosure are illustrated.

[0029] Figure 22 Example implementations of this disclosure are illustrated.

[0030] Figure 23 An example of the content of the prediction of the UE trajectory is shown.

[0031] Figure 24 An example of the content of the prediction of the UE trajectory is shown.

[0032] Figure 25 Example implementations of this disclosure are illustrated.

[0033] Figure 26 Example implementations of this disclosure are illustrated.

[0034] Figure 27 An example of a UE moving between cells is shown.

[0035] Figure 28 An example of a UE moving between cells is shown.

[0036] Figure 29 Example implementations of this disclosure are illustrated.

[0037] Figure 30 Example implementations of this disclosure are illustrated. Detailed Implementation

[0038] In this disclosure, various embodiments are presented as examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in various environments and scenarios. Those skilled in the art will understand that various modifications in form and detail can be made to this disclosure without departing from its scope. In fact, after reading the specification, those skilled in the art should understand how to implement alternative embodiments. This disclosure should not be limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements in the embodiments of this disclosure can be combined to create further embodiments within the scope of this disclosure. Any figures emphasizing features and advantages are used only as examples. The disclosed architecture is flexible and configurable enough to allow it to be used in ways other than those shown. For example, in some embodiments, any actions listed in the flowcharts can be reordered or used only optionally.

[0039] Each implementation can be configured to operate as needed. The disclosed mechanisms can be executed when certain criteria are met, such as in wireless devices, base stations, radio environments, networks, or combinations thereof. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, or combinations thereof. Various example implementations can be applied when one or more criteria are met. Therefore, example implementations that selectively implement the disclosed protocols can be achieved.

[0040] A base station can communicate with multiple wireless devices. Wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices can have specific capabilities, depending on the wireless device category and / or capabilities. When this disclosure relates to a base station communicating with multiple wireless devices, this disclosure can relate to a subset of all wireless devices in a coverage area. This disclosure can refer to, for example, multiple wireless devices having given capabilities and in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure can refer to selected multiple wireless devices, and / or a subset of all wireless devices in a coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in a coverage area that may not conform to the disclosed method; for example, those wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0041] In this disclosure, “a” and “an”, and similar phrases, should be interpreted as “at least one” and “one or more”. Similarly, if any term ends with the suffix “(s)” in the original English text, it should be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” will be interpreted as “for example, may.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be employed by one or more of the various embodiments. The terms “comprising” and “consisting of” as used herein enumerate one or more components of the described element. The term “comprising” may be used interchangeably with “including” and does not exclude the inclusion of unlisted components in the described element. Conversely, “consisting of” provides a complete enumeration of one or more components of the described element. The term “based on” as used herein should be interpreted as “at least partially based on”, rather than, for example, “based on only.” The term “and / or” as used herein refers to any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0042] If A and B are sets and every element of A is an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are: {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase “based on” (or likewise “at least based on”) indicates that the phrase following the term “based on” is an example of one of many suitable possibilities that may or may not be used in one or more of the various implementations. The phrase “in response to” (or likewise “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of many suitable possibilities that may or may not be used in one or more of the various implementations. The phrase “depends on” (or likewise “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of many suitable possibilities that may or may not be used in one or more of the various implementations. The phrase “adopt / use” (or similarly “at least adopt / use”) indicates that the phrase following “adopt / use” is an example of one of many suitable possibilities that may or may not be used in one or more of the various implementation schemes.

[0043] The term "configuration" can refer to the capacity of a device, whether the device is in an operational or non-operational state. Configuration can also refer to specific settings within a device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within a device to provide specific characteristics, regardless of whether the device is in an operational or non-operational state. Terms such as "control messages induced in the device" can mean that control messages have parameters that can be used to configure specific characteristics or to implement certain actions within the device, regardless of whether the device is in an operational or non-operational state.

[0044] In this disclosure, a parameter (or similarly referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In the example implementation, when one or more messages include multiple parameters, this means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0045] Many of the features presented are described as optional using the word "may" or parentheses. For the sake of brevity and clarity, this disclosure does not explicitly list every permutation and combination that can be obtained by selecting from the set of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations and combinations. For example, a system described as having three optional features can be implemented in seven ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0046] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has an interface to the definitions of other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, software (e.g., hardware with biological elements), or combinations thereof, and these forms can be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a physical computer (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). Modules can be implemented using physical hardware that combines discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between internal hardware modules with limited functionality on the programmable device. The techniques mentioned are often combined to achieve the desired result of functional modules.

[0047] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is illustrated. The mobile communication network 100 may, for example, be a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0048] CN 102 can 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 carrier-internal DNs). As part of the interface functionality, CN 102 can establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide billing functions.

[0049] RAN 104 can connect CN 102 to radio device 106 via radio communication over its air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these duplexing technologies.

[0050] The term "wireless device" can be used throughout this disclosure to refer to and cover any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device can be a telephone, smartphone, tablet computer, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, vehicle, roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, mobile phone, wireless transceiver unit (WTRU), and / or wireless communication equipment.

[0051] 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 cover Node B (associated with UMTS and / or 3G standards), Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), Remote Radio Header (RRH), baseband processing unit coupled to one or more RRHs, repeater node or relay node for extending the coverage area of ​​donor nodes, Next Generation Evolved Node B (ng-eNB), Generation Node B (gNB, associated with NR and / or 5G standards), Access Point (AP, associated with, for example, WiFi or any other suitable wireless communication standard), and / or any combination thereof. A base station may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

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

[0053] Besides three-sector sites, other specific implementations of the base stations are also possible. For example, one or more of these base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more of these base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeaters or relay nodes for extending the coverage area of ​​donor nodes. The baseband processing units coupled to the RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing units can be centralized in a pool of baseband processing units or virtualized. Relay nodes can amplify and rebroadcast radio signals received from donor nodes. Relay nodes can perform the same / similar functions as repeater nodes, but can decode the radio signals received from donor nodes to remove noise before amplifying and rebroadcasting the radio signals.

[0054] RAN 104 can be deployed as a homogeneous network with macrocell base stations having similar antenna patterns and similar high levels of transmit power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can 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, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or femtocell base stations.

[0055] The Third Generation Partnership Project (3GPP) was established in 1998 to provide partnerships with similar organizations. Figure 1AChina Mobile's mobile communication network 100 provides globally standardized specifications. To date, 3GPP has defined specifications for three generations of mobile networks: the third-generation (3G) network known as Universal Mobile Telecommunications System (UMTS), the fourth-generation (4G) network known as Long Term Evolution (LTE), and the fifth-generation (5G) network known as 5G System (5GS). The embodiments disclosed herein will be described with reference to the RAN (Related to Next-Generation RAN, or NG-RAN) of the 3GPP 5G network. Various embodiments can be applied to the RAN of other mobile communication networks, such as... Figure 1A RAN 104, the RAN of earlier 3G and 4G networks, and the RAN of future networks that have not yet been specified (e.g., 3GPP 6G networks). NG-RAN implements a 5G radio access technology called New Radio (NR) and can be supplied to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0056] Figure 1B Another example of an embodiment of this disclosure is illustrated: a mobile communication network 150. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). These components are capable of operating in conjunction with... Figure 1A The corresponding components are implemented and function in the same or similar manner.

[0057] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs. As part of its interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and one or more DNs, authenticate UE 156, and provide billing functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes that make up 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0058] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of illustration, they are... Figure 1BThe UPF 158B is shown as a component AMF / UPF 158. The UPF 158B can act as a gateway between the NG-RAN 154 and one or more DNs. The UPF 158B can perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. The UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with one or more DNs, and / or a branch point supporting multi-homed PDU sessions. The UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0059] AMF 158A can perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle-mode UE reachability (e.g., control and enforcement of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming permission checks, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0060] 5G-CN 152 may include, for clarity, in Figure 1B One or more additional network functions not shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Storehouse Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

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

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

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

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

[0065] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as "non-standalone operation." In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B Only one AMF / UPF 158 is shown, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0066] As discussed, Figure 1B The interfaces between network elements (e.g., Uu, Xn, and NG interfaces) can be associated with the protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: the user plane and the control plane. The user plane handles data of interest to the user, and the control plane handles signaling messages of interest to the network elements.

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

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

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

[0070] PDCP 214 and PDCP 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from their intended source). PDCP 214 and PDCP 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and PDCP 224 can perform packet duplication to increase the likelihood of packets being received and remove any duplicate packets at the receiver. Packet duplication can be useful for services requiring high reliability.

[0071] Although Figure 3 Although not shown, PDCP 214 and PDCP 224 can perform mapping / demapping between separate radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology that allows a UE to connect to two cells, or more generally two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Separate bearers refer to individual radio bearers (such as those provided by PDCP 214 and PDCP 224 as services to SDAP 215 and SDAP 225) handled by the cell group in dual connectivity. PDCP 214 and PDCP 224 can map / demapping separate radio bearers between RLC channels belonging to the cell group.

[0072] RLC 213 and RLC 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MAC 212 and MAC 222. RLC 213 and RLC 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode in which the RLC is operating, it can perform one or more of the aforementioned functions. RLC configuration can be tailored to each logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and RLC 223 can provide RLC channels as services to PDCP 214 and PDCP 224, respectively.

[0073] MAC 212 and MAC 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include multiplexing data elements belonging to one or more logical channels to / from a transport block (TB) delivered to / from PHY 211 and PHY 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed for downlink and uplink in gNB 220 (at MAC 222). MAC 212 and MAC 222 can be configured to perform error correction by hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority handling between logical channels of UE 210 by means of logical channel prioritization, and / or padding. MAC 212 and MAC 222 can support one or more parameter sets and / or transmission timing. In one example, mapping constraints in logical channel prioritization can control the set of parameters and / or transmission timing that the logical channel can use. For example... Figure 3 As shown, MAC 212 and MAC 222 can provide logical channels as services to RLC 213 and RLC 223.

[0074] PHY 211 and PHY 221 can perform transmission channel to physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, decoding / decoding and modulation / demodulation. PHY 211 and PHY 221 can perform multi-antenna mapping. Figure 3 As shown, PHY 211 and PHY 221 can provide one or more transport channels as services to MAC 212 and MAC 222.

[0075] Figure 4A An example downlink data flow through the NR user plane protocol stack is illustrated. Figure 4A This example illustrates three IP packets passing through the NR user plane protocol stack. n , n+1 and m The downlink data flow, which generates two TBs at gNB 220, is similar to the uplink data flow through the NR user plane protocol stack. Figure 4A The downlink data flow described in the document.

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

[0077] Figure 4A The remaining protocol layers can perform their associated functions (e.g., relative to...) Figure 3 ), add the corresponding headers and forward their respective outputs to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., for...). Figure 4A IP packets m (As shown) and forwards its output to MAC 222. MAC 222 can multiplex multiple RLC PDUs and can append MAC sub-headers to RLC PDUs to form transport blocks. In NR, MAC sub-headers can be distributed across MAC PDUs, such as... Figure 4A As shown. In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be computed before the complete MAC PDU is assembled.

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

[0079] Figure 4B Examples also include MAC control elements (CEs) inserted into the MAC PDU by MACs such as MAC 223 or MAC 222. For example, Figure 4BThis example illustrates two MAC CEs inserted into a MAC PDU. A MAC CE can be inserted at the beginning of a MAC PDU (e.g., ...). Figure 4B (As shown in the diagram) for downlink transmission, and the end of the MAC PDU for uplink transmission. MAC CEs can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as MAC CEs for activating / deactivating PDCP copy detection, Channel State Information (CSI) reports, Sounding Reference Signal (SRS) transmission, and previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader with a similar format as described for MAC SDUs, and may be identified using a reserved value in the LCID field, which indicates the type of control information included in the MAC CE.

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

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

[0082] Transport channels are used between the MAC and PHY layers and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example: - Paging Channel (PCH), used to carry paging messages originating from the PCCH; - Broadcast channel (BCH), used to carry MIBs from the BCCH; - Downlink Shared Channel (DL-SCH), used to carry downlink data and signaling messages, including SIBs from BCCH; - Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and - Random Access Channel (RACH) is used to allow a UE to contact the network without any prior scheduling.

[0083] A PHY can use physical channels to transfer information between processing levels within the PHY. A physical channel can have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide control information to 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 includes, for example: - Physical Broadcast Channel (PBCH), used to carry MIBs from the BCH; - Physical Downlink Shared Channel (PDSCH), used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH; - Physical Downlink Control Channel (PDCCH) is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorization, and uplink power control commands; - Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from UL-SCH, and in some instances, uplink control information (UCI) as described below. - The Physical Uplink Control Channel (PUCCH), used to carry the UCI, may include HARQ acknowledgments, Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and - Physical Random Access Channel (PRACH) for random access.

[0084] Similar to the physical control channel, the physical layer generates physical signals to support lower-level physical layer operations. For example... Figure 5A and Figure 5B As shown, the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals will be described in more detail below.

[0085] Figure 2B An example NR control plane protocol stack is shown. For example... Figure 2B As shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and PHY 221, MAC 212 and MAC 222, RLC 213 and RLC 223, and PDCP 214 and PDCP 224. The NR control plane stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the NR control plane protocol stack, instead of having SDAP 215 and SDAP 225 on top of the stack as in the NR user plane protocol stack.

[0086] NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 (e.g., AMF 158A) or more generally between UE 210 and CN. NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages known as NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. NAS messages can be transmitted using ASs on Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection establishment, mobility management, and session management.

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

[0088] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 depicted in the text Figure 2A and Figure 2B The UE 210 depicted herein, or any other wireless device described in this disclosure, is the same as or similar to it. Figure 6 As shown, the UE can be in at least one of the three RRC states: RRC connected state 602 (e.g., RRC_CONNECTED), RRC idle state 604 (e.g., RRC_IDLE), and RRC inactive state 606 (e.g., RRC_INACTIVE).

[0089] In RRC connection state 602, the UE has an established RRC context and can have at least one RRC connection with a base station. This base station can be similar to... Figure 1A One of the one or more base stations included in RAN 104 as described herein, Figure 1B One of gNBs 160 or ng-eNB 162 described in the document. Figure 2A and Figure 2BThe gNB 220 depicted herein, or any other base station described in this disclosure. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may include 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., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY layer, MAC layer, RLC layer, PDCP layer, and / or SDAP layer configuration information. When in RRC connection state 602, the UE's mobility may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the 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 handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can be transitioned from the RRC connected state 602 to the RRC idle state 604 through the connection release process 608, or to the RRC inactive state 606 through the connection deactivation process 610.

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

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

[0092] RRC states can be associated with mobility management mechanisms. In RRC Idle State 604 and RRC Inactive State 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle State 604 and RRC Inactive State 606 is to allow the network to notify the UE of events via paging messages, without having to broadcast paging messages across the entire mobile network. The mobility management mechanism used in RRC Idle State 604 and RRC Inactive State 606 allows the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells of the cell group where the UE is currently camped, rather than across the entire mobile network. Mobility management mechanisms in RRC Idle State 604 and RRC Inactive State 606 track the UE at the cell group level. They can do this using different grouping granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area, referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

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

[0094] RAN areas can be used to track UEs at the RAN level. For UEs in RRC inactive state 606, a RAN notification area can be assigned to them. A RAN notification area can include one or more cell identifiers, RAI lists, or TAI lists. In one example, a base station can belong to one or more RAN notification areas. In another example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in the RAN notification area assigned to the UE, the UE can perform a notification area update with the RAN to update the UE's RAN notification area.

[0095] The base station storing the RRC context for the UE, or the UE's last serving base station, may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the time period when the UE is in the anchor base station's RAN notification area and / or during the time period when the UE is in an RRC inactive state.

[0096] gNB (such as Figure 1BThe gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

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

[0098] Figure 7An example configuration of an NR frame in which OFDM symbols are grouped is illustrated. NR frames can be identified by a System Frame Number (SFN). An SFN can repeat for 1024 frames in a period. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, each time slot including, for example, 14 OFDM symbols.

[0099] The duration of a time slot can depend on the parameter set of the OFDM symbols used for the time slot. NR supports flexible parameter sets to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter-wave range). Parameter sets can be defined based on subcarrier spacing and cyclic prefix duration. For parameter sets in NR, subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of 2, and cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 µs by powers of 2. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 µs; 30 kHz / 2.3 µs; 60 kHz / 1.2 µs; 120 kHz / 0.59 µs; and 240 kHz / 0.29 µs.

[0100] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing has a shorter time slot duration and correspondingly more time slots per subframe. Figure 7 This illustrates a time slot duration and per-subframe time slot transmission structure that depends on the parameter set (for ease of illustration, in...). Figure 7 (A parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the time slot duration and can begin at any OFDM symbol and continue for as many symbols as required for transmission. These partial time slot transmissions can be referred to as micro-time slot or sub-time slot transmissions.

[0101] Figure 8 An example configuration of time slots in the time and frequency domains for NR carriers is illustrated. A time slot consists of a Resource Element (RE) and a Resource Block (RB). An RE is the smallest physical resource in NR. For example... Figure 8 As shown, the RE spans one OFDM symbol in the time domain and one subcarrier in the frequency domain. Figure 8As shown, the RB spans twelve consecutive REs in the frequency domain. The NR carrier can be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. Using such a limitation, the NR carrier can be limited to 50MHz, 100MHz, 200MHz, and 400MHz for subcarrier spacings of 15kHz, 30kHz, 60kHz, and 120kHz, respectively, where the 400MHz bandwidth can be set based on a bandwidth limit of 400MHz per carrier.

[0102] Figure 8 This example illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other example configurations, multiple parameter sets can be supported on the same carrier.

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

[0104] NR defines a Bandwidth Partition (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In one example, a BWP can be defined by a subset of consecutive Relays (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have 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 any given time, one or more BWPs configured for the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

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

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

[0107] For an uplink BWP in a set of configured uplink BWPs, the BS can configure one or more resource sets for the UE to transmit one or more PUCCHs. The UE can receive downlink reception (e.g., PDCCH or PDSCH) in the downlink BWP based on the parameter set configured for the downlink BWP (e.g., subcarrier spacing and cyclic prefix duration). The UE can transmit uplink transmission (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured parameter set (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0108] One or more BWP indicator fields can be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in a set of configured BWPs is the downlink BWP for one or more downlink reception activities. The value of the one or more BWP indicator fields can indicate the uplink BWP for one or more uplink transmission activities.

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

[0110] The base station can configure the BWP inactivity timer value for the PCell for the UE. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer in the following situations: ( a When the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP used for paired spectrum operations; or ( bWhen the UE detects a DCI indication for an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP used for unpaired spectrum operation, the UE may run a BWP inactivity timer until it expires (e.g., incrementing from zero to the BWP inactivity timer value, or decrementing 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.

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

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

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

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

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

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

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

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

[0119] SCells configured for a UE can be activated and deactivated based on factors such as service and channel conditions. Deactivation of a SCell can mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. This can be done using relative to... Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0120] Downlink control information for a cell, such as scheduling allocation and grant, can be transmitted on the cell corresponding to the allocation and grant; this is called self-scheduling. The DCI of that cell can be transmitted on another cell; this is called cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0121] Figure 10BThis illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10B In the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. In this example, PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be sent in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be sent in the uplink of PSCell 1061. In one example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs related to the downlink CC, and the PCell may become overloaded. Overload can be prevented by dividing the transmission of UCIs between PCell 1021 and PSCell 1061.

[0122] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using a synchronization signal transmitted on the downlink component carrier. The cell index can be determined using an RRC message. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, the specification can mean that a cell including the first carrier is activated.

[0123] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In one example, the HARQ entity can operate on the serving cell. Transport blocks can be generated for each allocation / grant for each serving cell. Transport blocks and potential HARQ retransmissions of transport blocks can be mapped to the serving cell.

[0124] In the downlink, the base station may send (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, such as...). Figure 5A As shown). In the uplink, the UE can send one or more RSs (e.g., DMRS, PT-RS, and / or SRS, such as...) to the base station. Figure 5B (As shown). PSS and SSS can be sent by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS can be provided in the synchronization signal (SS) / physical broadcast channel (PBCH) block, which includes PSS, SSS, and PBCH. The base station can periodically send bursts of SS / PBCH blocks.

[0125] Figure 11A An example illustrating the structure and location of SS / PBCH blocks is provided. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks, such as...). Figure 11A (As shown). Bursts can be sent periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11A This is an example, and these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, and the position of the burst within a frame) can be configured based on, for example, the carrier frequency of the cell transmitting the SS / PBCH blocks; the cell's parameter set or subcarrier spacing; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In one example, unless the radio network configures the UE to assume a different subcarrier spacing, the UE can assume the subcarrier spacing of the SS / PBCH blocks based on the monitored carrier frequency.

[0126] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11A(as shown in the example), and can span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH can have a common center frequency. PSS can be transmitted first, and PSS can span, for example, one OFDM symbol and 127 subcarriers. SSS can be transmitted after PSS (e.g., after two symbols), and SSS can span one OFDM symbol and 127 subcarriers. PBCH can be transmitted after PSS (e.g., across the next three OFDM symbols), and PBCH can span 240 subcarriers.

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

[0128] The UE can use the SS / PBCH block to determine one or more parameters of the cell. For example, the UE can determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE can determine the location of the cell's frame boundary based on the location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission mode in which the SS / PBCH block is at a known distance from the frame boundary.

[0129] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity decoding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can include the cell's current system frame number (SFN) and / or an indication of the SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can include a Master Information Block (MIB) to provide one or more parameters to the UE. The UE can use the MIB to locate the Remaining Minimal System Information (RMSI) associated with the cell. The RMSI can include System Information Block Type 1 (SIB1). SIB1 can contain information required by the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH, which can be used to schedule the PDSCH. The PDSCH can include SIB1. SIB1 can be decoded using parameters provided in the MIB. The PBCH can indicate that SIB1 is not present. Based on the PBCH indicating the absence of SIB1, the UE can be directed to a specific frequency. The UE can search for SS / PBCH blocks at the frequency directed to by the UE.

[0130] The UE may assume that one or more SS / PBCH blocks transmitted using the same SS / PBCH block number 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 a QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

[0131] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In one example, a first SS / PBCH block can be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block can be transmitted in a second spatial direction using a second beam.

[0132] In one example, within the frequency span of a carrier, a base station can transmit multiple SS / PBCH blocks. In one example, the first PCI of the first SS / PBCH block among these multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block among these multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or the same.

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

[0134] The base station can semi-statically configure one or more CSI-RS resource sets for the UE. CSI-RS resources may be associated with location and period in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0135] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, non-periodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI reports at specific times and / or periodically. For non-periodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurement. For semi-persistent CSI reporting, the base station can configure the UE to send periodically and selectively activate or deactivate periodic reporting. The base station can use RRC signaling to configure the CSI-RS resource set and CSI reports for the UE.

[0136] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. When the downlink CSI-RS and CORESET are spatially QCLed, and the resource elements associated with the downlink CSI-RS are outside the Physical Resource Block (PRB) configured for the CORESET, the UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the control resource set (CORESET). When the downlink CSI-RS and SS / PBCH blocks are spatially QCLed, and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block, the UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block.

[0137] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a preloaded DMRS mode. Preloaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure multiple (e.g., a maximum number) preloaded DMRS symbols for the UE for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can support (e.g., at least for CP-OFDM) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS mode, and / or scrambling sequence can be the same or different. The base station can use the same pre-decoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS for coherent demodulation / channel estimation of the PDSCH.

[0138] In one example, a transmitter (e.g., a base station) may use a pre-decoder matrix for a portion of the transmission bandwidth. For instance, the transmitter may use a first pre-decoder matrix for a first bandwidth and a second pre-decoder matrix for a second bandwidth. The first and second pre-decoder matrices may differ depending on the first bandwidth and the second bandwidth. The UE may assume that the same pre-decoder matrix is ​​used across a set of PRBs. This set of PRBs can be represented as a Predecoder Resource Block Group (PRG).

[0139] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. Higher layers can configure up to three DMRS for the PDSCH.

[0140] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS may depend on the RRC configuration. The presence and / or mode of downlink PT-RS can be configured on a UE-specific basis using RRC signaling and / or a combination of one or more parameters associated with other purposes (e.g., modulation and decoding scheme (MCS)), which can be indicated by the DCI. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters that include at least the MCS. The NR network can support multiple PT-RS densities defined in the time and / or frequency domains. When present, the frequency domain density can be associated with at least one configuration of the scheduling bandwidth. The UE can assume the same pre-decoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduling resources. Downlink PT-RS can be restricted to the time / frequency duration scheduled for the UE. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0141] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE can use PUSCH and / or PUCCH to transmit uplink DMRS. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure one or more uplink DMRS configurations for the UE. At least one DMRS configuration can support preloaded DMRS mode. Preloaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure a certain number (e.g., a maximum number) of preloaded DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS mode, and / or scrambling sequence of the DMRS can be the same or different.

[0142] A PUSCH may include one or more layers, and a UE may transmit at least one symbol if a DMRS exists on one of the layers of the PUSCH. In one example, a higher layer may configure up to three DMRSs for the PUSCH.

[0143] Depending on the UE's RRC configuration, uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or mode of uplink PT-RS can be configured on a UE-specific basis based on a combination of RRC signaling and / or one or more parameters (e.g., modulation and decoding scheme (MCS)) for other purposes, which can be indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters that include at least an MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduling bandwidth. The UE can assume the same pre-decoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduling resources. For example, uplink PT-RS can be restricted to the time / frequency duration scheduled for the UE.

[0144] SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to allocate one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically configure one or more SRS resource sets for the UE. For each SRS resource set, the base station can configure one or more SRS resources for the UE. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at some time (e.g., simultaneously). The UE can transmit one or more SRS resources in an SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the one or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In one example, at least one DCI format can be used by the UE to select at least one SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 can refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 can refer to SRS triggered based on one or more DCI formats. In one example, when transmitting PUSCH and SRS in the same time slot, the UE can be configured to transmit SRS after transmitting PUSCH and the corresponding uplink DMRS.

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

[0146] Antenna ports are defined such that the channel through which a symbol is transmitted on an antenna port can be inferred from the channel through which another symbol is transmitted on the same antenna port. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) for transmitting the second symbol on the antenna port from the channel through which the first symbol is transmitted on the antenna port. The first and second antenna ports can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol is transmitted on the second antenna port. These one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0147] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)) and generate a beam measurement report. After establishing an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0148] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown can span a resource block (RB) within the cell's bandwidth. The base station can send one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured via higher-layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration: CSI-RS resource configuration identifier, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transmit 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.

[0149] Figure 11B The three beams illustrated can be configured for the UE according to the UE-specific configuration. Figure 11B The diagram illustrates three beams (beam #1, beam #2, and beam #3), and more or fewer beams can be configured. Beam #1 can be assigned CSI-RS 1101 that can be transmitted in one or more subcarriers within the RB of the first symbol. Beam #2 can be assigned CSI-RS 1102 that can be transmitted in one or more subcarriers within the RB of the second symbol. Beam #3 can be assigned CSI-RS 1103 that can be transmitted in one or more subcarriers within the RB of the third symbol. By using Frequency Division Multiplexing (FDM), the base station can use other subcarriers within the same RB (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using Time Domain Multiplexing (TDM), a beam for a UE can be configured such that the beam for the UE uses symbols from beams of other UEs.

[0150] CSI-RS such as Figure 11BThe measurements shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) of a configured CSI-RS resource. The base station can configure a reporting configuration for the UE, and the UE can report the RSRP measurement to the network (e.g., via one or more base stations) based on this reporting configuration. In one example, the base station can determine one or more Transmit Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurements. In one example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can use the receive (Rx) beam determined based on the one or more TCI states to receive downlink transmissions. In one example, the UE may or may not have beam-matching capability. If the UE has beam-matching capability, the UE can determine the spatial domain filter of the transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-matching capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE can perform an uplink beam selection process based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the uplink beam for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0151] During beam management, the UE can evaluate (e.g., measure) the channel quality of one or more beampup links, which include transmit beams sent by the base station and receive beams received by the UE. Based on this evaluation, the UE can send a beam measurement report indicating one or more beampup quality parameters, including, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, pre-decoded matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0152] Figure 12AExamples of three downlink beam management procedures are illustrated: P1, P2, and P3. Procedure P1 can implement UE measurement of the transmit (Tx) beams of a transmit-receive point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP may include a Tx beam scan for a set of beams (shown as an ellipse rotating counterclockwise in the top row of P1 and P2, indicated by the dashed arrow). Beamforming at the UE may include an Rx beam scan for a set of beams (shown as an ellipse rotating clockwise in the bottom row of P1 and P3, indicated by the dashed arrow). Procedure P2 can be used to implement UE measurement of the Tx beams of a TRP (shown as an ellipse rotating counterclockwise in the top row of P2, indicated by the dashed arrow). The UE and / or base station can perform process P2 using a smaller set of beams than those used in process P1, or using narrower beams than those used in process P1. This can be referred to as beam refinement. The UE can perform process P3 for Rx beam determination by using the same Tx beams at the base station and scanning the Rx beams at the UE.

[0153] Figure 12B Examples of three uplink beam management procedures: U1, U2, and U3 are given. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, a Tx beam scan from a set of beams (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrows). Beamforming at the base station can include, for example, an Rx beam scan from a set of beams (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrows). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than those used in procedure P1, or using a narrower beam than those used in procedure P1. This can be referred to as beam refinement. When the base station uses a fixed Rx beam, the UE can execute procedure U3 to adjust its Tx beam.

[0154] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can send a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect a beam fault based on determining that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0155] The UE can use one or more reference signals (RS) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS) to measure the quality of the beamp-link. The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station can indicate one or more DMRS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). One or more DMRS of the RS resources and channels can be QCLed when the channel characteristics transmitted from the RS resources to the UE (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) are similar to or the same as the channel characteristics transmitted from the channels to the UE.

[0156] The network (e.g., the network's gNB and / or ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection establishment from the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., uplink transmission for SR when no PUCCH resources are available) and / or acquire uplink timing (e.g., when the uplink synchronization state is out of sync). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for a beam fault recovery request. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell addition.

[0157] Figure 13A A four-step contention-based random access procedure is illustrated. Before initiating this procedure, the base station may send configuration message 1310 to the UE. Figure 13AThe process shown involves the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0158] For example, one or more RRC messages can be used to send configuration message 1310. These one or more RRC messages can indicate one or more Random Access Channel (RACH) parameters to the UE. These one or more RACH parameters can include at least one of the 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 can broadcast or multicast these one or more RRC messages to one or more UEs. These one or more RRC messages can be UE-specific (e.g., dedicated RRC messages sent to UEs in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE can determine the time-frequency resources and / or uplink transmit power for transmitting Msg 1 1311 and / or Msg 3 1313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE can determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0159] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. The one or more PRACH timings may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the 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-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0160] One or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmit power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., the receive target power and / or initial power for preamble transmission). One or more power offsets indicated by the one or more RACH parameters may exist. For example, the one or more RACH parameters can indicate: power ramp-up steps; power offset between SSB and CSI-RS; power offset between the transmissions of Msg 1 1311 and Msg 3 1313; and / or power offset values ​​between preamble groups. The one or more RACH parameters can indicate one or more thresholds upon which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

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

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

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

[0164] The Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 has been received by the base station. Msg 2 1312 may include a time alignment command that the UE can use to adjust the UE's transmission timing, a scheduling permission for the transmission of Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may open a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE may determine when to open the time window based on the timing of the PRACH used by the UE to transmit the preamble. For example, the UE can open a time window at one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing after the end of the preamble transmission). These one or more symbols can be determined based on a set of parameters. The PDCCH may be in a common search space configured by the RRC message (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on the Radio Network Temporary Identifier (RNTI). The RNTI can be used based on one or more events that initiate the random access procedure. The UE can use the Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on the OFDM symbol index; the slot index; the frequency domain index; and / or the UL carrier indication identifier of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier, 1 for SUL carrier).

[0165] The UE may send Msg 3 1313 in response to the successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). For example, in Figure 13A In the contention-based random access procedure shown, Msg 3 1313 can be used for contention resolution. In some scenarios, multiple UEs may send the same preamble to the base station, and the base station can provide a RAR corresponding to each UE. If multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use another UE's identifier. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., if a C-RNTI is assigned, then the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier).

[0166] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 includes a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identifier MAC CE that matches (e.g., is transmitted) the CCCH SDU transmitted in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

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

[0168] Figure 13B This illustrates a two-step contention-free random access procedure. Similar to... Figure 13A The four-step contention-based random access procedure shown can be initiated by the base station by sending configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The process shown involves sending two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg 4 1314.

[0169] Figure 13B The contention-free random access procedure shown can be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, the base station can indicate or assign a preamble to the UE for Msg 1 1321. The UE can receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0170] After sending the preamble, the UE can open a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for RAR. In the case of a beam failure recovery request, a separate time window and / or a separate PDCCH can be configured for the UE in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the transmission of PDCCH addressed to the cell RNTI (C-RNTI) in the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure has been successfully completed after the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322, or in response to the successful completion of such transmission and reception. For example, if the PDCCH transmission is addressed to C-RNTI, the UE can determine that the random access procedure has been successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure has been successfully completed. The UE can determine this response as an indication of acknowledgment of the SI request.

[0171] Figure 13C Another two-step random access procedure is illustrated. Similar to... Figure 13A and Figure 13B In the random access procedure shown, the base station may send configuration message 1330 to the UE before initiating the procedure. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The process shown involves sending two messages: Msg A1331 and Msg B1332.

[0172] Msg A 1331 can be transmitted by the UE in uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content of Msg 3 1313 shown is similar to and / or equivalent to the content shown. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after sending Msg A 1331 or in response to sending Msg A. Msg B 1332 may include content similar to... Figure 13A and Figure 13B Msg 2 1312 (e.g., RAR) and / or exemplified in the example Figure 13A The content shown in Msg 41314 is similar to and / or equivalent to the content shown in the document.

[0173] UE can initiate [action] against licensed spectrum and / or unlicensed spectrum. Figure 13C The two-step random access procedure is used in the UE. The UE may determine whether to initiate a two-step random access procedure based on one or more factors. These factors may include: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; cell size; the UE's RRC status; spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0175] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing advance command; a power control command; uplink grant (e.g., radio resource allocation and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble sent by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

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

[0177] Downlink control signaling may include: downlink scheduling allocation; uplink scheduling permission for uplink radio resources and / or transmission formats; time slot format information; preemption indication; power control commands; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a Group Common PDCCH (GC-PDCCH) common to a group of UEs.

[0178] A base station can append one or more Cyclic Redundancy Check (CRC) parity bits to a DCI to facilitate error detection. When the DCI is for a UE (or a group of UEs), the base station can scramble the CRC parity bits using the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with an identifier can include modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. This identifier can include a 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0179] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled with the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmission and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., with...). Figure 13AThe example Msg 3 1313 is similar to Msg 3. Other RNTIs configured by the base station for the UE may include the configured scheduling RNTI (CS RNTI), transmit power control PUCCH RNTI (TPC PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and decoding scheme cell RNTI (MCS-C RNTI), etc.

[0180] Depending on the purpose and / or content of the DCI, a base station may transmit the DCI using one or more DCI formats. For example, DCI format 0_0 can be used for scheduling PUSCH in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for scheduling PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for scheduling PDSCH in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for scheduling PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide a slot format indication to a group of UEs. DCI format 2_1 can be used to notify a group of UEs of physical resource blocks and / or OFDM symbols, where UEs may assume that no transmission is directed to them. DCI format 2_2 can be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to send a set of TPC commands for SRS transmission of one or more UEs. New DCI formats for future features may be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

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

[0182] Figure 14A An example of CORESET configuration for the bandwidth portion is illustrated. DCI can be transmitted via PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources in which the UE attempts to decode the DCI using one or more search spaces. CORESETs can also be configured in the time-frequency domain. Figure 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol of the time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol of the time slot. The fourth CORESET 1404 appears at the seventh symbol of the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0183] Figure 14B An example of CCE-to-REG mapping for DCI transmission and PDCCH processing on a CORESET is illustrated. CCE-to-REG mapping can be interleaved (e.g., for providing frequency diversity) or non-interleaved (e.g., for facilitating interference coordination and / or frequency-selective transmission of the control channel). Base stations can perform different or the same CCE-to-REG mappings on different CORESETs. A CORESET can be associated with a CCE-to-REG mapping configured via RRC. A CORESET can be configured with antenna port quasi-cooperative positioning (QCL) parameters. Antenna port QCL parameters can indicate the QCL information for the demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0184] An RRC message can be sent to the UE, including configuration parameters for one or more CORESETs and one or more search space sets. These configuration parameters can indicate the association between search space sets and CORESETs. A search space set can include a set of PDCCH candidates formed by CCEs for a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring periodicity and PDCCH monitoring mode; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. A set of CCEs in a common search space set can be predefined and known to the UE. A set of CCEs in a UE-specific search space set can be configured based on the UE's identifier (e.g., C-RNTI).

[0185] like Figure 14B As shown, the UE can determine the time-frequency resources for the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) for the CORESET based on the CORESET configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. In response to a CRC check (e.g., the scrambled bits of the CRC parity bit of the DCI match the RNTI value), the UE can determine that the DCI is valid for that UE. The UE can process the information contained in the DCI (e.g., scheduling allocation, uplink granting, power control, slot format indication, downlink preemption, etc.).

[0186] The UE can send uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may send a HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may send the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may send an SR to the base station indicating that uplink data is available for transmission. The UE can send UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE can use one of several PUCCH formats to send uplink control signaling via the PUCCH.

[0187] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If the transmission is on one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can include two or fewer bits. If the transmission is on four or more symbols and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If the transmission is on one or two symbols and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

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

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

[0190] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is illustrated. The wireless device 1502 and the base station 1504 may be a mobile communication network (such as...) Figure 1A The mobile communication network 100 shown Figure 1B It is part of the mobile communication network 150 (or any other communication network shown). Figure 15 Only one wireless device 1502 and one base station 1504 are illustrated, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, having the same characteristics as... Figure 15 The configuration shown is the same or similar.

[0191] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication on air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, and the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using FDD, TDD, and / or some combination of these two duplex technologies.

[0192] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. For example, data can be provided to processing system 1508 via the core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data to be transmitted. For example, relative to... Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 2 may include the SDAP layer, PDCP layer, RLC layer, and MAC layer. Layer 3 may include, as relative to... Figure 2B The RRC layer.

[0193] After processing by processing system 1508, data to be transmitted to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after processing by processing system 1518, data to be transmitted to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 can implement Layer 1 OSI functions. Layer 1 may include functions related to... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer, as described above, can perform operations such as forward error correction decoding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing for transmission processing.

[0194] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include, relative to... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer, as described above, can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping from the transport channel to the physical channel, demodulation of the physical channel, MIMO, or multi-antenna processing for receiving data.

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

[0196] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more functions discussed in this application. Although in Figure 15 Although not shown, the transmitting processing system 1510, transmitting processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0197] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal decoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0198] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keypads, displays, touchpads, power sources, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, laser sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from one or more peripheral devices 1516 and / or one or more peripheral devices 1526 and / or provide user output data to them. Processing system 1518 in wireless device 1502 may receive power from a power source and / or may be configured to distribute power to other components in wireless device 1502. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 and / or processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for wireless device 1502 and base station 1504, respectively.

[0199] Figure 16AAn example structure for uplink transmission is illustrated. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or more transmission layers; transform pre-decoding to generate complex-valued symbols; pre-decoding the complex-valued symbols; mapping the pre-decoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; etc. In one example, when transform pre-decoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In another example, when transform pre-decoding is not enabled, a CP-OFDM signal for uplink transmission can be generated by... Figure 16A Generation. These functions are illustrated as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0200] Figure 16B An example structure for modulating and up-converting a baseband signal to a carrier frequency is illustrated. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal for the antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0201] Figure 16C An example structure for downlink transmission is illustrated. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling the decoded bits in a codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transmission layers; pre-decoding the complex-valued modulation symbols on the layers for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; etc. These functions are illustrated as examples, and other mechanisms are expected to be implemented in various implementations.

[0202] Figure 16D Another example structure for modulating and up-converting a baseband signal to a carrier frequency is illustrated. The baseband signal can be a complex-valued OFDM baseband signal used at the antenna port. Filtering can be applied before transmission.

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

[0204] Once a timer is started, it can begin running and continue running until it is stopped or until it expires. A timer can be started while it is not running, or restarted while it is running. A timer can be associated with a value (e.g., a timer can be started or restarted from a certain value, or it can be started from zero and expire once that value is reached). The duration of a timer can not be updated until the timer stops or expires (e.g., due to a BWP switch). Timers can be used to measure time periods / windows used in a process. When this specification relates to specific implementations and processes associated with one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing a timer can be used to measure the time period / window of the process. For example, a random access response window timer can be used to measure the time window used to receive a random access response. In one example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the process used to measure the time window can be restarted. Other example implementations for restarting the measurement of the time window can be provided.

[0205] Figure 17 Examples of functional architectures for artificial intelligence (AI) and / or machine learning (ML) are illustrated.

[0206] Data collection function 1701 is a function that provides input data to model training function 1702 and model inference function 1703.

[0207] The input data from data collection function 1701 to model training function 1702 is called training data. It is used to train, validate, and test AI / ML models in model training function 1702. Examples of training data are measurements and statistics.

[0208] The input data from data collection function 1701 to model inference function 1703 is called inference data. It is used to generate the output in model inference function 1702. It is also used to generate model performance feedback in model inference function 1702. Examples of inference data are measurements and statistics.

[0209] Model training function 1702 is a function that can be used for training, validating, and testing AI / ML models. Model training function 1702 can also use the training data received from data collection function 1701 to perform AI / ML model-specific data preparation (e.g., data preprocessing and cleaning, formatting, and transformation).

[0210] AI / ML models can be deployed to model inference function 1703. AI / ML models can be trained and tested by model training function 1702 (e.g., before deployment).

[0211] Model inference function 1703 is a function that uses the deployed AI / ML model to generate inference output. This output is provided to actor function 1704 to perform actions based on the output received from model inference function 1703. Model inference function 1703 can use training data received from data collection function 1701 to perform AI / ML model-specific data preparation (e.g., data preprocessing and cleaning, formatting and transformation). Examples of outputs are determinations (predictions), policies, strategies, implementation plans, and requests.

[0212] The actuator function 1704 is a function that receives the output from the model inference function 1703 and performs the corresponding action.

[0213] After the action is performed by the action function 1704, feedback information can be generated and forwarded to the data collection function 1701, where it can become part of the training data or inference data. Examples of feedback information are measurements and performance metrics.

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

[0215] For example, AI / ML model training, updates, and inference can be performed in real time and in parallel. This is called online training, the opposite of offline training. In offline training, the AI / ML model can be trained, validated, and tested, and can deliver acceptable performance before deployment.

[0216] This will be discussed in more detail below. Figure 17 The AI / ML functional architecture illustrated herein can be used to address a variety of tasks in radio access networks. For example, this AI / ML functional architecture can be used to improve network energy efficiency, perform load balancing, perform mobility optimization, or any other suitable task.

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

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

[0219] The methods described in this disclosure may include one or more determinations (e.g., choices, selections, decisions, etc.). As will be discussed in more detail below, Figure 18 and Figure 19 This indicates that it can be based on and Figure 17 The AI / ML functional architecture described herein is similar to the AI / ML functional architecture used to make one or more of the determinations described in this paper. Specifically, Figure 18 An example of model training performed by OAM is shown, and Figure 19An example is shown in which model training is performed by the base station. In both cases, model inference is performed by the base station. The base station may include an actor 1704 and / or use the output of model inference 1703 to perform one or more actions (e.g., power-saving actions). It should be understood that other architectures are also possible. It should also be understood that implementing one or more determinations as described in this disclosure does not require AI / ML. Figures 17 to 19 This disclosure merely indicates that one or more determinations described herein may optionally be based in whole or in part on AI / ML.

[0220] Figure 18 An example of using AI / ML in a radio access network is shown. Figure 18 It can include similar to Figure 17 The AI / ML functional architecture is described in this example. In this example, the model training function 1702 is deployed in OAM, and the model inference function 1703 is deployed in BS 1 (e.g., base station, base station distributed unit, and / or base station central unit).

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

[0222] The UE performs measurement 1802. Measurement 1802 can be performed based on measurement configuration message 1801. The UE transmits a measurement report 1803 to BS 1.

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

[0224] BS 2 can send input data 1805 for model training to OAM. Input data 1805 for model training can be similar to input data 1804 for model training of BS 1.

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

[0226] OAM deploys the trained AI / ML model to BS 1 (model deployment / update 1807).

[0227] BS2 transmits input data 1808 to BS1 for model inference.

[0228] The UE transmits UE measurement report 1809 to BS 1.

[0229] BS 1 performs model inference 1810. Information from other sources that can host data collection functions can be used as input for AI / ML model inference. BS 1 can also evaluate deployed AI / ML models and send model performance feedback to OAM 1811.

[0230] Based on the output of model inference 1810, BS 1 executes action 1812. These actions can involve the UE and other BSs, for example... Figure 18 The UE and BS 2 are shown. These actions may include, for example, actions to improve network energy efficiency and / or actions to perform load balancing and / or actions to perform mobility optimization in the radio access network. These actions may include, for example, transmitting predictions from BS 1 to BS 2 and / or performing handover of one or more radio devices from BS 1 to BS 2.

[0231] After executing action 1812, BS 1 sends feedback 1813 to OAM. BS 2 sends feedback 1814 to OAM. Information from other sources that can host the actioner function can be used as feedback.

[0232] Figure 19 An example of using AI / ML in a radio access network is illustrated. AI / ML can be similar to... Figure 17 AI / ML. In this example, model training function 1702 and model inference function 1703 are deployed in BS 1 (e.g., base station, base station distributed unit, and / or base station central unit).

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

[0234] The UE performs measurement 1902. Measurement 1902 can be performed based on measurement configuration message 1901. The UE transmits a measurement report 1903 to BS 1.

[0235] BS 2 transmits input data 1904 for model training to BS 1. The input data 1904 for model training may include measurements performed by BS 2 and / or other data collected by BS 2.

[0236] BS 1 performs model training 1905. Model training 1905 can be based on measurement reports 1903, input data 1904 for model training, and / or other data determined by BS 1. For example, the number of measurement reports 1903 and input data 1904 for model training can be tens of thousands, hundreds of thousands, millions, or even more. Measurement reports 1903 can be received from any number of UEs, and input data 1904 for model training can be received from any number of BSs. Information from other sources that can host data collection functions can be used as input for AI / ML model training.

[0237] BS2 transmits input data 1906 to BS1 for model inference.

[0238] The UE transmits UE measurement report 1907 to BS 1.

[0239] BS 1 performs model inference 1908. Information from other sources that can host data collection functions can be used as input for AI / ML model inference.

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

[0241] After executing action 1909, BS 2 sends feedback 1910 to BS 1. Information from other sources that can host the actioner function can be used as feedback.

[0242] The output of the model inference can be a UE trajectory prediction. UE trajectory prediction can help the BS take actions to improve network energy efficiency and / or to perform load balancing and / or mobility optimization in the radio access network. For example, if actions to improve network energy efficiency and / or perform load balancing and / or perform mobility optimization in the radio access network result in UE handover, this UE trajectory prediction can help improve the handover process.

[0243] Figure 20 An example of UE trajectory prediction in the prior art is given.

[0244] UE 2001 moves within the coverage area of ​​the radio access network. UE 2001 is served by cell 2011 of BS 2010 for duration 1. Then, UE 2001 is transferred to cell 2021 of BS 2020. UE 2001 is served by cell 2021 of BS 2020 for duration 2. Then, UE 2001 is transferred to cell 2022 of BS 2020. UE 2001 is served by cell 2022 of BS 2020 for duration 3. Then, UE 2001 is transferred to cell 2031 of BS 2030.

[0245] In the prior art, a network (e.g., BS 2020 as shown in the figure) can be equipped with AI / ML functionality. This AI / ML functionality can determine (e.g., predict) the future trajectory of UE 2001. The prediction of UE 2001's trajectory can help BS 2020 select a target cell for UE 2001. For example, BS 2020 can use measurements of UE 2001 and / or information from BS 2030 (e.g., resource status information) and / or the prediction of UE 2001's trajectory to select cell 2031 of BS 2030 as the target cell for UE 2001 to be handed over from cell 2022 of BS 2020. BS 2020 can determine the prediction of UE 2001's trajectory before UE 2001 is handed over to BS 2030.

[0246] In the prior art, the AI / ML function of BS 2020 can determine predictions of UE 2001's trajectory during such future time periods, covering several handovers and / or several future serving cells. For example, the AI / ML function of BS 2020 can predict that UE 2001 will be handed over to cell 2031 of BS 2030. BS 2020 can predict that UE 2001 will be served by cell 2031 of BS 2030 for duration 4. BS 2020 can predict that UE 2001 will subsequently be handed over to cell 2041 of BS 2040. BS 2020 can predict that UE 2001 will be served by cell 2041 of BS 2040 for duration 5. BS 2020 can predict that UE 2001 will subsequently be handed over to cell 2051 of BS 2050. BS 2020 can predict that UE 2001 will be served by cell 2051 of BS 2050 for a duration of 6.

[0247] In the prior art, BS 2020 may be equipped with AI / ML functionality. BS 2030 and / or BS 2040 and / or BS 2050 may not be equipped with AI / ML functionality. BS 2020 may transmit a determined prediction of the UE 2001 trajectory to BS 2030 during the handover of UE 2001 from BS 2020 to BS 2030. For example, BS 2020 may use a handover request message to transmit the determined prediction of the UE 2001 trajectory to BS 2030. BS 2030 may use the predicted UE 2001 trajectory (along with other measurements and information) to determine a handover decision for UE 2001. BS 2030 may transmit the determined prediction of the UE 2001 trajectory to BS 2040 during the handover of UE 2001 from BS 2030 to BS 2040. BS 2040 can use the prediction of UE 2001 trajectory (along with other measurements and information) to determine the handover decision for UE 2001.

[0248] In the prior art, UE trajectory prediction is determined by a list of cells that will be serving cells in the future, and this list is associated with a duration indicating how long each cell in the list will be the UE's serving cell. For example, UE trajectory prediction can be expressed as ((Cell ID 1, Duration 1), (Cell ID 2, Duration 2), (Cell ID 3, Duration 3)). This prediction indicates that the UE is predicted to be served by the cell with Cell ID 1 for Duration 1, then the UE is predicted to be served by the cell with Cell ID 2 for Duration 2, and then the UE is predicted to be served by the cell with Cell ID 3 for Duration 3.

[0249] In existing technologies, it is also possible to predict the UE service beam. For example, UE trajectory prediction can be expressed as ((cell ID1, beam ID1, duration 1), (cell ID2, beam ID2, duration 2), (cell ID3, beam ID3, duration 3)). This prediction indicates that the UE is predicted to be served by the beam with beam ID1 in the cell with cell ID1 for duration 1, then the UE is predicted to be served by the beam with beam ID2 in the cell with cell ID2 for duration 2, and then the UE is predicted to be served by the beam with beam ID3 in the cell with cell ID3 for duration 3.

[0250] The problem with UE trajectory prediction in the prior art is that BS 2030, BS 2040, and BS 2050 make handover decisions independently of each other and independently of BS 2020, which performs UE trajectory prediction. Typically, for each handover decision, BS 2030 and / or BS 2040 and / or BS 2050 may have multiple candidates serving the UE. When selecting a target cell for handover from several available candidate serving cells, BS 2030 and / or BS 2040 and / or BS 2050 may consider many different factors, measurements, and information, not just UE mobility. For example, when making a handover decision, they may consider load information and / or energy efficiency information in their own cell and neighboring cells. BS 2020 may not typically have such information when determining the prediction of the UE trajectory. This can lead to inaccurate predictions. For example, a cell with cell ID 10 may be predicted as the UE's serving cell, but the actual serving cell will be the cell with cell ID 12.

[0251] Another problem with UE trajectory prediction in the prior art is the lack of clarity regarding how BS 2030 and / or BS 2040 and / or BS 2050 can utilize this UE trajectory prediction determined by BS 2020. The UE trajectory prediction indicates the handover decision (the selected target cell for handover) prior to such a decision being made by BS 2030 and / or BS 2040 and / or BS 2050. If BS 2030 and / or BS 2040 and / or BS 2050 select different target cells for the UE's handover, it is unclear how UE trajectory prediction in the prior art contributes to the handover decision.

[0252] Another problem with UE trajectory prediction in the prior art is that predicting the handover time is crucial. Such prediction can help reduce the probability of premature and / or late handover. Prior art UE trajectory prediction does not provide sufficient information about the handover time. This is because the duration is associated with the prediction for a specific serving cell. If one of BS 2030 and / or BS 2040 and / or BS 2050 selects at least one target cell for UE handover that differs from the prediction, all future predicted serving cells and durations may change.

[0253] A solution is needed that determines accurate predictions of UE trajectories and includes auxiliary information useful for independent handover decisions in BS 2030 and / or BS2040 and / or BS 2050.

[0254] The example embodiments of this disclosure implement an enhancement mechanism for UE trajectory prediction. Specifically, the example embodiments of this disclosure implement an enhancement mechanism for transmitting UE trajectory predictions from a first BS to a second BS. This allows the second BS to improve its handover decisions for the UE, for example, to reduce the probability of late and / or early handover and / or handover to the wrong cell. This allows the second BS to select a smaller number of candidate target cells for UE handover, which can result in fewer resource reservations in the candidate target cells, thereby increasing the available capacity in these cells.

[0255] In an example embodiment of this disclosure, a first base station may transmit one or more messages to a second base station. The one or more messages may include one or more time indications. The one or more messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the wireless device. The one or more messages may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become a serving cell of the wireless device.

[0256] In an example embodiment of this disclosure, the one or more messages may further include: a prediction of one or more candidate serving beams for the wireless device for each of the one or more candidate serving cells. The one or more messages may include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the wireless device.

[0257] In the example embodiments of this disclosure, the time indicator may include a point in time. The time indicator may include a start time and an end time. The time indicator may include a duration. The time indicator may include a start time and a duration. The time indicator may include both a duration and an end time.

[0258] In an example embodiment of this disclosure, the candidate serving cells for the wireless device during a time indication period may include cells whose reference signal level and / or quality are higher than a threshold for the wireless device during that time indication period. This threshold may include the minimum cell reference signal level and / or quality required for a cell to provide service to the wireless device.

[0259] In exemplary embodiments of this disclosure, the prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the candidate serving cell reference signal level during the time indication period. The prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the difference between the candidate serving cell reference signal level and a threshold cell reference signal level during the time indication period. The prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the ratio of the candidate serving cell reference signal level to the threshold cell reference signal level during the time indication period. The prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the candidate serving cell reference signal quality during the time indication period. The prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the difference between the candidate serving cell reference signal quality and the threshold cell reference signal quality during the time indication period. The prediction of the priority of a candidate serving cell becoming a serving cell of a radio device during the time indication period may include the prediction of the ratio of the candidate serving cell reference signal quality to the threshold cell reference signal quality during the time indication period.

[0260] In an example embodiment of this disclosure, the candidate serving beam for a candidate serving cell of a wireless device during a time indication period may include beams whose beam reference signal level and / or quality are higher than a threshold for the wireless device during that time indication period. This threshold may include the minimum beam reference signal level and / or quality of the beams serving the wireless device.

[0261] In exemplary embodiments of this disclosure, predicting the priority of a candidate serving beam becoming a serving beam of a wireless device during the time indication period may include predicting the reference signal level of the candidate serving beam during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of a wireless device during the time indication period may include predicting the difference between the candidate serving beam reference signal level and a threshold beam reference signal level during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of a wireless device during the time indication period may include predicting the ratio of the candidate serving beam reference signal level to the threshold beam reference signal level during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of a wireless device during the time indication period may include predicting the quality of the candidate serving beam reference signal during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of a wireless device during the time indication period may include predicting the difference between the quality of the candidate serving beam reference signal and the threshold beam reference signal quality during the time indication period. Predicting the priority of candidate serving beams that become serving beams of wireless devices during the time indication period may include predicting the ratio of the candidate serving beam reference signal quality to the threshold beam reference signal quality during the time indication period.

[0262] In an example embodiment of this disclosure, a second base station may receive one or more messages from a first base station. The one or more messages may include one or more time indications. The one or more messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the wireless device. The one or more messages may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become a serving cell of the wireless device.

[0263] In an example embodiment of this disclosure, the one or more messages may further include: a prediction of one or more candidate serving beams for the wireless device for each of the one or more candidate serving cells. The one or more messages may include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the wireless device.

[0264] In an example embodiment of this disclosure, a first base station may receive one or more messages from one or more wireless devices served by the base station and / or from one or more other base stations. The one or more messages may include measurements and information for determining predictions of one or more candidate serving cells for the wireless device for each of the one or more time indications. The one or more messages may also include measurements and information for determining predictions of priority for each of the one or more candidate serving cells to become a serving cell for the wireless device.

[0265] In an example embodiment of this disclosure, a first base station may use one or more received messages, including measurements and information, to determine a prediction of one or more candidate serving cells for a wireless device for each of one or more time indications. The first base station may also use the received messages, including measurements and information, to determine a prediction of the priority for each of the one or more candidate serving cells to become a serving cell for the wireless device.

[0266] In an example embodiment of this disclosure, a first base station may transmit one or more messages to a second base station. The one or more messages may include one or more time indications. The one or more messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the wireless device. The one or more messages may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become a serving cell of the wireless device.

[0267] In an example embodiment of this disclosure, the one or more messages may further include: a prediction of one or more candidate serving beams for the wireless device for each of the one or more candidate serving cells. The one or more messages may include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the wireless device.

[0268] In an example embodiment of this disclosure, a second base station may receive one or more messages from a first base station. The one or more messages may include one or more time indications. The one or more messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the wireless device. The one or more messages may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the serving cell of the wireless device. The second base station may use the one or more messages received from the first base station to perform radio access network performance improvement decisions and / or actions. The second base station may, for example, use the one or more messages received from the first base station to determine the next serving cell for the handover of the wireless device.

[0269] In an example embodiment of this disclosure, the one or more messages may further include: a prediction of one or more candidate serving beams for the wireless device for each of the one or more candidate serving cells. The one or more messages may include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the wireless device.

[0270] In the example embodiments of this disclosure, handover may include routine handover. Handover may include conditional handover. Handover may include dual connectivity. Handover may include multiple connectivity. Handover may include business-oriented handover. Handover may include coverage area reconfiguration.

[0271] The example implementation of this disclosure implements an enhancement mechanism for transmitting UE trajectory prediction from a first base station to a second base station. For each of the one or more time indications, the second base station receives a list of candidate serving cells for a radio device, wherein each of these candidate serving cells is associated with a priority to become the serving cell for the radio device. For each of the one or more time indications and for each candidate serving cell, the second base station may receive a list of candidate serving beams for the radio device, wherein each of these candidate serving beams is associated with a priority to become the serving beam for the radio device. This information can help the second base station make handover decisions for the radio device (selecting a serving cell from the candidate serving cells and / or selecting a serving beam from the candidate serving beams). This can allow the second base station to improve its handover decisions for the radio device, for example, to reduce the probability of late handover and / or early handover and / or handover to the wrong cell. This can allow the second base station to select fewer candidate target cells for radio device handover, which can result in fewer resource reservations in the candidate target cells, which can increase the available capacity in these cells.

[0272] Figure 21Example implementations of this disclosure are illustrated.

[0273] In an example implementation of this disclosure, BS 2101 may transmit one or more messages 2110 to BS 2102. The one or more messages 2110 may include one or more time indications. The one or more messages 2110 may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the UE. The one or more messages 2110 may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the UE's serving cell.

[0274] In an example embodiment of this disclosure, one or more messages 2110 may include: a prediction of one or more candidate serving beams for the UE for each of the one or more candidate serving cells. The one or more messages may also include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the UE.

[0275] In the example embodiments of this disclosure, the time indicator may include a point in time. The time indicator may include a start time and an end time. The time indicator may include a duration. The time indicator may include a start time and a duration. The time indicator may include both a duration and an end time.

[0276] In an example embodiment of this disclosure, the time point and / or start time and / or end time may indicate, for example, an absolute time measured by International Atomic Time (TAI). The time point and / or start time and / or end time may indicate, for example, a time offset between an absolute time reference and an absolute time measured by TAI. The absolute time reference may be selected to be equal to, for example, 1980-01-06 T00:00:19 measured by TAI. The duration may include, for example, 100 milliseconds or 1.2 seconds.

[0277] In an example embodiment of this disclosure, the candidate serving cells for the UE during the time indication period may include cells whose cell reference signal level and / or quality are higher than a threshold for the UE during that time indication period. This threshold may include the minimum cell reference signal level and / or quality required for a cell to provide service to the UE.

[0278] In exemplary embodiments of this disclosure, a cell may include a 3G cell. In exemplary embodiments of this disclosure, a cell may include a 4G cell. In exemplary embodiments of this disclosure, a cell may include a 5G cell. In exemplary embodiments of this disclosure, a cell may include a cell of a next-generation radio access network. In exemplary embodiments of this disclosure, a cell may include the coverage area of ​​a transmitter of a Wi-Fi system. In exemplary embodiments of this disclosure, a cell may include the coverage area of ​​a transmitter of a radio system of any other radio access system.

[0279] In exemplary embodiments of this disclosure, predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the reference signal level of the candidate serving cell during the time indication period. Predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the difference between the candidate serving cell reference signal level and a threshold cell reference signal level during the time indication period. Predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the ratio of the candidate serving cell reference signal level to the threshold cell reference signal level during the time indication period. Predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the reference signal quality of the candidate serving cell during the time indication period. Predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the difference between the candidate serving cell reference signal quality and the threshold cell reference signal quality during the time indication period. Predicting the priority of a candidate serving cell becoming a serving cell of the UE during the time indication period may include predicting the ratio of the candidate serving cell reference signal quality to the threshold cell reference signal quality during the time indication period.

[0280] In an example embodiment of this disclosure, the candidate serving beam for a candidate serving cell of the UE during the time indication period may include beams whose beam reference signal level and / or quality are higher than a threshold for the UE during that time indication period. This threshold may include the minimum beam reference signal level and / or quality of the beams serving the UE.

[0281] In exemplary embodiments of this disclosure, predicting the priority of a candidate serving beam becoming a serving beam of the UE during the time indication period may include predicting the reference signal level of the candidate serving beam during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of the UE during the time indication period may include predicting the difference between the candidate serving beam reference signal level and a threshold beam reference signal level during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of the UE during the time indication period may include predicting the ratio of the candidate serving beam reference signal level to the threshold beam reference signal level during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of the UE during the time indication period may include predicting the quality of the candidate serving beam reference signal during the time indication period. Predicting the priority of a candidate serving beam becoming a serving beam of the UE during the time indication period may include predicting the difference between the quality of the candidate serving beam reference signal and the threshold beam reference signal quality during the time indication period. Predicting the priority of candidate serving beams that become the serving beam of the UE during the time indication period may include predicting the ratio of the candidate serving beam reference signal quality to the threshold beam reference signal quality during the time indication period.

[0282] In an example embodiment of this disclosure, the reference signal level may include a Received Signal Strength Indicator (RSSI). The reference signal level may include a Reference Received Power (RSRP). The reference signal quality may include a Reference Received Quality (RSRQ).

[0283] In an example embodiment of this disclosure, the threshold for the reference signal level (e.g., for RSRP) can be selected to be equal to, for example, -100 dBm or -110 dBm. The threshold for the reference signal quality (e.g., for RSRQ) can be selected to be equal to, for example, -15 dB or -10 dB.

[0284] In an example implementation of this disclosure, BS 2102 may receive one or more messages 2110 from BS 2101. The one or more messages 2110 may include one or more time indications. The one or more messages 2110 may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the UE. The one or more messages 2110 may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the UE's serving cell.

[0285] In an example embodiment of this disclosure, one or more messages 2110 may include: a prediction of one or more candidate serving beams for the UE for each of the one or more candidate serving cells. The one or more messages may also include: a prediction of the priority for each of the one or more candidate serving beams to become a serving beam for the UE.

[0286] Figure 22 Example implementations of this disclosure are illustrated. Figure 22 An example is shown of the content of the prediction of the UE trajectory determined by the BS.

[0287] In an example embodiment of this disclosure, the one or more time indicators may include time indicator 1, time indicator 2, time indicator 3, time indicator 4, time indicator 5, time indicator 6, time indicator 7, time indicator 8, and time indicator 9.

[0288] For time indication 1, the prediction of the one or more candidate serving cells for the UE may include cell 1. For time indication 1, for candidate serving cell 1, the prediction of the priority of candidate serving cell 1 becoming the serving cell of the UE may include priority 11.

[0289] For time indication 2, the prediction of the one or more candidate serving cells for the UE may include cell 1. For time indication 2, for candidate serving cell 1, the prediction of the priority of candidate serving cell 1 becoming the serving cell of the UE may include priority 12.

[0290] For time indication 3, the prediction of the one or more candidate serving cells for the UE may include cell 1, cell 2, and cell 3. For time indication 3, for candidate serving cell 1, the prediction of the priority for candidate serving cell 1 to become the UE's serving cell may include priority 13. For time indication 3, for candidate serving cell 2, the prediction of the priority for candidate serving cell 2 to become the UE's serving cell may include priority 23. For time indication 3, for candidate serving cell 3, the prediction of the priority for candidate serving cell 3 to become the UE's serving cell may include priority 33.

[0291] For time indication 4, the prediction of the one or more candidate serving cells for the UE may include cell 2 and cell 3. For time indication 4, the prediction of the priority for candidate serving cell 2 to become the UE's serving cell may include priority 24. For time indication 4, the prediction of the priority for candidate serving cell 3 to become the UE's serving cell may include priority 34.

[0292] For time indication 5, the prediction of the one or more candidate serving cells for the UE may include cell 2, cell 3, and cell 4. For time indication 5, for candidate serving cell 2, the prediction of the priority for candidate serving cell 2 to become the UE's serving cell may include priority 25. For time indication 5, for candidate serving cell 3, the prediction of the priority for candidate serving cell 3 to become the UE's serving cell may include priority 35. For time indication 5, for candidate serving cell 4, the prediction of the priority for candidate serving cell 4 to become the UE's serving cell may include priority 45.

[0293] For time indication 6, the prediction of the one or more candidate serving cells for the UE may include cell 4. For time indication 6, the prediction of the priority of candidate serving cell 4 becoming the serving cell of the UE may include priority 46.

[0294] For time indication 7, the prediction of the one or more candidate serving cells for the UE may include cell 4. For time indication 7, the prediction of the priority of candidate serving cell 4 becoming the serving cell of the UE may include priority 47.

[0295] For time indication 8, the prediction of the one or more candidate serving cells for the UE may include cell 5 and cell 6. For time indication 8, the prediction of the priority for candidate serving cell 5 to become the serving cell of the UE may include priority 58. For time indication 8, the prediction of the priority for candidate serving cell 6 to become the serving cell of the UE may include priority 68.

[0296] For time indication 9, the prediction of one or more candidate serving cells for the UE may include cell 5, cell 6, and cell 7. For time indication 9, the prediction of the priority for candidate serving cell 5 to become the UE's serving cell may include priority 59. For time indication 9, the prediction of the priority for candidate serving cell 6 to become the UE's serving cell may include priority 69. For time indication 9, the prediction of the priority for candidate serving cell 7 to become the UE's serving cell may include priority 79.

[0297] Figure 23 An example of such a prediction of UE trajectory is shown.

[0298] The prediction of the UE trajectory may include: predicting the one or more candidate serving beams for the UE for each of the one or more candidate serving cells. The prediction of the UE trajectory may also include: predicting the priority of each candidate serving beam becoming the UE's serving beam for each of the one or more candidate serving beams.

[0299] In an example embodiment of this disclosure, the one or more time indicators may include time indicator 1, time indicator 2, and time indicator 3.

[0300] For time indication 1, the prediction of the one or more candidate serving cells for the UE may include cell 1. For time indication 1, for candidate serving cell 1, the prediction of the priority for candidate serving cell 1 to become the UE's serving cell may include cell priority 11. For time indication 1, for candidate serving cell 1, the prediction of the one or more candidate serving beams for the UE may include beam 111 and beam 112. For time indication 1, for candidate serving cell 1, for candidate serving beam 111, the prediction of the priority for candidate serving beam 111 to become the UE's serving beam may include beam priority 1111. For time indication 1, for candidate serving cell 1, for candidate serving beam 112, the prediction of the priority for candidate serving beam 112 to become the UE's serving beam may include beam priority 1121. Beams 111 and 112 are beams of cell 1.

[0301] For time indication 2, the prediction of the one or more candidate serving cells for the UE may include cell 1 and cell 2. For time indication 2, for candidate serving cell 1, the prediction of the priority for candidate serving cell 1 to become the UE's serving cell may include cell priority 12. For time indication 2, for candidate serving cell 1, the prediction of the one or more candidate serving beams for the UE may include beam 113. For time indication 2, for candidate serving cell 1, for candidate serving beam 113, the prediction of the priority for candidate serving beam 113 to become the UE's serving beam may include beam priority 1132. For time indication 2, for candidate serving cell 2, the prediction of the priority for candidate serving cell 2 to become the UE's serving cell may include cell priority 22. For time indication 2, for candidate serving cell 2, the prediction of the one or more candidate serving beams for the UE may include beam 121 and beam 122. For time indication 2, for candidate serving cell 2, for candidate serving beam 121, the prediction of the priority for candidate serving beam 121 to become the UE's serving beam may include beam priority 1212. For time indication 2, for candidate serving cell 2, for candidate serving beam 122, the prediction of the priority of candidate serving beam 122 becoming the serving beam of the UE may include beam priority 1222.

[0302] For time indication 3, the prediction of one or more candidate serving cells for the UE may include cell 2 and cell 3. For time indication 3, for candidate serving cell 1, the prediction of the priority for candidate serving cell 1 to become the UE's serving cell may include cell priority 12. For time indication 3, for candidate serving cell 2, the prediction of the priority for candidate serving cell 2 to become the UE's serving cell may include cell priority 23. For time indication 3, for candidate serving cell 2, the prediction of one or more candidate serving beams for the UE may include beam 123 and beam 124. For time indication 3, for candidate serving cell 2, for candidate serving beam 123, the prediction of the priority for candidate serving beam 123 to become the UE's serving beam may include beam priority 1233. For time indication 3, for candidate serving cell 2, for candidate serving beam 124, the prediction of the priority for candidate serving beam 124 to become the UE's serving beam may include beam priority 1243. For time indication 3, for candidate serving cell 3, the prediction of the priority for candidate serving cell 3 to become the UE's serving cell may include cell priority 33. For time indication 3, for candidate serving cell 3, the prediction of one or more candidate serving beams for the UE may include beam 131 and beam 132. For time indication 3, for candidate serving cell 3, for candidate serving beam 131, the prediction of the priority for candidate serving beam 131 to become the serving beam of the UE may include beam priority 1311. For time indication 3, for candidate serving cell 3, for candidate serving beam 132, the prediction of the priority for candidate serving beam 132 to become the serving beam of the UE may include beam priority 1323.

[0303] Figure 24 An example of such a prediction of UE trajectory is shown.

[0304] Figure 25 An example embodiment of the present invention is illustrated.

[0305] In an example implementation of this disclosure, BS 2500 may receive one or more messages from one or more UEs (e.g., UE 2501 and / or UE 2502) served by BS 2500 and / or from one or more other base stations (e.g., BS 2503 and / or BS 2504). For example, BS 2500 may receive one or more messages 2511 from UE 2501. BS 2500 may receive one or more messages 2512 from UE 2502. For example, BS 2500 may receive one or more messages 2513 from BS 2501. BS 2500 may receive one or more messages 2514 from BS 2502.

[0306] In an example embodiment of this disclosure, the one or more messages may include measurements and information for determining predictions of one or more candidate serving cells for the UE for each of the one or more time indications. The one or more messages may also include measurements and information for determining predictions of priority for each of the one or more candidate serving cells to become a serving cell of the UE.

[0307] For example, one or more messages 2511 from UE 2501 and / or one or more messages 2512 from UE 2502 may include location measurements (e.g., geographic coordinates, such as latitude and / or longitude and / or altitude) of UE 2501 and / or UE 2502. One or more messages 2511 from UE 2501 and / or one or more messages 2512 from UE 2502 may include measurements of the reference signal level and / or quality of candidate serving cells performed by UE 2501 and / or UE 2502. One or more messages 2511 from UE 2501 and / or one or more messages 2512 from UE 2502 may include UE historical information (e.g., a sequence of the UE's previous serving cells, where each serving cell is associated with the duration for which that cell was the UE's serving cell).

[0308] For example, one or more messages 2513 from BS 2503 and / or one or more messages 2514 from BS 2504 may include location measurements and / or candidate serving cell reference signal level and / or quality measurements and / or UE history information from one or more UEs served by BS 2503 and / or BS 2504.

[0309] In an example implementation of this disclosure, the BS 2500 may use one or more received messages 2511 and / or 2512 and / or 2513 and / or 2514, including measurements and information, to determine a prediction of one or more candidate serving cells for the UE for each of the one or more time indications. The BS 2500 may use one or more received messages 2511 and / or 2512 and / or 2513 and / or 2514, including measurements and information, to determine a prediction of the priority for each candidate serving cell to become a serving cell of the UE for each of the one or more candidate serving cells. The BS 2500 may perform this determination, for example, using AI / ML functions. The BS 2500 may perform this determination, for example, using extrapolation and / or interpolation.

[0310] In an example implementation of this disclosure, BS 2500 may transmit one or more messages to BS 2503 and / or BS 2504. The one or more messages may include one or more time indications. The one or more messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the UE. The one or more messages may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the serving cell of the UE.

[0311] In an example implementation of this disclosure, the one or more messages may further include: a prediction of one or more candidate serving beams for the UE for each of the one or more candidate serving cells. The one or more messages may include: a prediction of the priority for each candidate serving beam to become a serving beam for the UE.

[0312] In an example implementation of this disclosure, the UE that BS 2500 may transmit to BS 2503 and / or BS 2504 including one or more messages including a prediction of the UE trajectory may be UE 2501 and / or UE 2502 and / or another UE served by BS 2500 when the prediction is being determined and / or another UE not served by BS 2500 when the prediction is being determined.

[0313] In an example implementation of this disclosure, the messages that BS 2500 may transmit to BS 2503 and / or BS 2504 may include, for example, a handover request message for the UE (for which a UE trajectory prediction is transmitted).

[0314] In example embodiments of this disclosure, BS 2500 may transmit one or more messages to BS 2503 when BS 2500 has already determined a prediction. For example, BS 2500 may transmit one or more messages to BS 2503 when AI / ML functionality is available in BS 2500. For example, BS 2500 may transmit one or more messages to BS 2503 when AI / ML functionality available in BS 2500 is capable of determining a UE trajectory prediction. For example, BS 2500 may transmit one or more messages to BS 2503 when AI / ML functionality available in BS 2500 is activated.

[0315] Figure 26 Example implementations of this disclosure are illustrated.

[0316] In an example implementation of this disclosure, BS 2602 may receive one or more messages 2611 from BS 2601. The one or more messages 2611 may include one or more time indications. The one or more messages 2611 may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the UE. The one or more messages 2611 may include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the UE's serving cell.

[0317] In an example implementation of this disclosure, BS 2602 may use one or more messages 2611 received from BS 2601 to perform RAN performance improvement decisions and / or actions 2612. RAN performance improvement decisions and / or actions 2612 may include, for example, determining the next serving cell for the UE's handover.

[0318] In an example embodiment of this disclosure, one or more messages 2611 may further include: a prediction of one or more candidate serving beams for the UE for each of the one or more candidate serving cells. One or more messages 2611 may include: a prediction of the priority for a candidate serving beam to become a serving beam for the UE for each of the one or more candidate serving beams.

[0319] In the example embodiments of this disclosure, handover may include routine handover. Handover may include conditional handover. Handover may include dual connectivity. Handover may include multiple connectivity. Handover may include business-oriented handover. Handover may include coverage area reconfiguration.

[0320] In an example implementation of this disclosure, BS 2 may receive one or more messages from BS 1. These messages may include one or more time indications. The messages may include, for each of the one or more time indications, a prediction of one or more candidate serving cells for the UE. The messages may also include, for each of the one or more candidate serving cells, a prediction of the priority for that candidate serving cell to become the UE's serving cell.

[0321] In an example implementation of this disclosure, BS 2 may use the one or more messages received from BS 1 to perform RAN performance improvement decisions and / or actions. RAN performance improvement decisions and / or actions may include, for example, determining the next serving cell for the UE's handover.

[0322] Figure 27An example of a UE moving between cells is shown. For instance, a UE can move between cell 1 of BS 2 and cell 2 and cell 3 of BS 3.

[0323] The UE can perform measurements of the signal level and / or signal quality of candidate serving cells (including the UE's current serving cell). At time indication 2, the UE can perform a measurement that indicates the signal level and / or signal quality of candidate serving cell 2 of BS 3 is higher than the signal level and / or signal quality of current serving cell 1 of BS 2 by a pre-configured value. The UE can report the result of this measurement to BS 2. Based on such a measurement report, BS 2 can initiate a handover of the UE from cell 1 of BS 2 to cell 2 of BS 3.

[0324] If the UE is moving rapidly, even if it has performed a measurement indicating that the signal level and / or signal quality of candidate serving cell 2 of BS 3 is higher than the signal level and / or signal quality of the current serving cell 1 of BS 2 by a pre-configured value, the UE may be unable to transmit the measurement results to BS 2 via serving cell 1 because the UE may move out of the coverage area of ​​cell 1 before transmitting the measurement report. Even if the UE is able to transmit the measurement report to BS 2, the UE may still move out of the coverage area of ​​its serving cell (cell 1 of BS 2) before it can receive a request to perform a handover. In this case, the UE will lose its connection with the serving cell and will have to perform a connection re-establishment process. This may result in service interruption and / or waste of system resources in the radio access network. Such an unintended event is referred to as delayed handover in 3GPP specifications, for example.

[0325] In an example implementation of this disclosure, BS 2 can receive predictions of the UE trajectory for time indication 1 and time indication 2 from BS 1. In time indication 1, the one or more candidate serving cells for the UE may include cell 1 with priority 11. In time indication 3, the one or more candidate serving cells for the UE may include cell 2 with priority 23 and cell 3 with priority 33. Based on this prediction of the UE trajectory, BS 2 can determine the UE's handover needs between time indication 1 and time indication 3 before receiving the measurement report for time indication 2 from the UE. Based on this determination, BS 2 can, for example, pre-configure conditional handover for the UE with cells 2 and 3 of BS 3 before time indication 1. This will not result in wasted resources, as BS 2 can indicate to BS 3 that resources need to be reserved for the UE only between time indication 1 and time indication 3. Using the conditional handover procedure, the UE can begin handover directly after the measurement at time indication 2. This allows the UE to complete the handover to cell 2 and / or to cell 3 before moving out of the coverage area of ​​cell 1. This allows the UE to avoid late handover. This allows the UE to avoid service interruptions and / or waste of system resources in the radio access network.

[0326] UE trajectory prediction can allow for the avoidance of other unintended events during movement, such as late handover and / or handover to the wrong cell.

[0327] Figure 28 An example of a UE moving between cells is illustrated. For instance, a UE can move between cell 2 of BS 2 and / or cell 3 of BS 3 and / or cell 4 of BS 4.

[0328] BS 2 can configure conditional handover for the UE with cell 3 of BS 3 and cell 4 of BS 4. During conditional handover, BS 2 can request BS 3 to reserve resources in cell 3 for the UE based on UE measurements of the reference signal level and / or quality of cell 3. BS 2 can also request BS 4 to reserve resources in cell 4 for the UE based on UE measurements of the reference signal level and / or quality of cell 4. Because only one of cell 3 and cell 4 will be used by the UE for conditional handover, reserving resources in the other cell (not used for conditional handover) would waste system resources.

[0329] In an example embodiment of this disclosure, BS 2 can receive predictions of the UE trajectory from BS 1 for time indication 1, time indication 2, and time indication 3. In time indication 1, the one or more candidate serving cells of the UE may include cell 2 with priority 21. In time indication 2, the one or more candidate serving cells of the UE may include cell 3 with priority 32 and cell 4 with priority 42. In time indication 3, the one or more candidate serving cells of the UE may include cell 3 with priority 33.

[0330] Based on the received prediction of the UE trajectory, if priority 32 is significantly higher than priority 42, BS 2 can request the handover of reserved resources for the UE only in cell 3 of BS 3. Alternatively or additionally, by comparing the candidate serving cells in time indication 2 and time indication 3, BS 2 can determine that cell 3 is a candidate serving cell at both time indication 2 and time indication 3, but determine that cell 4 is a candidate serving cell only at time indication 2. Based on this determination, BS 2 can request the handover of reserved resources for the UE only in cell 3 of BS 3. Because BS 2 may not request resource reservations in cell 4, this can save system resources in cell 4. This can increase the capacity of the radio access network.

[0331] In an example implementation of this disclosure, the priority of a candidate serving cell to become the UE's serving cell may include the accuracy of the priority prediction. The priority of a candidate serving cell to become the UE's serving cell may include a confidence interval for the priority prediction.

[0332] In an example embodiment of this disclosure, the priority of a candidate serving beam becoming a serving beam of a wireless device may include the accuracy of the priority prediction. The priority of a candidate serving beam becoming a serving beam of a wireless device may include a confidence interval for the priority prediction.

[0333] In example, in an exemplary implementation of this disclosure, if the reference signal level and / or quality of a cell is above a threshold during a certain time indication period, the cell may be included in one or more candidate serving cells for the UE for that time indication.

[0334] In example embodiments of this disclosure, if the reference signal level and / or quality of a beam is above a threshold during a certain time indication period, the beam may be included in one or more candidate serving beams for the UE for that time indication.

[0335] In the example implementation of this disclosure, the number of candidate serving cells for each time-indicated UE can be limited to a pre-configured number (e.g., 4 or 8).

[0336] In the example implementation of this disclosure, the number of candidate serving beams for each cell UE for each time indication can be limited to a pre-configured number (e.g., 4 or 8).

[0337] Figure 29 Example implementations of this disclosure are illustrated.

[0338] Figure 30 Example implementations of this disclosure are illustrated.

[0339] The following terms describe certain implementation schemes. The implementation schemes described in these terms are provided as non-limiting examples of implementation schemes. These implementation schemes may be used individually or in combination.

[0340] Clause 1. A method comprising transmitting one or more messages from a first base station to a second base station, the one or more messages comprising: one or more time indications; a prediction of one or more candidate serving cells for a wireless device for each of the one or more time indications; and a prediction of the priority of each candidate serving cell for the wireless device to become a serving cell for each of the one or more candidate serving cells.

[0341] Clause 2. A method comprising receiving one or more messages from a first base station by a second base station, the one or more messages comprising: one or more time indications; a prediction of one or more candidate serving cells for a wireless device for each of the one or more time indications; and a prediction of the priority of each candidate serving cell for the wireless device to become a serving cell for each of the one or more candidate serving cells.

[0342] Clause 3. A method comprising: receiving, by a first base station, one or more messages including measurements and / or information from one or more wireless devices served by the first base station and / or one or more other base stations; determining, by the first base station, based on the received one or more messages: one or more time indications; a prediction of one or more candidate serving cells for the wireless device for each of the one or more time indications; and a prediction of the priority of each candidate serving cell for the wireless device to become the serving cell of the wireless device for each of the one or more candidate serving cells; and transmitting, by the first base station, one or more messages to a second base station, the one or more messages including: the one or more time indications; the prediction of the one or more candidate serving cells for the wireless device for each of the one or more time indications; and the prediction of the priority of each candidate serving cell for the wireless device to become the serving cell of the wireless device for each of the one or more candidate serving cells.

[0343] Clause 4. A method comprising receiving one or more messages from a first base station by a second base station, the one or more messages comprising: one or more time indications; a prediction of one or more candidate serving cells for a wireless device for each of the one or more time indications; a prediction of the priority of each candidate serving cell for the wireless device to become a serving cell for the wireless device for each of the one or more candidate serving cells; and the second base station using the one or more messages received from the first base station to perform a radio access network performance improvement decision and / or action.

[0344] Clause 5. The method described in Clause 4, wherein performing the radio access network performance improvement actions includes routine handover and / or conditional handover and / or dual connectivity and / or multiple connectivity and / or service orientation and / or coverage area reconfiguration.

[0345] Clause 6. The method according to any one of Clauses 1 to 5, wherein the one or more messages further include: prediction of one or more candidate serving beams of the wireless device for each of the one or more candidate serving cells; and prediction of the priority of the candidate serving beams becoming serving beams of the wireless device for each of the one or more candidate serving beams.

[0346] Clause 7. The method according to Clause 6, wherein the candidate service beam for the wireless device during the time indication period includes: a beam reference signal level higher than a threshold of the wireless device during the time indication period; and / or a beam reference signal quality higher than a threshold of the wireless device during the time indication period.

[0347] Clause 8. The method according to Clause 7, wherein the threshold includes: a minimum beam reference signal level for the beam to provide services to the wireless device; and / or a minimum beam reference signal quality for the beam to provide services to the wireless device.

[0348] Clause 9. The method according to any one of Clauses 6 to 8, wherein the prediction of the priority for the candidate serving beam to become a serving beam of the wireless device comprises: prediction of the candidate serving beam reference signal level during the time indication period; and / or prediction of the difference between the candidate serving beam reference signal level and a threshold beam reference signal level during the time indication period; and / or prediction of the ratio of the candidate serving beam reference signal level to the threshold beam reference signal level during the time indication period; and / or prediction of the candidate serving beam reference signal quality during the time indication period; and / or prediction of the difference between the candidate serving beam reference signal quality and the threshold beam reference signal quality during the time indication period; and / or prediction of the ratio of the candidate serving beam reference signal quality to the threshold beam reference signal quality during the time indication period.

[0349] Clause 10. The method according to any one of Clauses 6 to 9, wherein the prediction of the priority of the candidate serving beam becoming the serving beam of the wireless device further comprises: the accuracy of the prediction of the priority, and / or the confidence interval of the prediction of the priority.

[0350] Clause 11. The method according to any one of Clauses 1 to 10, wherein the time indication includes: time point and / or start time and end time and / or duration and / or start time and duration and / or duration and end time.

[0351] Clause 12. The method according to any one of Clauses 1 to 11, wherein the candidate serving cells for the wireless device during the time indication period include: cells with a cell reference signal level higher than a threshold of the wireless device during the time indication period; and / or cells with a cell reference signal quality higher than a threshold of the wireless device during the time indication period.

[0352] Clause 13. The method according to Clause 12, wherein the threshold includes: a minimum cell reference signal level for the cell to provide services to the wireless device; and / or a minimum cell reference signal quality for the cell to provide services to the wireless device.

[0353] Clause 14. The method according to any one of Clauses 1 to 13, wherein the prediction of the priority for the candidate serving cell to become a serving cell of the radio device comprises: prediction of the candidate serving cell reference signal level during the time indication period; and / or prediction of the difference between the candidate serving cell reference signal level and a threshold cell reference signal level during the time indication period; and / or prediction of the ratio of the candidate serving cell reference signal level to the threshold cell reference signal level during the time indication period; and / or prediction of the candidate serving cell reference signal quality during the time indication period; and / or prediction of the difference between the candidate serving cell reference signal quality and the threshold cell reference signal quality during the time indication period; and / or prediction of the ratio of the candidate serving cell reference signal quality to the threshold cell reference signal quality during the time indication period.

[0354] Clause 15. The method according to any one of Clauses 1 to 14, wherein the prediction of the priority for the candidate serving cell to become a serving cell of the wireless device further comprises: the accuracy of the prediction of the priority, and / or the confidence interval of the prediction of the priority.

[0355] Clause 16. The method according to any one of Clauses 1 to 15, wherein when the first base station has enabled and / or activated AI / ML functionality, the first base station transmits one or more messages to the second base station.

[0356] Clause 17. An apparatus comprising one or more processors and a memory storing instructions, which, when executed by the one or more processors, cause the apparatus to perform at least the method according to any one of Clauses 1 to 16.

[0357] Clause 18. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of Clauses 1 to 16.

[0358] Clause 19. An apparatus comprising components for performing the method according to any one of Clauses 1 to 16.

[0359] Clause 20. An apparatus comprising circuitry configured to perform the method according to any one of Clauses 1 to 16.

[0360] Clause 21. A computer program product, said computer program product being encoded with instructions for performing the method according to any one of Clauses 1 to 16.

Claims

1. A method comprising: receiving, by a second base station from a first base station, one or more messages comprising: a plurality of time indications; for each time indication of the plurality of time indications, a prediction of one or more candidate serving cells for a wireless device; and for each candidate serving cell of the one or more candidate serving cells, a prediction of a priority of the candidate serving cell to become a serving cell for the wireless device; and. performing, by the second base station, radio access network performance improvement decisions and / or actions using the one or more messages received from the first base station.

2. The method of claim 1, wherein performing the radio access network performance improvement action comprises: regular handover and / or conditional handover and / or dual connectivity and / or multi-connectivity and / or traffic steering and / or coverage area reconfiguration.

3. The method of claim 1 or 2, wherein the one or more messages further comprise: for each candidate serving cell of the one or more candidate serving cells, a prediction of one or more candidate serving beams for the wireless device; for each candidate serving beam of the one or more candidate serving beams, a prediction of a priority of the candidate serving beam to become a serving beam for the wireless device.

4. The method of claim 3, wherein the candidate serving beams for the wireless device during a time indication of the plurality of time indications comprise: beams for which a beam reference signal level is above a threshold for the wireless device during the time indication; and / or beams for which a beam reference signal quality is above a threshold for the wireless device during the time indication.

5. The method of claim 4, wherein the threshold comprises: a minimum beam reference signal level for the beam to provide service to the wireless device; and / or a minimum beam reference signal quality for the beam to provide service to the wireless device.

6. The method of any one of claims 3 to 5, wherein the prediction of the priority of the candidate serving beam to become a serving beam for the wireless device comprises: a prediction of a candidate serving beam reference signal level during a time indication of the plurality of time indications; and / or a prediction of a difference between the candidate serving beam reference signal level and a threshold beam reference signal level during a time indication of the plurality of time indications; and / or a prediction of a ratio of the candidate serving beam reference signal level to a threshold beam reference signal level during a time indication of the plurality of time indications; and / or a prediction of a candidate serving beam reference signal quality during a time indication of the plurality of time indications; and / or a prediction of a difference between the candidate serving beam reference signal quality and a threshold beam reference signal quality during a time indication of the plurality of time indications; and / or a prediction of a ratio of the candidate serving beam reference signal quality to a threshold beam reference signal quality during a time indication of the plurality of time indications. ​ ​ 7. The method of any one of claims 3-6, wherein the prediction of the priority of the candidate serving beam to become a serving beam for the wireless device further comprises: an accuracy of the prediction of the priority, and / or a confidence interval of the prediction of the priority.

8. The method of any one of claims 1-7, wherein a time indication of the plurality of time indications comprises: a time point, and / or a start time and an end time, and / or a duration, and / or a start time and a duration, and / or a duration and an end time.

9. The method of any one of claims 1-8, wherein the candidate serving cell for the wireless device during a time indication of the plurality of time indications comprises: a cell having a cell reference signal level above a threshold for the wireless device during the time indication; and / or a cell having a cell reference signal quality above a threshold for the wireless device during the time indication.

10. The method of claim 9, wherein the threshold comprises: a minimum cell reference signal level for the cell to provide service to the wireless device; and / or a minimum cell reference signal quality for the cell to provide service to the wireless device.

11. The method of any one of claims 1-10, wherein the prediction of the priority of the candidate serving cell to become a serving cell for the wireless device comprises: a prediction of a candidate serving cell reference signal level during a time indication of the plurality of time indications; and / or a prediction of a difference between the candidate serving cell reference signal level and a threshold cell reference signal level during a time indication of the plurality of time indications; and / or a prediction of a ratio of the candidate serving cell reference signal level to a threshold cell reference signal level during a time indication of the plurality of time indications; and / or a prediction of a candidate serving cell reference signal quality during a time indication of the plurality of time indications; and / or a prediction of a difference between the candidate serving cell reference signal quality and a threshold cell reference signal quality during a time indication of the plurality of time indications; and / or a prediction of a ratio of the candidate serving cell reference signal quality to a threshold cell reference signal quality during a time indication of the plurality of time indications.

12. The method of any one of claims 1-11, wherein the prediction of the priority of the candidate serving cell to become a serving cell for the wireless device further comprises: an accuracy of the prediction of the priority, and / or a confidence interval of the prediction of the priority.

13. The method of any one of claims 1-12, wherein the first base station transmits one or more messages to the second base station when the first base station has an AI / ML function enabled and / or activated. ​ ​ 14. An apparatus, the apparatus comprising one or more processors and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least the method of any one of claims 1-13.

15. A non-transitory computer-readable medium containing instructions that, when executed by one or more processors of a device, cause the device to perform the method of any one of claims 1-13.

16. An apparatus comprising means for performing the method of any one of claims 1-13.

17. An apparatus comprising circuitry configured to perform the method of any one of claims 1-13.

18. A computer program product encoding instructions for performing the method of any one of claims 1-13.

Images