[go: up one dir, main page]

WO2025064801A1 - Gestion de session d'unité de données de protocole (pdu) pendant la mobilité dans un réseau d'accès radio - Google Patents

Gestion de session d'unité de données de protocole (pdu) pendant la mobilité dans un réseau d'accès radio Download PDF

Info

Publication number
WO2025064801A1
WO2025064801A1 PCT/US2024/047670 US2024047670W WO2025064801A1 WO 2025064801 A1 WO2025064801 A1 WO 2025064801A1 US 2024047670 W US2024047670 W US 2024047670W WO 2025064801 A1 WO2025064801 A1 WO 2025064801A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
wireless device
admitted
messages
pdu sessions
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/047670
Other languages
English (en)
Inventor
Stanislav Filin
Jian Xu
Esmael Hejazi Dinan
Kyungmin Park
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ofinno LLC
Original Assignee
Ofinno LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ofinno LLC filed Critical Ofinno LLC
Publication of WO2025064801A1 publication Critical patent/WO2025064801A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • Protocol Data Unit Session Management during Mobility in Radio Access Network CROSS-REFERENCE TO RELATED APPLICATIONS
  • FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.
  • FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.
  • NR New Radio
  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.
  • FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.
  • FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.
  • FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.
  • FIG. 6 is an example diagram showing RRC state transitions of a UE.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
  • FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.
  • FIG. 10A illustrates three carrier aggregation configurations with two component carriers.
  • FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.
  • FIG. 11A illustrates an example of an SS/PBCH block structure and location.
  • FIG. 11 B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.
  • FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.
  • FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.
  • FIG. 15 illustrates an example of a wireless device in communication with a base station.
  • FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.
  • FIG. 17 illustrates an example of a functional architecture for artificial intelligence and/or machine learning.
  • FIG. 18 illustrates an example of using AI/ML in a radio access network.
  • FIG. 19 illustrates an example of using AI/ML in a radio access network.
  • FIG. 20 illustrates an example of AI/ML information reporting in a radio access network.
  • FIG. 21 illustrates an example of AI/ML action evaluation in a radio access network.
  • FIG. 22 illustrates an example of a handover in a radio access network.
  • FIG. 23 illustrates an example of a conditional handover in a radio access network.
  • FIG. 24 illustrates an example of a secondary node addition procedure for EN-DC.
  • FIG. 25 illustrates an example of a secondary node addition procedure for MR-DC with 5GC.
  • FIG. 26 illustrates an example of a conditional secondary node addition procedure for EN-DC.
  • FIG. 27 illustrates an example of a conditional secondary node addition procedure for MR-DC with 5GC.
  • FIG. 28 illustrates an example of a secondary node initiated secondary node change procedure for EN-DC.
  • FIG. 29 illustrates an example of a secondary node initiated secondary node change procedure for MR-DC with 5GC.
  • FIG. 30 illustrates an example of a master node initiated secondary node modification procedure for EN-DC.
  • FIG. 31 illustrates an example of a master node initiated secondary node modification procedure for MR-DC with 5GC.
  • FIG. 32 illustrates an example of a handover preparation procedure.
  • FIG. 33 illustrates an example of a SgNB addition preparation procedure for EN-DC.
  • FIG. 34 illustrates an example of a S-NG-RAN node addition preparation procedure for MR-DC with 5GC.
  • FIG. 35 illustrates an example of a SgNB change procedure for EN-DC.
  • FIG. 36 illustrates an example of a S-NG-RAN node change procedure for MR-DC with 5GC.
  • FIG. 37 illustrates an example of a secondary node addition procedure for MR-DC with 5GC.
  • FIG. 38 illustrates an example embodiment of the present disclosure.
  • FIG. 39 illustrates an example embodiment of the present disclosure.
  • FIG. 40 illustrates an example embodiment of the present disclosure.
  • FIG. 41 illustrates an example embodiment of the present disclosure.
  • FIG. 42 illustrates an example embodiment of the present disclosure.
  • FIG. 43 illustrates an example embodiment of the present disclosure.
  • FIG. 44 illustrates an example embodiment of the present disclosure.
  • FIG. 45 illustrates an example embodiment of the present disclosure.
  • FIG. 46 illustrates an example embodiment of the present disclosure.
  • FIG. 47 illustrates an example embodiment of the present disclosure.
  • FIG. 48 illustrates an example embodiment of the present disclosure.
  • Embodiments may be configured to operate as needed.
  • the disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like.
  • Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
  • a base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology.
  • Wireless devices may have some specific capability(ies) depending on wireless device category and/or capabil ity(ies).
  • this disclosure may refer to a subset of the total wireless devices in a coverage area.
  • This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station.
  • the plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like.
  • There may be a plurality of base stations ora plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.
  • a and B are sets and every element of A is an element of B, A is called a subset of B.
  • A is called a subset of B.
  • possible subsets of B ⁇ celH , cell2 ⁇ are: ⁇ celH ⁇ , ⁇ cell2 ⁇ , and ⁇ celH, cell2 ⁇ .
  • the phrase “based on” is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
  • phrases “in response to” is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
  • the phrase “depending on” is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
  • the term configured may relate to the capacity of a device whether the device is in an operational or non- operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.
  • parameters may comprise one or more information objects, and an information object may comprise one or more other objects.
  • an information object may comprise one or more other objects.
  • parameter (IE) N comprises parameter (IE) M
  • parameter (IE) M comprises parameter (IE) K
  • parameter (IE) K comprises parameter (information element) J.
  • N comprises K
  • N comprises J.
  • one or more messages comprise a plurality of parameters
  • modules may be implemented as modules.
  • a module is defined here as an element that performs a defined function and has a defined interface to other elements.
  • the modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) ora combination thereof, which may be behaviorally equivalent.
  • modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Script, or LabVI E WMathScript.
  • modules may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware.
  • programmable hardware comprise: computers, microcontrollers, microprocessors, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs).
  • Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like.
  • FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device.
  • HDL hardware description languages
  • VHDL VHSIC hardware description language
  • Verilog Verilog
  • FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented.
  • the mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator.
  • PLMN public land mobile network
  • the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.
  • CN core network
  • RAN radio access network
  • wireless device 106 wireless device
  • the CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs.
  • DNs data networks
  • the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.
  • the RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols.
  • the communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink.
  • Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques.
  • FDD frequency division duplexing
  • TDD time-division duplexing
  • wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable.
  • a wireless device maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RS U), relay node, automobile, and/or any combination thereof.
  • the term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and/or wireless communication device.
  • the RAN 104 may include one or more base stations (not shown).
  • the term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and/or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and/or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (g N B, associated with NR and/or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and/or any combination thereof.
  • a base station may comprise at least one g N B Central Unit (gNB-CU) and at least one a g NB Distributed Unit (gNB-DU).
  • a base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface.
  • one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors).
  • the size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell.
  • the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.
  • one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors.
  • One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node.
  • RRHs remote radio heads
  • a baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized.
  • a repeater node may amplify and rebroadcast a radio signal received from a donor node.
  • a relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.
  • the RAN 104 maybe deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers.
  • the RAN 104 may be deployed as a heterogeneous network.
  • small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations.
  • the small coverage areas may be provided in areas with high data traffic (or so-called "hotspots”) or in areas with weak macrocell coverage.
  • Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.
  • 3GPP The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1 A.
  • 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS).
  • UMTS Universal Mobile Telecommunications System
  • 4G fourth generation
  • LTE Long-Term Evolution
  • 5G 5G System
  • Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG- RAN).
  • NG- RAN next-generation RAN
  • Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG.
  • NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.
  • NR New Radio
  • FIG. 1 B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented.
  • Mobile communication network 150 may be, for example, a PLMN run by a network operator.
  • mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.
  • 5G-CN 5G core network
  • NG-RAN 154 a 5G core network
  • UEs 156A and 156B collectively UEs 156
  • the 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs.
  • the 5G-CN 152 may set up end- to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality.
  • the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions.
  • the network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).
  • the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF/UPF 158 in FIG. 1B for ease of illustration.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • the UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs
  • the UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering.
  • QoS quality of service
  • the UPF 158B may serve as an anchor point for intra-/i nter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and/or a branching point to support a multi-homed PDU session.
  • the UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.
  • the AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and/or session management function (SMF) selection.
  • NAS may refer to the functionality operating between a CN and a UE
  • AS may refer to the functionality operating between the UE and a RAN.
  • the 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1 B for the sake of clarity
  • the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF).
  • SMF Session Management Function
  • NRF Policy Control Function
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • AF Application Function
  • AUSF Authentication Server Function
  • the NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface.
  • the NG-RAN 154 may include one or more g NBs, illustrated as g NB 160A and g NB 160B (collectively gNBs 160) and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162).
  • the gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations.
  • the gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface.
  • one or more of the gNBs 160 and/or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.
  • the gNBs 160 and/or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface.
  • the NG and Xn interfaces may be established using direct physical connections and/or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network.
  • IP internet protocol
  • the gNBs 160 and/or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface.
  • g N B 160A may be connected to the UE 156A by means of a Uu interface.
  • the NG, Xn, and Uu interfaces are associated with a protocol stack.
  • the protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane.
  • the user plane may handle data of interest to a user.
  • the control plane may handle signaling messages of interest to the network elements.
  • the gNBs 160 and/or the ng-eNBs 162 may be connected to one or more AMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means of one or more NG interfaces.
  • the gNB 160A maybe connected to the UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U) interface.
  • the NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B.
  • the gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface.
  • the NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and/or warning message transmission.
  • the 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF/UPF 158 is shown in FIG. 1 B, one gNB or ng-eNB may be connected to multiple AMF/UPF nodes to provide redundancy and/or to load share across the multiple AMF/UPF nodes.
  • an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages.
  • a protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.
  • FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220.
  • the protocol stacks illustrated in FIG. 2A and FIG. 2B maybe the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.
  • FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220.
  • PHYs physical layers
  • PHYs 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model.
  • the next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.
  • MACs media access control layers
  • RLCs radio link control layers
  • PDCPs packet data convergence protocol layers
  • SDAPs service data application protocol layers
  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack.
  • the SDAPs 215 and 225 may perform QoS flow handling.
  • the UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN.
  • the PDU session may have one or more QoS flows.
  • a UPF of a CN e.g., the UPF 158B
  • the SDAPs 215 and 225 may perform mapping/de-mapping between the one or more QoS flows and one or more data radio bearers.
  • the mapping/de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the g NB 220.
  • the SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220.
  • the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping/de-mapping between the QoS flows and the data radio bearers.
  • QFI QoS flow indicator
  • the PDCPs 214 and 224 may perform header compression/decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering/deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources.
  • the PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover.
  • the PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.
  • PDCPs 214 and 224 may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario.
  • Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • a split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity
  • the PDCPs 214 and 224 may map/de-map the split radio bearer between RLC channels belonging to cell groups.
  • the RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively.
  • the RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions.
  • the RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.
  • TTI Transmission Time Interval
  • the MACs 212 and 222 may perform multiplexing/demultiplexing of logical channels and/or mapping between logical channels and transport channels.
  • the multiplexing/demultiplexing may include multiplexing/demultiplexing of data units, belonging to the one or more logical channels, into/from Transport Blocks (TBs) delivered to/from the PHYs 211 and 221.
  • the MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink.
  • the MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g.
  • HARQ Hybrid Automatic Repeat Request
  • the MACs 212 and 222 may support one or more numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223. [0091]
  • the PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface.
  • the PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.
  • FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack.
  • FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the g N B 220.
  • An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.
  • the downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers.
  • the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404.
  • An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet.
  • the data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.
  • the remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer.
  • the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223.
  • the RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222.
  • the MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block.
  • the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A.
  • the MAC subheaders may be entirely located at the beginning of the MAC PDU.
  • the NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled
  • FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.
  • the MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.
  • FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222.
  • CEs MAC control elements
  • FIG. 4B illustrates two MAC CEs inserted into the MAC PDU.
  • MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.
  • MAC CEs maybe used for in-band control signaling.
  • Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs.
  • a MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.
  • logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types.
  • One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.
  • FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels.
  • Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack.
  • a logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane.
  • a logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE.
  • a logical channel may also be defined by the type of information it carries.
  • the set of logical channels defined by NR include, for example: a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level; a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell; a common control channel (CCCH) for carrying control messages together with random access; a dedicated control channel (DCCH) for carrying control messages to/from a specific the UE to configure the UE; and a dedicated traffic channel (DT CH) for carrying user data to/from a specific the UE.
  • PCCH paging control channel
  • BCCH broadcast control channel
  • MIB master information block
  • SIBs system information blocks
  • Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface.
  • the set of transport channels defined by NR include, for example: a paging channel (PCH) for carrying paging messages that originated from the PCCH; a broadcast channel (BCH) for carrying the MIB from the BCCH; a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH; an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.
  • PCH paging channel
  • BCH broadcast channel
  • DL-SCH downlink shared channel
  • UL-SCH uplink shared channel
  • RACH random access channel
  • the PHY may use physical channels to pass information between processing levels of the PHY.
  • a physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels.
  • the PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1/L2 control channels.
  • the set of physical channels and physical control channels defined by NR include, for example: a physical broadcast channel (PBCH) for carrying the MIB from the BCH; a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL- SCH, as well as paging messages from the PCH; a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below; a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and a physical random access channel (PRACH) for random access.
  • PBCH physical broadcast channel
  • PDSCH physical downlink shared channel
  • DCI down
  • the physical layer Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer.
  • the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.
  • FIG. 2B illustrates an example NR control plane protocol stack.
  • the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224.
  • the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.
  • RRCs radio resource controls
  • the NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN.
  • the NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported.
  • the NAS messages may be transported using the AS of the Uu and NG interfaces.
  • NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.
  • the RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN.
  • the RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages.
  • RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers.
  • the MAC may multiplex control-plane and user-plane data into the same transport block (TB).
  • the RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLE); and/or NAS message transfer.
  • RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.
  • FIG. 6 is an example diagram showing RRC state transitions of a UE.
  • the UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2Aand FIG. 2B, or any other wireless device described in the present disclosure.
  • a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).
  • RRC connected 602 e.g., RRC_CONNECTED
  • RRC idle 604 e.g., RRC_I DLE
  • RRC inactive 606 e.g., RRCJNACTIVE
  • the UE has an established RRC context and may have at least one RRC connection with a base station
  • the base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure.
  • the base station with which the UE is connected may have the RRC context for the UE.
  • the RRC context referred to as the UE context, may comprise parameters for communication between the UE and the base station.
  • These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information.
  • bearer configuration information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • security information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • PHY e.g., MAC, RLC, PDCP, and/or SDAP layer configuration information
  • the RAN e.g., the RAN 104 or the NG-RAN 154
  • the UE may measure the signal levels (e.g., reference signal levels) from a serving cell
  • the UE’s serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements.
  • the RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.
  • RRC idle 604 an RRC context may not be established for the UE.
  • the UE may not have an RRC connection with the base station.
  • the UE While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power).
  • the UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN.
  • Mobility of the UE may be managed by the UE through a procedure known as cell reselection.
  • the RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.
  • Tracking areas may be used to track the UE at the CN level.
  • the CN e.g., the CN 102 or the 5G-CN 152 may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE’s location and provide the UE with a new the UE registration area.
  • RAN areas may be used to track the UE at the RAN level.
  • the UE may be assigned a RAN notification area.
  • a RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs.
  • a base station may belong to one or more RAN notification areas.
  • a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.
  • a base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station.
  • An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.
  • AgNB such as gNBs 160 in FIG. 1B, maybe split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU).
  • a gNB-CU may be coupled to one or more gNB-DUs using an F1 interface.
  • the gNB-CU may comprise the RRC, the PDCP, and the SOAP.
  • a gNB-DU may comprise the RLC, the MAC, and the PHY.
  • OFDM orthogonal frequency divisional multiplexing
  • FAM frequency divisional multiplexing
  • M-QAM M-quadrature amplitude modulation
  • M-PSK M-phase shift keying
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols
  • the IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers.
  • the output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers.
  • the F time-domain samples may form a single OFDM symbol.
  • an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency.
  • the F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • An NR frame may be identified by a system frame number (SFN).
  • the SFN may repeat with a period of 1024 frames.
  • one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration.
  • a subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.
  • the duration of a slot may depend on the numerology used for the OFDM symbols of the slot.
  • a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range).
  • a numerology may be defined in terms of subcarrier spacing and cyclic prefix duration.
  • subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz
  • cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps.
  • NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 ps; 30 kHz/2.3 ps; 60 kHz/1.2 ps; 120 kHz/0.59 ps; and 240 kHz/0.29 ps.
  • a slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).
  • a numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe.
  • FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration).
  • a subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled.
  • scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.
  • FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
  • the slot includes resource elements (REs) and resource blocks (RBs).
  • An RE is the smallest physical resource in NR.
  • An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8.
  • An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8.
  • Such a limitation may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
  • FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier.
  • multiple numerologies may be supported on the same carrier.
  • NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and/or for other purposes, a UE may adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.
  • NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation.
  • BWP may be defined by a subset of contiguous RBs on a carrier.
  • a UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell).
  • one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell.
  • the serving cell When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.
  • a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same.
  • a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.
  • a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space.
  • CORESETs control resource sets
  • a search space is a set of locations in the time and frequency domains where the UE may find control information.
  • the search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs).
  • a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.
  • a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions.
  • a UE may receive downlink receptions (e.g. , PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP.
  • the UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).
  • One or more BWP indicator fields may be provided in Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • a value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions.
  • the value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.
  • a base station may semi-statical ly configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.
  • a base station may configure a UE with a BWP inactivity timer value for a PCell.
  • the UE may start or restart a BWP inactivity timer at any appropriate time.
  • the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation.
  • the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero).
  • the UE may switch from the active downlink BWP to the default downlink BWP.
  • a base station may semi-statically configure a UE with one or more BWPs.
  • a UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).
  • Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and/or an initiation of random access.
  • FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.
  • a UE configured with the three BWPs may switch from one BWP to another BWP at a switching point.
  • the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz.
  • the BWP 902 may be an initial active BWP
  • the BWP 904 may be a default BWP.
  • the UE may switch between BWPs at switching points.
  • the UE may switch from the BMP 902 to the BWP 904 at a switching point 908.
  • the switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DCI indicating BWP 904 as the active BWP.
  • the UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP.
  • the UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and/or in response receiving a DCI indicating BWP 904 as the active BWP.
  • the UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.
  • UE procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the UE would use these values for a primary cell.
  • CA carrier aggregation
  • the aggregated carriers in CA may be referred to as component carriers (CCs).
  • CCs component carriers
  • the CCs may have three configurations in the frequency domain.
  • FIG. 10A illustrates the three CA configurations with two CCs.
  • the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band.
  • the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap.
  • the two CCs are located in frequency bands (frequency band A and frequency band B).
  • up to 32 CCs may be aggregated.
  • the aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD).
  • a serving cell for a UE using CA may have a downlink CC.
  • one or more uplink CCs may be optionally configured for a serving cell.
  • the ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.
  • one of the aggregated cells for a UE may be referred to as a primary cell (PCell).
  • the PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover.
  • the PCell may provide the UE with NAS mobility information and the security input.
  • UEs may have different PCells.
  • the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC).
  • the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC).
  • the other aggregated cells for the UE may be referred to as secondary cells (SCells) .
  • SCells secondary cells
  • the SCells may be configured after the PCell is configured for the UE.
  • an SCell may be configured through an RRC Connection Reconfiguration procedure.
  • the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC).
  • DL SCC downlink secondary CC
  • UL SCC uplink secondary CC
  • Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells maybe activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated.
  • a bitmap e.g., one bit per SCell
  • Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).
  • Downlink control information such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling.
  • the DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling.
  • Uplink control information e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and/or Rl
  • the PUCCH of the PCell may become overloaded.
  • Cells may be divided into multiple PUCCH groups.
  • FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.
  • a PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively.
  • the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013.
  • the PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053.
  • One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023.
  • One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063.
  • Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010 shown as UC1 1031, UC1 1032, and UC1 1033, may be transmitted in the uplink of the PCell 1021.
  • Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071, UC1 1072, and UC1 1073, maybe transmitted in the uplink of the PSCell 1061.
  • a cell comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index.
  • the physical cell ID or the cell index may identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used.
  • a physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier.
  • a cell index may be determined using RRC messages.
  • a physical cell ID may be referred to as a carrier ID
  • a cell index may be referred to as a carrier index.
  • the disclosure when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier.
  • the same/similar concept may apply to, for example, a carrier activation.
  • the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.
  • a multi-carrier nature of a PHY may be exposed to a MAC.
  • a HARQ entity may operate on a serving cell.
  • a transport block may be generated per assignment/grant per serving cell.
  • a transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.
  • a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A).
  • RSs Reference Signals
  • the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and/or SRS, as shown in FIG. 5B).
  • the PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station.
  • the PSS and the SSS may be provided in a synchronization signal (SS) I physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • the base station may periodically transmit a burst of SS/PBCH blocks.
  • FIG. 11A illustrates an example of an SS/PBCH block's structure and location.
  • a burst of SS/PBCH blocks may include one or more SS/PBCH blocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11 A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG.
  • 11 A is an example, and that these parameters (number of SS/PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS/PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor.
  • the UE may assume a subcarrier spacing for the SS/PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.
  • the SS/PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers).
  • the PSS, the SSS, and the PBCH may have a common center frequency.
  • the PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers.
  • the SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers.
  • the PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.
  • the SS/PBCH block may be a celldefining SS block (CD-SSB).
  • a primary cell may be associated with a CD-SSB.
  • the CD-SSB may be located on a synchronization raster.
  • a cell selection/search and/or reselection may be based on the CD- SSB.
  • the SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary.
  • PCI physical cell identifier
  • the PBCH may use a QPSK modulation and may use forward error correction (FEC).
  • FEC forward error correction
  • the FEC may use polar coding.
  • One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH.
  • the PBCH may include an indication of a current system frame number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station.
  • the PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell.
  • MIB master information block
  • the RMSI may include a System Information Block Type 1 (SIB1 ).
  • SIB1 may contain information needed by the UE to access the cell.
  • the UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH.
  • the PDSCH may include the SIB1.
  • the SIB1 may be decoded using parameters provided in the MIB.
  • the PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1 , the UE may be pointed to a frequency.
  • the UE may search for an SS/PBCH block at the frequency to which the UE is pointed.
  • the UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters).
  • QCL quasi co-located
  • SS/PBCH blocks may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell).
  • a first SS/PBCH block may be transmitted in a first spatial direction using a first beam
  • a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.
  • a base station may transmit a plurality of SS/PBCH blocks.
  • a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks.
  • the PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same.
  • the CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI).
  • the base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose.
  • the base station may configure a UE with one or more of the same/similar CSI-RSs.
  • the UE may measure the one or more CSI-RSs.
  • the UE may estimate a downlink channel state and/or generate a CSI report based on the measuring of the one or more downlink CSI-RSs.
  • the UE may provide the CSI report to the base station.
  • the base station may use feedback provided by the UE (e.g. , the estimated downlink channel state) to perform link adaptation.
  • the base station may semi-statically configure the UE with one or more CSI-RS resource sets.
  • a CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity.
  • the base station may selectively activate and/or deactivate a CSI-RS resource.
  • the base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated.
  • the base station may configure the UE to report CSI measurements.
  • the base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently.
  • periodic CSI reporting the UE maybe configured with a timing and/or periodicity of a plurality of CSI reports.
  • aperiodic CSI reporting the base station may request a CSI report.
  • the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements.
  • the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting.
  • the base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.
  • the CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports.
  • the UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET.
  • the UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks.
  • Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation.
  • the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH).
  • An NR network may support one or more variable and/or configurable DMRS patterns for data demodulation.
  • At least one downlink DMRS configuration may support a front-loaded DMRS pattern.
  • a front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols).
  • a base station may semi- statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH.
  • a DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MI MO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE.
  • a radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence may be the same or different.
  • the base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix.
  • the UE may use the one or more downlink DMRSs for coherent demodulation/channel estimation of the PDSCH.
  • a transmitter may use a precoder matrices for a part of a transmission bandwidth.
  • the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth.
  • the first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth.
  • the UE may assume that a same precoding matrix is used across a set of PRBs.
  • the set of PRBs may be denoted as a precoding resource block group (PRG).
  • PRG precoding resource block group
  • a PDSCH may comprise one or more layers.
  • the UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH.
  • a higher layer may configure up to 3 DMRSs for the PDSCH.
  • Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS.
  • An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains.
  • the UE may transmit an uplink DMRS to a base station for channel estimation.
  • the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels.
  • the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.
  • the uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel.
  • the base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front- loaded DMRS pattern.
  • the front-loaded DMRS maybe mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols).
  • One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH.
  • the base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS.
  • An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different.
  • CP-OFDM cyclic prefix orthogonal frequency division multiplexing
  • a PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH.
  • a higher layer may configure up to three DMRSs for the PUSCH.
  • Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE.
  • the presence and/or pattern of uplink PT- RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI.
  • MCS Modulation and Coding Scheme
  • a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS.
  • a radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain.
  • a frequency domain density may be associated with at least one configuration of a scheduled bandwidth.
  • the UE may assume a same precoding for a DMRS port and a PT-RS port.
  • a number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource.
  • uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.
  • SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation.
  • SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies.
  • a scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE.
  • the base station may semi-statically configure the UE with one or more SRS resource sets For an SRS resource set, the base station may configure the UE with one or more SRS resources.
  • An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter.
  • an SRS resource in an SRS resource set of the one or more SRS resource sets may be transmitted at a time instant (e.g., simultaneously).
  • the UE may transmit one or more SRS resources in SRS resource sets.
  • An NR network may support aperiodic, periodic and/or semi-persistent SRS transmissions.
  • the UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats.
  • At least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets.
  • An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling.
  • An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats.
  • the UE when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.
  • An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port.
  • the channel e.g., fading gain, multipath delay, and/or the like
  • a first antenna port and a second antenna port may be referred to as quasi co- located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed.
  • the one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving ( x) parameters.
  • FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains.
  • CSI-RSs channel state information reference signals
  • a square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell.
  • a base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs.
  • CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements.
  • the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources.
  • the base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration.
  • the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals.
  • TCI transmission configuration indication
  • the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and/or a DCI).
  • the UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states.
  • the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam.
  • the UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station.
  • the base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.
  • SRS sounding reference signal
  • a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (Rl).
  • FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3.
  • Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow).
  • Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow).
  • the UE and/or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement.
  • the UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.
  • a UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure.
  • the UE may transmit a BFR request (e.g. , a preamble, a UCI, an SR, a MAC CE, and/or the like) based on the initiating of the BFR procedure.
  • the UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and/or the like).
  • the base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and/or the like).
  • the RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.
  • the channel characteristics e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like
  • a network e.g., a gNB and/or an ng-eNB of a network
  • the UE may initiate a random access procedure.
  • a UE in an RRC_I DLE state and/or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network.
  • the UE may initiate the random access procedure from an RRC_CONNECTED state.
  • the UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and/or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized).
  • the UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and/or the like).
  • SIBs system information blocks
  • the UE may initiate the random access procedure for a beam failure recovery request.
  • a network may initiate a random access procedure for a handover and/or for establishing time alignment for an SCell addition.
  • FIG. 13A illustrates a four-step contention-based random access procedure.
  • a base station may transmit a configuration message 1310 to the UE.
  • the procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 31313, and a Msg 4 1314.
  • the Msg 1 1311 may include and/or be referred to as a preamble (or a random access preamble).
  • the Msg 2 1312 may include and/or be referred to as a random access response (RAR).
  • RAR random access response
  • the configuration message 1310 may be transmitted, for example, using one or more RRC messages.
  • the one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE.
  • RACH random access channel
  • the one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and/or dedicated parameters (e.g., RACH-configDedicated).
  • the base station may broadcastor multicast the one or more RRC messages to one or more UEs.
  • the one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and/or Msg 3 1313.
  • the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission).
  • the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and/or a power offset value between preamble groups.
  • the one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).
  • at least one reference signal e.g., an SSB and/or CSI-RS
  • an uplink carrier e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier.
  • the Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions).
  • An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B).
  • a preamble group may comprise one or more preambles.
  • the UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 31313.
  • the UE may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS).
  • the UE may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.
  • the UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 3 1313.
  • the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e g., group A and group B).
  • a base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs).
  • the UE may determine the preamble to include in Msg 1 1311 based on the association.
  • the Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions.
  • the UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion.
  • One or more RACH parameters e.g., ra-ssb-OccasionMsklndex and/or ra-OccasionList
  • the UE may perform a preamble retransmission if no response is received following a preamble transmission.
  • the UE may increase an uplink transmit power for the preamble retransmission.
  • the UE may select an initial preamble transmit power based on a pathloss measurement and/or a target received preamble power configured by the network.
  • the UE may determine to retransmit a preamble and may ramp up the uplink transmit power.
  • the UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission.
  • the ramping step may be an amount of incremental increase in uplink transmit power for a retransmission.
  • the UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and/or CSI-RS) that is the same as a previous preamble transmission.
  • the UE may count a number of preamble transmissions and/or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER).
  • the UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).
  • the Msg 2 1312 received by the UE may include an RAR.
  • the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.
  • the Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311.
  • the Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI).
  • RA-RNTI random access RNTI
  • the Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station.
  • the Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 31313, and/or a Temporary Cell RNTI (TC-RNTI).
  • TC-RNTI Temporary Cell RNTI
  • the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312.
  • the UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble.
  • the UE may start the time window one or more symbols after a last symbol of the preamble (e.g , at a first PDCCH occasion from an end of a preamble transmission).
  • the one or more symbols may be determined based on a numerology.
  • the PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message.
  • the UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure.
  • the UE may use random access RNTI (RA-RNTI).
  • the RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble.
  • the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions.
  • RA-RNTI 1 + sjd + 14 x tjd + 14 x 80 * fjd + 14 x 80 x 8 x ul_carrier_id
  • s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g .
  • tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 ⁇ tjd ⁇ 80)
  • f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0 ⁇ f_id ⁇ 8)
  • ul_carrierjd may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).
  • Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves Contention resolution (e.g., using the Msg 3 1313 and the Msg 4 1314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE.
  • Contention resolution e.g., using the Msg 3 1313 and the Msg 4 1314.
  • the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and/or any other suitable identifier).
  • the Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRC_I DLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI.
  • the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed.
  • the UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier.
  • An initial access (e.g., random access procedure) may be supported in an uplink carrier.
  • a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier.
  • the network may indicate which carrier to use (NUL or SUL).
  • the UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold.
  • Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on the selected carrier.
  • the UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases.
  • the UE may determine and/or switch an uplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on a channel clear assessment (e.g., a listen- before-talk).
  • FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE.
  • the configuration message 1320 may be analogous in some respects to the configuration message 1310.
  • the procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.
  • the Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.
  • the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and/or the Msg 4 1314.
  • the contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and/or handover.
  • a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321.
  • the UE may receive, from the base station via PDCCH and/or RRC, an indication of a preamble (e.g., ra-Preamblelndex).
  • the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR.
  • a time window e.g., ra-ResponseWindow
  • the base station may configure the UE with a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld).
  • the UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space.
  • C-RNTI Cell RNTI
  • the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322.
  • the UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI.
  • the UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier.
  • the UE may determine the response as an indication of an acknowledgement for an SI request.
  • the Msg B 1332 may comprise contents that are similar and/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated in FIG. 13A.
  • an RAR e.g., an RAR
  • the UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and/or an uplink transmit power for the preamble 1341 and/or the transport block 1342 included in the Msg A 1331.
  • the RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and/or a power control for the preamble 1341 and/or the transport block 1342.
  • MCS modulation and coding schemes
  • a time-frequency resource for transmission of the preamble 1341 e.g., a PRACH
  • a time-frequency resource for transmission of the transport block 1342 e.g., a PUSCH
  • the RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and/or receiving Msg B 1332.
  • the transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and/or device information (e.g., an International Mobile Subscriber Identity (IMSI)).
  • the base station may transmit the Msg B 1332 as a response to the Msg A 1331.
  • the Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI ora TC-RNTI).
  • RNTI e.g., a C-RNTI ora TC-RNTI
  • the UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and/or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).
  • a UE and a base station may exchange control signaling.
  • the control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2).
  • the control signaling may comprise downlink control signaling transmitted from the base station to the UE and/or uplink control signaling transmitted from the UE to the base station.
  • the downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and/or a transport format; a slot format information; a preemption indication; a power control command; and/or any other suitable signaling.
  • the UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH).
  • the payload transmitted on the PDCCH may be referred to as downlink control information (DCI).
  • the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.
  • a base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors.
  • CRC cyclic redundancy check
  • the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits.
  • the identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).
  • RNTI radio network temporary identifier
  • a DCI having CRC parity bits scrambled with a random access RNTI may indicate a random access response (RAR).
  • a DCI having CRC parity bits scrambled with a cell RNTI may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access.
  • a DCI having CRC parity bits scrambled with a temporary cell RNTI may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A).
  • the base station may transmit the DCIs with one or more DCI formats.
  • DCI format 0_0 may be used for scheduling of PUSCH in a cell.
  • DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • DCI format 0 J may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0).
  • DCI format 1_0 may be used for scheduling of PDSCH in a cell.
  • DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0).
  • DCI format 2_0 may be used for providing a slot format indication to a group of UEs.
  • DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE.
  • DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH.
  • DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs.
  • DCI format(s) for new functions may be defined in future releases.
  • DCI formats may have different DCI sizes, or may share the same DCI size.
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • the base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs).
  • a CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces.
  • the base station may configure a CORESET in the time-frequency domain.
  • a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot.
  • the first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain.
  • a third CORESET 1403 occurs ata third symbol in the slot.
  • a fourth CORESET 1404 occurs at the seventh symbol in the slot.
  • FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.
  • the CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and/or frequency- selective transmission of control channels).
  • the base station may perform different or same CCE-to-REG mapping on different CORESETs.
  • a CORESET may be associated with a CCE-to-REG mapping by RRC configuration.
  • a CORESET may be configured with an antenna port quasi co-location (QCL) parameter.
  • the antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.
  • DMRS demodulation reference signal
  • the base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets.
  • the configuration parameters may indicate an association between a search space set and a CORESET.
  • a search space set may comprise a set of PDCCH candidates formed by CCEsata given aggregation level.
  • the configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE- specific search space set.
  • a set of CCEs in the common search space set may be predefined and known to the UE.
  • a set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).
  • the UE may determine a time-frequency resource fora CORESET based on RRC messages.
  • the UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET.
  • the UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages.
  • the UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set.
  • the UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs.
  • the UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station.
  • the uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL- SCH transport blocks.
  • HARQ hybrid automatic repeat request
  • the UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block.
  • Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel.
  • the UE may transmit the CSI to the base station.
  • the base station based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission.
  • Uplink control signaling may comprise scheduling requests (SR).
  • SR scheduling requests
  • the UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two.
  • PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more.
  • PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code.
  • PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.
  • FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure.
  • the wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown in FIG. 15.
  • the base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506.
  • the communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink.
  • Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and/or some combination of the two duplexing techniques. Other techniques are also permitted, including multipath, such as downlink over a Uu interface and uplink over a PC5 interface.
  • data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504.
  • the data may be provided to the processing system 1508 by, for example, a core network.
  • data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502.
  • the processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission.
  • Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.
  • Layer 3 may include an RRC layer as with respect to FIG. 2B.
  • the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (Ml MO) or multi-antenna processing, and/or the like.
  • a reception processing system 1512 may receive the uplink transmission from the wireless device 1502.
  • a reception processing system 1522 may receive the downlink transmission from base station 1504.
  • the reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality.
  • Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.
  • the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and/or the like.
  • a wireless device 1502 and the base station 1504 may include multiple antennas.
  • the multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming.
  • the wireless device 1502 and/or the base station 1504 may have a single antenna.
  • the processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively.
  • Memory 1514 and memory 1524 may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518 to carry out one or more of the functionalities discussed in the present application.
  • the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and/or the reception processing system 1522 may be coupled to a memory (eg., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.
  • the processing system 1508 and/or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively.
  • the one or more peripherals 1516 and the one or more peripherals 1526 may include software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g. , for a motor vehicle), and/or one or more sensors (e.g.
  • the processing system 1508 and/or the processing system 1518 may receive user input data from and/or provide user output data to the one or more peripherals 1516 and/or the one or more peripherals 1526.
  • the processing system 1518 in the wireless device 1502 may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device 1502.
  • the power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof.
  • the processing system 1508 and/or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively.
  • the GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.
  • FIG. 16A illustrates an example structure for uplink transmission.
  • a baseband signal representing a physical uplink shared channel may perform one or more functions.
  • the one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP- OFDM signal for an antenna port; and/or the like.
  • SC-FDMA Single Carrier-Frequency Division Multiple Access
  • FIG. 16A illustrates an example structure for uplink transmission.
  • These functions are illustrated as examples. Other mechanisms may be implemented in various embodiments.
  • FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency.
  • the baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.
  • PRACH Physical Random Access Channel
  • FIG. 16C illustrates an example structure for downlink transmissions.
  • a baseband signal representing a physical downlink channel may perform one or more functions.
  • the one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complexvalued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued timedomain OFDM signal for an antenna port; and/or the like.
  • These functions are illustrated as examples. Other mechanisms may be implemented in various embodiments.
  • FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency.
  • the baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.
  • a wireless device may receive from a base station one or more messages (e.g. RRC messages) including configuration parameters of a plurality of cells (e.g. primary cell, secondary cell).
  • the wireless device may communicate with at least one base station (e.g. two or more base stations in dual connectivity) via the plurality of cells.
  • the one or more messages (e.g. as a part of the configuration parameters) may include parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device.
  • the configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc.
  • the configuration parameters may include parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.
  • a timer may begin running once the timer is started and continue running until the timer is stopped or until it expires.
  • a timer may be started if the timer is not running or restarted if the timer is running.
  • a timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once the timer reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g , due to BWP switching).
  • a timer may be used to measure a time period/window for a process.
  • a timer may be used to measure a time period/window for the procedure.
  • a random access response window timer may be used for measuring a window of time for receiving a random access response.
  • the time difference between two time stamps may be used.
  • a timer may be implemented as a countdown timer that expires when a value of zero is reached, a count-up timer that expires when a target value is reached, or any other desired way.
  • a timer may stop and expire at the same or a timer may be stopped before expiry and may potentially be restarted.
  • a timer can be set for a single continuous time period having a single start time and a single end time.
  • a timer can be set for a set of discontinuous time segments, each segment having a start time and end time. In the discontinuous case, the time periods can be periodic as to start time and/or end time, or can be aperiodic. Other example implementations may be provided to restart a measurement of a time window.
  • FIG. 17 illustrates an example of a functional architecture for artificial intelligence (Al) and/or machine learning (ML).
  • Al artificial intelligence
  • ML machine learning
  • the data collection function 1701 is a function that provides input data to the model training function 1702 and the model inference function 1703.
  • Input data from the data collection function 1701 to the model training function 1702 is called training data.
  • the training data is used to train, validate, and test an AI/ML model in the model training function 1702. Examples of the training data are measurements and statistics.
  • Input data from the data collection function 1701 to the model inference function 1703 is called inference data.
  • Inference data is used to generate an output in the model inference function 1702.
  • Inference data is also used to generate model performance feedback in the model inference function 1702. Examples of the inference data are measurements and statistics.
  • the model training function 1702 is a function that may be used for training, validation, and testing of an AI/ML model.
  • the model training function 1702 may also perform AI/ML model-specific data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) using training data received from the data collection function 1701.
  • AI/ML model may be deployed into the model inference function 1703.
  • the AI/ML model may be trained and tested by the model training function 1702 (e.g., before deployment).
  • the model inference function 1703 is a function that uses the deployed AI/ML model to generate inference output. This output is provided to the actor function 1704 to perform actions based on the received output from the model inference function 1703.
  • the model inference function 1703 may perform AI/ML model-specific data preparation (e g., data pre-processing and cleaning, formatting, and transformation) using training data received from the data collection function 1701. Examples of the output are determinations (predictions), policies, strategies, execution plans, and requests.
  • the actor function 1704 is a function that receives the output from the model inference function 1703 and performs corresponding actions.
  • feedback information may be generated and forwarded to the data collection function 1701, where it may become a part of the training data or the inference data.
  • Examples of the feedback information are measurements and performance indicators.
  • the model inference function 1703 may use inference data (including feedback information) from the data collection function 1701 to monitor the performance of the deployed AI/ML model and to report the model performance feedback to the model training function 1702. For example, with time, characteristics of the data used for training the currently deployed AI/ML model may change. In this case, the currently deployed AI/ML model may not provide sufficiently accurate output. This may be indicated in the model performance feedback. Based on the received model performance feedback, the model training function 1702 may deploy an updated AI/ML model to the model inference function 1703.
  • processes of the AI/ML model training, the AI/ML model update, and the AI/ML model inference may be performed in parallel in real-time. This is called online training, as opposite to offline training.
  • offline training an AI/ML model may be trained, validated, tested, and can provide acceptable performance prior to deployment.
  • the AI/ML functional architecture illustrated in FIG. 17 may be used to solve various tasks in radio access networks. For example, it can be used to improve network signaling efficiency, network energy efficiency, perform load balancing, perform mobility optimization, or any other suitable task.
  • Each element of an AI/ML functional architecture may reside and/or be deployed within a single network element, or across multiple network elements. Different elements of a single AI/ML functional architecture may reside and/or be deployed within a single network element, or in different network elements.
  • the signaling within the AI/ML functional architecture (e.g the arrows) may be performed within a particular network element or using network interfaces between network elements.
  • the network elements may include, for example, a wireless device ( UE, etc ), an access network (radio access network, base station, eNB, ng-eNB, gNB, gNB-CU, gNB-DU, etc.), a core network element (AMF, SMF, UPF, NWDAF, etc.), and/or an operations, administration, and maintenance (0AM).
  • a wireless device UE, etc
  • an access network radio access network
  • base station eNB, ng-eNB, gNB, gNB-CU, gNB-DU, etc.
  • AMF operations, administration, and maintenance
  • training data and inference data may comprise measurements, estimates, configuration information, etc.
  • output of the model inference 1703 may comprise a prediction, estimate, action, determination, etc.
  • feedback may comprise measurements, UE key performance indicators (KPIs), system wide KPIs, etc.
  • the methods described in the present disclosure may include one or more determinations (e.g., choices, selections, decisions, etc.).
  • FIG. 18 and FIG. 19 demonstrate that one or more of the determinations described herein may be made based on an AI/ML functional architecture analogous to the AI/ML functional architecture depicted in FIG. 17.
  • FIG. 18 illustrates an example in which model training is performed by an OAM
  • FIG. 19 illustrates an example in which model training is performed by a base station.
  • model inference is performed by a base station.
  • the base station may comprise the actor 1704 and/or use an output of the model inference 1703 to perform one or more actions (e.g., energy saving actions).
  • FIGS. 17 - 19 merely demonstrate that the one or more determinations described in the present disclosure may optionally be AI/ML-based, either in full or in part.
  • FIG. 18 illustrates an example of using AI/ML in a radio access network.
  • FIG. 18 may include an AI/ML functional architecture analogous to the AI/ML functional architecture of FIG 17.
  • the model training function 1702 is deployed in an OAM and the model inference function 1703 is deployed in the BS1 (e.g., base station, base station distributed unit, and/or base station central unit).
  • the BS1 e.g., base station, base station distributed unit, and/or base station central unit.
  • the UE performs measurement(s) 1802.
  • the measurements 1802 maybe performed based on the measurement configuration message 1801.
  • the UE sends a measurement report 1803 to the BS1 .
  • BS1 Based on the output of the model inference 1810, BS1 performs action(s) 1812. These actions may involve UEs and other BSs, for example, the UE and the BS2 shown in FIG. 18. 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 a radio access network. These actions may include, for example, sending predictions from the BS1 to the BS2 and/or performing handover of one or more wireless devices from the BS1 to the BS2.
  • the UE sends the UE measurement report 1907 to the BS1.
  • the AI/ML information request 2001 may comprise a parameter indicating which measurements are requested (e.g., the parameter indicating which measurements are requested may be a report characteristics parameter).
  • the measurements that are requested may be, for example, a feedback information after one or more actions and/or other measurements used for AI/ML.
  • the parameter indicating which measurements are requested may comprise a list of measurements that are requested.
  • the list of measurements that are requested may comprise a bitmap where each position corresponds to a specific measurement. A value of “1” and/or TRUE may indicate that the measurement corresponding to the position of the value is requested. A value of “0” and/or FALSE may indicate that the measurement corresponding to the position of the value is not requested.
  • the AI/ML information response 2002 may comprise a list of the requested measurements (list of measurements requested by the BS1 from the BS2 in the AI/ML information request 2001) that the BS2 is able to report to the BS1 (e.g. , the parameter indicating which measurements will be provided may be a failed reporting characteristics parameter).
  • the list of the requested measurements that the BS2 is able to report to the BS1 may comprise a bitmap where each position corresponds to a specific measurement. A value of “1” and/or TRUE may indicate that the BS2 is able to report to the BS1 the requested measurement corresponding to the position.
  • the BS2 may send to the BS1 , AI/ML information failure 2003.
  • the AI/ML information failure 2003 may comprise the measurement identifier at the BS1 and/or the measurement identifier at the BS2 from the AI/ML information request 2001.
  • the AI/ML information failure 2003 may comprise a parameter (e.g., cause) indicating why the predictions and/or measurements are not supported.
  • the parameter indicating why the predictions and/or the measurements are not supported may comprise, for example, AI/ML model is not supported and/or AI/ML model is not active and/or AI/ML model is overloaded and/or prediction is not supported and/or measurement is not supported and/or prediction is not available and/or measurement is not available and/or reporting configuration/periodicity is not supported.
  • the BS2 may send to the BS1 , AI/ML information update 2004.
  • the AI/ML information update 2004 may comprise the measurement identifier at the BS1 and/or the measurement identifier at the BS2 from the AI/ML information request 2001.
  • the AI/ML information update 2004 may comprise a list of cells for which the predictions are reported.
  • the list of cells for which the predictions are reported may correspond to the list of cells for which the predictions are requested in the AI/ML information request 2001
  • the list of cells for which the predictions are reported may comprise a list of cell identifiers (e.g., global NG-RAN cell identity).
  • the AI/ML information update 2004 may comprise an energy cost parameter.
  • the energy cost parameter may comprise a measurement and/or a prediction of the energy cost.
  • the BS2 may send to the BS1, the AI/ML information update 2004 according to the configuration (e.g., reporting periodicity) specified in the AI/ML information request 2001.
  • the BS1 may send to the BS2, the AI/ML information request 2001 with the registration request parameter equal to stop and the reporting periodicity parameter equal to 2000 ms.
  • the BS2 may send to the BS1, the AI/ML information update 2004 with the requested predictions and/or measurements until the BS2 receives from the BS1 corresponding (with the same measurement identifiers) AI/ML information request 2001 with the registration request parameter equal to stop.
  • the BS2 may send to the BS1 , the AI/ML information update 2004 only one time (e.g., if reporting periodicity parameter is not present in the AI/ML information request 2001).
  • FIG. 21 illustrates an example of AI/ML action evaluation in a radio access network.
  • the BS1 may send to the BS2, an AI/ML action evaluation request 2101.
  • the AI/ML action evaluation request 2101 may comprise a request for the BS2 to evaluate a potential action of the BS1.
  • the BS1 may receive from the BS2, an AI/ML action evaluation response 2102.
  • the AI/ML action evaluation response 2102 may comprise a result of the evaluation by the BS2 of the potential action of the BS1.
  • the AI/ML action evaluation request 2101 may comprise a request for a prediction of an increase in energy consumption of the BS2 in case one or more UEs are handed over from the BS1 to the BS2.
  • the AI/ML action evaluation response 2102 may comprise the prediction of an increase in energy consumption of the BS2 in case the one or more UEs are handed over from the BS1 to the BS2.
  • the AI/ML action evaluation request 2101 may comprise a request for a prediction of a performance (e.g., data rate, packet delay, packet loss) of a UE in case the UE is handed over from the BS1 to the BS2
  • the AI/ML action evaluation response 2102 may comprise the prediction of a performance of the UE in case the UE is handed over from the BS1 to the BS2.
  • FIG. 22 illustrates an example of a handover in a radio access network.
  • the BS1 and the UE may perform measurement control and reports 2201.
  • the BS1 may send to the UE, one or more messages comprising one or more configuration parameters for the UE measurements procedures.
  • the UE may send to the BS1 , one or more messages comprising measurement results determined based on the configuration parameters.
  • the BS1 may determine a handover decision 2202 for the UE based on the measurement results received from the UE (e.g. , MeasurementReporf) and/or radio resource management (RRM) information.
  • the measurement results received from the UE e.g. , MeasurementReporf
  • RRM radio resource management
  • the BS1 may send to the BS2, a handover request 2203 requesting the BS2 to prepare resources for the handover of the UE from a cell of the BS1 (e.g., source cell) to a cell of the BS2 (e.g., target cell).
  • the handover request 2203 may comprise information required for the BS2 to perform admission control for the UE.
  • the handover request 2203 may comprise a list of E-UTRA radio access bearers (E-RABs) requested to be added for the UE (e.g., E-RABs to be setup list).
  • the list of E-RABs requested to be added for the UE may comprise E- RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the BS2 may use the list of E-RABs requested to be added for the UE to perform admission control for the UE.
  • the handover request 2203 may comprise a list of protocol data unit (PDU) sessions requested to be added for the UE (e.g., PDU session resources to be setup list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU session configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the BS2 may use the list of PDU sessions requested to be added for the UE to perform admission control for the UE.
  • the BS2 may perform admission control 2204 for the UE based on the information received from the BS1 in the handover request 2203.
  • the BS2 may prepare resources for the UE.
  • the BS2 may send to the BS1, a handover request acknowledge 2205.
  • the handover request acknowledge 2205 may comprise configuration parameters for the UE to connect to the cell of the BS2.
  • the handover request acknowledge 2205 may comprise a list of admitted E-RABs for the UE (e.g , E-RABs admitted list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the handover request acknowledge 2205 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the handover request acknowledge 2205 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the handover request acknowledge 2205 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the UE, BS1 , and BS2 perform RAN handover completion 2206.
  • the BS2 and the AMF perform path switch 2207.
  • the path switch 2207 comprises switching user data from the BS1 to the BS2.
  • the BS2 sends to the BS1, a UE context release 2208. After the BS1 receives the UE context release 2208, the BS1 is no longer required to keep the UE context.
  • FIG. 23 illustrates an example of a conditional handover in a radio access network.
  • the BS1 and the UE perform measurement control and reports 2301.
  • the BS1 sends to the U E, one or more messages comprising one or more configuration parameters for the UE measurements procedures.
  • the UE sends to the BS1, one or more messages comprising measurement results determined based on the configuration parameters.
  • the BS1 determines a conditional handover decision 2302 for the UE based on the measurement results received from the UE (e.g., MeasurementReporfj and/or radio resource management (RRM) information.
  • the conditional handover decision comprises determining one or more candidate cells of the one or more candidate BSs.
  • the one or more candidate cells of the one or more candidate BSs comprise a first cell of the BS2 and a second cell of the BS3.
  • the BS1 send to the BS2, a handover request 2303.
  • the handover request 2303 comprises information required for the BS2 to perform admission control for the UE.
  • the handover request 2303 may comprise a list of E-RABs requested to be added for the UE (e.g., E-RABs to be setup list).
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the BS2 may use the list of E-RABs requested to be added for the UE to perform admission control for the UE.
  • the handover request acknowledge 2308 may comprise a list of admitted E-RABs for the UE (e.g , E-RABs admitted list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the handover request acknowledge 2308 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the handover request acknowledge 2308 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the handover request acknowledge 2308 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the BS1 sends to the UE, an RRCReconfiguration 2309.
  • the RRCReconfiguration 2309 comprises configuration parameters for the UE to connect to the first cell of the BS2 or to the second cell of the BS3.
  • the RRCReconfiguration 2309 comprises conditional handover execution conditions for the first cell of the BS2 and to the second cell of the BS3.
  • the UE sends to the BS1 , an RRCReconfigurationCompiete 2310.
  • the UE evaluates the conditional handover execution conditions for the first cell of the BS2 and to the second cell of the BS3. If the first cell of the BS2 satisfies the conditional handover execution conditions, the UE makes handover decision 2311 to the first cell of the BS2.
  • the BS1 sends to the BS3, a handover cancel 2314. After receiving the handover cancel 2314, the BS3 may release the resources reserved for the UE.
  • the BS2 and the AMF perform path switch 2315.
  • the path switch 2315 comprises switching user data from the BS1 to the BS2.
  • Multi-radio dual connectivity is a dual connectivity (DC), where a UE capable of receiving signals from multiple BSs and/or transmitting signals to multiple BSs may be configured to use resources provided by two different BSs, one providing NR access and the other one providing either E-UTRA or NR access.
  • One node acts as the master node (MN) and the other as the secondary node (SN).
  • MN and SN are connected via a network interface and at least the MN is connected to the core network.
  • the core network may be EPC or 5GC.
  • MR-DC may be supported via NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), in which a UE is connected to one eNB that acts as a MN and one gNB that acts as a SN.
  • eNB may be call ng-eNB.
  • MR-DC may be supported via NR-E-UTRA dual connectivity (NE-DC), in which a UE is connected to one gNB that acts as a MN and one eNB that acts as a SN.
  • NE-DC NR-E-UTRA dual connectivity
  • a UE is connected to one gNB that acts as a MN and one eNB that acts as a SN.
  • eNB may be call ng-eNB.
  • MR-DC may be supported via NR-NR dual connectivity (NR-DC), in which a UE is connected to one gNB that acts as a MN and another gNB that acts as a SN.
  • NR-DC NR-NR dual connectivity
  • a cell of a SN to which a UE performs initial access in the SN is called primary secondary cell (PSCell). If, in addition to PSCell, the UE uses one or more cells of the SN for carrier aggregation, these cells are called secondary cells (SCell).
  • SCell secondary cells
  • the PSCell and SCell(s) of the SN form a secondary cell group (SCG).
  • FIG. 24 illustrates an example of a secondary node addition procedure for EN-DC.
  • a secondary node addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE.
  • the MN may send to the SN, SgNB addition request message 2401 requesting the SN to allocate resources for the UE.
  • the SgNB addition request message 2401 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SgNB addition request message 2401 may comprise the latest measurement results for SN cells.
  • the SN may use the measurement results to select and configure the SCG cell(s).
  • the SgNB addition request message 2401 may comprise a list of E-RABs requested to be added for the UE (e g., E-RABs to be added list)
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the SN may use the list of E-RABs requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the SN may perform admission control, resource reservation, and may select a PSCell for the UE.
  • the SN may also select one or more SCells for the UE.
  • the SN may send to the MN, SgNB addition request acknowledge message 2402.
  • the SgNB addition request acknowledge message 2402 may comprise the new SCG radio resource configuration in a NR RRC configuration parameter.
  • the SgNB addition request acknowledge message 2402 may comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted to be added list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the SgNB addition request acknowledge message 2402 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the MN may send to the UE, RRCConnection Reconfiguration message 2403.
  • RRCConnection Reconfiguration message 2403 may comprise the NR RRC configuration message.
  • the UE may perform a reconfiguration procedure according to the received NR RRC configuration.
  • the UE may send to the MN, RRCConnection ReconfigurationComplete message 2404 confirming that the UE has performed the reconfiguration procedure according to the received NR RRC configuration.
  • the MN may send to the SN, SgNB reconfiguration complete message 2405, informing the SN that the UE has completed the reconfiguration procedure successfully.
  • the SN may trigger random access procedure 2406 with the UE to perform the UE synchronization with the allocated SN resources.
  • FIG. 25 illustrates an example of a secondary node addition procedure for MR-DC with 5GC.
  • a secondary node addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE.
  • the MN may send to the SN, SN addition request message 2501 requesting the SN to allocate resources for the UE.
  • the SN addition request message 2501 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SN addition request message 2501 may comprise the latest measurement results for SN cells. The SN may use the measurement results to select and configure the SCG cell(s).
  • the SN addition request message 2501 may comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be added list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU sessions configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the SN may use the list of PDU sessions requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the SN may perform admission control, resource reservation, and may select a PSCell for the UE.
  • the SN may also select one or more SCells for the UE.
  • the SN may send to the MN, SN addition request acknowledge message 2502.
  • the SN addition request acknowledge message 2502 may comprise the new SCG radio resource configuration in a RRC configuration parameter.
  • the SN addition request acknowledge message 2502 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted to be added list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the SN addition request acknowledge message 2502 may comprise a list of not admitted PDU sessions for the UE (e.g . , PDU session resources not admitted list).
  • the MN may send to the UE, RRC reconfiguration message 2503.
  • the RRC reconfiguration message 2503 may comprise the RRC configuration.
  • the UE may perform a reconfiguration procedure according to the received RRC configuration.
  • the UE may send to the MN, RRC reconfiguration complete message 2504 confirming that the UE has performed the reconfiguration procedure according to the received RRC configuration.
  • the MN may send to the SN, SN reconfiguration complete message 2505, informing the SN that the UE has completed the reconfiguration procedure successfully.
  • the SN may trigger random access procedure 2506 with the UE to perform the UE synchronization with the allocated SN resources
  • FIG. 26 illustrates an example of a conditional secondary node addition procedure for EN-DC.
  • a conditional secondary node addition procedure may be used when there are more than one candidate secondary nodes for a UE.
  • the MN may send to the SN1, SgNB addition request message 2601 requesting the SN1 to allocate resources for the UE.
  • the SgNB addition request message 2601 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SgNB addition request message 2601 may comprise the latest measurement results for SN1 cells.
  • the SN1 may use the measurement results to select and configure the SCG cell(s).
  • the SgNB addition request message 2601 may comprise a list of E-RABs requested to be added for the UE (eg., E-RABs to be added list)
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the SN1 may use the list of E-RABs requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the MN may send to the SN2, SgNB addition request message 2602 requesting the SN2 to allocate resources for the UE.
  • the SgNB addition request message 2602 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SgNB addition request message 2602 may comprise the latest measurement results for SN2 cells.
  • the SN2 may use the measurement results to select and configure the SCG cell(s).
  • the SgNB addition request message 2602 may comprise a list of E-RABs requested to be added for the UE (e.g., E-RABs to be added list).
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the SN2 may use the list of E-RABs requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the SN1 may perform admission control, resource reservation, and may select one or more candidate PSCells of the SN1 for the UE. The SN1 may also select one or more SCells of the SN1 for the UE.
  • the SN2 may perform admission control, resource reservation, and may select one or more candidate PSCells of the SN2 for the UE. The SN2 may also select one or more SCells of the SN2 for the UE.
  • the SN1 may send to the MN, SgNB addition request acknowledge message 2603.
  • the SgNB addition request acknowledge message 2603 may comprise the new SCG radio resource configuration of the SN1 in a NR RRC configuration parameter.
  • the SgNB addition request acknowledge message 2603 may comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted to be added list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the SgNB addition request acknowledge message 2603 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the SN2 may send to the MN, SgNB addition request acknowledge message 2604.
  • the SgNB addition request acknowledge message 2604 may comprise the new SCG radio resource configuration of the SN2 in a NR RRC configuration parameter.
  • the SgNB addition request acknowledge message 2604 may comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted to be added list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the SgNB addition request acknowledge message 2604 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the MN may send to the UE, RRCConnection Reconfiguration message 2605.
  • RRCConnection Reconfiguration message 2605 may comprise the NR RRC configuration message from the SN1 and the NR RRC configuration message from the SN2.
  • the UE may send to the MN, RRCConnectionReconfigurationComplete message 2606 confirming that the UE is able to perform the reconfiguration procedure according to the received NR RRC configuration from the SN1 and according to the received NR RRC configuration from the SN2.
  • the UE may perform evaluation of execution conditions (e.g., conditions for SN addition) according to the received NR RRC configuration from the SN1 and according to the received NR RRC configuration from the SN2. For example, the execution conditions for at least one PSCell of the SN1 are met.
  • the UE may perform a reconfiguration procedure according to the received RRC configuration from the SN1.
  • the UE may send to the MN, RRCConnectionReconfigurationComplete message 2607 indicating that the UE has performed the reconfiguration procedure according to the received RRC configuration from the SN1.
  • the MN may send to the SN1, SgNB reconfiguration complete message 2608, informing the SN that the UE has completed the reconfiguration procedure successfully.
  • the MN may send to the SN2, SgNB release request message 2609, to cancel the conditional secondary node addition with the SN2.
  • the SN2 may send to the MN, SgNB release request message 2610 to confirm the cancellation.
  • the SN may trigger random access procedure 2611 with the UE to perform the UE synchronization with the allocated SN resources.
  • FIG. 27 illustrates an example of a conditional secondary node addition procedure for MR-DC with 5GC.
  • a conditional secondary node addition procedure may be used when there are more than one candidate secondary nodes for a UE.
  • the MN may send to the SN1, SN addition request message 2701 requesting the SN1 to allocate resources for the UE.
  • the SN addition request message 2701 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SN addition request message 2701 may comprise the latest measurement results for SN1 cells.
  • the SN1 may use the measurement results to select and configure the SCG cell(s).
  • the SN addition request message 2701 may comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be added list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU sessions configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the SN1 may use the list of PDU sessions requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the MN may send to the SN2, SN addition request message 2702 requesting the SN2 to allocate resources for the UE.
  • the SN addition request message 2702 may comprise the requested SCG configuration information, including the UE capabilities.
  • the SgNB addition request message 2702 may comprise the latest measurement results for SN2 cells.
  • the SN2 may use the measurement results to select and configure the SCG cell(s).
  • the SN addition request message 2702 may comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be added list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU sessions configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the SN2 may use the list of PDU sessions requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the SN1 may perform admission control, resource reservation, and may select one or more candidate PSCells of the SN1 for the UE.
  • the SN1 may also select one or more SCells of the SN1 for the UE.
  • the SN2 may perform admission control, resource reservation, and may select one or more candidate PSCells of the SN2 for the UE.
  • the SN2 may also select one or more SCells of the SN2 for the UE.
  • the SN1 may send to the MN, SN addition request acknowledge message 2703.
  • the SN addition request acknowledge message 2703 may comprise the new SCG radio resource configuration of the SN1 in a RRC configuration parameter.
  • the SN addition request acknowledge message 2703 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted to be added list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the SN addition request acknowledge message 2703 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the SN2 may send to the MN, SN addition request acknowledge message 2704.
  • the SN addition request acknowledge message 2704 may comprise the new SCG radio resource configuration of the SN2 in a RRC configuration parameter.
  • the SN addition request acknowledge message 2704 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted to be added list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the SN addition request acknowledge message 2704 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the MN may send to the SN2, SN release request message 2709, to cancel the conditional secondary node addition with the SN2.
  • the SN2 may send to the MN, SN release request message 2710 to confirm the cancellation.
  • the SN may trigger random access procedure 2711 with the UE to perform the UE synchronization with the allocated SN resources.
  • FIG. 28 illustrates an example of a secondary node initiated secondary node change procedure for EN-DC.
  • a secondary node change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another.
  • the source SN may send to the MN, SgNB change required message 2801.
  • the SgNB change required message 2801 may comprise target SN (T-SN) identifier.
  • the SgNB change required message 2801 may comprise the requested SCG configuration information.
  • the SgNB change required message 2801 may comprise the latest measurement results for T-SN cells.
  • the T-SN may use the measurement results to select and configure the
  • the MN may send to the T-SN, SgNB addition request message 2802 requesting the SN to allocate resources for the UE.
  • the SgNB addition request message 2802 may comprise the requested SCG configuration information.
  • the SgNB addition request message 2802 may comprise the latest measurement results for T-SN cells.
  • the T-SN may use the measurement results to select and configure the SCG cell(s).
  • the SgNB addition request message 2802 may comprise a list of E-RABs requested to be added for the UE (e.g., E-RABs to be added list).
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the SN may use the list of E-RABs requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the T-SN may perform admission control, resource reservation, and may select a PSCell for the UE.
  • the T-SN may also select one or more SCells for the UE.
  • the T-SN may send to the MN, SgNB addition request acknowledge message 2803.
  • the SgNB addition request acknowledge message 2803 may comprise the new SCG radio resource configuration in a NR RRC configuration parameter.
  • the SgNB addition request acknowledge message 2803 may comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted to be added list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the SgNB addition request acknowledge message 2803 may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the MN may send to the UE, RRCConnection Reconfiguration message 2804.
  • RRCConnection Reconfiguration message 2804 may comprise the NR RRC configuration message.
  • the UE may perform a reconfiguration procedure according to the received NR RRC configuration.
  • the UE may send to the MN, RRCConnectionReconfigurationComplete message 2805 confirming that the UE has performed the reconfiguration procedure according to the received NR RRC configuration.
  • the MN may send to the S-SN, SgNB change confirm message 2806, informing the S-SN that the resources allocated for the UE may be released.
  • the MN may send to the T-SN, SgNB reconfiguration complete message 2807, informing the T-SN that the UE has completed the reconfiguration procedure successfully.
  • the T-SN may trigger random access procedure 2808 with the UE to perform the UE synchronization with the allocated T-SN resources.
  • FIG. 29 illustrates an example of a secondary node initiated secondary node change procedure for MR-DC with 5GC.
  • a secondary node change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another.
  • the source SN may send to the MN, SN change required message 2901.
  • the SN change required message 2901 may comprise target SN (T-SN) identifier.
  • the SN change required message 2901 may comprise the requested SCG configuration information.
  • the SN change required message 2901 may comprise the latest measurement results for T-SN cells.
  • the T-SN may use the measurement results to select and configure the SCG cell(s).
  • the MN may send to the T-SN, SN addition request message 2902 requesting the SN to allocate resources for the UE.
  • the SN addition request message 2902 may comprise the requested SCG configuration information.
  • the SN addition request message 2902 may comprise the latest measurement results for T-SN cells.
  • the T-SN may use the measurement results to select and configure the SCG cell(s).
  • the SN addition request message 2902 may comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be added list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU sessions configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the SN may use the list of PDU sessions requested to be added for the UE to perform admission control and resource reservation for the UE.
  • the T-SN may perform admission control, resource reservation, and may select a PSCell for the UE.
  • the T-SN may also select one or more SCells for the UE.
  • the SN addition request acknowledge message 2903 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted to be added list)
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the SN addition request acknowledge message 2903 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the list of E-RABs requested to be added for the UE and/or the list of E-RABs requested to be modified for the UE and/or the list of E-RABs requested to be released for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the SN may use the list of E-RABs requested to be added for the UE and/or the list of E-RABs requested to be modified for the UE and/or the list of E-RABs requested to be released for the UE to perform admission control for the UE.
  • FIG. 31 illustrates an example of a master node initiated secondary node modification procedure for MR-DC with 5GC.
  • the source node may send to the target node, the handover request message 3201.
  • the handover request message 3201 may comprise a request to the target node to prepare resources for the handover of a UE from a cell of the source node (e.g., source cell) to a cell of the target node (e.g., target cell).
  • the handover request message 3201 may comprise information required for the target node to perform admission control for the UE.
  • the source node may comprise, for example, a source NG-RAN node.
  • the target node may comprise, for example, a target NG-RAN node.
  • the handover request acknowledge message 3202 may comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted list).
  • the list of admitted PDU sessions for the UE may comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the handover request acknowledge message 3202 may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • FIG. 35 illustrates an example of a SgNB change procedure for EN-DC.
  • the SgNB change procedure for EN-DC may be used as part of the SN initiated SN change procedure for EN- DC.
  • the SgNB change procedure for EN-DC may be used as part of the SN initiated conditional SN change procedure for EN-DC.
  • the S-NG-RAN node may send to the M-NG-RAN node, S-Node change required message 3601.
  • the S- Node change required message 3601 may comprise target SN (T-SN) identifier.
  • the S-Node change required message 3601 may comprise the requested SCG configuration information.
  • the S-Node change required message 3601 may comprise the latest measurement results for T-SN cells.
  • the T-SN may use the measurement results to select and configure the SCG cell(s).
  • the S-NG-RAN node change procedure for MR-DC with 5GC may be used as part of the SN initiated SN change procedure for MR-DC with 5GC.
  • the S-NG-RAN node change procedure for MR-DC with 5GC may be used as part of the SN initiated conditional SN change procedure for MR-DC with 5GC.
  • the MN may send to the SN, SN addition request message 3701 requesting the SN to allocate resources for the UE.
  • the SN node may send to the MN node, S-Node addition request acknowledge message 3702.
  • the S-Node addition request acknowledge message 3702 may comprise the new SCG radio resource configuration in a RRC configuration parameter.
  • Such exchange of S-Node addition request and S-Node addition request acknowledge messages between the MN and the SN may continue until the MN and the SN converge to an acceptable configuration of admitted PDU sessions for the UE in the SN.
  • resources in SN may be reserved and released without actually being used by any UE.
  • this procedure may involve extensive signaling between the MN and the SN (e.g., PDU sessions configuration and/or QoS flows configuration and/or UE RRC configuration and/or measurement results may be quite large messages).
  • this procedure consumes resources at the MN and/or at the SN, for example, for selecting PDU sessions to be requested to be added for the UE in the MN and/or for reserving and releasing resources in the SN.
  • Similar problems may exist in procedures using, for example, a handover preparation procedure and/or an SgNB addition preparation procedure and/or an S-NG-RAN node addition preparation procedure and/or an MeNB initiated SgNB modification preparation procedure and/or an M-NG-RAN node initiated S-NG-RAN node modification preparation procedure.
  • a BS2 may send to a BS1 a handover request message for a UE.
  • the BS1 may perform an admission control for the UE to a cell of the BS1.
  • the BS1 may perform the admission control for the UE, for example, based on the current available capacity in the cell and/or based on the QoS requirements of the wireless device. For example, the BS1 may determine not to admit the UE because the available capacity is not enough to satisfy the QoS requirements of the wireless device.
  • the BS1 may send to the BS2, a handover preparation failure message indicating to the BS2 that the BS1 does not admit the UE.
  • a first base station may receive from a second base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the first base station may send to the second base station, one or more second messages.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • a second base station may send to a first base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the second base station may receive from the first base station, one or more second messages comprising the prediction of admitted PDU sessions for the wireless device.
  • a first base station may receive from a second base station, one or more first messages requesting a prediction of not admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the first base station may send to the second base station, one or more second messages.
  • the one or more second messages may comprise the prediction of not admitted PDU sessions for the wireless device.
  • a second base station may send to a first base station, one or more first messages requesting a prediction of not admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the second base station may receive from the first base station, one or more second messages.
  • the one or more second messages may comprise the prediction of not admitted PDU sessions for the wireless device.
  • a first base station may receive from a second base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the first base station may send to the second base station, one or more third messages.
  • the one or more third messages may comprise an indication that the first base station will provide the prediction of admitted PDU sessions for the wireless device.
  • the first base station may send to the second base station, one or more second messages.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • a second base station may send to a first base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the second base station may receive from the first base station, one or more third messages.
  • the one or more third messages may comprise an indication that the first base station will provide the prediction of admitted PDU sessions for the wireless device.
  • the second base station may receive from the first base station, one or more second messages.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • a first base station may receive from a second base station, one or more first messages requesting a prediction of not admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the first base station may send to the second base station, one or more third messages.
  • the one or more third messages may comprise an indication that the first base station will provide the prediction of not admitted PDU sessions for the wireless device.
  • the first base station may send to the second base station, one or more second messages.
  • the one or more second messages may comprise the prediction of not admitted PDU sessions for the wireless device.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • the one or more second messages may comprise the prediction of not admitted PDU sessions for the wireless device.
  • the one or more second messages may comprise the prediction that all of the PDU sessions for the wireless device are admitted.
  • the one or more second messages may comprise the prediction that none of the PDU sessions for the wireless device are admitted.
  • the one or more third messages may comprise an indication that the first base station will provide the prediction of admitted PDU sessions for the wireless device.
  • the one or more third messages may comprise an indication that the first base station will provide the prediction of not admitted PDU sessions for the wireless device.
  • a first base station may receive from a second base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the first base station may determine the prediction of admitted PDU sessions for the wireless device.
  • the first base station may send to the second base station, one or more second messages.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • a second base station may send to a first base station, one or more first messages requesting a prediction of admitted PDU sessions for a wireless device.
  • the one or more first messages may indicate PDU sessions requested to be added for the wireless device.
  • the second base station may receive from the first base station, one or more second messages.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the wireless device.
  • the second base station may determine, based on the prediction, whether to request the first base station to add PDU sessions for the wireless device.
  • the one or more first messages may further comprise an indication of time for which the prediction is requested.
  • the one or more first messages may further comprise a time schedule for the first base station to send to the second base station the prediction.
  • the one or more first messages may further comprise a time interval when the second base station may request the first base station to add PDU sessions for the wireless device.
  • the one or more first messages may further comprise a measurement of an amount of traffic of the wireless device.
  • the one or more first messages may further comprise a prediction of an amount of traffic of the wireless device.
  • the one or more first messages may further comprise a measurement of a signal quality by the wireless device.
  • the one or more first messages may further comprise a prediction of a signal quality for the wireless device.
  • the one or more second messages may comprise the prediction of the admitted and/or not admitted PDU sessions for the indication of time of the one or more first messages.
  • the first base station may send to the second base station, the one or more second messages according to the time schedule received in the one or more first messages.
  • the one or more second messages may further comprise a prediction of admitted QoS flows.
  • the one or more second messages may further comprise a prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the wireless device.
  • the one or more second messages may further comprise a prediction of not admitted QoS flows.
  • the one or more second messages may further comprise a prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the wireless device.
  • the one or more second messages may further comprise candidate serving cells of the first base station for the wireless device.
  • the prediction of the admitted and/or not admitted PDU sessions may be per one or more candidate serving cells of the first base station for the wireless device.
  • the one or more second messages may further comprise an alternative QoS profile per PDU session.
  • the one or more second messages may further comprise an alternative QoS profile per QoS flow.
  • the one or more second messages may further comprise an alternative QoS profile per QoS flow per PDU session.
  • Example embodiments of the present disclosure implement an enhanced mechanism for the first base station to send to the second base station, a prediction of admitted PDU sessions for the wireless device. This may allow to reduce signaling between the first base station and the second base station. This may allow to reduce unnecessary resource reservation at the first base station. This may allow to reduce unnecessary processing and memory resources consumption at the first base station and at the second base station.
  • FIG. 38 illustrates an example embodiment of the present disclosure.
  • a BS1 may send to a BS2, one or more second messages 3801.
  • the one or more second messages 3801 may comprise a prediction of admitted PDU sessions for a UE.
  • a BS2 may receive from a BS1 , one or more second messages 3801.
  • the one or more second messages 3801 may comprise a prediction of admitted PDU sessions for a UE.
  • FIG. 39 illustrates an example embodiment of the present disclosure.
  • a BS1 may send to a BS2, one or more second messages 3901.
  • the one or more second messages 3901 may comprise a prediction of not admitted PDU sessions for a UE.
  • a BS2 may receive from a BS1 , one or more second messages 3901.
  • the one or more second messages 3901 may comprise a prediction of not admitted PDU sessions for a UE.
  • FIG. 40 illustrates an example embodiment of the present disclosure.
  • a BS1 may receive from a BS2, one or more first messages 4001 requesting a prediction of admitted PDU sessions for a UE.
  • the one or more first messages 4001 may indicate PDU sessions requested to be added for the UE.
  • the BS1 may send to the BS2, one or more second messages 4002.
  • the one or more second messages 4002 may comprise the prediction of admitted PDU sessions for the UE.
  • the one or more first messages 4001 may further comprise the UE identifier (e.g., BS2 UE XnAP identifier and/or BS2 UE X2AP identifier).
  • the UE identifier e.g., BS2 UE XnAP identifier and/or BS2 UE X2AP identifier.
  • the PDU sessions requested to be added for the UE may comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be added list).
  • An element of the list of PDU sessions requested to be added for the UE may comprise an information related to a PDU session requested to be added for the UE.
  • the element of the list of PDU sessions requested to be added for the UE may comprise an identifier of the PDU session.
  • the element of the list of PDU sessions requested to be added for the UE may comprise an S-NSSAI corresponding to the PDU session.
  • the element of the list of PDU sessions requested to be added for the UE may comprise an aggregate maximum bit rate of the PDU session in the BS1.
  • the element of the list of PDU sessions requested to be added for the UE may comprise a list of QoS flows requested to be added for the PDU session (e.g., QoS flows to be setup list)
  • An element of the list of QoS flows requested to be added for the PDU session may comprise an information related to a QoS flow requested to be added for the PDU session.
  • the element of the list of QoS flows requested to be added for the PDU session may comprise an identifier of the QoS flow.
  • the element of the list of QoS flows requested to be added for the PDU session may comprise QoS parameters of the QoS flow.
  • the PDU sessions requested to be added for the UE may also refer to E-RABs requested to be added for the UE.
  • the PDU sessions requested to be added for the UE may comprise a list of E-RABs requested to be added for the UE (e.g. , E-RABs to be added list).
  • An element of the list of PDU sessions requested to be added for the UE may comprise an information related to a E-RAB requested to be added for the UE.
  • the element of the list of PDU sessions requested to be added for the UE may comprise an identifier of the E-RAB.
  • the element of the list of PDU sessions requested to be added for the UE may comprise an identifier of a DRB corresponding to the E-RAB.
  • the element of the list of PDU sessions requested to be added for the UE may comprise QoS parameters corresponding to the E-RAB.
  • the one or more first messages 4001 may request the prediction of admitted PDU sessions for the UE.
  • the one or more first messages 4001 may request the prediction of admitted PDU sessions for the UE at one or more points and/or time intervals in future.
  • the one or more first messages 4001 may request the prediction of admitted PDU sessions for the UE 10 seconds after sending the one or more first messages 4001 and/or 15 seconds, 25 seconds, and 35 seconds after sending the one or more first messages 4001.
  • the one or more second messages 4002 may comprise the prediction of admitted PDU sessions for the UE.
  • the prediction of admitted PDU sessions for the UE is a prediction by the BS1 of which PDU sessions, out of the PDU sessions requested to be added for the UE, the BS1 may admit in future. For example, there may be five PDU sessions requested to be added for the UE. Out of five PDU sessions requested to be added for the UE, the BS1 may predict that in 15 seconds it may admit 3 PDU sessions, in 25 seconds it may admit 2 PDU sessions, and in 35 seconds it may admit 4 PDU sessions (time may be counted, for example, from the time the BS1 receives the one or more first messages 4001).
  • the prediction of admitted PDU sessions for the UE may comprise a list of identifiers of the PDU sessions predicted to be admitted.
  • the prediction of admitted PDU sessions for the UE may comprise a bitmap, where each bit corresponds to a PDU session requested to be added for the wireless device, and a value of bit indicates whether the PDU sessions is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of not admitted PDU sessions for the UE may comprise an indication that all of the PDU sessions are predicted to be admitted.
  • the prediction of not admitted PDU sessions for the UE may comprise an indication that all of the PDU sessions are predicted to be not admitted.
  • a BS2 may send to a BS1 , one or more first messages
  • the one or more first messages 4001 may indicate PDU sessions requested to be added for the UE.
  • the BS2 may receive from the BS1 , one or more second messages
  • FIG. 41 illustrates an example embodiment of the present disclosure.
  • a BS1 may receive from a BS2, one or more first messages 4101 requesting a prediction of not admitted PDU sessions fora UE.
  • the one or more first messages 4101 may indicate PDU sessions requested to be added for the UE
  • the BS1 may send to the BS2, one or more second messages 4102.
  • the one or more second messages 4102 may comprise the prediction of not admitted PDU sessions for the UE.
  • the one or more second messages 4102 may comprise the prediction of not admitted PDU sessions for the UE.
  • the prediction of not admitted PDU sessions for the UE is a prediction by the BS1 of which PDU sessions, out of the PDU sessions requested to be added for the UE, the BS1 may not admit in future. For example, there may be five PDU sessions requested to be added for the UE.
  • the BS1 may predict that in 15 seconds it may not admit 2 PDU sessions, in 25 seconds it may not admit 3 PDU sessions, and in 35 seconds it may not admit 1 PDU sessions (time may be counted, for example, from the time the BS1 receives the one or more first messages 4101).
  • the prediction of not admitted PDU sessions for the UE may comprise a list of identifiers of the PDU sessions predicted to be not admitted.
  • the prediction of not admitted PDU sessions for the UE may comprise a bitmap, where each bit corresponds to a PDU session requested to be added for the wireless device, and a value of bit indicates whether the PDU sessions is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of not admitted PDU sessions for the UE may comprise an indication that all of the PDU sessions are predicted to be admitted.
  • the prediction of not admitted PDU sessions for the UE may comprise an indication that all of the PDU sessions are predicted to be not admitted.
  • a BS2 may send to a BS1 , one or more first messages 4101 requesting a prediction of not admitted PDU sessions for a UE.
  • the one or more first messages 4101 may indicate PDU sessions requested to be added for the UE.
  • the BS2 may receive from the BS1, one or more second messages 4102.
  • the one or more second messages 4102 may comprise the prediction of not admitted PDU sessions for the UE.
  • FIG. 42 illustrates an example embodiment of the present disclosure.
  • a BS1 may receive from a BS2, one or more first messages 4201 requesting a prediction of admitted PDU sessions for a UE.
  • the one or more first messages 4201 may indicate PDU sessions requested to be added for the UE.
  • the BS1 may send to the BS2, one or more third messages 4202.
  • the one or more third messages 4202 may comprise an indication that the BS1 will provide the prediction of admitted PDU sessions for the UE.
  • the BS1 may send to the BS2, one or more second messages 4203.
  • the one or more second messages 4203 may comprise the prediction of admitted PDU sessions for the UE.
  • the one or more third messages 4202 may comprise the indication that the BS1 will provide the prediction of admitted PDU sessions for the UE.
  • the indication may indicate whether the BS1 will provide the requested prediction of admitted PDU sessions for the UE.
  • the indication may be a parameter, where “1” or “true” or “will provide” or “yes,” etc. may indicate that the BS1 will provide the requested prediction of admitted PDU sessions for the U E .
  • the indication may be a parameter, where “0” or “false” or “will not provide,” etc. may indicate that the BS1 will not provide the requested prediction of admitted PDU sessions for the UE.
  • the indication may be a position in a bitmap indicating whether the BS1 will provide the requested prediction of admitted PDU sessions for the UE (e.g . , the parameter indicating which predictions will be provided may be a failed reporting characteristics parameter).
  • a BS2 may send to a BS1 , one or more first messages 4201 requesting a prediction of admitted PDU sessions for a UE.
  • the one or more first messages 4201 may indicate PDU sessions requested to be added for the UE.
  • the BS2 may receive from the BS1 , one or more third messages 4202.
  • the one or more third messages 4202 may comprise an indication that the BS1 will provide the prediction of admitted PDU sessions for the UE.
  • the BS2 may receive from the BS1 , one or more second messages 4203.
  • the one or more second messages 4203 may comprise the prediction of admitted PDU sessions for the UE.
  • FIG. 43 illustrates an example embodiment of the present disclosure.
  • a BS1 may receive from a BS2, one or more first messages 4301 requesting a prediction of not admitted PDU sessions for a UE.
  • the one or more first messages 4301 may indicate PDU sessions requested to be added for the UE.
  • the BS1 may send to the BS2, one or more third messages 4302.
  • the one or more third messages 4302 may comprise an indication that the BS1 will provide the prediction of not admitted PDU sessions for the UE.
  • the BS1 may send to the BS2, one or more second messages 4303.
  • the one or more second messages 4303 may comprise the prediction of not admitted PDU sessions for the UE.
  • the one or more third messages 4302 may comprise the indication that the BS1 will provide the prediction of not admitted PDU sessions for the UE.
  • the indication may indicate whether the BS1 will provide the requested prediction of not admitted PDU sessions for the UE.
  • the indication may be a parameter, where “1” or “true” or “will provide” or “yes,” etc. may indicate that the BS1 will provide the requested prediction of not admitted PDU sessions for the UE.
  • the indication may be a parameter, where “0” or “false” or “will not provide,” etc. may indicate that the BS1 will not provide the requested prediction of not admitted PDU sessions for the UE.
  • the indication may be a position in a bitmap indicating whether the BS1 will provide the requested prediction of not admitted PDU sessions for the UE (e.g., e.g., the parameter indicating which predictions will be provided may be a failed reporting characteristics parameter).
  • a BS2 may send to a BS1 , one or more first messages 4301 requesting a prediction of not admitted PDU sessions for a UE.
  • the one or more first messages 4301 may indicate PDU sessions requested to be added for the UE.
  • the BS2 may receive from the BS1, one or more third messages 4302.
  • the one or more third messages 4302 may comprise an indication that the BS1 will provide the prediction of not admitted PDU sessions for the UE.
  • the BS2 may receive from the BS1, one or more second messages 4303.
  • the one or more second messages 4303 may comprise the prediction of not admitted PDU sessions for the UE.
  • the one or more first messages may request a prediction of admitted PDU sessions for a UE.
  • the one or more first messages may request a prediction of not admitted PDU sessions for a UE.
  • the one or more second messages may comprise the prediction of admitted PDU sessions for the UE.
  • the one or more second messages may comprise the prediction of not admitted PDU sessions for the UE.
  • the one or more second messages may comprise the prediction that all of the PDU sessions for the UE are admitted.
  • the one or more second messages may comprise the prediction that none of the PDU sessions for the UE are admitted.
  • the one or more third messages may comprise an indication that the BS1 will provide the prediction of admitted PDU sessions for the UE.
  • the one or more third messages may comprise an indication that the BS1 will provide the prediction of not admitted PDU sessions for the UE.
  • FIG. 44 illustrates an example embodiment of the present disclosure.
  • a BS1 may receive from a BS2, one or more first messages 4401 requesting a prediction of admitted PDU sessions for a UE.
  • the one or more first messages 4401 may indicate PDU sessions requested to be added for the UE.
  • the BS1 may determine the prediction of admitted PDU sessions for the UE.
  • the BS1 may send to the BS2, one or more second messages 4402.
  • the one or more second messages 4402 may comprise the prediction of admitted PDU sessions for the UE.
  • the BS1 may determine the prediction of admitted PDU sessions for the UE.
  • the BS1 may determine the prediction of admitted PDU sessions for the UE, for example, using an Al model and/or an ML model and/or an AI/ML model and/or any other suitable means.
  • the BS1 may use information from the BS2 (e.g., information about PDU sessions requested to be added for the UE) as an input for an AI/ML model training and/or inference.
  • the BS1 may use internal information (e.g., current load, e.g., load per cell and/or load per slice etc.) as an input for an AI/ML model training and/or inference.
  • the BS1 may use information about QoS performance of UEs served by the BS1 as an input for an AI/ML model training and/or inference.
  • the BS1 may use any other suitable measurements and/or predictions as an input for an AI/ML model training and/or inference.
  • the BS1 may use deep learning models and/or algorithms, supervised learning models and/or algorithms, unsupervised learning models and/or algorithms and/or any other suitable algorithms.
  • a BS2 may send to a BS1 , one or more first messages 4401 requesting a prediction of admitted PDU sessions for a UE.
  • the one or more first messages 4401 may indicate PDU sessions requested to be added for the UE.
  • the BS2 may receive from the BS1 , one or more second messages 4402.
  • the one or more second messages 4402 may comprise the prediction of admitted PDU sessions for the UE.
  • the BS2 may determine, based on the prediction, whether to request the BS1 to add PDU sessions for the UE.
  • the BS2 may determine, based on the prediction, whether to request the BS1 to add PDU sessions for the UE.
  • the BS2 may request the BS1 to add 8 PDU sessions for a UE
  • the BS1 may predict that it will admit 7 out of 8 PDU sessions for the UE.
  • the one PDU session that is predicted to be not admitted may have a low priority (e.g., from the UE applications point of view).
  • the BS2 may determine to request the BS1 to add 7 out of 8 PDU sessions for the UE (the 7 PDU sessions that are predicted to be admitted).
  • the BS2 may request the BS1 to add 6 PDU sessions for a UE.
  • the BS1 may predict that it will admit only 1 out of 6 PDU sessions for the UE.
  • another BS5 may predict that it will admit 5 out of 6 PDU sessions for the UE.
  • the BS2 may determine not to request the BS1 to add PDU sessions for the UE (e.g., the BS2 may request the BS5 to add PDU sessions for the UE).
  • the one or more first messages may further comprise an indication of time for which the prediction is requested.
  • the one or more first messages may further comprise a time schedule for the BS1 to send to the BS2 the prediction.
  • the one or more first messages may further comprise a time interval when the BS2 may request the BS1 to add PDU sessions for the UE.
  • the indication of time for which the prediction is requested may comprise one or more points in time.
  • a point in time may comprise an absolute time as measured by the International Atomic Time (TAI).
  • TAI International Atomic Time
  • the point in time may be equal to, for example, 2023-02-08 T04:23: 13 and/or 2023-03- 09 T11 :33:33.
  • the point in time may comprise a time offset between an absolute time reference and an absolute time as measured by the TAI.
  • the absolute time reference may be selected to be equal to, for example, 1980-01-06 T00:00:19 as measured by the TAI.
  • the offset may be equal to, for example, 0043-00-00 T00:00:00 and/or 0043-01 -00 T09:24:10.
  • the indication of time for which the prediction is requested may comprise a duration.
  • the duration maybe equal to, for example, 100 milliseconds (ms) and/or 1.2 seconds (s).
  • the indication of time for which the prediction is requested may comprise a start time and an end time.
  • the start time and/or the end time may comprise an absolute time as measured by TAI.
  • the start time and/or the end time may be equal to, for example, 2023-02-08 T04:23: 13 and/or 2023-03-09 T 11 :33: 33.
  • the start time and/or the end time may comprise a time offset between an absolute time reference and an absolute time as measured by the TAI.
  • the absolute time reference may be selected to be equal to, for example, 1980-01-06 TOO :00: 19 as measured by the TAI.
  • the offset may be equal to, for example, 0043-00-00 T00:00:00 and/or 0043-01-00 T09:24:10.
  • the indication of time for which the prediction is requested may comprise a start time and a duration.
  • the indication of time for which the prediction is requested may comprise a duration and an end time.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise one or more points in time.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a duration.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a start time and an end time.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a start time and a duration.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a duration and an end time.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a periodicity.
  • the periodicity may indicate a time interval between two consecutive time points when the BS1 sends to the BS2 the prediction.
  • the periodicity may be equal to, for example, 500 milliseconds (ms) and/or 1000 ms and/or 2000 ms etc.
  • the time schedule for the BS1 to send to the BS2 the prediction may comprise a time interval between sending two consecutive predictions.
  • the time interval may be equal to, for example, 500 milliseconds (ms) and/or 1000 ms and/or 2000 ms etc.
  • the time interval when the BS2 may request the BS1 to add PDU sessions for the UE may comprise one or more points in time.
  • the time interval when the BS2 may request the BS1 to add PDU sessions for the UE may comprise a duration.
  • the time interval when the BS2 may request the BS1 to add PDU sessions for the UE may comprise a start time and an end time.
  • the time interval when the BS2 may request the BS1 to add PDU sessions for the UE may comprise a start time and a duration.
  • the time interval when the BS2 may request the BS1 to add PDU sessions for the UE may comprise a duration and an end time.
  • the one or more first messages may further comprise a measurement of an amount of traffic of the UE.
  • the one or more first messages may further comprise a prediction of an amount of traffic of the UE.
  • the measurement of the amount of traffic of the UE may comprise one or more previous (e.g., the most recent) measurements of the amount of traffic of the UE.
  • the prediction of the amount of traffic of the UE may comprise one or more future predictions (e.g., determined by the BS2 using, e.g., AI/ML model) of the amount of traffic of the UE.
  • the amount of traffic of the UE may comprise a data rate (e.g., 23 Mb/s and/or 12 Mb/s).
  • the amount of traffic of the UE may comprise a throughput (e.g., 4 Mb/s and/or 8 Mb/s).
  • the amount of traffic of the UE may comprise an amount of downlink traffic of the UE.
  • the amount of traffic of the UE may comprise an amount of uplink traffic of the UE.
  • the amount of traffic of the UE may comprise an amount of GBR traffic of the UE.
  • the amount of traffic of the UE may comprise an amount of non-GBR traffic of the UE.
  • the amount of traffic of the UE may comprise the amount of traffic of the UE per the UE.
  • the amount of traffic of the UE may comprise the amount of traffic of the UE per one or more PDU sessions of the UE.
  • the amount of traffic of the UE may comprise the amount of traffic of the UE per one or more QoS flows of the UE.
  • the amount of traffic of the UE may comprise the amount of traffic of the UE per one or more slices of the UE.
  • the amount of traffic of the UE may comprise the amount of traffic of the UE per one or more 5Qls of the UE.
  • the one or more first messages may further comprise a measurement of a signal quality by the UE.
  • the one or more first messages may further comprise a prediction of a signal quality for the UE.
  • the measurement of the signal quality by the UE may comprise one or more previous (e.g., the most recent) measurements of the signal quality by the UE.
  • the prediction of the signal quality for the UE may comprise one or more future predictions (e.g., determined by the BS2 using, e.g., AI/ML model) of the signal quality for the UE.
  • the signal quality may comprise a signal level (e.g., reference signal received power (RSRP)).
  • the signal quality may comprise a signal quality (e.g., reference signal received quality (RSRQ)).
  • the signal quality may comprise a signal to interference plus noise ratio (SINR).
  • the signal quality may comprise the signal quality in one or more cells.
  • the one or more cells may comprise one or more serving cells of the UE.
  • the one or more cells may comprise one or more candidate serving cells of the UE.
  • the one or more cells may comprise one or more neighbor cells of the UE.
  • the one or more cells may comprise one or more cells requested to be measured by the UE by the BS2.
  • the one or more second messages may comprise the prediction of the admitted and/or not admitted PDU sessions for the indication of time of the one or more first messages.
  • the one or more first messages may comprise the indication of time for which the prediction is requested.
  • the indication of time for which the prediction is requested may comprise a start time and a duration.
  • the one or more second messages may comprise the prediction of the admitted and/or not admitted PDU sessions for the time interval between the start time and the start time plus duration.
  • the indication of time for which the prediction is requested may comprise a start time and an end time.
  • the one or more second messages may comprise the prediction of the admitted and/or not admitted PDU sessions for the time interval between the start time and the end time.
  • the BS1 may send to the BS2, the one or more second messages according to the time schedule received in the one or more first messages.
  • the one or more first messages may comprise the time schedule for the BS1 to send to the BS2 the prediction.
  • the time schedule may comprise a start time and an end time.
  • the BS1 may send to the BS2, the one or more second messages comprising the prediction of the admitted and/or not admitted PDU sessions between the start time and the end time.
  • the time schedule may comprise a periodicity.
  • the BS1 may send to the BS2, the one or more second messages comprising the prediction of the admitted and/or not admitted PDU sessions with the indicated periodicity (e.g. , every 500 ms and/or every 2000 ms etc.).
  • the one or more second messages may further comprise a prediction of admitted QoS flows.
  • the one or more second messages may further comprise a prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE.
  • the one or more second messages may further comprise a prediction of not admitted QoS flows.
  • the one or more second messages may further comprise a prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE.
  • the prediction of admitted QoS flows may comprise a list of identifiers of the QoS flows predicted to be admitted.
  • the prediction of admitted QoS flows may comprise a bitmap, where each bit corresponds to a QoS flow requested to be added for the UE, and a value of bit indicates whether the QoS flow is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of admitted QoS flows may comprise an indication that all of the QoS flows are predicted to be admitted.
  • the prediction of admitted QoS flows may comprise an indication that all of the QoS flows are predicted to be not admitted.
  • the prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise a list of identifiers of the QoS flows per PDU session of the PDU sessions requested to be added for the UE predicted to be admitted.
  • the prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise a bitmap, where each bit corresponds to a QoS flow per PDU session of the PDU sessions requested to be added for the UE, and a value of bit indicates whether the QoS flow is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise an indication that all of the QoS flows are predicted to be admitted.
  • the prediction of admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise an indication that all of the QoS flows are predicted to be not admitted.
  • the prediction of not admitted QoS flows may comprise a list of identifiers of the QoS flows predicted to be not admitted.
  • the prediction of not admitted QoS flows may comprise a bitmap, where each bit corresponds to a QoS flow requested to be added for the UE, and a value of bit indicates whether the QoS flow is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of not admitted QoS flows may comprise an indication that all of the QoS flows are predicted to be admitted.
  • the prediction of not admitted QoS flows may comprise an indication that all of the QoS flows are predicted to be not admitted.
  • the prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise a list of identifiers of the QoS flows per PDU session of the PDU sessions requested to be added for the UE predicted to be not admitted.
  • the prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise a bitmap, where each bit corresponds to a QoS flow per PDU session of the PDU sessions requested to be added for the UE, and a value of bit indicates whether the QoS flow is predicted to be admitted or not (e.g., “1” or “true” for admitted and “0” or “false” for not admitted or, for example, reverse).
  • the prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise an indication that all of the QoS flows are predicted to be admitted.
  • the prediction of not admitted QoS flows per PDU session of the PDU sessions requested to be added for the UE may comprise an indication that all of the QoS flows are predicted to be not admitted.
  • the one or more second messages may further comprise candidate serving cells of the BS1 for the UE.
  • the candidate serving cells of the BS1 for the UE may comprise a target cell.
  • the candidate serving cells of the BS1 for the UE may comprise one or more PSCells.
  • the candidate serving cells of the BS1 for the UE may comprise one or more SCells.
  • the candidate serving cells of the BS1 for the UE may comprise one or more combinations of one PSCell and zero or more corresponding SCells.
  • the prediction of the admitted and/or not admitted PDU sessions may be per one or more candidate serving cells of the BS1 for the UE.
  • the one or more candidate serving cells of the BS1 for the UE may comprise a target cell.
  • the one or more candidate serving cells of the BS1 for the UE may comprise a PSCell.
  • the one or more candidate serving cells of the BS1 for the UE may comprise a PSCell and zero or more corresponding SCells.
  • the prediction of the admitted and/or not admitted PDU sessions may be per target cell.
  • the predictions may be different.
  • the prediction of the admitted and/or not admitted PDU sessions may be per PSCell.
  • the predictions may be different.
  • the prediction of the admitted and/or not admitted PDU sessions may be per a group of one PSCell and zero or more SCells (a group of PSCell and SCells).
  • the predictions may be different for different groups of PSCell and SCells.
  • the one or more second messages may further comprise an alternative QoS profile per PDU session.
  • the one or more second messages may further comprise an alternative QoS profile per QoS flow.
  • the one or more second messages may further comprise an alternative QoS profile per QoS flow per PDU session.
  • a QoS flow may be able to adapt to different combinations of QoS parameters.
  • An alternative QoS profile may comprise a combination of QoS parameters that are acceptable for the QoS flow.
  • One QoS flow may have one or more alternative QoS profiles. For example, if the BS1 determines a prediction that it cannot admit a PDU session and/or a QoS flow with the requested QoS parameters, the BS1 may determine a prediction that it can admit the PDU session and/or the QoS flow with an alternative QoS profile.
  • the BS1 may include the alternative QoS profile for the PDU session and/or the QoS flow in the one or more second messages.
  • the BS1 may comprise a target eNB and/or a target NG- RAN node and/or a target MN and/or a target ng-eNB and/or a target g N B.
  • the BS2 may comprise a source eNB and/or a source NG-RAN node and/or a source MN and/or a source ng-eNB and/or a source gNB.
  • the one or more first messages may comprise a handover request message.
  • the one or more second messages may comprise a handover request acknowledge message.
  • the one or more first messages may further comprise a list of E-RABs requested to be added for the UE (e.g., E-RABs to be setup list).
  • the list of E-RABs requested to be added for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the one or more first messages may further comprise a message type.
  • the one or more first messages may further comprise a UE identifier in the source base station (e.g., old eNB UE X2AP ID).
  • the one or more first messages may comprise further a cause of the handover.
  • the one or more first messages may further comprise a target cell identifier.
  • the one or more first messages may further comprise a UE context information.
  • the one or more first messages may further comprise a UE RRC context.
  • the one or more first messages may further comprise a conditional handover information.
  • the one or more first messages may further comprise a list of PDU sessions requested to be added for the UE (e.g., PDU session resources to be setup list).
  • the list of PDU sessions requested to be added for the UE may comprise PDU session configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the one or more first messages may comprise a message type.
  • the one or more first messages may comprise a UE identifier in the source base station (e.g., source NG-RAN node UE XnAP ID reference).
  • the one or more first messages may further comprise a cause of the handover.
  • the one or more first messages may further comprise a target cell identifier.
  • the one or more first messages may further comprise a UE context information.
  • the one or more first messages may further comprise a UE RRC context.
  • the one or more first messages may further comprise a conditional handover information.
  • the one or more second messages may further comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted list).
  • the list of admitted E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the one or more second messages may comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the one or more second messages may further comprise a message type
  • the one or more second messages may further comprise a UE identifier in the source base station.
  • the one or more second messages may further comprise a UE identifier in the target base station (e.g., new eNB UE X2AP ID).
  • the one or more second messages may further comprise target base station to source base station transparent container.
  • the one or more second messages may further comprise a conditional handover information.
  • the one or more second messages may further comprise a list of admitted PDU sessions for the UE (e.g. , PDU session resources admitted list).
  • the one or more second messages may further comprise PDU sessions configuration, for example, PDU session identifier, QoS parameters etc.
  • the one or more second messages may comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted list).
  • the one or more second messages may further comprise a message type.
  • the one or more second messages may further comprise a UE identifier in the source base station.
  • the one or more second messages may further comprise a UE identifier in the target base station (e.g., target NG-RAN node UE XnAP ID).
  • the one or more second messages may further comprise target base station to source base station transparent container.
  • the one or more second messages may further comprise a conditional handover information.
  • the BS2 may comprise a master node (MN).
  • the BS2 may comprise a master eNB (MeNB).
  • the BS2 may comprise a master NG-RAN node (M-NG-RAN) node.
  • the BS1 may comprise a secondary node (MN).
  • the BS1 may comprise an en-gNB.
  • the BS1 may comprise a secondary NG- RAN node (S-NG-RAN) node.
  • the one or more first messages may comprise a secondary g N B (SgNB) addition request message.
  • the one or more first messages may comprise a secondary node (SN) addition request message.
  • the one or more first messages may further comprise a list of radio access bearers (e.g., E-UTRAN radio access bearers (E-RABs)) to be added (e.g., to be set up in the SN to serve the UE).
  • the list of radio access bearers may comprise a configuration of each radio access bearer.
  • the one or more first messages may further comprise a containerfrom MN to SN (e.g., CG-Configlnfo message).
  • the container from MN to SN may comprise the requested SCG configuration information, including the UE capabilities.
  • the containerfrom MN to SN may comprise a list of candidate cells in the SN for the UE and the latest measurement results for the candidate cells in the SN.
  • the container from MN to SN may comprise a list of candidate cells for SCG, where each element of the list of candidate cells may comprise carrier frequency and physical cell identifier (PCI)
  • the one or more first messages may further comprise a message type.
  • the one or more first messages may further comprise a UE identifier in the MN (e.g., M-NG-RAN node UE XnAP ID).
  • the one or more first messages may further comprise UE security capabilities.
  • the one or more first messages may further comprise an S-NG-RAN node security key.
  • the one or more first messages may further comprise an S-NG-RAN node UE aggregate maximum bit rate.
  • the one or more first messages may further comprise a selected PLMN.
  • the one or more first messages may further comprise a mobility restriction list.
  • the one or more first messages may further comprise an index to RAT and/or frequency selection priority.
  • the one or more first messages may further comprise a list of PDU sessions to be setup in the SN to serve the UE (e.g PDU session resources to be added list).
  • the list of PDU sessions may comprise a configuration of each PDU session.
  • the one or more first messages may further comprise a container from MN to SN (e.g., CG-Configlnfo message).
  • the container from MN to SN may comprise the requested SCG configuration information, including the UE capabilities.
  • the container from MN to SN may comprise a list of candidate cells in the SN for the UE and the latest measurement results for the candidate cells in the SN.
  • the container from MN to SN may comprise a list of candidate cells for SCG, where each element of the list of candidate cells may comprise carrier frequency and physical cell identifier (PCI).
  • PCI physical cell identifier
  • the one or more second messages may further comprise a message type
  • the one or more second messages may further comprise a UE identifier in the MN (e.g., MeNB UE X2AP ID).
  • the one or more second messages may further comprise a UE identifier in the SN (e.g., SgNB UE X2AP ID).
  • the one or more second messages may further comprise a list of admitted radio access bearers (e.g., E- RABs admitted to be added list).
  • the list of admitted radio access bearers may comprise configuration of admitted radio bearers.
  • the one or more second messages may further comprise a list of not admitted radio access bearers.
  • the one or more second messages may further comprise a container from SN to MN (e.g., CG-Configlnfo message).
  • the container from SN to MN may comprise the SCG configuration information.
  • the container from SN to MN may comprise a list of serving cells configured in the SN for the UE (e.g., one or more PS Cells and zero or more SCells).
  • the one or more second messages may further comprise a list of candidate PS Cells for the UE.
  • the one or more second messages may further comprise a message type.
  • the one or more second messages may further comprise a UE identifier in the MN (e.g., M- NG-RAN node UE XnAP ID).
  • the one or more second messages may further comprise a UE identifier in the SN (e.g., S-NG-RAN node UE XnAP ID).
  • the one or more second messages may further comprise a list of admitted PDU sessions (e.g., PDU session resources admitted to be added list).
  • the list of admitted PDU sessions may comprise configuration of admitted PDU sessions.
  • the one or more second messages may further comprise a list of not admitted PDU sessions.
  • the one or more second messages may further comprise a container from SN to MN (e.g., CG- Configlnfo message).
  • the container from SN to MN may comprise the SCG configuration information.
  • the container from SN to MN may comprise a list of serving cells configured in the SN for the UE (e.g., one or more PSCells and zero or more SCells).
  • the one or more second messages may further comprise a list of candidate PSCells for the UE.
  • the BS1 may comprise a secondary node (SN).
  • the BS1 may comprise an en-gNB.
  • the BS1 may comprise an S-NG-RAN node.
  • the BS2 may comprise a master node (MN).
  • the BS2 may comprise a MeNB.
  • the BS2 may comprise an M-NG-RAN node.
  • the one or more first messages may comprise a secondary g N B (SgNB) modification request message.
  • the one or more first messages may comprise a secondary node (SN) modification request message.
  • the one or more second messages may comprise a secondary gNB (SgNB) modification request acknowledge message.
  • the one or more second messages may comprise a secondary node (SN) modification request acknowledge message.
  • the one or more first messages may further comprise a list of E-RABs requested to be added for the UE (e.g., E-RABs to be added list) and/or a list of E-RABs requested to be modified for the UE (e.g., E-RABs to be modified list) and/or a list of E-RABs requested to be released for the UE (e.g., E-RABs to be released list).
  • the list of E-RABs requested to be added for the UE and/or the list of E-RABs requested to be modified for the UE and/or the list of E-RABs requested to be released for the UE may comprise E-RABs configuration, for example, E-RAB identifier, DRB identifier, QoS parameters etc.
  • the one or more first messages may further comprise a message type.
  • the one or more first messages may further comprise UE X2AP identifiers in the MN and the SN.
  • the one or more first messages may further comprise a cause of the SN modification request.
  • the one or more first messages may further comprise a UE context information.
  • the list of PDU sessions requested to be added for the UE and/or the list of PDU sessions requested to be modified for the UE and/or the list of PDU sessions requested to be released for the UE may comprise PDU session configuration, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the one or more first messages may further comprise a message type.
  • the one or more first messages may further comprise UE XnAP identifiers in the MN and the SN.
  • the one or more first messages may further comprise a cause of the SN modification request.
  • the one or more first messages may further comprise a UE context information.
  • the one or more second messages may further comprise a list of admitted E-RABs for the UE (e.g., E-RABs admitted to be added list) and/or a list of admitted to be modified E-RABs for the UE (e.g., E-RABs admitted to be modified list) and/or a list of admitted to be released E-RABs for the UE (e.g., E-RABs admitted to be released list).
  • a list of admitted E-RABs for the UE e.g., E-RABs admitted to be added list
  • a list of admitted to be modified E-RABs for the UE e.g., E-RABs admitted to be modified list
  • a list of admitted to be released E-RABs for the UE e.g., E-RABs admitted to be released list
  • the list of admitted E-RABs for the UE and/or the list of admitted to be modified E-RABs for the UE and/or the list of admitted to be released E-RABs for the UE may comprise E-RABs configuration, for example, E-RAB identifier, QoS parameters etc.
  • the one or more second messages may further comprise a list of not admitted E-RABs for the UE (e.g., E-RABs not admitted list).
  • the one or more second messages may further comprise a message type.
  • the one or more first messages may further comprise UE XnAP identifiers in the MN and the SN.
  • the one or more second messages may further comprise a list of admitted PDU sessions for the UE (e.g., PDU session resources admitted to be added list) and/or a list of admitted to be modified PDU sessions for the UE (e.g., PDU session resources admitted to be modified list) and/or a list of admitted to be released PDU sessions for the UE (e.g., PDU session resources admitted to be released list).
  • the list of admitted PDU sessions for the UE and/or the list of admitted to be modified PDU sessions for the UE and/or the list of admitted to be released PDU sessions for the UE may comprise PDU session configuration, for example, PDU session identifier, QoS parameters etc.
  • the one or more second messages may further comprise a list of not admitted PDU sessions for the UE (e.g., PDU session resources not admitted to be added list).
  • the one or more second messages may further comprise a message type.
  • the one or more first messages may further comprise UE XnAP identifiers in the MN and the SN.
  • the BS1 may comprise a secondary node (SN).
  • the BS1 may comprise an en-gNB.
  • the BS1 may comprise an S-NG-RAN node.
  • the BS1 may comprise a target SN.
  • the BS1 may comprise a target eNB.
  • the BS1 may comprise a target NG-RAN node.
  • the BS1 may comprise a target MN.
  • the BS1 may comprise a target ng-eNB.
  • the BS1 may comprise a target g N B .
  • the BS2 may comprise a master node (MN).
  • the BS2 may comprise a MeNB.
  • the BS2 may comprise an M-NG-RAN node.
  • the BS2 may comprise a target MN.
  • the BS2 may comprise a source eNB.
  • the BS2 may comprise a source NG-RAN node.
  • the BS2 may comprise a source MN.
  • the BS2 may comprise a source ng-eNB.
  • the BS2 may comprise a source g NB .
  • the one or more first messages may comprise an AI/ML information request message.
  • the one or more first messages may comprise an AI/ML action evaluation request message.
  • the one or more second messages may comprise an AI/ML information request message.
  • the one or more second messages may comprise an AI/ML action evaluation response message.
  • the one or more third messages may comprise an AI/ML information response message.
  • the one or more first messages may further comprise a parameter indicating which predictions are requested (e.g., the parameter indicating which predictions are requested may be a report characteristics parameter).
  • the parameter indicating which predictions are requested may comprise a list of predictions that are requested.
  • the list of predictions that are requested may comprise a predicted radio resource status.
  • the list of predictions that are requested may comprise a predicted number of active UEs.
  • the list of predictions that are requested may comprise a predicted RRC connections.
  • the one or more first messages may further comprise a parameter indicating whether to start or to stop the predictions that are requested (e.g., registration request parameter that may be equal to, for example, start or stop).
  • the one or more first messages may further comprise a list of cells to which the request applies.
  • the one or more first messages may further comprise a reporting periodicity.
  • the one or more first messages may further comprise a parameter indicating which measurements are requested (e.g., the parameter indicating which measurements are requested may be a report characteristics parameter).
  • the measurements that are requested may be, for example, a feedback information after one or more actions and/or other measurements used for AI/ML.
  • the parameter indicating which measurements are requested may comprise a list of measurements that are requested.
  • the list of measurements that are requested may comprise an average UE throughput in downlink.
  • the list of measurements that are requested may comprise an average UE throughput in uplink.
  • the list of measurements that are requested may comprise an average packet delay.
  • the list of measurements that are requested may comprise an average packet loss.
  • the list of measurements that are requested may comprise an energy cost.
  • the one or more first messages may further comprise a measurement identifier at the BS 1 and/or a measurement identifier at the BS2 corresponding to the requested predictions and/or measurements.
  • the one or more third messages may further comprise a list of the requested predictions that the BS2 is able to report to the BS1 (e.g., the parameter indicating which predictions will be provided may be a failed reporting characteristics parameter).
  • the list of the requested predictions that the BS2 is able to report to the BS1 may comprise a bitmap where each position corresponds to a specific prediction. For example, the first bit may correspond to the predicted radio resource status, the second bit may correspond to the predicted number of active UE, the third bit may correspond to the predicted RRC connections.
  • the one or more third messages may further comprise a list of the requested measurements that the BS2 is able to report to the BS1 (e.g., the parameter indicating which measurements will be provided may be a failed reporting characteristics parameter).
  • the list of the requested measurements that the BS2 is able to report to the BS1 may comprise a bitmap where each position corresponds to a specific measurement.
  • the fourth bit may correspond to the average UE throughput in downlink
  • the fifth bit may correspond to the average UE throughput in uplink
  • the sixth bit may correspond to the average packet delay
  • the seventh bit may correspond to the average packet loss
  • the eight bit may correspond to the energy cost.
  • the one or more third messages may further comprise the measurement identifier at the BS1 and/or the measurement identifier at the BS2 from the one or more first messages.
  • the one or more second messages may further comprise the measurement identifier at the BS1 and/or the measurement identifier at the BS2 from the one or more first messages.
  • the one or more second messages may further comprise a list of cells for which the predictions are reported.
  • the list of cells for which the predictions are reported may correspond to the list of cells for which the predictions are requested in the one or more first messages.
  • the list of cells for which the predictions are reported may comprise a list of cell identifiers (e.g., global NG-RAN cell identity).
  • the list of cells for which the predictions are reported may comprise for each cell identifier the predictions that are reported for this cell.
  • the predictions that are reported may comprise a predicted radio resource status and/or a predicted number of active UEs and/or a predicted RRC connections.
  • the one or more second messages may further comprise a UE associated information result parameter.
  • the UE associated information result parameter may comprise a list of UE identifiers.
  • the UE associated information result parameter may comprise for each of the UE identifiers, a UE performance parameter.
  • the UE performance parameter may comprise an average UE throughput in downlink and/or an average UE throughput in uplink and/or an average packet delay and/or an average packet loss.
  • the parameters inside the UE performance parameter may correspond to the measurements requested in the one or more first messages.
  • the one or more second messages may further comprise an energy cost parameter.
  • the energy cost parameter may comprise a measurement and/or a prediction of the energy cost.
  • FIG. 45 illustrates an example embodiment of the present disclosure.
  • a BS1 may configure measurements (e.g., signal quality measurements) to a UE.
  • the UE may perform the configured measurements and may report the results of the preformed measurements to the BS1.
  • the reported measurements e.g., signal quality measurements of one or more cells of the BS2 and of one or more cells of the BS3 may indicate that a BS2 and a BS3 are candidate base stations for the UE handover.
  • the BS1 may determine a need of a future handover of the UE.
  • the BS1 may determine the need of the future handover of the UE, for example, during a time interval between 50 seconds and 55 seconds from now.
  • the BS1 may determine that the BS2 and the BS3 are candidate base stations for the UE handover.
  • the BS1 may send an AI/ML action evaluation request message 4501 to the BS2.
  • the AI/ML action evaluation request message 4501 may request a prediction of admitted PDU sessions for the UE if the UE is handed over to the BS2 between 50 seconds and 55 seconds from now.
  • the AI/ML action evaluation request message 4501 may indicate PDU sessions requested to be added for the UE.
  • the AI/ML action evaluation request message 4501 may indicate that 8 PDU sessions may be requested to be added for the UE between 50 seconds and 55 seconds from now.
  • the AI/ML action evaluation request message 4501 may comprise PDU session configuration for each of the PDU sessions requested to be added for the UE, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the prediction of admitted PDU sessions for the UE may be requested for the time interval between 50 seconds and 55 seconds from now.
  • the BS1 may receive an AI/ML action evaluation response message 4502 from the BS2.
  • the AI/ML action evaluation response message 4502 may comprise a prediction of admitted PDU sessions for the UE
  • the AI/ML action evaluation response message 4502 may comprise a prediction that out of 8 PDU sessions, the BS2 may admit 6 PDU sessions during the time interval between 50 seconds and 55 seconds from now.
  • the BS1 may send an AI/ML action evaluation request message 4503 to the BS3.
  • the AI/ML action evaluation request message 4503 may request a prediction of admitted PDU sessions for the UE if the UE is handed over to the BS3 between 50 seconds and 55 seconds from now.
  • the AI/ML action evaluation request message 4503 may indicate PDU sessions requested to be added for the UE.
  • the AI/ML action evaluation request message 4503 may indicate that 8 PDU sessions may be requested to be added for the UE between 50 seconds and 55 seconds from now.
  • the AI/ML action evaluation request message 4503 may comprise PDU session configuration for each of the PDU sessions requested to be added for the UE, for example, PDU session identifier, S-NSSAI, QoS parameters etc.
  • the prediction of admitted PDU sessions for the UE may be requested for the time interval between 50 seconds and 55 seconds from now.
  • the BS1 may receive an AI/ML action evaluation response message 4504 from the BS3.
  • the AI/ML action evaluation response message 4504 may comprise a prediction of admitted PDU sessions for the UE.
  • the AI/ML action evaluation response message 4504 may comprise a prediction that out of 8 PDU sessions, the BS3 may admit 3 PDU sessions during the time interval between 50 seconds and 55 seconds from now.
  • the BS1 may select a base station for the UE handover.
  • the BS1 may select a base station for the UE handover among the candidate base stations BS2 and BS3.
  • the BS1 may select a base station for the UE handover based on the received AI/ML action evaluation response message 4502 and AI/ML action evaluation response message 4504.
  • the BS1 may select the BS2 for the UE handover based on the number of PDU sessions predicted to be admitted (e,gvia 6 in BS2 compared to 3 in BS3).
  • the BS1 may perform necessary steps for a handover execution of the UE with the BS2.
  • both BS2 and BS3 while receiving an AI/ML action evaluation request message, performing a prediction, and sending an AI/ML action evaluation response message, both BS2 and BS3 do not need to reserve resources for the UE (e.g., compared to a need to reserve resources after a handover request message). Also amount of signaling during an AI/ML action evaluation procedure may be less than during a handover preparation procedure.
  • FIG. 46 illustrates an example embodiment of the present disclosure.
  • an MN may send to an SN, an SN addition request message 4601.
  • the SN addition request message 4601 may comprise a request to add 8 PDU sessions for a UE.
  • the SN addition request message 4601 may comprise a request for a prediction of admitted PDU sessions for the UE, for example, for time points 5 seconds, 10 seconds, 15 seconds, and 20 seconds from now.
  • the SN may perform admission control, resource reservation, and selection of PSCell and SCells for the UE.
  • the result of the admission control is that 5 out of 8 PDU sessions are admitted.
  • the MN may receive from the SN, an SN addition request acknowledge message 4602.
  • the SN addition request acknowledge message 4602 may comprise a list of admitted PDU sessions. For example, 5 out of 8 PDU sessions are admitted.
  • the SN addition request acknowledge message 4602 may comprise the requested prediction of admitted PDU sessions for the UE. For example, the prediction may indicate that 5 seconds from now the SN may admit 5 PDU sessions, 10 seconds from now the SN may admit 6 PDU sessions, 15 seconds from now the SN may admit 8 PDU sessions, 20 seconds from now the SN may admit 8 PDU sessions.
  • the MN may configure the UE to connect to the SN (e.g., RRC reconfiguration 4603, RRC reconfiguration complete 4604) and inform the SN (e.g., SN reconfiguration complete 4605).
  • the UE may perform a random access procedure 4606 with the SN to connect to the SN.
  • the MN may send to the SN, an SN modification request message 4607.
  • the SN modification request message 4607 may comprise a request to add the 3 remaining PDU sessions for the UE.
  • the MN may send to the SN, the SN modification request message 4607, for example, based on the prediction of admitted PDU sessions for the UE received in the SN addition request acknowledge message 4602.
  • the MN may send to the SN, the SN modification request message 4607 after 15 seconds after sending the SN addition request message 4601 to the SN (i.e., after the time for which the prediction indicates that the SN can admit 8 PDU sessions for the UE).
  • the prediction may provide to the MN information that it can offload 5 PDU session now and 3 PDU session 15 seconds later.
  • the MN may decide to wait for 15 seconds and then start offloading (e.g. , send an SN addition request), for example, to reduce signaling between the MN and the SN.
  • FIG. 47 illustrates an example embodiment of the present disclosure.
  • FIG. 48 illustrates an example embodiment of the present disclosure.

Landscapes

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

Abstract

Un procédé peut faire appel à la réception, par une première station de base en provenance d'une seconde station de base, d'un ou de plusieurs premiers messages demandant une prédiction de sessions d'unité de données de protocole (PDU) admises (ou non admises ou à la fois admises et non admises) pour un dispositif sans fil. Le ou les premiers messages indiquent des sessions PDU demandées à ajouter pour le dispositif sans fil. Le procédé peut également faire appel à la détermination, par la première station de base, de la prédiction de sessions PDU admises pour le dispositif sans fil. Le procédé peut en outre faire appel à l'envoi, par la première station de base à la seconde station de base, d'un ou de plusieurs seconds messages comprenant la prédiction de sessions PDU admises (ou non admises ou les deux) pour le dispositif sans fil.
PCT/US2024/047670 2023-09-22 2024-09-20 Gestion de session d'unité de données de protocole (pdu) pendant la mobilité dans un réseau d'accès radio Pending WO2025064801A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363539954P 2023-09-22 2023-09-22
US63/539,954 2023-09-22

Publications (1)

Publication Number Publication Date
WO2025064801A1 true WO2025064801A1 (fr) 2025-03-27

Family

ID=93015019

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/047670 Pending WO2025064801A1 (fr) 2023-09-22 2024-09-20 Gestion de session d'unité de données de protocole (pdu) pendant la mobilité dans un réseau d'accès radio

Country Status (1)

Country Link
WO (1) WO2025064801A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11039349B2 (en) * 2017-03-25 2021-06-15 Lg Electronics Inc. Method and apparatus for enhancing procedure for LTE/NR interworking in wireless communication system
US20220053390A1 (en) * 2018-11-09 2022-02-17 Lg Electronics Inc. Support of inter-gnb handover in higher layer multi-connectivity
EP4236419A1 (fr) * 2020-10-20 2023-08-30 NEC Corporation Station de base secondaire, station de base maîtresse et procédé associé

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11039349B2 (en) * 2017-03-25 2021-06-15 Lg Electronics Inc. Method and apparatus for enhancing procedure for LTE/NR interworking in wireless communication system
US20220053390A1 (en) * 2018-11-09 2022-02-17 Lg Electronics Inc. Support of inter-gnb handover in higher layer multi-connectivity
EP4236419A1 (fr) * 2020-10-20 2023-08-30 NEC Corporation Station de base secondaire, station de base maîtresse et procédé associé

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "TP for the solution of SN change failure", vol. RAN WG3, no. Chongqing, CN; 20191014 - 20191018, 4 October 2019 (2019-10-04), XP051809610, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_105bis/Docs/R3-195018.zip R3-195018_SON_SNchange_TP_Xn.doc> [retrieved on 20191004] *

Similar Documents

Publication Publication Date Title
US12501359B2 (en) Energy saving in communications network
US20240107410A1 (en) Energy Efficiency in Radio Access Network
US20240031899A1 (en) Mobility in Radio Access Network
US20250287249A1 (en) Measurements in a Radio Access Network
US20250184823A1 (en) Load Prediction in Radio Access Network
US20240107406A1 (en) Feedback In Radio Access Network
WO2024207010A1 (fr) Mesure dans un réseau d&#39;accès radio
US20250374179A1 (en) Information Exchange in a Radio Access Network
US20250374105A1 (en) Wireless Device Measurement Reporting in a Radio Access Network
US20250317786A1 (en) Model Performance Evaluation in Radio Access Network
US20250351053A1 (en) Wireless Device Predictions
WO2025064801A1 (fr) Gestion de session d&#39;unité de données de protocole (pdu) pendant la mobilité dans un réseau d&#39;accès radio
WO2025049752A1 (fr) Ajout/changement de nœud secondaire dans un réseau d&#39;accès radio
WO2025090896A1 (fr) Mobilité de couche inférieure dans réseau d&#39;accès radio
WO2025111292A1 (fr) Commutation de cellule rapide dans un réseau d&#39;accès radio
WO2025137520A1 (fr) Commutation de cellules dans un réseau d&#39;accès radio
WO2025193954A1 (fr) Informations supplémentaires pour modification de couverture dans un réseau d&#39;accès radio
WO2024207013A1 (fr) Échange d&#39;informations de stations de base dans un réseau d&#39;accès radio
WO2024091693A1 (fr) Trajectoire de dispositif sans fil dans un réseau d&#39;accès radio
WO2024263578A1 (fr) Couverture et capacité dans un réseau d&#39;accès radio
WO2025184532A1 (fr) Rétroaction de modification de couverture dans un réseau d&#39;accès radio
WO2025006761A2 (fr) Couverture et capacité dans un réseau d&#39;accès radio
WO2025184341A1 (fr) Rapport de rétroaction de modification de couverture dans un réseau d&#39;accès radio
WO2025260008A1 (fr) Prédictions par un dispositif sans fil dans un réseau d&#39;accès radio
WO2025198952A1 (fr) Modification de couverture dans un réseau d&#39;accès radio

Legal Events

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

Ref document number: 24786936

Country of ref document: EP

Kind code of ref document: A1